Abstract:
A graphical user interface, i.e., multimedia communications application program, for setting up and handling a multimedia call is disclosed that employs realistic metaphors of real life face-to-meetings in setting up and handling a multimedia call to establish a virtual meeting which is automatically reconfigured in response to user action. This is realized by taking advantage of prospective virtual meeting participants&#39; already existing knowledge of how real life face-to-face meetings operate. To this end, the multimedia communications application program enables the virtual meeting participants through direct manipulation of the realistic graphical metaphors to establish a realistic virtual meeting room which is displayed on the screen of their workstation monitor. The virtual meeting room includes a table and chairs arranged in a realistic manner in the virtual meeting room. The virtual meeting room and table are automatically configured in response to user action in such a manner as to minimize the screen area displaying the virtual meeting room and, thereby, maximizing the screen area available for multimedia collaboration by the meeting participants. An empty chair is displayed at the table which indicates that at least one more participant can be added to the virtual meeting. Once a predetermined maximum number of participants have been included in the virtual meeting, the empty chair is no longer displayed.

Description:
CROSS-REFERENCE TO RELATED APPLICATION 
     This application is related to U.S. patent application Ser. No. 08/357,809 and U.S. patent application Ser. No. 08/358,214 which were filed concurrently herewith. 
     TECHNICAL FIELD 
     This invention relates to telecommunications networks and, more particularly, to multimedia communications networks for providing flexible multimedia telephone service and the like including video, voice and/or data. 
     BACKGROUND OF THE INVENTION 
     The essential characteristics of face-to-face meetings can be simulated by multimedia telecommunications conference systems. Such conference systems permit separated meeting participants to communicate with one another in multiple media such as video voice and/or data from their own workplace without requiring that they convene in the same place. 
     In prior known multimedia conference systems, it has been required that the individual meeting participants had to be conversant with sophisticated video and data communications protocols, including, for example network address and transport protocols, in order to set-up and handle a multimedia call in order to establish and operate a virtual meeting. If a prospective participant was not familiar with the video and/or data protocols, it essentially precluded his or her participation in the full virtual meeting. Those prospective participants would be limited to only the audio portion of the virtual meeting. This of course is extremely undesirable. Therefore, a problem exists in providing an easy natural real life way for unsophisticated prospective meeting participants to set-up and handle multimedia telephone calls. 
     SUMMARY OF THE INVENTION 
     The problems and limitations with prior multimedia telecommunications conference systems are overcome by utilizing a graphical user interface (multimedia communications application program) that employs realistic metaphors of real life face-to-face meetings in setting up and handling a multimedia call to establish a virtual meeting which is automatically reconfigured in response to user action. This is realized by taking advantage of prospective virtual meeting participants&#39; already existing knowledge of how real life face-to-face meetings operate. To this end, the multimedia communications application program enables the virtual meeting participants through direct manipulation of the realistic graphical metaphors to establish a realistic virtual meeting room metaphor which is displayed on the screen of their workstation monitor. The virtual meeting room includes a table and chairs arranged in a realistic manner in the meeting room. The virtual meeting room and table are automatically configured in response to user action in such a manner as to minimize the screen area displaying the virtual meeting room and, thereby, maximizing the screen area available for multimedia collaboration by the virtual meeting participants. In one embodiment, an empty chair is displayed at the table which indicates that at least one more participant can be added to the virtual meeting. Once a predetermined maximum number of participants have been included in the virtual meeting, the empty chair is no longer displayed. In a specific example, the multimedia call is established by use of a realistic telephone icon that looks and operates like an ordinary real life telephone. 
    
    
     BRIEF DESCRIPTION OF DRAWING 
     FIG. 1 is an example of a multimedia telecommunications system in which the invention may be employed; 
     FIG. 2 shows, in simplified block diagram form, the relationships between the multimedia communications application program (hereinafter multimedia application), middleware and the communications network; 
     FIG. 3 shows, in simplified block diagram form, details of a workstation which may be employed in practicing the invention; 
     FIG. 4 is a graphical screen representation of the realistic graphical meeting room metaphor; 
     FIG. 5 is a graphical screen representation with the multimedia application minimized; 
     FIG. 6 is a flow chart illustrating the steps a user performs in starting the multimedia application in the initiation of a multimedia telephone call; 
     FIG. 7 is a graphical screen representation which is displayed upon a user starting the multimedia application in the initiation of the multimedia telephone call; 
     FIG. 8 is a flow chart illustrating the steps that the user would perform in selecting a telephone to initiate a multimedia call; 
     FIG. 9 is a graphical screen representation of the call bar that appears when the telephone is selected to initiate the multimedia call; 
     FIG. 10 is a flow chart illustrating the steps in placing a multimedia call from the directory shown in FIG. 11; 
     FIG. 11 is a graphical screen representation of a directory; 
     FIG. 12 is a graphical screen representation of a multimedia call initiated from an entry in the directory; 
     FIG. 13 is a flow chart illustrating the steps taken in effecting a multimedia call directly from the call bar; 
     FIG. 14 is a graphical screen representation illustrating a phone number being entered directly from the keyboard of the user workstation; 
     FIG. 15 is a graphical screen representation illustrating ringing at a remote participant&#39;s phone number that is being displayed; 
     FIG. 16 is a flow chart illustrating the steps taken in effecting a multimedia call from a dial pad; 
     FIG. 17 is a graphical screen representation illustrating the appearance of the dial pad below the call bar; 
     FIG. 18 is a graphical screen representation illustrating a phone number entered on the dial pad; 
     FIG. 19 is a graphical screen representation illustrating ringing at a remote participant&#39;s phone number that is being displayed; 
     FIG. 20 is a flow chart illustrating the steps taken once the call is placed; 
     FIG. 21 is a graphical screen representation illustrating the meeting upon a remote participant answering the call; 
     FIG. 22 is a flow chart illustrating the steps which are taken upon receipt of an incoming call at a user workstation; 
     FIG. 23 is a graphical screen representation illustrating the name and phone number of the calling party; 
     FIG. 24 is a graphical screen representation illustrating the meeting room upon the called party answering the incoming call; 
     FIG. 25 is a flow chart illustrating the steps taken in adding a participant to an ongoing meeting. 
     FIG. 26 is a graphical screen representation illustrating an ongoing meeting with three participants; 
     FIG. 27 is a graphical screen representation illustrating an ongoing meeting with four participants; 
     FIG. 28 is a graphical screen representation illustrating the addition of a participant to the meeting shown on the screen of FIG. 26; 
     FIG. 29 is a graphical screen representation illustrating the addition of a participant to the meeting shown on the screen of FIG. 27; 
     FIG. 30 is a graphical screen representation illustrating the addition of an empty chair to the meeting shown in the screen of FIG. 28; 
     FIG. 31 is a graphical screen representation illustrating expansion of the meeting room from the meeting shown in the screen of FIG. 29; 
     FIG. 32 is a graphical screen representation illustrating the addition of an empty chair to the meeting shown in the screen of FIG. 31; 
     FIG. 33 is a flow chart illustrating the steps taken when a meeting participant permanently leaves the meeting room; 
     FIG. 34 is a graphical screen representation of an ongoing meeting including six participants; 
     FIG. 35 is a graphical screen representation of the meeting shown in the screen of FIG. 34 upon a participant leaving that meeting; 
     FIG. 36 is a graphical screen representation of the meeting shown in the screen of FIG. 35 with the chairs rearranged; 
     FIG. 37 is a graphical screen representation of the meeting with the participants rearranged around the table to fill in empty chairs; 
     FIG. 38 is a graphical screen representation of the meeting shown in the screen of FIG. 37 with the extra empty chair being removed; 
     FIG. 39 is a graphical screen representation of an ongoing meeting including five participants; 
     FIG. 40 is a graphical screen representation of the meeting shown in the screen of FIG. 39 upon a participant leaving that meeting; 
     FIG. 41 is a graphical screen representation of the meeting shown in the screen of FIG. 40 with the chairs rearranged; 
     FIG. 42 is a graphical screen representation of the meeting with the participants rearranged around the table to fill in empty chairs; 
     FIG. 43 is a graphical screen representation of the meeting shown in the screen of FIG. 42 with the extra empty chair being removed; 
     FIG. 44 is a graphical screen representation illustrating the shrinking of the size of the meeting room. 
    
    
     DETAILED DESCRIPTION 
     FIG. 1 shows an example of multimedia telecommunications system 100 in which an embodiment of the invention may be readily employed. Individual users at different work locations can set-up a multimedia conference call via a number of different desktop communications devices. As shown, the desktop communications devices may include, but are not limited to, personal computer 101 with built in microphone for audio, workstation 102 including an attached video camera 103 and ISDN telephone 104, workstation 105 with attached video camera 106, personal computer 107 with an integrated video camera 108, workstation 109 including video camera 110 and an analog telephone 111, ISDN telephone 112, facsimile (FAX) machine 113 and, finally, analog telephone 114. It should be noted that personal computer 101 does not provide local user video to the meeting, FAX machine 113 only provides FAX service and ISDN telephone 112 and analog telephone 114 only provide audio access to the meeting. The personal computers and workstations may be any of those known in the art, for example, personal computers and/or workstations commercially available from AT&amp;T Corp., Apple Computer Inc., Sun Microsystems Inc. and others. 
     The several different desktop communications devices are interconnected via communications network 116. Note that workstations 101, 102, 107 and 109, and ISDN telephone 112, facsimile machine 113, and analog telephone 114 are directly connected to communications network 116, while workstation 105 is connected through multimedia server 115 to communications network 116. In this example, communications network 116 could be, for example, a long distance telecommunications network such as a long distance network provided by AT&amp;T. It may be connected to a number of local telephone networks provided by local exchange carriers or alternate access vendors to provide access to the different desktop communications devices. Alternatively, communications network 116 could be a wide band area network, a local area network or the like. Typically, communications network 116 may include the usual public switched long distance network composed of a plurality of well known digital switching units and may contain one or more packet networks. Additionally, communications network 116 may include known video conference bridge arrangements capable of conferencing video, audio and/or data bit streams among the different desktop communication devices. Communications network 116 may also include multimedia multipoint control units (MCUs) that provide multimedia call capability including video, audio and/or data bit streams. Such MCU units are known and are described in Bell Core Generic Requirements GR-1337-CORE, Issue 1, September 1993 and entitled &#34;Multipoint Multimedia Conferencing Control Unit&#34;. Furthermore, communications network 116 may include an asynchronous transport mode (ATM) network capable of transporting and switching multimedia calls including video, audio, and/or data bit streams. 
     As indicated above, workstation 105 is connected via multimedia server 115 to communications network 116. Multimedia server 115 provides for one or more video, one or more audio and one or more data bit streams to be combined, while maintaining the integrity of those bit streams for transmission to communications network 116, for workstation 105 and the other desktop communications devices in a particular meeting including workstation 105. The functionality of multimedia server 115 can be provided for a particular workstation locally, as shown in relationship to workstation 105, and for the other desktop communications devices in a meeting including workstation 105. It is noted that for the other desktop communications devices in a meeting not including workstation 105 and multimedia server 115, communications network 116 must provide the multimedia server functionality for them. 
     Thus, communications network 116, which is not part of this invention, provides the functionality including the multimedia server functionality, when necessary, for interconnecting selected ones of the desktop communications devices in particular virtual meetings, as desired. 
     FIG. 2 illustrates in simplified block diagram from how multimedia application, i.e., the graphical user interface, 201 (201&#39;) located on the user personal computer or workstation communicates via application program interfaces that connect to middleware 202 (202&#39;). Note that the solid lines in FIG. 2 denote direct connectivity between elements 201 through 203 and 203&#39; through 201&#39;, and vice versa, while the dotted lines denote logical connectivity between, for example, elements 201 and 201&#39;, and 202 and 202&#39;. Middleware 202 (202&#39;) is software that is located at the workstation and also distributed among intelligent points in communications network 116. Middleware 202 (202&#39;) serves to isolate the multimedia application from platform differences (e.g., UNIX versus MS-DOS and the like) and communications network 116 details. Middleware 202 (202&#39;) also serves as a link between the workstation application programs, for example, 201, and network transport 203 server functions, as well as, applications that include, but are not limited to, multimedia call connection setup, directory services of people and network resources, information services, messaging services, and the like. When a user places or receives a multimedia call from his or her workstation, the workstation automatically registers its capabilities with middleware 202 (202&#39;). Middleware 202 (202&#39;) employs the registered capabilities to control call setup and transmission of video, audio and/or data. Since, all the capabilities (e.g., full-video, shared data, facsimile, audio and the like) from all of the meeting participants&#39; workstations are registered with middleware 202 (202&#39;), it is available to all of the meeting participants. When information is to be transmitted to participants in the multimedia meeting, middleware 202 (202&#39;) determines the proper display formats and transport protocols. Such middleware is known in the art, see for example, an article entitled &#34;Middleware&#39;s Next Step: Enterprise-Wide Applications&#34;, Data Communications, Sept. 1992, pages 157-164 and an article entitled &#34;Closeup Middleware: Networking&#39;s Silly Putty&#34;, Communications Week, Jun. 20, 1994, pages 48-49. 
     FIG. 3 shows, in simplified block diagram for details of a user&#39;s workstation. Specifically, shown is central processing unit (CPU) 301 which is interconnected via bus 302 to random access memory (RAM) 303, data memory 304, which may be a ROM, and input/output (I/O) unit 305. I/O 305 interfaces pointing device 306, video camera 307, if available, telephone 308, analog or ISDN if available, keyboard 309, and display device 310 to bus 302 and to network interface 311. Such workstations units are known in the art and commercially available, as indicated above, and provide shared data capabilities. Network interface 311 comprises an application program interface that translates computer application requests into the appropriate transport format for transmission via communications network 116 and also takes requests from communications network 116 and translates them into a format appropriate for interacting with the workstation&#39;s applications program. Such arrangements are known in the art. It is further noted that transmission from a user workstation to communications network 116 may be via any of a number of transmission arrangements for example, digital data system (DDS), basic rate interface (BRI) ISDN, primary rate interface (PRI) ISDN, a modem, analog transmission, digital transmission, facsimile transmission, or the like. It is noted that a mouse, track ball, touch screen, keyboard cursor control keys or the like may be employed as a pointing device. 
     FIG. 4 is a graphical screen representation of the real life meeting room metaphor illustrating the various components that could be included in a multimedia meeting. Shown in FIG. 4 is image icon 401, illustrating the image of the originator of the meeting, realistic telephone 402 which is used to place and receive multimedia calls, image icon 403 of a participant in the meeting, empty chair 404 which is available for an additional participant to be included in the meeting, generic image icon 405 which would be employed for a participant whose bit map image is not available, table 406 on which objects can be placed to be shared among the meeting participants, projector 407 which is shown on table 406 and may be utilized to share images among the participants, and view graph folder 408 which contains images that can be placed on the projector 407. Also, shown in FIG. 4 is tool closet 409, which includes the multimedia tools that may be utilized during a multimedia meeting by the participants. Shown in tool closet 409, in this example, are copier 410 which may be utilized by the participants to send computer files from one participant to one or more of the other participants, application sharer (link) 411 which enables the participants to share a computer application program, screen snapshot camera 412 which is used to create a view graph by taking a snapshot of any portion of the monitor screen, call timer 413 which times the length of the multimedia call and can be used to set an alarm, slide projector 414 which is used to display a presentation of a sequence of one or more images to the meeting participants, and FAX machine 415 which is used to send facsimiles to meeting participants and others. The instrumentalities shown in tool closet 409 are by way of example and any other desired multimedia tools may also be included. It is noted that tool closet 409 may be closed to save screen space on the user&#39;s workstation monitor screen. Note that the icons are of realistic real life objects that are or should be well known to the meeting participants. Since, all of the objects are well known as to their nature and use, the meeting participants do not need to know any sophisticated protocols in order to use them. Indeed, the virtual meeting participants use the realistic icons in the same manner as they would their real life counterparts. Additionally, the image icons of the meeting participants are arranged around the table in similar fashion as the participants would be seated in a real life face-to-face meeting. This allows the participants to interact with each other and use the objects in the meeting room based on their already existing knowledge. This, in turn, enhances the ease of use of the graphical user interface of this invention. 
     FIG. 5 is a graphical screen representation with the multimedia application (MMECA) 501 minimized. Also shown are a number of other application programs which have been minimized. Note that the multimedia application of this invention can be implemented on top of a number of known personal computer systems. Examples of such systems programs are the Vistium* personal video system commercially available from AT&amp;T Corp. and the ProShare* personal conferencing system 200 commercially available from Intel Corporation (* note that Vistium is a trademark of AT&amp;T Corp. and that ProShare is a trademark of Intel Corporation). In this example, it is assumed that the personal video system is included as part of the user workstation and provides the network interface 311 (FIG. 3). 
     FIG. 6 is a flow chart illustrating the steps in utilizing the multimedia application for initiating a multimedia telephone call. In step 601, a user initiates a multimedia call. Then, in step 602, the user determines whether or not the multimedia application is running. If the test result in step 602 is YES, in step 603, the user determines whether the multimedia application is minimized. If the test result in step 603 is YES, the user selects the minimized multimedia application icon 501, as shown in FIG. 5. Thereafter, control is transferred to step 605 in which the meeting room window opens as shown in the screen of FIG. 7. Returning to step 603, if the test result is NO, the multimedia application is not minimized and the meeting room window is already open, as shown in the screen of FIG. 7. Returning to step 602, if the test result is NO, in step 607, the user starts the multimedia application in a manner consistent with the operating system employed in the user workstation. Thereafter, control is passed to step 605 where the meeting room window opens and is displayed, as shown in the screen of FIG. 7. 
     FIG. 7. as indicated above, is a graphical screen representation displayed upon a user starting the multimedia application upon initiating a multimedia call. In the example shown in FIG. 7, image icon 701 is of the multimedia call originator. Also shown is telephone 702 which may be used to originate the multimedia call, empty chair 703 which is available for an additional meeting participant to join the meeting in the multimedia call, table 704 which is used to share objects among the participants, projector 705 which is used to share images among the meeting participants, view graph folder 706, which contains the images to be shared among the meeting participants, and tool closet 707, which is closed. Again, note that the icons are of realistic real life objects which are well known to the meeting participants. 
     FIG. 8 is a flow chart illustrating the steps taken in the user selecting telephone 702 (FIG. 7) to initiate a multimedia call. Thus, in step 801, the user selects the realistic telephone icon 702. This causes a call bar to appear on the screen adjacent to telephone 702, as shown in the screen of FIG. 9. The call bar includes a field 901 for the user to enter a number to be called directly from the workstation keyboard, and a dial pad button 902, which when selected will display a dial pad for entering the number. Additionally, in this example, option buttons 903 and 904 are provided to select either a local on-line telephone directory or a corporate telephone directory located on the network. It should be noted that the directories associated with option buttons 903 and 904 are just examples of such directories that can be utilized for selecting the number to be called. 
     FIG. 10 is a flow chart illustrating the steps the user takes in placing a call from a multimedia directory. Thus, the process is initiated via step 1001 from the screen shown in FIG. 9. Then, in step 1002, the user selects the call initiation technique which, in this example, is the directory. This causes the directory application window to open via step 1003 and is shown in the screen of FIG. 11. The directory, shown in the window of FIG. 11, is just one example of numerous such directories that may be employed. Then, in step 1004, the user searches for the name of the desired prospective participant to be called in the multimedia call. This is realized by the user browsing through the directory. Upon the user locating the name of the desired prospective meeting participant, he or she places the multimedia call via step 1005. The call placement may be effected by any desired method, one of which is to select call button 1101, as shown adjacent to the prospective participant&#39;s telephone number in FIG. 11. The placement of the call by the user in step 1005 causes the screen as shown in FIG. 12 to be displayed via step 1006. As shown in FIG. 12, the call bar adjacent to the telephone displays the name and telephone number of the prospective meeting participant that was dialed. 
     FIG. 13 is a flow chart illustrating the steps the user takes in effecting a multimedia call directly from the call bar, shown in FIG. 9. This process is initiated in step 1301 from the screen shown in FIG. 9. Then, in step 1302, the user enters the desired participant&#39;s telephone number on the local workstation keyboard. This causes the telephone number being dialed to appear in the call bar, as shown in the screen of FIG. 14. Then, in step 1303, the user, in this example, presses enter on the keyboard to cause the displayed number to be dialed. which also causes the call bar to display that the number is being dialed, as shown in the screen of FIG. 15. 
     FIG. 16 is a flow chart illustrating the steps a user would take in effecting a multimedia call from the dial pad. This process is initiated in step 1601 from the screen of FIG. 9. In this instance, the user selects the dial pad option 902 from the call bar via step 1602, which causes the dial pad to appear on the screen, as shown in the screen of FIG. 17. Then, in step 1603, the user enters the desired participant&#39;s telephone number from the dial pad using a pointing device such as a mouse. This, in turn, causes the number entered to appear in the call bar, as shown in the screen of FIG. 18. Then, in step 1604, the user selects the dial button from the dial pad, which causes the telephone number to be dialed. This, causes the call bar screen to display that the number is being dialed, as shown in the screen of FIG. 19. 
     FIG. 20 is a flow chart illustrating the steps which are taken once the multimedia call is placed, as displayed in either of the screens in FIGS. 12, 15 or 19, as initiated via step 2001. Then, as shown in either of FIGS. 12, 15 or 19, and as indicated in step 2002, the call has been placed and the dialed number and the name of the called participant, if available, appear in the call bar, as well as, a hang up option. Then, step 2003 tests to determine if the call has been answered. If the test result in step 2003 is NO, in step 2004, the user selects the hang up option from the call bar. Thereafter, the call bar is removed and the screen appears, as shown in FIG. 7. Returning to step 2003, if the test result is YES, step 2006 causes the call to begin with audio only, causes the call bar to be removed from the screen, and causes an icon of the called participant to be placed in the meeting room on a chair, as shown in the screen of FIG. 21. It is noted that if the participant&#39;s image bit map is not available the generic image icon 405 will appear instead. 
     FIG. 22 is a flow chart illustrating the steps which are effected upon receipt of an incoming multimedia call at a prospective meeting participant&#39;s workstation. The process is entered with the incoming call via step 2201. Thereafter, step 2202 tests to determine if the multimedia application is running at the prospective participant&#39;s workstation. If the test result in step 2202 is NO, step 2203 causes only the telephone to ring. Then, the only option available to the called participant is to participate in the audio portion of the meeting. Returning to step 2202, if the test result is YES, step 2204 causes audible ringing to occur, the meeting room to appear on the participant&#39;s screen and the call bar to appear next to the telephone in a realistic meeting room metaphor, as shown in the screen of FIG. 23. Additionally as shown in the screen of FIG. 23, the name and number of the calling party is displayed in the call bar. Then, in step 2205, the participant selects a desired call bar option. Thereafter step 2206 tests to determine which option has been selected by the participant, namely, ignore, answer or other. If the test result in step 2206 indicates that the ignore option is selected, step 2207 causes the telephone to stop ringing, the realistic meeting room metaphor to be minimized and the call follows whatever call path has been setup by the network (tier example with a PBX the call could be sent to voice mail or to coverage) and the called participant&#39;s screen appears as shown in FIG. 5. Returning to step 2206, if the called participant selects other, step 2208 causes the called participant&#39;s workstation to perform any system specific action that the participant desires, such as voice mail or the like. Again, returning to step 2206, if the called participant selects answer, step 2209 causes the called participant&#39;s workstation to register its capabilities with the communications network middleware, the call bar on the called participant&#39;s screen is removed and the screen displays the real life meeting room with icons representing all the current meeting participants including the called participant being placed around the table in a realistic manner as would occur in a real life face-to-face meeting, as shown in the screen of FIG. 24. 
     FIG. 25 is a flow chart illustrating the steps that are taken in the automatic reconfiguration of the room and table when adding a participant to an ongoing virtual meeting. This process of adding a participant is initiated by step 2501 from either a meeting having an odd number of participants as shown in the screen of FIG. 26 or a meeting having an even number of participants as shown in the screen of FIG. 27. Then, step 2502 causes the participant to be added to the empty chair in the meeting room, as shown in the screens of either FIG. 28 or FIG. 29. Once the participant has been added, step 2503 tests to determine if the number of participants has reached a predetermined maximum. If the test result in step 2503 is YES, the process is ended via step 2504, since no more participants can be added. Note that since the maximum number of participants has been reached, the room cannot be expanded nor can an empty chair be added for any additional participants. If the test result in step 2503 is NO, step 2505 tests to determine if there is room to add an empty chair around the meeting table, i.e. whether there is an even number of participants. If the test result in step 2505 is NO, step 2506 causes the virtual meeting room and the table to expand by one participant space, as shown in the screen of FIG. 31. Thereafter, control is passed to step 2507. If the test result in step 2505 is YES, control is passed directly to step 2507, which causes an empty chair to be added to the virtual meeting room. This is shown in the screen of FIG. 30 for a room which did not require expansion and in the screen of FIG. 32 for a room which has been expanded. Thereafter, step 2508 causes the automatically reconfigured meeting(s) to continue. 
     FIG. 33 is a flow chart illustrating the steps taken in the automatic reconfiguration of the meeting room and table when a participant permanently leaves the virtual meeting room. This process is initiated in step 3301 from an ongoing meeting having either an even number of participants, as shown in the screen of FIG. 34, or an odd number of participants, as shown in the screen of FIG. 39. Then, in step 3302, a test is made to determine whether a participant has permanently left the virtual meeting room, as shown in the screens of FIGS. 35 and 40, for the meeting shown in the screens of FIGS. 34 and 39, respectively. If a participant temporarily leaves the meeting (puts the call on hold) the room does not reconfigure and the particular participant&#39;s chair will remain empty until he or she returns. Step 3303 causes the meeting participants of the virtual meeting on the same side of the table below the empty chair of the participant who left to move up one chair, as illustrated in the screens of FIGS. 36 and 41. Thereafter, step 3304 tests whether or not there are two empty chairs on the same side of the table. If the test result in step 3304 is YES, step 3305 causes the person in the chair at the bottom of the table to move from the other side of the table to the top empty chair, as shown in the screens of FIGS. 37 and 42. Thereafter, control is passed to step 3306 which tests to determine whether or not them are two empty chairs around the table. Returning to step 3304, if the test result is NO, control is directly passed to step 3306. If the test result in step 3306 is NO, there is only one empty chair and the process is ended via step 3307. If the test result in step 3306 is YES, step 3308 causes an empty chair at the lowest point of the table or on the left side of the table to be removed, as shown in the screens of FIGS. 38 and 43. Then, step 3309 tests whether or not there is excess space at the bottom of the table so that the room and table can be shrunk in size, i.e. whether or not there is an even number of participants in the virtual meeting room, as shown in the screen of FIG. 43. If the test result in step 3309 is NO, the process is ended via step 3307. If the test result in step 3309 is YES, the table and room are shrunk by one chair space, as shown in the screen of FIG. 44, and the meeting is continued including the automatically reconfigured room and table.