JP7059756B2 - 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.

An electronic document that digitizes materials used in meetings or seminars can be displayed on a tablet or PC (Personal Computer) at the participant's hand, display pages can be synchronized between devices, and each participant can freely hand-write. A paperless meeting system is known for conducting effective meetings while writing notes at. As such a paperless conference system, in the conventional system, it is assumed that the server is temporarily overloaded in order to ensure that each device (participant terminal) operates in synchronization as described above. Regarding the processing, the client may act on behalf of the server without processing it, or the processing may be restricted and executed. However, due to the effects of such measures, it is possible to provide the complete functions that the user (participant) originally wants, and to enable the operation in cooperation with other systems by aggregating the data on the server. There is a problem that it is difficult to realize such things.

As a process that is expected to temporarily overload the server as described above, for example, a process in which each individual saves a memo on the server after the end of the paperless meeting can be mentioned. In such a process, it is easily assumed that many participants participating in the conference receive a trigger of the end of the conference and request the server to save their memos almost at the same time. When the memo storage process is processed by the server at once, it is possible that the larger the number of clients (participant terminals), the greater the load on the server and the lower the throughput and processing capacity of the entire system. .. As a measure to avoid such overload on the server, even if the convenience or quality deteriorates, it is processed by the client, and if the quality cannot be ensured, the memo saving function is provided depending on the model of the client used. You can prevent it from being used, or set a small number of clients that can be handled at the same time, but in the end, the above problems will remain.

The above-mentioned paperless conference system constitutes a so-called client-server system, but as a technology of this client-server system, the load status of the server is monitored, and if it is determined that the load is high, it is processed by another server. A technique for preventing overload of a server and improving the processing capacity of a system by migrating is disclosed (see Patent Document 1).

However, in the system described in Patent Document 1, it is necessary to prepare another server, and therefore, in terms of preparing this other server, the hardware specifications of the original system are changed, and the cost is increased. Has risen, and there is a problem that it does not meet the needs of system users.

The present invention has been made in view of the above, and is a conference device, a conference system, an information processing method, and a program capable of suppressing an overload of a conference server without changing the hardware specifications of the conference server. The purpose is to provide.

In order to solve the above-mentioned problems and achieve the object, the present invention is received by a reception unit that accepts memo data added in a conference terminal and a request for creating data with a memo for the memo data, and at least the reception unit. About the process of creating the memo-attached data based on the conference use data and the memo data based on the number of the creation requests made and the predetermined upper limit of the number of creation requests simultaneously received by the reception unit. By the setting unit that sets the maximum number of simultaneous processes less than the set maximum number of simultaneous processes and the thread that is less than or equal to the maximum number of simultaneous processes set by the setting unit, the conference use data and the memo data can be obtained. It is characterized by having a creation unit for creating the data with memos based on the above.

According to the present invention, it is possible to suppress the overload of the conference server without changing the hardware specifications of the conference server.

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 illustrating a basic flow of a process of synchronizing the operations of each participant terminal in the conference system according to the embodiment. FIG. 3 is a diagram showing an example of the appearance of the participant terminal according to the embodiment. FIG. 4 is a diagram showing an example of the hardware configuration of the participant terminal according to the embodiment. FIG. 5 is a diagram showing an example of the hardware configuration of the conference server according to the embodiment. FIG. 6 is a diagram showing an example of the configuration of the functional block of the participant terminal according to the embodiment. FIG. 7 is a diagram showing an example of a material display screen during a meeting. FIG. 8 is a diagram showing an example of the configuration of the functional block of the conference server according to the embodiment. FIG. 9 is a diagram illustrating a queue of requests requesting the creation of materials with memos. FIG. 10 is a diagram illustrating a flow when a conference server is made to process a personal memo. FIG. 11 is a diagram illustrating an outline of a processing flow for preventing a load from being applied to the conference server according to the embodiment. FIG. 12 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. 13 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. 14 is a diagram showing an example in which a memo is written on the material display screen. FIG. 15 is a diagram showing an example of a memo save / exit screen. FIG. 16 is a diagram showing an example of an acquisition method selection screen. FIG. 17 is a diagram showing an example of a material selection screen. FIG. 18 is a diagram showing an example of a state transition screen (waiting for creation start). FIG. 19 is a diagram showing an example of a state transition screen (under construction). FIG. 20 is a diagram showing an example of a state transition screen (during downloading). FIG. 21 is a diagram showing an example of a state transition screen (download completed). FIG. 22 is a diagram showing an example of the acquisition URL screen. FIG. 23 is a diagram showing an example of a data list 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 23. 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 and basic operation 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. 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 are connected to the network 2 so as to be communicable. If so, a paperless meeting will be realized.

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 (meeting use data) used in the conference can be registered in association with the conference. At this time, the conference server 20 issues a material ID 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 (requests, responses, etc.) necessary for the above, and memo data described later. 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 example shown in FIG. 1, the participant terminals 10a and 10b are illustrated as tablets, the participant terminals 10c and 10d are notebook PCs, and the participant terminals 10e are shown as electronic blackboards. The configuration of such a participant terminal is an example, and is not limited to this.

In addition, when referring to arbitrary participant terminals or generically referring to two or more participant terminals, it is simply referred to as "participant terminal 10". In the following, the participant terminal 10 will be described as being a tablet.

Further, 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.

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 used in the conference from the conference server 20 via the network 2. In this case, the participant terminal 10 also acquires a material ID 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.

FIG. 2 is a diagram illustrating a basic flow of a process of synchronizing the operations of each participant terminal in the conference system according to the embodiment. With reference to FIG. 2, the basic flow of the process of synchronizing the operations of the participant terminals 10 in the conference system 1 according to the present embodiment will be described.

FIG. 2 shows a state in which the participant terminals 10a to 10e participate in the conference A and the participant terminals 10f participate in the conference B. When each participant terminal 10 participates in the conference, each participant terminal 10 downloads the conference material registered in the conference server 20 and displays the conference material.

Here, for example, it is assumed that the participant terminal 10c has the authority to present the conference, and the participant using the participant terminal 10c performs an operation of turning the page of the conference material. Information on the operation content in this case (target material ID, page number information after being turned over, etc.) is transmitted to the conference server 20 via the network 2 ((1) shown in FIG. 2). The conference server 20 transmits the received operation content information to the other participant terminals 10 (participant terminals 10a, 10b, 10d, 10e) participating in the conference A via the network 2 (FIG. 2). Shown (2)). At this time, since the participant terminal 10f participates in the conference B different from the conference A, the above-mentioned operation content information is not transmitted. Then, on the participant terminals 10a, 10b, 10d, and 10e, the page after being turned is displayed based on the received operation content information ((3) shown in FIG. 2), and the operation on the participant terminal 10c is performed. Is synchronized.

Further, in addition to the operation of turning the page described above, for example, when an operation of writing a memo (shared memo described later) is performed on the participant terminal 10 having the presenter authority, the conference server 20 is used in the same manner as described above. The operation content is reflected (displayed in a memo) on the other participant terminals 10 via the system. The information of the operation content in this case is, for example, the target material ID, the color number of the pen, the thickness number of the pen, the coordinate information constituting the memo, and the like.

In providing a system in which the participant terminals 10 operate in synchronization with each other as described above, in order to reduce the load on the conference server 20 and the traffic on the network 2 as the number of the participant terminals 10 participating at the same time increases. For example, the following measures are taken. In the synchronization of page turning, only the page number of the displayed conference material is sent from the conference server 20 to each participant terminal 10, and in the synchronization of memo writing, the content of the stroke information of the memo data is numerically displayed. By exchanging only the short character strings shown, the amount of data transmitted by the conference server 20 to the participant terminal 10 can be reduced. However, for these page turning and synchronization of memo writing, the conference server 20 receives the content operated by the participant having the presenter authority, and the content is simply transmitted to the participant terminal 10 participating in the conference. Therefore, even if there are many participating participant terminals 10, the load on the conference server 20 is not so high. In the paperless conference system (conference system 1), the processing that is expected to put a heavy load on the conference server 20 is the request when many participant terminals 10 request the conference server 20 for processing all at once. This is a process executed by the conference server 20 after the reception of. Such processing will be described in detail with reference to FIGS. 10 and 11.

(Hardware configuration of participant terminals)
FIG. 3 is a diagram showing an example of the appearance of the participant terminal according to the embodiment. FIG. 4 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. 3 and 4.

As shown in FIG. 4, 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. 3) touching the touch panel to the CPU 201. It is a display device. As shown in FIG. 3, 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, for example, a pen 251. That is, the drawing data (memo data) written on the touch panel display 204 can be shared with the other participant terminals 10. 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. 3, 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. 3, the operation unit 208 is not limited to being composed of buttons 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 for connecting a ROM (Read Only Memory), which is a non-volatile storage device that stores firmware or the like for controlling the participant terminal 10, or a PC or an external storage device. It may be provided with an I / F or the like for an external device of the above.

Further, in FIG. 3, 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. 5 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. 5, 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 (Network Interface Card) 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 (DVD Recordable), 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. 6 is a diagram showing an example of the configuration of the functional block of the participant terminal according to the embodiment. The configuration and operation of the functional block of the participant terminal 10 according to the present embodiment will be described with reference to FIG.

As shown in FIG. 6, 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 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 conducting an electronic conference. The conference processing unit 401 is realized, for example, by the CPU 201 shown in FIG. 4 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. 4 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. 4 executing a program.

The creation request unit 404 requests the creation of a memo-attached material (data with memo) obtained by merging the above-mentioned memo data and the conference material used in the conference, and the creation request (request) held in the queue of the conference server 20. This is a functional unit that requests the number of conference servers 20 and the like. Here, merging indicates a process of synthesizing memo data and meeting materials. The creation request unit 404 is realized, for example, by the CPU 201 shown in FIG. 4 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. 4 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. 4 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. 4 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. 6, 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.

Note that some or all of the conference processing unit 401, screen control unit 402, memo data management unit 403, creation request unit 404, material acquisition unit 405, communication unit 408, and display control unit 410 are not programs that are software. It may be realized by a hardware circuit such as FPGA (Field-Programmable Gate Array) or ASIC (Application Specific Integrated Circuit).

Further, each functional unit shown in FIG. 6 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. 6 may be configured as one functional unit. On the other hand, the function of one functional unit in FIG. 6 may be divided into a plurality of functions and configured as a plurality of functional units.

(Overview of operation on participant terminals)
FIG. 7 is a diagram showing an example of a material display screen during a meeting. With reference to FIG. 7, 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. 7 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 document 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, and the memo (shared memo) of the participant who has the presenter authority can be written. The same memo is displayed in synchronization.

The material display screen shown in FIG. 7 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. 7, the "Individual" button is pressed) and press the "Memo entry" button. , A personal memo 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. 15) 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. 8 is a diagram showing an example of the configuration of the functional block of the conference server according to the embodiment. FIG. 9 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. 8 and 9.

As shown in FIG. 8, the conference server 20 according to the present embodiment includes a conference control unit 501, a creation request reception unit 502 (an example of a reception unit and a third notification unit), a registration unit 510, and a processing number setting unit. 511 (setting unit), creation unit 503, status notification unit 504 (example of first notification unit and third notification unit), URL notification unit 505 (second notification unit), and document 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. 5 executing a program.

The creation request reception unit 502 is a functional unit that receives (receives) a creation request for a document with a memo from the participant terminal 10 via the communication unit 508. In this case, the creation request receiving unit 502 sets the number of creation requests simultaneously received in the creation request acceptance process up to a predetermined upper limit (for example, 100), and the subsequent processing (for example, request registration processing, And do not consume up to the memory area required for document creation processing with memos, etc.). Here, "all at once" does not necessarily mean "at the same time", but also includes, for example, the concept of "within a predetermined short period of time". When the creation request receiving unit 502 receives a creation request (request) exceeding the upper limit value, the participant terminal gives an instruction to "request again after a specific number of seconds" as a response (response) to the request exceeding the upper limit value. Send to 10. This is a standard specification of HTTP (Hypertext Transfer Protocol), and this "specific number of seconds" is calculated according to the number of requests received.

Further, the creation request reception unit 502 generates a memo ID that uniquely identifies the memo data included in the reception request for creating the material with memo.

The creation request receiving unit 502 is realized, for example, by the CPU 301 shown in FIG. 5 executing a program.

The registration unit 510 uses the memo data included in the creation request received by the creation request reception unit 502, the generated memo ID, and the like as a request, and merges them with the conference material to create a material with a memo (queue). ) Is a functional unit that is stored (registered). Specifically, as shown in FIG. 9, the registration unit 510 stores (registers) the request including the memo data and the memo ID in the queue 601 configured in the request registration DB (Database) 509c described later. do. The queue 601 shown in FIG. 9 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 has a configuration as shown in FIG. 9, for example, the request 602, and includes a memo ID (MemoID), a UserID, and one or a plurality of stroke information. The one or more stroke information is the substance of the memo data described above, and the stroke information includes, for example, a material ID, a page number, and coordinate information of the memo. 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 substance of the memo has been described as XY coordinate information (coordinate information of the memo) on the screen, which is a collection of points constituting the memo, but the present invention is not limited to this, and graphic data, stamp data, etc. May be included.

The registration unit 510 is realized, for example, by the CPU 301 shown in FIG. 5 executing a program.

The processing number setting unit 511 is a functional unit that sets the maximum number of simultaneous processing (number of threads) of the processing for creating the document with memo corresponding to each memo data by the creating unit 503. As described above, the simultaneous processing (multithreading) in the processing for creating the document with memo is realized by the function of the CPU 301 shown in FIG. Specifically, the processing number setting unit 511 has at least one of a creation request acceptance process (for example, the number of accepted creation requests) by the creation request reception unit 502 and a request registration process by the registration unit 510. Set the maximum number of simultaneous processes (number of threads) based on the load status. For example, when the maximum number of simultaneous processes (number of threads) is set to "5" by the process number setting unit 511, the creation unit 503 normally creates a document with a memo about five requests by the maximum five threads. Perform processing at the same time to achieve the highest possible processing speed. However, when the number of created requests received by the created request receiving unit 502 reaches near the upper limit, the processing number setting unit 511 sets the number of simultaneous processes by the creating unit 503 to be small, thereby loading the entire conference server 20. To balance.

The processing number setting unit 511 is realized, for example, by the CPU 301 shown in FIG. 5 executing a program.

The creation unit 503 is a functional unit that creates a material with a memo by merging the memo data included in the request stored in the queue by the registration unit 510 and the conference material used in the conference. In this case, the creation unit 503 creates the document with memo with the maximum number of simultaneous processes (number of threads) set by the process number setting unit 511. As described above, the creation unit 503 normally performs processing with the maximum number of simultaneous processes (number of threads) set by the process number setting unit 511, but is not limited to this, and the set maximum number is set. Processing may be performed by threads that are less than or equal to the number of simultaneous processes (number of threads). The creation unit 503 stores the created material with a memo in the material storage unit 509b, which will be described later. The creation unit 503 is realized, for example, by the CPU 301 shown in FIG. 5 executing a program.

The status notification unit 504 is a functional unit that notifies the participant terminal 10 that has requested the creation of the memo-attached material of the progress of the creation of the memo-attached material by the creation unit 503. In this case, the status notification unit 504 notifies the progress status of the creation of the document with memo by push notification. The states notified by the status notification unit 504 include, for example, "waiting" (waiting for creation start), "processing" (creating), "downloading" (downloading), and "complete" (downloading completed). The status notification unit 504 is realized, for example, by the CPU 301 shown in FIG. 5 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. 5 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. 5 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. 5 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. 8, the storage unit 509 includes a conference information storage unit 509a, a material storage unit 509b, and a request registration DB 509c.

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 request registration DB 509c is configured with a queue (queue) for storing (registering) the memo data included in the creation request received by the creation request reception unit 502, the generated memo ID, and the like as a request.

A part of the conference control unit 501, the creation request reception unit 502, the registration unit 510, the processing number setting unit 511, the creation unit 503, the status notification unit 504, the URL notification unit 505, the material transmission unit 507, and the communication unit 508. Alternatively, all may be realized by a hardware circuit such as FPGA or ASIC instead of a program which is software.

Further, each functional unit shown in FIG. 8 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. 8 may be configured as one functional unit. On the other hand, the function of one functional unit in FIG. 8 may be divided into a plurality of functions and configured as a plurality of functional units.

(Overview of conference system processing)
FIG. 10 is a diagram illustrating a flow when a conference server is made to process a personal memo. In the case where many participant terminals 10 described above request processing to the conference server 20 all at once in FIG. 2, the processing executed by the conference server 20 after receiving the request is, for example, the conference start time. Participation processing when participants participate in meetings one after another at about the same time, and registration processing in which participants register their opinions one after another as meeting materials in discussions, etc. are assumed. Among them, the process that is assumed to have the highest load on the conference server 20 is the process of creating a document with a memo on the conference server 20 at the end of the conference. This is because the timing of the end of the conference becomes a common trigger for all the participants participating in the conference, and each participant performs the termination processing for the conference materials starting from the trigger, so that the conference ends. This is because there is a high possibility that the process of causing the conference server 20 to create a document with a memo is a simultaneous operation by the participants of the completed conference.

As described in FIG. 10, the details of the reason why the process of creating the document with memo on the conference server 20 at the end of the conference causes the overload on the conference server 20 is as shown in FIG. 10, in which the memo data is input from the participant terminal 10. Not only the reception process for accepting the creation request including, but also the registration process for registering the creation request as a request in the database (request registration DB 509c), and the creation process for creating the document with memo by merging the memo data and the meeting material. To do. In this case, in order to improve the processing speed in places where processing takes time, if simple simultaneous processing (multithreading) is performed, when processing is requested all at once, the number of simultaneous processing is the specification for all processing. Since it starts up to the maximum, the memory consumption becomes excessive, and the conference server 20 becomes overloaded. On the other hand, if the number of simultaneous processes is reduced, the processes will be slow even when a large number of participant terminals 10 are not participating in the conference, and the usability of the system will be reduced. Furthermore, if the hardware specifications of the conference server 20 itself are increased and the number of servers that process at the same time is increased, the processing capacity can be increased, but in that case, the cost for the system user increases, and the needs of the user are met. Will not match.

Further, in order to avoid the overload on the conference server 20 as described above, it is conceivable that the process of creating the document with memo is performed on the participant terminal 10 side. However, in order to create a document with a memo on the participant terminal 10, a Web application (especially an application executed on an older version of the browser) can be supported by a native application that can easily operate the document. In the case of, there is a problem that the document operation cannot be processed by the Web application alone. Further, when the participant terminal 10 performs the process of creating the material with memo, there is a problem that the quality of the material with memo to be created varies depending on the type of the application to be used and is not constant. Further, since it is saved in the participant terminal 10, for example, when a tablet or a notebook PC shared by the department is used as the participant terminal 10, the participant terminal 10 further transfers to its own information processing device. There is also the problem that it is necessary to save the material with memos or send it by e-mail, which increases the time and effort of operation. Furthermore, if you want to save your own memo data as materials with memos, cooperation from the paperless conference system to the document management server or file server is required, but the materials are also stored in the participant terminal 10 for cooperation between the systems. If it is saved, seamless cooperation becomes difficult, and if the creation process is performed on the participant terminal 10 side, a problem remains from the viewpoint of expandability.

FIG. 11 is a diagram illustrating an outline of a processing flow for preventing a load from being applied to the conference server according to the embodiment. With reference to FIG. 11, the outline of the process flow for avoiding overload in the conference server 20 according to the present embodiment will be described. In the present embodiment, the load of the conference server 20 is taken into consideration by the following processing, the processing load of the conference server 20 is balanced by software, and the memo data and the conference material written in each participant terminal 10 are used. By merging with, the conference server 20 can perform the creation process of creating a document with a memo.

First, in (1) shown in FIG. 11, a large number of participant terminals 10 simultaneously transmit a request for creating a document with a memo (including memo data) to the conference server 20 as a request. When a large number of requests are generated, the process from the process of accepting this request to the process of registering the request in the database (request registration DB 509c) is first performed in the memory area (specifically, the memory of the RAM 303 shown in FIG. 5). Area) is a part that consumes a large amount. Therefore, as shown in (2), the upper limit of the number of requests that can be simultaneously received in the request reception process in the conference server 20 is set. This upper limit does not consume the memory area required for the subsequent processing (for example, request registration processing, memo-attached material creation processing, etc.). Further, when the conference server 20 receives a request exceeding the upper limit, the conference server 20 transmits an instruction to "request again after a specific number of seconds" as a response (response) to the request exceeding the upper limit to the participant terminal 10. do.

Further, as shown in (4), the conference server 20 is a document with a memo based on at least one of the load states of the request acceptance process and the request registration process ((3) shown in FIG. 11). The maximum number of simultaneous processes (number of threads) for the creation process is set (controlled). For example, when the maximum number of simultaneous processes (number of threads) is set to "5", the conference server 20 can normally simultaneously perform the process of creating a document with a memo for five requests by the maximum of five threads. Achieve as high-speed processing as possible. However, when the number of requests received has reached the upper limit, the conference server 20 tries to balance the entire load by setting the maximum number of simultaneous processes to be small. As a result, without increasing the hardware specifications of the conference server 20, the maximum capacity can be exhibited according to the state of the number of requests at that time while maintaining the current processing capacity of the conference server 20. Overload can be suppressed.

After the process of creating the material with memo is completed, the participant terminal 10 acquires the material with memo. At this time, since there is a case where the participant terminal 10 wants to know the timing of the completion of creating the document with memo, a method of periodically checking by polling process from the participant terminal 10 or the like can be considered. Since the conference server 20 bears periodic communication processing for the number of participant terminals 10, this polling processing also becomes a constant load on the conference server 20 as the number of participant terminals 10 increases. Therefore, as shown in (5), a mechanism is provided to notify the completion of creation of the document with memo by push notification from the conference server 20 to the participant terminal 10. Then, after receiving the notification of the completion of creation of the material with memo, the participant terminal 10 downloads the material with memo from the conference server 20 ((6) shown in FIG. 11), so that the load on the conference server 20 is reached. Can be reduced.

As described above, the hardware specifications of the conference server 20 are raised by changing the number of simultaneous processes (number of threads) in the process of creating the document with memo, which is the subsequent process, according to the number of requests received. It is possible to process even when a large number of participant terminals 10 simultaneously receive a request for creating a document with a memo as a request on the conference server 20.

(Details of conference system processing)
FIG. 12 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. 13 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. 14 is a diagram showing an example in which a memo is written on the material display screen. FIG. 15 is a diagram showing an example of a memo save / exit screen. FIG. 16 is a diagram showing an example of an acquisition method selection screen. FIG. 17 is a diagram showing an example of a material selection screen. 18 to 21 are diagrams showing an example of a state transition screen. FIG. 22 is a diagram showing an example of the acquisition URL screen. FIG. 23 is a diagram showing an example of a data list screen. The details of the processing of the conference system 1 according to the present embodiment will be described with reference to FIGS. 12 to 23.

<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. 14, 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 determines the number of requests registered in the queue configured by the request registration DB 509c of the conference server 20. The request 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 creation request receiving unit 502 of the conference server 20 receives a request for the number of requests from the participant terminal 10 via the communication unit 508, the creation request receiving unit 502 acquires the number of requests registered in the queue at that time. Then, the creation request receiving unit 502 includes the number of acquired queue requests in the response to the number of requests, and transmits the response 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 response including the number of requests in the queue via the communication unit 408.

<Step S16>
When the above-mentioned response 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. As shown in the acquisition method selection screen of FIG. 16, the screen control unit 402 displays the number of requests included in the response received 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. 17. 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 material ID of the stroke information included in the memo data with the material ID of the conference material. Further, as shown in FIG. 17, 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 the "Next" button is pressed while any of the conference materials is selected on the material selection screen, 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 S1929 shown in FIG.

<< Step S1901 >>
The creation request unit 404 of the participant terminal 10 sends a request for creating a material with a memo, which is a merge of the conference material selected on the material selection screen and the memo data written in the conference material, to the communication unit 408 and the network 2. It is transmitted to the conference server 20 via. The creation request includes one or more stroke information constituting the memo data.

<< Step S1902 >>
The creation request receiving unit 502 of the conference server 20 receives (receives) a request for creating a document with a memo via the communication unit 508. In this case, the creation request receiving unit 502 limits the number of creation requests that are simultaneously accepted in the creation request acceptance process to a predetermined upper limit. Then, the creation request reception unit 502 generates a memo ID that uniquely identifies the memo data included in the reception request for creating the material with memo.

<< Step S1903 >>
The creation request reception unit 502 includes the generated memo ID in the response to the creation request and transmits it to the participant terminal 10 via the communication unit 508 and the network 2.

<< Step S1904 >>
The registration unit 510 of the conference server 20 receives the memo data included in the creation request received by the creation request reception unit 502, the generated memo ID, and the like as a request, and merges the memo data with the conference material to create the material with memo. Store (register) in a queue (queue). Specifically, the registration unit 510 stores (registers) the request including the memo data and the memo ID in the queue configured in the request registration DB 509c.

<< Step S1905 >>
The process number setting unit 511 of the conference server 20 sets the maximum number of simultaneous processes (thread number) of the process of creating the document with memo corresponding to each memo data by the create unit 503. Specifically, the processing number setting unit 511 has at least one of a creation request acceptance process (for example, the number of accepted creation requests) by the creation request reception unit 502 and a request registration process by the registration unit 510. Set the maximum number of simultaneous processes (number of threads) based on the load status.

<< 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. In this case, the creation unit 503 creates a document with a memo by multithreading with the maximum number of simultaneous processes (number of threads) set by the process number setting unit 511. As described above, the creation unit 503 normally performs processing with the maximum number of simultaneous processes (number of threads) set by the process number setting unit 511, but is not limited to this, and the set maximum number is set. Processing may be performed by threads that are less than or equal to the number of simultaneous processes (number of threads).

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 S1919.

<< Step S1907 >>
The status notification unit 504 of the conference server 20 sends a status notification to the participant terminal 10 by push notification via the communication unit 508 and the network 2 in order to notify the progress status of the creation of the document with memo by the creation unit 503. Send. The status notification unit 504 transmits a status notification notifying the progress of the creation of the document with memo, for example, at predetermined intervals (for example, every 10 seconds). The status notification includes a memo ID that identifies the memo data for which the document with memo is created, the status of creation, and the number of requests for the queue. When the request for creating the document with memo is in the waiting state in the queue, the status notification unit 504 sets the creation status to "waiting" (waiting for creation start) and transmits the status notification.

<< Step S1908 >>
When the screen control unit 402 of the participant terminal 10 receives a status notification that the creation status is "waiting" (waiting for creation start) from the conference server 20 via the communication unit 408, a memo as shown in FIG. 18 The display unit 411 displays a state transition screen for displaying the fact that the creation of the attached document is waiting for the start and the "number of people waiting". 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. 18, 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 S1914.

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

<< Step S1910 >>
When the screen control unit 402 receives the status notification that the creation status is “processing” (processing) from the conference server 20 via the communication unit 408, a document with a memo as shown in FIG. 19 is being created. The display unit 411 displays a state transition screen that displays the state 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 >>
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. After that, the creation unit 503 moves on to the processing of the next request in the queue.

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

<< Step S1913 >>
When the screen control unit 402 receives the status notification that the creation status is "downloading" (downloading) from the conference server 20 via the communication unit 408, a document with a memo as shown in FIG. 20 is being downloaded. The display unit 411 displays a state transition screen that displays the state and the "waiting number of people". Here, the "waiting number" is 0 because the material with the memo to be acquired is already being downloaded.

<< Step S1914 >>
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 S1919. 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 S1915 >>
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 S1916 >>
When the download (sending) of the material with a memo is completed by the material sending unit 507, the status notification unit 504 pushes a status notification indicating that the download is completed via the communication unit 508 and the network 2. It is transmitted to the participant terminal 10 by the notification. Specifically, the status notification unit 504 sets the created status to "complete" (download completed) and transmits the status notification. Further, after transmitting the status notification whose creation status is "complete" (download completed), the status notification unit 504 stops the transmission of the status notification (notification of the creation status).

<< Step S1917 >>
When the screen control unit 402 receives the status notification that the creation status is "complete" (download completed) from the conference server 20 via the communication unit 408, the document with memo as shown in FIG. 21 is downloaded. The display unit 411 displays a state transition screen that displays the state and the "waiting number of people". Here, the "waiting number" is 0 because the material with the memo to be acquired has already been downloaded.

<< Step S1918 >>
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. 17 again.

<< Step S1919 >>
When the second acquisition form (“acquire later”) is selected as the acquisition form of the material with memo by the participant, the material acquisition unit 405 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 status notification stop request 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 S1920 >>
When the status notification unit 504 receives the status notification stop request including the memo ID for identifying the memo data from the participant terminal 10 via the communication unit 508, the status notification unit 504 identifies the request stored in the queue by the memo ID. Stop sending status notifications for the requested request.

<< Step S1921 >>
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 S1922 >>
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. 22. It is displayed on the display unit 411. Participants make a note of the URL notified on the acquisition URL screen.

<< Steps S1923, S1924 >>
Participants access the URL reserved in step S1922 using a Web browser or the like at an arbitrary timing.

<< Step S1925 >>
The material sending unit 507 of the conference server 20 receives access to the URL notified by the URL notification unit 505 from the participant terminal 10, and is a list of materials with memos that have already been created and can be downloaded (downloadable data list). ) Is transmitted to the participant terminal 10 via the communication unit 508 and the network 2.

<< Step S1926 >>
When the screen control unit 402 receives the downloadable data list from the conference server 20 via the communication unit 408, the screen control unit 402 displays a data list screen for displaying the contents of the downloadable data list as shown in FIG. 23 on the display unit 411. Let me.

<< Step S1927 >>
Participants press the "Download" button on the data list screen shown in FIG. 23. Then, the material acquisition unit 405 of the participant terminal 10 makes a meeting of the material request with memo including the memo ID that identifies the memo data merged with the material with memo requesting acquisition via the communication unit 408 and the network 2. Send to server 20.

<< Step S1928 >>
When the material sending unit 507 receives the memo-attached material request from the participant terminal 10 via the communication unit 508, the material sending unit 507 extracts the memo-attached material specified by the memo-attached material request from the material storage unit 509b.

<< Step S1929 >>
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, the maximum number of simultaneous processes for creating the document with memo is based on the load state of at least one of the request acceptance process and the request registration process (the maximum number of simultaneous processes. The number of threads) is set. As a result, without increasing the hardware specifications of the conference server 20, the maximum capacity can be exhibited according to the state of the number of requests at that time while maintaining the current processing capacity of the conference server 20. Overload can be suppressed.

Further, the upper limit of the number of requests that can be received all at once in the request reception process in the conference server 20 is set. As a result, it is possible to prevent the memory area required for subsequent processing (for example, request registration processing, memo-attached material creation processing, etc.) from being consumed.

Further, a push notification from the conference server 20 to the participant terminal 10 is used to notify the state of creation of the material with memo including the completion of creation of the material with memo. Therefore, since the conference server 20 is not burdened with a load such as polling processing with each participant terminal 10, the load on the conference server 20 can be reduced. Further, since the participant terminal 10 downloads the material with memo from the conference server 20 after receiving the notification of the completion of creation of the material with memo based on the push notification, the load on the conference server 20 can be reduced. ..

As a method of switching to the second acquisition mode after the first acquisition mode is selected, in FIG. 13, 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, although the number of requests is displayed as the "waiting number" on the acquisition method selection screen shown in FIG. 16 and the state transition screens shown in FIGS. 18 to 21, the number of requests 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.

Further, in the sequence diagrams of FIGS. 12 and 13, 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. 17, 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 Disk-File), 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-10f 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 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 Creation request reception unit 503 Creation unit 504 Status notification unit 505 URL notification unit 507 Material transmission unit 508 Communication unit 509 Storage unit 509a Conference information storage unit 509b Material storage unit 509c Request registration DB
510 Registration unit 511 Processing number setting unit 601 Queue 602 Request

Japanese Unexamined Patent Publication No. 9-106381

Claims (10)

Memo data added at the conference terminal, and a reception unit that accepts requests to create data with memos for the memo data.
With the memo based on the conference use data and the memo data based on at least the number of the creation requests received by the reception unit and the predetermined upper limit of the number of creation requests received all at once by the reception unit. A setting unit that sets the maximum number of simultaneous processes for data creation to be less than the set maximum number of simultaneous processes ,
A creation unit that creates the data with memos based on the conference use data and the memo data by threads having the maximum number of simultaneous processes set by the setting unit.
Conference device equipped with. Further, a registration unit for registering the memo data received by the reception unit as a request in a queue is further provided.
The conference device according to claim 1, wherein the setting unit further sets the maximum number of simultaneous processes so as to suppress the load of the conference device based on the load state of the registration process by the registration unit. The first acquisition form in which the data with memos is downloaded by the conference terminal when the creation of the data with memos is completed after receiving the request for creating the data with memos from the conference terminal, and from the conference terminal. The creation request is made, and the memo-attached data is downloaded by the conference terminal at an arbitrary timing after the memo-attached data is created. Among the second acquisition forms, the form selected by the conference terminal is used. A sending unit that sends data with memos to the conference terminal,
When the first acquisition form is selected by the conference terminal, the first notification unit that notifies the conference terminal of the state of creation of the memo-attached data by the creation unit by push notification.
The conference device according to claim 1 or 2 , further comprising. When the second acquisition form is selected by the conference terminal, the conference terminal is further provided with a second notification unit that notifies the conference terminal of the access destination for downloading the memo-attached data created by the creation unit. The conference device according to claim 3 . Based on the number of the requests registered in the queue by the registration unit for display on the conference terminal, the first is to notify the waiting period until the processing for the creation request corresponding to the memo-attached data is performed. 3. The conference device according to claim 2, further comprising a notification unit. The creating unit is to be 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 item according to any one of claims 1 to 5 , wherein the data with the memo is created based on at least one of the memo data selected from the added shared memo data and the conference use data. Conference device. Memo data added at the conference terminal, and a reception unit that accepts requests to create data with memos for the memo data.
The memo is based on the conference use data and the memo data, at least based on the number of the creation requests received by the reception unit and the vicinity of a predetermined upper limit of the number of creation requests received all at once by the reception unit. A setting unit that sets the maximum number of simultaneous processes for the process of creating attached data to be less than the set maximum number of simultaneous processes ,
A creation unit that creates the data with memos based on the conference use data and the memo data by threads having the maximum number of simultaneous processes set by the setting unit.
Meeting system with. 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. A reception step that accepts the memo data added in the conference terminal and a request to create data with a memo for the memo data, and
Maximum simultaneous processing to create the memo data based on the conference usage data and the memo data based on at least the number of the created requests received and the predetermined upper limit of the number of created requests received all at once. A setting step that sets the number of processes less than the set maximum number of simultaneous processes , and
A creation step of creating the data with a memo based on the conference usage data and the memo data by a thread having the maximum number of simultaneous processes set or less.
Information processing method with. On the computer
A reception step that accepts the memo data added in the conference terminal and a request to create data with a memo for the memo data, and
Maximum simultaneous processing to create the memo data based on the conference usage data and the memo data based on at least the number of the created requests received and the predetermined upper limit of the number of created requests received all at once. A setting step that sets the number of processes less than the set maximum number of simultaneous processes , and
A creation step of creating the data with a memo based on the conference usage data and the memo data by a thread having the maximum number of simultaneous processes set or less.
A program to execute.

Images