JP7043932B2 - Conference equipment, conference systems, information processing methods and programs - Google Patents

Description

The present invention relates to a conference device, a conference system, an information processing method and a program.

A paperless conference system that displays electronic documents on a PC (Personal Computer) or smart device, synchronizes display pages between devices, and allows each participant to freely write notes by hand while proceeding with the conference. Are known. In such a paperless conference system, there is a need for conference participants to read back the conference materials in which their memos at the conference are written at a later date (after the conference is over). Therefore, a "material with memo" is created and saved by merging the memo written by each participant into the meeting material, and the storage location of the material with memo (URL (Uniform Resource Locator), etc.) is sent to the participants by e-mail or the like at a later date. The technology of paperless conference systems that can be sent and downloaded by participants is already known. Here, merging indicates a process of synthesizing the written memo data and the conference material.

As a technology to realize such a paperless conference system, a memo written on the conference material displayed on the mobile terminal during the conference is created as memo data, and the conference material and the memo data are combined at the end of the conference. By creating a synthetic material (corresponding to the above-mentioned material with memo), storing it in the specified storage location on the server, and sending an e-mail describing the storage location to the email address of the conference participant, the participant Discloses a technique for downloading synthetic data from the storage location at a later date (see Patent Document 1). In this way, the reason why we send an email to download the edited synthetic material at a later date is that if the participants try to get the edited synthetic material (material with memo) immediately after the meeting. Then, the creation process (which needs to be created individually for each participant) puts a heavy load on the system, the creation process takes a long time, and as a result, there is a high possibility that the participants will be kept waiting. There is.

However, for the participants who participated in the meeting, depending on the degree of urgency, it may take some time, so there are times when you want to obtain the edited synthetic material (for example, material with notes) immediately, or at a later date. In some cases, it would be good if it could be obtained. In the technique described in Patent Document 1, each participant can obtain the document with memo from the storage location at a later date by sending an e-mail notifying the storage location after the material with memo has been created. However, it is not possible to obtain materials with memos immediately after the meeting. That is, there is a problem that it is not possible to select the acquisition timing of the memo-attached material, such as acquiring the memo-attached material immediately after the meeting or acquiring it later. Along with this problem, if you choose to acquire materials with memos immediately after the meeting, there is also the problem that you do not have the convenience of changing to acquiring them later because of the waiting time.

The present invention has been made in view of the above, and provides a conference device, a conference system, an information processing method, and a program capable of improving convenience when a conference participant obtains materials with memos. The purpose is.

In order to solve the above-mentioned problems and achieve the object, the present invention acquires the memo data added in the conference terminal and requests the creation of the data with memo based on the conference use data and the memo data. An acquisition unit that stores a request in a queue, a creation unit that creates data with a memo based on the conference use data and the memo data after the memo data is acquired by the acquisition unit, and the conference terminal. The first acquisition form in which the memo-attached data is downloaded by the conference terminal when the creation of the memo-attached data is completed after receiving the creation request of the memo-attached data from, and the creation from the conference terminal. Of the second acquisition modes in which the data with memos is downloaded by the conference terminal at an arbitrary timing after the request is made and the data with memos are created, the memos are attached based on the form selected by the conference terminal. The second acquisition of the sending unit that sends data to the conference terminal and the second acquisition after the first acquisition mode is selected in the conference terminal and at least until the data with memo is created by the creation unit. Based on the number of the creation requests stored in the queue, the processing for the creation request corresponding to the memo-attached data is performed so as to be displayed on the screen for operating whether to switch to the form. The sending unit includes a second notification unit that notifies the waiting period until the first acquisition mode is selected, and at least until the data with memo is created by the creating unit. When the conference terminal is switched to the second acquisition mode, the memo-attached data is sent to the conference terminal based on the second acquisition mode.

According to the present invention, it is possible to improve the convenience for the participants of the conference to obtain the material with memo.

FIG. 1 is a diagram showing an example of the overall configuration of the conference system according to the embodiment. FIG. 2 is a diagram showing an example of the appearance of the participant terminal according to the embodiment. FIG. 3 is a diagram showing an example of the hardware configuration of the participant terminal according to the embodiment. FIG. 4 is a diagram showing an example of the hardware configuration of the conference server according to the embodiment. FIG. 5 is a diagram showing an example of the configuration of the functional block of the participant terminal according to the embodiment. FIG. 6 is a diagram showing an example of the configuration of the MemoData message. FIG. 7 is a diagram showing an example of a reply configuration for a MemoData message. FIG. 8 is a diagram showing an example of the configuration of a NumberOfWaiting message. FIG. 9 is a diagram showing an example of a reply configuration for a NumberOfWaiting message. FIG. 10 is a diagram showing an example of the configuration of the StopMemoPhaseInfo message. FIG. 11 is a diagram showing an example of the configuration of a MemoPassword message. FIG. 12 is a diagram showing an example of a material display screen during a meeting. FIG. 13 is a diagram showing an example of the configuration of the functional block of the conference server according to the embodiment. FIG. 14 is a diagram showing an example of the configuration of the MemoPhaseInfo message. FIG. 15 is a diagram showing an example of the configuration of the document management table with memo. FIG. 16 is a diagram illustrating a queue of requests requesting the creation of materials with memos. FIG. 17 is a sequence diagram showing an example of the flow of the selection process of the material acquisition method with memo of the conference system according to the embodiment. FIG. 18 is a sequence diagram showing an example of the flow of the document creation / acquisition process with memo of the conference system according to the embodiment. FIG. 19 is a diagram showing an example in which a memo is written on the material display screen. FIG. 20 is a diagram showing an example of a memo save / exit screen. FIG. 21 is a diagram showing an example of an acquisition method selection screen. FIG. 22 is a diagram showing an example of a material selection screen. FIG. 23 is a diagram showing an example of a state transition screen (waiting for creation start). FIG. 24 is a diagram showing an example of a state transition screen (under construction). FIG. 25 is a diagram showing an example of a state transition screen (during downloading). FIG. 26 is a diagram showing an example of a state transition screen (download completed). FIG. 27 is a diagram showing an example of a password setting screen. FIG. 28 is a diagram showing an example of the acquisition URL screen. FIG. 29 is a diagram showing an example of a password input screen.

Hereinafter, embodiments of a conference device, a conference system, an information processing method, and a program according to the present invention will be described in detail with reference to FIGS. 1 to 29. Further, the present invention is not limited to the following embodiments, and the components in the following embodiments include those easily conceived by those skilled in the art, substantially the same, and so-called equivalent ranges. Is included. Further, various omissions, substitutions, changes and combinations of components can be made without departing from the gist of the following embodiments.

(Overall configuration of the conference system)
FIG. 1 is a diagram showing an example of the overall configuration of the conference system according to the embodiment. The overall configuration of the conference system 1 according to the present embodiment will be described with reference to FIG.

As shown in FIG. 1, the conference system 1 according to the present embodiment has a configuration in which the conference server 20 and the participant terminals 10a to 10e are connected to each other so as to be communicable via the network 2. It should be noted that the number of participant terminals participating in the paperless conference is not limited to the five participant terminals 10a to 10e shown in FIG. 1, and two or more participant terminals can communicate with the network 2. If connected to, a paperless conference will be realized. In this case, with respect to two or more participant terminals, when indicating an arbitrary participant terminal or generically, it is simply referred to as "participant terminal 10".

The conference server 20 is a conference device in which participants who participate in a paperless conference (hereinafter, simply referred to as “conference”) perform overall control for conducting the conference via the participant terminals 10a to 10e, respectively. .. A conference scheduled to be held can be registered in advance in the conference server 20. In addition, data of one or more conference materials used in the conference can be registered in association with the conference. At this time, the conference server 20 issues a DocID for identifying each of the registered conference materials.

The participant terminal 10 (participant terminals 10a to 10e in FIG. 1) establishes a session with another participant terminal 10 based on the control of the conference server 20, and the conference is established through the established session. It is a conference terminal that sends and receives various messages necessary for the above and memo data described later. In addition to the above-mentioned message, video data, audio data, and drawing data may be transmitted and received. That is, the above-mentioned paperless conference can be applied not only to a form in which information of conference materials is shared, but also to a video conference (video conference) in which video data, audio data, etc. are transmitted and received as described above. It is possible. In this case, at the time of the conference, the participant terminal 10 transmits video data, audio data, and drawing data to the conference server 20 at the time of transmission, and the conference server 20 transmits the video to the participant terminal 10 at the partner base. Send data, audio data and drawing data. Further, the participant terminal 10 receives the video data, the audio data, and the drawing data of the participant terminal 10 of the partner base from the conference server 20 at the time of reception. The participant terminal 10 is, for example, a tablet, a PC, a smartphone, a video conference terminal, an electronic blackboard, or the like. In the following, the participant terminal 10 will be described as being a tablet.

For example, when a conference is held on the participant terminals 10a to 10c in the conference system 1 shown in FIG. 1, the data transmitted by the participant terminals 10a is transmitted to the participant terminals 10b and 10c via the conference server 20. It is not transmitted to the participant terminals 10d and 10e. Similarly, the data transmitted by each of the participant terminals 10b and 10c is transmitted to the participant terminals 10 participating in the conference via the conference server 20, and the participant terminals 10 not participating in the conference (participants). It is not transmitted to the terminals 10d and 10e). As a result, in the conference system 1, a conference between a plurality of participant terminals 10 is realized.

Further, when the participant terminal 10 participates in the conference, the participant terminal 10 downloads the data of the conference material to be documented in the conference from the conference server 20 via the network 2. In this case, the participant terminal 10 also acquires a DocID that identifies the downloaded conference material. During the meeting, the participants can hold a meeting while looking at the contents of the meeting materials displayed on the participant terminal 10, and can write a memo at that time, as will be described later.

Further, the software executed on the participant terminal 10 may be a native application that operates independently on the participant terminal 10, or may be a Web application that operates on a Web browser.

The network 2 is a communication network capable of bidirectional data communication such as a LAN (Local Area Network), a dedicated line, or the Internet. The network 2 may include a plurality of types of networks having different protocols, and may include either a wired network or a wireless network.

(Hardware configuration of participant terminals)
FIG. 2 is a diagram showing an example of the appearance of the participant terminal according to the embodiment. FIG. 3 is a diagram showing an example of the hardware configuration of the participant terminal according to the embodiment. The hardware configuration of the participant terminal 10 according to the present embodiment will be described with reference to FIGS. 2 and 3.

As shown in FIG. 3, the participant terminal 10 according to the present embodiment operates the CPU (Central Processing Unit) 201, the memory 202, the storage device 203, the touch panel display 204, the microphone 206, and the speaker 207. A unit 208 and a wireless communication unit 209 are provided. Each of these devices is communicably connected to each other by a bus 215 such as an address bus and a data bus.

The CPU 201 is an integrated circuit that controls the operation of the entire participant terminal 10.

The memory 202 is a storage device such as a volatile RAM (Random Access Memory) used as a work area of the CPU 201.

The storage device 203 is a non-volatile auxiliary storage device that stores various programs that realize the operation of the participant terminal 10 and various data such as conference materials used in the conference. The storage device 203 is, for example, a flash memory, an HDD (Hard Disk Drive), an SSD (Solid State Drive), or the like.

The touch panel display 204 has a touch detection function having a function of displaying conference materials and the like on a display device and a touch detection function of transmitting the coordinates of the pen (for example, the pen 251 shown in FIG. 2) touching the touch panel to the CPU 201. It is a display device. As shown in FIG. 2, the touch panel display 204 has a function as an electronic blackboard on which a memo can be written by displaying a locus that traces the surface of the panel with a pen 251 for example. That is, the drawing data written on the touch panel display 204 can be shared with the participant terminal 10 at the partner base. Further, the display device of the touch panel display 204 is configured by, for example, an LCD (Liquid Crystal Display), an organic EL (Organic Electro-Luminence) display, or the like.

The microphone 206 is, for example, a sound collecting device that inputs the voices of the participants participating in the conference.

The speaker 207 is a device that outputs sound according to the control of the CPU 201. As shown in FIG. 2, for example, the speaker 207 is installed on the upper side of the touch panel display 204, and for example, the voice data picked up by the participant terminal 10 of the partner base received via the network 2 is voiced. Is output as.

The operation unit 208 is an input device such as a button for performing various operations on the participant terminal 10. The operation unit 208 is installed on the lower side of the touch panel display 204, for example, as shown in FIG. As shown in FIG. 2, the operation unit 208 is not limited to being configured by a button or the like as hardware. For example, the software switch on the touch panel display 204 by the touch detection function of the touch panel display 204. It may be configured as.

The wireless communication unit 209 is a device for wirelessly communicating data with an external device by using a network such as the Internet (for example, the network 2 shown in FIG. 1 described above). The wireless communication unit 209 is realized by a wireless communication standard such as Wi-Fi (registered trademark) (Wireless Fidelity).

The hardware configuration of the participant terminal 10 is not limited to the configuration shown in FIG. For example, the participant terminal 10 is a ROM (Read Only Memory), which is a non-volatile storage device that stores firmware or the like for controlling the participant terminal 10, a PC (Personal Computer), an external storage device, or the like. It may be provided with an I / F or the like for an external device for connecting the above.

Further, in FIG. 2, the participant terminal 10 shows a configuration in which the microphone 206 and the speaker 207 are built in the main body, but at least one of these may be configured as a separate body. For example, when the speaker 207 is not a built-in device but a separate external device, it may be connected to the participant terminal 10 via the above-mentioned I / F for the external device.

(Hardware configuration of conference server)
FIG. 4 is a diagram showing an example of the hardware configuration of the conference server according to the embodiment. The hardware configuration of the conference server 20 according to the present embodiment will be described with reference to FIG.

As shown in FIG. 4, the conference server 20 includes a CPU 301, a ROM 302, a RAM 303, an auxiliary storage device 304, a media drive 306, an operating device 307, a network I / F 308, a display 309, and a DVD (Digital). It is equipped with a Versail Disc) drive 311. Each of these devices is communicably connected to each other by a bus 312 such as an address bus and a data bus.

The CPU 301 is a device that controls the operation of the entire conference server 20. The ROM 302 is a non-volatile storage device that stores a program for the conference server 20. The RAM 303 is a volatile storage device used as a work area of the CPU 301.

The auxiliary storage device 304 is a non-volatile storage device that stores various data such as conference materials and created materials with memos. The auxiliary storage device 304 is, for example, an HDD or an SSD.

The media drive 306 is a device that controls reading and writing of data to the media 305 such as a flash memory according to the control of the CPU 301. The media 305 is a storage device that can be attached to and detached from the media drive 306. The media 305 is not limited to the flash memory as long as it is a non-volatile memory that reads and writes data under the control of the CPU 301, and an EEPROM (Electrically Erasable and Programmable ROM) or the like may be used.

The operation device 307 is an input device for inputting characters and numbers, selecting various instructions, moving a cursor, and the like. The operating device 307 is, for example, a mouse or a keyboard.

The network I / F 308 is an interface for communicating data using the network 2. The network I / F 308 is, for example, a NIC or the like.

The display 309 is a display device that displays characters, numbers, various screens, operation icons, and the like. The display 309 is, for example, a CRT (Cathode Ray Tube) display, an LCD, an organic EL display, or the like.

The DVD drive 311 is a device that controls reading and writing of data to the DVD 310 as an example of a detachable storage medium. The DVD 310 is, for example, a DVD-ROM, a DVD-R, a DVD-RW (DVD Rewritable), or the like. In addition, the above-mentioned removable recording medium may be a CD-R (Compact Disc Recordable), a Blu-ray disc, or the like.

The hardware configuration of the conference server 20 is not limited to the configuration shown in FIG. For example, if it is not necessary to use external media (media 305, DVD 310, etc.), the media drive 306 and the DVD drive 311 may not be provided.

(Configuration and operation of functional blocks of participant terminals)
FIG. 5 is a diagram showing an example of the configuration of the functional block of the participant terminal according to the embodiment. FIG. 6 is a diagram showing an example of the configuration of the MemoData message. FIG. 7 is a diagram showing an example of a reply configuration for a MemoData message. FIG. 8 is a diagram showing an example of the configuration of a NumberOfWaiting message. FIG. 9 is a diagram showing an example of a reply configuration for a NumberOfWaiting message. FIG. 10 is a diagram showing an example of the configuration of the StopMemoPhaseInfo message. FIG. 11 is a diagram showing an example of the configuration of a MemoPassword message. The configuration and operation of the functional block of the participant terminal 10 according to the present embodiment will be described with reference to FIGS. 5 to 11.

As shown in FIG. 5, the participant terminal 10 according to the present embodiment includes a conference processing unit 401, a screen control unit 402, a memo data management unit 403, a creation request unit 404, and a material acquisition unit 405 (reception unit). ), A password setting unit 406, an authentication request unit 407, a communication unit 408, an input unit 409, a display control unit 410, a display unit 411, and a storage unit 412.

The conference processing unit 401 is a functional unit that performs general processing (conference participation processing, synchronization processing, presentation right acquisition processing, etc.) for participating in a paperless conference and holding a paperless conference. The conference processing unit 401 is realized, for example, by the CPU 201 shown in FIG. 3 executing a program.

The screen control unit 402 is a functional unit that controls screen transition processing of the screen to be displayed on the display unit 411 and processing on each screen. The screen control unit 402 is realized, for example, by the CPU 201 shown in FIG. 3 executing a program.

The memo data management unit 403 is a functional unit that stores and manages memos written (added) via the input unit 409 in the storage unit 412 as memo data. The memo data management unit 403 is realized, for example, by the CPU 201 shown in FIG. 3 executing a program.

The creation request unit 404 requests the creation of materials with memos by merging the above memo data and the conference materials used in the conference, and requests for the number of such requests (requests) held in the queue of the conference server 20. Is a functional unit that performs the above for the conference server 20. Specifically, the creation request unit 404 sends, for example, a MemoData message as shown in FIG. 6 to the communication unit 408 as a request for creating a material with a memo by merging the above memo data and the conference material used in the conference. And transmission to the conference server 20 via the network 2. As shown in FIG. 6, the MemoData message includes a header part that defines the type of the message and a body part that is the main body of the message. As shown in FIG. 6, in the body part of the MemoData message, among the memo data held in the participant terminal 10, the memo data written in the conference material separately selected to be acquired as the material with a memo is stored. included. The memo data is composed of one or a plurality of stroke information. The stroke information includes DocID, Page, and Trace information as shown in FIG. The DocID is an ID of the conference material in which the memo is written (an ID that uniquely identifies the conference material). Page is the page number on which the memo is written in the conference material. The Trace contains a collection of points that make up the memo as a sequence of XY coordinates on the screen. The substance of the memo has been described as a sequence of XY coordinates on the screen, which is a collection of points constituting the memo, as in Trace, but the present invention is not limited to this, and graphic data, stamp data, etc. may be used. It may be included.

Then, after transmitting the above-mentioned MemoData message to the conference server 20, the creation request unit 404 receives, for example, a reply to the MemoData message as shown in FIG. 7. As shown in FIG. 7, the reply of the MemoData message includes a header part that defines the type of reply and a body part that is the main body of the reply. As shown in FIG. 7, in the body part of the reply of the MemoData message, the MemoID (memo ID) uniquely assigned by the conference server 20 to the MemoData message (request for creating a document with a memo) received by the conference server 20. ) ("12ab" in the example shown in FIG. 7) is included.

Further, the creation request unit 404 requests, for example, the NumberOfWaiting message as shown in FIG. 8 as a request for the number of the requests (requests) held in the queue of the conference server 20 performed before selecting the acquisition method of the document with memo. Is transmitted to the conference server 20 via the communication unit 408 and the network 2. As shown in FIG. 8, the NumberOfWaiting message includes a header part that defines the type of the message and a body part that is the main body of the message. However, as shown in FIG. 8, there is no content in the body part of the NumberOfWaiting message.

Then, after transmitting the above-mentioned NumberOfWaiting message to the conference server 20, the creation request unit 404 receives, for example, a reply to the NumberOfWaiting message as shown in FIG. As shown in FIG. 9, the reply of the NumberOfWaiting message includes a header part that defines the type of reply and a body part that is the main body of the reply. As shown in FIG. 9, in the body part of the reply of the NumberOfWaiting message, the number of requests for creating the document with memo held in the queue when the conference server 20 receives the NumberOfWaiting message (Figure 9). In the example shown in 9, 5) are included.

The creation request unit 404 is realized, for example, by the CPU 201 shown in FIG. 3 executing a program.

The conference material to which the memo data is merged is not limited to, for example, document data such as PDF (registered trademark) (Portable Document Form) data, and may be, for example, video (moving) data or image data. ..

The material acquisition unit 405 is a functional unit that acquires (downloads) a material with a memo from the conference server 20 via the network 2 and the communication unit 408, in which the memo data transmitted by the creation request unit 404 and the conference material are merged. Is. The document acquisition unit 405 is realized, for example, by the CPU 201 shown in FIG. 3 executing a program.

The password setting unit 406 is a functional unit that is input on the password setting screen (see FIG. 27) described later and transmits a password used for authentication in the conference server 20 when acquiring materials with memos to the conference server 20. Specifically, the password setting unit 406 transmits, for example, a MemoPassword message including a password entered on the password setting screen to the conference server 20 via the communication unit 408 and the network 2, as shown in FIG. .. As shown in FIG. 11, the MemoPassword message includes a header part that defines the type of the message, and a body part that is the main body of the message. As shown in FIG. 11, the body portion of the MemoPassword message includes a MemoID and a Password (password). The MemoID is an ID (“12ab” in the example shown in FIG. 11) that identifies the memo data merged into the conference material, and is the same as the MemoID described above. The password is a character string of the password entered on the password setting screen (in the example shown in FIG. 11, "myp @ password").

Further, the password setting unit 406 is, for example, as shown in FIG. 10 in order to stop the notification of the status (progress) of the process of creating the document with memo on the conference server 20 when the above-mentioned password setting screen is displayed. A StopMemoPhaseInfo message is transmitted to the conference server 20 via the communication unit 408 and the network 2. As shown in FIG. 10, the StopMemoPhaseInfo message includes a header part that defines the type of the message, and a body part that is the main body of the message. As shown in FIG. 10, in the body part of the StopMemoPhaseInfo message, a MemoID (memo ID) (example shown in FIG. 10) that identifies memo data to be stopped from notifying the status (progress) of the process of creating a document with a memo. Then, "12ab") is included.

The password setting unit 406 is realized, for example, by the CPU 201 shown in FIG. 3 executing a program.

When the authentication request unit 407 acquires the document with a memo, the password entered on the password input screen (see FIG. 29) described later in order to request the authentication on the conference server 20, and the memo requesting the acquisition. It is a functional unit that sends a MemoID (memo ID) that identifies the memo data merged with the attached material to the conference server 20. The authentication request unit 407 is realized, for example, by the CPU 201 shown in FIG. 3 executing a program.

The communication unit 408 is a functional unit that performs data communication with another participant terminal 10 and the conference server 20 via the network 2. The communication unit 408 is realized, for example, by the wireless communication unit 209 shown in FIG. 3 and the CPU 201 executing a program.

The input unit 409 is a functional unit that accepts writing by the pen of the participants of the conference. The input unit 409 is realized by the touch detection function in the touch panel display 204 shown in FIG.

The display control unit 410 is a functional unit that controls the display unit 411 to display various screens, images, and the like. The display control unit 410 is realized, for example, by the CPU 201 shown in FIG. 3 executing a program.

The display unit 411 is a functional unit that displays various screens, images, and the like under the control of the display control unit 410. The display unit 411 is realized by a function of displaying on the display device in the touch panel display 204 shown in FIG.

The storage unit 412 is a functional unit that stores various data such as various programs, video data, audio data, and drawing data that realize the operation of the participant terminal 10. Further, as shown in FIG. 5, the storage unit 412 includes a conference information storage unit 412a and a memo data storage unit 412b.

The conference information storage unit 412a stores conference materials shared by all participants, current display page information, conference participant information, current presenter information, downloaded materials with memos, and the like. The memo data storage unit 412b stores the memo written by the participant via the input unit 409 as memo data.

A part of the conference processing unit 401, screen control unit 402, memo data management unit 403, creation request unit 404, document acquisition unit 405, password setting unit 406, authentication request unit 407, communication unit 408, and display control unit 410, or All may be realized by a hardware circuit such as FPGA (Field-Programmable Gate Array) or ASIC (Application Specific Integrated Circuit) instead of a program which is software.

Further, each functional unit shown in FIG. 5 conceptually shows a function, and is not limited to such a configuration. For example, a plurality of functional units shown as independent functional units in FIG. 5 may be configured as one functional unit. On the other hand, the function of one functional unit in FIG. 5 may be divided into a plurality of functions and configured as a plurality of functional units.

(Overview of operation on participant terminals)
FIG. 12 is a diagram showing an example of a material display screen during a meeting. With reference to FIG. 12, an outline of the operation on the screen displayed on the participant terminal 10 according to the present embodiment and the operation associated therewith will be described.

When the participant terminal 10 requests the conference server 20 to participate in a specific conference, the participant terminal 10 downloads the conference materials used in the conference from the conference server 20. The screen shown in FIG. 12 is an example of a material display screen in which a specific page of the conference material downloaded by the participant terminal 10 is displayed on the display unit 411. On this material display screen, the displayed page changes in synchronization with the page turning operation of the participant who has the presenter authority, which will be described later.

The material display screen shown in FIG. 12 includes an "individual" button, a "share" button, a "presenter" button, a "memo entry" button, an "exit" button, and an "end" button.

The "individual" button is a button for a participant who uses the participant terminal 10 to write a personal memo (personal memo). Participants can press the "Individual" button (in the example shown in FIG. 12, the "Individual" button is pressed) and press the "Memo entry" button. Personal memos can be written via the input unit 409. As described above, the written personal memo is stored in the storage unit 412 (memo data storage unit 412b) as memo data by the memo data management unit 403.

The "share" button is for synchronizing (reflecting) the memo (shared memo) written by the participant who uses the participant terminal 10 with the participant terminals 10 of all the participants participating in the conference. It's a button. Therefore, the data of the shared memo written on the participant terminal 10 needs to be immediately transmitted to the conference server 20. Also, in order for participants to write shared notes, they must have presenter authority at the conference, which requires them to acquire presenter authority by pressing the "Presenter" button. .. For example, if none of the participants participating in the conference have the presenter authority, the presenter authority may be acquired by pressing the "presenter" button.

The "exit" button is a button for exiting the meeting. As will be described later, when the "Exit" button is pressed, a memo save / exit screen (see FIG. 20) for selecting whether or not to create a document with a memo is displayed.

The "End" button is a button for ending the conference. The "End" button may be displayed only on the participant terminal 10 used by the administrator who is proceeding with the conference, and when pressed, the conference is held in order to prevent the conference from being accidentally terminated. A screen requesting a password for terminating the above may be displayed.

(Configuration and operation of functional blocks of the conference server)
FIG. 13 is a diagram showing an example of the configuration of the functional block of the conference server according to the embodiment. FIG. 14 is a diagram showing an example of the configuration of the MemoPhaseInfo message. FIG. 15 is a diagram showing an example of the configuration of the document management table with memo. FIG. 16 is a diagram illustrating a queue of requests requesting the creation of materials with memos. The configuration and operation of the functional block of the conference server 20 according to the present embodiment will be described with reference to FIGS. 13 to 16.

As shown in FIG. 13, the conference server 20 according to the present embodiment includes a conference control unit 501, a material data management unit 502 (acquisition unit), a creation unit 503, and a creation status notification unit 504 (first notification unit, It has a second notification unit), a URL notification unit 505 (third notification unit), an authentication unit 506, a material transmission unit 507 (sending unit), a communication unit 508, and a storage unit 509.

The conference control unit 501 is a functional unit that performs general processing (user management for joining / leaving a conference, synchronization processing, display page management, presenter management, etc.) for realizing and proceeding with a paperless conference. The conference control unit 501 is realized, for example, by the CPU 301 shown in FIG. 4 executing a program.

When the document data management unit 502 acquires the MemoData message from the participant terminal 10 via the communication unit 508, the document data management unit 502 uniquely identifies the memo data included in the MemoData message (see, for example, FIG. 6). ) Is issued, and is registered and managed in the document management table 509c with a memo described later. Specifically, the material data management unit 502 registers the issued MemoID (memo ID) in the material management table 509c with a memo as shown in FIG. 15, for example. As shown in FIG. 15, the document management table 509c with memo is a table that associates the memo ID, the password, and the document path with memo. The password is a character string, a number string, or the like set for authentication when a material with a memo in which memo data is merged with the conference material is acquired after the conference. The material path with memo is a path indicating a save destination in which the material with memo created by the creation unit 503 is stored (stored). At the time when the memo ID is issued by the material data management unit 502, the password and the material path with the memo are not generated, so only the memo ID is registered.

The material management table with memo 509c shown in FIG. 15 is information in a table format, but is not limited to this, as long as it is information that associates the memo ID, the password, and the material path with memo. It is not limited to the table format.

Further, the material data management unit 502 includes the issued MemoID in a reply to the MemoData message (see, for example, FIG. 7), and transmits the issued MemoID to the participant terminal 10 via the communication unit 508 and the network 2. Further, the material data management unit 502 receives the acquired memo data as a request, merges it with the conference material (meeting use data), and stores it in a queue (queue) for creating the material with memo (data with memo).

Specifically, the material data management unit 502 stores memo data as a request in the queue 601 as shown in FIG. 16, for example. The queue 601 shown in FIG. 16 is stored in the order of request (1), request (2), request (3), request (4), ... For example, in the order of FIFO (First In, First Out) format. It is assumed that each request is processed by. Each request stored in the queue 601 is configured as, for example, the request 602 shown in FIG. 16, and includes MemoID, UserID, Notification, and one or more stroke information. The User ID is an ID that identifies a participant (user) who has transmitted memo data to the conference server 20 by the participant terminal 10. The Notification is information indicating whether or not to notify the progress status when the document with memo is created by the creation unit 503. The stroke information is the information of the main body of the memo data acquired by the material data management unit 502, and is as described above. Each stroke information included in the request 602 includes a DocID, a Page, and a Trace as shown in the stroke information 603 shown in FIG.

The document data management unit 502 is realized, for example, by the CPU 301 shown in FIG. 4 executing a program.

The creation unit 503 is a functional unit that creates a material with a memo by merging the memo data acquired by the material data management unit 502 and the conference material used in the conference. The creation unit 503 stores the created material with memo in the material storage unit 509b, and stores the path indicating the stored storage destination in association with the memo ID registered in the material management table 509c with memo, and has a memo. The document management table 509c is updated. The creation unit 503 is realized, for example, by the CPU 301 shown in FIG. 4 executing a program.

The creation status notification unit 504 has a function of notifying the participant terminal 10 that has requested the creation of the memo-attached material of the progress status of the creation when the creation process of the memo-attached material is started by the creation unit 503. It is a department. Specifically, the creation status notification unit 504 transmits, for example, a MemoPhaseInfo message as shown in FIG. 14 to the participant terminal 10 via the communication unit 508 and the network 2. As shown in FIG. 14, the MemoPhaseInfo message includes a header part that defines the type of the message, and a body part that is the main body of the message. As shown in FIG. 14, the body portion of the MemoPhaseInfo message includes a MemoID (memo ID), Phase, and NumberOfWaiting. Phase indicates the state of creation of the document with memo based on the message identified by MemoID. Examples include "waiting" (waiting for creation start), "processing" (creating), "downloading" (downloading), and "complete" (downloading completed). NumberOfWaiting is the number of requests for creating a document with a memo held in the queue at the time when the MemoPhaseInfo message is transmitted.

The creation status notification unit 504 is realized, for example, by the CPU 301 shown in FIG. 4 executing a program.

The URL notification unit 505 sends the participant terminal 10 the URL indicating the access destination for downloading the material with memo created by the creation unit 503 to the participant terminal 10 that has requested the creation of the material with memo. It is a function part to notify. The URL notification unit 505 is realized, for example, by the CPU 301 shown in FIG. 4 executing a program.

The authentication unit 506 is a functional unit that authenticates whether or not to allow the transmission of the material with memo by the password received together when the material with memo is requested from the participant terminal 10. The authentication unit 506 is realized, for example, by the CPU 301 shown in FIG. 4 executing a program.

The material sending unit 507 is a functional unit that sends (transmits) the material with a memo requested from the participant terminal 10 to the participant terminal 10 via the communication unit 508 and the network 2. The document sending unit 507 is realized, for example, by the CPU 301 shown in FIG. 4 executing a program.

The communication unit 508 is a functional unit that performs data communication with the participant terminal 10 via the network 2. The communication unit 508 is realized, for example, by the network I / F 308 shown in FIG. 4 and the CPU 301 executing a program.

The storage unit 509 is a functional unit that stores various data such as various programs that realize the operation of the conference server 20, conference materials, and created materials with memos. Further, as shown in FIG. 13, the storage unit 509 includes a conference information storage unit 509a, a material storage unit 509b, and a material management table 509c with a memo.

The conference information storage unit 509a stores the current display page information, the conference participant information, the current presenter information, and the like.

The material storage unit 509b stores conference materials, created materials with memos, and the like.

The document management table 509c with memo is as described above in FIG.

A part or all of the conference control unit 501, the material data management unit 502, the creation unit 503, the creation status notification unit 504, the URL notification unit 505, the authentication unit 506, the material transmission unit 507, and the communication unit 508 are software. It may be realized by a hardware circuit such as FPGA or ASIC instead of a program.

Further, each functional unit shown in FIG. 13 conceptually shows a function, and is not limited to such a configuration. For example, a plurality of functional units shown as independent functional units in FIG. 13 may be configured as one functional unit. On the other hand, the function of one functional unit in FIG. 13 may be divided into a plurality of functions and configured as a plurality of functional units.

(Flow of processing of conference system)
FIG. 17 is a sequence diagram showing an example of the flow of the selection process of the material acquisition method with memo of the conference system according to the embodiment. FIG. 18 is a sequence diagram showing an example of the flow of the document creation / acquisition process with memo of the conference system according to the embodiment. FIG. 19 is a diagram showing an example in which a memo is written on the material display screen. FIG. 20 is a diagram showing an example of a memo save / exit screen. FIG. 21 is a diagram showing an example of an acquisition method selection screen. FIG. 22 is a diagram showing an example of a material selection screen. 23 to 26 are diagrams showing an example of a state transition screen. FIG. 27 is a diagram showing an example of a password setting screen. FIG. 28 is a diagram showing an example of the acquisition URL screen. FIG. 29 is a diagram showing an example of a password input screen. The flow of processing of the conference system 1 according to the present embodiment will be described with reference to FIGS. 17 to 29.

<Step S11>
Participants who are participating in the conference using the participant terminal 10 write a memo about the conference via the input unit 409. Hereinafter, the written memo will be described as if the personal memo, which is a personal memo of the participant, is written. Here, an example in which a memo (personal memo) is written on the material display screen is shown in FIG. The memo data management unit 403 of the participant terminal 10 writes the written memo as memo data in the memo data storage unit 412b.

<Step S12>
When the "exit" button is pressed on the material display screen as shown in FIG. 19, the screen control unit 402 of the participant terminal 10 causes the display unit 411 to display the memo saving / exit screen as shown in FIG. .. On the memo save / exit screen, when the "exit" button is pressed, the process proceeds to step S13, and when the "save memo" button is pressed, the process proceeds to step S14.

<Step S13>
When the "Exit" button is pressed on the memo save / exit screen, the user exits without creating a document with a memo based on the memo data stored in the memo data storage unit 412b.

<Step S14>
When the "save memo" button is pressed on the memo save / exit screen, the creation request unit 404 of the participant terminal 10 receives the number of requests (requests for creating materials with memos) held in the queue of the conference server 20. As a request for, a NumberOfWaiting message (see, for example, FIG. 8) is transmitted to the conference server 20 via the communication unit 408 and the network 2. It should be noted that the "save memo" button may be pressed even after the meeting is over or during the meeting.

<Step S15>
When the material data management unit 502 of the conference server 20 receives the NumberOfWaiting message from the participant terminal 10 via the communication unit 508, the material data management unit 502 acquires the number of request queues at that time. Then, the material data management unit 502 includes the number of requests in the queue in the reply to the message and transmits the data to the participant terminal 10 via the communication unit 508 and the network 2. The creation request unit 404 of the participant terminal 10 receives a reply of the NumberOfWaiting message including the number of requests in the request queue via the communication unit 408.

<Step S16>
When the reply of the NumberOfWaiting message is received by the creation request unit 404, the screen control unit 402 causes the display unit 411 to display the acquisition method selection screen as shown in FIG. 21. As shown in the acquisition method selection screen of FIG. 21, the screen control unit 402 displays the number of requests included in the reply acquired by the creation request unit 404 as the “waiting number” (an example of the waiting period). In this way, by displaying the number of requests on the acquisition method selection screen, it is possible to predict the time until the material with memo is created, and it is possible to acquire the material with memo immediately. It will be easier to determine if it is more appropriate to acquire it later.

<Step S17>
Participants select whether to acquire the material with memo immediately or later on the acquisition method selection screen. The creation request unit 404 identifies whether the "acquire as is" button for immediately acquiring the material with memo is pressed or the "acquire later" button for acquiring later is pressed by the participant. Set the value to be set to a predetermined variable (acquisition variable).

Here, "acquire as it is" means that after the creation request unit 404 requests the conference server 20 to create a material with a memo, the material with a memo is immediately obtained when the material with a memo is created. The form to download and acquire (the first acquisition form) is shown. On the other hand, "acquire later" means that the creation request unit 404 only requests the conference server 20 to create the material with memo, and then the conference server 20 is made at an arbitrary timing after the material with memo is created. The form (second acquisition form) of accessing to and downloading and acquiring the material with a memo is shown.

<Step S18>
When the "acquire as is" button or the "acquire later" button is pressed by the participants, the screen control unit 402 causes the display unit 411 to display the material selection screen as shown in FIG. 22. The screen control unit 402 acquires thumbnail images of each conference material, confirms the presence or absence of memo data written in each conference material from the memo data storage unit 412b, and displays the acquired thumbnail image and the acquired thumbnail image on the material selection screen. Display the presence or absence of confirmed memo data. Here, the thumbnail image may be created from the file of each conference material stored in the conference information storage unit 412a, or may be acquired from the outside such as the conference server 20. Further, the presence or absence of the memo data written in each conference material can be confirmed, for example, by comparing the DocID of the stroke information included in the memo data with the DocID of the conference material. Further, as shown in FIG. 22, the screen control unit 402 may display information on the material name and the total number of pages.

Participants select the meeting material to be merged with the memo data of the memo (personal memo) written by the participant on the material selection screen. If any of the conference materials is selected on the material selection screen and the "Next" button is pressed, the process proceeds to step S19.

<Step S19>
The conference system 1 executes a memo-attached material creation / acquisition process for creating and acquiring memo-attached materials by merging the conference materials selected on the material selection screen and the memo data written in the conference materials. .. The document creation / acquisition process with memo is executed in the flow of steps S1901 to S1935 shown in FIG.

<< Step S1901 >>
The creation request unit 404 of the participant terminal 10 requests to create a material with a memo by merging the conference material selected on the material selection screen and the memo data written in the conference material, in order to make a MemoData message. Is transmitted to the conference server 20 via the communication unit 408 and the network 2. In the MemoData message, as one or more stroke information constituting the memo data, the DocID which is the ID of the conference material selected on the material selection screen, the Page which is the page number where the memo is written, and the memo are configured. A Trace indicating a set of points is included.

<< Step S1902 >>
Upon receiving the MemoData message via the communication unit 508, the material data management unit 502 of the conference server 20 issues (generates) a MemoID (memo ID) that uniquely identifies the memo data included in the MemoData message.

<< Step S1903 >>
The material data management unit 502 registers the issued MemoID (memo ID) in the material management table 509c with a memo. In this case, the path and password in the registered memo ID record are empty.

<< Step S1904 >>
The document data management unit 502 includes the issued MemoID in a reply to the MemoData message (see, for example, FIG. 7), and transmits the issued MemoID to the participant terminal 10 via the communication unit 508 and the network 2.

<< Step S1905 >>
The material data management unit 502 receives the acquired memo data as a request, merges it with the conference material, and stores it in a queue for creating a material with a memo. Specifically, the material data management unit 502 stores a request for a configuration including a MemoID (memo ID), a UserID, Notification, and one or a plurality of stroke information in a queue. Here, the material data management unit 502 sets "true" in the notification of the request.

<< Step S1906 >>
The creation unit 503 of the conference server 20 starts creating the memo-attached material by merging the memo data specified by each request with the conference material according to the order of the requests stored in the queue. When the creation request unit 404 in the participant terminal 10 described above sets a value for identifying that the "acquire as it is" button is pressed in the acquisition variable (when the first acquisition form is selected), the process proceeds to step S1907. When the process is performed and a value for identifying that the "acquire later" button is pressed is set (when the second acquisition mode is selected), the process proceeds to step S1920.

<< Step S1907 >>
The creation status notification unit 504 of the conference server 20 confirms that the Notification included in the request stored in the queue is "true", and the creation unit 503 notifies the progress status of the creation of the document with memo. , MemoPhaseInfo message is transmitted to the participant terminal 10 via the communication unit 508 and the network 2. The MemoPhaseInfo message notifying the progress of the creation of the document with memo by the creation status notification unit 504 is transmitted, for example, at predetermined intervals (for example, every 10 seconds). The MemoPhaseInfo message includes a MemoID (memo ID) that identifies memo data for which a memo-attached material is to be created, a Phase that indicates the creation status, and a NumberOfWaiting. When the request for creating the document with memo is in the waiting state in the queue, the creation status notification unit 504 sets Phase to "waiting" (waiting for creation start) and sends a MemoPhaseInfo message.

<< Step S1908 >>
When the screen control unit 402 of the participant terminal 10 receives the MemoPhaseInfo message whose Phase is “waiting” (waiting for creation start) from the conference server 20 via the communication unit 408, a document with a memo as shown in FIG. 23. The display unit 411 displays a state transition screen for displaying the fact that the creation of is in the waiting state and the "waiting number of people". By displaying the number of requests on the state transition screen in this way, it is possible to predict the time until the material with memo is created, and the first acquisition to immediately acquire the material with memo in step S17. Even if the form is selected, as shown below, it is possible to easily determine whether or not to switch to the second acquisition form in which the material with memo is acquired later.

As shown in FIG. 23, a “get later” button is arranged on the state transition screen, and the participant presses the “get later” button to obtain a document with a memo in step S17 described above. Even if the first acquisition form is selected as the acquisition method, it is possible to switch to the second acquisition form to be acquired later. The operation when this "acquire later" button is pressed will be described later in step S1915.

<< Step S1909 >>
When the creation status notification unit 504 is in the state of creating the document with memo by the creation unit 503, the creation status notification unit 504 sends a MemoPhaseInfo message indicating that the document is being created to the participant terminal 10 via the communication unit 508 and the network 2. Send. Specifically, the creation status notification unit 504 sets Phase to “processing” (under creation) and transmits a MemoPhaseInfo message.

<< Step S1910 >>
When the screen control unit 402 receives the MemoPhaseInfo message whose Phase is “processing” (processing) from the conference server 20 via the communication unit 408, the screen control unit 402 is in a state where a document with a memo is being created as shown in FIG. 24. The display unit 411 displays a state transition screen for displaying the fact and the "waiting number of people". Here, the "waiting number" is 0 because the material with memo to be acquired is already being created.

<< Step S1911, Step S1912 >>
When the creation of the material with memo is completed by merging the memo data specified by the request which is the request for creating the material with memo and the conference material, the creation unit 503 stores the memo data in the material storage unit 509b and saves the stored data. The path indicating the above is stored in association with the memo ID registered in the memo-attached material management table 509c, and the memo-attached material management table 509c is updated. After that, the creation unit 503 moves on to the processing of the next request in the queue.

<< Step S1913 >>
Since the creation status notification unit 504 is ready for download when the creation of the document with memo is completed by the creation unit 503, the MemoPhaseInfo message indicating that the download is in progress is sent via the communication unit 508 and the network 2. It is transmitted to the participant terminal 10. Specifically, the creation status notification unit 504 sets Phase to "downloading" (downloading) and transmits a MemoPhaseInfo message.

<< Step S1914 >>
When the screen control unit 402 receives the MemoPhaseInfo message of "downloading" (downloading) from the conference server 20 via the communication unit 408, the document with memo is being downloaded as shown in FIG. 25. A state transition screen for displaying the fact and the "waiting number of people" is displayed on the display unit 411. Here, the "waiting number" is 0 because the material with the memo to be acquired is already being downloaded.

<< Step S1915 >>
In order to switch from the first acquisition form to the second acquisition form after the participant is requested to create the material with memo based on the target request and before the material with memo is downloaded, on the state transition screen, If the "Get Later" button is pressed, the process proceeds to step S1920. At this time, the creation request unit 404 sets a value indicating that the "acquire later" button has been pressed (that is, indicating that the second acquisition form has been selected) in the above-mentioned acquisition variable. If the "Get Later" button is pressed during the download (acquisition) of the material with memo, the material acquisition unit 405 of the participant terminal 10 stops the download and a part of the material with memo downloaded halfway. May be kept as it is, or may be discarded. In this way, when the first acquisition form is switched to the second acquisition form, the material acquisition unit 405 stops the download, that is, the material transmission unit 507 stops the transmission process, thereby reducing the traffic in the network 2. , The load on the conference server 20 can be reduced. Further, after the download of the document with memo is started, the button may be disabled so that the "Get Later" button cannot be pressed.

<< Step S1916 >>
When the material sending unit 507 of the conference server 20 completes the creation of the material with memo by the creating unit 503, the material with memo is sent (transmitted) to the participant terminal 10 via the communication unit 508 and the network 2.

<< Step S1917 >>
When the download (sending) of the material with a memo is completed by the material sending unit 507, the creation status notification unit 504 sends a MemoPhaseInfo message indicating that the download is completed via the communication unit 508 and the network 2. It is transmitted to the participant terminal 10. Specifically, the creation status notification unit 504 sets Phase to "complete" (download completion) and transmits a MemoPhaseInfo message. Further, the creation status notification unit 504 stops the transmission (notification of the progress status) of the MemoPhaseInfo message after the Phase has transmitted the "complete" (download completed) MemoPhaseInfo message.

<< Step S1918 >>
When the screen control unit 402 receives the MemoPhaseInfo message from the conference server 20 via the communication unit 408 and the Phase is “complete” (download completed), the document with memo is in the state of being downloaded as shown in FIG. 26. A state transition screen for displaying the fact and the "waiting number of people" is displayed on the display unit 411. Here, the "waiting number" is 0 because the material with the memo to be acquired has already been downloaded.

<< Step S1919 >>
When the participant presses the "close" button on the state transition screen indicating the download completion state, the screen control unit 402 causes the display unit 411 to display the material selection screen as shown in FIG. 22 again.

<< Step S1920 >>
When the second acquisition form (“acquire later”) is selected as the acquisition form of the material with memo by the participant, the password setting unit 406 of the participant terminal 10 creates the material with memo on the conference server 20. In order to stop the notification of the processing status (progress), the StopMemoPhaseInfo message including the memo ID that identifies the memo data is transmitted to the conference server 20 via the communication unit 408 and the network 2.

<< Step S1921 >>
When the StopMemoPhaseInfo message is transmitted by the password setting unit 406, the screen control unit 402 causes the display unit 411 to display the password setting screen as shown in FIG. 27.

<< Step S1922 >>
Participants enter the password required for authentication when requesting the acquisition of materials with memos on the password setting screen displayed on the display unit 411, and press the "send" button.

<< Step S1923 >>
When the creation status notification unit 504 receives the StopMemoPhaseInfo message including the memo ID that identifies the memo data from the participant terminal 10 via the communication unit 508, the creation status notification unit 504 is identified by the memo ID among the requests stored in the queue. Change the request Notification = "false". As a result, the creation status notification unit 504 shall not notify the participant terminal 10 of the progress status of the creation of the document with memo.

<< Step S1924 >>
The password setting unit 406 identifies the password used for authentication on the conference server 20 when acquiring the memo-attached material, and the memo data to be created for the memo-attached material, which is input on the password setting screen (see FIG. 27). A Memo Password message including a memo ID is transmitted to the conference server 20 via the communication unit 408 and the network 2.

<< Step S1925 >>
When the authentication unit 506 of the conference server 20 receives the MemoPassword message from the participant terminal 10 via the communication unit 508, the password included in the message is set to the memo ID included in the message in the document management table 509c with memo. It is stored in association with the matching memo ID, and the document management table 509c with memo is updated.

<< Step S1926 >>
The URL notification unit 505 of the conference server 20 participates in the participant terminal 10 that has requested the creation of the memo-attached material with a URL indicating an access destination for downloading the memo-attached material created by the creation unit 503. Notify the person terminal 10. Here, if the memo ID is received from the participant terminal 10, the URL notification unit 505 can predefine the access destination for downloading the material with the memo as the URL including the memo ID. Notify the URL even before the creation of the document with memo is completed.

<< Step S1927 >>
When the screen control unit 402 receives the URL indicating the access destination for downloading the material with memo from the conference server 20 via the communication unit 408, the screen control unit 402 displays the acquisition URL screen as shown in FIG. 28. It is displayed on the display unit 411. Participants make a note of the URL notified on the acquisition URL screen.

<< Steps S1928, S1929 >>
Participants access the URL reserved in step S1927 by a Web browser or the like at an arbitrary timing.

<< Step S1930 >>
When the authentication unit 506 receives an access from the participant terminal 10 to the URL notified by the URL notification unit 505, the authentication unit 506 authenticates whether or not to permit the transmission of the document with memo requested by the participant terminal 10. The authentication request is transmitted to the participant terminal 10 via the communication unit 508 and the network 2.

<< Step S1931 >>
When the screen control unit 402 receives the authentication request from the conference server 20 via the communication unit 408, the screen control unit 402 causes the display unit 411 to display the password input screen as shown in FIG. 29.

<< Step S1932 >>
In step S1922, the participant inputs the password entered and set on the password setting screen on the password input screen, and presses the "send" button. The authentication request unit 407 of the participant terminal 10 receives the password entered on the password input screen and the memo merged with the memo-attached material for which the acquisition is requested in order to be authenticated by the conference server 20 for the acquisition of the memo-attached material. A document request with a memo including a Memo ID (memo ID) for identifying data is transmitted to the conference server 20 via the communication unit 408 and the network 2.

<< Step S1933 >>
When the authentication unit 506 receives the memo-attached material request from the participant terminal 10 via the communication unit 508, the authentication unit 506 authenticates whether or not to allow the transmission of the memo-attached material by the password included in the request. Specifically, the authentication unit 506 refers to the document management table 509c with memo, and whether the password of the record matching the memo ID included in the document request with memo matches the password included in the document request with memo. Authentication is performed depending on whether or not.

In addition, it is assumed that only the password is included in the document request with memo by the authentication request unit 407, and when the authentication unit 506 receives the document request with memo including the password, the record that matches the memo ID included in the URL of the access destination. Authentication may be performed based on whether or not the password of the above matches the password included in the document request with memo.

<< Step S1934 >>
When the authentication unit 506 permits the authentication, the material sending unit 507 extracts the memo-attached material specified by the memo-attached material request from the material storage unit 509b.

<< Step S1935 >>
The material sending unit 507 sends (sends) the extracted material with a memo to the participant terminal 10 via the communication unit 508 and the network 2. Then, the material acquisition unit 405 acquires (receives) the requested material with a memo from the conference server 20 via the communication unit 508.

As described above, in the conference system 1 according to the present embodiment, in the paperless conference, after the end (or exit) of the conference, the memo written on the participant terminal 10 is merged with the conference material to create a document with a memo. Can be selected immediately (first acquisition form) or later (second acquisition form). As a result, it is possible to select the acquisition timing of the material with memo at the convenience of the participant, so that the convenience when acquiring the material with memo is improved.

Further, even if the participant once selects to acquire immediately (first acquisition form), for example, in the state transition screen displayed when the above-mentioned first acquisition form is selected, "acquire later". By pressing the "button", it is possible to switch to the second acquisition form in which the material with memo is acquired later. As a result, it is possible to further improve the convenience for the participants of the conference to obtain the material with the memo.

As a method of switching to the second acquisition mode after the first acquisition mode is selected, in FIG. 18, by pressing the "acquire later" button arranged on the state transition screen displayed by the screen control unit 402. It is supposed to be switched, but it is not limited to this. For example, a screen other than the state transition screen may be used to switch to the second acquisition form in the operation screen for switching to the second acquisition form, or the input unit 409 is not operated on the screen. It may be switched to the second acquisition form by a predetermined command operation for.

Further, the number of requests included in the reply of the NumberOfWaiting message on the acquisition method selection screen shown in FIG. 21 and the number of requests included in the MemoPhaseInfo message on the state transition screens shown in FIGS. 23 to 26 are displayed as "waiting number". However, it is not limited to this. For example, the screen control unit 402 may display a “waiting time” (an example of a waiting period) predicted based on the number of requests on each screen, and may be displayed by the above-mentioned reply of the NumberOfWaiting message and the MemoPhaseInfo message. The waiting time itself may be received and displayed instead of the number of requests.

Further, in the sequence diagrams of FIGS. 17 and 18, the memo written by the participants is assumed to be an individual memo, and the memo to be merged into the conference material is assumed to be an individual memo, but the present invention is limited to this. Shared memos may be merged instead of things. For example, on the material selection screen shown in FIG. 22, in addition to selecting the conference material for creating the material with memo, select both the personal memo, the shared memo, or both the personal memo and the shared memo as the memo to be merged with the conference material. It may be possible.

Further, "acquire later" means that, as described above, the creation request unit 404 only requests the conference server 20 to create the document with memo, and then, after the document with memo is created, it is arbitrary. The form is such that the conference server 20 is accessed at the timing and the material with the memo is downloaded and acquired (second acquisition form). For example, after the request, the download starts when the preset date and time arrives. The acquisition form may be such that the date and time can be set.

Further, in the above-described embodiment, when at least one of the functional units of the conference server 20 and the participant terminal 10 is realized by executing a program, the program is provided by being incorporated in a ROM or the like in advance. Further, the program executed on the conference server 20 and the participant terminal 10 according to the above-described embodiment is a CD-ROM (Computer Disc Read Only Memory) or a flexible disk (FD) in an installable format or an executable format file. ), CD-R (Compact Disc-Recordable), or DVD (Digital Versaille Disc), which may be stored and provided in a computer-readable storage medium. Further, the program executed by the conference server 20 and the participant terminal 10 of the above-described embodiment is configured to be stored on a computer connected to a network such as the Internet and provided by downloading via the network. May be good. Further, the program executed by the conference server 20 and the participant terminal 10 of the above-described embodiment may be configured to be provided or distributed via a network such as the Internet. Further, the program executed by the conference server 20 and the participant terminal 10 of the above-described embodiment has a module configuration including at least one of the above-mentioned functional units, and the actual hardware is CPU 301, 201. Reads a program from the above-mentioned storage device (for example, auxiliary storage device 304, storage device 203) and executes the program, so that each of the above-mentioned functional units is loaded and generated on the main storage device (for example, RAM 303, memory 202). It is supposed to be done.

1 Conference system 2 Network 10, 10a-10e Participant terminal 20 Conference server 201 CPU
202 Memory 203 Storage device 204 Touch panel display 206 Microphone 207 Speaker 208 Operation unit 209 Wireless communication unit 215 Bus 251 Pen 301 CPU
302 ROM
303 RAM
304 Auxiliary storage 305 Media 306 Media drive 307 Operating device 308 Network I / F
309 Display 310 DVD
311 DVD drive 312 Bus 401 Conference processing unit 402 Screen control unit 403 Memo data management unit 404 Creation request unit 405 Document acquisition unit 406 Password setting unit 407 Authentication request unit 408 Communication unit 409 Input unit 410 Display control unit 411 Display unit 412 Storage unit 412a Conference information storage unit 412b Memo data storage unit 501 Conference control unit 502 Material data management unit 503 Creation unit 504 Creation status notification unit 505 URL notification unit 506 Authentication unit 507 Material transmission unit 508 Communication unit 509 Storage unit 509a Conference information storage unit 509b Data storage unit 509c Data management table with memo 601 Queue 602 Request 603 Stroke information

Japanese Patent No. 6108679

Claims (10)

An acquisition unit that acquires the memo data added in the conference terminal and stores in the queue a creation request requesting the creation of data with a memo based on the conference usage data and the memo data .
After the memo data is acquired by the acquisition unit, the creation unit that creates the data with memo based on the conference use data and the memo data, and the creation unit.
The first acquisition form in which the memo-attached data is downloaded by the conference terminal when the creation of the memo-attached data is completed after receiving the creation request of the memo-attached data from the conference terminal, and the conference terminal. Based on the form selected by the conference terminal among the second acquisition forms in which the creation request is made from the above and the data with memo is downloaded by the conference terminal at an arbitrary timing after the data with memo is created. A sending unit that sends the data with memos to the conference terminal,
A screen for operating whether or not to switch to the second acquisition form in the conference terminal after the first acquisition form is selected and at least until the data with memo is created by the creation unit. As shown in the second notification unit, which notifies the waiting period until the processing for the creation request corresponding to the memo-attached data is performed based on the number of the creation requests stored in the queue. ,
Equipped with
When the sending unit is switched to the second acquisition form in the conference terminal after the first acquisition form is selected and at least until the data with memo is created by the creating unit, the sending unit is said to be the same. A conference device that sends the data with memos to the conference terminal based on the second acquisition form. The conference according to claim 1, further comprising a first notification unit for notifying the conference terminal of the state of creation of the memo-attached data by the creation unit when the first acquisition form is selected by the conference terminal. Device. The creating unit is displayed on the conference terminal as the memo data by reflecting the data of the personal memo for the participants who use the conference terminal to use as individuals and all the conference terminals. The conference device according to claim 1 or 2 , wherein the data with a memo is created based on at least one of the memo data selected from the added shared memo data and the conference use data. When the second acquisition form is selected by the conference terminal, a third notification unit for notifying the conference terminal of the access destination for downloading the memo-attached data created by the creation unit is further provided. The conference device according to any one of claims 1 to 3 . The conference device according to claim 4 , further comprising an authentication unit that makes an authentication request to the conference terminal when the access destination notified by the third notification unit is accessed from the conference terminal. After the first acquisition form is selected, the sending unit creates the memo-attached data by the creating unit, and while the memo-attached data is being sent to the conference terminal, the second acquisition form is performed at the conference terminal. The conference device according to any one of claims 1 to 5 , which stops sending the data with a memo when switched to. An acquisition unit that acquires the memo data added in the conference terminal and stores in the queue a creation request requesting the creation of data with a memo based on the conference usage data and the memo data .
After the memo data is acquired by the acquisition unit, the creation unit that creates the data with memo based on the conference use data and the memo data, and the creation unit.
The first acquisition form in which the memo-attached data is downloaded by the conference terminal when the creation of the memo-attached data is completed after receiving the creation request of the memo-attached data from the conference terminal, and the conference terminal. Based on the form selected by the conference terminal among the second acquisition forms in which the creation request is made from the above and the data with memo is downloaded by the conference terminal at an arbitrary timing after the data with memo is created. A sending unit that sends the data with memos to the conference terminal,
A screen for operating whether or not to switch to the second acquisition form in the conference terminal after the first acquisition form is selected and at least until the data with memo is created by the creation unit. As shown in, a creation status notification unit that notifies a waiting period until processing for the creation request corresponding to the memo-attached data is performed based on the number of creation requests stored in the queue. ,
Have,
When the sending unit is switched to the second acquisition form in the conference terminal after the first acquisition form is selected and at least until the data with memo is created by the creating unit, the sending unit is said to be the same. A conference system that sends the data with memos to the conference terminal based on the second acquisition form. Including the conference terminal
The conference system according to claim 7 , wherein the conference terminal includes a receiving unit for receiving the data with memos. An acquisition step in which the acquisition unit acquires the memo data added in the conference terminal and stores in the queue a creation request requesting the creation of data with a memo based on the conference usage data and the memo data .
After the memo data is acquired by the acquisition unit, the creation unit creates the memo data based on the conference use data and the memo data, and a creation step.
The first acquisition mode in which the data with memos is downloaded by the conference terminal when the transmission unit receives the request for creating the data with memos from the conference terminal and the creation of the data with memos is completed. , The creation request is made from the conference terminal, and the data with memo is downloaded by the conference terminal at an arbitrary timing after the data with memo is created. The data with memo is downloaded by the conference terminal. A sending step of sending the data with memos to the conference terminal based on the form, and
Whether or not the creation status notification unit switches to the second acquisition mode after the first acquisition mode is selected in the conference terminal and at least before the creation unit creates the memo-attached data. Based on the number of the creation requests stored in the queue, the waiting period until the processing for the creation request corresponding to the memo-attached data is performed is notified so as to be displayed on the screen for operating. Notification step and
When the sending unit is switched to the second acquisition form at the conference terminal after the first acquisition form is selected and at least until the data with memo is created by the creating unit , the said. A step of sending the data with a memo to the conference terminal based on the second acquisition form, and
Information processing method with. On the computer
An acquisition step of acquiring the memo data added in the conference terminal and storing in a queue a creation request requesting the creation of data with a memo based on the conference usage data and the memo data .
After acquiring the memo data, a creation step of creating the data with a memo based on the conference use data and the memo data, and
The first acquisition form in which the memo-attached data is downloaded by the conference terminal when the creation of the memo-attached data is completed after receiving the creation request of the memo-attached data from the conference terminal, and the conference terminal. Based on the form selected by the conference terminal among the second acquisition forms in which the creation request is made from the above and the data with memo is downloaded by the conference terminal at an arbitrary timing after the data with memo is created. The sending step of sending the data with memos to the conference terminal, and
In the conference terminal, after the first acquisition form is selected, at least until the data with memo is created, it is displayed on the screen for operating whether or not to switch to the second acquisition form. In addition, a notification step for notifying the waiting period until the processing for the creation request corresponding to the memo-attached data is performed based on the number of the creation requests stored in the queue.
When the conference terminal is switched to the second acquisition form after the first acquisition form is selected and at least until the data with the memo is created, the memo is attached based on the second acquisition form. The step of sending data to the conference terminal and
A program to execute.

Images