WO2012091723A1

WO2012091723A1 - Method for holding a meeting, using server and terminals connected to a network

Info

Publication number: WO2012091723A1
Application number: PCT/US2010/062581
Authority: WO
Inventors: Chao King; Samuel DUH; Albert Lieu
Original assignee: Konica Minolta Holdings, Inc.
Priority date: 2010-12-30
Filing date: 2010-12-30
Publication date: 2012-07-05

Abstract

Provided is a virtual collaboration system for holding a meeting among a server and computer terminals connected to a network, the system having: a server configuredtobe connected to tte network; a plurality of computer terminals configured to be connected to the network; and a storage device configured to be connected to the sever; wherein a first meeting element and first attribute information including a first time of receiving the first meeting element and a first user ID is stored, in correlation to each other, and when there is a second meeting element, to be inserted in the fast meeting element, having been transmitted from one of the computer terminals, link information to link the second meeting element to the first meeting element stored, and also provided are a method for holding the meeting and a computer-readable recording medium storing a program for holding the meeting.

Description

METHOD FOR HOLDING A MEETING, USING SERVER AND TERMINALS CONNECTED TO A NETWORK

TECHNICAL FIELD

[0001] The present invention relates to a system for folding a meeting using a server and a plurality of computer tenninals connected to a network, a method for holding themeeting, and acompite-readab!erecordi^ storing a program for making the server and the computer terminals execute the method

BACKGROUND

[0002] The network and Internet make the communication from different locations easier, and clifierent work places can communicate and share multi-media inibrmation such as pictures, audio, video, and other document files on the Internet for collaboration or a virtual meeting

[0003] Ifcollaboration or a virtual meetin s The conventional methods to record this type of on-line meeting or collaboration is to record the shared muM-media information into a single oai ^

line meeting and collaboration This stored video like file in tie storage device is retrieved through tie netwoik when re-play is requested. It only plays back as video recorded with all m ti-media components shared and viewed on participants' displays. But it is riot easy to play back desiiedcomr^

particular participant's record of video, audio or otier shared whitebc^ activities, OT to revi^

shared ciuring the collaboration It is also difficult to fird the pc¾

desired documents into these recorded file while reviewing the recorded on-line meeting or collatoratioa For example, when a previously recorded on-line meeting or collaboration event video file is being replayed, it is difficult to pause the playing video at a certain position and to insert new comments therein, or to add doannents, and to record these new activities and comr^ because the recorded collaboration is just astream data without any structure. Therefore, a more convenient method and algorithm are required for recording a network meeting and collaboration event, for archiving and playing back, and for more efficient ieiecording BRIEF DESCRIPTION OF THE INVENTION

PROBLEMS TO BE SOLVED BY THE INVENTION

[0004] Many people are using the network and Internet to conduct on-line meetings with video/ audioand other types of multi-media contents for collaboration from many different remote locations. There are some application programs to record these on-line meetings. However, none of them can provide a ample solution, because they record these events and its contents by converting all these content components into one combined and mixed file Kke a movie or video file with audio tracks. When litis type of file Is accessed for playback, the player application program will then, amply re-play it as a movie or a video.

MEANS TO SOLVE THE PROBLEMS

[0005] In view of forgoing, one embodiment according to one aspect of the present invention is a virtual collaboration system for holding a meeting using a server and a plurality of computer terminals connected to a network, (he system cccnprising:

the server configured tobe oc nected to tte network;

the plurality of computer terminals configured to be connected to the network; and

a storagedevice is configured to be connected to the sever,

wherein the server configured

to receive, fium a first c snputer terminal of thecorrrputCTtemTinals, information of a first user ID of a user of the first computer terninal and a first meeting element both transmitted by the first computer terminal through the network and transmit the received first meeting element to fie computer terminals;

to store in the storage device the received first meeting element and first attribute information including a fii^ timeofrecavirig the first meetm

to read out tram meeting demaiissta

correlatedto second attribute infcm alm

second usa- ID and transmit the second meeting demeri to the ccsripute^

to suspend, when the server is required from one of (he computer terminals to suspend the traagnission of the second meeting dement the liarisrniss^ tiie storage device a third meeting dement lwingtxmtra^

of recaving the third meeting dement and a third user ID of a user of the ore of the computer terminals tram which the third meeting demerit rtas em

tostore, when the third meeting dem

meeting dement and the second meeting dement to resume, when the transmission of the third meeting element has been terminated, the transmission of the second meeting dement; and

tostore^ when storing ihe first mee^

information, link information between the second meeting demerit and the first meeting demer¾ and

wherein tfe first oomput rterrn^^

through the network;

the plurality of computer terminals are configured to receive and reproduce the second meeting dement transmitted from the server through the network; and

theoneofthe computer termir.^

second meeting dement and transmit the third meeting element during the su¾xnsion of the transmission of the second meeting dement

[0006) According to another aspect of the present invention, another embc<iirnent is a method for a holding a video meetirigby using a virtual collaboration system liavinga server and a phiraKty of cornrwter terminals wH are connected to a network and ccornmuiicable to each other, the method crjrrpising the steps of

(a) transmit a meeting dement to the server through the network from one of the corrrputer terminals through the network;

(b) receiving on the server the transmitted first meeting, and trarBmitting the recdved first meeting element to the corrrputer terminals through the network;

(c) recdving and reprcdL ng the first meeting dement transmitted from the server through the network;

(d) storing in the storage device the first meeting element haviiig been recdved on die server and first attribute inforrriation including a first time of recdving the first meeting dement and a user ID of a user of a computer terminal from which the first meeting dement was transmitted, in correlation to each other,

(e) reading from meeting elements stored in the storing device into the server, a second meeting dement which has been correlated to second attribute inibrmation including a second time of recdving the second meeting dement and a second user ID, and transmitting the second meeting dement to the computer terminals through the network;

(f) recdving and reproducing on the computer terminals the transmitted second meeting dement;

(g) when a suspension request for requiring suspension of the transmission of the second meeting dement is inputted in any one of the computer terminals, transmitting the inputted suspension request to the server through the network;

(h) recdving on tie server the suspension request on the server, and suspending the transmission of the second meeting dement (i) ttansiriitting a third meetm

network while die trararrrission of the second meeting dement is suspended;

®recdvhg on the sew me third meetm^

and storing in Ihe storage device die received third meeting dement and third attribute information induding a third tfmeofrecei\½g me third meeting dem

which the third meeting dement has been transmitted, in correlation to each other, and

(k) when storing the fhirdmeetir¾ dement having been r^

inforrnation, storing Knk intbimation between the third meeting element and the second meeting dement; and

(I) resuming the transmission of the second meeting dement when the transmission of the third meeting demerit has been finished;

(m) when storing the first meeting dement having been received on the sever and the first attribute irrforrnarion at step (d), storing Knk irrformation between the second meeting dement and the first meeting dement [0007] A∞cirding to another aspect of the present invention, another embodiiuent is a compiiler-rcadable recording medium stormgaprogram fomakmgaserverar^ computer terminals to execute a method for holding a video meeting by using a virtual collaboration system having the server and the pluraHry ofcornputer teirninals which are connected to a network and communicable to each other, the method comprising the stops of

(a) transmit a meeting dement to the server through the network from one of the computer terminals through the network;

(b) receiving on the server the transmitted first meeting, and transmitting the reedved first meeting dement to the computer terrninals tfarciiighrhe network;

(c) receiving and reproducing the firstmeeting dement transmitted from the server through the network;

(d) storing in the storage device Ihe first meeting dement raving been received on the server and first attribute intormaticm iradidi^

computer terminal from which the first meeting dement was transmitted, in correlation to each other,

(e) reading, from meeting dements stored mfiiestonng device into the server, a second

which has been correlated to second attribute information including a second time of receiving the second meeting element and a second user ID, and trar-anitfingthe second meeting element to the computer terminals through the network;

(f) recdving and ierxrjclucing on the corrpjter terminals me tia^

(g) when a suspension request for requiring suspension of the transmission of the second meeting element is inputted in any one of the amnputer temiinals, transmitting me inpu^

ihe network; (h) receiving on the server the siBpensacmreqiiest on tte server, arri

second meeting dement;

(i) transmitting a third meeting dement from the one of the computer terminals to the serva through the network while the Irarujnission of the second meeting dement is suspended;

(j) receiving on the server the third meeting dement transrnitied fiom the one of the computer terminals, and storing in the storage device the received third meeting dement and third attribute inibrination including a third timeofrecavmg the third meeting dem

wKdi the thM meeting demerit has been tr^^

(k)whmstrjrir¾ the third meeting

information, storing fink information between the third meeting dement and the second meeting dement; and

(1) resuming the transmission of the second meeting dement when the transmission of the third meeting dement has been finished;

(m) when storing the first meeting dement having been received on the sever and die first attribute information at step (d), storing link information between the second meeting element and the first meeting dement

DESCRIPTION OF THE DRAWINGS

[0008J Fig 1 sr» ^ a o ofiguratimofa personal oon uter of mem

invention

Fig 2 shows a virtual collaboration systanoftheenilxxiimeritaccoirlingto thepreseril

Fig 3 shows a fog-in window of the embodiment according to the present invention;

Fig 4 shows a meeting manager page of the crnbodirncnt according to the present invention;

Fig 5 shows a meeting window of the embodiment according to the present invention;

Figs.6a and 6b show a bask structure of the embodiment accordingto the present invention;

Fig 7 shows a example of sharing w itEboard drawings and uploaded images in the meeting window of the emboomentaccandin to the present invention;

Fig 8 shows a playback screen of the embodiment according to the present invention;

Fig 9 shows a partitipant's window of the erfoodiment accordingto fterjresenthiveritirai;

Fig 10 stows one exiin leofa window ofthe local PC 100 of the embodiment when a previous meeting is replayed

Fig 11 shows another example of a window of the local PC 100 of the embodiment when a previous meeting is replayed; Fig. 12 shows still another example of a window of the local PC 100 of the emtodirnent when a previous meeting is replayed;

Fig 13 shows a timing diagram of the recording function and the playback function of the embodiment according to the present invention;

Fig Mshowsatimelmeoftheprocedureofi^^ 13;

Fig 15 shows adatastructureoftte

present invention;

Fig 16a shows atimmg diagram ofreoo^

Fig 16bstowsadatastnKSureoftheairre^ 16a;

Fig 17 shows a flowchart of a program of a collaboration media server o the emlxxiiment according to the present invention

Fig 18 shows ameetir¾ room table of th^

Fig 19a shows a situation where two participants are logged-in;

Fig 19b shows a timeline of the situation ofFig 19a;

Fig 1¾ shows a data structureofthesto

invention.

Fig 20a shows a flowchart of a procedure of the collaboration media server of the embodiment of the present invention;

Fig 20b shows a flowchart o f a procedure of a recording mode of the embodiment of the present invention; Fig 21 shows a flowchart of rerjroducrng aprevious meeting, of thecmbodrment according to the present invention; and

Fig 22 shows a flowchart, of the emrxxEment, of rocesdrigarneeting to v^rich arwther meeting is added

PREFERRED EMBODIMENTS OF THE INVENTION

[0009] Figl shows ftmctional devices of a pen^; ial ccnTrpiirer(hereinaiter,re

through which a user joins the on-line meeting as a collaborating participant In fireon-line meeting, the

)Daborating participants share multimedia component files. Tne PC 100 is provided with a PC main body 101 including a central processor 110, amemory 111 , a Displaying graphic card (not shown), a sound card (not shown), a storage device 109, and a network interface card (NIC) 105. An externally connected web camera 103 is used to capture the motion and static image of the collaborating paiticipanL An

to pesent a sound voice file An externally connected microphone 112 is used to input the voice of the collaborating participant. The web camera 103 and the microphone 112may be buillinthePC 101. A monitor display 102 is used to show multimedia m

tablet as apointingdevice 106 is used to make object selection, and to input hand draw graphics and commands. A keyboard 108 isusedtoirpitextsarxicor^ Thenetwc^inlserfacecaid lOSisu^

other PC or a gateway or a router for network connection. A PC built-in operating system and Internet browser program are installed for browsing Internet and searching internet content The staragedevice 109 is used for storing data to be shared with other cxtUatorating participants.

[0010] An embodiment of a virtual collaboration system according to the present invention is configured with a plurality ofPCs as shown in Fig2. The procedure of a connection from each collaborating p-utidpant to the on-line meeting, an access to a collaboration media server 204, and starting the meeting will be described

[0011] Fig 2 shows a basic connection between collaborating participants' PCs 201, 203, 207, 208, and 209 and the ojllaborationmedia server 204. A software program fcr realizing ameetin between the PCs is running on tie collaboration media server 204. In particular, the collaboration media server includes the storage device 205 as a means for storingmeetings. The first collaborating participant's PC 201 isc HTnectedto<heInteniet206thiougli a local gateway 202 thereby connected to the collaboration media server 204 through an internet browser program. The second collaboratmgparticipaiifs PC 203 is also corrected to IheTOflatorationmedk

internet browser program. the virtual coUaboration system of trie emb^ the collaborating participants can upload multi-media files including audio, video, document, whiteboard activities and text chatting files to the collaboration media server 204, and then being managed by a coDaborationmedia server program, those uploaded files can be downloaded to each and every collaborating participants' PCs 201, 203, 207-209 through the Internet 206.

10012] The collaboration media server program allows the coflaborating participants to log in with user determined meeting room name and a password. The operation of tire collaboration media server program will be described in reference to Fig 17. Anacx^fiomthe^ertPCiswaitedfbriristepSOl. In step S02, if an access fiom the client PC is detected, a log-in window (see Fig 3) is sent to that client PC (step S03). Aroomnameanda asswerf are waited tobeirtput in 5ίφ804. In^S05,iftheojmbiru3ti^

conect,flieproceduregoescntost^S06,arritf The correct

∞mbinations ofroom names and passwords are stored in the storage device 205 of the collaboration media server 204 asarneetingtable 2101 ofFig. 18, and this tabic is referred in order to verify the ccimbination of room names and passwords in step S05. The login cftreiiser is accept^

stepS07. ff the user iiame is irir m step S08,tfe

fri step S09, a meeting window (see Fig 5) is sent to the client' s PC step S 10, it is determined if the user shares audio arid video, ard if the user shares, aiai clients' PCsinste Sll. The collaboration modiasen£T_tees the aiKlio and w

audio and video received fiomthc client PCinstepSll The detailed rrocess for storingtheau^

described later.

[0013] Although not shown in figures, regardless of the determination, in step S10, ofbeing shared or not, the collaboration media server receives whiteboard drawings, texts, and chatting, which are oennponents other than audio and video, from the client PC and communicates them to other clients' PCs (step SI 1) while storing them (stepsl2).

[0014] lnst^S13,itisjudgediftherneefir¾

is logged out in step sl4.

[0015] Fig 3 shows a log-in window 300 for a first participant to log-in the collaboration media server 204 after thepalic^anthasccraiededhisPC201 by inputting the collaboration media server's address by name or by numbers. A meeting room name and a log-in password both previously determined (Fig 18)areinputinaroorn name input box 301 and apassword input box 302 in cmkr to join the or Hne meeting, respectively. The participant canjoin a cunert meeting by selecting a Go To Meetm

t e storage device 205 of the collaboration media server 204 by selecting a Get Meeting record button 304.

[0016] Once the participant logs-in to the collaboration media server, a meeting manager page 400 ofFig, 4 will appear arxl the partiupant is aflowed to specify After the name is altered, the participant can enter file collaboration ic<m by pressing Erto

conn ection by pressing the Caned button 405 to return to the log-in window 300. The coBaboration media server program checks the connection speed between the participant's PC 201 and the collaboration media server 204. Once a participant logs-in to the meetingroorn, the collaboration media server program recognizes the participant arrf starts to shiare trie rrrdti-m^

601 triatall∞flaborarir¾partd The collaboration media server 204 downloads this window to tterjarticipant PC. T½rjarticipanl can share their au^

A group of whiteboard graphic tool buttons 602 also allow the participant to choose and perform graphic drawing and texting tasks which includes line, shape, text typing, pointing and eraser functions on the whiteboard 601. The functions ofline, shape, text typing, pointing, and eraser are the same as those in, tor example, Paint Brush of Microsoft inc., and the description thereof is omitted Once an AudioVidco sharing function is selected by the participant, the collaboration media server 204 starts to upload the participant's video and audio to the collaboration meda server 204 and serriitto those rjar^

Reference numerals 613 is a video window ofthe first participant of the on-line meeting, and the reference numeral 614 is a video window o the second participant ofthe on-line meeting. The participants can upload a document file from their own PCs (local PQtD the collaboration media server 204, share with other participants by using an upload button 605, and select a file from the storagedevice 109 of their own Once the file is selected and uploaded to the coDaboratian media server 204, its file name is displayed on a file list window 603, anyparticipant can select a file from the file list window603 to share with alltheofher participants by selecting the file name in the file fist windows 603 and then pressing a load button 604, and tre selected file wfl be distn¾uted to aU

participants can also download the file on tie file list window 603 to their local PC by selecting tie file name and pressing tie download button 606 to download the fflefrcm the collaboration m

storagedevice 109. Arry file cm the ffle list windcw6O3 canted^ name areltrm pressing a delete button 607 to remove from the collaboration media server. The window 600 also provides a text chatting function while collaboration is in progress. To use this function, tie patricrpant can and use a keytoara to serd text messages to dther all

mml^ list 612 can show the currency parti When the internet connection does not have required quality during the collafr

In this case, a participant can change the connectic« and srtaring data rate setting b^

cX)9tochange the data rate settingtorjeWghercTkm^toadj^ia

[0017] To manage and distribute shared multi-media ccanponenls, the c»llaboration media server 204 of the embodiment according to the present invention processes all the multi-media files and connection information as individual components. When a participant bgs-in to the collaboration media server 204, and starts to share multimedia components such as video, audio, whiteboard drawing, text, and upload c cument, each οαητροηεηί is attached with an information tag ami stored in the storage device 205 of the collaboration media sa er 204 for management In addition, every time a participant logs-in, a participant tag is stored in the storage device 205 of tie collaboration media server 204.

[0018] Fig 6a and Fig.6b show the basic structure of multi-media components stored in the storage device 205 of the collaboration media server 204. Each exjmponent uploaded from the respective coM*>rating participants such as a video file 706 captured by tie web camera 103 from die local PC 100 is stored in tie storage device 205 of collaboration media server 20 with a file name and a video information tag 707. An audio 705 captured by a microphone 112 of the local PC 100 is stored in the collaboration media server 204 with a file name and an information tag 708. The information tag 708 has a pointer 724 to the audio file 705. In Fig 6b, the information tag 708 may include a type 721 of tie component to be stored, an ID 722 of the meeting to which the component to be stoned bdongs, the time fkm tie start of fliemee^

togged-in from the PC from wMch the corrrp^ The information teg 708 is stored in the s

205 of the coDaboration media serva 20 together with the componenL In Fig 6b, the audio file is illustrated as an example, and the following whiteboard activity and text chatting are the same. Every time when the participant uses the whiteboard tool to make any activity such as dtrawing line, rnakingshape^

moving objectives to other location, this initiation is recorded in a whiteboard event file 702 and stored with an information lag710m the storage device 205 of the collaboration media server 204. WhrnttecoMwrating partidpant uses the chat tool to make text cnattirig, each cr^ stream is s

tag711. The collaboration media server 204 creates a participant tag 709 when a participant logs-in to the collaborating rcorn,arai the pa^

tags 707, 708, 709, and 710 of the components uploaded fiomrhepaiticipant'sPC, for file sharingpiocessingand management Video files 706, audio files 705, whiteboard event files 702, and chat files 703 arc stored with their respective information tags in a component managarnent table 701 for each meeting.

[0019] An rocedureinvvliichapo^

reference to Figs. 19a, 19b, and 19c.

[0020] Fig 19a shows the situation where two participants are loggrng-in to have a meeting Suppose a case where user A F01 wrote equation F06, saying ' This is my opinion¹ ' (F03), and user B F02 drew a red cross F07, saymg'¾'swrong",arduserAF01 said 'Oh, you are righf' to that Fig 19b shows this case in order of time. Reference numeral F13, F14, and F15 denote audiovideo files carcsponding to F03, F04, and F05, respectively. The reference numerals F 16 and F 17 denote whiteboard corrrponents ccrrresponding to F06 and F07, respectively. In this embodiment, audio conipanents and video ccrrrporraitsareortc^usinga silent part thereof

[0021] Fig 1 c ill ustrates how the interaction between user A and user B described in Figs. 19a and 19b are stored in the storage device 205 of the collaboration media server 204. m the Figure, video components are canittad.

[0022] When user A and user B log-in, participant tags F41 and 142 are generated, respectively. When user A talks ' This is my opinion'', an audio corrrponent F33 including this audio is uploaded to the collaboratian media server 204 to be stored in the storing device 205. AninfomiationtagF43 issimiiita^

Since this audio cempcrient F33 is uploaded tram the client PC of user A, a link F53 is created fiam tie participant tagF41 to the information tag F44 of this audio oomponerrt Similarly, links F54 and F55 are created fiom the participant tags F42 and F41 to information tags F44 and F45, respectively. Similarly with respect to tie writing to the whiteboard, when a writing to the whiteboard is rjerfbmiedb^

the storage device 205 of the collaboration media server 204. An inibrmation tag F46 is shndtaneousry stored. It should be noted that when "z = ax +by+c" is written for example, many whiteboard event files and inibirnation - tags are stored since a whiteboard event is C-teated for a single draw. However, series of event files arc each denoted by individual reference numeral F36 and F37, and series ofiriformation tags are each denoted by individital reference numeral F46 and F47, in Fig 19c. WhentheiiiforrriatimtagF46oftte link F56 is created from ⁽he participant tag F 1 of user A, similarly to the case of an audio component to Ihe information tag F46. Similariy, the vhiteboard component F37 is stored together with the information Tag F47, a link F57 is ieated ikm thepan crpart

[0023] Since the multi-media components shared in the meeting room are stored for fixture reviewing and other usages, the present embodiment also provides the tools and algorithm to reocnd all shared components from the participants trring a meeting When a plurality of participants login to the collaboration media server 204 via Internet, a room was pre-set with a room name, a subject, and a log-in password (see Fig. 18). All participants log-in to the meeting room with room name and password verified. A ccmmrjrdy shared \vrnte^

by afl participants. Fig 7 STKWS a meeting WTT IOW 800m with all the other shared muM-media components with participant-added objects. The first participant can be seen on tire video window 802 after the first participant logs-in and dicks his share button which is the samebutton as the share button 812 in a window 800 fcrtheseccrdpaiticipartTTie second partic^

after the second participant logs-in and his auaio/video is shared. Tnethirdparticrparlis also shown in a video wirxfow804adlerhelogs-marrihis is sliaredTte first participant uses tablet 106 to write some phrases 805 on his wlriteboard 801, and the seccrd participant can view the phrases 805 on his whiteboard 801 , distributed through the collaboration media server 204. T¾e second paiticrpant can see the srrntowirdow on the window 800. The second partidpant also makes drawing with his pen tablet (pointing device 106) to illustrate a time to business graph on his whiteboard (not shown). The time to business graph 806, 807 and 808 are shown on the whiteboard 801 of the first participant's window 800, where reference numeral 808 points the caption "START" and the upper arrow just above the caption The third participant also adds the target time and business size with tines on his whiteboard (not shown) with his pen tablet (pointing device 106), and the added target time 811, the business

Each of the drawn objects is shared as an independent oorrrponent with its information tag defining a line width, a color, drawing time, a name of the participant who draws the object, other connection ir&rrnation, and so on In addition, when a participant also adds a flow chart file uploaded to be shared from his storage device 109ofhis PC 100, the flow chart 813 is shown on the crffra- participant's whiteboard as well as his own whiteboards. All multimedia components including video, audio, text, drawings are components shared through the collaboration media server. So far, the afl mtiltimedia components are shared, but not saved

|0024] A participant can also cfick a reccmdfo

meeting The collabaration media server 204 distributes rhemulti-meclia components uploaded from each of the participant local PC 100 to all the other participants and saves all the uploaded components in the storage device 205 of the collaboration media server 204, with iiifbrmation tags in the component management table 701. The component management table 701 has a Mst of all the components recorded while recording. The participant can start nEOordingbydickingft^

Οτκ« the recording process Ls stopped, th^

session, \ Wch starts at1hecli The multi-media components are oonlmuedtDbeuplc«dedi -raaUp

other participants until the collaborafingmeeting is finished with all participants lagging-out ofthe room The on-line meeting is then completed.

[0025] Fig 20a shows Hie procedure ofthe collaboration media server 204 to change a retxirding mode The collaboration media saver 204 waits for a command from the participant PC (step S21). When the command is received from the participant PC at step S22, the command is judged to indicate "start ' or "end' 'atstepS23. Ifthe received comiT-arri is '¾arf^ Ar^ the component rranagpnent table 701 is opened for the meeting in the storage device 205 of the collaboration media server 205 at step S25. The recording mode is checked by the flowchart ofFig 20b. If the command is "end' ' at Ihe step S23, the rrocessgc<s∞tost^S26 to turn offthe recent for the ongoing meeting at step S27.

[0026] Fig 20b is a flowchart snowingthereocidingr^

S12 of the flowchart ofFig 17. In Fig 20b, the recordirig mode, which is turned on or offin the flowchart ofFig 20a, is checked at step S30, and if thereccnlingrnodeis "on", the collaboration media server 204 records the components from fie participant PCs with infcnnation tags in the storage device 205 of the collaboration media server 204.

[0027] A follow-up meeting can beheld to resume theun-fnished first session of meeting as a second session The foflow-up meeting startstyttesrmto session In themeetingroom, a participant can search and view the past meeting records from the collaboration media server 204. When "Get Meeting record" button 304 of the log-in window (see Fig 3) is clicked, a playback window 1000 ofFig 8 is displayed . Ttis screen is for the participant to specify the details of the playback mode. The playback mode contains, what types of components (cambirtation of audio, video, whiteboard activities, text chatting, file uploading such as uploaded flowchart 813 in Fig.7) and whose events of which meeting will be replayed. In this screen, a record table 1001 is shown. Theparticipaniofthemcctingcanch^ In trie record table lOOl_jttetotalparticrpartiTmibff ^ rntherocord table 1CI01, meetings are listed. Ora¾apatticrpaiilcheseameetingm 1005 are displayed under the record table 1001. Then, the partidpant ofthe current sessim can also sdecttoplayoack the meeting in difrouTt oumbinatio ts, such as ccnibination of participant's name 1007. When a participanl of the previous session is selected, only the recorded components such as video, audio, text, document and whiteboard activMesofsdected participants \viU be re^ The reference numeral 1007 denotes thenaneofthesdectedpartidpant It is also possible to sdect the typeof component to be played back, byusingsdect buttons 1008, such as video and audio for the selected participanls of the previous session A participant can also sdeda'playair'buttrm 1015 tDi^e\¾anoftheccnr^menlstoplayrjack the recorded collaborating meeting. Theurritofaudioairivi(feois at^

shareandvAentheuserterminateslheshai^ Audio and video may be analyzed and stored in different pieces divided by parts whose audio level is bbw a predetermined level A single draw to in a whiteboard is a single component Fig 21 srtowstheprocedureofrepioduri

[0028] TheFi 9showsameetingwinu 1100with and 1102 on a participant's PC 100 screen 102. After the first paiticipanl and the second participant log-in to the meeting room, a meeting member table 1103 will display the names of the participants in this meeting In this case, only the fist participant David and the second participant Jenny are in the meeting The screen display is from Jenny^" s local PC 100, and the footer showing the attendee logging-in to the coUaboration media server 204 is named Jenny. Once the participants share their audio video, the participants' video windows 1101, 1102 ar^earmthewindow 1100. On the local PC 100 ofDavid, who is a partidpant, the video window of Jenny appears. Each participant can make adjustment of die other's video display size, bigger or smaller and of the location on the screen. 61 this meeting one of the objects is to review and make an agreement based on the record of the previous meeting and to post comments and to write the statement of the agreement A text irpitc¾eacon onent 1105 is u0

between the two participants. Any ofthe participants cm cHci the view butto 1106 to display the playback screen 1000ofFi 8. AfierspecifyingthedetailsoftheD^ 1010, the collaboration media server 204 starts retrieving the recorded files from the storage device 205. The window for the participant changes to Fig 10. The case of replaying whole the recorded meeting will be described bdow. When a complete record replay is selected as in this case, the collaboration media server 204 retrieves all the components data offhe concerned meeting from the storage device 205, and starts to distribute each component to the two participants. Fig 10 shows a window of the local PC 100 of the participant Jenny after the recorded component files are distributed and displayed A se∞ndary sharing box 1201, wfachLs a sub-window to ciisplay the r^

previous meeting is a sharing space of the retrieved meeting records irffihrding various multi-media components of ttiepaddpantsdected in the window 1000. TheazeofftHSseoondaryshartngbox 1201 and the location on the currently shared whiteboard 1212 can be set by a participant, arri their settings

for a default setting The description 1205 on theprevious meeting is displayed, and the video window 1202 of the first participant of the previous meeting appears. According to the progress of the recorded meeting the video window 1203 of the second participant of the previous meeting will be displayed, and then the window 120 of the third participant of the previous meeting will be displayed The voice of each participant will be played parallel with the voice of the current meeting In the previous coBaborating meeting, one of the participants has shared the hand writing 1206 on the wKteboard 1212 A graphic 1207 created and shared by another participanl in the previous meeting will be displayed as the replayed previous meeting progresses, and a line 1208 drawn by the second participant and marks 1209 written by rhethird participant will be replayed The flow chart 1210 is also replayed, and the progress bar 1211 sho S the pkying status ofrhe previous n e^

of the previous meeting

[0029] Fig 11 shows another example of a widow 1400oftheparticrpant's local PC 100, the shared whiteboard 1401 of the recorded components of the previous meeting shows no video from any participants and no sound or voice displayed if the playback mode is specified to display only whiteboard events and file upload events. The pkybadc sequence goes from the f¾

follow the real time duration. It will display all the retrieved components one at a time in order of time of file upload arrf whiteboard everl creation. The next component 1404 will tr^liedisrfevedarKl Mowed by aD die cdier whiteboard event oornponent 1405 and file uploading component 1406 until all coiTpments in the recorded meeting are all displayed acx»rding1othetimesequence. The progress bar 1407i^ectsthecurrmtdisplayingstarus with respect to the total time for displaying recorded collaboration

[0030] The current meeting includes multi-media components such as video, audio, text, drawing and document from two different sub-meetings. One sub-meeting is the currently running meeting with two participants, and the other sub-meeting is the meeting previously recorded and being replayed accordingto the playback mode selected by the current meeting particrpant All the components canbe adjusted and controlled in diflerot sizes ar^ by each anient participant, within the snared whiteboard cm the screen of each participant's local PC 100.

[0031] The process of the collaboration media serva program will be illustrated in Fig 21.

Atst^S41, the meetirig lobe replayed is 1001 ofRg 8. At sl^S42, the component management table 701 o the selected meeting is opened, and the components of the selected meeting are collected Atst^S43,rhepaitidpantswtopa^

having attended the meeting are displayed as in Fig 8. fo^S 4, the participant to be replayed is alfowed to be selected A pluraHtyofparticipants may besdected Ats^S45,typesofthcoomrxjn^

allowed to be selected Plural oftvpesnraybesdected InFig21,s^S44arris^S45areproassedm but ether one may be processed earlier.

[0032] At step s46, based on the playback mode selected at steps S44 and s45, in other words based on the participanls and the types of the components, the components in the designated types of the designated participants are collected from the component management table 701 of the selected meeting. At step S47, the collected components are sorted moida of starr^

components.

[0033] At step S08. a clock for replay is set at the starting time. ThestartmgtrmeistheearHesttimeins^ times stored in the inforrnarion tags of the collected components. At step S49, the dock forreplay is started The Parted clock counts one second in response to one second in leal time.

[0034] At step S50, the starting times of the sorted components are compared with the clock for replay. When the starting time is the same -B the tir^

other words, the component is sent to the participants' PCs. At step S50, the times arc not the same, the clock is advanced to the starting time of the next component

[0035] At step S53, it is checked if there is un-replayed component If there is no un-replayed component the replay ofthe meeting is tenriinated. Ifthereisanun^layedcrjmpo^

[0036] Another acrvanlage of tteembod 12, which is a window

1500 of aparticipant's local PC 100. The first participant, who is displayed in a video 1501 , can make comments and rrKxiificarion to theplaybackmeetingby clicking the record button 1502 of the window 1500 and then the Start button 1503. CT » recc>iding starts by dicking the Start button 1503, playback of the previous meeting shown in a whiteboard 1510 is paused and all the shared components of ίτκαι^^

205 of the collaboration media server 204 with inforrnarion tags generated. The information tagsinclude links to the iiifornation tags ofthe oamponehts which were being replayed when theplayback function was paused When the second participani shown in a video 1506 makes a drawing 1507 on a flow chat ofthe previous meeting and makes al rf writing 1508 ardacornment 1509 as remarks on agraph ofthe preview

iritoimationta^. The first partiripant ofthe cur^

button 1504 undertherecord button 1502. Thus, the collaboration media server 204 stops recording all the shared conrpments. The record con ra as anew meeting recoid. Once the recoiding function is stopped, the playback function will resume replaying the previous meeting that has been paused, until either the replay ofthe whole previous meeting record is finished or the current participant selects to end the playback function by clicking the Stop button 1505 under View burton 1511. After recording is stopped, all the multi-media corrrponents ofthe current meeting continue all thepartidpanls,bul no component is recorded in the storage device 205 ofthe collaboration media server 204.

Fig 13 shows a timing diagram of this recording sequence and the playback sequence ofthe previous meeting. The eririre meeting 1601 starts atatimir¾ 16O2 when the first∞

when the first participant requests playing back a selected past meeting record from the collaboration media server 204 and specifies the details of theplaybackmode at a timing 1603, the collaboration media server 204 retrieves the components rrom the stc^^c ire 1605 and distributes the selected components during aperiod 1604 accordingto theplayback mode. When the first participant clicks the Start (recording) burton 1503, at a timing 1606, to add comments to the past meeting component, the playback ofrhepast event is paused at 1607, and all the currently shared components, oft e current meeting, with the information tags begin to be stored in the storage device 205 of collaboration media server 204 from a timing 1608. The information tag of the first compmenttobeirisatedmtte

to the irrformation tags of the paused component In addition, the irrformation tag of the last component to be insated in rhepai-sedocmpcmentism.de to incM The information tag of the component to be inserted includes the time at the point of the pausing of the previous meeting ojinpcmeriWhenlhecornponerfcto

component management table 701 of the played back meeting in the storage device 205. When the first participant clicks the stop (recording) button 1504 at a timing 1609, recording of the currently shared components, which are to be inserted, is stopped at a timing 1611.

[0037] Then t e playback of thepievious meeting ocmpor^

be cccflini^ until ertecmeoft^

whole playback of the previous meting components is completed at a timing 1614. The current meeting continues until the last paiticipail logs-out tiie curral meeting room at a timing 1615. Then, the ament meeting is then completed.

[0038] Fig. 14showsatimelrneoftheabovesecrum¾. In an oldermeeting G40, there vvererbjiee participants. Jenny GO 1, David G02 and John G03. John uploaded a flowchart G05 to the meeting with a statement G04. Then, David ckw a graph G07 on the wh^ These interactions were recorded as a previous meeting. Alter that, Jenny and David replay this previous meeting in a new meeting G41. David pauses theplayback ofthe previous meeting and draws a picture G22 and hand-writes some messages G23, G24 on the wniteboaid while giving a statement G21. The statements G04, G06, G08 and G21 are video audio components. Block arrows G05, (307, G22, G23 and G24 are sequences of whiteboard events. (One block arrow corresponds to one sequera^of whiteboard events.) After David completes his statement G21 and whiteboariever-sG22,G23,G24,hestrj^

playback of the previous meeting. Reference numeral G42 indicates a paused point at which the previous meeting is paused [0039] Fig. l5shov^thedatastiuctr^ Reference numeral H40 denotes the ocnnporK^trriariagernert H41 denotes the component management table of the anient meeting G41.

[0040] The components of the previous meeting G40 arc recorded in the component management table H40, arid these oftheonTent meeting G41 are recorded m the component marag

exsrrpanent management tables contain participant tags, but the participant tags are not shown in Fig 1-5. The components H04 through H08 and H21 through H24ofFig 15 correspond tothecornponents G04 through G08 andG21 through G2 ofFig 14.ArrfinfrarrLatiOTtagsH14t

ccsrrponents H04 through H08 and H21 through H24, respectively.

[0041] Tlier3ieviousmeerir¾was paused atthepoirt 14. Theprecedingoomponerttthatisthe closesttn the pause is a wliiteboard event for the graph G07. The information tag H31 ofme first corrrponentH21 of the current meetir¾G41 has a lir-kH50fr^ of Ihe first compcmertH21 to the information tag HI 7 of the ccmponent H07. M auction, the rnfbrniationt¾ from the information tag H34 of the last component H24 of the current meeting G41 to the information tag H 18 of the component H07 of the previous meeting G40.

[0042] In this example, no part of the current meeting G41 before playing back the previous meeting G40 is recorded. In this case, the component management table H41 has a special information tag H60 to point the infbrrnation tag of the top τητροηεηΐ of the previous (recorded) rrieetirtg. In this embodiment, v^ien a added, in the current meeting, to the previous meeting G40, the errnpementtote

meeting and the data structure of theprewcn-sma¾ingG40isnot«±iar¾ed

[0043] Fig loaisatirrringdagramofthecas^ is recorded. The current meeting

1921 starts at a timing 1901 when the first participant logs-in, and the recording is started at a timing 1902 when the first participant activates recordingby clicking the start recording button. ThefrrstpaTticipanlthenretri^ subjecting 1922 from the storage device 205 of the collabordtion media server 204 for playback and review at a timing 1903, and the server starts retrieving the components and sharing them between all of the participants according to the selected playback mode at a timing 1 04. While the retrieved sub-meeting is played back, when an additional event (audio / video activities, whiteboard drawing, and so on) is ccrakcted, the playback of the sub- meeting is paused at a timing 1 06, the newly added event is played and shared between all ofthe participants, and recorded in the storage device 205 of collaborarion media server 204 from a timing 1907. Any of the played back ccsrrponents that have been previously recorded are not recorded this time, and the inforrnation of the activity that was newly added is recorded in the storage device 205 of the collaboration media server 204. The additional event component is completed at a timing 1908, and the paused stiMneeting component is allowed to be played back and shared at a timing 1909 and continues until the end of the sub-meeting at a timing 1910. A participant also retrieves another past sub-meeting 1923 for reviewing at a timing 1911, and the saver retrieves the components and shares them between all the participants at a timing 1912, the playback of the components continues until the end of the sub-meeting orbeiiigstoppedby a articipartatat(rning l913. Thereora Hngoferitiremeeimgisendedbya r^c^artfatatirningl915,arrithea

10O 4J Fig.16bshc«\BthectostrudUTeofthemeetirgsr» 16a Reference numerals 1921b, 1922b are! 19^bderote the cc5Tpc¾^mar¾ement tables ofthemeeting 1921, 1922 and 1923, respectively. Reference numeral 1940b demtes the liritostartplayingba 1922. Reference numeral 1906b indicates that the playback offcmeetmg l922ispaused It oaiesrx>ndstoflielinkH50ofF g.15. Reference numeral 1909b denotes the component just after the pause. It corresponds to the link H51 ofFig 15. Reference numeral 1912b indicates to startplayingback themeeting 1923.

[0045] Fig 22 shows a process for replaying a meeting to which another succeeding meeting is added.

[0046] Similarto ttereplaypocessof ameetingsnawninFig.21, the figure describes the process afierthe information tags ofthe meeting are sorted in order of time

[0047] At step S61. the clock for replay is initialized to the time contained in the iriforrnarion tag ofthe component to be replayed If themeeting 1921b is replayed from the beginning the dock for replay is initialized to be tiie starring timeoftheuifcmi-ώοη If the meeting 1922 is replayed from the rjegjnrring, the dock for replay is initialized to be the starting time of the information tag 1922.1b. Iiistead,ifthemeeting 1922 is replayed from the 19223b -which is therniddleoffliemeeting 1922b, the dock for replay is initialized to be the startingtime ofthe irifbrrnation tag 19223b.

[0048] At ^S62, the ckx^ for replay- starts ccnjrding At step S63, the dock for replay is compared to the times recorded in the informatioii tags ofthe components havingbeen sorted in order of starting time. Ifthereisa match, the component wk)se starting tm In oilier words, the data of tiie concerned ajmponent is distributed to the connected PCs. If there is no component whose starting time is the same as the time ofthe clock for replay at step S63, the dock for replay is advanced to the starting time of the next component At step S66, it is checked if the information tag of the component having been just replayed has a link to other ii^^ Ifitnas∞lir^fliepTOcessgoestostepS70. Ifthe information ofthe corriponent having been just replayed has a link to other information tag ofthe meeting the orrrenltimeoflhe dock is tempore

inforrnation tag of the linked meeting at step S68. The subroutine of step S68 is the same subroutine as the process of the flowchart ofFig 22 and is reflexivdy called. When step S68 is finished, the time saved at step S67 is restored totiiedcK±forreplayatstepS69. Atst^S70,itiscleteaTnin6d iflhere The condition for the determination of completion is either of the Mowings: 1 ) the chronologically last component has been completely replayed and there remains no component to be replayed in the concerned meeting; 2) in the subjecting called duringther^lay of other ccmrxiri^ 1607 ofFig. 13. In the case of above 2), the completion of replay of sub-meeting is determined by the existence of a link from another meeting such as the link 1906b ofFig. 16b. If the replay is judged to have been completed at step S70, the replay of the concerned rnccting is terminated. When the execution ofthe flowchart ofFig.22 is ended, if this flowchart is started by the oommand from a participant, die replay ofthe meeting is ended, and if this flowchart is started by subroutine step S08 during the replay of other meeting, tie process goes back to the flowchart ofthe invoker and step S90ov later are executed. Accardin to the ernbodiment, die shared inf rrn-icrnand muM-mcdia components are recorded as individually separated mmponenrs, each of which is attached with an information tag corvraning event related information such as a participanl lag of the participant who created the cornponent, when the cornponent is created Those shared information and multi-media components are separately recorded and are not combined or mixed with each other. When those information arelmdti-rnedacorTipmenis are accessed for replay, a system application program ofthe ernlxxriment will compose these information and multi-media comrxmerrts together based on the information tags, and the procedure of replay based on thedesire ofthe viewer as a formula to reproduce the recorded on-line collabonrtion events conlairang those information and multimedia (x nponenrs, and then redistribute to all the collaborating participants. This embodiment is more adaptive to various collaborating environments, since the recorded information and the multi-media content components can be composed by various requn rnenls and can be mixed from different time and date ofthe events. These features rovicle so called a timeless present-meet-past collaboration evert receding, a re-poducing and re-recoiding technology, and application programs for them

[0049] Theanrxxiimentacxcrramgto

conferencing system with on-line multi-media components such as audio, video, whiteboard activities such as hand writing and drawing, document uploading, and text chatting to be shared arnongmultiple users that tag-on to the same collaboration media server. The erribrjdiment also provides a method of recording, storing and archiving, and playing back the shared components such as video, audio, document, whiteboard activities such as hand writing and hand drawing, graphics created by any and all ofthe coUaborating participants, and the text chatting from all participants.

[0050] If an on-line collaborating event with three rxrrticipants are held replaying a previous meeting with 4 participants. All the three participants will receive total of 7 video displays from collaboration server, three videos frcm current on-Bneshari^

components are displayed as if seven participants are on-line sharing and collarxrrating. When the participanl selects to record current sharhgct^^

shared components into the storage device with event irrformation tags attached Playback with multiple recorded events by viewer determined mode is also convenient for viewing in certain parameter or progress gathered from multiple ujllaburations. It saves more time and improves the efficiency of meeting and collaboration with combined and grouped object reviewing The participants will observe that the current collaboration is combined with past collaboration

[0051] Tte jresert meeting aiidrjastn etm

coUabcrarhgpartciparil can view current video, audio, whiteboard, chat and uploaded document, and viewer can also share selected past video, audio, whiteboard, chat and uploaded document at the same time to make some corriDarisoi commeri, and o1her The played back ccimponents can be setup and adjusted as viewer^'s request such as to play the whole events by combining multiple events records together or to play the events of the specified participants. Only the selected rarnponents without unwanted cornponenls can be connected together for playback, reviewing, analysis, and other purpose.

[0052] WhflethepresertfinveriticHiha^

thereof, it is to be understood that the present invention is net liimt^

modifications which will become possible without departing from the spirit of the invention as defined in the appended claims.

Claims

What is claimed is:

1. A virtual collaboration system for folding a meeting using a server and a plurality of computer tarrrinals connected to a network, the system comprising;

the server configured to be corrnected to the network;

the pruraliry of computer terminals configured to be connected to the network; and

astaragedcwceisconfiguredtobe

wherein the server corvfigured

to receive, from afirst ccnnputertemiinal of the computer terrninals, information of a first user ID of a user of the first computer tenrrinal and a first meeting demerit bdhtiar^

network and transmit the received frrstmeetingdementtothecorrir^

tostore in thestrarage device the recdvrf

first time of receiving the first meeting derr^ aid the first ljser ID, kcc^ationtoeadiothe^

to read out from meeting dements stc^ in the sta

correlatedto second atrrikrteirrfbrrr^

secciid user ID and trartsmit the second rneetm

to suspend, when the server is required from one of the oorrrputer terrninals to suspend the transmission of the second meeting dement, the transmission of the seocndme^gdemert:andtoa

meeting dement having been transmitted through the network and third attribute mforrnatiari including a third time of receiving the third meeting dement and a third user ID of a usa- of the one of the computer terminals from which tte third meeting dement has

to store, when the third meeting dement is stored m the storage device, link information between the third meeting dement and the second meeting dement;

to resume, when the trarrsmission of the third meeting dement has been temvmated, the traremission of the second meeting dement; and

to store, when storing the first meeting dement having been received on the sever and the first attribute information, Hnk information between the second meeting danent and the first meeting dement, and

wherein the first computer ter^

through trie network;

the plurality of computer terrninals are configured to receive and reproduce the second meeting dement trararnitted from the server through the network; and the one of the computer teaninals is ccmfiguredtorequiielhesevertosusper^ second meeting element and transmit the third meeting element during the suspension of tie transmission ofthe second meeting dement

2 The virtual collaboration system of claim 1, wherein when the server transmit the second meeting dement stored in the storage device to the computer tenrnnals, when fere is li^

indicating a fourti meeting dcinent

second meeting dement, the server suspends the transmission of the second meeting dement at a point in time when the forth meeting dement has been inserted and transmits lhe forth meeting dement to the computer tenriinals, and (he server resumes the trdnsmission of the second meeting dement when having finished the transmission ofthe forth meeting dement

3. The virtual coflaborarion system of daim 1 , wherein the meeting dements include at least one of audio data, image data, figures hand-written by a user, and ch-ffadierstnhgsir -ttedbyauser.

4. The virtual collaboration system of ^

meeting dement as a separate data unit

5. The virtual collaboration system of claim 1 , wherein any one ofthe computer tenrnnals is configured to specify' tie user ID in tie second attribute information.

6. The virtual collaboration system of daim 1 , wherein when the server sends the second meeting element stored in the storage device to the computer terminals, the server reads out and send the second meeting dement whose data type is the same as a data type specified by any one ofthe corrrputertmrrinals.

7. A method for a holding a video meeting by using a virtual colaboration system having a server and a plurality of computer terminals which are corrected to a network arclociri^

steps of

(a) transmit a meeting dement to the server through the network from one ofthe computer tenrrinals trough the network;

(b) receiving on the server the transmitted first meeting, and transrnitling tie received first meeting dement to the computer tenriinals through the network; (c) receiving and reproducing the first meeting dement transmitted from the server through the network

(d) storing in the storage device the first meeting dement having been received on the saver and first attribute information rreduding a first time of recdving the first meeting dement and auser ID of auserof a computer terminal from which the first meeting dement was transmitted, in correlation to each other,

(e) reading from meeting dements stored in the storing device into the server, a second meeting dement which has been correlated to second attribute information including a second time of receiving the second meeting dement and a second user ID, and tartsrnitringme second meeting d mert

network;

(f) receiving and ieprcducing on the computer terminals the transmitted second meeting dement;

(g) when a suspension request for requiring suspension of the transmission of the second meeting dement is inputted in any one of the computer terminals, transmiri^

the network;

(h) receiving on the server the suspension request on the server, and suspending the transmissian of the second meeting dement

(i) trar-smitting a r ini meeting derne^

network while the transmission of the second meeting dement is suspended;

φ receiving cnth-serverme

and storing in the storage device the recdved tiiiid meeting dement and third attribute rn&imation induding a third time of receiving the third meeting dement and a third user ID of a user of the one of the computer terminals from which ttK third meedrig dement has b

(k) when storing the third meeting element having been nxcived on the sever and the third attribute information, storing link irfomrarion between the third meeting dement and the second meeting dement; and

(1) resuming the transmission of the second meeting dement when the transmission of the third meeting element has been finished;

(m) when storing the first meeting dement having been received on the sever and the first attribute ^formation at step (d), storing Mnk information between the second meeting dement and the first meeting dement

8. The method ofdaim 7, wherein the step (e) indudes the step of

(n) when there is link information, stored in the storage device, indicating a fourth meeting dement which is stored in the storage device and has bem ins^

transmission of the second meeting dement at a point in time when me fourth dement has been inserted, men transmittingthe fourth meeting element to the computer terminals, and when the transmission of the fourth meeting dement has been finished, resinning the transmission of the second meeting dement

9. The method of claim 7, wherein the meeting dements indude at least one of audio data, image data, figures handwritten by a user, and character strings inputted by a user.

10. Themethod of darm 7, wherein the first attain

meeting dement

11. The method of daim 7, comprising the step of

(o) transmitting through the network auser ID havingbeen inputted in any one ofthe ccrrpjter terminals therefrom, and receiving the transmitted user ID an the server,

wherein when rrarsTirtring the sera

ccmputer terminals at step (e), reading out the second meeting dement which is correlated to the attribute inforrnation containing the same ID as the user ID received on the server, into the sever, and then transmitting the read out second meeting element

12. The method of claim 7, comprising thestepofi

(p) trananitting data type information, which has been inputted in any one ofthe cxjrnputer terrninals and indicates adata typeofthe data having been inputted in any one of the computer terminal, from the any one of the computer terminals to the server through the network, and receiving the transmitted data type infomiation on the server,

wherein when trarm^tdng the second meeting dement stored in the storage section to the computer terrninals at step (e), reading out the second meeting element wtase date type is the sameas the c¼rar

type information received on the server, into the server, and then transmitting the read out second meeting dement

13. A computer-readable imarding medium storing aprogram for making a serverand a plurality of computer terrninals to execute a method for holding a video meeting by using a virtual collaboration system having the server and tie plurality of computer terrninals which are connected to a network and communicable to each other, the method comprising the steps of:

(a) transmit a meeting dement to the

through the rbstwork; (b) receiving on the server the transmitted first meeting, and transmitting the received first meeting element to the computer terminals through the network;

(c) receiving and ieproducing the first meeting dement transmitted from the server through the network

(d) storing in the storage device the first meeting dement ha\dng been re^

attribute irribrmarion including a first time of receiving the first meeting dement and a user ID of a user of a computer terminal from which the first meeting dement was transmitted, in correlation to each other;

(e) reading from meeting dements stored in the storing device into the server, a second meeting dement which has been correlated to second attribute information mduding a second time of receiving the second meeting dement and a second user ID, and tianarriiflinglhesecoixi meeting

network

(f) receiving and repirxtucing on the computer terminals the transmitted second meeting dement;

(g) when a suspension request for requiringsuspensionofttetra.^

is inputted in any one of the computer terminals, transmitting die inputted suspension request to the server through the network

(h) receiving on the server the suspension request on the server, and suspending the tranai-iission of the second meeting dement;

(i) transmitting a third meeting element from the one of the computer terminals to the server through the network while the transmission of the second meeting dement is suspended;

0 receiving on the server the third meeting dement trarsmitted from the one of the computer terminals, and storing in the storage device the received third meeting dement and third attribute information induding a third timeofrecdvir¾ the third meetir¾ element

which the thiid meeting dement has been transmitted, in ccnxMrai to each ofl^

(k) when strjring the third meeta^

information, storing link information between the third meeting element and the second meeting dement; and

(1) resuming the transmission of the second meeting element when the transmission of the third meeting dement rasbem finished;

(m) when storing the first meeting dement having been received on the sever and the first attribute iribrrriation at step (d), storing link information between the second meeting dement and the first meeting element

14. The corrpjtter-readable recording medium of daim 13, wherein the step (e) includes the step of

(n) when there is link iiifomiation, stored in the storage device, indicating a fourth meeting dement which is stca¾d m the storage device arri hasbeen transmission of the second meeting clement at a point in time when the fourth dement has been inserted, then transmitting the fourth meeting element to the computer terminals, and when the transmission of the fourth meeting element has been finished, resuming the transrnission of the second meeting dement

15. The computer-readable recording medium of claim 13, wherein the meeting dements include at least one of audio data, image data, figures harci-written by a user, and character strings inputted by auser.

16. The computer-readable recording medium of claim 13, wherein the first attn¾uleiiif rrnarion is stored as a (liferent data unit from the first meeting dement

17. The ccrnputer-readable reocrcfogmediurn of claim 13, wherein the method comprising the step of

(o) transmitting through the network a user ID having been inputted in any one of the computer terminals rherefmrn, and receiving the transmitted user ID on the server,

vAerein when transmitting the secorxl meeting element storedmthe storage sec^

computer terminals at step (e), reading out the second meeting dement which is corrdated to the attribute infbrm-aion contairrm

read out second meeting dement

18. The cornputer-readable recording medium of daim 13, wherein the method comprising the step of

(p) transrrritrjngdata type information, which has been inputted in any one of the computer tierrninals and indicates a data typeof the data havmgbeen inputted in any one of the computer terminal, from the any one of the COTnputer terminals to rJie server to

server,

wherein when trarismirfing the seoondmeetm

at step (e), reading out the second meeting demeri whose data type istr^ same as tte

type information received on the server, into the server, and then trar-srmtting the read out second meeting dement