Communication apparatus, a communication system and a communication method

[0002] 1. Field of the Invention

[0003] The present invention relates to a communication apparatus, a communication system, and a communication method for performing a task involving the cooperative employment of a plurality of networked terminals that are remotely located.

[0004] 2. Related Background Art

[0005] Conventionally, a variety of tasks are cooperatively performed by persons at remote locations while using systems comprising a plurality of terminals that are joined together to form networks. A conventional system is created for each task that constitutes a cooperative effort (session). That is, a remote conference convening system is activated convening a remote conference, a remote lecture assembly system is activated for presenting a remote lecture, and a status evaluation system is activated for evaluating existing conditions.

[0006] These systems are independently developed, and the user interfacing specifications for each of them differ.

[0007] When an independent system is created for each task that involves a cooperative effort, it is not possible to smoothly shift the performance of one task to another.

[0008] For example, when a user is performing a task that involves using the status evaluation system to obtain an understanding of the status of a person located at a remote side, and he or she desires to converse with that person, the user must activate a conversation participation system.

[0009] Since the user interface specifications differ from system to system, the user must understand all of the user interface specifications for all of the systems he or she uses.

[0010] As a security problem that is conventionally encountered, a conventional system can not clearly distinguish between the access management procedures that apply when a third party is to participate in a session and the privacy management procedures that apply when a third party is to be provided information concerning the session. Therefore, a conventional system can not adequately respond to a request for information concerning a session when participation in the session is not contemplated.

[0011] As another security problem, since conventionally a plurality of terminals are employed and are used in common during a session in which static images are mutually transmitted, the reception programs at all of the receiving terminals access and display data output by a transmission program that is employed at one terminal. In this case, when the transmission and reception programs are intended for a special application, such as for a video conference, special authentication means and operation rejection and acceptance means are provided for the transmission and the reception programs, so that a system having no security problem can be provided.

[0012] Further, in order to use in common a general program, not a special one, among a plurality of terminals networked for a video conference, or to eliminate the labor involved in creating a special reception program, a display instruction from a general program that is operating on one terminal may be received by general-purpose display programs at the other, individual terminals, which thereafter display the data they receive. This reception and display operation is accomplished at a workstation by using a server program, a so-called window server.

[0013] Besides window servers, file I/O servers are popular server programs that provide some services in response to external requests. A file I/O server may, for example, respond to an external request by transferring data from a file to a requesting person. But since the file I/O servers, as well as the window servers, have not been developed for the purpose of supporting the convening of video conferences, setups by which access of conference is enabled can not be provided, with the result that the security procedures are either excessively strict, such as one that requires the use of a password by each participant, or they are excessively lax, such as one that grants access to anybody.

[0014] A window server, for example, includes a procedure for designating users to whom operating permission is to be provided, so as to prevent the execution of display instructions that are issued by unauthorized persons. Since the persons for whom communication is authorized can not be selected in advance when a window server is employed for a video conference, the server is so set that it permits the execution of display instructions it receives from any person.

[0015] It is therefore one object of the present invention to provide a communication apparatus that has a preferable usability for operating a plurality of sessions, and a communication system and a communication method therefor.

[0016] It is another object of the present invention to provide a communication apparatus that can easily ascertain whether access to a session is required or not, and a communication system and a communication method therefor.

[0017] It is an additional object of the present invention to provide a communication apparatus that can identify a request for access and that, in response to the access request, can appropriately determine whether or not it is possible to permit access, and a communication system and a communication method therefor.

[0018] It is a further object of the present invention to provide a communication apparatus that has an innovative function, and a communication system and a communication method therefor.

[0019] By referring to the following embodiments and drawings, other features of the present invention will become readily apparent.

[0020] FIGS. 1A and 1B are diagrams illustrating the structure of a session operation apparatus according to a first embodiment of the present invention;

[0021] FIG. 2 is a diagram illustrating a user interface according to the first embodiment of the present invention;

[0022] FIG. 3 is a diagram showing the relationship between data in a session data management unit and a session content display section;

[0023] FIG. 4 is a diagram in which session objects are shown as classes according to the first embodiment of the present invention;

[0024] FIG. 5 is a flowchart of the processing for an object generator for a conversation session object;

[0025] FIG. 6 is a flowchart of the processing for an object extinguisher for a conversation session object;

[0026] FIG. 7 is a flowchart of the processing for adding the icon for a participant to a conversation session object;

[0027] FIG. 8 is a flowchart of the processing for deleting an icon for a participant from a conversation session object;

[0028] FIG. 9 is a flowchart of the processing for a function for calling back a drop event for a conversation session object;

[0029] FIG. 10 is a flowchart of the processing for a function for calling back a drag event for a conversation session object;

[0030] FIG. 11 is a flowchart of the processing for each function for calling back a lecture assembly session creating request event;

[0031] FIG. 12 is a flowchart of the processing for a function for calling back a lecture assembly session creating request event;

[0032] FIG. 13 is a flowchart of the processing for a function for calling back a session termination event;

[0033] FIG. 14 is a block diagram illustrating the structure of a session operation apparatus according to a second embodiment of the present invention;

[0034] FIG. 15 is a diagram illustrating a user interface according to the second embodiment;

[0035] FIGS. 16A and 16B are diagrams illustrating a user interface, a camera control interface, and an input image display on a session content display panel according to the second embodiment;

[0036] FIG. 17 is a diagram illustrating the line connections for understanding the operating conditions of a session;

[0037] FIG. 18 is a diagram illustrating the line connections while participating in a session;

[0038] FIG. 19 is a diagram in which session objects are shown as classes according to the second embodiment of the present invention;

[0039] FIG. 20 is a flowchart of the processing for calling back a drag event for a window icon;

[0040] FIG. 21 is a flowchart of processing for calling back a drop event to a window icon;

[0041] FIG. 22 is a flowchart of the processing for calling back a mouse input event for a window icon;

[0042] FIG. 23 is a flowchart of the processing for calling back a drop event for a door icon;

[0043] FIG. 24 is a flowchart of the processing for calling back a mouse input event for a door icon;

[0044] FIG. 25 is a block diagram illustrating a third embodiment of the present invention;

[0045] FIG. 26 is a flowchart of the participation request processing for a video conference system that employs the present invention;

[0046] FIGS. 27A and 27B are diagrams illustrating a panel that is displayed on a screen at user determination step S206;

[0047] FIG. 28 is a flowchart of the detailed processing for the user determination step S206;

[0048] FIG. 29 is a flowchart of the processing for exiting from a conference;

[0049] FIG. 30 is a block diagram illustrating a fourth embodiment of the present invention; and

[0050] FIG. 31 is a flowchart of the processing for a fifth embodiment of the present invention.

[0051] The preferred embodiments of the present invention will now be described while referring to the accompanying drawings.

[0052] FIG. 1A is a diagram illustrating the external appearance of a session operation apparatus according to a first embodiment of the present invention. It should be noted that sessions in this embodiment and in embodiments that will be described later are performed by using communication equipment to connect together the apparatuses in FIG. 1A.

[0053] In FIG. 1A, a display device 1 displays a user interface, which will be described later, an image acquired by the camera of an apparatus of another participant in a session, and a camera control interface. Reference numeral 2 denotes a display portion. A main body 3 includes a terminal 10 in FIG. 1B that will be described later. Pointing devices 4 and 5 are a mouse or a keyboard for inputting a user event.

[0054] A camera 6 is employed to capture a likeness of a user that operates the session operation apparatus. The camera 6 can be remotely controlled, by means of a camera control interface that will be described later, by a user at another apparatus.

[0055] A microphone 7 is attached to the camera 6, and audio volume can be remotely controlled, using the camera control interface, by the user at the other apparatus.

[0056] In FIG. 1B, reference numeral 10 denotes a terminal; and 11 denotes a session list display section, in the display portion 2 shown in FIG. 1A, that displays a list of session contents display sections 12-1 through 12-n. The session contents display sections 12-1 through 12-n in the display portion 2 in FIG. 1A are employed to display for a user data that are managed by a session information management unit 16. A session operation unit 13 instructs the generation of a session and its termination.

[0057] When information is updated by the session information management unit 16, a session information update event detecting unit 14 relays the updated contents to the session contents display sections.

[0058] A control unit 15 calls the appropriate procedures, which will be described later, in response to events that are initiated by user entries at the keyboard 5 or with the mouse 4 in FIG. 1A.

[0059] The session information management unit 16 collectively manages information concerning a session. The functions of the session information management unit 16 can be provided by using a special terminal, or by the session information unit 16 being employed at a terminal that provides control for a session.

[0060] The operations of the individual components in FIG. 1B will now be described.

[0061] The control unit 15 detects and responds to an event that is input using either the pointing device 4 or 5, or a session information update event from the session information management unit 16, and performs processing in consonance with the detected event. More specifically, when the control unit 15 detects a user initiated request for a scroll instruction event in the display region of the session list display section 11, the control unit 15 transmits the event request to the session list display section 11. Upon receipt of the event request, the session list display section 11 horizontally or vertically displaces data in the regions wherein the session contents display sections 12 are displayed. Even when the size of the display region of the session list display section 11 is limited, this operation can be performed to display all the session contents display sections 12.

[0062] When the control unit 15 detects a user initiated request for a display content update event in the display region of the session contents display section 12, the control unit 15 transmits the event request to the session contents display section 12. Upon receipt of the event request, the session contents display section 12 updates its display contents and updates the information held by the session information management unit 16.

[0063] When the control unit 15 detects a user initiated request for a session generation or termination of the generation in the display region of the session operation unit 13, the control unit 15 transmits the event request to the session operation unit 13. Upon receipt of the event request, the session operation unit 13 either generates the session contents display section 12 or terminates its generation, and updates the information held by the session information management unit 16.

[0064] When the control unit 15 detects an event request for a session information update originating at the session information management unit 16, i.e., an event request initiated by a user at another terminal, the control unit 15 transmits the event request to the session data update detecting unit 14. Upon receipt of the event, the session information update detecting unit 14 either generates the session contents display section 12 or terminates its generation, or updates the display contents in consonance with the detected event request.

[0065] The session information management unit 16 manages the information concerning a session. The session information management unit 16 receives requests from either the session contents display section 12 or the session operation unit 13, and updates the managed information. The session information management unit 16 then transmits to the control unit 15 of another terminal the updated contents.

[0066] A user interface is shown in FIG. 2.

[0067] In FIG. 2, a session list display panel 31 is the user interface for the session list display section 11, and includes session contents display panels 32-1 through 32-6. Upon receipt of input at a scroll bar 311, the display region is moved horizontally.

[0068] The session contents display panels 32-1 through 32-6 are user interfaces for the session contents display section 12, and information concerning the session is displayed thereon in a form that is consonant with a session type.

[0069] In the session contents display panel 32-1 in FIG. 2, a situation is depicted wherein B and C are participating in a conversation session. The indicated identification number for this session is 71.

[0070] In the session contents display panel 32-2, a situation is depicted wherein D3, E and F are participating in a conversation session. The indicated identification number for this session is 35.

[0071] In the session contents display panel 32-3, a situation is depicted wherein H is presenting a lecture and I, J, K, L and M are attending the lecture. The indicated identification number for this session is 57.

[0072] In the session contents display panel 32-4 is depicted a situation wherein A is present in his or her private room. In this situation, A can participate in (start) a session at any time.

[0073] In the session contents display panel 32-5 is depicted a situation wherein B is not present in his or her private room. B is participating in a session.

[0074] In the session contents display panel 32-6 is depicted a situation wherein C is not present in his or her private room.

[0075] The acts of participating in a session and exiting from a session are effected by dragging and dropping an icon for a person.

[0076] When, for example, A, who is an operator of this apparatus, desires to participate in the conversation between B and C, the icon for A in the panel 32-4 is dragged, by using the previously mentioned pointing device, and is dropped into the panel 32-1. Then, the icon of A in the panel 32-4 is altered to indicate absence, the icon A is added to the display region in the panel 32-1, and the situation is depicted wherein A, B and C are participating in a conversation. With this instruction, the main body 3 in FIG. 1A makes a communication line connections in consonance with telephone numbers, or addresses, for B and C that are stored in advance in a RAM (not shown). As a result, audio/video communication is attained.

[0077] A session operation panel 33 is a user interface for the session operation unit 13, and is employed to instruct the generation of a session and its termination.

[0078] A lecture assembly session is generated by depressing (clicking) a button 33-1 using the pointing device, and a conversation session is generated by depressing a button 33-2.

[0079] When a session is to be ended, the session is dragged using the previously mentioned pointing device, and is dropped on an ion 33-3.

[0080] Such a user interface can be built by a combination of, for example, the UNIX X-Window system and an OSF motif widget set.

[0081] The session list display panel 31 is constructed using a scroll window widget.

[0082] The session contents display panels 32-1 through 32-6 are constructed by using in a window a combination composed of a plurality of widgets.

[0083] The conversation session contents display panel, in which information concerning a conversation session is displayed, can be constructed by using in a combination composed of a label widget for displaying a session identifier in a window, a label widget for displaying the icon of a participant, and a RowColumn widget for arranging these label widgets.

[0084] The lecture assembly session contents display panel in which information concerning a lecture assembly session is displayed can be constructed using a combination composed of a label widget for displaying a session identifier in a window, a label widget for displaying the icon of a lecturer, and a RowColumn widget for arranging these label widgets.

[0085] The private room session contents display panels in each of which is displayed information concerning a private room session can be constructed by using a combination composed of a label widget for displaying the name of an owner of a session in a window, a label widget for displaying the icon of the owner, and a label widget for displaying the status of the owner.

[0086] The session operation panel 33 can be constructed by using a combination composed of a button widget for generating a conversation session, a button widget for generating a lecture assembly session, and a label widget for dropping an icon when a session is terminated.

[0087] The processing for the first embodiment will now be described while referring to FIGS. 2 through 13.

[0088] Since the session list display panel 31, which is the user interface for the session list display section 11, is provided by using a scroll window widget, the display region for the session list display section 11 is automatically scrolled in response to input at the scroll bar 311.

[0089] The number of sessions that are registered in the session information management unit 16 varies depending on the generation and the extinguishing of sessions.

[0090] Since the session contents display sections 12-1 through 12-n are provided in order to display for a user information that is managed by the session information management unit 16, the amount of information varies in consonance with the number of sessions that are registered by the session information management unit 16.

[0091] Therefore, the session contents display sections 12-1 through 12-n are provided by objects that are generated or extinguished in consonance with the generation and the extinguishing of sessions.

[0092] The session contents display sections 12-1 through 12-n are provided as objects, which are instances of a C++ class and are hereinafter called session objects.

[0093] Since the display condition varies depending on the session type and the information to be managed, and since the procedures that are used also differ, different session objects are introduced in consonance with the session types. For a display, the session contents display section for displaying information concerning a private room session introduces a private room session object; the session contents display section for displaying information concerning a conversation session introduces a conversation session object; and the session contents display section for displaying information concerning a lecture assembly session introduces a lecture assembly session object.

[0094] FIG. 3 is a diagram showing the relationship between information that is managed by the session information management unit 16 and information that is managed by a session object, and that is stored in a RAM (not shown) in the terminal.

[0095] In FIG. 3, information that is managed by the session information management 16 is shown in the form of a table 41. Reference numerals 421 and 422 each denote information that is managed by a session object in a terminal 10.

[0096] The session information management unit 16 manages session identifiers, session types, and information that accompanies the session types.

[0097] The session object is established for each session, and manages information that is managed by the session information management unit 16 and information that is valid only in the terminal 10, such as window identifiers.

[0098] Since information concerning a session must be used in common by all the terminals that display a session list, the terminals hold in their memories session objects that correspond to all of the sessions that are registered in the session information management units 16.

[0099] FIG. 4 is a diagram for explaining the classes that constitute each session object.

[0100] A private session object is an instance of a private room class 52, a conversation session object is an instance of a conversation class 53, and a lecture assembly session object is an instance of a lecture assembly class 54.

[0101] The private room class 52, the conversation class 53, and the lecture class 54 inherit the properties of a session class 51 that possesses attributes that are required for all the classes.

[0102] The session class 51 has as its members a window identifier 513 and a session identifier 514.

[0103] Further, as methods for session objects, the session class 51 includes an object generator 511, an object extinguisher 512, a procedure 515 for adding a person's icon to a display section, and a procedure 516 for deleting a person's icon from a display section.

[0104] Since the procedure 515 for adding a person's icon to a display section and the procedure 516 for deleting a person's icon from a display section differ, depending on the object, the procedures 515 and 516 at the session class 51 are declared as virtual functions.

[0105] The private room session class 52 inherits the session class 51 and includes a private room owner 525 and an owner's status 526 as its members.

[0106] Further, as methods for a private room session object, the private room session class 52 includes an object generator 521, an object extinguisher 522, a procedure 523 for adding a person's icon to a display section, and a procedure 524 for deleting a person's icon from a display section.

[0107] The conversation session class 53 inherits the session class 51 and has as its member a participant list 535.

[0108] Further, as methods for a conversation session object, the conversation session class 53 includes an object generator 531, an object extinguisher 532, a procedure 533 for adding a person's icon to a display section, and a procedure 534 for deleting a person's icon from a display section.

[0109] The lecture session class 54 inherits the session class 51 and has as its members a lecture 545 and an audience list 546.

[0110] Further, as methods for a lecture assembly session object, the lecture session class 54 includes an object generator 541, an object extinguisher 542, a procedure 543 for adding a person's icon to a display section, and a procedure 544 for deleting a person 's icon from a display section.

[0111] Various classes, such as a condition understanding class and a joint design class, can be easily created by inheriting the properties of the session class 51, and various sessions can be easily represented.

[0112] The operation for session objects will now be described while referring to FIGS. 5 through 8.

[0113] The generation of session objects can be performed by the functions of the classes shown in FIG. 4. The individual operations, i.e. the individual functions, will now be described.

[0114] First, the processing for generating a conversation session object will be explained. When a user has instructed the generation of a conversation object, the object generator 531 of the conversation class 53, which is the above described method stored in the RAM, is called. The generation instruction is transmitted as an argument to a session object, and a conversation session object is generated. The generation instructions in this case are a user's instruction designating a session identifier for performing a conversation session and a list of participants.

[0115] FIG. 5 is a flowchart of the processing for the object generator 531 of the conversation session class 53. The session identifier and the participant list are transmitted as arguments to the object generator 531.

[0116] In FIG. 5, first, at step S61 a session identifier that is obtained by the argument is substituted into the member 513 of the session class 51.

[0117] The session generator (method) is processed by a CPU (not shown) in the main body 3. At step S62, the scroll window widget of the session list display panel 31 is employed as a parent window to generate a session contents display window for a conversation session. This session contents display window is a session contents display panel in which is displayed information concerning a conversation session, which was explained previously while referring to FIG. 2.

[0118] At step S63, the identifier for the window that is generated at step S62 is substituted into the member 513 of the session class 51.

[0119] At step S64, a call back function for detecting a drop event for the window that is generated at step S62 is registered by the control unit 15.

[0120] At step S65, a call back function for detecting a drag event for the window that is generated at step S62 is registered by the control unit 15.

[0121] At step S66, the participant list that is obtained by the argument is substituted into the member 535 of the conversation session class 53.

[0122] Finally, at step S67, the window that is generated at step S62 is employed as a parent window for the generation of an icon for a participant, which is then displayed.

[0123] In the following operations, the methods that have been called by a user using the pointing device are processed by a CPU (not shown) in the main body 3, as is described above. Then, the generation of the window and the termination of the window, and the addition and the deletion of a person's icon are performed.

[0124] The processing for the deletion of a conversation session object will now be described.

[0125] The object extinguisher 532 of the conversation session class 53 is called from the previously mentioned RAM in accordance with a D & D instruction of a user to end a conversation session, and a conversation session object is extinguished.

[0126] FIG. 6 is a flowchart of the processing for the object extinguisher 532 of the conversation session class 53.

[0127] In FIG. 6, first, at step S71, the window indicated by the member 513 of the session class 51 is terminated. In other words, the conversation session window that is generated at step S62 is terminated.

[0128] At step S72, a storage area that the object uses is opened and the object itself is extinguished.

[0129] The processing performed when the procedure 533 for adding a person's icon to a display section will now be described.

[0130] FIG. 7 is a flowchart of the procedure 533 for adding a person 's icon to the session content display panel for the conversation session object.

[0131] In FIG. 7, first, at step S81, a participant who is obtained by an argument, which represents a participant designated in accordance with a user's D & D instruction, is added to the conversation session object participant list 535.

[0132] At step S82, the icon for the added participant is generated by employing, as a parent window, the window indicated by the window identifier that is substituted into the session object member 513.

[0133] The processing performed when the procedure 534 for deleting a person's icon from a display section is called will now be explained.

[0134] FIG. 8 is a flowchart of the procedure 534 for deleting a person's icon from the session contents display panel for the conversation session object.

[0135] In FIG. 8, first, at step S91, the participant who is obtained by the argument that is indicated in accordance with a user's D & D instruction, in the same manner as is described above, is deleted from the conversation session object participant list 535.

[0136] At step S92, the icon for the deleted participant is deleted.

[0137] The processing of the call back functions that are registered at steps S64 and S65 in FIG. 5 will now be explained while referring to FIGS. 9 and 10.

[0138] FIG. 9 is a flowchart of the procedures for the call back function that is registered at step S64.

[0139] In FIG. 9, first, at step S101, the procedure 533 for adding a person's icon to the session contents display panel for the conversation session object is called. In other words, the procedures at step S80 and the following steps are performed. At step S102, the information held by the session information management unit 16 is updated.

[0140] FIG. 10 is a flowchart of the procedures for the call back function that is registered at step S65.

[0141] In FIG. 10, first, at step S111, the procedure 534 is called to delete a person's icon from the session contents display panel for the conversation session object. In other words, the procedures at step S90 and the following steps are performed. At step S112, the information held by the session information management unit 16 is updated.

[0142] The processing for generating a lecture assembly session object will now be described.

[0143] When a user has instructed the generation of a lecture assembly session object, the object generator 541 of the lecture session class 54 is called. The generation instruction is provided as an argument to the object generator 541, so that the lecture assembly session object is generated.

[0144] A session identifier, a lecturer, and an audience list are provided as arguments for the object generator 541.

[0145] In the processing for the generation of the lecture assembly session object, the window that is generated at step S62 in the processing for the generation of the conversation session object is replaced with a window for a lecture assembly session. Further, step S66, wherein the participant list is set to the member 535, is replaced with a process whereby the audience list is substituted into the member 546 and the lecturer is substituted into the member 545, and step S67, whereat the participant's icon is generated and displayed, is replaced with a process whereby the icon for the lecturer is generated and displayed in a lecturer display region and the icon for an audience is generated and displayed in an audience display region.

[0146] The processing for the deletion of the lecture assembly session object will now be described.

[0147] The lecture assembly session object is extinguished by calling the object extinguisher 542 of the lecture session class 54 in accordance with a user 's instruction to terminate a lecture assembly session.

[0148] In the processing for extinguishing the lecture assembly session object, the window that is terminated at step S71 in the processing for extinguishing the conversation session object is replaced with a window for a lecture.

[0149] The processing performed when the procedure 543 is called for adding a person's icon to the lecture assembly session object display section will now be explained

[0150] In the procedure 543 for adding a person's icon to the lecture assembly session object, the audience list is set instead of setting the participant list at step S81 of the procedure 533 for adding a person's icon to the conversation session object, and the icon for the audience is displayed in the display region instead of displaying the icon for the participant at step S82.

[0151] The processing performed when the procedure 544 is called for deleting a person's icon from the lecture assembly session object display section will now be explained.

[0152] In the procedure 544 for deleting a person's icon from the lecture assembly session object, a designated audience is deleted from the audience list 546, instead of deleting a participant from the participant list 535 at step S91 of the procedure 534 for deleting the person's icon from the conversation session object.

[0153] In the processing for setting the call back function when the lecture assembly session object is generated, the procedure 533 in the processing for setting the call back function for the conversation session object is replaced with the procedure 543, and the procedure 534 is replaced with the procedure 544.

[0154] The processing for generating a private room session object will now be described.

[0155] When a user has instructed the generation of a private room session object, the object generator 521 of the private room session class 52 is called. The generation instruction is provided as an argument to the object generator 521, so that the private room session object is generated.

[0156] A session identifier and a room owner are provided as arguments for the object generator 521.

[0157] In the processing for generating the private room session object, the window that is generated at step S62 in the processing for generating the conversation session object is replaced with a window for a private room session. Further, step S66 whereat the participant list is set to the member 535 is replaced with a process whereby the owner is substituted into the member 525, and step S67 whereat the participant's icon is generated and displayed is replaced with a process whereby the icon for the room owner is generated and is displayed in a owner display region.

[0158] The processing for deleting the private room session object will now be described.

[0159] The private room session object is extinguished by calling the object extinguisher 522 of the private room session class 52 in accordance with a user's instruction to terminate a private room session.

[0160] In the processing for extinguishing the private room session object, the window that is terminated at step S71 in the processing for extinguishing the conversation session object is replaced with a window for a private room.

[0161] The processing performed when the procedure 523 is called for adding a person's icon to the private room session object display section will now be explained.

[0162] In the procedure 523 for adding a person's icon to the private room session object, the status of the owner is set to present instead of setting the participant list at step S81 of the procedure 533 for adding the person's icon to the conversation session object, and the icon for the owner is displayed in the owner's display region instead of displaying the icon for the participant at step S82.

[0163] The processing performed when the procedure 524 is called for deleting a person's icon from the private room session object display section will now be explained.

[0164] In the procedure 524 for deleting a person's icon from the private room session object, the absence of the owner is set instead of deleting a participant from the participant list 535 at step S91 of the procedure 534 for deleting the person's icon from the conversation session object.

[0165] In the processing for setting the call back function when the private room session object is generated, the procedure 533 in the processing for setting the call back function for the conversation session object is replaced with the procedure 523, and the procedure 534 is replaced with the procedure 524.

[0166] Since only the owner of the private room is allowed to enter the private room, the call back procedure is performed only when the icon that is dropped in the display region for the private room session object belongs to that owner.

[0167] The call back routine of the session operation unit 13 will now be explained while referring to FIGS. 11 through 13.

[0168] FIG. 11 is a flowchart of a call back routine that is begun when the lecture assembly session generation request button 33-1 is depressed by a user using the pointing device.

[0169] In FIG. 11, first, at step S121, the lecture assembly session object is generated. This process corresponds to the calling of the object generator 541 from the lecture class 54. At step S122, the information in the session information management unit 16 is updated.

[0170] FIG. 12 is a flowchart of a call back routine that is begun when the conversation session generation request button 33-2 is depressed by a user using the pointing device.

[0171] In FIG. 12, first, at step S131, the conversation session object is generated. This process corresponds to the calling of the object generator 531 from the conversation class 54. At step S132, the information in the session information management unit 16 is updated.

[0172] FIG. 13 is a flowchart of the call back routine that is begun when the session contents display panel is dropped to the session end region 33-3 by a user using the pointing device.

[0173] In FIG. 13, first, at step S141, the session object is terminated.

[0174] This process corresponds to the calling of the object extinguisher for the class to be terminated. The object extinguisher 532 for the conversation class 53 is called to terminate the conversation session object. The object extinguisher 542 for the lecture class 54 is called to terminate the lecture assembly session object. Then, at step S142, the information held by the session information management unit 16 is updated.

[0175] The session information update detecting unit 14 is provided by the call back routine that is activated when the control unit 15 has detected the session information update event from the session information management unit 16.

[0176] The operation of the session information update detecting unit 14 is as follows.

[0177] In the call back routine for an event that the session has been generated, the session information update detecting unit 14 receives the session identifier, the session type and its attribute as arguments, and generates a session object that corresponds to the session type.

[0178] In the call back routine for an event that the session has been terminated, the session information update detecting unit 14 receives the session identifier as an argument, and terminates the session object that is indicated by the session identifier.

[0179] In the call back routine for an event when a participant is added to a session, the session information update detecting unit 14 receives the session identifier and the added participant as arguments, and adds the participant to the session object that is indicated by the session identifier. This process corresponds to the calling of the procedure for adding a person's icon to the display section of the session object that is designated by the argument.

[0180] In the call back routine for an event where a participant has exited a session, the session information update detecting unit 14 receives, as arguments, the session identifier and the identification for the participant who has exited, and deletes the participant from the session object that is indicated by the session identifier. This process corresponds to the calling of the procedure for deleting a person's icon from the display section of the session object that is designated by the argument.

[0181] The control unit 15 calls the appropriate procedure in response to the event that has occurred, and is set in an event wait loop of the X-Window. The operation of the control unit 15 is as follows.

[0182] When an event that a user has initiated by clicking the pointing device has been detected as an event for the scroll bar 311 of the session list display panel 31, the control unit 15 scrolls the display region of the session list display section 31.

[0183] When an event that a user has initiated by clicking the pointing device has been detected as an event for the session contents display panel 32, the control unit 15 performs the call back routine of the session contents display section 12.

[0184] When an event that a user has initiated by clicking the pointing device has been detected as an event for the session operation panel 33, the control unit 15 performs the call back routine of the session operation unit 13.

[0185] When a message from the session information management unit 16 has been detected, the control unit 15 performs the call back routine of the session information detecting unit 14.

[0186] A second embodiment will now be described.

[0187] In the second embodiment, management of session access and of session privacy in the first embodiment introduced.

[0188] FIG. 14 is a functional block diagram illustrating the components of a session operation apparatus according to the second embodiment.

[0189] In FIG. 14, access level operation units 21-1 through 21-n, which introduce session contents display sections in the first embodiment, display a permission level for participation in a session and set the permission level to participate in a session.

[0190] Privacy level operation units 23-1 through 23-n display a permission level for accessing the status of the situation for a session and sets a permission level for accessing the status of the situation for a session.

[0191] The operations of the individual components in FIG. 14 will now be explained.

[0192] The access level operation units 22-1 through 22-n and the privacy level operation units 23-1 through 23-n are generated when the session contents display sections 21 are generated, and are extinguished when the session contents display sections 21 are extinguished.

[0193] When a control unit 15 has detected input to the access level operation units 22-1 to 22-n, the displays of the access level operation units 22 are updated, and the information held by a session information management unit 16 is updated. When the control unit 15 has detected input to the privacy level operation unit 23-1 to 23-n, the displays of the privacy level operation units 23 are updated, and the information held by a session information management unit 16 is updated.

[0194] User interfaces according to the second embodiment are shown in FIG. 15.

[0195] In FIG. 15, session contents display panels 151, 152, 153, 154 and 155 are user interfaces for the session contents display sections 21.

[0196] The session contents display panel has a window icon and a door icon. The door icon indicates a permission level for participating in a session, and the window icon indicates the access level for obtaining information concerning the statue of the situation in a session. The door icon is an interface for the access level operation unit 22, and the window icon is an interface for the privacy level operation unit 23.

[0197] In the second embodiment, when the window icon is in the open state it indicates that it is possible to obtain knowledge concerning the situation by using audio/video information, and when the window icon is in the closed state it indicates that it is impossible to obtain knowledge concerning the situation by using audio/video information.

[0198] When the door icon is in the open state it indicates that users can participate in a session as desired, and when the door icon is in the closed state it indicates that users can not participate in a session.

[0199] In FIG. 15, the session contents display panel 151 indicates a conversation session, a window icon 1511 indicates that knowledge of the situation in the session can be obtained by using audio/video information, and a door icon 1512 indicates that users can participate in a session as desired.

[0200] The session contents display panel 152 indicates a conversation session, a window icon 1521 indicates that knowledge concerning the situation in the session can not be obtained, and a door icon 1522 indicates that users can not participate in a session.

[0201] The session contents display panel 153 indicates a private room session, a window icon 1531 indicates that knowledge concerning the situation in the private room can be obtained by using audio/video information, and a door icon 1532 indicates that users can participate in a session as desired.

[0202] The session contents display panel 154 indicates a private room session, a window icon 1541 indicates that knowledge concerning the situation in the private room can not be obtained by using audio/video, and a door icon 1542 indicates that users can not freely participate in a session.

[0203] The session contents display panel 155 indicates a private room session, a window icon 1551 indicates that knowledge concerning the situation in the private room can be obtained by using audio/video, and a door icon 1552 indicates that users can not freely participate in a session.

[0204] When more door icons and window icons are provided, access management and privacy management at additional stages can be realized. For example, it is possible to obtain knowledge concerning a situation by using only video or only audio, and to participate in a session only in an emergency.

[0205] In FIG. 16A is shown an example session contents display panel 161.

[0206] In the session contents display panel 161 shown in FIG. 16A, A, B and C are conversing, and a window icon 1611 and a door icon 1612 are open.

[0207] When a user D drops his or her icon into the window icon 1611, by using the previously mentioned pointing device, the user D can directly obtain knowledge concerning the situation in the session. As a result, the display in FIG. 16B is displayed on the session contents display panel 161, with three real time images of A, B and C being displayed in a window icon 1614. Reference numerals 1615, 1616, 1617 and 1618 are camera control interfaces that enable the controls for panning and tilting, brightness, and zooming for a camera, which is connected to a terminal that is designated by an instruction icon 1613. An interface 1619 is employed to instruct an increase and a decrease in the volume for the session. The line connections shown in FIG. 17 are provided, and audio/video output from A, B and C can be acquired. The directions indicated by the arrows represent the directions in which audio/video data are transmitted.

[0208] When the icon of the user D is dropped on the door icon, the user D can participate in the session. In other words, the line conditions shown in FIG. 18 is provided.

[0209] The processing will now be described while referring to FIGS. 19 through 24.

[0210] Just as in the case of the session contents display sections 12 in the first embodiment, the session contents display section 21 in this embodiment are realized as instances of classes that are consonant with session types, i.e., as objects.

[0211] FIG. 19 is a diagram for explaining classes that constitute session objects in this embodiment.

[0212] In addition to the session objects for the first embodiment, the session objects in this embodiment further include a procedure 1917 for setting the state of a door, a procedure 1918 for setting the state of a window, a session door state 1919, a session window state 1920, a window identifier 1921 for a window icon, and a window identifier 1922 for a door icon.

[0213] The access level operation unit 22 and the privacy level operation unit 23 are realized by employing information that is managed by the session object and the procedure for the session object.

[0214] That is, the access level operation unit 22 is constituted by the procedure 1917 for setting the state of a door, the session door state 1919, and the window identifier 1922. The privacy level operation unit 23 is constituted by the procedure 1918 for setting the state of a door, the session window state 1920, and the window identifier 1921.

[0215] When a user employs the pointing device to instruct the generation of a conversation session, a generator 1931 for a conversation session object is called and a conversation session object is generated. While the conversation session window is generated at step S62 in the processing for the first embodiment for generating the conversation session object, according to the processing of the conversation session object generator 1931, a window icon for displaying the session privacy set state is generated and its window identifier is substituted into a member 1921; a window for displaying information about the conversation session is generated by using the window icon as a parent and its window identifier is substituted into a member 513; and a door icon for displaying the access set state is generated and its window identifier is substituted into a member 1922. Further, while the call back function is registered at steps S64 and S65 during the generation of the conversation session object, a call back function for detecting an event at a window icon and a call back function for detecting an event at a door icon are registered.

[0216] When a user employs the pointing device to instruct the termination of a conversation session, a conversation session object extinguisher 1932 is called and the conversation session object is extinguished. While the window indicated by the session class member 513 is terminated at step S71 in the processing for the first embodiment for extinguishing the conversation session object, additionally, in the processing for the conversation session object extinguisher 1932, the window that represents the privacy set state indicated by the member 1921 and the window that represents the access set state indicated by the member 1922 are terminated.

[0217] For the conversation session object, a procedure 1933 for adding a person's icon and a procedure 1934 for deleting a person's icon are the same as the procedures 533 and 534 in the first embodiment.

[0218] When a user employs the pointing device to instruct the generation of a lecture assembly session, a generator 1941 for a lecture assembly session object is called and a lecture assembly session object is generated. While the lecture assembly session window is generated in the processing for the first embodiment for generating the lecture assembly session object, according to the processing for the lecture assembly session object generator 1941, a window icon for displaying the session privacy set state is generated and its window identifier is substituted into a member 1921; a window for displaying information about the lecture assembly session is generated by using the window icon as a parent and its window identifier is substituted into a member 513; and a door icon for displaying the access set state is generated and its window identifier is substituted into a member 1922. Further, while the call back function is registered at steps S64 and S65 during the generation of the lecture assembly session object, a call back function for detecting an event at a window icon and a call back function for detecting an event at a door icon are registered.

[0219] When a user employs the pointing device to instruct the termination of a lecture assembly session, a lecture assembly session object extinguisher 1942 is called and the lecture assembly session object is extinguished. While the window indicated by the session class member 513 is terminated in the processing for the first embodiment for extinguishing the lecture assembly session object, additionally, in the processing for the lecture assembly session object extinguisher 1942, the window that represents the privacy set state indicated by the member 1921 and the window that represents the access set state indicated by the member 1922 are terminated.

[0220] For the lecture assembly session object, a procedure 1943 for adding a person's icon and a procedure 1944 for deleting a person's icon are the same as the procedures 543 and 544 in the first embodiment.

[0221] When a user employs the pointing device to instruct the generation of a private room session, a generator 1921 for a private room session object is called and a private room session object is generated. While the private room session window is generated in the processing for the first embodiment for generating the private room session object, according to the processing for the private room session object generator 1921, a window icon for displaying the session privacy set state is generated and its window identifier is substituted into a member 1921; a window for displaying information about the private room session is generated by using the window icon as a parent and its window identifier is substituted into a member 513; and a door icon for displaying the access set state is generated and its window identifier is substituted into a member 1922. Further, while the call back function is registered at steps S64 and S65 during the generation of the private room session object, a call back function for detecting an event at a window icon and a call back function for detecting an event at a door icon are registered.

[0222] When a user employs the pointing device to instruct the termination of a private room session, a private room session object extinguisher 1922 is called and the private room session object is extinguished. While the window indicated by the session class member 513 is terminated at step S71 in the processing for the first embodiment for extinguishing the private room session object, additionally, in the processing for the private room session object extinguisher 1922, the window that represents the privacy set state indicated by the member 1921 and the window that represents the access set state indicated by the member 1922 are terminated.

[0223] For the private room session object, a procedure 1923 for adding a person's icon and a procedure 1924 for deleting a person 's icon are the same as the procedures 523 and 524 in the first embodiment.

[0224] The call back function that is to be registered when the conversation session object is generated will now be explained.

[0225] FIG. 20 is a call back routine that is activated when a drag event at the window icon of the conversation session object is detected.

[0226] In FIG. 20, at step S201, the procedure 1934 is called for deleting the icon for a participant from the window.

[0227] FIG. 21 is a call back routine that is activated when a drop event at the window icon of the conversation session object is detected.

[0228] At step S211, a check is performed to determine whether or not the window is open. When the window is open, at step S212 the procedure 1933 is called for adding a person's icon to the display section of the conversation session object. At step S213, the information held by the session information management unit 16 is updated (knowledge concerning the situation is available).

[0229] When the window is not opened, at step S214, the icon that is dropped is not accepted and is returned to the original window (a request for knowledge concerning the situation is rejected).

[0230] FIG. 22 is a call back routine that is activated when a mouse input event at a window icon is detected.

[0231] First, at step S221, a check is performed to determine whether or not a user is himself present at the session. When the user is present, at step S222, the privacy setting information 1920 is updated. At step S223, the procedure 1918 is called and the display state of the window icon is changed. In other words, the open and closed states of the window are cyclically switched. At step S224, the information held by the session information management unit 16 is updated.

[0232] When the user is not present at the session, he or she terminates the procedure without performing further processing (no change occurs).

[0233] FIG. 23 is a call back routine that is activated when the drop event at a door icon is detected. It should be noted that, since a person's icon is not included in the door icon, the call back function for the drag event is not registered. First, at step S231 a check is performed to determine whether or not the door is open. When the door is open (a user can participate in the session), at step S232 the procedure 1933 is called for adding a person's icon to the display section for the conversation session object. At step S233, the information held by the session information management unit 16 is updated.

[0234] When the door is not open, at step S234 the icon that is dropped is not accepted and is returned to its original window (no change occurs).

[0235] FIG. 24 is a call back routine that is activated when a mouse input event at a door icon is detected.

[0236] First, at step S241, a check is performed to determine whether or not a user is himself present at the session. When the user is present, at step S242, the access setting information 1919 is updated. At step S243, the procedure 1917 is called and the display state of the door icon is changed. In other words, the open and closed states of the door are cyclically switched. At step S244, the information held by the session information management unit 16 is updated.

[0237] When the user is not present at the session, he or she terminates the procedure without performing any further processing (no change occurs).

[0238] For a call back function that is to be registered when a lecture assembly session object is generated, the procedure 1943 is called for adding a participant and the procedure 1944 is called for extinguishing the participant, instead of the respective procedures 1933 and 1934, for the call back function that is to be registered when the conversation session object is generated.

[0239] For a call back function that is to be registered when a private room session object is generated, the procedure 1923 is called for adding a participant and the procedure 1924 for extinguishing the participant, instead of the respective procedures 1933 and 1934, for the call back function that is to be registered when the conversation session object is generated.

[0240] In addition to the operation of the session information update detecting unit 14 in the first embodiment, a session information update detecting unit 14 in this embodiment performs a call back routine for accepting a session access information update event and a call back routine for accepting a session privacy information update event.

[0241] In the call back routine for accepting an access information update event, the access setting information 1919 for a session object that is indicated by a session identifier is set in order to update the access level for the selected session object, and the procedure 1917 for the access level operation unit in the object is called in order to update the display of the door icon.

[0242] In the call back routine for accepting a privacy information update event, the access setting information 1920 for a session object that is indicated by a session identifier is set in order to update the privacy level for the selected session object, and the procedure 1918 for the privacy level operation unit in the object is called in order to update the display of the door icon.

[0243] The control unit 15 performs event processing concerning the access management and the privacy management in addition to the operations performed by the control unit 15 in the first embodiment.

[0244] The operation of the session information management unit 16 is expanded to enable it to handle privacy management information and access management information, in addition to the operations performed by the session information management unit 16 in the first embodiment.

[0245] As is described above in the first and the second embodiments, various cooperating task performance systems can be handled by identical interfaces, and shifting between a plurality of cooperative tasks can be smoothly performed.

[0246] Since the access management procedure and the privacy management procedure are independently provided, the permission level for participating in a session and the permission level for obtaining knowledge concerning the situation in a session can be set for each session. A third party can obtain knowledge concerning the situation in a session without participating in the session.

[0247] FIG. 25 is a block diagram illustrating a third embodiment of the present invention. A video conference is employed as one example session for the third embodiment.

[0248] In FIG. 25, a conference terminal 2501 is a communication device that is used for participation in a video conference. In the conference terminal 2501 are included an accepting means 2502, for receiving a request to participate in or to exit from a conference and for determining whether to approve or to reject the request; certifying means 2503, for certifying a requesting person and for notifying it of the decision by the accepting means 2502; permission setting means 2504, for, in consonance with the decision by the accepting means 2502, setting permission for a requesting person to externally operate a window server 2506; permission cancel means 2505, for, in consonance with the decision by the accepting means 2502, canceling the permission to externally operate the window server 2506 by a participant who requested permission to exit from a conference; and the window server 2506 for performing input/output operations, such as displaying data.

[0249] A conference server 2507 manages information concerning the names of participants in a conference and the name of a terminal host performing the task. Reference numeral 2508 denotes a display device and 2509 denotes an input device, such as a mouse or a keyboard, that a user manipulates.

[0250] The conference terminal 2501 accepts an external request for participating in a conference at the accepting means 2502, certifies the request transmitter by using the certifying means 2503, and determines whether the request should be approved or rejected. When the request is permitted, the permission setting means 2504 refers to the conference server 2507 as needed and sets the appropriate permission for external operation in the window server 2506.

[0251] Also, in the conference terminal 2501, the accepting means 2502 accepts a request from a participant to exit from the conference, and refers to the conference server 2507 as needed, and the permission cancel means 2505 refers to the conference server 2507 and sets, in the window server 2506, cancellation of the permission for an external operation.

[0252] FIG. 26 is a flowchart of the participation request processing for a video conference system.

[0253] In FIG. 26, S2601 is an acceptance request step for accepting a request from an external participant; S2602 is a certifying step for certifying a requesting person; S2603 is a decision step for checking whether or not the certification is performed correctly; S2604 is an automatic decision step for automatically determining whether to approve or reject the participation request based on participation permission list information that is set in advance by a user; S2605 is a decision step for determining whether or not a user should make a decision; S2606 is a user decision step for querying a user concerning the decision to approve or to reject a participation request from a person that is not included in the participation permission list; S2607 is a decision step for checking the decision made by a user; S2608 is a permission setting step for setting permission for an external operation in the window server 2606; and S2609 is a permission message transmission step for transmitting a message for participation permission to the requesting person; S2610 is a rejection message transmission step for transmitting a message for participation rejection to the requesting person.

[0254] The processing will now be described while referring to the flowchart in FIG. 26.

[0255] The operation of the system in this embodiment will be described for two situations: where when the user of the terminal is participating in a conference, a request to participate in the conference is received from another user; and where while the user of the terminal is not participating in a conference, a request to participate in the conference is received from another user.

[0256] At step S2601, a participation request is accepted from the outside by the accepting means 2502. At step S2602, the accepting means 2502 employs the certifying means 2503 to certify the person who submitted the request. If, at step S2603, the requesting person can not be certified, program control advances to rejection message transmission step S2610. When the requesting person is correctly certified, at step S2604, approval or rejection of the participation request is automatically determined. At this time, the accepting means 2502 refers to a specific file that is set in advance by the user that owns the terminal, and when the name of the requesting person is found in this file, the accepting means 2502 automatically approves the participation request. When, at step S2605, the request is approved, program control advances to permission setting step S2608.

[0257] When the determination for the requesting person can not be automatically performed, program control goes to user decision step S2606. At step S2606, a panel for requesting a decision by a user is opened on a screen of the display panel 2508, and approval or rejection of the request is determined based on the input by the user using the input device 2509. When, at step S2607, the user decides to approve the request, program control moves to permission setting step S2608. When the user decides to reject the request, program control goes to rejection message transmission step S2610.

[0258] At permission setting step S2608, when the user of the terminal is already participating in the conference, the accepting means 2502 instructs the conference server 2507 and the permission setting means 2504 to add the person who requested permission to participate in the conference. When the user of the terminal is not participating in the conference, the accepting means 2502 instructs the permission setting means 2504 to add all the conference members so that it can communicate with the members that are participating in the conference. The permission setting means 2504 instructs the window server 2506 to add a designated person or member as a person for whom the screen operation is permitted.

[0259] When the addition of all the members at the conference is instructed or when the host name of the target person is required for the following process, the permission setting means 2504 queries the conference server 2507 to obtain necessary information. The conference server 2507 is provided by a client/server system that has recently been commonly employed, and the permission setting means 2504 performs communication with the conference server 2507 by using a client function.

[0260] At step S2609, a message that the request has been approved is transmitted to the requesting person, and thereafter the participation request processing is terminated.

[0261] When the request for permission to participate is rejected, at rejection message transmission step S2610, a message that the request has been rejected is transmitted to the person requesting participation permission, and thereafter the participation request processing is terminated.

[0262] As for the contents of the communication passed from the permission setting means 2504 to the window server 2506, assuming that the window server 2506 is the X-Window Server that is often used in this field (UNIX), the commands that are associated with the X-Window System are employed and the person who is added and for whom the screen operation is permitted is represented by

[0263] xhost hostname

[0264] or

[0265] xhost username@domain,

[0266] where hostname denotes the host name of the terminal of a target person, and username@domain denotes the name of the target user and the name of the domain in which the user is managed.

[0267] The certifying means 2503 performs the certifying step S2602 by using public key encryption, for which a digital signature method is employed that is known in this technical field. With this method, a combination of a personal secret key and a public key is generated by a key server, and a transmitter transmits a message that is enciphered by using a secret key. On the reception side, the message is deciphered by using the public key of the transmitter and it is confirmed that the received message is the one output by the transmitter. A detailed description of this process can be found in “Trends in Enciphering Techniques and Security”, Information Processing, Vol. 30, No. 8, pp. 892-901, or the like.

[0268] FIGS. 27A and 27B are diagrams showing panels that are opened on the screen of the display device 2508 at user decision step S2606. In FIG. 27A is shown a panel that is opened when the user of a terminal is participating in a conference, and in FIG. 27B is shown a panel for the other cases. Reference numerals 2701 through 2704 denote buttons that are displayed on the panel.

[0269] FIG. 28 is a flowchart of the detailed processing performed at the user decision step S2606.

[0270] At step S2801, when the user of a terminal is participating in a conference and a determination is to be made concerning a participation request by another member, the panel in FIG. 27B is opened. When whether or not the user of a terminal should be permitted to participate in the conference is to be determined as the result of a request submitted by another user, the panel in FIG. 27A is opened. In either case, the user is required effect the selection by depressing a button. When a participation button 2701 or a participation permission button 2703 is depressed, program control branches at step S2802 and moves to a participation permission process at step S2806. At step S2806, it is determined that the decision is made as participation is permitted and thereafter the processing is terminated. When a non-participation button 2702 or a participation rejection button 2704 is depressed, program control branches at step S2803 and moves to a participation rejection process at step S2805. At step S2805 it is determined that the participation request is rejected and thereafter the processing is terminated. When, at step S2804, no button is depressed within a set period of time, it is ascertained that the time allotted for a decision has expired, and at step S2805, it is determined that the participation request is rejected, and the processing is thereafter terminated.

[0271] The processing performed when a request for participation in the conference is submitted is as is described above.

[0272] FIG. 29 is a flowchart of the processing for a request to exit from a conference. Step S2901 is a step for accepting a request to exit a conference; step S2902 is a step for canceling permission to perform screen operations; and step S2903 is a step for transmitting an exit acceptance message.

[0273] When a participant exits a conference while it is in session or when the conference is terminated, an exit request is transmitted to individual terminals by appropriate means (not shown). In the conference terminal 2501, the accepting means receives an exit request from a participant, and at step S2902, the permission cancel means 2505 sets to the window server 2506 the cancel of permission of external operation to a person who requests the exit of the conference. When the host name of a target person is required, the permission cancel means 2505 inquires of the conference server 2507 to obtain necessary information.

[0274] After the permission is canceled at step S2902, at step S2903 an exit acceptance message is returned to the transmission source of the exit request. The processing is thereafter terminated.

[0275] Assuming that the window server 2506 is the X-Window Server that is often used in this field (UNIX), the commands that are associated with the X-Window System are employed and the person for whom permission for screen operations is canceled is represented by

[0276] xhost-hostname

[0277] or

[0278] xhost-username@domain;

[0279] where hostname denotes the host name of the terminal of a target person, and username @ domain denotes the name of the target user and the name of the domain in which the user is managed.

[0280] FIG. 30 is a block diagram illustrating a fourth embodiment of the present invention.

[0281] Although the third embodiment provides a security mechanism for the window server 2506 for display operations, this embodiment provides a security mechanism for a shared file server.

[0282] In FIG. 30, in a conference terminal 3001 that participates in a video conference are included accepting means 3002, for receiving and processing a request to participate in a conference and a request to exit from a conference; certifying means 3003, for certifying a requesting person; permission setting means 3004, for setting permission for external operation of the shared file server 3006 by the requesting person; and permission cancel means 3005, for canceling permission for external operation of the shared file server 3006 by the person submitting an exit request; the shared file server 3006 for performing input/output and transmission/reception of a data file; a conference server 3007 for managing information concerning conference participants and the host name of a terminal performing the task; and 3008, a file that is used by the shared file server 3006.

[0283] The processing will now be described.

[0284] In the conference terminal 3001, the accepting means 3002 receives an external request for permission to participate in a conference, and the certifying means 3003 certifies the requesting person to determine whether the request should be approved or rejected. When the request is approved, the permission setting means 3004 refers to the conference server 3007 as needed, and sets, at the shared file server 3006, permission for the requesting person to perform appropriate external operations.

[0285] Further, in the conference terminal 3001, the accepting means 3002 receives an exit request from a conference participant. The permission cancel means 3005 refers to the conference server 3007 as needed and sets, in the shared file server 3006, cancellation of the exit requesting person's permission to perform external operations.

[0286] When a conference participant exits which a conference is in session, or when the conference is terminated, an exit request is transmitted to individual terminals by appropriate means (not shown). Then, in the conference terminal 3001, the accepting means 3002 receives an exit request from a conference participant, and the permission cancel means 3005 sets, in the shared file server 3006, cancellation of the permission for the exit request transmitter to perform external operations. When the host name of the target person is required, the permission cancel means 3005 queries the conference server 3007 to obtain the necessary information. Thereafter, the exit acceptance message is returned to the exit requesting person and the processing is terminated.

[0287] The actual method for setting and canceling the permission for accessing the shared file server 3006 is effected by transmitting an appropriate command in accordance with the individual shared file installation methods.

[0288] For example, for an addition setup,

[0289] add user username@domain [usergroup],

[0290] and for a deletion and a cancellation,

[0291] del user username@domain [usergroup],

[0292] where usergroup can be omitted. When designated, a user in usergroup who is designated by username@domain can access a file for which accessing is enabled. Further, the usergroup can be so set that it is effective during the conference session.

[0293] With this arrangement, a conference participant can not only access the shared file server 3006 for a display, but can also easily share and access file information that is shared in a conference, and the file information can be securely protected from access by a person who is not participating in the conference.

[0294] According to the third and the fourth embodiments, provided is a communication device that is a conference terminal, in a video conference system, that can securely protect participants by using a server program and by performing secure communication.

[0295] A fifth embodiment will now be described.

[0296] In the third and the fourth embodiments, the determination performed by the accepting means 2502 for the approval or the rejection of a participation request is, depending on the situation, excessively complicated, or there may be no degree of freedom provided when a required setup is established. Very commonly, permission to participate is, for example, required for an extremely many large number of persons. In such as case, it is difficult for all the participants to be selected in advance. It may be more practical for a kind of black list to be prepared, listing the persons that may illegally attempt to use the service, and for special determination means is to be used to examine these persons.

[0297] In this embodiment, therefore, a user can set various determination means for permitting or rejecting requests to participate.

[0298] FIG. 31 is a flowchart of the processing for requesting permission to participate in the activities of a communication system when it is functioning as a video conference system. The structure of the system is the same as that shown in FIG. 25.

[0299] In FIG. 31, S3101 is an acceptance request step for accepting an externally submitted participation request; S3102 is a certifying step for certifying a requesting person; S3103 is a decision step for checking to see whether or not the certification is performed correctly; S3104 is an automatic rejection decision step for automatically deciding to reject the participation request based on first information that is set in advance by a user; S3105 is a decision step for determining whether or not automatic rejection of the request is appropriate; S3106 is an automatic permission decision step for automatically determining whether the participation request should be approved based on second information that is set in advance by a user; S3107 is a decision step for determining whether or not automatic approval of the request is appropriate; S3108 is a decision step for determining whether or not a user should make a decision; S3109 is a user decision step for querying a user concerning whether a participation request should be approved or rejected; S3110 is a decision step for determining whether or not the participation request is approved by the user; S3111 is a permission setting step for setting the window server to provide permission for external operations, and transmitting a message to the requesting person that the participation permission has been granted; and S3112 is a participation rejection step for performing participation request rejection processing, such as transmitting a message to the requesting person that the participation permission has not been granted.

[0300] S3113 is a decision step for determining whether or not a confirmation process for a user has been performed when the request is rejected as the result of the automatic decision process; S3114 is a user decision step for acquiring a user's confirmation for the requesting person whose request has been automatically rejected; S3115 is a decision step for determining whether or not the request is approved; S3116 is a decision step for determining whether or not a confirmation process by a user should be performed when the request is approved as a result of the automatic decision process; S3117 is a user decision step for acquiring a user's confirmation for the requesting person whose request has been automatically approved; and S3118 is a decision step for determining whether or not the request has been approved.

[0301] The processing will now be explained while referring to the flowchart in FIG. 31.

[0302] At step S3101, an external participation request is accepted by accepting means 2502. At step S3102, the accepting means 2502 employs certifying means 2503 to certify a person who submitted the request. If, at step S3003, the requesting person can not be certified, program control advances to participation rejection step S3112. When the request transmitter is certified correctly, at step S3104, automatic determination of whether the request should be rejected is performed. At this time, the accepting means 2502 refers to a first file that a user has set in advance, and when the name of the requesting person is listed in this file, the , accepting means 2502 automatically rejects the participation. When, at step S3105, the participation is rejected, program control advances to decision step S3113. At step S3113, data that designate the necessity for performing confirmation processing relative to the automatic rejection are employed to determine whether or not the confirmation processing is required. When the confirmation processing is required, program control moves to user decision step S3114. When the confirmation processing is not required, program control moves to request rejection step S3112. At user decision step S3114, the name of the requesting person and the fact that the request has been automatically rejected are displayed for the user and the user is requested to confirm the rejection. When, at step S3115, the rejection is confirmed, program control goes to request rejection step S3112. When the rejection is not confirmed, program control goes to request permission step S3111.

[0303] When, at step S3105, the result of the determination is that the participation request is not rejected, at step S3106, the participation request is automatically approved. In this case, the accepting means 2502 refers to a second file that the user of the terminal 2501 has set in advance. When the name of the requesting person is listed in this file, the participation request is automatically approved. When, at step S3107, the result of the determination is that the participation request is approved, program control goes to step S3116. At step S3116, data that are used to determine whether confirmation of the automatic decision to grant permission are employed to determine whether or not confirmation of the decision is required. When confirmation is required, program control moves to user decision step S3117. When confirmation is not required, program control moves to request permission step S3111. At user decision step S3117, the name of the requesting person and the fact that the request was automatically approved are displayed for the user and the user is requested to confirm the decision. When, at step S3118, the decision is confirmed, program control goes to request permission step S3111. When the decision is not confirmed, program control goes to request rejection step S3112.

[0304] If, at step S3107, automatic determination can not be performed, at step S3108 data that are used to determine whether the user should make a determination are referred to, and it is decided whether or not the user should make a determination. When the user is not requested to make a determination, program control moves to request rejection step S3112. When it is decided that the user should make a determination, program control goes to user decision step S3109. At step S3109, the panel for requesting a user to make a determination is displayed on a terminal screen, and approval or rejection is determined based on the input by the user. If, at step S3110, the result of the determination that the request for participation is approved, program control goes to step S3111. When the result of the determination is that the request for participation is rejected, program control goes to request rejection step S3112.

[0305] At request permission step S3111, when the user of the terminal 2501 is already participating in the conference, the accepting means 2502 instructs conference server 2507 and permission setting means 2504 to add the person who requested permission to participate in the conference. When the user of the terminal 2501 is not participating in the conference, the accepting means 2502 instructs the permission setting means 2504 to add all the conference members. The permission setting means 2504 instructs the window server 2506 to add a designated person or member as a person for whom the screen operation is permitted. Then, a participation permission message is transmitted to the requesting person, and the participation requesting processing is thereafter terminated. When the participation request is rejected, at request rejection step S3112, a message that the request was rejected is transmitted to the requesting person and the participation request processing is terminated.

[0306] It should be noted that AnyPerson, which means all the members, can be designated in the first and the second files that are used for automatic determination.

[0307] Through this processing, the automatic rejection, the automatic approval, and confirmation procedures for them can be flexibly set. For example, when the first file for automatic rejection is blank, and when the user decision at step S3108 is not required and confirmation at step S3116 is required, members described only in the second file are accessed, and the user confirmation can be performed at the time of accessing. If, in this case, AnyPerson is designated in the second file, the application condition for the common service that can be applied for anybody can be monitored.

[0308] On the other hand, when the second file for automatic permission is AnyPerson, and when the user decision at step S3116 is required and the confirmation at step S3113 is required, the rejection of requests for access by the members described in the first file can be confirmed. In this case, the first file can function as a black list and only the accessing by persons on which special restrictions have been placed can be monitored.

[0309] Therefore, according to the embodiments, provided is not only a service that users of a communication system, such as conference participants, can easily acquire by using a conventional server, and that can be securely protected from being accessed by a third person, but also flexible user management can be performed by setting up procedures for performing automatic rejections and automatic approvals, and by providing procedures for obtaining user's confirmations and user's decisions.

[0310] In the third through the fifth embodiments, the present invention is applied to a video conference system. However, the present invention is not limited to this system, and it can be applied in a case where a predetermined terminal controls access for a plurality of terminals connected to a network.

[0311] As is described above, provided is a service that users of a communication system, such as conference participants, can easily acquire by using a conventional server, and that can be securely protected from being accessed by a third person.

[0312] In addition, flexible user management can be performed by setting up procedures for performing automatic rejections and automatic approvals and by providing procedures for obtaining user's confirmations and user's decisions. Further, by using the window server or the file server, an access by a conference participant of a screen display or of an input/output file can be permitted while maintaining adequate security.

[0313] The above described embodiments may be applied to a system that is constituted by a plurality of devices, or to an apparatus that is constituted by a single device.

[0314] Included in the scope of the above described embodiments is included a processing method for storing a program, on a storage medium, that can operate the structures in the aforementioned embodiments to perform the functions of the embodiments, and for carrying out the embodiments according to the program that is stored on the storage medium. Further, the storage medium on which the program is stored is also included in the above embodiments.

[0315] Such a storage medium can be a floppy disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a magnetic tape, a nonvolatile memory card, or a ROM.

[0316] In addition, the processing method is not limited to the one in accordance with which a process is performed by a single program that is stored on a storage medium, for included within the scope of the above embodiment is a processing method that provides for the operation of a program on an OS that can, in cooperation with the functions of other software or of an expansion board, carry out the provisions of the above described embodiment.