JP2006146415A - Conference support system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a conference support system with improved convenience, capable of totally supporting a conference by integrating video/voice recording and reproducing function, blackboard writing function, personal memo function or the like for the purpose of supporting the conference to form various contents (data) by each function so that they can be referred to/utilized in association with each other. <P>SOLUTION: This conference support system comprises at least a conference application group for recording context information attached to conference items or the like, and a content management application for managing conference application documents generated by the conference application group in association with each conference. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a conference support system that electronically supports a conference.

  In a conventional conference support system that supports conferences electronically, information provided by each participant to a public place is distributed and shared on the handset of all participants and a common screen that all participants can view. Furthermore, all the participants have simultaneously edited the shared information and provided a function for expressing (displaying, etc.) the results in a consistent and real-time manner.

  EKC-Canvas (Canvas), eKC-Personal Cabin (PCab), Meeting Capture (MC), Interactive Station (IS), AssociaPad (AP) ) 5 applications are also well known. Each of these applications has already been proposed individually by the applicant of the present application. These applications will be further described later.

  However, when implementing such functions, the complexity of the programs that make up the system consumes a large amount of computing resources and tends to cause a decrease in operating speed, reliability, and robustness.

  In addition, when participants refer to the same information, it is possible for participants to refer to information with a common line of sight using a large screen, rather than distributing it to each person with paper or displaying the information on their terminals. It is also empirically known that it is effective for promoting sharing and concentration of information. Furthermore, the method of distributing the screen to each terminal is very different from the conventional conference style using a normal white board (blackboard) as a large screen with a common line of sight. There is also a problem that it is difficult to supply a high system.

  In addition, such a function provides the convenience of not having to print the paper on paper, but it can capture the contents of the meeting reliably, and the contents of the meeting (decisions, conclusions, problems, etc.) ) Cannot be said to support strengthening the essential role of the meeting, such as ensuring that members can do it after the meeting. In other words, it is hard to say that all members are surely sharing the context of the meeting.

  Therefore, the applicant of the present application simplifies the system by eliminating the need for synchronization processing in each information processing apparatus used by the conference participants, focusing on a large screen sharing the line of sight, and an information posting function and a board on it. The meeting support system of patent document 1 is proposed as a meeting support system which incorporated the function and the attribute assignment function as a support function.

  In the conference support system of Patent Document 1, a function for attaching a predetermined attribute to an object constituting a discussion process described in an editing area has been proposed. For example, the attributes shown in Patent Document 1 are simply pasted with labels (such as “conclusion” and “task”) that are simply expressed differently, such as a label character string, and an object is extracted according to the difference in the label and displayed in a predetermined view. It is intended to be viewed. Further, Patent Document 1 describes that a conference document described by the conference support system can be stored and stored in a document management system on a network.

  By the way, in the case of an operation system centering on a whiteboard metaphor as in the conference support system described in Patent Document 1, there is a degree of freedom in arrangement, but on the other hand, the user needs to input while always being aware of the layout. There is a demerit that there is.

  In addition, since the resolution of a large electronic display is not high compared with a conventional whiteboard that writes with ink markers, there is a demerit that the user is dissatisfied with the “writing” function in a system that mainly uses handwriting. .

  Furthermore, replacing the conventional whiteboard method with electronic means has advantages such as paperlessness, but it is difficult to set the advantage in terms of utilizing the information itself in the subsequent process, so the user's merit is diminished. become.

  In addition, as related to attribute assignment, when an attribute is simply a label character string, there is a problem that the expression differs even for a label indicating the same intention. Specifically, for example, a label indicating the result of the discussion can express “conclusion”, “result”, “decision item”, and the like. For this reason, it is difficult to make the meaning of the attribute machine-readable.

  In addition, Patent Document 1 also describes providing a search service for conference documents stored in storage on a network. For example, attributes attached to an object when information is shared among conference participants are described. It does not mention the provision of information. In addition, since the expression and meaning of the attribute vary depending on the user as described above, the user who has added the attribute to the object is not necessarily generated even though the view can be generated by extracting the object due to the difference in the expression of the assigned attribute. The view does not always reflect the intention of

  In addition, the user can easily write and erase information on the screen on which information video is displayed with a pen, etc., and quickly obtain shooting data of the subject on the front of the screen on the spot. A conventional white board that can shoot a display image on the screen and a moving image of the subject on the front of the screen at the same time, and is intended to provide a writable display device suitable for a video conference system. Patent Documents 2 and 3 propose a display device mainly for a large screen, which is a combination of the “pen writing function” and an electronic display.

  In addition, in connection with conference support systems, in recent years, with the development of telecommunications technology, video conferencing systems that capture the state of conferences and transmit the acquired images to remote locations will be used by many companies and organizations Became. In order to further improve the convenience of such a system, a number of devices for capturing the state of a conference as a video and a system for transmitting a partial video obtained by cutting out only a speaker have been proposed.

  As a prior art of such a system, for example, Patent Document 4 (“video conference system”) is cited. Patent Document 4 discloses a technology relating to a video conference system in which a voice input from a microphone is detected to determine a speaker, a camera control unit automatically controls the camera based on the determination result, and the speaker is captured. ing.

  Further, Patent Document 5 (“TV camera device”) is related to this. Patent Document 5 discloses a technique relating to a television camera apparatus using a fish-eye or super wide-angle lens and a variable directivity microphone. Specifically, an invention is disclosed in which the direction of a sound source position is determined, the sound source position direction is tracked, and an image in the sound source position direction is cut out to generate a video signal.

  In the technique disclosed in Patent Document 5 described above, when the television camera device using a fish-eye or an ultra-wide-angle lens is installed on a desk or the like, generally, a non-critical thing such as a ceiling occupies most of the field of view. There is a problem in that an important subject such as the face of a person is present in the peripheral part of the field of view and is affected by peripheral light reduction and aberration. That is, there is a problem that the conference cannot be viewed efficiently. In addition, when such a lens is used, there is a problem that the calculation for distortion correction greatly depends on the position of the image, and the calculation burden increases. In addition, the design of such a lens or optical system is very difficult and costly.

  In addition, in recent years, in addition to the so-called real-time property that is a feature of the conventional video conference system, there has been a demand to check the content of the conference again. As a solution to this problem, a conference system has been devised that enables the applicant of the present application to maintain a sense of presence in a conference and that can efficiently reproduce the content of the conference. Data recording and playback systems are provided that store video data and video data in a dedicated server device via a network, and retrieve and playback them later. This system has already been disclosed as Patent Document 6.

  In addition, a terminal device that records content data that changes with time, such as moving image data, can also record the recording time, and at the time of recording, it is not necessary to connect the terminal device to a network, and A data recording / reproducing system, a data recording method, a program, and a recording medium capable of accurately adjusting the time between the terminal device and the server device that stores the data without reducing convenience, and In such data recording / reproduction, a data recording / reproducing technique for recording various types of data such as text data and handwritten image data as memo data has been established and published as Patent Document 7. According to this technology, an important portion of moving image data can be easily searched and displayed by writing a memo in a portion that is considered as an important portion that the user wants to reproduce later during moving image shooting.

  In this case, in order to obtain a correct search result, it is necessary that the time correspondence is taken between the recorded and stored moving image data and the memo data (the clock is set). That is, time adjustment is required.

  As a conventional technique for time adjustment, a technique is known in which a clock is synchronized between computers already connected to a network using a protocol called NTP. Furthermore, Patent Document 8 proposes an improved method for improving the efficiency of time synchronization processing using NTP.

  Time adjustment by NTP as shown in Patent Document 8 can also be used in a data recording system which is the technical field of the present invention. In the moving image search system of Patent Document 1 described above, the time can also be synchronized between the moving image recording device and the local terminal device using such a synchronization processing method. That is, the time is synchronized between a terminal device (recording device) that takes in (records) moving image data and the like and a server device that stores the data using a synchronization method using NTP.

  However, in order to realize such synchronization, it is necessary to always connect the respective devices to a network. Therefore, if the connection of the terminal device at hand is to be realized by a cable, it is inconvenient to handle. There is a problem that there is a problem, and there is a problem that it is expensive when it is realized by the wireless LAN. In addition, it is conceivable to synchronize the time in advance and not to connect when using the terminal device at hand, but such a method complicates the use procedure and reduces convenience. For example, when participating in a meeting in an office with a personal terminal device, it is necessary to connect the cable to the terminal device in advance and perform the time adjustment process. If you bring it to the conference room, even if you perform a memo recording operation, there is a possibility that an accurate search cannot be performed later due to a time error.

JP 2003-111042 A JP 2003-94886 A JP 2003-143348 A Japanese Patent Laid-Open No. 5-12289 Japanese Patent Laid-Open No. 11-331827 JP 2003-18561 A JP 2003-323356 A JP 2000-349791 A

  Each conventional technique for conference support described so far is also intended for conference support, but each system functions independently. Therefore, when using these systems in a meeting, the content created by each system is not linked. For example, each content such as content composed of video / sound, content created by a board, and content created by taking a note by an individual is managed by the system alone.

  Therefore, in the present invention, for the purpose of conference support, each known system that integrates individual known systems supporting various conferences having various functions such as a video / audio recording / playback function, a board writing function, and a personal memo function is created by each known system. To provide a conference support system that can manage various types of content (data) in association with each conference, can refer to and utilize the managed content in association, can provide total support for conferences, and has improved convenience With the goal.

  For the purpose of solving the above-mentioned problem of Patent Document 1, the applicant of the present application has proposed in Japanese Patent Application No. 2003-409023. That is, Japanese Patent Application No. 2003-409023 provides an environment that allows quick / easy / reliable display / description while concentrating on the discussion, and also facilitates the use of the described information (object) in the subsequent process. The purpose is to make effective use of the information described in the discussion for each individual.

  In Japanese Patent Application No. 2003-409023, in a conference support system having a conference support apparatus that displays an information editing description area for describing discussion contents of a meeting as object information on a display device, the conference support apparatus includes A concept of a line exists in the information edit description area, and a conference support system has been proposed in which various objects are arranged according to the line in the information edit description area.

  A conference support device that edits an object that is personal knowledge transmitted by a conference participant via an information processing device and displays an information editing description area for describing information to be the object on a display device. In the conference support system, a concept of a row exists in the information edit description area of the conference support apparatus, and a conference support system in which various objects are arranged in the information edit description area according to the row. It is disclosed.

  Alternatively, in a conference support system having a conference support apparatus configured to display an information edit description area for describing discussion contents of a meeting as object information on a display device, the information described in the information edit description area is stored on a network. A conference support system is also disclosed in which the information stored in the storage means can be browsed using the browsing means of the information processing apparatus.

  In addition, Japanese Patent Application No. 2003-409023 includes an information edit description area for editing an object which is personal knowledge transmitted by a conference participant via an information processing apparatus and describing information to be the object. In a conference support system having a conference support apparatus configured to be displayed on a display device, information described in the information editing description area is stored in a storage unit on a network, and the information stored in the storage unit is stored in the information processing There is also disclosed a conference support system that enables browsing using the browsing means of the apparatus.

  In addition, the embodiment described in Patent Document 7 described above is intended to write a memo in a location that the user thinks is important to reproduce later during video recording, but is currently commercially available. The handwritten memo or text memo input function of mobile terminals is generally difficult to use and takes time to input. Therefore, attention is paid to memo input work and important stories are inadvertently heard. There is a risk. In addition, “an important part to be reproduced later” is not limited only by the arbitrary operation of the user as described above. For example, if you temporarily leave while you are attending a meeting due to an unforeseen circumstance such as interruption of other work, you will naturally want to replay the scene after the meeting. In the embodiment described in this prior art, this is the case. There is no effect in various scenes. A technique that solves these problems has been proposed by the present applicant (Japanese Patent Application No. 2003-64228).

  The present invention includes a technique obtained by further improving Japanese Patent Application Nos. 2003-409023 and 2003-64228, and solves the problems of Patent Documents 1 to 8 described above. The application (conference application) that provides the function to support the conference, which is assumed as an object to be associated with the content in the present invention, is eKC-Personal Cabin (PCab), eKC-Canvas (Canvas), Meeting Capture (MC), The five applications are Interactive Station (IS) and AssociaPad (AP). A document (conference application document) generated by each of these applications and recorded in the respective formats is handled as a “conference document”.

  The conference support system of the invention described in claim 1 is for managing a conference application group for recording context information attached to a conference proceeding and the like, and a conference application document generated by these conference application groups in association with each other. And at least a content management application.

    The conference support system of the invention described in claim 2 is a first conference application group for recording a conference proceeding as a conference application document, a second conference application group for recording streaming data attached to the conference proceedings, and the like, And a third conference application group for managing the conference application document and the streaming data in association with each other in a conference unit.

    According to a third aspect of the present invention, there is provided a conference support system comprising: an agenda recording means for recording contents in association with recording times of the contents; an agenda data registration means for registering each agenda data created by the agenda recording means; Video recording means for recording a scene, video data registration means for registering video data created by the video recording means, and agenda data management means for managing the agenda data and the video data in association with each other as common agenda data Agenda data designating means for designating desired agenda data among the agenda data managed by the agenda data management means as first agenda data; and content designating means for designating desired content in the first agenda data And second of the agenda data managed by the agenda data management means Reference means for referring to the agenda data, the reference means for referring to the content in the second agenda data corresponding to the recording time associated with the content in the first agenda data designated by the content designation means It is characterized by having.

    The meeting support system according to the invention as claimed in claim 4 comprises: a content recording unit configured to receive content input; and an attribute recording unit configured to provide a predetermined attribute to a desired content among the input content; Agenda data management means for managing agenda data created by the agenda recording means, and reference means for referring to desired agenda data among agenda data managed by the agenda data management means, Reference means for referring to the content in association with the type of attribute assigned to the content by the attribute assigning means.

    According to a fifth aspect of the present invention, in the conference support system according to the third aspect, the conference recording means for recording the conference content in association with the recording time of the content, and the conference data created by the conference recording means are registered. Proceedings data registration means, streaming data recording means for recording a meeting scene, streaming data registration means for registering streaming data created by the streaming data recording means, proceedings data created by the proceedings recording means, Management means for managing the streaming data created by the streaming data recording means in association with each other, content specifying means for specifying desired content in the agenda data, and playback means for playing back the streaming data associated with the agenda data Ah , And having a reproducing means for reproducing a scene corresponding to the time associated with the designated content by the content specifying means.

    A sixth aspect of the present invention is the conference support system according to any one of the third to fifth aspects, wherein at least one of the proceeding recording means is a canvas.

    According to a seventh aspect of the present invention, in the conference support system according to the sixth aspect, the agenda data created by the agenda recording unit is stored in a storage on a network and converted into a view set for each user by the browsing unit. It can be referred to.

    The invention described in claim 8 is the conference support system according to claim 6 or 7, wherein “semantic attribute” and “visual attribute” are defined as attributes to be given to the agenda data created by the agenda recording means. It is characterized by.

    The invention according to claim 9 is the conference support system according to claim 8, wherein “shared information”, “user information”, and “date / time information” are defined as internal values of the “semantic attribute”. And

    According to the tenth aspect of the present invention, in the conference support system according to the ninth aspect, by giving “semantic attribute”-“shared information”, the object has the meaning of “information shared by all members”. As a specific operation, the agenda data with “semantic attribute” − “shared information” is picked up and displayed in a predetermined view of the browsing means of all members.

    The invention described in claim 11 is the conference support system according to claim 9, wherein the meaning of “information associated with the designated user” is given to the object by assigning “semantic attribute”-“user information”. As a specific operation, the agenda data to which “semantic attribute”-“user information” is assigned is picked up and displayed in a predetermined view of the browsing means of the designated user.

  The invention according to claim 12 is the conference support system according to any one of claims 3 to 5, wherein at least one of the proceeding recording means is IS.

  The invention according to claim 13 is the conference support system according to any one of claims 3 to 5, wherein at least one of the proceeding recording means is an AP.

  According to a fourteenth aspect of the present invention, in the conference support system according to the third aspect, the video recording means is an MC.

    The invention described in claim 15 is the conference support system according to claim 4, wherein at least one of the proceeding recording means is IS.

    The invention described in claim 16 is the conference support system according to claim 4 or claim 10, further comprising registration means for registering with a predetermined attribute set in advance when registering the agenda data. And

    The invention according to claim 17 is the conference support system according to claim 4, wherein the proceeding recording means is an MC.

  According to the present invention, various contents (data) created by each function by integrating various functions such as a video / audio recording / playback function, a board writing function, and a personal memo function for the purpose of meeting support for each meeting. It is possible to obtain a conference support system that can be managed in association with each other and can be referred to and utilized in association with each other.

[Summary of the Invention]
[Conference application] As an application (conference application) that provides a function to support a conference, what is assumed as a target in the present invention is eKC-Personal Cabin (hereinafter referred to as a front-end application that performs content management and serves as an operation interface). PCB for short), eKC-Canvas (hereinafter abbreviated for Canvas), Meeting Capture (hereinafter abbreviated for MC), Interactive Station (hereinafter abbreviated for IS), and AssociaPad (hereinafter abbreviated for AP for short). ), But any conference application that has similar functions (content management function, conference management function, minutes management function, conference data creation function) can be applied to systems using these applications. .

  In the present invention, the functions of these applications are linked so that documents (conference application documents) generated by the respective applications and recorded in their respective formats (conference application documents) can be handled uniformly as “conference documents”. ing. Note that the conference document generated by the MC is video data.

[First Embodiment]
Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is an explanatory diagram showing the basic concept of an embodiment of the present invention. FIG. 2 is a block diagram showing the hardware configuration of the system according to this embodiment.

  [Overall System Configuration] The machines constituting the system of FIG. 2 are a platform server, eKC-Canvas machine, IS machine, MC machine, AssociaPad machine, eKC-PersonalCabin server, streaming server, and a plurality of client machines. The eKC-Canvas machine, IS machine, MC machine, and AssociaPad machine are collectively called capture machines, and the eKC-Canvas, IS, MC, and AssociaPad applications running on each machine are collectively called capture applications. “Backyard” in this system refers to the platform server, and the capture machine, eKC-PersonalCabin server, and streaming server are clients when viewed from the backyard.

  The platform server in the present embodiment includes a database that stores a data group of the system, a repository service that stores and retrieves various data in the database, and a Web service that provides various functions to clients. The repository service has a function of connecting to a database, storing data as records in various tables existing in the database, and acquiring a record from any table in the database. The Web service has a function to register data in various tables using the repository service, and to collect data from various tables using the repository service, and to collect data requested by the client. It has a function to process and return to the client.

  That is, as will be described later, in the present system (see FIG. 5), there are nine tables for storing various data as a database. That is, a meeting document table, a personal information table, a ToDo information table, a document information table, a user information table, an organization information table, a meeting room information table, a group information table, and a holding meeting table, which will be described in detail later.

  In the repository service, there are nine services that will be described later in detail in order to create a table object for each table in the database and store data or acquire data. In addition, the Web service includes eight services that will be described in detail later in order to properly use the nine services of the repository service and execute processing desired by the client. Each service has an operation function (called a method) for operating each table (see FIG. 27).

  First, an outline of each of the above five applications related to the present invention will be described. Note that details not mentioned here will be described as appropriate in specific usage examples which will be described later in detail.

  [PCab] PCab, which is a front-end application, is a Web application that manages and references documents (conference application documents) created by other conference applications (Canvas, MC, IS, AP) in association with each conference. . In the actual system configuration, PCab is a front-end application for performing these operations, and this front-end application is configured to access a database via various service groups. In the following, for ease of explanation, PCab will be described as an application system that includes front-end functions, services, and databases.

  Each document generated by each conference application is associated with each conference by an operation of uploading each document to a “conference document” defined in the PCab. In PCab, the display contents are customized for each user. For example, on the top screen, the conference scheduled for today is displayed (details will be described later). Therefore, it is assumed that the user logs in to the PCab before using the PCab.

  An overview of the "Refer to meeting document" function, which is one of the main functions of PCab, will be described. The first reference form in which the PCab refers to the conference document is a mode in which “conference” is designated, the “conference application document” associated therewith is further designated, and the desired “conference application document” is displayed and referenced. It is.

  According to the second reference form, the heading of the document or object is picked up and highlighted in a specific view in accordance with a predetermined “attribute” attached to the “conference application document” or “object in the conference application document”. It is a form referred to. In this case, if the highlighted headline is a document headline, it is linked to a view displaying the document contents. If the highlighted heading is an object, it is linked to a view displaying the object or a view displaying the corresponding document by highlighting where the object appears.

Specifically, the attributes here are a “shared information” attribute and a “user information” attribute that express the following two types of contexts that are considered to be important in a conference. Give an example.
(1) “Because it is an important item, mark it and remember it together”
(2) This should be investigated by Mr. A by the next time. ”
As described above, the “shared information” attribute corresponds to the attribute of (1) context, and the “user information” attribute corresponds to the attribute of (2) context.

  The “user information” attribute has “person” as a value. In the above example, for example, the character string “Mr. A” is used. In an actual system, “Mr. A” is information that can identify a person, such as a user ID and an account name.

  For example, when the “shared information” attribute is added, the specific view that displays the document or the object with the above attribute is a view called “notice” of the Personal Cabin of all the participants in the conference. When the “user information” attribute is added, the view is “ToDo” of the personalCabin of the user.

  [Canvas] Application Canvas is the first (type) proceedings recording means, and is a software application that supports board writing at the meeting site. It runs on a NotePC brought into the conference room or a PC that is equipped for the conference. Canvas generates a Canvas document having information that is referred to or written at the conference site, such as text, handwriting, and files. In the Canvas document, some attributes described later and the content generation time are recorded in association with the content. The structure of the recording data in Canvas will be described in detail later.

  [MC] Application MC is an application for recording and reproducing video and audio (hereinafter simply referred to as video) at the conference site. The MC recording application is software that runs on a special camera (a camera with a 180 or 360 degree field of view) and a PC to which it is connected. The recorded video data is sent to the MC server and stored as an MC document. The stored video can be played back by the MC playback application configured as a Web application and referenced by the user.

  [IS] Application IS is a second agenda recording means and is an application that supports handwriting with an ink pen (normal whiteboard marker pen). It consists of hardware consisting of a rear-projection display and a camera, and a PC connected to this hardware that displays conference materials. The software that controls the hardware runs on the connected PC. The IS display surface can be written with an ink pen. The written information is associated with the PC screen displayed at that time, and is taken into the PC as an electronic document. For example, when a presentation material is displayed on a PC at a meeting and written directly with an ink pen on the display and a predetermined operation is performed, the IS document is superimposed on the handwritten information written with the ink pen and the display page of the presentation material. Generated.

  [AP] Application AP is a third means for recording proceedings and is a tool for taking personal notes during a meeting. It is a software application that runs on information terminals brought in by conference participants, such as PDAs or NotePCs. The user activates the AP on his / her information terminal during the meeting. During the meeting, the user presses the operation button on the AP when he thinks the current discussion is important. When the operation button is pressed, the current time is stored. When the button is pressed, text such as a comment or memo can be entered as necessary. The input text is associated with the time and stored together with several bibliographic items and generated as an AP document.

  The individual conference applications have been briefly described above. A user who uses the present system browses and registers a conference document using an appropriate one of the applications described above, so that the entire conference proceeds. That is, a conference document with a conference ID is created, stored, and referenced for each conference by a Web application serving as a front end. The substance of the conference document is assumed to be stored with a predetermined bibliographic item with a conference ID assigned to the database described in “Detailed description of platform and data structure”.

  In this system, it is necessary to first register organization information and conference room information as advance preparations. Registration of organization and conference room information is not permitted for general users, and the system administrator has a policy of registration / edit / deletion as necessary. In addition, a user who uses this system needs to perform user registration in advance. User registration can be performed by following the link from the login screen of eKC-PersonalCabin, and can be realized by the user registration method of the user management service of the Web service.

  [Usage Method] This system assumes the usage method shown in FIG. In other words, preparation before the meeting, downloading / uploading of data during the meeting, editing and browsing after the meeting. The user can advance the conference using this system in the order of before, during, and after the conference, and can connect to the next conference. There are start (1) and start (2) in the start position. Start (1) is a case where a conference is reserved in advance, a conference is held using the reserved conference, and the conference is viewed after the conference. Start (2) is a case where a new meeting is created during the meeting and viewed after the meeting without preparations before the meeting.

  Before the conference, you can use eKC-PersonalCabin to prepare for the conference. First, a new conference is reserved using the conference reservation method of the Web service conference registration service. When a conference is booked, an email notification can be sent using the email service's event notification method. In addition, the conference material can be registered by using the conference material registration method of the web service conference registration service.

  [Conference Document Creation;] The user creates a conference document on the PCab by two kinds of operation methods. The first method is a method of creating from PCab. The user logs in to the PCab before the conference and creates a conference by a predetermined operation (conference reservation operation). That is, the user performs an input operation of predetermined bibliographic items such as the meeting name, the date and time of the meeting, the participating members. By performing a registration operation after the input operation, a unique conference ID is generated by the system and a conference document is created on the database. This is performed by a “conference document service” described later. The conference application document created by the conference application is registered by specifying the conference document from the conference application.

  The second method is a method performed directly from the conference application. The user activates the conference application at the conference site without operating anything prior to the conference. For example, start Canvas on a NotePC brought to the meeting. Write a board on Canvas while discussing. After the conference ends, the Canvas document is registered in the server using the “Upload to Server” function of Canvas.

  During a meeting, you can use a capture application (for example, eKC-Canvas) to download a meeting reserved before the meeting or download the data of a meeting that was held in the past using the batch download method of the meeting connection service of the Web service. . Or you can hold a meeting right away with a capture application without downloading. If you want to end the conference, upload the application data of the capture application using the batch upload method of the conference connection service of the Web service, and save the data (content) with the semantic attribute created in the capture application to the platform server. Is done. At this time, if a new upload is selected, a new conference is created and application data is uploaded. If an update upload is selected, an existing conference can be overwritten and uploaded to the platform server.

  In the registration operation, first, a login process is performed by a “user management service” described later. Next, a “conference document service” to be described later is called, and a conference document with a unique conference ID is created on the database. As the minimum bibliographic information for referring to this conference document later, the conference name is input during this operation. Also, the account used in the login process is added to the bibliographic information as owner information.

As described above, the procedure for registering the application document in the conference document according to the first method or the second method described above is as follows. Take. That is,
(1) Perform registration operation from the conference application ("Upload to server", menu selection, etc.).
(2) When the login prompt is displayed, enter the server name, account, and password.
(3) On the server, a list of existing conferences where the logged-in user is the owner or participant is obtained from the database and displayed.
(4) The user selects a conference from existing conferences (reserved conference by PCab) or inputs a new conference name.
As a result, the application document is registered in the database as a conference document.

  [Assignment of conference ID:] As described above, a unique conference ID is generated for each conference. This conference ID assignment is performed by first preparing a plurality of unique conference IDs in the system and registering each conference. Are assigned in order. Apps that want to link to each conference get on (participate in) a specific conference by specifying the conference ID.

  In this system, in particular, by using the conference open method and conference close method of the conference connection service, a plurality of capture applications can join / leave the same conference. In other words, if a conference is held with eKC-Canvas during the conference in FIG. 3, other capture applications such as IS, MC, and AssociaPad can be added (joint function).

  After the meeting, you can use eKC-PersonalCabin to edit the bibliographic items of the meeting and view the data uploaded by the capture application.

  Editing the bibliographic items of a conference such as changing the name of the conference, adding or deleting participants, can be realized by using the conference editing method of the conference registration service of the Web service. If you want to send the minutes by e-mail, you can use the minutes mail method of the web service mail service. If a participant wants to create a transcript and upload it to this system, it can be realized using the minutes registration method of the web service conference registration service.

  When viewing the minutes, various views are provided. If you want to see the bibliographic items of the conference, you can use the bibliographic item acquisition method of the web service conference browsing service. If you want to see the attention item, you can use the acquisition method of the attention item of the Web service conference browsing service. If you want to see the ToDo, you can use the ToDo acquisition method of the Web service meeting browsing service. If you want to see the contents of the meeting, you can use the meeting content acquisition method of the meeting browsing service of the Web service to acquire and display the application data and contents of the desired capture application. Each of the above browsing can be acquired using a conference (conference ID) as a key, but can also be acquired using a user (user ID) as a key. When acquiring with the user as the key, the personal information of the user is acquired by the acquisition method of the personal information of the conference browsing service of the Web service, and the personal conference, personal task, and personal attention items stored in the acquired personal information Each content can be browsed, and only the information necessary for the user can be provided as a view. In addition, personal information personal meetings, personal tasks, and personal attention items are displayed / hidden, so they can be hidden if the user does not need them, and can be set to display if they think they are necessary. It allows you to customize individual views and view meetings, tasks, and attention.

  In addition, application data of another capture application can be called from application data of a certain capture application. As mentioned above, the application data and content of the desired capture application can be acquired using the method for acquiring the content of the conference of the conference browsing service of the Web service. Since the acquired content has common information that is not related to the capture application, the content of another capture application can be searched using the common information as a key.

  For example, when eKC-Canvas, IS, MC, and AssociaPad are used in the same conference, it is assumed that application data is registered in the same conference document from each capture application by the batch upload method or the single upload method of the conference connection service. In the eKC-PersonalCabin view, application data of a capture application is displayed as content. By searching for the content of another capture application in the same conference document using the content creation date as a key, it is possible to search for content with the same creation date or a similar creation date. In addition, the streaming server has a function to play back the video data or audio data recorded with the date and time as the key, so if you send the creation date and time to the streaming server from eKC-PersonalCabin via HTTP communication, the creation date and time will be the time stamp. Video playback.

  As described above, the platform server includes a database that stores the data group of the system, a repository service that stores and retrieves various data in the database, and a Web service that provides various functions to clients. The repository service has a function of connecting to a database, storing data as records in various tables existing in the database, and acquiring a record from any table in the database. The Web service has a function to register data in various tables using the repository service, and to collect data from various tables using the repository service, and to collect data requested by the client. It has a function to process and return to the client.

  In Figure 2, the database, repository service, and web service are configured on a single machine, but they can be configured on different machines, the database and repository service are on one machine, and the web service is separate. An architecture that can be configured on a single machine is adopted.

  [Architecture] FIG. 4 shows the architecture of this system. As already mentioned, this system consists of a database, repository service, and Web service. This is the most common network system configuration at present. Currently, there are various methods for the architecture that expresses the function group like this system in such a configuration, but the most common method is a combination of Java (registered trademark) technology and application server, or .NET technology. The two are listed as representatives. Although this system can be realized using either of these two architectures, it is implemented using a combination of the former Java (registered trademark) technology and application server, which has already been proven in many ways.

  JBOSS is used as the application server. JBOSS is an open source application server that can provide JavaBeans (modules) developed in the Java (registered trademark) language as applications. By providing the repository service as JavaBeans on the JBOSS server, various functions of the repository service can be used from other applications such as Web services.

  Web services also run on the same JBOSS server, but generally speaking, web services need to use SOAP as a communication protocol, and a function to handle SOAP must be added to the JBOSS server. Therefore, in this system, Apache AXIS is installed on JBOSS. AXIS is a kind of server for expressing Web service functions using SOAP as a communication protocol. Therefore, in this system, the Web service function is realized by building the Web service on AXIS placed on the JBOSS server.

  Various databases currently exist, but MySQL is used as the database because it can use the SQL language and is open source. With the above architecture, database, repository service, and Web service are built.

  Next, how to communicate between each will be described. JDBC, which is a Java (registered trademark) database connection technology, is used between the database and the repository service. If JDBC is used, each table in the database can be handled as a table object, which makes it very easy to store and retrieve data. RMI is used between the repository service and the web service. RMI is a typical communication means of Java (registered trademark) that communicates between two machines connected by a network. Communication between the Web service and the client is performed using SOAP as a protocol. Since SOAP communication has become common nowadays, applications other than capture applications and eKC-PersonalCabin can use various functions of this system according to the SOAP rules. In addition, HTTP data is used between the eKC-PersonalCabin server and the streaming server, and video data and audio data stored in the streaming server can be called from the eKC-PersonalCabin.

  Next, details of each part constituting this system will be described. A detailed configuration diagram of this system is shown in FIG. There are nine tables in the database for storing various data. In the repository service, there are nine services for creating a table object for each table in the database and storing data or acquiring data. There are eight services for executing the processing desired by the client by properly using the nine services of the repository service.

  [Database] As shown in FIG. 6, the database includes a meeting document table, personal information table, ToDo information table, document information table, user information table, organization information table, meeting room information table, group information table, and held meeting table. There are a total of nine tables. The meaning and data structure of the data stored in each table will be described in detail below.

  [Conference Document Table] The conference document table is a table that holds, as a record, a conference document that stores bibliographic items of a conference that can be edited by eKC-PersonalCabin and data created by a capture application. The conference document has a data structure as shown in FIG. That is, bibliographic items, content list, application information list, application data list, and minutes file information.

  Bibliographic items include a conference ID, a conference name, a conference description, a start date and time, a conference room ID and a conference room name, an organizer ID, a participant list, a viewer list, and an editor list. When a conference reservation is made with eKC-PersonalCabin, or when a new conference is created with a capture application, the conference ID is referred to and a non-conflicting ID is generated. Exists to uniquely point to a meeting.

  The name of the conference and the description of the conference are written when the conference is reserved with eKC-PersonalCabin, when the conference is edited, or when the conference name is set with the capture application. The start date / time and end date / time are written as the reservation start date / time and reservation end date / time when the conference is reserved with eKC-PersonalCabin, and when the conference is held and ended with the capture application, the actual start / end date / time of the conference Written as date and time.

  The conference room ID and the conference room name are written when the user selects a conference room name in a conference room information table described later from eKC-PersonalCabin. The organizer ID is the user ID of the person who reserved the conference with eKC-PersonalCabin, and the user ID of the person who logged in to eKC-PersonalCabin is written.

  The participant list, viewer list, and editor list are written when a conference is booked with eKC-PersonalCabin or when the conference is edited, and the participant list is the user ID list and viewer list of those who have joined the conference. Means the user ID list of people who can see the conference from eKC-PersonalCabin, and the editor list means the user ID list of people who can edit the conference from eKC-PersonalCabin.

  The content list is a set of a plurality of contents. Content is a part of application data registered from the capture application. Content such as one line of eKC-Canvas outline, IS base document and captured image, MC video file, audio file, thumbnail, chart data, AssociaPad time stamp corresponds to one content. The data structure of the content is shown in FIG. The content has a content ID, title, creation date / time, update date / time, creator ID, content type, file name, document ID, and semantic attributes.

  The content ID is an ID generated so as not to compete in the content list when the content is registered (uploaded) from the capture application, and exists to uniquely indicate the content. The title is a character string that represents the contents, and a character string set by the capture application, a file name, and the like are written therein. The creation date / time and the update date / time are written with the date / time when the content was created by the capture application and the last modified date / time.

  In the creator ID, the user ID of the person who created this content is written. The content type is a value indicating whether the content is text, an image, or a file, and is automatically written when the content is created by the capture application. As the file name and document ID, the original file name and document ID when the content type is image or file are written.

  The document ID is an ID issued when a file is registered in a document information table described later. The semantic attribute is data that is a key of the present system, and has a data structure as shown in FIG. That is, it has a label, a sharing flag, a user flag, a user ID list, a date / time flag, a current date / time, a start date / time, and an end date / time. The label is a character string displayed on the screen when a semantic attribute is added to the content, and includes “conclusion”, “task”, “ToDo”, and the like, and the user can enter an arbitrary character string.

  The sharing flag is a flag indicating whether or not the content is shared by a plurality of users. When the sharing flag is ON, this content can be shared with users existing in the bibliographic item participant list described above. The user flag and user ID list can determine whether this content is explicitly sent to the designated user. When the user flag is turned on and the user ID is written in the user ID list, this content can be explicitly sent to all users in the user ID list.

  There is ToDo as a concrete usage method. When it is ToDo, it is additionally displayed as ToDo in "Important" of "My room" of eKC-PersonalCabin. The date / time flag, the current date / time, the start date / time, and the end date / time can determine whether or not the content has a meaning regarding time. For example, when the date / time flag is set to ON and the end date / time is set, the time limit of the content is until the end date / time. Combined with a user flag, you can use it as a ToDo deadline.

  The application information list is data indicating which capture application registered the content in the conference document. The data structure is a collection of application information as shown in FIG. 10, and the application information has an application ID and an application identifier.

  The application ID is a unique ID in the conference document and exists to uniquely indicate the application. The application identifier is used to determine which capture application the application ID is, eKC-Canvas is defined as "EKC", IS is "IS", MC is "MC", and AssociaPad is "AP" is doing. If you look at this application information list, you can know the capture application related to the conference document, such as how many eKC-Canvas and how many IS.

  The application data list is a list of data bodies of capture applications registered in the conference document. As shown in FIG. 11, the data structure includes an eKC data list, an IS data list, an MC data list, and an AssociaPad data list. The number of each data is written in the application information list described above.

  The eKC data is data that is uploaded from eKC-Canvas or downloaded to eKC-Canvas. As shown in FIG. 12, the data structure includes an application ID, a content ID list, and eKC unique data. The application ID is an ID uniquely created in the conference document when eKC-Canvas uploads data to the conference document, and is registered and managed as the application identifier “EKC” in the aforementioned application information list. .

  The content ID list is the content ID described above, and is data in which content IDs issued at the same time that content is registered in units of one line of the outline when uploading from eKC-Canvas are collected. This indicates how much of the content list is belonging to eKC-Canvas.

  The eKC original data is data uniquely used by eKC-Canvas, and has an outline structure list, basket list, and Canvas file information as shown in FIG. The outline structure list is data indicating the outline structure of eKC-Canvas. As content, content ID and outline level are retained.

  The content ID is the same as the content ID in the content ID list, and the number of content IDs in the content ID list matches the number of outline structures in the outline structure list. The outline level represents the indent level of each line of the outline.

  The basket list is a group of data received in the eKC-Canvas basket, and each basket has a basket ID, title, file name, document ID, creator ID, creation date, and update date. The basket ID is an ID that does not compete in the basket list, and uniquely indicates the basket. The title is a character string displayed as a title in the basket function of eKC-Canvas. The file name is the file name of the file that holds the contents of the basket. The document ID is a document ID when the file indicated by the file name is registered as a document, and is stored in a document information table described later. In the creator ID, the user ID of the person who transmitted the basket information is written. The creation date / time and the update date / time hold the creation date / time and updated date / time of the basket. Canvas file information holds registration information of a Canvas file created by eKC-Canvas. Since a Canvas file is also registered, it has the file name and document ID as information.

  IS data is data uploaded from IS or downloaded to IS. As shown in FIG. 14, the data structure includes an application ID, a content ID list, and IS unique data. The application ID is an ID uniquely created in the conference document when the IS uploads data to the conference document, and is registered and managed as the application identifier “IS” in the application information list. The content ID list is the content ID described above, and is data in which content IDs issued at the same time that content is registered in units of base documents or captured images when uploading from IS are collected. It shows where from where in the content list is what is belonging to IS. IS-specific data is currently unused because IS complies with the content data specification and has no other data. However, if the IS is changed to have its own data, it can be stored in the IS original data.

  MC data is data that is uploaded from MC or downloaded to MC. As shown in FIG. 15, the data structure includes an application ID, a content ID list, and MC unique data. The application ID is an ID uniquely created in the conference document when the MC uploads data to the conference document, and is registered and managed as the application identifier “MC” in the application information list. The content ID list is an ID of the above-mentioned content. When uploading from the MC, the content ID issued at the same time that content is registered in MC content units such as video files, audio files, thumbnail images, chart data, etc. It is data. This indicates how far the content list is from the MC.

  The MC unique data is data uniquely used by the MC. As shown in FIG. 16, the MC unique data has MC content information including a start date / time, an end date / time, an MC type, a MIME type, and a child content list as a list. Each MC content information corresponds to the content ID list described above. The start date and time and the end date and time are the recording start date and time and the recording end date and time of video data or audio data. Data other than stream data has a start date and time and an end date and time of 0. The MC type and MIME type indicate the type of content, and are used to identify video data, audio data, thumbnail images, chart data, and the like. Here, since the MC itself is identified and the platform is not identified, the data received from the MC is simply stored. The child content list has a pointer to content related to the content as data.

  AssociaPad data is data that is uploaded from AssociaPad or downloaded to AssociaPad. As shown in FIG. 17, the data structure includes an application ID, a content ID list, and AssociaPad unique data. The application ID is an ID uniquely created in the conference document when the AssociaPad uploads data to the conference document, and is registered and managed as the application identifier “AP” in the application information list. The content ID list is the content ID described above, and is data in which content IDs issued at the same time that content is registered in units of time stamps when uploading from IS are collected. This indicates how much of the above content list is belonging to AssociaPad.

  AssociaPad unique data is data uniquely used by AssociaPad, and as shown in FIG. 18, has time stamp information in which unique IDs and heading numbers are collected as a list. Each time stamp information corresponds to the content ID list described above. The unique ID is an ID that AssociaPad itself manages in the application, and the heading number is data for displaying the heading number when displaying the time stamp.

  The minutes file information holds information about the minutes file of the meeting. When uploading from eKC-Canvas, a minutes file is automatically created. In the minutes file, the bibliographic items of the meeting and the content with the semantic attribute sharing flag ON (notice) and the content with the semantic attribute user flag ON (ToDo) are listed as html files. Generated. The generated file is registered as a document, and the document ID and file name are stored in the minutes file information.

  [Personal information table] The personal information table is a table that holds a list of IDs of groups, meetings, and contents related to individual users, and the display / non-display status of the meeting and contents, and personal information for storing What's New information. . The data structure is as shown in FIG. That is, the personal information table holds a user ID, a group ID list, a personal conference list, a personal ToDo list, a personal attention list, and a What's New list. eKC-PersonalCabin has a portal page for each person, allowing you to customize (view / hide settings) each meeting, ToDo, What's New, and attention items. In order to realize this function, the personal information table is an indispensable table.

  The user ID indicates who the personal information is. The user ID is data held in a user information table to be described later, and is an ID that uniquely indicates the user.

  The group ID list has a group ID indicating which group the owner of the personal information belongs to. The group ID is data held in a group information table to be described later, and is an ID that uniquely indicates the group.

  The personal conference list has a conference ID list of conferences in which the owner of the personal information is registered as a participant in a bibliographic item. It also has a status of showing / hiding the conference displayed on the personal portal page.

  The personal to-do list holds a list of to-dos generated from various meetings for the owner of the personal information. Actually, the conference ID and the content ID are held, and the content corresponding to which conference corresponds to the two IDs. It also has a ToDo status that is displayed on the personal portal page.

  The personal attention list holds contents (notices) in which the sharing attribute of the semantic attribute is ON among the meetings in which the owner of the personal information participates. Actually, the conference ID and the content ID are held, and the content corresponding to which conference corresponds to the two IDs. It also has a status to show / hide attention items displayed on the personal portal page.

  The What's New list is registered or changed for six subjects: bibliographic items, application data, ToDo, conference materials, ToDo materials, and minutes of conferences in which the owner of the personal information is a participant. It holds What's New used to display a character string indicating registration or change of the target on the personal portal page. What's New includes a conference ID, content ID, type, status, and update date / time. The conference ID and content ID indicate which content of which conference, type distinguishes six targets, status distinguishes whether it is registered or updated, and indicates the date of registration or change in the update date it can.

  [Document Information Table] As shown in FIG. 21, the document information table exists in files such as meeting materials, minutes files, and ToDo materials registered from eKC-PersonalCabin, or in application data uploaded by a capture application. It is a table for managing files with document IDs so that files can be stored on the hard disk and retrieved at any time. The document information table holds document information as a list. The document information includes a document ID, a conference ID, and a file name. The document ID is data for uniquely indicating the document that can be created by referring to the document information table and generating a non-conflicting ID when the document is registered. The conference ID is data indicating which conference the document is. The file name is the file name of the document.

  [User Information Table] As shown in FIG. 22, the user information table is a table for storing, as a list of user information, information on users who can log in to the system and use various functions. The user information has a user ID, last name, first name, organization ID, password, e-mail address, and description. The user ID is an ID that uniquely indicates who the user is. The full name is a user's full name. The organization ID is an ID indicating which organization the user belongs to, and is managed by an organization information table described later. The password is data necessary for the user to use the system, and is entered when logging in to perform user authentication. The e-mail address is data required when e-mail notification and meeting minutes are sent to participants using eKC-PersonalCabin. The description is a character string that the user can input arbitrarily, and is displayed on the screen when the user information is browsed by the user search of eKC-PersonalCabin.

  [Organization Information Table] As shown in FIG. 23, the organization information table is a table that holds organization names, and holds organization information in a list. The organization information has an organization ID and an organization name. The organization ID is an ID for uniquely indicating the organization, and is issued when registering organization information. The organization name is data that holds the name of the organization (for example, XX department ΔΔ section XX group).

  [Conference Room Information Table] As shown in FIG. 24, the conference room information table is a table that holds conference room names, and holds conference room information in a list. The conference room information has a conference room ID and a conference room name. The conference room ID is an ID for uniquely indicating the conference room, and is issued when registering the conference room information. The conference room name is data that holds the name of the conference room (eg, XX conference room).

  [Group Information Table] As shown in FIG. 25, the group information table is a table that holds a group, which is a set of users, in a list as group information. The group information has a group ID, a group name, a description, a group owner, and a member ID list. The group ID is an ID for uniquely indicating the group, and is issued when registering group information. The group name and description are data holding a character string that describes the name of the group and what kind of group, and can be arbitrarily set by the user. The group owner is the user ID of the person who registered the group information, and only the group owner is authorized to change the group information.

  [Organized Conference Table] As shown in FIG. 26, the organized conference table is a table that holds conference documents currently used in any of the capture applications as a list of held conferences. The held conference has only the bibliographic items and the application information list among the conference documents shown in FIG.

[Repository Service]
As shown in FIG. 5, there are nine services in the repository service, each corresponding to nine tables in the database on a one-to-one basis. That is, for example, when it is desired to operate the conference document table, the operation is performed using the conference document service. Therefore, an operation function (called a method) for operating each table is prepared for each service, as shown in FIG. The details of each service are described in detail below.

  [Conference Document Service] The conference document service is a service that connects to a conference document table in a database by JDBC, and performs operations such as creation and browsing of conference documents. The prepared methods are basically five methods: meeting document creation, meeting document update, meeting document deletion, meeting document acquisition, and meeting document search.

[Conference Document Creation Method] The conference document creation method newly creates and adds the conference document shown in FIG. 7 to the conference document table based on the information transmitted from the client. At this time, the conference document table is referred to, a non-conflicting ID is generated, and stored as a conference ID in the bibliographic item.
[Conference Document Update Method] The conference document update method retrieves the conference document in the conference document table with the specified conference ID based on the information transmitted from the client, changes the content, and overwrites the conference document table.
[Conference Document Deletion Method] The conference document deletion method searches the conference document table with the specified conference ID based on the information transmitted from the client, and deletes the corresponding conference document.

[Conference Document Acquisition Method] The conference document acquisition method searches the conference document table with the designated conference ID based on the information transmitted from the client, and returns the corresponding conference document to the client.
[Conference Document Search Method] The conference document search method searches the conference document table using the search condition transmitted from the client, and returns the corresponding conference document to the client in a list.

  [Personal Information Service] The personal information service is a service that connects to a personal information table of a database through JDBC and performs operations such as creation and browsing of personal information. The prepared methods are basically five methods: personal information creation, personal information update, personal information deletion, personal information acquisition, and personal information retrieval.

[Personal Information Creation Method] The personal information creation method newly creates and adds personal information shown in FIG. 19 to the personal information table based on the information transmitted from the client.
[Personal Information Update Method] The personal information update method retrieves personal information in the personal information table with the user ID based on the information transmitted from the client, changes the contents, and overwrites the personal information table.
[Personal Information Deletion Method] The personal information deletion method searches the personal information table with the user ID based on the information transmitted from the client, and deletes the corresponding personal information.

  [Personal Information Acquisition Method] The personal information acquisition method searches the personal information table with the user ID based on the information transmitted from the client, and returns the corresponding personal information to the client. The personal information search method searches the personal information table using the search condition transmitted from the client, and returns the corresponding personal information to the client in a list.

  [ToDo information service] The ToDo information service is a service that connects to the ToDo information table of the database by JDBC and performs operations such as creation and browsing of ToDo information. The prepared methods are basically five methods: ToDo information creation, ToDo information update, ToDo information deletion, ToDo information acquisition, and ToDo information search.

The ToDo information creation method newly creates and adds the ToDo information shown in FIG. 20 to the ToDo information table based on the information transmitted from the client.
The ToDo information update method retrieves ToDo information in the ToDo information table with the specified conference ID and the specified content ID based on the information transmitted from the client, changes the contents, and overwrites the ToDo information table.
The ToDo information deletion method searches the ToDo information table with the specified conference ID and the specified content ID based on the information transmitted from the client, and deletes the corresponding ToDo information.

The ToDo information acquisition method searches the ToDo information table with the designated conference ID and the designated content ID based on the information transmitted from the client, and returns the corresponding ToDo information to the client.
The ToDo information search method searches the ToDo information table using the search condition transmitted from the client, and returns the corresponding ToDo information to the client in a list.

  [Document Information Service] The document information service is a service that connects to a database document information table by JDBC and performs operations such as creation and browsing of document information. The prepared methods are basically five methods: document information creation, document information update, document information deletion, document information acquisition, and document information search.

The document information creation method newly creates and adds the document information shown in FIG. 21 to the document information table based on the information transmitted from the client. At this time, an ID that does not conflict is generated by referring to the document information table and stored in the document information as a document ID.
The document information update method retrieves the document information in the document information table with the specified document ID based on the information transmitted from the client, changes the contents, and overwrites the document information table.
The document information deletion method searches the document information table with a specified document ID based on information transmitted from the client, and deletes the corresponding document information.
The document information acquisition method searches the document information table with the specified document ID based on the information transmitted from the client, and returns the corresponding document information to the client.
The document information search method searches the document information table using the search condition transmitted from the client, and returns the corresponding document information to the client in a list.

  [User Information Service] The user information service is a service that connects to a database user information table by JDBC, and performs operations such as creation and browsing of user information. The prepared methods are basically five methods: user information creation, user information update, user information deletion, user information acquisition, and user information search.

  The user information creation method newly creates and adds the user information shown in FIG. 22 to the user information table based on the information transmitted from the client. At this time, if the user ID transmitted by the client is already registered in the user information table, an error that cannot be registered with the user ID is returned to the client.

  The user information update method retrieves user information in the user information table with the specified user ID based on the information transmitted from the client, changes the contents, and overwrites the user information table.

  The user information deletion method searches the user information table with the specified user ID based on the information transmitted from the client, and deletes the corresponding user information.

  The user information acquisition method searches the user information table with the specified user ID based on the information transmitted from the client, and returns the corresponding user information to the client.

  The user information search method searches the user information table with the search condition transmitted from the client, and returns the corresponding user information to the client in a list.

  [Organization Information Service] The organization information service is a service that connects to an organization information table of a database through JDBC, and performs operations such as creation and browsing of organization information. The prepared methods are basically five methods: organization information creation, organization information update, organization information deletion, organization information acquisition, and organization information search.

  The organization information creation method newly creates and adds the organization information shown in FIG. 23 to the organization information table based on the information transmitted from the client. At this time, the organization information table is referred to, a non-conflicting ID is generated, and stored as organization ID in the organization information.

  The organization information update method retrieves the organization information in the organization information table with the specified organization ID based on the information transmitted from the client, changes the contents, and overwrites the organization information table.

  The organization information deletion method searches the organization information table with the specified organization ID based on the information transmitted from the client, and deletes the corresponding organization information.

  The organization information acquisition method searches the organization information table with the specified organization ID based on the information transmitted from the client, and returns the corresponding organization information to the client.

  The organization information search method searches the organization information table with the search condition transmitted from the client, and returns the corresponding organization information in a list to the client.

  [Conference Room Information Service] The conference room information service is a service that connects to a database conference room information table through JDBC, and performs operations such as creation and browsing of conference room information. The prepared methods are basically five methods: conference room information creation, conference room information update, conference room information deletion, conference room information acquisition, and conference room information search.

  The conference room information creation method newly creates and adds the conference room information shown in FIG. 24 to the conference room information table based on the information transmitted from the client. At this time, the conference room information table is referred to, a non-conflicting ID is generated, and stored as the conference room ID in the conference room information.

  The conference room information update method retrieves the conference room information in the conference room information table with the designated conference room ID based on the information transmitted from the client, changes the content, and overwrites the conference room information table.

  The conference room information deletion method searches the conference room information table with the designated conference room ID based on the information transmitted from the client, and deletes the corresponding conference room information.

  The conference room information acquisition method searches the conference room information table with the designated conference room ID based on the information transmitted from the client, and returns the corresponding conference room information to the client.

  The conference room information search method searches the conference room information table with the search condition transmitted from the client, and returns the corresponding conference room information to the client in a list.

  [Group Information Service] The group information service is a service that connects to a group information table of a database by JDBC and performs operations such as creation and browsing of group information. The prepared methods are basically five methods: group information creation, group information update, group information deletion, group information acquisition, and group information search.

  The group information creation method newly creates and adds the group information shown in FIG. 25 to the group information table based on the information transmitted from the client. At this time, the ID in the group information table is referred to, an ID that does not conflict is generated, and stored as group ID in the group information.

  The group information update method extracts group information in the group information table with a specified group ID based on information transmitted from the client, changes the contents, and overwrites the group information table.

  The group information deletion method searches the group information table with a specified group ID based on information transmitted from the client, and deletes the corresponding group information.

  The group information acquisition method searches the group information table with the specified group ID based on the information transmitted from the client, and returns the corresponding group information to the client.

  The group information search method searches the group information table with the search condition transmitted from the client, and returns the corresponding group information to the client in a list.

  [Hosted Conference Service] The hosted conference service is a service that connects to the hosted conference table of the database by JDBC and performs operations for joining and leaving the conference. The prepared methods are basically two methods: conference participation and conference exit.

  The conference participation method causes the designated capture application to participate in the conference with the designated conference ID based on the information transmitted from the client. First, it is checked whether or not there is a holding meeting with the designated meeting ID in the holding meeting table. If not, the bibliographic item of the meeting with the designated meeting ID is copied from the meeting document table, an empty application information list is created, and the holding meeting with the designated meeting ID is registered in the holding meeting table. If it already exists, the above processing is not performed. Then, the application identifier specified by the client is registered in the application information list, a new application ID is issued, and returned to the client. With the above processing, the capture application has held and joined the conference.

  The conference exit method causes the designated capture application to exit from the host conference of the designated conference ID in the host conference table. First, the application information of the specified application ID is deleted from the application information list. Then, it is checked whether the application information list is empty. If it is not empty, do nothing. If it is empty, it is considered that all the capture applications have exited, and the held conference with the designated conference ID is deleted from the held conference table. With the above processing, the capture application exits the conference, and when all the capture applications disappear, the conference is terminated.

[Web Service] As shown in FIG. 5, there are eight Web services, and the functions are realized by combining and using nine services of the repository service. As shown in FIG. 27, each service has a method to be provided to the client. The details of each service are described in detail below.

  [Conference Registration Service] The conference registration service provides a client with a conference reservation method, a conference editing method, a conference deletion method, a conference material registration method, and a minutes registration method.

  The conference reservation method creates a new conference using the conference document creation method of the conference document service of the repository service based on the information sent by the client. At this time, only the bibliographic items are stored in the conference document of FIG. 5, and the content list, application information list, application data list, and minutes file information are empty. Further, a personal meeting is added to the personal information list of FIG. 19 by the personal information update method of the personal information service of the repository service. The users to be added are all the users having the user IDs included in the participant list of the bibliographic items of the conference document. What's New (conference ID = conference ID, content ID = -1, type = conference, status = registration, update date = current) Date) is registered as personal information.

  The conference editing method updates the conference by the conference document update method of the conference document service of the repository service based on the information sent by the client. In addition, in the personal information update method of the personal information service of the repository service, the user ID existing in the participant list of the bibliographic item of the conference document is compared with the user ID existing in the participant list of the bibliographic item sent by the client, For the deleted user ID, the individual meeting with this meeting ID is deleted, and for the added user ID, the individual meeting with this meeting ID is added. What's New (Conference ID = Meeting ID, Content ID = -1, Type = Conference, Status = Update, Update date = Current) Date) is registered as personal information.

  The conference deletion method deletes the conference by the conference document deletion method of the conference document service of the repository service based on the information sent by the client. In addition, for the user ID existing in the bibliographic item participant list, the personal meeting with the corresponding meeting ID is deleted by the personal information update method of the personal information service of the repository service. Also, for the user ID existing in the bibliographic item participant list, all information related to the conference ID in the personal information is deleted.

  The conference material registration method registers a file sent from the client as a conference material. First, a new document ID is obtained by creating document information of the document information service of the repository service. Next, enter the file name in the basket title and file name, enter the document ID acquired in the document ID, enter the user ID of the person who registered the conference material in the creator ID, and set the current date and time in the creation date and update date Put in and create a basket. The conference document is acquired by the conference document acquisition method of the conference document service of the repository service, a non-conflicting basket ID is generated by referring to the basket list of the Canvas data, and stored in the basket ID of the basket. Then, the created basket is added to the basket list, and the conference document is updated by the conference document update method of the conference document service of the repository service. Also, what's new (conference ID = corresponding conference ID, content ID = -1, type = conference material, status = registration, update date = current date) indicating that the conference material has been registered is displayed in the bibliographic item participant list. All users are registered with the personal information update method of the personal information service of the repository service.

  The minutes registration method registers the file sent from the client as the minutes. First, a new document ID is obtained by creating document information of the document information service of the repository service. The meeting document is acquired by the meeting document acquisition method of the meeting document service of the repository service, the file name is set as the file name of the minutes file information, and the acquired document ID is set as the document ID of the minutes file information. Update the meeting document using the meeting document update method of the meeting document service. Also, What's New (meeting ID = meeting ID, content ID = -1, type = meeting, status = updated, updated date = current date) indicating that the minutes have been registered in the participant list of bibliographic items All users are registered with the personal information update method of the personal information service of the repository service.

  [Conference Viewing Service] The conference viewing service provides clients with bibliographic item acquisition methods, attention item acquisition methods, ToDo acquisition methods, conference content acquisition methods, conference search methods, and personal information acquisition methods. .

  The bibliographic item acquisition method returns the bibliographic item of the conference document with the conference ID specified by the client to the client. The conference document acquisition method of the repository document conference document service acquires the conference document with the specified conference ID, retrieves the bibliographic items, and returns it to the client.

  The attention item acquisition method returns attention items related to the user with the user ID specified by the client to the client in a list. First, the personal information acquisition method of the personal information service of the repository service is used to acquire the personal information of the user ID specified by the client. With reference to the personal attention list of personal information, the conference document is acquired by the conference document acquisition method of the conference document service of the repository service using the conference ID and content ID as keys, and the corresponding content is extracted. Repeat as many as the number of personal attention in the personal attention list, and return the meeting ID and content list to the client.

  The ToDo acquisition method returns ToDo related to the user with the user ID specified by the client to the client in a list. First, the personal information acquisition method of the personal information service of the repository service is used to acquire the personal information of the user ID specified by the client. Refer to the personal ToDo list of personal information, and use the meeting ID and content ID as keys to acquire the ToDo by the ToDo information acquisition method of the ToDo information service of the repository service. Repeats the number of personal tasks in the personal task list, and returns the task list to the client.

  The conference content acquisition returns the application data and content list of the designated application ID of the conference document of the conference ID designated by the client. First, the conference document of the designated conference ID is acquired by the conference document acquisition method of the conference document service of the repository service. With reference to the application data of the designated application ID of the conference document, the content is extracted from the content list of the conference document using the content ID list as a key. Then, the application data and content list are returned to the client.

  The conference search method returns a list of bibliographic items of conference documents that match the search conditions specified by the client. First, conference documents that match the search conditions specified by the client are acquired in a list by the conference document search method of the conference document service of the repository service. A bibliographic item is extracted from the acquired conference document list and returned to the client as a bibliographic item list.

  The personal information acquisition method returns the personal information of the user whose user ID is specified by the client. Using the user ID specified by the client as a key, the personal information is acquired by the personal information acquisition method of the personal information service of the repository service. Return the acquired personal information to the client.

  [Conference Connection Service] The conference connection service is a service specialized for downloading and uploading application data from a capture application. The client is provided with a batch download method, a batch upload method, a conference open method, a conference close method, a single download method, and a single upload method.

  The batch download method returns a file group related to the designated capture application of the meeting document of the meeting ID designated by the client. First, the conference document is acquired using the conference document acquisition method of the conference document service of the repository service. The application data of the designated capture application is extracted from the acquired conference document, and the content in the content ID list of the application data is acquired from the content list of the conference document. In addition, the file ID is acquired by referring to the document ID in the acquired content list and the original data of the application data. Return the acquired file entity list to the client.

  The batch upload method has two functions. New upload function and update upload function. When the client uses the new upload function, a new conference is created by the conference document creation method of the conference document service of the repository service before uploading. Register the file group sent by the client for the new conference created as application data, analyze the file contents, store it in the conference document, and update it with the conference document update method of the conference document service of the repository service To do. In addition, contents whose semantic attribute user flag is ON are registered as ToDo using the ToDo information creation method of the ToDo information service of the repository service. At the same time, using the personal information update method of the personal information service of the repository service, the bibliographic items of the stored content list for the attention items whose semantic attribute sharing flag is ON and todos whose semantic attribute user flag is ON are used. Each information is added to the personal information of the user ID listed in the participant list and the user ID list of the semantic attribute.

  When the update upload function is used by the client, the application data of the designated capture application is deleted from the meeting document of the meeting ID designated by the client before uploading. Specifically, the conference document is acquired by the conference document acquisition method of the conference document service of the repository service, and the stored application data of the designated capture application and the content list related to the application data are deleted. At the same time, using the personal information update method of the personal information service of the repository service for the attention item whose semantic attribute sharing flag is ON and the ToDo whose semantic attribute user flag is ON in the deleted content list, Each information is deleted from the personal information of the user ID listed in the participant list and the user ID list of the semantic attribute. After that, for the new conference created, the file group sent by the client is registered as application data of the specified capture application, the contents of the file are analyzed and stored in the conference document as the content of the conference document service of the repository service Update with the meeting document update method. In addition, contents whose semantic attribute user flag is ON are registered as ToDo using the ToDo information creation method of the ToDo information service of the repository service. At the same time, using the personal information update method of the personal information service of the repository service, the bibliographic items of the stored content list for the attention items whose semantic attribute sharing flag is ON and todos whose semantic attribute user flag is ON are used. Each information is added to the personal information of the user ID listed in the participant list and the user ID list of the semantic attribute.

  The conference open method prepares to execute download or upload for a conference document with a specified conference ID. In other words, the designated application is made to participate in the conference by the conference participation method of the held conference service. This state continues until the conference close method is executed.

  The conference close method completes download or upload processing for the conference document with the specified conference ID. That is, the designated application is withdrawn from the conference by the conference exit method of the held conference service.

  The single download method acquires application data of a specified application ID and a specified content ID from a meeting document with a specified meeting ID. First, the conference document is acquired by the conference document acquisition method of the conference document service, and data related to the content of the specified content ID is acquired from the application data of the specified application ID. Return the acquired data to the client.

  Single upload methods include new uploads and update uploads. In the case of a new upload, the content sent by the client is registered in the conference document with the designated conference ID. In the case of update upload, the content information of the specified content ID is deleted from the conference document of the specified conference ID, and the personal information service of the repository service for ToDo with the semantic attribute sharing flag ON and the semantic attribute user flag ON Each information is deleted from the personal information of the user IDs listed in the bibliographic participant list and the semantic attribute user ID list. Then, the content sent by the client is registered in the conference document with the designated conference ID. For both new uploads and update uploads, the content whose semantic attribute user flag is ON is registered as a ToDo using the ToDo information creation method of the ToDo information service of the repository service. In addition, for the attention item whose semantic attribute sharing flag is ON and the ToDo whose semantic attribute user flag is ON, using the personal information update method of the personal information service of the repository service, the bibliographic item participant list and semantic attribute Each information is added to the personal information of the user IDs listed in the user ID list.

  [User Management Service] The user management service is a service that manages information on users who use the system and performs user authentication such as login. In the user management service, a login method, a user registration method, a user editing method, a user deletion method, a user information acquisition method, and a user search method are provided to the client.

  The login method authenticates whether the user ID specified by the client is a user who can use this system. First, user information is acquired by the user information acquisition method of the user information service of the repository service using the specified user ID as a key. At this time, if the user information does not exist, the specified user ID is not registered, and an error indicating that the system cannot be used with the specified user ID is returned to the client. If the user information exists, the password sent from the client is checked against the password of the user information. If they do not match, an error is returned to the client indicating that the password is incorrect. If they match, return success to the client.

  The user registration method registers new user information for the client to use this system. First, user information is generated based on information sent by the client. Then, user information is registered by the user information creation method of the user information service of the repository service. At this time, it is checked whether the user ID specified by the client already exists in the user information table, and if it exists, an error in which the specified user ID is already used is returned to the client. If not, complete registration.

  The user editing method changes user information already registered in the system. First, user information is acquired by the user information acquisition method of the user information service of the repository service using the user ID specified by the client as a key. The information sent by the client is stored in the acquired user information, and the user information is updated by the user information update method of the user information service of the repository service.

  The user deletion method deletes user information already registered in the system. User information is deleted by the user information deletion method of the user information service of the repository service using the user ID specified by the client as a key.

  The user information acquisition method acquires user information of a user ID specified by the client. User information is acquired by the user information acquisition method of the user information service of the repository service using the specified user ID as a key, and returned to the client.

  The user search method returns a list of user information that matches the search conditions specified by the client to the client. Use the user information search method of the user information service of the repository service to obtain a list of user information that matches the specified search conditions. Return the acquired user information list to the client.

  [Group management service] The group management service defines a set of users as a group and can handle users in groups, or in order to enable various searches using groups as a group information. Is a service for registering, editing, deleting, and acquiring. In the group management service, a group registration method, a group edit method, a group delete method, a group information acquisition method, and a group search method are provided to the client.

  The group registration method registers new group information. First, group information is generated based on information sent from the client. Then, group information is registered by the group information creation method of the group information service of the repository service.

  The group editing method changes the group information already registered in this system. First, group information is acquired by the group information acquisition method of the repository service group information service using the group ID specified by the client as a key. The information sent by the client is stored in the acquired group information, and the group information is updated by the group information update method of the group information service of the repository service.

  The group deletion method deletes group information already registered in this system. Delete group information using the group information deletion method of the repository information group information service using the group ID specified by the client as a key.

  The group information acquisition method acquires group information of the group ID specified by the client. Use the specified group ID as a key to acquire group information using the group information acquisition method of the group information service of the repository service and return it to the client.

  The group search method returns a list of group information that matches the search conditions specified by the client to the client. Use the group information search method of the group information service of the repository service to obtain a list of group information that matches the specified search conditions. Return the acquired group information list to the client.

  [Mail Service] The mail service is a service for sending a meeting notification and minutes mail to all participants. In the mail service, an event notification method and a minutes mail method are provided to the client.

  The event notification method creates the content of the event notification for the conference ID specified by the client, and sends an email to all participants. First, the conference document of the designated conference ID is acquired by the conference document acquisition method of the conference document service of the repository service. Bibliographic items are extracted from the acquired meeting document, and the name of the meeting, the date and time (start date and time), the venue, the organizer, and the participant list are listed in text format as the contents of the email. The venue is set by acquiring the conference room name using the conference room ID as a key in the conference room information acquisition method of the conference room information service of the repository service. The organizer and the participant list refer to the organizer ID and the participant list of the bibliographic items, acquire and set the first and last names with the user ID as a key by the user information acquisition method of the user information service of the repository service. At this time, the e-mail address of the user information is also acquired as the mail source and destination. As a subject of the mail, a character string “conference holding notification:”, a conference name, and a start date and time are set. As described above, the mail is transmitted with the set subject, transmission source, transmission destination, and the content of the mail, and the process ends.

  The minutes mail method creates the contents of the minutes for the meeting ID specified by the client and sends it to all participants by mail. First, the conference document of the designated conference ID is acquired by the conference document acquisition method of the conference document service of the repository service. Bibliographic items are extracted from the acquired meeting document, and the name of the meeting, the date and time (start date and time), the venue, the organizer, and the participant list are listed in text format as the contents of the email. The venue is set by acquiring the conference room name using the conference room ID as a key in the conference room information acquisition method of the conference room information service of the repository service. The organizer and the participant list refer to the organizer ID and the participant list of the bibliographic items, acquire and set the first and last names with the user ID as a key by the user information acquisition method of the user information service of the repository service. At this time, the e-mail address of the user information is also acquired as the mail source and destination. In addition, contents whose semantic attribute sharing flag is ON are taken into consideration, contents whose semantic attribute user flag is ON are listed as ToDo, and the titles of the contents are listed and included in the contents of the email. Also, the location of the minutes file and the login screen of eKC-PersonalCabin are expressed in URL format and included in the content of the email. As the mail subject, a character string “meeting minutes:”, a meeting name, and a start date and time are set. As described above, the mail is transmitted with the set subject, transmission source, transmission destination, and the content of the mail, and the process ends.

  [ToDo Management Service] The ToDo management service is a service for acquiring ToDo information registered in the system and attaching ToDo materials to ToDo information. In the ToDo management service, ToDo information acquisition method and ToDo material registration method are provided to the client.

  The ToDo information acquisition method returns the ToDo information (conference ID and content ID) specified by the client to the client. When the client requests the attached material, the ToDo material is returned. First, the ToDo information is acquired using the ToDo information acquisition method of the ToDo information service of the repository service using the specified conference ID and the specified content ID as keys. If the client requests ToDo information, the acquired ToDo information is returned. If the client requests the attached material, refer to the acquired ToDo information material list, retrieve the document ID, and use the document information acquisition method of the repository service's document management service to acquire the file name The file entity is returned to the client.

  The ToDo material registration method registers the file sent by the client to the ToDo (conference ID and content ID) specified by the client. First, a new document ID is acquired using the document information creation method of the document management service of the repository service. ToDo information service of repository service Todo information acquisition method of ToDo information service of ToDo information service, set the file name to the file name of ToDo material, set the acquired document ID to the document ID of ToDo material, and toDo information service of repository service Update ToDo information with the ToDo information update method. In addition, What's New (conference ID = corresponding conference ID, content ID = corresponding content ID, type = ToDo material, status = registration, update date = current date) indicating that the ToDo material has been registered, and bibliographic item participant list For all users, register with the personal information update method of the personal information service of the repository service.

  [System Management Service] The system management service is a service for acquiring organization information and conference room information registered as system information. In the system management service, an acquisition method for organization information and an acquisition method for conference room information are provided to the client.

  The organization information acquisition method returns the organization information registered in this system to the client. First, the organization information list is acquired by the organization information acquisition method of the organization information service of the repository service. Return the acquired organization information list to the client.

  The conference room information acquisition method returns the conference room information registered in this system to the client. First, the conference room information list is acquired by the conference room information acquisition method of the conference room information service of the repository service. Return the acquired conference room information list to the client.

Subsequently, some of the cooperation functions according to the present invention will be exemplified and the outline thereof will be described.
[A: Canvas and MC, PCab]
During the meeting, capture the video with MC while writing on Canvas. Register both MC and Canvas documents in the PCab as related to the same meeting. From PCab, you can specify a meeting and refer to both documents. When a Canvas document is referenced from the PCab, a board screen created with Canvas is displayed on the Web Browser. Each object (text, reference file, handwriting, etc.) on the board is linked to a video corresponding to its generation time. That is, when each object on the board is clicked, a video scene (MC document) at the time when the object is written is called, a video playback window is displayed, and the video is played back.

[B: IS and MC, Pcab]
Reference materials using IS while capturing video with MC during the meeting. Write to the reference material with an ink pen as needed. The generated MC document and IS document are registered and managed in PCab. When an IS document is referenced from PCab, a list of IS documents created by IS is displayed on Web Browser. Each item in the IS document list is linked to a video corresponding to the generation time. That is, when each item on the IS document list is clicked, the video scene at the time when it was written is called, a video playback window is displayed, and the video is played back.

[C; AP and MC, PCab]
Create personal notes with AP while capturing video with MC during the meeting. Register both MC and AP documents in the PCab as the same meeting. You can refer to both documents by specifying a meeting from PCab. When an AP document is referenced from the PCab, the personal memo screen created with the AP is displayed on the Web Browser. AP documents can only be referenced by their owners. The owner is determined by the login name to PCab. Each item of the personal memo is linked to a video corresponding to the generation time. That is, when each item on the personal memo is clicked, a video scene at the time when the item is written is called, a video playback window is displayed, and the video is played back.

  [D: Canvas and IS, PCab (Memo: No implementation)] During the meeting, the document is displayed using the application IS, and written on the canvas. Register both IS and Canvas documents in the PCab as the same meeting. In one conference, one Canvas document and multiple IS documents are registered as necessary. You can refer to both documents by specifying a meeting from PCab. When a Canvas document is referenced from the PCab, the board writing screen created with Canvas is displayed on the Web Browser. Each object (text, reference file, handwriting, etc.) on the board is linked to the IS document corresponding to the generation time.

  That is, when each object on the board is clicked, the IS document corresponding to the time when it was written is called and displayed. At this time, since the IS document is not streaming data, only one time information when the IS document is generated corresponds to one IS document. Therefore, when a postcard object on Canvas is specified, an IS document having the latest generation time before the time when the object was generated is displayed.

[E; Canvas and AP (Memo: No implementation)]
Participants create personal notes with AP while writing on Canvas during the meeting. Register both Canvas and AP documents in the PCab as the same meeting. You can refer to both documents by specifying a meeting from PCab. When an AP document is referenced from the PCab, the personal memo screen created with the AP is displayed on the Web Browser. AP documents can only be referenced by their owners. The owner is determined by the login name to PCab. Each item of the personal memo is linked to each object (text, reference file, handwriting, etc.) of the Canvas document corresponding to the generation time.

  That is, when each item on the personal memo is clicked, the corresponding Canvas document is called, and the object on the Canvas at the time when it was written is highlighted and displayed. At this time, since the Canvas document is not streaming data, the generation time of the object on the Canvas is discrete. Therefore, when the personal memo item on the AP document is designated, the object on the Canvas document having the latest generation time before the time when the object was generated is highlighted and displayed.

[F: IS and AP (memo: not implemented)]
During the meeting, the IS is used to display and refer to the materials for discussions, and participants create personal notes on the AP. Register both IS and AP documents to the PCab as the same meeting. You can refer to both documents by specifying a meeting from PCab. When an AP document is referenced from the PCab, the personal memo screen created with the AP is displayed on the Web Browser. AP documents can only be referenced by their owners. The owner is determined by the login name to PCab. Each item of the personal memo is linked to each object (text, reference file, handwriting, etc.) of the IS document corresponding to the generation time.

  That is, when each item on the personal memo is clicked, the corresponding IS document is called, and the IS document at the time when it was written is displayed. At this time, since the IS document is not streaming data, the generation time of the IS document is discrete. Therefore, when the personal memo item on the AP document is specified, the IS document having the most recent generation time before the IS document generation time is displayed.

[G: IS and Pcab]
During the meeting, handwritten annotations are made on the reference material (for example, writing with an ink pen). Perform embedding from the IS application when the user thinks it is necessary. By this operation, the IS content is generated by superimposing the display content and the content written by the ink pen, and is registered as a conference document.

  At this time, there are two types of embedding operations. The first way is to press the “Embed” button. By this operation, the “Shared attribute” of the “Semantic attribute” described later is given to the IS document in the “No label” state and registered in the conference document. The The second way is to press the “Embed Important” button. By this operation, the “Shared Attributes” of the “Semantic Attributes” to be described later is given to the IS document with the label “Important”. Registered in

  Since the IS document registered in the conference document has a “semantic attribute-shared attribute” to be described later, it is picked up and displayed on the attention screen of the PCab of all conference participants. At this time, since the label character string cannot be attached in the first operation described above, it is displayed on the PCab attention item screen with a predetermined notation such as “IS document” indicating an IS document. In the second operation above, the label string “important” is attached, so the PCab's attention screen displays the prompt “important” along with a predetermined notation such as “IS document” indicating that the document is an IS document. Is displayed. Furthermore, when an IS document is explicitly referenced from the PCab, a list of IS documents created by the IS is displayed on the Web Browser together with the IS document thumbnails.

[Embodiment 1 (Personal Cabin)] Next, details of each part constituting the system will be described with reference to an embodiment. Below, the outline | summary of the meeting assistance system centering on Personal Cabin is first demonstrated as an Example. The configuration of this embodiment system is shown in the configuration diagram of FIG. This system uses Canvas as a conference application.

  In FIG. 28, the collaboration space is a site where a meeting is held. The team workspace is a place where individuals work as a team while performing their assigned tasks, and corresponds to an individual desk when working in an organization. The personal work space is a place where a user works using only his / her personal computer, regardless of other users. This means the place of individual work as a concept rather than a concrete place for the former two.

  In the present embodiment, applications existing in a form visible to the user are “eKC Canvas”, “eKC Basket”, “eKC BasketClient”, and “Personal Cabin” shown in FIG. In the following, these are simply described as “Canvas”, “Basket”, “BasketClient”, and “Cabin” for simplicity.

  “Canvas”, “Basket”, and “BasketClient” are applications mainly used in a collaboration space. “Canvas” is an application that is assumed to be used mainly by facilitators of conferences called facilitators. This application is a program that runs on a PC brought in by the facilitator or a PC installed in the conference room. The screen of the PC on which Canvas runs is displayed using a display device such as a projector so that all participants in the conference can see it.

  The main function of Canvas is that the facilitator records and visualizes the context of the discussion as the meeting progresses. It provides functions that have traditionally been handled by white boards in a form that reinforces them. The information to be described includes text input by keyboard, file icons, handwritten figures, and the like. In other words, Canvas functions as an information editing description area.

  “Basket” has a function that the facilitator collects a document file created in advance by a conference participant, an instant message conceived on the spot, a handwritten sketch, and the like, and is literally equivalent to a “cage”. It runs on the same PC that runs Canvas. The information sent by participants to the facilitator using the BasketClient described below is displayed cumulatively in the Basket. The facilitator can paste the information displayed in the basket into the canvas by dragging and dropping. That is, the basket functions as an information sharing area.

  BasketClient is an application for sending document files created by conference participants in advance, instant messages that came up on the spot, hand-drawn sketches, etc. to the basket of the facilitator, and runs on the PC that the participants bring.

  The process of discussion described in Canvas can be exported to a local storage (hard disk, floppy disk (registered trademark), etc.) used by the facilitator, that is, on the PC on which Canvas is operated, and saved as a conference document. Furthermore, the saved conference document can be read again into the Canvas and the contents can be edited.

  Further, the discussion process described in Canvas can be saved as a conference document in a network storage (network storage). At the time of storage, a predetermined bibliographic item is attached and stored. Bibliographic items specifically include the name of the meeting, the date and time of the meeting, and the members. Hereinafter, a document described in Canvas is simply referred to as a “conference document” regardless of its storage location (network or local storage).

  The conference document stored in the network storage can be referred to from another PC via the network. The tool that refers to this is “Cabin” (Personal Cabin). Cabin is configured as a web application (browser). A user uses a Cabin by starting a Web browser (Internet Explorer (registered trademark), Netscape Navigator (registered trademark), etc.) from his / her PC and specifying a predetermined URL (Uniform Resource locator). Cabin logs in for each user who uses it. Therefore, the view provided by Cabin is different for each user.

  In the above description, Canvas and Basket are described as separate applications in order to clarify their functions. However, in Patent Document 1, these functions correspond to the editing area and stacking area of the master client, respectively. Is. Furthermore, BasketClient is equivalent to a slave client as well.

  The function of Canvas is explained. The types of information that can be described in Canvas are text, handwriting, and file. Hereinafter, these are called a text object, a handwritten object, and a file object, respectively.

  The basic part of Canvas has a function as a rich text editor, and a user (facilitator as a role) can input text with a keyboard. The text object is inserted as a text object in units of lines as a text object in units of lines by the user, and specifically, a “text” button arranged on the right side of the screen in FIG. 29 is pressed. Or by selecting a menu to which a similar function is assigned.

  The handwritten object is inserted at an arbitrary position between the rich text lines when the user performs a predetermined operation. Specifically, it is inserted by pressing a “handwriting” button arranged on the right side of the screen in FIG. 29 or selecting a menu to which a similar function is assigned.

  The file object is inserted at an arbitrary position between the rich text lines when the user performs a predetermined operation. Specifically, a file selection dialog is opened by pressing a “file” button arranged on the right side of the screen of FIG. 29 or selecting a menu to which a similar function is assigned, and the file is inserted by selecting a file. You can also directly insert file icons by dragging and dropping them on the PC on which Canvas starts.

  In addition, text, file, and handwritten objects can be sent from the BasketClient to the Basket. On the receiving side, each object is listed in the basket. It can be pasted into Canvas by Drag & Drop from the displayed list.

  [Recording of time information] When the object is generated, the time at which each object is generated is stored in association with the object. Specifically, according to the data structure described later, the object is stored together with the generation time in the memory of the machine on which the Canvas operates. In addition, they are written out as temporary files on the local disk of the machine where Canvas runs as needed.

[Editing objects] Text, handwriting, and file objects can be edited.
[Object search function] Text, handwriting, and file objects can be searched.
[Object Layout Editing Function] The discussion process description has an object layout function for the purpose of the following functions. Opinion is visualized by expressing the description of the discussion process in bullets. Organize the flow of discussions by hierarchizing by indenting bullets and moving hierarchical objects in hierarchical units.

  [Attributes] The outline of the system describes the function to display the discussion process by converting the contents described in Canvas into the network storage and referencing them from the Cabin to convert them into views for each user. In the present invention, in order to realize this, an approach for realizing this is taken by describing machine-readable attributes in the description of the discussion process. First, two attributes are defined as attributes. One is defined as a visual attribute and the other as a semantic attribute.

  [A: Visual attribute] The visual attribute is mainly an attribute relating to the appearance of the object on the Canvas. Specifically, it is an attribute that defines the color, size, and shape of a symbol (handle) displayed at the beginning of each object on the Canvas. Use this when you want to pick up a visually noticeable item while writing information on the Canvas. For example, an operation of changing the leading symbol from the default black to red.

[B: Semantic attribute] The semantic attribute is an attribute that is defined / assigned to assign a meaning to the object indicating the discussion process described on the Canvas. The elements constituting the semantic attribute are as follows.
・ Shared information ・ User information ・ Date information

The attribute values of the above attributes are as shown below.
-Sharing information (attribute value: true / false, label string)
-User information (attribute value: "person" list)
-Date and time information (attribute values: INIT, FINAL, NOW; each has a time including date)
Each attribute will be described in further detail.

  Shared information, if its value is true, means that it should be shared by all conference members. Specifically, an object whose sharing information is true is treated as information that is specifically picked up and memorized by all the conference members, and is picked up and displayed in a predetermined view of Cabins of all the conference members. Furthermore, the label character string is a character string that can be arbitrarily defined when the user assigns a shared information attribute to an arbitrary object on the Canvas. For example, it is a character string such as “conclusion” and “problem”. This can be an empty string.

  The user information is a list of values “people”. Specifically, it is a list of ID information that points to a machine-readable “person” defined by the system, such as “user ID” and “email address” that specify “person”. Hereinafter, it will be simply referred to as “user ID”.

  User IDs must be unique across the entire Canvas and Cabin system. The user ID is desirably managed uniquely using a mechanism such as a directory service that is not described here. Canvas has a unique “user ID list” for each machine or user on which it runs. The list of user IDs that Canvas has is one in which the user individually copies the desired user ID from the directory service or is manually input by the user. This is a form similar to the “personal address book” of e-mail software, for example.

  An object to which a user information attribute is assigned is defined as an object having an important meaning for “person” indicated by the attribute value. Specifically, the target “person” ToDo item. The object to which the user information is given is picked up and displayed in a predetermined view of the “person” Cabin indicated by the value.

  The date / time information has three types of time information. INIT is the time that means the beginning of things. NOW is the time when the attribute was granted, and FINAL is the time that means the end of things. Specifically, for example, in combination with "user information", to make an object meaningful as a ToDo that associates the time when the request occurred (NOW), delivery date (FINAL), and the person in charge ("people" list) Used for.

  [Exporting to and reading from a local file] Objects described in Canvas can be written as a file on the local disk of the machine on which Canvas runs, along with information such as the creation time and attributes. In addition, the exported file can be read into the Canvas and displayed.

  [Upload / Download Function] Not only can be stored in the local storage, but also can be stored in the network storage on the network. By saving to network storage, the contents can be referenced from any PC running Web Browser via Cabin. Hereinafter, this is described as “upload to server”.

  The procedure for uploading a file to the server is shown. Select "Upload to server" by a predetermined operation such as a menu from Canvas. At this time, login processing to the server is first executed.

  After the login process, the conference list is displayed. The conference displayed here is “conference name” described in the conference document defined as the owner of the login user. Here, when an existing meeting name is selected, the meeting document on the server is overwritten with the contents of Canvas for the meeting. When a conference name is newly input, a conference document is registered on the server with the conference name, and the login user is set as the owner in this conference document. In addition, when registering the conference file, bibliographic items such as the date and time of the event, the participants, and the like can be input together as necessary.

  The procedure to start Canvas and download the meeting document on the network storage (server) is shown. Select "Download from Server" by a predetermined operation such as a menu from Canvas. At this time, login processing to the server is first executed.

  After the login process, the conference list is displayed. The conference displayed here is “conference name” described in the conference document defined as the owner of the login user. Here, when an existing meeting name is selected, the meeting document corresponding to the meeting is downloaded from the server and loaded into the Canvas.

[Basket functions]
Basket runs on a PC running Canvas. When the Basket is started as a part of the Canvas as the first embodiment (refer to FIGS. 30 and 31 (corresponding to FIGS. 10 and 11 of Patent Document 1)), a predetermined example is provided from the Canvas or the operating system as the second embodiment. When starting by performing a starting operation (button, menu, etc.), it is conceivable.

  When Basket starts up, it displays the display part that displays the received information and the password that BasketClient requires to input to send information to this Basket. The password is a combination of the IP address and port number of the PC on which the basket is running, or a character string encoded uniquely from these character strings. Each basket program has one port number for information exchange. When the access password issuing function is activated, the port scan is performed from the default port number (for example, 3000), and if the port is already in use, the default port number is incremented by 1 (for example, 3001, 3002, ...). If acquisition of the port number is successful, the port number is set. This password is issued not as a security password, but as a pointer to specify the destination basket from the BasketClient. For this reason, a character string that is easy for the user to visually recognize is desirable.

  The user of BasketClient performs the operation of sending information by inputting the password displayed in the Basket that is the other party to whom information is to be sent to the BasketClient. When Basket receives predetermined information, it displays this list (FIG. 31). The information displayed in the list can be pasted on the Canvas by Drag & Drop. At this time, according to the difference in the type of information character string, file, and handwriting, the object is inserted in the manner of object insertion into the Canvas described in the section.

  [Functions of BasketClient] BasketClient runs on the PC of any conference participant. BasketClient has a user interface for inputting text, handwriting, and file information to the basket (see FIG. 32 [corresponding to FIG. 8 of Patent Document 1)). Further, a password input area for designating a transmission destination is displayed. In the password input area, the user sees the password displayed on the other party's Basket and inputs the same character string. The entered password is retained internally until the BasketClient is terminated. Therefore, once the user enters the password of the basket used by the facilitator, the information can be sent to the basket at any time without entering the password by running the BasketClient during the conference.

[Second Example]
Next, FIG. 33 shows an outline of the second embodiment related to the basket regarding the exchange of information via the BasketClient and the Basket. In FIG. 28 in the previous embodiment, when sending information from the participant to the facilitator, the participant used BasketClient which is a single function application for sending information. This is suitable for sending information immediately on the spot. However, for example, when sending a text message, if you enter text in the text input area of BasketClient and press the send button, the text will be sent but will not remain at the sender's hand.

  In addition, during the discussion, participants wrote down their memos and realized that some of them were important, so when sending to facilitators for the purpose of sharing with members, the first example showed In the manner, you need to copy from your memo, paste it in the input area of BasketClient, and press the send button.

The second embodiment aims to solve these disadvantages. The main points of this embodiment are as follows.
(a) The Canvas has an object transmission function for transmitting each text, file, and handwritten object described in the Canvas to the specified Basket, and the function of the BasketClient is replaced with this.
(b) Both the facilitator and general participants have the same Canvas and Basket functions.
Canvas for facilitators is a place to visualize discussions and share them with members.
(c) For general participants, Canvas is their own notepad.

  Furthermore, (d) since the facilitator and the general participant have the same Canvas and Basket functionally, it is possible to send information from the facilitator Canvas to the general participant's Basket.

[Cabin Function] Next, eKC Personal Cabin will be described in detail.
Specifying the Cabin URL from the Web Browser displays the login screen (Figure 34). When login is successful by performing a predetermined input operation, a top screen for the login user is displayed (FIG. 35).

  [Top Screen] On the top screen, two items “Today's Meeting” and “ToDo” are displayed. “Today's meeting” is a meeting in which the logged-in user is included in the participants, and the meeting name of the meeting document whose holding time is today is extracted and displayed. “ToDo” extracts and displays all objects whose login user is included in “semantic attribute”-“user information” from all meeting documents registered in the system. When the corresponding object is text, a character string of a predetermined number of characters is displayed from the top of the text.

  When the corresponding objects are a file and a handwritten object, a character string of a predetermined number of characters from the top is displayed among the label character strings attached to these objects. The label character string is a unique character string generated from the file name in the case of a file object, the generation time in the case of a handwritten object, etc. unless explicitly changed by the user on the Canvas.

When a meeting name displayed for today's meeting, for example, “Review Meeting” (FIG. 35) is clicked, a list of bibliographic items of the meeting is displayed. Bibliographic items include the date and time, location, members, and explanation. An example of such a meeting recording screen is shown in FIG.
7.1.1.2

  [Meeting Record Screen] The meeting record shown in FIG. 36 is the top screen of the meeting document of the meeting named “Review Meeting” saved in the PCab. From the “conference document”, the conference application document registered in association with each conference by each conference application can be referred to. The parts indicated by A, B, C, and D in FIG. 36 are links to the conference application document. A is a Canvas document, B is an MC document, C is an IS document, and D is a link to an AP document.

  FIG. 37 shows an example in which the above A is clicked and a Canvas document is referenced from the PCab. The contents of the board written in Canvas are displayed in the same format. Among the displayed screens, the handwritten object is linked to the original handwritten object, and the handwritten object can be displayed in actual size by clicking. In the case of a file object, it is linked to an actual file and can be opened with a predetermined application by clicking. These objects constituting the Canvas document are stored in the PCab in association with the conference document according to the data structure described in detail later. When the MC document is displayed by clicking B above, the MC playback screen shown in FIG. 69 described later is displayed on the Web Browser.

  FIG. 38 shows an example in which the IS document is displayed by clicking C above. Two items are displayed. Each item is a link to an IS document captured by the IS function at this conference. Specifically, the IS document is a bitmap image obtained by combining the display screen and the ink pen locus by writing with the ink pen while displaying the document on the IS. However, when the material displayed in IS is a predetermined application (for example, MS-Office manufactured by Microsoft Corporation), the IS document is a material file in a state in which a locus written with an ink pen is embedded as an object in the material file.

  FIG. 39 shows an example in which the above D is clicked and the AP document is referenced from the PCab. Each item is a comment character string input from the AP, and the leftmost column is the time when the comment is written. Each comment character string is linked to an MC document associated with the same conference document. By clicking this, a video at that time can be reproduced from the MC document.

[Link to MC document from Canvas document screen and IS document screen]
Each object of the Canvas document and the IS document records the time when they were created during the meeting in association with each other according to the data structure described later. From the Canvas document screen and the IS document screen shown in FIGS. 37 and 38, a video at the time when each object was created during the conference can be called with reference to the MC document.

  When the “video mode” button at the upper end in FIG. 37 and FIG. 38 is clicked, each screen is switched to the video mode. In the video mode, each object is linked to the video playback start point at the generation time. By clicking this, the video image at that time is reproduced and displayed on the MC reproduction screen shown in FIG.

[ToDo screen]
For example, when “Define data structure” is clicked in the ToDo item displayed on the top screen, the board document of the conference document in which the item has occurred, that is, the board document content created and registered in Canvas is displayed in the Browser. At this time, the corresponding object is displayed so as to be visible. That is, when the corresponding object is near the end of the sentence of the conference document, it is scrolled and displayed so that it can be seen. In addition, a mark is displayed near the corresponding object, or the color is changed. FIG. 41 shows an example of scrolling and displaying an arrow near “Data structure definition”. FIG. 41 corresponds to FIG. 29 described in Canvas.

  Further, when the “display details” of the ToDo item is clicked on the top screen (FIG. 35), bibliographic items of the conference document in which the corresponding ToDo occurs are displayed (FIG. 42).

  [Attention item screen] When the attention item tab in the top screen is clicked, a list of “attention items” is displayed (FIG. 43). A part of a bibliographic item such as a meeting name where each object (notable item) occurs is displayed in the list at the same time. “Attention” extracts all meeting documents in which the logged-in user is a participant or owner from all meeting documents registered in the system. All objects with “semantic attribute”-“shared information” are extracted and displayed. When the corresponding object is text, a character string of a predetermined number of characters is displayed from the top of the text. When the corresponding objects are a file and a handwritten object, a character string of a predetermined number of characters from the top is displayed among the label character strings attached to these objects. The label character string is a unique character string generated from the file name in the case of a file object, the generation time in the case of a handwritten object, etc. unless explicitly changed by the user on the Canvas.

  When the list is displayed, click “Function (Other)” (second line from the bottom in FIG. 43), for example, the board document of the conference document in which the item occurred, that is, the board document contents created and registered in Canvas. Display in Browser. FIG. 44 shows an example in which “function (others)” is scrolled to the top and displayed with an arrow. FIG. 44 corresponds to FIG. 29 described in Canvas. At this time, the corresponding object is displayed so as to be visible. That is, the display is scrolled so that the corresponding object can be seen. In addition, a mark is displayed near the corresponding object, or the color is changed.

  Furthermore, in FIG. 41 and FIG. 44, when the displayed object is a file object, the file can be opened by an application associated with the file by clicking on the object. In addition, in the case of a handwritten object, the handwritten object generated by Canvas is stored internally as a bitmap file (xxx.bmp) in Cabin. Open the application associated with the bitmap file. For example, in Browser on MS-Windows (registered trademark), an application called “Paint” (attached to MS-Windows (registered trademark) as a standard) is started by default, and a handwritten object is displayed.

  ["Matter of interest" by IS document] The "shared information" attribute and "user information" attribute described above do not depend on the application that creates the conference document in the architecture of the PCab. In IS, an IS document is registered with PCab with the same attribute as in Canvas. The operation of attaching an attribute to an IS document on the IS side will be described in the description of the IS operation.

  The IS document to which the “shared information” attribute is given in the IS document is picked up and displayed on the “notice screen” in the same manner as the Canvas document in addition to the conference recording screen 36 described above. An example of the display screen at this time is shown in FIG. A predetermined character string is given by the IS so that the headline is an IS document. In this example, it is “BASE DOCUMENT”.

  Further, the IS document with the “shared attribute” on the screen from the minutes shown in FIG. 38 is described as such. In FIG. 38, the mark “Shared” indicates this. Further, in FIG. 38, the “important” mark indicates that the label character string “important” is further added to the “shared information” attribute by the IS and registered in the PCab. The relationship between the “shared information” attribute and the label character string has already been described in “Canvas functions” and “Conference document table”.

[Example * 2]
In the system shown in the configuration block diagram of FIG. 46, “IS” is used as the conference application. As described above, IS is an application that supports handwriting with an ink pen (ordinary whiteboard marker pen).

  [Hardware Configuration] First, FIG. 47 and FIG. 48 show a system configuration including a known device for handwritten annotation in IS. The hardware configuration of the IS is equivalent to a publicly known one that has already been applied for a patent.

  The camera and projector are installed together with the projection screen in the IS hardware casing (IS body) (FIG. 47). The projector is connected to the video output of the personal computer, and the operation screen provided by the personal computer operating system is input to the projector. The camera is connected to a personal computer via an IEEE 1394 interface. As a result, a command for camera operation (shooting instruction, data transfer instruction, etc.) is sent from the personal computer to the camera. Furthermore, the photographed image data is taken into the personal computer through this. The personal computer is connected to the network, and images taken by the camera can be stored in a remote machine on the network, such as a PCab machine.

  The IS application runs on the personal computer. The IS application sends a predetermined command to the camera or projector to acquire an image from the camera, a function to convert the acquired image into a predetermined IS document format, and an IS document generated by calling a predetermined service to the PCab. And a function of providing an operation interface (operation screen) operated by a user. The IS application may be automatically started when the system is started, in addition to the case where the IS application is explicitly started by a predetermined operation of the user. The operation screen is shown in FIG.

  The notation personal computer stores applications used by the user (word processing software, presentation software, etc.) and a user's desired document. The user opens this document by a predetermined operation with a corresponding application, and displays the screen on the IS screen via the projector.

  The concept of annotation on a document document by the IS application in the present invention will be described with reference to FIG. The document document is an arbitrary application document composed of a plurality of pages. Specifically, it is a document generated by an application such as a word processor.

  The annotation data is annotation data to the document document input by handwriting input means. Here, the handwriting input means may be an IS system or a combination of a general pointing device such as a mouse, a tablet, or a touch panel and a transparent board application. When the handwriting input means is the former, the annotation data is a bitmap image. When the handwriting input means is the latter, the annotation data is a stroke directly. However, it is assumed that the image is converted into a bitmap image by an intermediate process not shown. For example, “Rakugaki Kakae: Fujitsu Oita Software Laboratory” is known as the transparent board application.

  The acquired annotation data is embedded in the “document document” by a predetermined procedure, and an “annotation embedded document document” is generated. The acquired annotation data is managed in association with “annotation embedded document document” and “document document”. The association parameter is a page in the document and a position in the page in addition to information (document ID or the like) specifying the document.

  On the other hand, when referring to the annotation, the annotation is displayed superimposed on the print image or the document document by a predetermined application. Alternatively, an annotation may be embedded in a print image or document document to create a new document file, which may be managed in association with the original document document, the original print image, and annotation data. However, embedding annotations in the original document document depends on the format of the original document document. An example in which the original document is an MS-Office (trademark) product manufactured by Microsoft Corporation will be described later.

  Annotations can have the attributes already explained in the PCab overview. Specifically, “semantic attribute-shared information” and “semantic attribute-user information”. These attributes are the “meaning” that the user intentionally attaches to the annotations in the document document, and are metadata that is referenced in the PCab. The present invention is characterized in that the metadata can be defined without depending on the application for generating the document document. As means for realizing this, in the present invention, the attribute is managed in association with annotation data. As a result, it is possible to perform a reference (by PCab) such as “annotation with a specific attribute in the document document is here in the document”. 51, 52, and 53 show examples of the document screen, the document screen after annotation, and the annotation image.

  The IS application is activated by the user on the personal computer shown in FIG. The flow of starting the IS application is described below. First, the user is asked to select whether to place the IS document generated in the subsequent operation on the PCab or in the local storage. In the following description, a case where the user selects PCab will be described. If the user selects the local storage, the description stored in the PCab in the following explanation is replaced with the local disk.

  When the user selects PCab, login processing to Pcab is performed. If login is successful, the user is prompted to set the name of the meeting to which the IS connects. Here, using the “conference connection service” described later, a list of conferences owned by the logged-in user is acquired, and a procedure for selecting a conference from the list or creating a new conference is requested from the user. When the connection destination meeting is determined, the document document to be annotated is selected and the document document is displayed. The document document is selected from documents registered in an existing conference on the local storage or PCab. When a series of procedures is completed, a group of operation buttons such as an “embedding” button for providing an operation for acquiring an annotation is displayed, and the user waits for a desired operation.

  The first procedure until an IS document is generated will be described. For this, a document document by MS-Office application is used. The document processing procedure is shown in the flowchart of FIG. First, the user starts the IS application described above. Next, the user activates an arbitrary document document created by Microsoft's MS-Office on the personal computer. A scroll operation or the like is performed on the activated document document to display a desired portion. Write on the document document displayed on the IS screen with an ink pen.

  When the user wants to embed the writing with the ink pen in the display material, the user clicks the “embed” or “important embed” button of the IS application with the mouse. Here, the program detects the currently active window and the applications running on it. The detection of the currently active window and the detection of the type of application running there are realized by the IS application using a known method provided by the operating system.

  When the detected application is MS-Office (registered trademark), the following processing is executed. That is, for example, in the case of MS-Word (registered trademark), the Paste () function is called from the dynamic link library WordDLL, and the size of the additional image and information on the pasting position are given as arguments to paste the image at the specified position. . A series of IS documents is generated by the above procedure (see FIG. 54).

The series of IS documents is as follows.
A. Original MS-Office document
B. Handwritten image obtained by shooting
C. MS-Office document in which handwritten images obtained by shooting are embedded as objects

  Next, a procedure for registering the IS document generated by the procedure described above in the PCab will be described. This procedure is executed as a series of operations following the aforementioned procedure. Therefore, there is no user operation to start this procedure.

First, when the “Embed” button is pressed, the following attributes are attached to a series of IS documents.
IS document A: “Shared information” = false
IS document B: “Shared information” = true, Label string = “null”
IS document C: “Shared information” = false

First, when the “important embedding” button is pressed, the following attributes are attached to a series of IS documents.
IS document A: “Shared information” = false
IS document B: “Shared information” = true, Label string = “Important”
IS document C: “Shared information” = false

  Furthermore, in any of the above button operations, the generation time of the IS document is associated with the IS document. An IS document with attributes and generation time is converted into a predetermined data format and registered in the PCab. The registration destination is a conference on the PCab with the ID specified when starting the IS application. The registration procedure and data format for PCab will be described in detail in “Conference Connection Service” and “Conference Document Table”.

  The second procedure (screen recording) until the IS document is generated will be described. The processing procedure is shown in the flowchart of FIG. The user activates an arbitrary document document created by an arbitrary application on the personal computer. At this time, the above-mentioned IS application is also activated at the same time.

  When the user wants to record the display material screen, the user clicks “Save screen” of the IS application with the mouse. Here, the program obtains a snapshot bitmap image of the entire screen as an IS document. The above procedure generates a series of IS documents. A series of IS documents is a snapshot image of D. screen.

Next, a procedure for registering the IS document generated by the second procedure described above in the PCab will be described. This procedure is executed as a series of operations following the aforementioned procedure. Therefore, there is no user operation to start this procedure. When the “Screen Record” button is pressed, the following attributes are attached to the IS document.
IS document D: “Shared information” = true, Label string = “null”

  Furthermore, in any of the above button operations, the generation time of the IS document is associated with the IS document. An IS document with attributes and generation time is converted into a predetermined data format and registered in the PCab. The registration destination is a conference on the PCab having the ID specified when the IS application is started.

  A third procedure (automatic screen recording) until an IS document is generated will be described. This processing procedure is shown in the flowchart of FIG. The user activates an arbitrary document document created by an arbitrary application on the personal computer. At this time, the above-mentioned IS application is also activated at the same time.

  First, the user explicitly switches to the automatic screen recording mode on the operation screen of the IS application. Specifically, press the “Auto Screen Save” button. This button is a toggle operation, and the automatic recording mode is maintained until this button is pressed again.

  In the automatic screen recording mode, the operation described in the third procedure (screen recording) is repeated at predetermined time intervals. The acquired bitmap image IS document is registered in the PCab in the same manner every time it is acquired.

The above procedure generates a series of IS documents. The series of IS documents is as follows.
E. Group of screen snapshot images acquired at specified time intervals

  Next, a procedure for registering the IS document generated by the procedure described above in the PCab will be described. This procedure is executed as a series of operations following the aforementioned procedure. Therefore, there is no user operation to start this procedure.

When the “Auto Screen Save” button is pressed, the following operation is performed every time a bitmap image of a screen snapshot is acquired at a predetermined time interval.
Attach the following attributes to the IS document.
IS document E: “Shared information” = false, Label string = “null”

  Furthermore, every time the snapshot is acquired, the IS document generation time (snapshot acquisition time) is associated with the IS document. An IS document with attributes and generation time is converted into a predetermined data format and registered in the PCab. The registration destination is a conference on the PCab having the ID specified when the IS application is started.

  As described above, one snapshot image is handled and managed as one IS document. In addition, a series of snapshots are acquired at a predetermined time interval, so this is regarded as a unit of streaming data (for example, video). It is also possible to adopt a management method. In this case, the time when the "Auto Screen Save" button is pressed and the automatic screen save mode is turned on is the start time, the time when the "Auto Screen Save" button is pressed again and the automatic screen save mode is turned off is the end time, The frame interval is a snapshot acquisition time interval.

  Furthermore, if the snapshot acquisition time interval is longer than the video frame rate, for example, 1/30 seconds (30 frames / second), the time is calculated by interpolating between adjacent snapshots every 1/30 seconds with the first snapshot. Data having the same structure as the video data can be generated for the axis. Thus, a series of automatically saved screens can be managed in the same manner as the video generated by the MC, which is managed according to the start time and the time from the start time.

  In addition, since the change of the handwritten annotation screen is slower than that of a general moving image, it may be sufficient that the time interval of snapshot acquisition is about several minutes. However, when referring to a snapshot group, the user wants to specify an arbitrary time. This is because the user is not aware of the time and time interval when the snapshot was acquired. In this case, for example, if the snapshot acquisition interval is 5 minutes, the user can specify a reference point at an arbitrary time in minutes by complementing this at 1 minute intervals, improving usability To do. A conceptual diagram of such a complementary process is shown in FIG.

  Furthermore, as a method of generating screen storming data, instead of automatically recording the screen at predetermined time intervals, changes in the screen (for example, increments of the number of strokes written, length, etc.) have a predetermined threshold. A method of acquiring a snapshot when the value is exceeded may be introduced. Taking snapshots from changes in the screen itself is known in QuickBoard (Ichimura et al., "QuickBoard: Web system that distributes arbitrary application screens in real time", IPSJ Journal Vol.45, No.1,2004.1) is there.

[Example * 3]
In the system shown in the configuration block diagram of FIG. 58, “AP” is used as the conference application. AP is a third agenda recording means according to the present invention, and is a program for recording personal memos during scene recording (hereinafter referred to as “personal memo program”). It is a software application (tool) that runs on the information terminal that is brought in. The user can input text such as comments and memos as necessary during the meeting, and the input text is associated with time and stored together with several bibliographic items and generated as an AP document.

FIG. 59 is a diagram showing a display screen example on the information terminal of the “personal memo program”. Hereinafter, components on the display screen of the figure will be described.
[1a] Agenda button; a button for recording a turning point of a topic. When this button is pressed, an agenda flag to be described later is attached.
[1b] Agenda display column: A column for displaying the chapter number and text input when the agenda button is last pressed.
[1c] Normal button; unlike the agenda button, a button that does not have an agenda flag when pressed. The user sets the name of each button using a separately prepared editing program (not shown).
[1d] End button; button to end the program.

Each time each button shown in FIG. 59 is pressed, the following three pieces of information are added to the memo file in a state of being associated with each other.
[2a] Time: Absolute time when each button is pressed. Expressed in year / month / day / hour / minute / second.
[2a] Agenda flag: 1 if the pressed button is an agenda button, 0 if it is a normal button.
[2a] Button name or text input; (set)

  Here, when the agenda button or comment button is pressed, a text input screen for inputting the agenda item or free comment is displayed as shown in FIG. When a predetermined character string is input in the text input field and the OK button is pressed, the text input in the text input field is added to the memo file together with the time when the button is pressed and the agenda flag.

  FIG. 61 shows the configuration of a mobile terminal on which the personal memo program operates. CPU, memory, liquid crystal display for data display, touch panel for input, and serial communication interface for connection with PC to execute programs.

  The touch panel detects that the user has touched the pen, and when the pen touches the panel, the pen down signal, when the pen moves while touching the panel, the pen move signal, and when the pen leaves the panel, the pen touches the panel. The up signal and its position (xy coordinate value) signal are output. In addition, it is installed on the display surface of the liquid crystal display so that the user can operate buttons and the like displayed on the display.

  During the time recording operation, the mobile terminal operates independently. After recording, connect the mobile terminal to the client PC with a serial cable and transfer the time data. The client PC searches and displays the moving image data recorded on the video server on the network according to the transferred time data.

  The conference application AP of the present embodiment is realized by (a) a personal memo program that operates on a mobile terminal, (b) a transmission program that operates on the mobile terminal, and (c) a search program that operates on a client PC. . Each operation will be described below.

  [Personal Memo Program] The operation of the personal memo program will be described for each step with reference to the flowchart of FIG.

[Screen Display]; The screen shown in FIG. 58 is displayed on the display.
[Pen display]; Waits for the user to use the pen and tap the button.
[End button]; The position touched by the pen is acquired. If the position is above the x button, the memo file is recorded in the memory, and the process is terminated. If it is over the other buttons, the process proceeds to the next “Record Time / Agenda Flag” step.
[Record time / agenda flag]: The absolute time when the button is pressed and the agenda flag are recorded in the memory.
[Agenda or comment button]: If the position touched by the pen is above the agenda button or the comment button, the process proceeds to the “display text input screen” step. If it is over any other button, the process proceeds to the next “button name acquisition” step.
[Acquire Button Name]: The button name written on the pressed button is recorded in the memory.
[Text input screen display]; The text input screen shown in Fig. 38 is displayed on the display.
[Text acquisition]; When the user detects that the user taps the OK button on the screen shown in FIG. 60, the character string recorded in the text input field at that time is recorded in the memory.
[Add to memo file]; Add the time, agenda flag, and button name or text recorded in the memory to the memo file.
Thereafter, the process returns to the “pen instruction input” step, and the process is repeated as described above.

  An example of the memo file recorded by the above series of operations is shown in FIG. This figure shows an agenda button (no text input), an important button, an agenda button (text input with “Mr. Suzuki's announcement”), an omission button, a conclusion button, a comment button (input text “homework until the end of the month”), and an end button It shows that the button was pushed in the order. The time, agenda flag, button name, or text is separated by tabs.

  [Transmission program] A program executed on the portable terminal, which transmits a memo file recorded by a personal memo program to a client PC connected by a serial cable. Since this program is already on the market (for example, ActiveSync is applicable when the mobile terminal is a Microsoft Pocket PC), the description thereof is omitted here.

[Example 2]
An example of a system in which Canva of the conference application already described is replaced with MC of another conference application is shown in the configuration block diagram of FIG. The system structure leading to the network storage is slightly different depending on each application, but is simplified because it is an explanation of the entire structure.

  In the system shown in the configuration block diagram of FIG. 63, “MC” is used as the conference application. “MC” is a system that records and plays back video, audio, etc. for recording the entire conference scene, and consists of a recording and playback subsystem. Hereinafter, “MC” including a known part will be described.

  First, the hardware configuration of the recording subsystem in which “MC” operates is shown in the schematic block diagram of FIG. The recording PC is a general personal computer incorporating a CPU, memory, hard disk, and the like. The analog video signal output from the camera is input to the recording PC through a video capture board connected to the recording PC. The analog audio signal output from each microphone of the microphone array is input to the recording PC through a 4-channel audio capture board connected to the recording PC.

[Panorama Camera (Panorama Video Shooting Function)] A panoramic (180 degree or more) video camera with a curved mirror is used for video recording.
FIG. 66 shows the arrangement of the microphone and the camera.

  FIG. 67 shows a schematic configuration of the panoramic camera. A curved mirror is placed in front of a normal camera, and the surrounding scenes reflected on the mirror are shot at a wide angle. The mirror is a convex mirror having a curvature only in the horizontal direction. By using such a curved mirror to capture an image compressed only in the horizontal direction and expanding it uniformly in the horizontal direction, a wide-angle image is formed in the horizontal direction. Since such enlargement processing can be performed at the time of reproduction on a PC, there is a feature that substantially no modification is required. The lens is an ordinary imaging lens for a video camera. The imaging unit converts an image formed by the optical system into an electronic signal by a CCD imaging device. Output as an analog video signal through the interface circuit. The installation of such a camera on the desk has advantages such as no operation of a camera pan or the like, and easy participation of the participant's face.

  FIG. 68 shows the configuration of the playback system. A system that executes a video playback function includes a server PC and a client PC connected via a network. The client PC is connected with a monitor for displaying an image, a speaker for reproducing sound, a keyboard for inputting user operations, and a mouse. The client transmits a video data search request to the server in accordance with a user operation. The server transmits to the client data for displaying searched video data or the like for searching for data that meets the conditions from the data registered from the recording subsystem.

Next, control (software) of this system will be described.
[Conference ID acquisition] The user name and location ID input by the user are transmitted to the server, and the conference ID currently being held is acquired.
[Video / audio recording] Video and audio data are input from the camera and microphone, compressed by the MPEG algorithm, etc., and then recorded as a file on the hard disk.
[Sound source direction detection] The time difference between audio information input from each microphone is calculated.
[Preprocessing] The time difference information of each period is smoothed to reduce noise, and speech time and direction data are obtained. Based on the time direction data, time chart image data is generated.
[Server registration] The recorded data is registered in the server so that it can be used in the playback system. Each registered data is assigned a unique identifier called a content ID, and the content can be called up using the content ID thereafter (refer to the description of the conference document table described above for details of the content ID).

  The recording function by the recording (sub) system in the present embodiment has the following features suitable for recording a conference scene, and records video, audio, and others (sound source direction).

  [Sound source direction detection function] The information on who spoke and when is important for reproducing the meeting scene. In MC, in order to record the information, the direction of the sound source is measured. That is, sound is acquired by a plurality of microphones arranged in each part of the camera housing, and the direction of the sound source is sequentially calculated and recorded based on the arrival time difference of the sound information. The cross-correlation is calculated for each short time interval, and the time difference with the highest correlation is obtained. The audio itself is recorded for audio playback. Since the positional relationship between the camera and the microphone array is fixed, the sound source direction can be measured and recorded in correspondence with the video content.

  [Attachment information (time, place, meeting ID) assigning function] Recording start and end times are recorded as images in individual video data. In addition, in order to associate with recording in a subsystem other than MC (Canvas, IS, etc.), when recording video data, a society ID is acquired (generated) based on time / location / user information and recorded in association with the video data. .

The data to be registered by the server registration function in the embodiment is as follows.
“Time chart image data”; shooting video data For video data, the following information is recorded.
“Pointer”: URL for accessing video data. The video data itself is copied to a streaming server for video streaming communication.
“Recording time”: Time when video recording starts and ends.
Corresponding time chart.

  [Server Program] The server program receives HTTP communication as a search request and returns HTML data. The server program is realized as an HTTP daemon. That is, search conditions are input as GET or POST parameters for HTTP communication, and HTML data for video display is output. Therefore, any program can play back desired video data simply by calling a Web browser (component) and accessing a specific URL including a search condition.

  [Reproduction function] The data recorded by the recording subsystem is reproduced. When the recording system is operated for a long time, a large number of video data is recorded, and the total time can be enormous. However, at a certain point in time, the user really wants to refer only to a certain time range of one piece of video data. Therefore, a method for appropriately searching for video data to be reproduced is important.

In this embodiment, the MC document is
Cabin (Canvas data outline display page)
・ Cabin (IS data thumbnail display page)
・ Cabin (Personal note display page)
・ AssociaPad Viewer
The following processing is performed by calling from a subsystem such as:

[Search] Search the video data that matches the input conditions from the recorded data.
[Input parameters]: The input parameters for the search are as follows.
“Conference ID (sid)”: Specify the conference to be played back.
“Content ID (cid)”; specifies a content ID indicating video data to be reproduced.
“Playback start time (t)”: Specify the start time of video playback.

  [Video Data Selection Method] First, a method for selecting one of a plurality of stored video files will be described. Several methods are provided here.

  [Selection by Conference ID] When referring to a conference (in Cabin), the system can recognize the conference ID that the user is referring to. Therefore, when a user is referring to specific conference data in Cabin and reproducing the video of the conference, the video data to be reproduced can be searched using the conference ID. When a conference ID is given, the video associated with the conference ID is searched and played.

  [Selection by time] Each video data is recorded with recording start and end times. Therefore, the user designates the time, and the system can select and reproduce the video data by searching for the video data including the time in the recording time range.

[Search condition combination selection (mixed)]
In addition to the conference ID and time, users who are allowed to browse and location information can be used for searching. However, such information alone may not be sufficient as a search condition. Therefore, a search is performed by combining these pieces of information. Thereby, search accuracy can be improved.

For example, if you enter host name: videoserver and program name: viewer,
http: // videoserver / viewer? sid = 1 & cid = 10 & t = 2004/2 / 20-10: 20: 30
The video playback is instructed under the search conditions of conference ID: 1, content ID: 10, time: 2004/2/20 10:20:30.

Also, input parameters can be omitted, for example
http: // videoserver / viewer? t = 2004/2 / 20-10: 20: 30
Is a search request that uses only time information as a key.

[Presentation and selection of multiple candidates]
If there is more than one candidate video data as a result of searching using one of the methods described above (for example, when two videos are shot in one conference), the user can display a list of these candidate videos. One video data is finally determined by presenting it to the user and allowing the user to select it. That is, when a plurality of video data is obtained as a search result, the following processing is performed.

[List display] Outputs HTML data listing the time data of each video data. Here, each list is set as a link to a reproduction URL specifying a content ID.
[User selection] The user selects one of the lists displayed on the client PC. As a result, the video display request designating the video data is retransmitted to the server.
[Video Playback Data Output] At this stage, since the video data is uniquely determined, the server transmits HTML data for playing back the data.
[Data transmission] As a result of the above processing, HTML data including the following information is transmitted to the client.

“Video data URL”; Pointer information for accessing video data “Time chart URL”; Pointer information for accessing time chart data “User operation processing program”; Web browser of client PC for seek operation etc. A javascript program to be executed above.
When single video data is extracted as a search result, the server transmits HTML data for reproducing the data (video reproduction data output).

  [Playback Function] A function related to playback of HTML data received from the server will be described. FIG. 69 shows a playback screen in which the received video playback data is displayed on the client PC. In addition to the time chart and video, the “Start”, “Pause”, and “Stop” buttons for playback are displayed. By pressing these buttons, video playback is started / paused / stopped in the same manner as a general video playback device.

[Client-side program] As described above, the video playback data is HTML data, and includes a program written in javascript or the like that is executed on the Web browser of the client PC. The operation and function of the program related to the reproduction of HTML data received from the server on the client side will be described.
[Current Time] The current time bar displayed on the time chart is moved as the video playback progresses. Fires periodically (every second), gets the current playback time from the video playback component, and sets the vertical position of the current time bar element.

  [Time jump] It takes time to reproduce video and audio data itself. It usually takes 1 hour to play the whole video data for 1 hour. Assuming that the video file to be played can be selected, the user further needs to select a specific time range within it. Hereinafter, a function for searching an important time range in the video data provided by the system of this embodiment will be described.

[Time chart display]
The playback time is specified by spatially displaying the time on a time chart and instructing the position within the time with a pointing device such as a mouse. The following information is displayed on the time chart.

[Sound source direction]
The sound source direction measured and recorded by the recording subsystem is displayed. The horizontal axis of the time chart is made to correspond to the horizontal axis of the panoramic video image, and a mark is displayed in the direction and time when the utterance occurred. If the image in the same horizontal position as the mark is seen, the speaker can be identified, so the user can specify the speaker. Unlike the content mark described below, the utterance mark is automatically recorded and displayed as long as a conversation is made, and is characterized in that no burden is placed on the user.

  [Mark display] Called to display the time corresponding to other content display such as Cabin, AssociaPad on the time chart. A mark is displayed on the time chart corresponding to the input time and label.

[Content (APad, Canvas)]
When recording in cooperation with a time recording system such as AssociaPad or Canvas, the time information is also displayed on the time chart. For example, in FIG. 69, a mark is displayed at a position corresponding to the content “today's conclusion”. This makes it possible to realize abundant visual expressions. Unlike the previous utterance mark, the content mark records the user's device operation, so that an accurate time can be displayed.

[Seek] Change the video playback time. Set the current time in the video playback component. There are two kinds of calling scenes as follows.
[A: From within the video playback screen] It is activated from a mouse click event on the time chart, calculates the corresponding time on the time chart from the click position, and changes the playback time.
[B: From an external program] The recording start time of the video being played is subtracted from the time (absolute time) that is activated from the click on each content display on the AssocidPad or Canvas and recorded with the content, Jump to that time after finding the relative time.

The present invention has been described with reference to examples. In the embodiment, the following effects can be obtained.
(1) Various meeting documents generated at the meeting can be managed in association with each meeting, and the meeting context, such as the meeting flow, history, decisions, and subsequent action results, is securely shared by the meeting members. Can be expected to significantly improve the efficiency of group work.
(2) By associating objects in a conference document with different generation times, for example, streaming media (video) and non-streaming data (minutes) generated at the same conference, the conference context can be understood and shared with certainty. It can be expected to be greatly improved.
(3) Users can manage and reference conference documents or objects in conference documents that are generated by various conference applications with different manners and media based on attribute information given to the conference documents or objects in the conference documents. Regardless of the use tool depending on the purpose and thinking style, the target context can be shared with the group reliably and quickly, or can be grasped by the individual, and a significant improvement in the efficiency of group work can be expected.
(4) By defining the data structure of conference documents generated by various conference applications and the services that access them as a platform, the general versatility of the system can be expected to improve significantly. This makes it possible to efficiently provide various conference document creation tools with different manners.

It is explanatory drawing showing the basic concept of one Embodiment of this invention. It is a block diagram which shows the hardware constitutions of embodiment system. It is a flowchart which shows the utilization method of embodiment system. It is a figure which shows the architecture of embodiment system. 1 is a configuration diagram of a system according to the present invention. It is a data structure figure of the database concerning the present invention. It is a figure which shows the data structure of a meeting document. It is a figure which shows the data structure of the content of a meeting document. It is a figure which shows the data structure of the semantic attribute of a meeting document. It is a figure which shows the data structure of the application information list | wrist of a meeting document. It is a figure which shows the data structure of the application data list | wrist of a meeting document. It is a figure which shows the data structure of the eKC data of a meeting document. It is a figure which shows the data structure of the eKC original data of a meeting document. It is a figure which shows the data structure of IS data which is a meeting document. It is a figure which shows the data structure of MC data which is a meeting document. It is a figure which shows the data structure of MC original data of a meeting document. It is a figure which shows the data structure of AssociaPad data which is a meeting document. It is a figure which shows the data structure of AssociaPad original data of a meeting document. It is a figure which shows the data structure of a personal information table. It is a figure which shows the data structure of a ToDo information table. It is a figure which shows the data structure of a document information table. It is a figure which shows the data structure of a user information table. It is a figure which shows the data structure of an organization information table. It is a figure which shows the data structure of a meeting room information table. It is a figure which shows the data structure of a group information table. It is a figure which shows the data structure of a holding meeting table. It is a figure which shows an operation function (method). 1 is a configuration diagram of a system using a conference application Canvas according to the present invention. FIG. This is a document creation / edit screen for Canvas. It is a front view which shows an example of the display screen of a display based on a master client application. Schematic behavior of objects in the master client application It is a front view which shows an example of the display screen of a display based on a master client application. It is explanatory drawing which shows the outline | summary of the 2nd Example relevant to a basket. It is a display example of a login screen in Cabin. It is a display example of the top screen for the logged-in user in Cabin. It is a display example of a meeting recording surface. It is an example of a reference screen that refers to a Canvas document from PCab. It is the example of a reference screen which referred IS document from PCab. It is the example of a reference screen which referred AP document from PCab. MC playback screen. It is a display example when the board document content of the conference document is scrolled to the vicinity of “definition of data structure”. This is a detailed display screen that displays the bibliographic items of the conference document where the task occurred. It is a list display screen of “attention matters”. It is a list display screen of “attention matters”. It is an example of a screen on which “notices” by an IS document are displayed. It is a block diagram of the system using conference application IS based on this invention. It is an IS system block diagram for performing handwritten annotation in IS. It is an IS system block diagram for performing handwritten annotation in IS. It is a figure which shows the example of an operation screen of IS application. It is a figure explaining the concept of the annotation to the document document by IS application. It is an example of the display screen of a document sentence. It is an example of the document screen (annotation screen) after an annotation. It is an example of an annotation image. It is a flowchart which shows the annotation taking-in procedure to a document document. It is a flowchart which shows the screen recording procedure in IS application. It is a flowchart which shows the automatic screen recording mode in IS application. It is a conceptual diagram of the complementary process of automatic screen recording in IS application. It is a block diagram of the system using conference application AP based on this invention. It is a figure which shows the example of a display screen on the information terminal of a "personal memo program." It is a text input screen in the “personal memo program”. It is a block diagram of the configuration of a portable terminal on which a personal memo program operates. It is an operation | movement flowchart of a personal memo program. It is an example of the memo file recorded by the personal memo program. It is a block diagram of a system using a conference application MC according to the present invention. It is a schematic block diagram which shows the hardware constitutions of the recording subsystem which "MC" operates. It is explanatory drawing of arrangement | positioning of the microphone and camera in a recording subsystem. It is a figure which shows schematic structure of a panoramic camera. It is a schematic block diagram which shows the hardware constitutions of the reproduction | regeneration system which "MC" operates. It is an example of a playback screen in which video playback data is displayed on a client PC.

Claims (17)

A group of conference applications for recording context information attached to conference proceedings,
A conference support system comprising at least a content management application for managing conference application documents generated by these conference application groups in association with each other in a conference unit. A first conference application group for recording the meeting proceedings as a conference application document;
A second conference application group for recording streaming data attached to the conference proceedings, etc .;
A third conference application group for associating and managing the conference application document and streaming data on a conference basis;
A conference support system characterized by comprising: Proceedings recording means for recording the content in association with the recording time of the content;
Agenda data registration means for registering each agenda data created by the agenda recording means,
Video recording means for recording a meeting scene;
Video data registration means for registering video data created by the video recording means;
Agenda data management means for managing each agenda data and the video data as a common agenda data in association with each other,
Agenda data designation means for designating desired agenda data among the agenda data managed by the agenda data management means as first agenda data;
Content specifying means for specifying desired content in the first agenda data;
Reference means for referring to second agenda data among agenda data managed by the agenda data management means, at a recording time associated with the content in the first agenda data designated by the content designation means And a corresponding reference means for referring to the content in the second agenda data. A proceeding recording unit comprising a content input unit that receives input of content, and an attribute assigning unit that assigns a predetermined attribute to a desired content among the input content;
Agenda data management means for managing agenda data created by the agenda recording means;
Reference means for referring to desired agenda data among the agenda data managed by the agenda data management means, and refers to content in association with the type of attribute assigned to the content in the agenda data by the attribute assigning means Referencing means, and
A conference support system characterized by comprising: Proceedings recording means for recording the content of the conference in association with the recording time of the content;
Agenda data registration means for registering agenda data created by the agenda recording means;
Streaming data recording means for recording a conference scene;
Streaming data registration means for registering the streaming data created by the streaming data recording means;
Management means for managing the agenda data created by the agenda recording means and the streaming data created by the streaming data recording means in association with each other;
Content specifying means for specifying desired content in the agenda data;
Replay means for replaying streaming data associated with the agenda data, replaying a scene corresponding to the time associated with the content designated by the content designation means;
The conference support system according to claim 3, further comprising:   The meeting support system according to claim 3, wherein at least one of the proceeding recording units is a canvas. 7. The meeting support system according to claim 6, wherein the agenda data created by the agenda recording means is stored in a storage on a network and can be referred to after being converted into a view set for each user by the browsing means.   The meeting support system according to claim 6 or 7, wherein "semantic attribute" and "visual attribute" are defined as attributes to be given to the agenda data created by the agenda recording means.   9. The meeting support system according to claim 8, wherein "shared information", "user information", and "date information" are defined as internal values of the "semantic attribute".   By giving "semantic attribute"-"shared information", the object is given the meaning of "information shared by all members", and as a specific operation, a predetermined view of the browsing means of all members, The conference support system according to claim 9, wherein the agenda data to which “semantic attribute”-“shared information” is added is picked up and displayed.   By giving “semantic attribute”-“user information”, the object is given the meaning of “information associated with the designated user”, and as a specific operation, a predetermined user's browsing means The conference support system according to claim 9, wherein the agenda data to which “semantic attribute” − “user information” is given is picked up and displayed in the view.   The meeting support system according to claim 3, wherein at least one of the proceeding recording means is IS.   The meeting support system according to claim 3, wherein at least one of the proceeding recording means is an AP.   4. The conference support system according to claim 3, wherein the video recording means is an MC.   The conference support system according to claim 4, wherein the proceeding recording unit is an IS.   11. The conference support system according to claim 4, further comprising registration means for registering with a predetermined attribute set in advance when registering the agenda data. 5. The meeting support system according to claim 4, wherein the proceeding recording means is an MC.

Images