JPH0637909A - Remote conference terminal equipment - Google Patents

Abstract

PURPOSE:To easily attain the memory-reception of conference data only by managing the conference data at the range of his or her own conference directory by each user even at the time of receiving the conference data beyond the memory amounts of the conference directory of each user, by preliminarily distributing a memory at a reception side to the conference directory of each user, at the time of memory receiving the conference data from a transmission side by a remote convention terminal at the reception side. CONSTITUTION:At the time of memory-receiving the conference data transmitted from the transmission side by a remote convention terminal equipment at the reception side, the conference directory (33a, 33b, and 33c) of each user to which the prescribed memory amounts are preliminarily distributed by each user are prepared at the hard disk of a remote conference terminal equipment 32-1 at the reception side. A title name for designating the directory is added to the transmitted and received convention data, and when the conference data are received, the conference data are memory-received in the prescribed convention directory 33a of each user at the reception side. Then, when the conference data are beyond the memory amounts of the pertinent conference directory of each user, the reception of the conference data is refused.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a remote conference terminal device, and more particularly to a remote conference terminal device for receiving conference material sent from a remote conference terminal on the transmitting side in a memory on the remote conference terminal on the receiving side via a digital public network. Regarding

[0002]

2. Description of the Related Art In a conventional remote conference terminal device, in order to hold a conference between remote locations, each remote conference terminal device connected by a communication line is used, and the voice during the conference and the appearance of the conference partner are
Alternatively, a conference material or the like is transmitted / received as voice / image data and is output to a speaker, a display, a printer, or the like to hold a conference between remote persons.

In such a conventional remote conference terminal device, when the remote conference terminal on the transmitting side and the remote conference terminal on the receiving side receive the conference material in memory via the digital public network (for example, ISDN line). In addition, there is a case that the transmitted conference material cannot be received in the memory because there is not enough memory in the remote conference terminal on the receiving side. Therefore, the user on the receiving side of the conventional remote conference terminal deletes unnecessary unnecessary conference materials stored in the memory (hard disk etc.) using the touch panel, keyboard, etc., and newly stores the conference material memory. Forming an empty area in the area was performed.

Further, as described above, when the user of the remote conference terminal on the receiving side deletes unnecessary conference material, he / she can judge whether or not his / her conference material is necessary. However, since it is not possible to determine whether or not the conference materials of other users are necessary, it is not possible to arbitrarily delete the conference materials and form an empty area.

[0005]

As described above, in the conventional teleconferencing terminal device, when transmitting / receiving the conference material between the teleconferencing terminals, it is premised that the memory has an empty area for receiving the memory. However, if the old conference material remains stored and there is no empty area in the memory, new conference material cannot be written. For this reason, if unnecessary old meeting materials are deleted and an empty area is formed in the memory, new meeting materials can be received in the memory. It was difficult to judge the point of the, and it could not be erased arbitrarily. Therefore, in the conventional remote conference terminal device, when the memory of the remote conference terminal device on the receiving side overflows,
There is a problem that the situation where the memory cannot be received cannot be easily resolved.

The present invention has been made in view of the above conventional problems, and when receiving the conference material from the transmitting side to the receiving side remote conference terminal in the memory, the receiving side memory is previously stored in the conference directory for each user. Therefore, even if the meeting material exceeds the memory capacity of the meeting directory for each user, each user only needs to manage the meeting material within the range of his / her meeting directory. An object of the present invention is to provide a remote conference terminal device capable of easily forming an enabled state.

[0007]

The invention according to claim 1 is
In a remote conference terminal device in which the conference material sent from the remote conference terminal on the transmitting side is received by a memory in the remote conference terminal on the receiving side via the digital public network, the memory of the remote conference terminal on the receiving side is stored in the memory for each user. User-specific conference directory creating means for allocating the conference directory for each memory amount that can be stored and managed, and the memory amount of the user-specific conference directory when receiving the conference material of a predetermined user in the user-specific conference directory. If it exceeds,
If the meeting material reception refusal means for rejecting the reception of the meeting material and the memory amount of the meeting directory for each user are exceeded,
In the user-specific conference directory, a reception-disabled state notifying means for notifying the remote conference terminal on the transmitting side that no further conference material can be received, and notifying the user of the conference terminal on the receiving side, is also provided. It is characterized by having.

According to a second aspect of the present invention, in the remote conference terminal device according to the first aspect, when the conference material received by the receiving remote conference terminal in the memory exceeds a predetermined memory amount of the conference directory for each user. In addition, a backup directory creating means for creating a backup directory for storing the remaining conference material, and when the conference material is received exceeding the memory capacity of the predetermined conference directory for each user, the backup directory is stored in the backup directory. And a saving directory storage notifying means for storing the conference material and notifying the user of the remote conference terminal on the reception side of the conference material.

The invention according to claim 3 is the invention according to claim 1 or 2.
In the remote conference terminal device described in the above, when receiving the conference material in the memory exceeding the memory amount of each conference directory in which the memory of the remote conference terminal on the receiving side is allocated for each predetermined memory amount, the memory receiving conference is performed. An empty memory area that searches the meeting material with the oldest update date among the meeting materials already stored in the directory for data output to the plotter and deletes the output meeting material data to form an empty memory area Forming means, and a conference material to be received exceeding the memory amount of the conference directory is stored in an empty memory area formed in a predetermined conference directory of the remote conference terminal on the receiving side, and to that effect the remote conference terminal on the receiving side. And an empty memory area storage notifying unit for notifying the user.

[0010]

According to the first aspect of the present invention, the conference directory is allocated for each user in the memory of the remote conference terminal on the receiving side so that each user can store and manage the conference material.
When the meeting material is received in excess of the allocated memory capacity of the user-specific meeting directory, the reception is rejected, and it is notified that no more meeting material can be received in the user-specific meeting directory. Notify the user of the remote conference terminal on the receiving side. For this reason, there is no need to worry about the remaining memory capacity due to the memory usage of other users, and simply managing the meeting materials in your own meeting directory will smoothly store the newly sent meeting materials. You can deal with it so that you can receive it.

According to the second aspect of the invention, a save directory is created in addition to the user-specific conference directory,
When the conference material is received exceeding the memory capacity of the predetermined conference directory for each user, the conference material is stored in the save directory and the user of the remote conference terminal on the receiving side is notified of the fact. Therefore, it is not necessary to worry about the remaining capacity of the memory used by other users, and even if the meeting material cannot be received because the memory capacity of the meeting directory for each user is exceeded, it will be saved. The meeting material can be stored in the directory and the memory reception of the meeting material can be completed.

According to the third aspect of the present invention, when the memory reception of the conference material exceeds the memory capacity of each conference directory of the remote conference terminal on the receiving side, the update already stored in the conference directory. After the conference material with the oldest date is output to the plotter, the output data is deleted from the conference directory to form an empty memory area. And
In this empty memory area, the conference material which cannot be received due to exceeding the memory capacity is stored, and the fact is notified to the user of the remote conference terminal on the receiving side. Therefore, the user of the remote conference terminal on the receiving side does not need to judge whether or not to delete the conference material in the conference directory, and the conference material cannot be received because there is no empty memory area in the conference directory. The situation can be avoided.

[0013]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described below with reference to the drawings. First, the configuration will be described. FIG. 1 is a block diagram showing the configuration of a remote conference terminal device according to an embodiment of the present invention. In the figure, 1 is a remote conference terminal device that is connected to another remote conference terminal device via a digital public network such as ISDN to form a remote conference system, and 2 is a received document, guidance information, etc. on a display such as an LCD. Display part to display, 3
Is a VRAM as a memory for displaying characters and graphics on the display unit 4, 4 is a graphic controller for controlling image data such as characters and graphics, 5 is a CPU for controlling the entire system of the remote conference terminal device 1, 6
Is a DMA controller for directly inputting / outputting data to / from a memory unit or a hard disk, which is a main storage device,
Is an interrupt controller for interrupt control, 8 is a CP
A memory including a ROM (Read Only Memory) that stores firmware that determines the control operation of the U5 and a RAM (Random Access Memory) that forms a work area and a temporary storage area necessary for the CPU 5 to control Section, 9 is a writing pad for handwriting input with a touch pen, 10 is a serial interface of the writing pad 9, and 11 is an LAPD (Link Access Procedure on) for performing a link access procedure for ISDN D channel.
The D-channel), 12 and 13 are LAPB (Link Access Procedure-Balance) for performing balanced link access procedure.
d) and 14 are media that multiplex and transmit information for separating various communication media such as voice, data, facsimile, and images using a single high-speed digital line, or a medium that separates the multiplexed received information. Multiplexer, 15 is ISDN
ISDN interface for connection with (service integrated digital network), 16 is a digital public network (for example, ISDN
Line), 17 is a video interface that outputs the received video data to a video display, 18 is a speaker that outputs the meeting audio, 19 is a microphone that inputs the meeting audio, and 20 is a received meeting material, etc. Hard disk (hereinafter also referred to as HD) for storing original data, 21 is HD20
Small computer system interface SCSI (Small Computer System Interfac)
e), 22 is a keyboard for specifying a file title by key input, 23 is a serial interface for connecting the keyboard 22, 24 is a scanner for reading a document and converting it into image data, 25 is an SCS for connecting the scanner 24
I and 26 are printers for printing out the received image data and the like, 27 is a serial interface for connecting the printer 26, 28 is compression of the image data to be transmitted by encoding, or decoding and expansion of the compressed received data is expanded. A compression / expansion unit 29 is a system bus for connecting the above units to exchange data.

As shown in FIG. 2, the remote conference terminal device 1 shown in FIG. 1 has a digital public network (ISDN: Integrat).
ed Services Digital Network) 31, and here, the remote conference terminal device 30 on the side of transmitting the conference material and the remote conference terminal devices 32-1 to 32-n on the side of receiving the conference material. It is composed of. When the conference material for remote conference is transmitted from the remote conference terminal device 30 shown in FIG. 2 to another remote conference terminal device 32-1, the scanner 24 shown in FIG.
The conference material document to be transmitted is read, or the conference material data already stored in the HD 20 is read and the conference material is transmitted to the partner terminal via the ISDN line 16.

In this transmitted manuscript, it is necessary that all the participants have a common conference material (file) name when the conference is held. Therefore, in this embodiment, the conference name (file) is added to the document profile of the conference material (file) to be transmitted.
The conference material manuscript information such as the number of conferences and the conference material number is added. Then, in the remote conference terminal device 32-1 on the receiving side,
Check the information such as the meeting name, the number of meetings, and the material number of the meeting material (file) from the document profile of the received meeting material, perform the necessary processing, and then in the corresponding directory of the document profile, the same file as the document profile. Store by name. Then, the user can execute the desired remote conference service by using the conference material stored in the predetermined directory at an appropriate time.

The hard disk (hereinafter, also referred to as HD) of the remote conference terminal device 32-1 on the receiving side in this embodiment has a directory structure as shown in FIGS. 3 to 5, for example. That is, FIG. 3 is a diagram showing a directory structure of the remote conference terminal device according to the embodiment of the invention described in claim 1. As shown in FIG. 3, in the hard disk of the remote conference terminal device 32-1 on the receiving side, in addition to the conference directory 33 for receiving and storing the conference material in the memory, for example, received data from the G4 facsimile device is stored. A G4 facsimile file 34 for storing and a system parameter file 35 for storing system parameters are formed. In the case of claim 1, the conference directory 33 is further divided for each user (user A33a,
User B33b, user B33c ...), here 2Mb
A user-specific conference directory having a work area for each yte is formed.

FIG. 4 is a diagram showing a directory structure of a remote conference terminal device according to an embodiment of the present invention. The characteristic directory structure of FIG. 4 is, in addition to the user-specific conference directory formed in the conference directory 33 of FIG. 3, an evacuation directory for storing conference materials that exceed the work area in each user-specific conference directory.
33e is formed.

Further, FIG. 5 is a diagram showing a directory structure of a remote conference terminal device according to an embodiment of the present invention. The directory structure of FIG. 5 is the same as that of FIG. 3, but when the conference material received in the memory in any of the conference directories for each user (for example, user A33a) exceeds the work area, the update date of the directory is updated. After outputting the old meeting material of No. 1 to the plotter, the data is erased to form an empty memory area, and the meeting material exceeding the work area is received in the memory.

Next, the operation will be described. First, as shown in FIG. 2, from the remote conference terminal device 30 to the digital public network (IS
In the case where the conference material is received by the remote conference terminal device 32-1 via the DN 31 in the memory, the remote conference terminal device on the receiving side.
When the conference material sent from the remote conference terminal device 30 cannot be received because the 32-1 memory is insufficient, the conventional remote conference terminal device does not require the user of the remote conference terminal device 32-1. The meeting material was selected and deleted using the touch panel or keyboard 22 to create an empty area in the memory.

However, the remote conference terminal device 32-1 on the receiving side
It was inconvenient for other users to delete the unnecessary meeting materials, but could not judge the meeting materials of their own, but could not judge the meeting materials of other users. . Therefore, in the embodiment according to the invention described in claim 1, in the remote conference terminal device 32-1 on the receiving side, as shown in FIG. 3, a conference directory for each user dedicated to each user is formed. When the memory capacity (2 Mbytes) of the conference directory for each user is exceeded, the reception of the conference material from the remote conference terminal device 30 on the transmitting side is rejected.

FIG. 6 is a flowchart of the remote conference terminal device having the directory structure of the remote conference terminal device shown in FIG. As shown in FIG. 6, when the remote conference terminal device 32-1 on the receiving side receives an incoming call, the following process is started. First, it is determined whether the received document is a normal G4 facsimile document or conference material (step 100). In the case of the meeting material, the directory to be stored is determined from the title name of the meeting material sent (step 101). Here, if the directory corresponding to the title name does not exist (step 102) or if the received document is a normal G4 facsimile document in step 100, the received document is immediately output to the plotter and the transmission ends (step 102).
103).

Next, when the directory to be stored exists and is determined in step 102, it is determined whether or not the amount of conference material already stored exceeds the memory amount allocated to each directory ( Step 104). If the amount of memory is not exceeded, the conference material is received in the corresponding directory (step 105), and the amount of newly received conference material data is added to the amount of already received conference material (step 106). Then, in step 105, it is determined whether or not the memory capacity is constantly exceeded even while storing the meeting material in the corresponding directory (step
107) If the memory capacity is exceeded, the display device such as the plotter or LCD does not have enough memory so that the user on the receiving side is notified that the conference material cannot be received any more and the communication is terminated (step 108). ). If the memory capacity is not exceeded in step 107, the conference material is stored in the corresponding directory and the communication ends (step 109).

If the memory capacity is exceeded at the time of step 104, the transmitting side terminal is notified that the receiving side memory is full, and the communication is terminated (step 110), and the plotter or receiving side The display such as the LCD is informed that the conference material cannot be received due to lack of memory (step 111). As described above, according to the embodiment of the invention described in claim 1, it is not necessary to care about the remaining memory capacity of the memory used by other users, and only the conference material in the conference directory dedicated to each user is used. To manage the
When the received conference material exceeds the memory capacity of the unique conference directory, the reception is automatically rejected, and both the sender and the receiver are notified of that. Appropriate treatment can be taken.

Next, in the embodiment according to the second aspect of the invention, in the remote conference terminal device 32-1 on the receiving side, as shown in FIG. 4, a conference directory for each user (33a, 33b, 33c) is formed, and an evacuation directory 33e is formed for receiving the remaining conference material in the memory when the memory capacity (2 Mbytes) of the predetermined conference directory for each user is exceeded. Then, in this embodiment, when receiving the meeting material exceeding the memory amount allocated to the user-specific meeting directory, the meeting material is received in the above-mentioned evacuation directory 33e,
This is notified to the user by outputting it as a report to a plotter or an indicator.

FIG. 7 is a flowchart of the remote conference terminal device having the directory structure of the remote conference terminal device shown in FIG. As shown in FIG. 7, when the receiving remote conference terminal device 32-1 receives an incoming call, the following process is started. First, it is determined whether the received document is a normal G4 facsimile document or conference material (step 200). In the case of meeting materials, the directory to be stored is determined from the title name of the meeting materials sent (step 201). Here, if the directory corresponding to the title name does not exist (step 202) or if the received document is a normal G4 facsimile document in step 200, the received document is immediately output to the plotter and the transmission is terminated (step
203).

Next, when the directory to be stored exists and is determined in step 202, it is determined whether the amount of conference material already stored exceeds the memory amount allocated to each directory ( Step 204). If the memory capacity is not exceeded, the conference material is received in the corresponding directory (step 205), and the data amount of the newly received conference material is added to the amount of the conference material already received (step 206). Then, in step 205, it is determined whether or not the memory capacity is constantly exceeded even while the conference material is being stored in the corresponding directory (step
207) If the amount of memory is exceeded, the display device such as the plotter or LCD does not have enough memory, so the user on the receiving side is notified that the conference material cannot be received any more, and the communication ends (step 208 ). If the memory capacity is not exceeded in step 207, the conference material is stored in the corresponding directory and the communication ends (step 209).

If the memory capacity is exceeded at the time of step 204, the conference material is stored in the save directory and the communication is terminated (step 210), and saved on the display device such as the plotter or LCD on the receiving side. Display that meeting materials are temporarily stored in the directory for use (step 21)
1). As described above, according to the second embodiment of the present invention, there is no need to care about the remaining memory capacity of the memory used by other users, and the memory of the conference directory for each user on the receiving side can be eliminated. By receiving the conference material in the evacuation directory even if the amount is exceeded, it is possible to avoid the situation where the conference material cannot be received.

Further, in the embodiment according to the invention described in claim 3, in the remote conference terminal device 32-1 on the receiving side, as shown in FIG. 5, a conference directory (33a, 33b, 33c for each user) dedicated to each user is provided. ) Is formed. In this embodiment, the memory capacity of the predetermined conference directory for each user (2 Mby
te) is exceeded, out of the conference materials already stored in the conference directory for each user, the conference material with the oldest update date is output to the plotter, then the data is deleted and empty memory in the directory. Form an area. And
Store meeting materials in the automatically created empty memory area,
This is notified to the user by outputting it as a report to a plotter or an indicator.

FIG. 8 is a flowchart of the remote conference terminal device having the directory structure of the remote conference terminal device shown in FIG. As shown in FIG. 8, when the remote conference terminal device 32-1 on the receiving side receives an incoming call, the following process is started. First, it is determined whether the received document is a normal G4 facsimile document or conference material (step 300). In the case of meeting materials, the directory to be stored is determined from the title name of the meeting materials sent (step 301). Here, if the directory corresponding to the title name does not exist (step 302), or if the received document is a normal G4 facsimile document in step 300, the received document is immediately output to the plotter and transmission is terminated (step
303).

Next, if the directory to be stored in step 302 exists, the conference material is stored in the corresponding directory (step 304), and the conference material data amount to be stored in that directory is stored in the conference. It is added to the data amount of the material (step 305). Then, in step 304, it is determined whether or not the memory amount is always exceeded even while the conference material is being stored in the corresponding directory (step 306).
Search the meeting materials with the oldest update date among the meeting materials stored in the corresponding directory (step
307). Then, the retrieved conference material manuscript is applied to the plotter to delete the output data from the memory to form an empty memory area (step 308). Therefore, the data amount of the conference material output to the plotter is subtracted from the corresponding directory (step 309).

Here, again, returning to step 306, it is judged again whether the amount of the conference material already stored exceeds the memory amount allocated to each directory.
If the memory capacity is exceeded, the same processing as the above steps 307 to 309 is performed. If the memory capacity is not exceeded, the conference material is stored in the directory and the communication is terminated (step 310).

As described above, according to the third embodiment of the present invention, it is not necessary to care about the remaining memory capacity of the memory used by other users, and the conference directory for each user on the receiving side is provided. Even if the conference material is received in excess of the memory capacity of, even if the user on the receiving side does not delete the conference material, the empty memory area is automatically formed and the memory reception is continued. You can

[0033]

According to the invention described in claim 1, the memory of the remote conference terminal on the receiving side stores the conference material for each user.
A conference directory is allocated for each manageable memory amount, and when the conference material is received in excess of the allocated memory amount of the predetermined conference directory for each user,
Reject the reception and notify the users of the remote conference terminals on the transmission side and the reception side that no further conference material can be received in the conference directory for each user. As a result, there is no need to worry about the remaining memory capacity due to other users' memory usage conditions. Simply by managing the meeting materials in your own meeting directory, newly sent meeting materials can be stored smoothly. You can deal with it so that you can receive it.

According to the second aspect of the invention, in the case where a save directory is created in addition to the user-specific conference directory and the conference material is received exceeding the memory capacity of the predetermined user-specific conference directory, The conference material is stored in the save directory and the user of the remote conference terminal on the receiving side is notified of that fact. This eliminates the need to worry about the remaining capacity of the memory used by other users, and saves it even if the meeting material cannot be received due to exceeding the memory capacity of the meeting directory for each user. The meeting material can be stored in the directory and the memory reception of the meeting material can be completed.

Further, according to the third aspect of the invention, when the memory reception of the conference material exceeds the memory amount of each conference directory of the remote conference terminal on the receiving side, it is already stored in the conference directory. After outputting the conference material having the oldest update date to the plotter, the output data is deleted from the conference directory to form an empty memory area. Then, the conference material that cannot be received due to exceeding the memory amount is stored in this empty memory area, and the fact is notified to the user of the remote conference terminal on the receiving side. As a result, the user of the remote conference terminal on the receiving side does not need to judge whether or not to delete the conference material in the conference directory, and the conference material cannot be received because there is no empty memory area in the conference directory. The situation can be avoided.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of a remote conference terminal device according to an embodiment of the present invention.

FIG. 2 is a diagram showing a line connection state and operation of a remote conference terminal device according to an embodiment of the present invention.

FIG. 3 is a diagram showing a directory structure of a remote conference terminal device according to the first aspect of the invention.

FIG. 4 is a diagram showing a directory structure of a remote conference terminal device according to a second aspect of the invention.

FIG. 5 is a diagram showing a directory structure of a remote conference terminal device according to a third aspect of the invention.

FIG. 6 is a flowchart for explaining the operation of the remote conference terminal device according to the invention of claim 1.

FIG. 7 is a flowchart for explaining the operation of the remote conference terminal device according to the invention of claim 2.

FIG. 8 is a flowchart illustrating an operation of the remote conference terminal device according to the third aspect of the invention.

[Explanation of symbols]

 1 remote conference terminal device 2 display unit 5 CPU 9 writing pad 11 LAPD 12,13 LAPB 14 media multiplexing unit 15 ISDN interface 16 ISDN line 20 hard disk 22 keyboard 24 scanner 26 printer 28 compression / expansion unit 29 system bus 30 remote conference terminal device (Sender) 31 Digital public network 32 Remote conference terminal device (Receiver) 33 Conference directory 33a, 33b, 33c User-specific conference directory 33e Evacuation directory

Claims (3)

[Claims] 1. A remote conference terminal device for receiving conference material sent from a remote conference terminal of a transmitting side in a memory of the remote conference terminal of a receiving side via a digital public network, comprising: A user-specific conference directory creating means for allocating the conference material for each user to a conference directory for each memory size capable of storing and managing the conference material, and a conference for each user when receiving the conference material of a predetermined user in the user-specific conference directory from the memory. When the memory capacity of the directory is exceeded, the meeting material reception refusal means for rejecting the reception of the meeting material and when the memory capacity of the user-specific meeting directory is exceeded, further meeting material is not stored in the user-specific meeting directory. Notifies the remote conference terminal on the sending side that the message cannot be received, and also notifies the user of the conference terminal on the receiving side. Teleconference terminal apparatus characterized by comprising: a signal disabling state notifying means. 2. The remote conference terminal device according to claim 1, wherein when the conference material received by the receiving remote conference terminal in the memory exceeds the memory capacity of a predetermined user-specific conference directory, the remaining conference material is retained. Save directory creating means for creating a save directory for storing, and when meeting material is received exceeding the memory capacity of the predetermined user-specific meeting directory, the meeting material is stored in the save directory, A remote conference terminal device, comprising: a saving directory storage notifying means for notifying the user of the remote conference terminal on the receiving side. 3. The remote conference terminal device according to claim 1 or 2, wherein the conference material is stored in a memory exceeding the memory amount of each conference directory in which the memory of the remote conference terminal on the receiving side is allocated for each predetermined memory amount. When receiving, retrieves the conference material with the oldest update date among the conference materials already stored in the conference directory received by the memory, outputs it to the plotter, and deletes the output conference material data. Empty memory area forming means for forming an empty memory area and a meeting material to be received exceeding the memory capacity of the meeting directory in the empty memory area formed in a predetermined meeting directory of the remote conference terminal on the receiving side. A remote conference terminal device, comprising: empty memory area storage notifying means for notifying the user of the remote conference terminal on the receiving side.