JP2020123791A - Remote communication system, communication method, and program - Google Patents

Abstract

To provide a remote communication system capable of achieving communication with a guest without modifying application software of a communication terminal.SOLUTION: A remote communication system 100 in which at least a first communication terminal 10B and a second communication terminal 10A communicate with each other through a communication management system 50, includes: a destination list registration unit 67, when a guest management unit accepts a registration of a user and a guest, registers the guest as a requester and the user as a destination in a destination list management information 53 and registers the user as the requester and the guest as the destination in the destination list management information; and a communications management unit 39, when there is a request to start communication from the first communication terminal operated by the user or the second communication terminal operated by the guest, connects the first communication terminal and the second communication terminal based on the destination list management information.SELECTED DRAWING: Figure 1

Description

The present invention relates to a remote communication system, a communication method, and a program.

One communication terminal at a remote location transmits the image data captured by the camera and the audio data captured by the microphone to the other communication terminal, and the image data transmitted by the one communication terminal is displayed on the display of the other communication terminal. A remote communication system in which voice data is output from a speaker is known. In this remote communication system, one communication terminal similarly displays the image data transmitted from the other communication terminal on the display and outputs the voice data from the speaker.

In the remote communication system, in order for one communication terminal to call the other communication terminal, the user of one communication terminal needs to know some identification information such as a telephone number that specifies a communication partner. Here, when a meeting with a person outside the company or a meeting with an employee of another department is held, there is also a demand for a one-time meeting with a user who does not have identification information.

Therefore, a technology has been devised to hold a conference at a remote place without registration of identification information in advance (for example, refer to Patent Document 1). Patent Document 1 discloses a system in which a host creates a virtual conference room in advance and only a user who knows the identification information (URL) and the invitation code of the conference room can participate in the conference. .. A user who is a guest can temporarily join the conference without registering information about the guest in advance.

However, the conventional remote communication system has a problem that remote communication with a guest cannot be realized without adding processing necessary for communication with the guest to application software on the communication terminal side. In other words, the application software of the communication terminal needs to be improved in order to communicate with the guest.

The application software runs on the OS (Operating System) of the information processing apparatus, and is developed for each type of OS. There is also a dedicated terminal dedicated to the remote communication system. Therefore, application software is prepared for dedicated terminals and for various OSs (there are at least five types of OSs on the market). In order to realize communication with a guest, work of installing a communication function with a guest in all types of application software occurs.

In view of the above problems, an object of the present invention is to provide a remote communication system that can realize communication with a guest without improving application software of a communication terminal.

In view of the above problems, the present invention is a remote communication system in which at least a first communication terminal and a second communication terminal communicate via a communication management system,
The communication management system includes a storage unit that stores destination list management information in which destinations that can be designated as a communication destination by a communication request source are stored, a guest management unit that manages registration of information about a user who invites guests and the guest. Section and the guest management unit accepts registration of the user and the guest, registers the guest in the destination list management information with the guest as the request source and the user as the destination, and the user as the request source, the When there is a request to start communication from a destination list registration unit that registers a guest as the destination in the destination list management information and the first communication terminal operated by the user or the second communication terminal operated by the guest A communication management unit that connects the first communication terminal and the second communication terminal based on the destination list management information.

It is possible to provide a remote communication system that can realize communication with a guest without improving application software of a communication terminal.

It is an example of the figure explaining the outline of the processing which the host of a meeting registers a guest. It is an example of a schematic configuration diagram of a remote communication system. It is an example of a hardware configuration diagram of a communication terminal. It is an example of a hardware configuration diagram of a communication management system. It is an example of a functional block diagram showing in block form the functions of a communication management system, a communication terminal, and a client PC included in a remote communication system. It is an example of a sequence diagram showing a process of displaying a guest management screen by a communication terminal or a client PC. It is a figure which shows an example of the guest management screen (with invitation authority) displayed on a communication terminal or a client PC display. It is a figure which shows an example of the guest management screen (without invitation authority) displayed on a communication terminal or a client PC display. It is an example of a sequence diagram showing a process in which the guest management server creates the invitation information. It is a figure which shows an example of the invitation information creation dialog displayed on the display of a communication terminal or a client PC. It is a figure which shows an example of the guest management screen (when invitation information creation succeeds) displayed on the display of a communication terminal or a client PC. It is a figure which shows an example of the invitation information creation dialog (at the time of invitation information creation error) displayed on the display of a communication terminal or a client PC. It is an example of a sequence diagram showing a process in which a guest who receives an invitation registers guest information in a guest management server. It is a figure which shows an example of the guest registration screen displayed on the display of a client PC. It is a figure which shows an example of the text of the guest registration notification mail transmitted to a guest by registration of guest information. It is a figure which shows an example of the guest registration screen (when registration succeeds) displayed on the display of a client PC. It is a figure which shows an example of the guest registration screen (at the time of registration error) displayed on the display of a client PC. It is an example of a sequence diagram showing a process in which the organizer browses or deletes registered guest information. It is a figure which shows an example of the registered guest information confirmation dialog displayed on the display of a communication terminal or a client PC. It is a figure which shows an example of the registered guest confirmation dialog (when guest information deletion succeeded) displayed on the display of a communication terminal or client PC. It is a figure which shows an example of the text of a guest deletion notification mail. It is an example of a sequence diagram showing a procedure for a sponsor to delete invitation information. It is a figure which shows an example of the invitation information deletion dialog displayed on the display of a communication terminal or client PC. It is a figure which shows an example of the guest management screen (when invitation information deletion succeeds) displayed on the display of a communication terminal or a client PC. It is a flowchart figure which shows the flow of the whole process of a guest account processing server. FIG. 26 is an example of a flowchart showing the guest account creation processing of step S101 of FIG. 25. FIG. 26 is an example of a flowchart showing the guest destination list creation processing of step S102 of FIG. 25. FIG. 26 is an example of a flowchart showing the expired invitation information deletion processing of step S103 of FIG. 25. FIG. 26 is an example of a flowchart showing the invalidation guest account deletion processing of step S104 of FIG. 25. It is a sequence diagram which shows the example of a process of the preparation stage of communication of a remote communication system. It is a figure which shows an example of the destination selection screen which a communication terminal displays. It is a sequence diagram which shows the example of the communication processing of a remote communication system. It is an example of a sequence diagram of a process in which the organizer registers invitation information and guest information from the guest management screen. It is a figure which shows an example of the invitation information creation dialog displayed on the display of a communication terminal or a client PC. It is a figure which shows an example of the guest management screen (at the time of successful creation of invitation information) displayed on the display of a communication terminal or a client PC. It is an example of a sequence diagram showing a process in which the host invites an additional guest on the guest management screen (when the invitation information is successfully created). It is a figure which shows an example of the additional invitation dialog displayed on the display of a communication terminal or client PC. It is a figure which shows an example of the guest management screen (at the time of successful addition invitation) displayed on the display of a communication terminal or a client PC.

Hereinafter, a remote communication system and a communication method performed by the remote communication system will be described as an example of a mode for carrying out the present invention with reference to the drawings.

<Outline of processing>
First, the outline of the processing of the remote communication system will be described with reference to FIG. FIG. 1 is an example of a diagram for explaining an outline of a process in which a meeting organizer registers a guest.

(1) As shown in FIG. 1A, the remote communication system uses a destination list management DB 53 (Data Base). The destination list management DB 53 is a table in which destination users that can be called by a communication request source user are registered. According to FIG. 1(a), Mr. A can call to Mr. B, and Mr. B can also call to Mr. A. In this way, unless the users are registered in the destination list management DB 53 with each other, communication is not possible.

(2) Mr. A who wants to hold a meeting with the guest, for example, becomes the organizer of the meeting and notifies the guest of how to register the guest information (FIG. 1B). The guest who has received the notification from the organizer (Mr. A) of the conference can register his or her own information as a guest in the guest management DB 54. Alternatively, Mr. A, who is the organizer of the conference, may register the guest information in the guest management DB 54. Mr. A or a guest registers, for example, a guest name or a mail address. As a result, the server side generates a guest ID and a token.

(3) The guest account processing server 60 monitoring the guest management DB 54 detects the guest registration and registers the guest (guest ID) in the destination list management DB 53 (FIG. 1(c)). That is, a guest is registered in the address of the organizer, Mr. A, and Mr. A is registered in the address of the guest. By thus registering Mr. A and the guest in the destination list management DB 53, Mr. A and the guest can start remote communication.

Further, since the processing described in FIG. 1 is executed on the server side (cloud), the function of the application software operating on the communication terminal 10 used by the guest for remote communication needs only the function for the guest to communicate. There is no need to improve the application software.

<About terms>
Remote communication means that a user at a remote place communicates using visual information or auditory information. As a remote communication, for example, a video conference is known.

The organizer is a user of the remote communication system who has the authority to invite guests.

Guest means a temporary attendee. In this embodiment, the user is a user who can use the remote communication system when invited.

<System configuration example>
FIG. 2 shows an example of a schematic configuration diagram of a remote communication system. As shown in FIG. 2, the remote communication system 100 has a plurality of communication terminals 10 capable of communicating via the communication network 2, a client PC 20, a relay device 30, and a communication management system 50.

The communication network 2 has one or more of the Internet, a LAN, and a mobile communication line, and the communication terminal 10, the communication management system 50, and the relay device 30 are communicatively connected to each other. The LAN includes not only a wired LAN but also a wireless LAN. The mobile communication line includes communication systems such as 5G, LTE (Long Term Evolution), WiMAX, and CDMA. It is not always necessary to go through the Internet, and communication may be performed within the LAN. In addition, the mobile communication line may not be used.

The communication terminal 10 establishes a communication session with one or more other communication terminals 10 or client PCs 20 through the communication management system 50, and through the relay device 30 designated by the communication management system 50, image data, audio data, and material data. (Hereinafter referred to as content data) is transmitted and received. This enables remote communication between a plurality of remote bases. The image data may include either a still image or a moving image.

The communication terminal 10 may be a terminal dedicated to the remote communication system 100 or a general-purpose information processing terminal. The general-purpose information processing device is, for example, a PC (Personal Computer), a smartphone, a tablet terminal, or the like, and operates as the communication terminal 10 by executing application software dedicated to the remote communication system 100. In addition, in both cases of a dedicated terminal and a general-purpose terminal, the organizer can serve as a registration terminal for performing the processing described in FIG.

Further, when the communication terminal 10 is a general-purpose terminal, the general-purpose terminal executes remote application by executing application software dedicated to the remote communication system 100, and by executing general-purpose browser software. In some cases, it enables remote communication. In this embodiment, the latter communication terminal 10 is called a client PC 20.

OSs included in general-purpose information processing devices include Windows (registered trademark), MacOS (registered trademark), Android (registered trademark), iOS (registered trademark), and Linux (registered trademark). The guest can participate in the conference as a guest by operating the communication terminal 10 having any OS.

The client PC 20 serves as the communication terminal 10 when executing the browser software, and serves as a registration terminal for the guest to register guest information described later. The guest causes the browser software to communicate with the guest management server 44 and registers the guest information.

The communication management system 50 is one or more computers that manage the entire remote communication system 100 of this embodiment. Since the communication management system 50 is a server, it has the function of an information processing device. In FIG. 2, it has an authentication management server 41, a terminal management server 42, a destination list management server 43, a guest management server 44, a session management server 45, and a guest account processing server 60. Of the servers included in the communication management system 50, any server other than the guest account processing server 60 is simply referred to as “each server”. Each server manages a database required for controlling the remote communication system 100 in response to a request from the communication terminal management system 40.

Moreover, the communication terminal management system 40 transmits the information acquired from each server to the communication terminal 10, and also transmits the information received from each communication terminal 10 to the server which handles this information. Further, when the communication terminal 10 communicates with the communication management system 50 using browser software, the screen information described in HTML, script language (JavaScript: registered trademark), CSS (Cascade Style Sheet), or the like is displayed. It is generated and transmitted to the communication terminal 10. Such screen information may be referred to as a web page or web application.

The authentication management server 41 authenticates the communication terminal 10 by referring to the authentication management DB 51. If the authentication is successful, the organizer or guest can log in to the communication management system 50. The DB is a storage unit that stores information. The same applies to each DB other than the authentication management DB 51.

The terminal management server 42 updates the operating status (status) of the communication terminal 10 on the terminal management DB 52, and provides the operating status of each communication terminal 10 acquired from the terminal management DB 52 to other servers. The operating state is a state of the communication terminal 10 in the remote communication system 100. The operating state includes offline, online (transmittable), online (in a meeting), online (temporarily suspended), and the like.

The address list management server 43 updates the address list management DB 53 (guest registration and deletion) in response to the request from the guest account processing server 60, and also updates the information registered in the address list management DB 53. Provide to other servers. The general user can be registered in the destination list management DB 53 by an administrator or a user who desires registration.

The session management server 45 functions as a call control server that performs call control such as starting a session with two or more communication terminals 10 when a call arrives at a destination. Call control relates to connections such as receiving an outgoing call to start communication and letting the other party receive the incoming call, receiving the other party's response to the incoming call, disconnecting the other communication when either one disconnects the communication, etc. A series of processes. Two or more communication terminals 10 with which a session has been established (communicating) are associated with the session management DB 55.

The guest management server 44 registers or deletes the invitation information and guest information transmitted from the communication terminal 10 or the client PC 20 in the guest management DB 54. In addition, in response to a request from the guest account processing server 60, the invitation information is deleted, the guest information is updated, and the guest information is deleted.

The guest account processing server 60 repeatedly refers to the guest management DB 54 via the guest management server 44 regardless of the request from the communication terminal management system 40. Then, the authentication management DB 51, the terminal management DB 52, the destination list management DB 53, and the guest management DB 54 are updated based on the guest information and the like.

In addition, the communication management system 50 also manages the state of the relay device 30, selects the relay device 30 used for remote communication, manages the communication log, and so on.

The relay device 30 is a computer that relays content data from one communication terminal 10 to another communication terminal 10 among a plurality of communication terminals 10 that perform remote communication. The relay device 30 has a function of an information processing device. The relay device 30 monitors the band with the communication terminal 10 and transmits image data of a quality (high image quality, medium image quality, low image quality) suitable for the band. Although only one relay device 30 is illustrated in FIG. 2, there are many relay devices 30 in many cases. The communication management system 50 may include a relay device.

<Hardware configuration example>
<<Example of hardware configuration of communication terminal>>
FIG. 3 is a hardware configuration diagram of the communication terminal 10 according to the present embodiment of the present invention. The communication terminal 10 of the present embodiment is a ROM (Read Only Memory) that stores programs used to drive the CPU 101 such as a CPU (Central Processing Unit) 101 that controls the operation of the entire communication terminal 10 and an IPL (Initial Program Loader). 102, a RAM (Random Access Memory) 103 used as a work area of the CPU 101, a flash memory 104 for storing various data such as a terminal program, image data, and audio data. Further, the communication terminal 10 controls reading or writing (storing) of data from or to a recording medium 106 such as an SSD (Solid State Drive) 105 or a flash memory, which controls reading or writing of various data from or into the flash memory 104 under the control of the CPU 101. The media drive 107, the operation button 108 operated when selecting the destination of the communication terminal 10, the power switch 109 for switching the power of the communication terminal 10 ON/OFF, and the data transmission using the communication network 2. A network I/F (Interface) 111 for performing the operation is provided.

In addition, the communication terminal 10 includes a built-in camera 112 that captures image data of a subject under the control of the CPU 101 to obtain image data, an image sensor I/F 113 that controls driving of the camera 112, a built-in microphone 114 that inputs voice, It has a built-in speaker 115 that outputs a sound, and 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. Further, the communication terminal 10 illustrates a display I/F 117 that transmits image data to an external display 120 under the control of the CPU 101, an external device connection I/F 118 for connecting various external devices, and the above-described components. As shown in FIG. 3, a bus line 110 such as an address bus or a data bus for electrically connecting is provided.

The display 120 is a display device including 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, HDMI (registered trademark) (High-Definition Multimedia Interface), or DVI (Digital Video). Interactive) signal cable.

The camera 112 includes a lens and a solid-state imaging device that converts light into electric charge to digitize an image (video) of a subject. As the solid-state imaging device, 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 recording medium 106 is configured to be attachable to and detachable from the communication 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 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 terminal program may be stored in the ROM 102 instead of the flash memory 104.

Further, it is assumed that the client PC 20 has the same hardware configuration as that of the communication terminal 10 or if the client PC 20 has a different hardware configuration, it does not hinder the description of the present embodiment.

<<Example of hardware configuration of communication management system>>
FIG. 4 is a hardware configuration diagram of the communication management system 50 according to the present embodiment of the present invention. That is, the communication terminal management system 40, the authentication management server 41, the terminal management server 42, the destination list management server 43, the guest management server 44, the session management server 45, and the guest account processing server 60 are hardware as shown in FIG. Have a configuration.

The communication management system 50 includes a CPU 201 that controls the overall operation of the communication management system 50, a ROM 202 that stores a program used for driving the CPU 201 such as an IPL, a RAM 203 that is used as a work area of the CPU 201, and various types of communication management programs and the like. It has an HD 204 for storing data. Further, the communication management system 50 controls the reading or writing (storing) of data from or into a recording medium 206 such as a HDD (Hard Disk Drive) 205 or a flash memory that controls reading or writing of various data from or into the HD 204 under the control of the CPU 201. It has a media drive 207. The communication management system 50 also includes a display 208 for displaying various information such as a cursor, a menu, a window, characters, or an image, a network I/F 209 for data transmission using the communication network 2, characters, numerical values, It has a keyboard 211 having a plurality of keys for inputting various instructions and the like, and a mouse 212 for selecting and executing various instructions, selecting a processing target, and moving a cursor. The communication management system 50 also includes a CD-ROM drive 214 that controls reading and writing of various data from and to a CD-ROM (Compact Disc Read Only Memory) 213, which is an example of a removable recording medium, and the above-described components. As shown in FIG. 4, a bus line 210 such as an address bus or a data bus for electrically connecting is provided.

The communication 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 communication management program may be stored in the ROM 202 instead of the HD 204.

Further, it is assumed that the relay device 30 has the same hardware configuration as the communication management system 50, or if the relay device 30 has a different hardware configuration, it does not hinder the description of the present embodiment.

<About functions>
Next, the function of the remote communication system 100 will be described with reference to FIG. FIG. 5 is a functional block diagram showing the functions of the communication management system 50, the communication terminal 10, and the client PC 20 included in the remote communication system 100 in block form. The function of the relay device 30 will be described as needed.

<<Functional configuration of communication terminal>>
The communication terminal 10 includes a second communication unit 11, an operation reception unit 12, a communication control unit 13, an imaging unit 14, a voice input unit 15, a voice output unit 16, a display control unit 17, and a storage/readout unit 18. ing. Each of these units has a function or a function realized by any of the components shown in FIG. 3 being operated by an instruction from the CPU 101 according to a terminal program expanded from the flash memory 104 to the RAM 103. It is a means. The terminal program is assumed to be application software developed for each OS, but may be browser software.

Further, the communication terminal 10 has the storage unit 19 realized by the RAM 103 shown in FIG. 3 and the flash memory 104 shown in FIG.

The second communication unit 11 transmits/receives various data (or information) to/from the communication management system 50 or the relay device 30 via the communication network 2. The second communication unit 11 starts reception of each state information indicating the status of each communication terminal 10 as a destination candidate from the communication management system 50 before starting a call with a desired destination terminal. It should be noted that this state information indicates not only the operating state of each communication terminal 10 (online or offline state) but also a detailed state such as whether or not a call is possible or a call is in progress when online.

The operation reception unit 12 receives various inputs from the operator to the communication terminal 10. For example, when the operator performs an operation of turning on the power of the communication terminal 10, the operation receiving unit 12 receives the operation and controls the power to be turned on. In addition, various operations including input of information to the communication terminal 10 are accepted.

When the communication terminal 10 is a dedicated terminal, the communication control unit 13 logs in from the second communication unit 11 via the communication network 2 to the communication management system 50 to request a login when the power ON is accepted. The request information and the current IP address of the request source terminal are automatically transmitted. When the communication terminal 10 is a general-purpose terminal, the same processing is performed upon activation of application software or a login operation by the user. Further, when the communication terminal 10 is a dedicated terminal and the operator performs an operation to turn off the power of the communication terminal 10, the second communication unit 11 transmits state information indicating that the power is turned off to the communication management system 50. After that, the communication terminal 10 turns off the power. As a result, the communication management system 50 side can recognize that the communication terminal 10 has been switched from power ON to power OFF. When the communication terminal 10 is a general-purpose terminal, similar processing is performed when the application software ends or the user logs off.

Further, the communication control unit 13 performs various communication controls such as establishing and disconnecting a session for transmitting and receiving content data with another communication terminal 10 via the relay device 30. The communication control unit 13 according to the present embodiment includes the communication ID of the communication terminal 10 in the data to be transmitted to the communication management system 50 and transmits the data.

The communication ID is an example of identification information of an account that can participate in a session in which content data is transmitted and received using the communication terminal 10. The communication ID may be, for example, a user ID that is operator identification information, an application ID that is application identification information, or a contract ID that is identification information of a contractor of the communication terminal 10. The communication ID may be information in which at least two of letters, numbers, symbols, and various indicia are combined. It may be an email address. Not only the user but also the guest is identified by the communication ID.

Further, ID is an abbreviation of Identification and means an identifier or identification information. The ID refers to a name, a code, a character string, a numerical value, or a combination of one or more of these, which is used to uniquely distinguish a specific object from a plurality of objects. The same applies to other IDs.

The imaging unit 14 converts the imaging data obtained by imaging the subject into predetermined image data and outputs the image data. The communication terminal 10 may have a plurality of imaging units 14.

After the voice of the operator is converted into a voice signal by the microphone 114, the voice input unit 15 converts the voice signal into predetermined voice data and outputs the voice data. The audio output unit 16 converts the audio data into an audio signal, outputs the audio signal to the speaker, and causes the speaker 115 to output the audio.

The display control unit 17, for example, causes the display 120 to display the image data included in the content data received by the communication terminal 10. Further, the display control unit 17 can cause the display 120 to display the information of the destination list (the destination selection screen described later) received from the communication management system 50.

The storage/readout unit 18 stores various data in the storage unit 19 and reads various data stored in the storage unit 19.

The storage unit 19 stores, for example, the above-mentioned communication ID and authentication management information such as a password corresponding to the communication ID. The storage unit 19 overwrites and stores the image data and the audio data received when a call is made with the destination terminal each time they are received. Among these, the image is displayed on the display 120 by the image data before being overwritten, and the sound is output from the speaker 115 by the audio data before being overwritten.

<<Functional configuration of communication management system>>
The communication management system 50 has each server shown in FIG. 1, and each server has a functional block and a database according to the function of the server. In FIG. 5, the communication terminal management system 40 has the first communication unit 31, the screen information generation unit 32, and the mail transmission unit 33, the authentication management server 41 has the terminal authentication unit 56 and the authentication management DB 51, and the terminal management server. 42 has a terminal management unit 57 and a terminal management DB 52, the destination list management server 43 has a destination list management unit 58 and a destination list management DB 53, and the guest management server 44 has a guest management unit 59 and a guest management DB 54. The session management server 45 has a communication management unit 39 and a session management DB 55.

Each of these functions is a function or function realized by any one of the components shown in FIG. 4 being operated by an instruction from the CPU 201 according to the communication management program expanded from the HD 204 onto the RAM 203. Is a means to do. The database of each server is built on the HD 204 or the RAM 203 shown in FIG.

Next, each functional configuration of the communication management system 50 will be described in detail. The first communication unit 31 transmits/receives various data (or information) to/from the communication terminal 10 or the relay device 30 via the communication network 2.

The screen information generation unit 32 generates screen information of a screen displayed by the communication terminal 10 or the client PC 20 using the information transmitted from each server. If the communication terminal 10 is a dedicated terminal or is executing application software, data indicating the structure of the screen is not necessary, and therefore information may be simply transmitted. For the client PC 20, data representing the screen structure, decoration, etc. is also generated by HTML, CSS, JavaScript (registered trademark), or the like.

The terminal authentication unit 56 determines whether the combination of the communication ID and the password included in the login request information received via the first communication unit 31 is included in the authentication management DB 51, and thereby the communication terminal 10 Authenticate. The terminal authentication unit 56 also authenticates the guest with the same mechanism.

The terminal management unit 57 associates and stores, in the terminal management DB 52, the terminal name, the operating state, the reception date and time of the request information, and the IP address of the request source terminal for each communication ID. For example, the terminal management unit 57 causes the terminal management DB 52 of the terminal management DB 52 to be based on the state information sent from the communication terminal 10 to turn off the power when the operator turns the communication terminal 10 off. Change the operating status from online to offline. In addition, the terminal management unit 57 registers and deletes the guest communication ID and the terminal name in the terminal management DB 52 in response to a request from the guest account processing server 60.

The destination list management unit 58 searches the destination list management DB 53 using the communication ID of the request source terminal that made the login request as a key, and extracts the communication ID of the destination terminal that can communicate with the request source terminal. Further, the destination list management unit 58 searches the destination list management DB 53, and also extracts the communication IDs of the other communication terminals 10 that have registered the communication ID of the request source terminal as a destination terminal candidate. In addition, the destination list management unit 58 registers the guest communication ID as the communication ID of the request source terminal in the destination list management DB 53 in response to the request from the guest account processing server 60, and sets the communication ID of the host as the communication ID of the destination terminal. Register the communication ID. Also, the communication ID of the organizer is registered as the communication ID of the request source terminal, and the communication ID of the guest is registered as the communication ID of the destination terminal.

The guest management unit 59 generates invitation information based on the information transmitted from the communication terminal 10 or the client PC 20, registers it in the guest management DB 54, and stores the guest information based on the information transmitted from the communication terminal 10 or the client PC 20. It is generated and registered in the guest management DB 54. In addition, the guest management unit 59 deletes the invitation information from the guest management DB 54 and updates or deletes the guest information in response to a request from the guest account processing server 60.

The communication management unit 39 controls a session managed by the communication management system 50. The session control includes, for example, control for establishing a session, control for allowing the communication terminal 10 to participate in the established session, control for disconnecting the session, generation of a session ID, and the like. In addition, the communication management unit 39 stores the communication ID of the communication terminal 10 that has requested the start of the session, the communication ID of the destination terminal, and the like in the session management DB 55 in association with the session ID that is the identification information of the session. ,to manage.

The communication management system 50 further has a guest account processing server 60. The guest account processing server 60 includes a guest information acquisition unit 61, an invitation information acquisition unit 62, a determination unit 63, an authentication management information creation unit 64, a terminal management registration unit 65, a guest information update unit 66, a destination list registration unit 67, and an invitation. It has an information deleting unit 68. Each of these functions is a function or function realized by one of the components shown in FIG. 4 operating according to an instruction from the CPU 201 according to a communication management program expanded from the HD 204 onto the RAM 203. Is a means to do.

The guest information acquisition unit 61 acquires guest information via the guest management server 44 at regular intervals or at some event (notification from each server, instruction from the administrator, etc.). The invitation information acquisition unit 62 acquires the invitation information via the guest management server 44 every certain period or every event (notification from each server, instruction from the administrator, etc.).

The determination unit 63 determines whether the guest information or the invitation information is in a predetermined state, and when the guest information or the invitation information is in a predetermined state, performs processing according to the state, the authentication management information creation unit 64, the terminal management registration unit. 65, the guest information update unit 66, the destination list registration unit 67, or the invitation information deletion unit 68 is called.

The authentication management information creation unit 64 transmits the guest ID and the token included in the guest information acquired from the guest management server 44 to the authentication management server 41 and causes the authentication management DB 51 to register them. This allows guests to log in. Further, the authentication management information creation unit 64 causes the authentication management server 41 to delete the information regarding the guest registered in the authentication management DB 51.

The terminal management registration unit 65 transmits the guest ID and the guest name included in the guest information acquired from the guest management server 44 to the terminal management server 42 and registers them in the terminal management DB 52. As a result, the operating state of the communication terminal 10 used by the guest is managed. In addition, the terminal management registration unit 65 causes the terminal management server 42 to delete the information regarding the guest registered in the terminal management DB 52.

The guest information update unit 66 requests the guest management server 44 to update the flag of the guest information, delete the guest information, and the like. The destination list registration unit 67 transmits the guest ID acquired from the guest management server 44 and the invitation source communication ID, which is the communication ID of the organizer, to the destination list management server 43 and causes the destination list management DB 53 to register the guest ID. As a result, the guest and the communication terminal 10 that invited the guest can communicate with each other. The destination list registration unit 67 causes the destination list management server 43 to delete the information about the guests registered in the destination list management DB 53.

The invitation information deletion unit 68 communicates with the guest management server 44, specifies the invitation ID, and deletes the invitation information.

<<Information registered in each database>>
Next, the information registered in each database will be described using Tables 1 to 7.

認証管理ＤＢ５１には、例えば、表１に示されているような認証管理テーブルが含まれる。認証管理ＤＢ５１は認証管理情報の記憶手段である。この認証管理テーブルでは、通信管理システム５０によって管理される通信端末１０の通信ＩＤと、通信ＩＤに対応するパスワードとが関連付けられて管理されている。通信ＩＤとパスワードはログインするための認証管理情報である。例えば、表１に示されている認証管理テーブルにおいて、通信ＩＤが「１１０００１」の通信端末１０のパスワードは、「ａａａａ」であることが示されている。

The authentication management DB 51 includes, for example, an authentication management table as shown in Table 1. The authentication management DB 51 is a storage unit of authentication management information. In this authentication management table, the communication ID of the communication terminal 10 managed by the communication management system 50 and the password corresponding to the communication ID are managed in association with each other. The communication ID and password are authentication management information for logging in. For example, the authentication management table shown in Table 1 indicates that the password of the communication terminal 10 having the communication ID “110001” is “aaaa”.

端末管理ＤＢ５２には、例えば、表２に示されているような端末管理テーブルが含まれる。端末管理ＤＢ５２は端末管理情報の記憶手段である。この端末管理テーブルでは、通信端末１０の通信ＩＤ毎に、各通信端末１０を端末名、各通信端末１０の稼動状態、ログイン要求情報が通信管理システム５０で受信された受信日時、及び通信端末１０のＩＰアドレスが関連付けられて管理される。端末管理テーブルに登録される情報は端末を管理するための端末管理情報である。例えば、表２に示されている端末管理テーブルにおいて、通信ＩＤが「１１０００１」の通信端末１０は、端末名が「東京事業所 ＡＡ端末」で、稼動状態が「オンライン（会議中）」で、受信日時が「２０１８年１０月１０日の１３時４０分」で、ＩＰアドレスが「１．２．１．３」であることが示されている。

The terminal management DB 52 includes, for example, a terminal management table as shown in Table 2. The terminal management DB 52 is a storage unit of terminal management information. In this terminal management table, for each communication ID of the communication terminal 10, the terminal name of each communication terminal 10, the operating state of each communication terminal 10, the reception date and time when the login request information was received by the communication management system 50, and the communication terminal 10 And associated IP addresses are managed. The information registered in the terminal management table is terminal management information for managing the terminal. For example, in the terminal management table shown in Table 2, the communication terminal 10 with the communication ID “110001” has the terminal name “Tokyo office AA terminal”, the operating state “online (in a meeting)”, It is indicated that the reception date and time is "13:40 on October 10, 2018" and the IP address is "1.2.1.3".

宛先リスト管理ＤＢ５３には、例えば、表３に示されているような宛先リスト管理テーブルが含まれる。宛先リスト管理ＤＢ５３は宛先リスト管理情報の記憶手段である。この宛先リスト管理テーブルでは、通信の開始を要求する要求元端末の通信ＩＤに対して、通信の宛先に指定できる宛先の通信ＩＤが全て関連付けられて管理される。要求元端末の通信ＩＤと宛先端末の通信ＩＤの組を宛先リスト管理情報という。また、各通信端末１０の宛先端末名が登録されている。

The destination list management DB 53 includes, for example, a destination list management table as shown in Table 3. The destination list management DB 53 is a storage unit for storing destination list management information. In this destination list management table, all the communication IDs of the destinations that can be designated as the communication destinations are managed in association with the communication IDs of the request source terminals that request the start of communication. A set of the communication ID of the request source terminal and the communication ID of the destination terminal is called destination list management information. Further, the destination terminal name of each communication terminal 10 is registered.

For example, in the destination list management table shown in Table 3, the destination terminal candidates that can request the start of communication from the request source terminal whose communication ID is "110001" are "110002", "110003", And the communication ID of “110004”. This destination terminal candidate is updated by being added or deleted by the destination list management server 43 in response to an addition or deletion request to the communication management system 50 from an arbitrary request source terminal.

With such a configuration, the request source terminal (for example, 110001) can start communication only with the destination terminal candidates (for example, 110002) that are registered in advance. This destination terminal (for example, 110002) cannot communicate with the request source terminal unless the request source terminal (for example, 110001) is registered in the destination list management table as the destination terminal. Such a mechanism is preferable in that the possibility of communication between unexpected communication terminals 10 can be reduced.

セッション管理ＤＢ５５には、例えば、表４に示されているようなセッション管理テーブルが含まれる。セッション管理ＤＢ５５はセッション管理情報の記憶手段である。このセッション管理テーブルには、セッションの識別情報であるセッションＩＤ毎に、中継に使用される中継装置３０の中継装置ＩＤ、要求元端末の通信ＩＤ、宛先端末の通信ＩＤ、及びセッション参加日時等の情報が管理される。例えば、表４に示されているセッション管理テーブルにおいて、セッションＩＤ「ｓｅ１」のセッションは、要求元端末の通信ＩＤ「１１０００１」と宛先端末の通信ＩＤ「１１０００２」及び「１１０００３」との間で行われていることが示されている。また、セッションＩＤ「ｓｅ１」のセッションは、中継装置ＩＤ「１１１ａ」の中継装置３０を介して、「２０ｘｘ／４／１０ １３：４５：３０」に開始されたことが示されている。

The session management DB 55 includes, for example, a session management table as shown in Table 4. The session management DB 55 is a storage unit of session management information. In this session management table, for each session ID that is the identification information of the session, the relay device ID of the relay device 30 used for relay, the communication ID of the request source terminal, the communication ID of the destination terminal, the session participation date and time, etc. Information is managed. For example, in the session management table shown in Table 4, the session with the session ID “se1” is stored between the communication ID “110001” of the request source terminal and the communication IDs “110002” and “110003” of the destination terminal. It is shown that Also, it is shown that the session with the session ID “se1” was started at “20xx/4/10 13:45:30” via the relay device 30 with the relay device ID “111a”.

ゲスト管理ＤＢ５４は招待権限管理情報、招待情報又はゲスト情報の記憶手段である。ゲスト管理ＤＢ５４には、例えば、表５（ａ）に示されているような招待権限管理テーブルが含まれる。この招待権限管理テーブルには、ゲストを招待する権限を有するユーザ（主催者）の通信ＩＤに対応付けて、招待数上限、招待期間上限、及び、招待ゲスト数上限等の情報が管理される。表５（ａ）の１レコード（１行）を招待権限管理情報という。招待数上限はこの通信ＩＤのユーザが作成できる招待情報の数の上限である。招待期間上限は招待情報で設定できる招待期間（招待開始日時〜招待終了日時）の上限である。これによりゲストが無制限に遠隔コミュニケーションシステムを利用してしまうことを防止できる。招待ゲスト数上限は一つの招待情報で招待できるゲスト数の上限である。招待ゲスト数の上限があることで、想定外の参加者が遠隔コミュニケーションに参加することを抑制しやすくなる。なお、表５（ａ）の内容はあくまで一例であり、これ以外の項目が含まれていても、一部の項目が含まれていなくてもよい。

The guest management DB 54 is a storage unit of invitation authority management information, invitation information, or guest information. The guest management DB 54 includes, for example, an invitation authority management table as shown in Table 5(a). The invitation authority management table manages information such as the upper limit of the number of invitations, the upper limit of the invitation period, and the upper limit of the number of invited guests in association with the communication ID of the user (organizer) having the authority to invite guests. One record (one line) in Table 5(a) is called invitation authority management information. The upper limit of the number of invitations is the upper limit of the number of invitation information that the user of this communication ID can create. The upper limit of the invitation period is the upper limit of the invitation period (invitation start date/time to invitation end date/time) that can be set in the invitation information. This can prevent the guest from using the remote communication system without limitation. The maximum number of invited guests is the maximum number of guests who can be invited with one piece of invitation information. The upper limit of the number of invited guests makes it easier to prevent unexpected participants from participating in remote communication. Note that the content of Table 5(a) is merely an example, and other items may be included or some items may not be included.

Further, the guest management DB 54 includes, for example, an invitation information management table as shown in Table 5(b). In this invitation information management table, information such as an invitation source communication ID, a host name, the number of invited guests, an invitation start date and time, and an invitation end date and time are managed in association with the invitation ID. One row or one record in Table 5(b) is called invitation information. The invitation ID is identification information that identifies the invitation information. Since guest invitations are often made on a conference basis, the invitation ID can be said to be information for identifying a conference invitation. The invitation source communication ID is the communication ID of the sponsor who is the invitation source. The communication ID used to log in when inviting a guest is the invitation source ID. Therefore, it can be said that it is the communication ID of the communication terminal 10 of the invitation source.

The initial value of the organizer name is the terminal name associated with the invitation source communication ID in the terminal management table, but the organizer can enter an arbitrary organizer name. The number of invited guests can be set by the organizer within the maximum number of invited guests of the organizer. The invitation start date and time is the date and time when the guest invitation is started, and the invitation end date and time is the date and time when the guest invitation is ended (for example, set to include from the start to the end of the conference). The contents of Table 5(b) are merely examples, and other items may be included or some items may not be included.

Further, the guest management DB 54 includes, for example, a guest information management table as shown in Table 5(c). One row or one record in Table 5(c) is called guest information. In this guest information management table, information such as an invitation ID, a guest name, a mail address, a token, a login available flag, a conference available flag, and an invalidation flag is managed in association with the guest ID. The guest ID is identification information of the guest that uniquely identifies or specifies the guest, and is automatically generated. The invitation ID associates guest information with invitation information. The guest name is the company name or name of the invited guest, and can be input by the guest (or the organizer). The email address is the email address of the invited guest and can be input by the guest (or the organizer). The token corresponds to the password used to authenticate the invited guest and is automatically generated. The log-in enable flag is a flag indicating whether or not the guest can log in, and the initial value is “No”. The meeting possible flag is a flag indicating whether or not the guest can start communication (start a meeting), and the initial value is “No”. As will be described later, the guest cannot start communication until the invitation start date and time. The invalidation flag is a flag indicating whether or not the guest information has been invalidated, and the initial value is “No”. “Invalid” means that the guest information does not make sense or is ignored (the guest information whose invalidation flag is YES is deleted as appropriate).

<<Functional configuration of client PC>>
Browser software runs on the client PC 20, and has functions generally possessed by the browser software. The client PC 20 has a third communication unit 21, a display control unit 22, and an operation reception unit 23. The function of the client PC 20 regarding remote communication is omitted. The illustrated function is mainly used by the guest to register guest information. Each of these functions is a function or means that is realized by any of the components shown in FIG. 4 being operated by an instruction from the CPU 201 according to a program expanded from the HD 204 to the RAM 203. is there.

The third communication unit 21 transmits and receives various information to and from the communication management system 50. The display control unit 22 displays various screens on the display 208 based on the screen information received from the communication management system 50. The operation reception unit 23 receives various operations on the browser.

<Operating procedure>
The operation of the remote communication system 100 will be described based on the above configuration. First, the process up to the registration of invitation information will be described with reference to FIGS. The invitation information can be registered by either the communication terminal 10 or the client PC 20. Application software runs on the communication terminal 10, and browser software runs on the client PC 20.

FIG. 6 is an example of a sequence diagram showing a process in which the communication terminal 10 or the client PC 20 displays a guest management screen.

S1: The organizer communicates with the communication terminal management system 40 through the application software of the communication terminal 10 or through the browser software of the client PC 20. In order to log in, the second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 transmits the communication ID and password to the communication terminal management system 40.

S2: The first communication unit 31 of the communication terminal management system 40 receives the login request and sends the login request (communication ID, password) to the authentication management server 41.

S3: The terminal authentication unit 56 of the authentication management server 41 refers to the authentication management table of the authentication management DB 51 and authenticates (verifies) the communication ID and password. In FIG. 6, it is assumed that the authentication is successful.

S4: The terminal authentication unit 56 of the authentication management server 41 returns the authentication result (authentication OK, authentication NG) to the communication terminal management system 40.

S5: Since the communication terminal management system 40 is authentication OK, it transmits login OK (accepts login) to the communication terminal 10 or the client PC 20.

S6: After logging in, the organizer who wants to create the invitation information operates the communication terminal 10 or the client PC 20 to display the guest management screen. The operation reception unit 12 of the communication terminal 10 or the operation reception unit 23 of the client PC 20 receives this operation, and the second communication unit 11 or the third communication unit 21 specifies the communication ID in the communication terminal management system 40 and the guest management screen. Send the display request of.

S7: The first communication unit 31 of the communication terminal management system 40 receives the display request for the guest management screen, specifies the communication ID, and transmits the invitation authority confirmation request to the guest management server 44.

S8: The guest management server 44 receives the invitation authority confirmation request, and the guest management unit 59 of the guest management server 44 determines whether or not the designated communication ID exists in the invitation authority management table of the guest management DB 54. The guest management unit 59 transmits the determination result (with or without invitation authority) to the communication terminal management system 40.

S9-1: In the case of having the invitation authority, the communication terminal management system 40 receives the invitation authority from the guest management server 44.

S10-2: The screen information generation unit 32 of the communication terminal management system 40 generates the screen information of the guest management screen (with invitation authority) 301 shown in FIG. 7, and the first communication unit 31 has the guest management screen (with invitation authority). The screen information 301 is transmitted to the communication terminal 10 or the client PC 20.

The second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 receives the screen information of the guest management screen (with invitation authority) 301, and the display control units 17 and 22 display the guest management screen (with invitation authority). ) 301 is displayed on the displays 120 and 208.

S9-2, S10-2: In the case of no invitation authority, the display control units 17 and 22 display the guest management screen (no invitation authority) 311 on the displays 120 and 208 through similar processing. In this case, the registration of the invitation information from the organizer is rejected.

FIG. 7 shows an example of a guest management screen (with invitation authority) 301 displayed on the displays 120 and 208 of the communication terminal 10 or the client PC 20. The guest management screen (with invitation authority) 301 has an invitation information creation button 302, a number of possible creations 303, and created invitation information 304. The invitation information creation button 302 is a button for the user to start creation of invitation information. The createable number 303 is the “maximum number of invitations” that the guest management server 44 has acquired from the invitation authority management table, and is transmitted from the guest management server 44 to the communication terminal management system 40. In the created invitation information 304, a list of already created invitation information is displayed. The created invitation information is acquired by searching for the communication ID of the organizer from the invitation source communication ID in the invitation information management table.

FIG. 8 shows an example of a guest management screen (without invitation authority) 311 displayed on the displays 120 and 208 of the communication terminal 10 or the client PC 20. The guest management screen (without invitation authority) 311 has a message 312 "Communication ID: 110004 Osaka office BB terminal does not have invitation authority." The communication ID is the communication ID of the logged-in organizer. “Osaka office BB terminal” is the terminal name of the logged-in user, and is transmitted from the terminal management server 42 to the communication terminal management system 40 when there is no invitation authority.

Next, a process when the create invitation information button 302 in FIG. 7 is pressed will be described. FIG. 9 is an example of a sequence diagram showing a process in which the guest management server 44 creates invitation information.

S11: When the organizer operating the communication terminal 10 or the client PC 20 presses the invitation information creation button 302, the operation accepting units 12 and 23 of the communication terminal 10 or the client PC 20 accept this operation. The second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 transmits a request to display the invitation information creation dialog 321 (see FIG. 10) to the communication terminal management system 40.

The first communication unit 31 of the communication terminal management system 40 receives the display request for the invitation information creation dialog 321, and the screen information generation unit 32 creates the screen information for the invitation information creation dialog 321. The screen information generation unit 32 specifies necessary information (the terminal name is acquired from the terminal management server 42, the maximum number of invited guests and the maximum invitation period are acquired from the guest management server 44) by specifying the communication ID of the organizer. To get from. FIG. 10 shows an example of the invitation information creation dialog 321. The first communication unit 31 transmits the screen information of the invitation information creation dialog 321 to the communication terminal 10 or the client PC 20.

S12: The second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 receives the screen information of the invitation information creation dialog 321, and the display control units 17 and 22 display the invitation information creation dialog 321 on the displays 120 and 208. To display. In the invitation information creation dialog 321, the organizer inputs the name of the organizer, the number of invited guests, and the invitation period. The operation receiving units 12 and 23 receive these inputs.

S13: When the organizer presses the create button 325 in the invitation information creation dialog 321, the operation accepting units 12 and 23 accept the operation.

S14: The second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 sends a request for creating invitation information to the communication terminal management system 40. The creation request includes the name of the host, the number of invited guests, the invitation period, and the communication ID of the host, which is a part of the invitation information.

S15: The first communication unit 31 of the communication terminal management system 40 receives the invitation information creation request and transmits the invitation information creation request to the guest management server 44.

S16: The guest management unit 59 of the guest management server 44 verifies the host name, the number of invited guests, and the invitation period. The specific verification contents are as follows.
-Whether the communication ID of the organizer exists in the communication ID item in the invitation authority management table.
-In the invitation information management table, is the communication ID of the organizer the same number as (or more than) the maximum number of invitations in the invitation authority management table in the item of the invitation communication ID?
Whether the number of invited guests transmitted from the communication terminal 10 or the client PC 20 does not exceed the maximum number of invited guests in the invitation authority management table.
-Whether the invitation period sent from the communication terminal 10 or the client PC 20 exceeds the invitation period upper limit of the invitation authority management table.

S17: If the verification result is true, the guest management unit 59 of the guest management server 44 registers the invitation information in the invitation information management table of the guest management DB 54. An invitation ID is newly generated. The communication ID of the organizer is sent to the item of the invitation source communication ID, the host name sent from the communication terminal 10 or the client PC 20 to the item of the host name, and the communication terminal 10 or the client PC 20 sent to the item of the number of invited guests. For the number of invited guests, the invitation start date and time and the invitation end date and time transmitted from the communication terminal 10 or the client PC 20 are registered in the items of invitation start date and time and invitation end date and time, respectively.

S18: The guest management server 44 sends the creation success together with the invitation information registered in the communication terminal management system 40.

S19: The first communication unit 31 of the communication terminal management system 40 receives the invitation information and the creation success, and the screen information generation unit 32 uses the invitation information to display the screen information of the guest management screen (when the invitation information is created successfully) 331. Is generated (see FIG. 11). Therefore, the screen information generation unit 32 generates the invitation URL including the invitation ID. The first communication unit 31 of the communication terminal management system 40 transmits the screen information of the guest management screen (when the invitation information is successfully created) 331 to the communication terminal 10 or the client PC 20. FIG. 11 shows an example of the guest management screen (when the invitation information is successfully created) 331.

The second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 receives the screen information of the guest management screen (when the invitation information is successfully created) 331, and the display control units 17 and 22 display the guest management screen (invitation information). When the creation is successful) 331 is displayed on the displays 120 and 208.

S20: If the verification result is false, the guest management server 44 transmits the creation failure together with the error information (specific reason why the verification result is false) to the communication terminal management system 40. In this case, the invitation information registration is rejected in response to the invitation information creation request exceeding the maximum number of invitations, the maximum invitation period, or the maximum number of invited guests.

S21: The first communication unit 31 of the communication terminal management system 40 receives the creation failure together with the error information, and the screen information creation unit 32 creates the screen information of the invitation information creation dialog (at the invitation information creation error) 341 (FIG. 12). reference). The first communication unit 31 of the communication terminal management system 40 transmits the screen information of the invitation information creation dialog (at the time of invitation information creation error) 341 to the communication terminal 10 or the client PC 20. FIG. 12 shows an example of the invitation information creation dialog (at the time of invitation information creation error) 341.

The second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 receives the screen information of the guest management screen (at the time of invitation information creation error) 341, and the display control units 17 and 22 cause the invitation information creation dialog (invitation). (At the time of information creation error) 341 is displayed on the displays 120 and 208.

FIG. 10 shows an example of the invitation information creation dialog 321 displayed on the displays 120 and 208 of the communication terminal 10 or the client PC 20. The invitation information creation dialog 321 has a sponsor name column 322, an invited guest number column 323, and an invitation period column 324. Although each column may be empty, it is preferable that the screen information generation unit 32 generate an appropriate initial value. The initial value of the organizer name column 322 is the terminal name associated with the communication ID of the organizer in the terminal management DB 52, the number of invited guests column 323 is the upper limit of the number of invited guests of the invitation authority management table, and the invitation start of the invitation period column 324. The date and time is set to 15 minutes, 30 minutes, 00 minutes, etc. after the current time, and the invitation end date and time in the invitation period field 324 is set to the invitation start date and time + 1 hour and the like. The organizer can set any of the input fields.

FIG. 11 is an example of the guest management screen (when the invitation information is successfully created) 331 displayed on the displays 120 and 208 of the communication terminal 10 or the client PC 20. Compared to the guest management screen (with invitation authority) 301 shown in FIG. 7, one piece of invitation information is displayed. A message 339 "Invited information created" is displayed. The guest management screen (when the invitation information is successfully created) 331 has an invitation URL column 332, a sponsor name column 333, an invitation start date/time column 334, an invitation end date/time column 335, and a registered guest column 336. The initial value is displayed except for the invitation URL field 332 or the value set by the organizer.

“Number of people/number of invited guests” is displayed in the registered guests column 336. The number of invited guests is the number of invited guests in the invitation information table, and the number of guests is the number of records having the same invitation ID in the guest information management table. A confirmation button 337 is provided in the registered guest column 336. The confirmation button 337 is a button for the organizer to confirm the currently registered guest information. Further, one delete button 338 is displayed in the invitation information. The delete button 338 is a button for the organizer to delete the invitation information.

This invitation information can be copied to the clipboard by the organizer. The organizer sends the invitation URL to the guest by e-mail or the like. The guest can access the invitation URL and register the guest information in association with the invitation ID.

FIG. 12 is an example of the invitation information creation dialog (at the time of invitation information creation error) 341 displayed on the displays 120 and 208 of the communication terminal 10 or the client PC 20. Compared with the invitation information creation dialog 321 shown in FIG. 10, an error message column 342 is displayed. In the error message column 342, the specific content for which the verification in step S15 of FIG. 9 is determined to be false is displayed.

In FIG. 12, "The maximum number of invited guests is 10." "The maximum invitation period is 24 hours." is displayed. The host can see this and enter the invitation information again.

<Registration of guest information>
Subsequently, a process up to registration of guest information will be described with reference to FIGS. 13 to 17. FIG. 13 is an example of a sequence diagram showing a process in which a guest who receives an invitation registers guest information in the guest management server 44.

The organizer shares the invitation URL displayed on the guest management screen (when the invitation information is successfully created) 331 in FIG. 11 with the person (guest) who wants to invite the guest by any means such as an electronic mail, a messenger, or a scheduler. This work corresponds to the invitation.

S31: The guest who shares the invitation URL operates the client PC 20 to access the invitation URL. The operation reception unit 23 of the client PC 20 receives this operation, and the third communication unit 21 accesses the invitation URL. This access corresponds to a display request for the guest registration screen 351.

S32: The first communication unit 31 of the communication terminal management system 40 takes out the invitation ID included in the invitation URL when receiving the access.

S33: The communication terminal management system 40 specifies the invitation ID and requests the guest management server 44 for the invitation information.

S34: The guest management server 44 receives the request for the invitation information and acquires the invitation information associated with the designated invitation ID from the invitation information management table.

S35: The guest management server 44 returns the acquired invitation information to the communication terminal management system 40.

S36: The communication terminal management system 40 receives the invitation information, the screen information generation unit 32 generates the screen information of the guest registration screen 351, and the first communication unit 31 transmits the screen information of the guest registration screen 351 to the client PC 20. (See FIG. 14).

S37: The third communication unit 21 of the client PC 20 receives the screen information of the guest registration screen 351, and the display control unit 22 displays the guest registration screen 351 on the display 208. An example of the guest registration screen 351 is shown in FIG. On the guest registration screen 351, the guest inputs the name and email address and presses the guest registration button 355. The operation reception unit 23 of the client PC 20 receives the operation.

S38: The third communication unit 21 of the client PC 20 specifies the guest registration information (name and mail address) and sends a guest information creation request to the communication terminal management system 40.

S39: The first communication unit 31 of the communication terminal management system 40 receives the guest information creation request and sends the guest information creation request to the guest management server 44.

S40: The guest management server 44 receives the guest information creation request, and the guest management unit 59 verifies the designated guest registration information. The specific verification contents are as follows.
-Whether the invitation ID acquired from the invitation URL exists in the invitation ID item of the invitation information management table.
-In the guest information management table, whether the number of guest information having the same invitation ID has reached the number of invited guests in the invitation information management table.
-In the guest information management table, does the same combination of invitation ID and email address already exist? This is to prevent the same user from accidentally or intentionally registering the same invitation ID and e-mail address to suppress the number of invited guests.
・Is the email address format correct?

S41: If the verification result of the guest information is true, the guest management unit 59 registers the guest information in the guest management DB 54. In this case, the guest ID and the token are generated. Other information is included in the invitation ID, the guest registration information, or the initial value is determined.

S42: The guest management server 44 specifies the created guest information and sends the creation success to the communication terminal management system 40.

S43: The communication terminal management system 40 receives the successful creation, the mail sending unit 33 creates a message using the guest information, and sends the guest registration notification mail 361 to the mail address included in the guest information. FIG. 15 shows an example of the text of the guest registration notification mail 361.

It should be noted that the guest registration notification mail 361 may be transmitted by detecting that “login enable flag==YES” in FIG. 26 described later. “==” means equal. This is because if "loginable flag == YES", it means that the guest's terminal authentication management information is registered, so that the guest can be guaranteed to be able to log in. Actually, when the guest information is registered in step S41, the guest account processing server 60 performs the processing of FIG. 26 in the background, and therefore the “login possible flag==YES” is set by the time the guest logs in. Alternatively, the mail transmitting unit 33 may detect the event that "loginable flag == YES" and transmit the guest registration notification mail 361.

S44: Further, the screen information generation unit 32 of the communication terminal management system 40 generates the screen information of the guest registration screen (when registration is successful) 371 and sends it back to the client PC 20. The content of the guest registration screen (when registration is successful) 371 may be fixed.

The third communication unit 21 of the client PC 20 receives the screen information of the guest registration screen (when registration is successful) 371, and the display control unit 22 displays the guest registration screen (when registration is successful) 371 on the display 208. FIG. 16 shows an example of the guest registration screen (when registration is successful) 371.

S45: If the verification result of the guest information is false, the guest management unit 59 sends the creation failure together with the error information (specific reason why the verification is false) to the communication terminal management system 40.

S46: The communication terminal management system 40 receives the creation failure, and the screen information generation unit 32 generates the screen information of the guest registration screen (during registration error) 381 and sends it back to the client PC 20 (see FIG. 17). The guest registration screen (at the time of registration error) 381 includes specific contents for which the verification is determined to be false.

The third communication unit 21 of the client PC 20 receives the screen information of the guest registration screen (when registration error occurs) 381, and the display control unit 22 displays the guest registration screen (when registration error occurs) 381 on the display 208. FIG. 17 shows an example of the guest registration screen (during registration error) 381.

FIG. 14 shows an example of the guest registration screen 351 displayed on the display 208 of the client PC 20. The guest registration screen 351 has a message 352 for inviting to a conference, a guest name input field 353, a mail address input field 354, and a guest registration button 355. The guest can input an arbitrary name in the guest name input field 353, and inputs his/her own mail address in the mail address input field 354. These are registered in the guest information management table. The guest registration button 355 is a button for starting registration of guest information.

FIG. 15 is a diagram showing an example of the text of the guest registration notification mail 361 transmitted to the guest by registering the guest information. The guest registration notification mail 361 is a mail notifying that the guest registration is completed. The guest registration notification mail 361 includes information such as the application download URL 362, the authentication management information 363, the invitation period 364, and the connection partner 365.

The application download URL 362 is a URL for the guest to download the application software of the remote communication system 100. At this URL, application software for various OSs is prepared. The authentication management information 363 is a guest ID and token for the guest to log in to the communication management system 50, and is described as “login ID” and “password” in FIG. 15. The invitation period 364 is an invitation start date and time and an invitation end date and time associated with the invitation ID of the guest information in the invitation information management table. The connection partner 365 indicates who invited, and is the name of the organizer associated with the invitation ID of the guest information in the invitation information management table.

The information of FIG. 15 may be displayed on the guest registration screen (when registration is successful) 371 of FIG. 16 instead of the email. Alternatively, both screen display and mail transmission may be performed.

FIG. 16 is a diagram showing an example of a guest registration screen (when registration is successful) 371 displayed on the display 208 of the client PC. A message 372 is displayed on the guest registration screen (when registration is successful) 371, "Guest registration is completed. Please check the conference participation procedure sent by email." The “conference participation procedure mail” mail is the guest registration notification mail 361 shown in FIG. 15, so the user can download application software in advance or log in. Communication (meeting) cannot start until the beginning of the invitation period.

FIG. 17 is a diagram showing an example of the guest registration screen (during registration error) 381 displayed on the display 208 of the client PC. Compared with the guest registration screen 351 of FIG. 14, an error message column 382 is displayed on the guest registration screen (during registration error) 381. In the error message column 382, the specific content of which the verification is false as a result of the verification in step S40 of FIG. 13 is displayed.

In FIG. 17, it is displayed that "the specified email address has already been registered as a guest." Guests can see this and confirm that they have already registered.

<Guest information confirmation, deletion, invitation information deletion>
Subsequently, confirmation of guest information, deletion, deletion of invitation information, and the like will be described with reference to FIGS. The organizer can check at any time whether the guest has registered guest information or is not inviting the wrong guest. Also, when a guest is invited to a canceled conference, the invitation information itself can be deleted.

FIG. 18 is an example of a sequence diagram showing a process in which the organizer browses and deletes registered guest information.

S51: The organizer presses the confirmation button 337 on the guest management screen 331 (when the invitation information is successfully created) 331 in FIG. The operation accepting units 12 and 23 of the communication terminal 10 or the client PC 20 accept the depression of the confirmation button 337, and the second communication unit 11 or the third communication unit 21 specifies the invitation ID in the communication terminal management system 40 and the registered guest. A request for displaying the information confirmation dialog 391 is transmitted (see FIG. 19).

S52: The first communication unit 31 of the communication terminal management system 40 receives the display request of the registered guest information confirmation dialog 391, specifies the invitation ID, and requests the guest management server 44 for the guest information list.

S53: The guest management unit 59 of the guest management server 44 acquires all guest information associated with the designated invitation ID from the guest information management table.

S54: The guest management server 44 transmits the acquired guest information list to the communication terminal management system 40.

S55: The communication terminal management system 40 receives the guest information list, and the screen information generation unit 32 uses the guest information list to generate the screen information of the registered guest information confirmation dialog 391. The first communication unit 31 transmits the screen information of the registered guest information confirmation dialog 391 to the communication terminal 10.

The second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 receives the screen information of the registered guest information confirmation dialog 391, and the display control units 17 and 22 display the registered guest information confirmation dialog 391 in the communication terminal. 10 on the display 120 or the display 208 on the client PC 20. FIG. 19 shows an example of the registered guest information confirmation dialog 391.

S56: In the registered guest information confirmation dialog 391, the organizer presses the delete button for the guest information to be deleted. The operation accepting units 12 and 23 of the communication terminal 10 or the client PC 20 accept the depression, and the second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 designates the guest ID to the communication terminal management system 40. Send a request to delete the relevant guest information.

S57: The first communication unit 31 of the communication terminal management system 40 receives the guest information deletion request and sends the guest information deletion request to the guest management server 44.

S58: The guest management server 44 receives the guest information deletion request, and the guest management unit 59 invalidates the guest information specified by the guest ID. Specific invalidation processing is as follows, for example.
-Acquire the guest information of the specified guest ID in the guest information management table.
-Set the invalidation flag of the acquired guest information to YES. The reason for invalidating the record instead of deleting it is that the guest account processing server 60 deletes the guest information whose invalidation flag is YES.

S59: The guest management server 44 designates the deleted guest information and sends the deletion success to the communication terminal management system 40.

S60: The communication terminal management system 40 receives the deletion success, creates the screen information of the registered guest information confirmation dialog (when the guest information is deleted successfully) 401 using the guest information deleted by the screen information generation unit 32, and The communication unit 31 transmits the screen information of the registered guest confirmation dialog (when guest information is deleted successfully) 401 to the communication terminal 10 or the client PC 20 (see FIG. 20).

The second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 receives the screen information of the registered guest confirmation dialog (when guest information is successfully deleted) 401. The display control units 17 and 22 of the communication terminal 10 or the client PC 20 display the registered guest confirmation dialog (when guest information is deleted successfully) 401 on the displays 120 and 208. FIG. 20 shows an example of the registered guest confirmation dialog (when guest information is successfully deleted) 401.

S61: When the communication terminal management system 40 transmits the deletion success to the communication terminal 10 or the client PC 20, the guest deletion mail indicating that the guest information has been deleted is sent to the guest's mail address. FIG. 21 shows an example of the text of the guest deletion notification mail 411.

FIG. 19 is a diagram showing an example of the registered guest information confirmation dialog 391 displayed on the displays 120 and 208 of the communication terminal or the client PC. A registered guest information confirmation dialog 391 pops up on the guest management screen. The registered guest information confirmation dialog 391 displays a list 392 of all guest information registered as guests in the sequence diagram described in FIG. A delete button 393 is displayed for each guest, and the organizer can individually delete the guest from the registered guest information. This can prevent the guest from participating in the conference when the guest is mistakenly invited or the guest is mistakenly registered.

FIG. 20 shows an example of the registered guest confirmation dialog (when guest information is successfully deleted) 401 displayed on the displays 120 and 208 of the communication terminal or the client PC. Since the sponsor has pressed the delete button 393 in FIG. 19, one guest is deleted in the sequence of FIG. 18, and there is one guest in FIG. In addition, a message 402 “Deleted ◯◯ corporation △△yyy@aa-tech.co.jp.” is displayed, and the deleted guest can be confirmed.

FIG. 21 is a diagram showing an example of the text of the guest deletion notification mail 411. In FIG. 21, a message 414 indicating that the guest information has been deleted and a mail address 413 of the inquiry destination are displayed. The “Sample Co., Ltd. ◯◯” 412 included in the message 414 is the name of the organizer of the invitation information management table associated with the same invitation ID as the invitation ID of the guest information management table. The deleted guest can know that the guest has been deleted, and can contact the contact point if necessary.

Next, the process of deleting the invitation information itself will be described with reference to FIG. FIG. 22 is an example of a sequence diagram showing a procedure in which the organizer deletes the invitation information.

S71: The organizer presses the delete button 338 on the guest management screen 331 (when the invitation information is successfully created) 331 in FIG. The operation receiving units 12 and 23 of the communication terminal 10 or the client PC 20 receive pressing of the delete button 338. The second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 specifies the invitation ID to the communication terminal management system 40 and transmits a display request for the invitation information deletion dialog 421.

S72: The first communication unit 31 of the communication terminal management system 40 receives the display request of the invitation information deletion dialog 421, specifies the invitation ID to the guest management server 44, and transmits the guest information list request.

S73: The guest management server 44 receives the guest information list request, and the guest management unit 59 acquires all the guest information associated with the designated invitation ID from the guest information management table.

S74: The guest management server 44 transmits the guest information list to the communication terminal management system 40.

S75: The communication terminal management system 40 receives the guest information list, the screen information generation unit 32 generates the invitation information deletion dialog 421 from the guest information list, and the first communication unit 31 communicates the screen information of the invitation information deletion dialog 421. It is transmitted to the terminal 10 or the client PC 20.

The second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 receives the screen information of the invitation information deletion dialog 421, and the display control units 17 and 22 display the invitation information deletion dialog 421 on the displays 120 and 208. To do. FIG. 23 shows an example of the invitation information deletion dialog 421.

S76: When the organizer presses the OK button 423 in the invitation information deletion dialog 421, the operation receiving units 12 and 23 of the communication terminal 10 or the client PC 20 receive the press. The second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 specifies the invitation ID and transmits a request to delete the invitation information to the communication terminal management system 40.

S77: The first communication unit 31 of the communication terminal management system 40 receives the invitation information deletion request. The communication terminal management system 40 specifies the invitation ID and sends a request for deleting the invitation information to the guest management server 44.

S78: The guest management server 44 receives the invitation information deletion request, and the guest management unit 59 invalidates the guest information associated with the designated invitation ID from the guest information management table (sets the invalidation flag to YES).

S79: The guest management server 44 deletes the invitation information specified by the invitation ID from the typeface information management table.

S80: The guest management server 44 sends the deletion success to the communication terminal management system 40.

S81: The communication terminal management system 40 receives the deletion success, and the screen information generation unit 32 of the communication terminal management system 40 generates the screen information of the guest management screen (when the invitation information is deleted successfully) 431 (see FIG. 24). The first communication unit 31 transmits the screen information of the guest management screen (when the invitation information is deleted successfully) 431 to the communication terminal 10 or the client PC 20.

The second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 receives the screen information of the guest management screen (when the invitation information is successfully deleted) 431, and the display control units 17 and 22 display the guest management screen (invitation information). When the deletion is successful) 431 is displayed on the displays 120 and 208. FIG. 24 shows an example of the guest management screen (when the invitation information is deleted successfully) 431.

S82: When the communication terminal management system 40 sends the deletion success to the communication terminal 10 or the client PC 20, the mail sending unit 33 sends a guest delete mail indicating that the guest information has been deleted to the guest mail address. The text of the guest deletion notification mail 411 may be the same as that shown in FIG.

Note that the order of the processes of "invalidating guest information associated with invitation ID" and "deletion of invitation information" may be reversed.

FIG. 23 shows an example of the invitation information deletion dialog 421 displayed on the display of the communication terminal or the client PC. The invitation information deletion dialog 421 in FIG. 23 is similar to the registered guest information confirmation dialog 391 in FIG. 19, but the message “If you delete the invitation information, the following registered guests will be deleted. Are you sure?” 422 is displayed. This allows the organizer to refer to the guest information and determine whether to delete. The invitation information deletion dialog 421 has an OK button 423. The OK button 423 is a button for deleting invitation information (invalidating all guest information). The guest can be individually deleted in the invitation information deletion dialog 421 shown in FIG.

FIG. 24 is an example of the guest management screen (when the invitation information is successfully deleted) 431 displayed on the displays 120 and 208 of the communication terminal or the client PC. The guest management screen (when the invitation information is deleted successfully) 431 in FIG. 24 is similar to the guest management screen (with invitation authority) 301 in FIG. 7, but the message 432 “Deleted invitation information” is displayed.

<Process by guest account processing server>
The processing of the guest account processing server 60 according to the monitoring result of the guest management DB 54 will be described below with reference to FIGS. 25 to 29. First, FIG. 25 is a flowchart showing the overall processing flow of the guest account processing server 60.

The guest account processing server 60 performs each processing of S101: guest account creation processing S102: guest destination list creation processing S103: expired invitation information deletion processing S104: invalidation guest account deletion processing.

As illustrated, the guest account processing server 60 repeats four processes. These processes are executed independently of the registration and deletion of the invitation information by the organizer, the deletion of the guest information, and the registration of the guest information by the guest. Thereby, the guest information can be flexibly updated and deleted.

Note that the order of the four processes in FIG. 25 may be changed in any order. The four processes may be executed in parallel instead of permutation. A sleep (standby) of a fixed number of seconds or a variable number of seconds may be inserted in some or all of the four processes. Hereinafter, the processes of steps S101 to S104 will be sequentially described.

<<Guest account creation process>>
FIG. 26 is an example of a flowchart showing the guest account creation processing of step S101 of FIG.

The guest information acquisition unit 61 of the guest account processing server 60 acquires guest information from the guest management server 44 periodically or when an event occurs. Then, the determination unit 63 extracts guest information that satisfies the following conditions (S201).
"Invalidation flag == NO, and "Login enabled flag == NO", and "Invitation end date and time> Current date and time"
This condition is a condition for extracting guest information in a state immediately after the guest information is registered.

When the guest information of this condition is extracted (Yes in S202), the authentication management information creation unit 64 newly registers the authentication management information for the guest to log in to the authentication management table (S203). “=” means substitution.
・Communication ID = Guest ID (guest_000001)
・Password = token (L5c2h7g6)

表６はゲストの認証管理情報が登録された認証管理テーブルの一例である。通信ＩＤの項目に「guest_000001」が、パスワードの項目に「L5c2h7g6」が登録されている。

Table 6 is an example of the authentication management table in which the guest authentication management information is registered. “Guest_000001” is registered in the item of communication ID, and “L5c2h7g6” is registered in the item of password.

Returning to FIG. 26, the terminal management registration unit 65 newly registers the terminal management information of the guest in the terminal management table (S204).
・Communication ID = Guest ID (guest_000001)
・Terminal name = Guest name registered by the guest (○○ Inc. △△)

表７はゲストの端末管理情報が登録された端末管理テーブルの一例である。通信ＩＤの項目に「guest_000001」が、端末名の項目に「○○株式会社 △△」が登録されている。この時点ではまだゲストが通信管理システム５０にログインしていないため、稼動状態、受信日時、ＩＰアドレスは空欄である。

Table 7 is an example of a terminal management table in which guest terminal management information is registered. "Guest_000001" is registered in the item of communication ID, and "XX Corporation ΔΔ" is registered in the item of terminal name. Since the guest has not yet logged in to the communication management system 50 at this point, the operating status, the reception date and time, and the IP address are blank.

Returning to FIG. 26, since the authentication management information has been registered, the guest information updating unit updates the login enable flag of the guest information extracted in step S201 (S205).
・Login enabled flag = YES
In this way, the guest can log in by registering the information about the guest in the authentication management table and the terminal management table. However, since information regarding guests is not registered in the destination list management table, communication (conference) cannot be performed.

<<Guest Destination List Creation Process>>
FIG. 27 is an example of a flowchart showing the guest destination list creation processing of step S102 of FIG.

The guest information acquisition unit 61 of the guest account processing server 60 acquires guest information from the guest management server 44 periodically or when an event occurs. Then, the determination unit 63 extracts guest information that satisfies the following conditions (S301).
"Invalidation flag == NO", "Login enable flag == YES", "Meeting enable flag == NO", "Invitation start date and time ≤ Current date and time", and "Invitation end date and time>Present" Date and time"
This condition is a condition that the guest can log in, but since the invitation start date and time has arrived, the guest information that can start the conference is extracted.

When the guest information of this condition is extracted (Yes in S302), the destination list registration unit 67 newly registers the destination list management information for the guest and the organizer to have a meeting in the destination list management table (S303). First, associate the guest with the organizer.
Communication ID=invitation source communication ID (acquires the invitation source communication ID associated with the invitation ID of the guest information acquired in step S301 from the invitation information management table)
Destination communication ID = guest ID (included in the guest information acquired in step S301)
-Destination terminal name = guest name (included in the guest information acquired in step S301)
Next, the destination list registration unit 67 newly creates a record in which the host is associated with the guest in the destination list management table (S304).
Communication ID = guest ID (included in the guest information acquired in step S301)
Destination communication ID = invitation source communication ID (acquires the invitation source communication ID associated with the invitation ID of the guest information acquired in step S301 from the invitation information management table)
-Destination terminal name = organizer name (acquire the organizer name associated with the invitation ID of the guest information acquired in step S301 from the invitation information management table)

表８は主催者とゲストが互いに対応付けられた宛先リスト管理情報が登録された宛先リスト管理テーブルの一例である。主催者である通信ＩＤ「１１０００１」に対応付けてゲストＩＤである「guest_000001」が登録されている。ゲストＩＤである「guest_000001」に対応付けて主催者である通信ＩＤ「１１０００１」が登録されている。

Table 8 is an example of the destination list management table in which the destination list management information in which the organizer and the guest are associated with each other is registered. The guest ID “guest_000001” is registered in association with the communication ID “110001” that is the organizer. The communication ID “110001” that is the organizer is registered in association with the guest ID “guest_000001”.

The destination terminal name associated with the communication ID “110001” and the destination terminal name associated with guest_000001 are different. The host can specify a host name that is different from the destination terminal name in the destination list management table when registering the invitation information, so that different destination terminal names can be displayed to guests depending on the situation such as a conference or event to be invited. .. Since the guest can also register a different guest name each time the guest is invited, it is possible to display a different destination terminal name to the organizer according to the situation of the invited conference or event.

Returning to FIG. 27, the guest information updating unit 66 updates the conference available flag of the guest information extracted in step S301 (S305).
・Meeting possible flag = YES
In this way, the guest is associated with the organizer of the destination list management DB 53, and the organizer is associated with the guest, so that the organizer or the guest can start communication (conference).

The processes of steps S303, S304, and S305 are in no particular order.

<<Processing to delete expired invitation information>>
FIG. 28 is an example of a flowchart showing the expired invitation information deletion processing of step S103 of FIG.

The invitation information acquisition unit 62 of the guest account processing server 60 acquires invitation information from the guest management server 44 periodically or when an event occurs. Then, the determination unit 63 extracts invitation information that satisfies the following conditions (S501).
"End date of invitation ≤ current date and time"
This condition is a condition for extracting invitation information whose invitation information has expired because the invitation end date and time has arrived.

When the invitation information of this condition is extracted (Yes in S502), the guest information updating unit 66 extracts all guest information having the invitation ID of this invitation information (S503). The guest information specified by the invitation ID may be acquired from the guest information management table.

When the guest information is extracted (Yes in S504), the guest information updating unit 66 invalidates the guest information (S505).
・Invalidation flag = YES
Then, the invitation information deletion unit 68 deletes the invitation information acquired in step S501 (S506).

By this processing, the guest information related to the invitation information can be invalidated and the invitation information can be deleted. Note that the order of the “guest information extraction & invalidation” in steps S503 and S505 and the “invitation information deletion” processing in step S506 may be interchanged in any order.

<<Invalidation guest account deletion process>>
FIG. 29 is an example of a flowchart showing the invalidation guest account deletion processing of step S104 of FIG.

The guest information acquisition unit 61 of the guest account processing server 60 acquires guest information from the guest management server 44 periodically or when an event occurs. Then, the determination unit 63 extracts invitation information that satisfies the following conditions (S601).
"Invalidation flag == YES"
This condition is a condition for extracting invalid guest information (not qualified as a guest).

When the invitation information of this condition is extracted (Yes in S602), the authentication management information creation unit 64 causes the authentication management server 41 to delete the following authentication management information from the authentication management DB 51 (S603).
・Communication ID == Guest ID of guest information to be deleted
Next, the terminal management registration unit 65 causes the terminal management server 42 to delete the following terminal management information from the terminal management DB 52 (S604).
・Communication ID == Guest ID of guest information to be deleted
Next, the destination list registration unit 67 causes the destination list management server 43 to delete the following destination list management information from the destination list management DB 53 (S605).
・Communication ID == Guest ID of guest information to be deleted
Next, the destination list registration unit 67 causes the destination list management server 43 to delete the following destination list management information from the destination list management DB 53 (S606).
-Destination communication ID == Guest ID of guest information to be deleted
Then, the guest information deletion unit deletes the guest information acquired in step S601 (S607). As described above, the guest information whose invalidation flag is YES can be deleted.

<Operation procedure until communication starts>
Next, a processing flow of the remote communication system 100 will be described.

(Processing at the preparation stage)
FIG. 30 is a sequence diagram showing an example of processing at the communication preparation stage of the remote communication system 100. Here, as an example, the process in the preparation stage before the session between the communication terminals 10A and 10B is started will be described. In the following description, it is assumed that the guest communication terminal 10 has a code “10A” and the host communication terminal 10 has a code “10B”.

First, in the case of a dedicated terminal, when the operator of the communication terminal 10A, which is the request source terminal, performs an operation to turn on the power of the communication terminal 10A, the operation receiving unit 12 receives the operation to turn on the power, The power of the communication terminal 10A is turned on (S1021). In the case of a general-purpose terminal, the operation of starting the application software corresponds to turning on the power.

Then, the communication control unit 13 transmits the login request information for requesting the login from the second communication unit 11 to the communication management system 50 via the communication network 2 when the power is turned on or the application software is activated (S1022). ..

In addition, the login request information includes a communication ID (communication ID of the request source terminal) and a password for identifying the communication terminal 10A that is the request source. These communication ID and password are, for example, information read from the storage unit 19 via the storage/reading unit 18. Further, when the login request information is transmitted from the communication terminal 10A to the communication management system 50, the communication management system 50 on the receiving side can grasp the IP address of the communication terminal 10A on the transmitting side.

Next, the terminal authentication unit 56 of the communication management system 50 searches the authentication management table using the communication ID and password included in the login request information received via the communication terminal management system 40 as search keys. The terminal authentication unit 56 authenticates whether or not the combination of the communication ID and the password included in the login request information received from the communication terminal 10A is included in the authentication management table (S1023).

When the terminal authentication unit 56 determines that the authentication is successful, the terminal management unit 57 sets the operating state of the communication ID “guest_000001” of the communication terminal 10A recorded in the terminal management table to “online (transmittable)”. Change to ". At this time, the terminal management unit 57 updates the reception date and time and, if necessary, the IP address of the communication terminal 10 (S1024). As a result, in the terminal management table, the communication ID “guest_000001” of the communication terminal 10A, the operating state “online (transmittable)”, the reception date and time “20xx.4.10.13:40”, and the IP address of the communication terminal 10A are displayed. “1.2.1.3” is associated and managed.

Then, the first communication unit 31 of the communication terminal management system 40 is the request source terminal that has made a login request for the authentication result information indicating the authentication result obtained by the terminal authentication unit 56 via the communication network 2. It is transmitted to the communication terminal 10A (S1025). Here, a case will be described below in which the terminal authentication unit 56 determines that the communication terminal 10 has a valid usage right.

Next, the destination list management unit 58 of the destination list management server 43 searches the destination list management table using the communication ID “guest_000001” of the request source terminal (communication terminal 10A) that made the login request as a search key. Thereby, the destination list management unit 58 extracts the communication ID of the candidate of the destination terminal that can communicate with the request source terminal (communication terminal 10A) (S1026). In this embodiment, the organizer “110001” is extracted as the communication ID of the destination terminal corresponding to the communication ID “guest_000001” of the request source terminal (communication terminal 10A).

Next, the terminal management unit 57 searches the terminal management table using the extracted communication ID “110001” of the destination terminal candidate as a search key. As a result, the operating status can be read for each of the extracted communication IDs, and the operating status of the communication terminal 10 of the sponsor “110001” is acquired (S1027).

Next, the first communication unit 31 transmits the destination state information including the operating state of each of the destination terminal candidate communication IDs “110001” to the request source terminal (communication terminal 10A) (S1028). As a result, the request source terminal (communication terminal 10A) can grasp the current operating state of the communication ID “110001” that is a candidate for the destination terminal of the request source terminal (communication terminal 10A).

Further, the destination list management unit 58 uses the communication ID “guest_000001” of the request source terminal (communication terminal 10A) that has made the login request as a search key and the communication ID “guest_000001” of the request source terminal (communication terminal 10A) as the destination terminal. The communication ID of another request source terminal registered as a candidate is extracted (S1029). As shown in Table 8, the communication ID of the other request source terminal that is extracted is “110001”.

Next, the terminal management unit 57 searches the terminal management table using the communication ID “guest_000001” of the request source terminal (communication terminal 10A) that has made the login request as a search key. Accordingly, the terminal management unit 57 acquires the operating state of the request source terminal (communication terminal 10A) that has made the login request (S1030).

Then, the terminal management unit 57 extracts the operating state of the communication ID “110001” extracted in step S29 from the terminal management table. Then, it is determined whether or not the operating state is "online (transmittable)".

When the operating state is “online (transmittable)”, the first communication unit 31 notifies the communication terminal 10B corresponding to the extracted communication ID “110001” to the communication ID of the request source terminal (communication terminal 10A). The destination status information including "guest_000001" and the operating status "online (transmittable)" is transmitted (S1031). On the other hand, the communication terminal 10B also performs the same process as that shown in FIG. 30 according to, for example, an operation of turning on the power.

The display control units of the communication terminals 10A and 10B that have received the destination state information display the destination selection screen (S1032, S1033). An example of the destination selection screen is shown in FIG.

<Address selection screen>
FIG. 31 is a diagram showing an example of a destination selection screen displayed on the communication terminals 10A and 10B. 31A is a destination selection screen 1201A displayed by the guest communication terminal 10A (second communication terminal), and FIG. 31B is a destination selection screen by the organizer communication terminal 10B (first communication terminal). This is a screen 1201B.

A message 1202 for prompting the operator to select the destination communication terminal 10 and a button 1203 for selecting the destination communication terminal 10 are displayed on the destination selection screen 1201A. The guest who is the operator of the communication terminal 10A selects the destination terminal to start communication by selecting the displayed button 1203, for example. As shown in the figure, since the destination terminal name of the destination list management table is displayed on the button 1203, the organizer can display a different destination terminal name for each invitation on the guest communication terminal 10A. For example, it is possible to show the conference name invited to the guest as the own terminal name.

<Communication processing>
FIG. 32 is a sequence diagram showing an example of communication processing of the remote communication system 100. Here, an example of communication start processing for starting communication between the communication terminal 10A and the communication terminal 10B that communicates will be described. Although the request for starting communication can be made from the guest communication terminal 10 or the organizer communication terminal 10, the communication start request is made from the guest communication terminal 10.

In step S1041, the operation receiving unit 12 of the communication terminal 10A receives a selection operation of the destination terminal (communication terminal 10B) by the operator of the communication terminal 10A.

The second communication unit 11 of the communication terminal 10A transmits start request information regarding a session start request to the communication management system 50 (S1042). The start request information includes, for example, the communication ID “guest_000001” of the request source terminal that is the communication ID of the communication terminal 10A that is the request source terminal, the communication ID “110001” of the communication terminal 10B that is the destination terminal, and the like. The start request information also includes information such as the IP address (request source IP address) of the communication terminal 10A.

In step S1043, the terminal management unit 57 of the communication management system 50 that has received the start request information from the communication terminal 10A, based on the communication ID “guest_000001” of the request source terminal (communication terminal 10A) included in the start request information, The management DB 52 is updated. For example, the terminal management unit 57 changes the operating status information corresponding to the communication ID “guest_000001” of the communication terminal 10A to “online (in a meeting)” and also updates the reception date and time information.

In step S1044, the communication management unit 39 associates the communication ID “guest_000001” of the request source terminal (communication terminal 10A) with the communication ID “110001” of the communication terminal 10B that is the destination terminal, The destination list management server 43 is inquired as to whether the communication ID “guest_000001” of the communication terminal 10A that is the request source terminal is associated with the communication ID “110001” of the (communication terminal 10B). Thus, unless the communication IDs of the request source terminal and the destination terminal are registered in the destination list management table in the destination list management table, the communication management unit 39 does not start the session. In the present embodiment, as shown in Table 8, the communication ID of the guest and the communication ID of the organizer are mutually registered in the destination list management table, so the communication management unit 39 starts the session. The communication management unit 39 transmits start request information requesting the start of a session to the communication terminal 10B which is the destination terminal. The start request information includes, for example, the communication ID of the request source terminal of the communication terminal 10A that is the request source terminal.

In step S1045, the communication terminal 10B that receives the start request information from the communication management system 50 transmits the start response information to the communication management system 50. This start response information includes, for example, the communication ID of the destination terminal of the communication terminal 10B.

In step S1046, the terminal management unit 57 of the communication management system 50 that has received the start response information from the communication terminal 10B updates the terminal management DB 52 based on the communication ID “110001” of the communication terminal 10B included in the start response information. .. For example, the terminal management unit 57 changes the operating state information corresponding to the communication ID “110001” of the communication terminal 10B to “online (in a meeting)” and updates the reception date and time information.

In step S1047, the communication management unit 39 of the communication management system 50 assigns a session ID, which is identification information for identifying the session. The communication management unit 39 also manages the session by associating the created session ID with the communication ID of the request source terminal (communication ID of the communication terminal 10A) and the communication ID of the destination terminal (communication ID of the communication terminal 10B). Store in DB55.

In step S1048, the communication management unit 39 of the communication management system 50 transmits the session information to the relay device 30. This session information includes, for example, information such as the session ID created in step S1047. The relay device 30 can acquire the session information from the session management DB 55 based on the session ID.

In step S1049, the communication management unit 39 of the communication management system 50 transmits start instruction information for instructing the communication terminal 10A to start the session. Similarly, in step S1050, the communication management unit 39 transmits start instruction information for instructing the communication terminal 10B to start a session. The start instruction information includes the session ID, and the communication terminals 10A and 10B can acquire the session information from the session management DB 55 based on the session ID.

In step S1051, the communication terminal 10A establishes a session with the relay device 30 based on the received start instruction information. Similarly, in step S1052, the communication terminal 10B establishes a session with the relay device 30 based on the received start instruction information. Thereby, the communication terminals 10A and 10B can participate in the same session. That is, the communication service is started.

The communication terminal 10A and the communication terminal 10B can participate in a session having the same session ID, and can send and receive content data such as image data and audio data to hold a video conference, for example (S1053).

<Summary>
As described above, the remote communication system 100 according to the present embodiment performs the guest registration in the authentication management information, the terminal management information, and the destination list management information on the server side (cloud side). In addition, the function of the application software operating on the communication terminal 10 used by the guest does not need the function only for the guest to communicate, and the application software does not need to be improved.

In this embodiment, a remote communication system 100 that allows the organizer to register guests will be described.

In the present embodiment, the hardware configuration diagrams of FIGS. 3 and 4 and the functional block diagram shown in FIG. 5 described in the above embodiments will be described as being usable.

<Registration of invitation information and guest information>
FIG. 33 is an example of a sequence diagram of a process in which the organizer registers invitation information and guest information from the guest management screen. In the description of FIG. 33, differences from FIGS. 9 and 13 will be mainly described. The processes of steps S11 and S12 may be the same as in FIG. However, the invitation information creation dialog generated by the screen information generation unit 32 is different from that in FIG. 10. FIG. 34 shows an example of the invitation information creation dialog 441 of this embodiment.

S13-2: The organizer can enter guest information (guest name and email address).

S14-2: When the organizer presses the create button 325 in the invitation information creation dialog 441, the operation accepting unit 12 of the communication terminal 10 or the client PC 20 accepts the operation, and the second communication unit 11 of the communication terminal 10 or the client PC 20. The third communication unit 21 sends a request for creating invitation information to the communication terminal management system 40. The creation request includes the name of the organizer, the number of invited guests, the invitation period, the communication ID of the organizer, and guest information.

Subsequent steps S15 to S18 may be similar to FIG. 9, and steps S39 to S43 may be similar to FIG. However, steps S39 to S43 are repeatedly executed by the number of guests.

S19-2: The second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 receives the screen information of the guest management screen (when the invitation information is successfully created) 451 and the display control units 17 and 22 manage the guest. A screen (when invitation information is successfully created) 451 is displayed on the displays 120 and 208. FIG. 35 shows an example of the guest management screen (at the time of successful creation of invitation information) 451 of this embodiment.

FIG. 34 is an example of the invitation information creation dialog 441 displayed on the displays 120 and 208 of the communication terminal 10 or the client PC 20. Different from FIG. 10, the invitation information creation dialog 441 of FIG. 34 has a guest list input field (guest name, mail address) 442 instead of the invited guest number field. Further, when the organizer presses the “+add guest frame” button 443, guest frames can be added and displayed by the maximum number of invited guests in the invitation authority management table.

FIG. 35 is an example of a guest management screen (when invitation information is successfully created) 451 displayed on the displays 120 and 208 of the communication terminal 10 or the client PC 20. Although it is almost the same as the guest management screen 331 (when the invitation information is successfully created) 331 in FIG. 11, there is no invitation URL column in FIG. This is because the guest information has already been registered, and the organizer does not need to share the invitation URL with the guest. Further, since the guest has already been registered, the button in the registered guest column 336 is the add invitation button 452. When the additional invitation button 452 is pressed, the guest can be invited.

Note that the invitation URL column may be included in FIG. 35 as well. In this case, the organizer can directly send the guest registration notification mail 361 to the guest who wants to invite, or can perform the guest registration via the invitation URL as in the processing sequence shown in FIG. 13.

<Additional invitation processing>
Subsequently, a method of inviting a guest to be added will be described with reference to FIG. FIG. 36 is an example of a sequence diagram showing a process in which the host invites additional guests on the guest management screen (when the invitation information is successfully created) 451.

S91: When the organizer presses the add invitation button 452 on the guest management screen (when the invitation information is successfully created) 451 in FIG. 35, the operation receiving unit 12 of the communication terminal 10 or the operation receiving unit 23 of the client PC 20 receives the press. The second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 specifies the invitation ID and transmits a request to display the additional invitation dialog to the communication terminal management system 40.

S92: The third communication unit 21 of the communication terminal management system 40 receives the request to display the additional invitation dialog, specifies the invitation ID, and transmits the guest information list request to the guest management server 44.

S93: The guest management server 44 receives the guest information list request, and acquires the guest information associated with the designated invitation ID from the guest information management table.

S94: The guest management server 44 transmits the acquired list of guest information to the communication terminal management system 40.

S95: The communication terminal management system 40 receives the list of guest information, and the screen information generation unit 32 generates the screen information of the additional invitation dialog based on the guest information.

S96: The first communication unit 31 of the communication terminal management system 40 transmits the screen information of the additional invitation dialog to the communication terminal 10 or the client PC 20.

The second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 receives the screen information of the additional invitation dialog, and the display control units 17 and 22 display the additional invitation dialog on the displays 120 and 208. An example of the additional invitation dialog is shown in FIG.

S97: In the add invitation dialog box, the host inputs the name and email address of the guest who wants to add and presses the add invitation button. The operation accepting units 12 and 23 of the communication terminal 10 or the client PC 20 accept. The second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 specifies the input guest information and sends an additional invitation request to the communication terminal management system 40. Subsequent processing may be the same as steps S39 to S43 in FIG.

S19-3: The second communication unit 11 of the communication terminal 10 or the third communication unit 21 of the client PC 20 receives the screen information of the guest management screen (when the additional invitation is successful), and the display control units 17 and 22 display the guest management screen ( (When the additional invitation is successful) is displayed on the displays 120 and 208. FIG. 38 shows an example of the guest management screen (when the additional invitation is successful).

FIG. 37 is a diagram showing an example of the additional invitation dialog 461 displayed on the displays 120 and 208 of the communication terminal 10 or the client PC 20. In FIG. 37, a list of registered guest information 392, a delete button 393, a guest name input field 462, a mail address input field 463, and an add invitation button 465 are provided. The registered guest information list 392 is similar to that shown in FIG. 19, for example. Further, the host has an “+add guest frame button” 464, and the organizer can additionally display a guest name input field 462 and a mail address input field 463.

FIG. 38 is a diagram showing an example of a guest management screen (upon successful addition invitation) 471 displayed on the displays 120 and 208 of the communication terminal 10 or the client PC 20. Compared with the guest management screen 451 (when the invitation information is successfully created) 451 in FIG. 35, a message 472 “Invited an additional guest from Sample Corporation ○○ 2018/10/10 13:30 to 15:00” Is displayed. "Sample Co., Ltd. ○○" is the name of the organizer, and "2018/10/10 13:30-15:00" is the invitation start date and time and the invitation end date and time.

<Summary>
According to the present embodiment, in addition to the effect of the first embodiment, it is possible to omit the work of the host sharing the invitation URL with the guest and the guest registering the guest information. The burden on the host may increase, but if the guest takes time to register the guest information, the burden on the guest can be reduced.

<Other application examples>
The best mode for carrying out the present invention has been described above with reference to the embodiments, but the present invention is not limited to these embodiments, and various modifications can be made without departing from the gist of the present invention. And substitutions can be added.

For example, the communication terminal 10 may have any name as long as it has a communication function. For example, an IWB (Interactive White Board: a white board having an electronic blackboard function capable of mutual communication), an output device such as a digital signage, a HUD (Head Up Display) device, an industrial machine, an imaging device, a sound collecting device, a medical device , A network home appliance, a car (Connected Car), a mobile phone, a game machine, a PDA (Personal Digital Assistant), a digital camera, a wearable PC, a desktop PC, or the like.

The devices described in the examples merely represent one of a plurality of computing environments for implementing the embodiments disclosed herein.

In some embodiments, communication management system 50 includes multiple computing devices such as server clusters. The plurality of computing devices are configured to communicate with each other via any type of communication link including a network, shared memory, or the like, and perform the processes disclosed herein. Further, each element of the communication management system 50 may be integrated into one server device or may be divided into a plurality of devices.

The configuration example of FIG. 5 shown in the above embodiment is divided according to the main functions in order to facilitate understanding of the processing of the communication management system 50, the communication terminal 10, and the client PC 20. is there. However, the present invention is not limited by the division method or name of each processing unit. The communication management system 50, the communication terminal 10, and the client PC 20 can be divided into more processing units according to the processing content. Also, one processing unit can be divided so as to include more processing.

Each function of the embodiments described above can be realized by one or a plurality of processing circuits. Here, the “processing circuit” in the present specification is a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, or designed to execute each function described above. ASICs (Application Specific Integrated Circuits), DSPs (digital signal processors), FPGAs (field programmable gate arrays) and conventional circuit modules.

2 communication network 10 communication terminal 20 client PC
40 Communication Terminal Management System 41 Authentication Management Server 42 Terminal Management Server 43 Destination List Management Server 44 Guest Management Server 45 Session Management Server 50 Communication Management System 100 Remote Communication System

Japanese Patent Laid-Open No. 2016-100724

Claims (14)

A remote communication system in which at least a first communication terminal and a second communication terminal communicate with each other via a communication management system,
The communication management system,
Storage means for storing destination list management information in which destinations that can be specified by the communication request source as communication destinations are registered;
A guest management unit that manages a user who invites a guest and registration of information about the guest;
When the guest management unit receives registration of the user and the guest, the guest is registered in the destination list management information with the request source and the user as the destination, and the user is the request source and the guest is the A destination list registration unit that is registered in the destination list management information as a destination,
When there is a request to start communication from the first communication terminal operated by the user or the second communication terminal operated by the guest, the first communication terminal and the second communication terminal based on the destination list management information. A communication management unit for connecting the communication terminals of
A remote communication system characterized by having. The communication management unit, when there is a communication start request from the first communication terminal or the second communication terminal,
The guest is registered as the request source, the user is registered as the destination in the destination list management information, and the user is registered as the request source and the guest as the destination in the destination list management information storage means. The remote communication system according to claim 1, wherein the first communication terminal and the second communication terminal are connected in this case. The guest management unit receives an invitation start date and time when the guest can start communication,
When the invitation start date and time arrives, the destination list registration unit registers the guest as the request source and the user as the destination in the storage unit of the destination list management information, and the user as the request source and the guest. 3. The remote communication system according to claim 1, wherein is registered in the storage unit of the destination list management information as the destination. When the guest management unit accepts registration of the user and the guest, authentication for registering authentication management information for the guest to log in to the storage unit of the authentication management information even if the invitation start date and time has not arrived. The remote communication system according to claim 3, further comprising a management information creating unit. The guest management unit receives the name of the user,
The destination list registration unit sets the guest as the request source and the user as the destination, and further registers the name of the user accepted by the guest management unit in a storage unit of the destination list management information,
The communication management system, when the guest logs in with the authentication management information, transmits the name of the user registered in the storage unit of the destination list management information to the second communication terminal operated by the guest,
The remote communication system according to claim 4, wherein the second communication terminal displays the name of the user on a display. The communication management system,
Inviting information regarding the invitation of the guest accepted by the guest management unit, and a storage unit for storing guest information regarding the guest associated with the invitation information with identification information for identifying the invitation information,
The guest information associated with the identification information of the invitation information is deleted when the guest management unit accepts a request for deleting the invitation information by designating the identification information of the invitation information. The remote communication system according to any one of 1 to 5. When the guest management unit accepts the guest list request by designating the identification information of the invitation information from the first communication terminal, the guest information is associated with the identification information of the invitation information as guest information. Obtained from, and sent to the first communication terminal,
The remote communication system according to claim 6, wherein the first communication terminal displays a list of the guests on a display. When the guest management unit accepts a guest deletion request by designating guest identification information for identifying the guest from the first communication terminal, the guest information specified by the guest identification information is set to the guest information. The remote communication system according to claim 6 or 7, wherein the remote communication system is deleted from the guest information. When the first communication terminal displaying the list of guests accepts the addition of a new guest, the guest information regarding the new guest is transmitted to the communication management system,
9. The remote communication system according to claim 8, wherein the guest management unit receives registration of a new guest transmitted from the first communication terminal. When the authentication management information creation unit registers in the authentication management information for the guest to log in,
6. The remote communication according to claim 4, wherein the guest management unit has a mail transmission unit for transmitting the fact that the registration of the guest information has been completed to the mail address of the guest received at the time of registering the guest as a destination. system. The communication management system,
A storage unit for storing invitation authority management information in which the user who has the authority to invite the guest is registered;
11. The remote communication system according to claim 1, wherein the guest management unit rejects registration of the guest from the user who is not registered in the invitation authority management information. In the invitation authority management information, the maximum number of guests invited, the maximum number of invitation periods, or the maximum number of invited guests is registered in association with the user.
12. The remote communication system according to claim 11, wherein the guest management unit rejects invitations of guests exceeding the maximum number of invited guests, the maximum invitation period, or the maximum number of invited guests. A communication method performed by a remote communication system in which at least a first communication terminal and a second communication terminal communicate with each other via a communication management system,
The communication management system,
Stores the destination list management information in which the destinations that can be specified by the communication request source are registered,
A guest management unit managing a user who invites a guest and registration of information about the guest;
When the guest management unit receives the registration of the user and the guest, the destination list registration unit registers the guest in the destination list management information with the guest as the request source and the user as the destination, and the user as the request source. , Registering the guest in the destination list management information as the destination,
When the communication management unit issues a communication start request from the first communication terminal operated by the user or the second communication terminal operated by the guest, the first communication based on the destination list management information. Connecting a terminal and the second communication terminal,
A communication method comprising: A communication management system that stores destination list management information in which destinations that can be specified by a communication request source as communication destinations are stored and that allows communication between a first communication terminal and a second communication terminal,
A guest management unit that manages a user who invites a guest and registration of information about the guest;
When the guest management unit receives registration of the user and the guest, the guest is registered in the destination list management information with the request source and the user as the destination, and the user is the request source and the guest is the A destination list registration unit that is registered in the destination list management information as a destination,
When there is a request to start communication from the first communication terminal operated by the user or the second communication terminal operated by the guest, the first communication terminal and the second communication terminal based on the destination list management information. Communication management unit that connects the communication terminals of
Program to function as.

Images