JP4694222B2 - Minutes reproduction method, conference terminal, and conference server in a network conference system. - Google Patents

Description

  The present invention relates to a minutes reproducing method, a conference terminal, and a conference server in a network conference system.

In the electronic conference system, the content of the electronic conference (multimedia data) is stored, so that the conference content can be reproduced later.
However, it is inefficient to check all stored conference data. Therefore, there is a conventional technique in which a minutes (minutes) edited from the contents of an electronic conference is created, and a minutes creation support apparatus is used when creating the minutes (see Patent Document 1).
In the above-described conventional technology, although there is support by a conference record creation support device, creating a conference record (minutes) edited from the contents of an electronic conference is a considerable labor and takes time.
In addition, in order to improve the accuracy of the minutes (minutes), it is necessary to review all past conference contents.
That is, even if all the contents of the conference (multimedia data) are stored, it takes much time to effectively use the stored conference data later.

  In recent years, VoIP (Voice over IP) technology that realizes voice calls over IP networks, speeding up and widening of networks, and recording on hard disks due to increased hard disk capacity, etc. The environment necessary to efficiently and effectively hold a conference concluded with is being prepared. Under such an environment, the recording and recording of the conference contents can be easily performed at each conference terminal.

However, it is common for meetings to record and save the contents as minutes. Such minutes may be presented to related parties (for example, those who have failed to attend the meeting or who are related to the contents of the proceedings). However, when all the contents of the meeting are recorded as minutes, there is a possibility that the contents other than those who participated in the meeting do not want to be heard, that is, contents that should not be recorded are recorded in the minutes.
In order to solve such a problem, “a voice input unit for inputting voice, a recording unit for recording voice input through the voice input unit, and input through the voice input unit” "Off-recording" or the like by a "meeting system that includes a speech recognition unit that recognizes speech content and a control unit that interrupts the recording operation of the recording unit when the speech recognition unit recognizes a predetermined keyword" After the predetermined keyword is recognized, a technique is known in which the recording operation is interrupted and the contents that should not be recorded are not recorded in the minutes. (See Patent Document 2)
JP 7-182365 A Japanese Patent Laying-Open No. 2004-177777 (Claim 1 (0002) (0003))

In the above-described conventional technology, although there is support by a conference record creation support device, creating a conference record (minutes) edited from the contents of an electronic conference is a considerable labor and takes time.
In addition, in order to improve the accuracy of the minutes (minutes), it is necessary to review all past conference contents.
That is, even if all the contents of the conference (multimedia data) are stored, it takes much time to effectively use the stored conference data later.
In the conventional technology, the technology that does not record the minutes up to the content that should not be recorded,
Recording can be interrupted after recognizing a predetermined keyword such as “off record”, but remarks such as “disappointment” that should not be left in the record are often understood after being remarked, and there has been a problem in practice.

  An example of a problem to be solved by the present invention is to improve the usability of the network conference system by providing a function that does not reproduce a message or data that is unnecessary to be reproduced as a minutes.

The network conference system according to claim 1, a real-time conference data file configured by arranging real-time conference data in time series,
A conference server that is used to search for the real-time conference data file, and includes an index file configured by associating time information, header information, and information for accessing the real-time conference data file; ,
A conference terminal as a client connected to the conference server via a network,
A server / client system capable of accessing the real-time conference data file based on the header information of the index file after the real-time conference is completed, and reading out desired real-time conference data and reproducing it on the conference terminal Network conferencing system
The conference terminal
A playback prohibition start button and a playback prohibition end button for setting the range of playback prohibition data are provided.
The conference server
On the time axis, when a time interval is set at a predetermined time interval from the start time of the real-time conference, and the playback prohibition start button of the conference terminal is pressed during the real-time conference , The time departed from the pressing time by a predetermined time, the time interval set immediately before the retroactive time is specified, and the reproduction prohibition start is set at the time corresponding to the specified time interval , and the set The reproduction prohibition start information is recorded in the index file.

The conference terminal according to claim 5 includes a reproduction prohibition start button and a reproduction prohibition end button used in the network conference system according to any one of claims 1 to 4 .

The conference server according to claim 6 includes a detection unit that detects pressing of a reproduction prohibition start button and a reproduction prohibition end button used in the network conference system according to any one of claims 1 to 4 , A real-time conference data file excluding the reproduction prohibited data range is transmitted to the conference terminal.

Hereinafter, the form of the network conference system as a premise of the present invention will be described with reference to the drawings.
(Prerequisite conference network system configuration)
FIG. 1 is a block diagram for explaining an outline of a characteristic configuration of a network conference system, execution of a real-time conference, and recording operation of real-time conference data. FIG. 2 is a diagram for explaining the outline of the operation when reproducing the real-time conference data.

  As shown in FIG. 1, the network conference system is a server / client system in which a plurality of conference terminals 140 a to 140 n are connected to a conference server 100 via a network 130.

  The conference server 100 includes a real-time conference processing unit 110 that centrally processes multimedia data generated in a real-time conference, and a conference data storage unit 120 that stores real-time conference data (multimedia data) as needed. ing.

Here, the conference data storage unit 120 stores the multimedia data as a file in a predetermined format (real-time conference data file 124).
In addition, the conference data storage unit 120 also generates a conference data index file 122 so that the real-time conference data file 124 can be efficiently accessed.

  The conference data index file 122 includes time information (time stamp), heading (chapter) information, and access information (reference destination address information) to the real-time conference data file 124.

  Participants of the conference make a conference reservation in the conference server 100 in advance, and when the conference start time comes, they access the conference server 100 from the conference terminals 140a to 140b and participate in the conference. Send and receive conference data between them.

  Real-time conference data (multimedia data) is stored in the conference data storage unit 120 as needed. That is, in parallel with the progress of the conference, the real-time conference data file 124 and the conference data index file 122 are generated and stored.

When reproducing real-time conference data, as shown in FIG. 2, the conference terminals 140 a to 140 n access the conference data storage unit 120 and refer to the conference data index file 122.
That is, referring to the heading list recorded in the conference data index file 122, a desired heading is designated.
Then, the real-time conference data file 124 after the time when the heading is set is read and sent to the conference terminals 140a to 140n, and the conference data is reproduced on each conference terminal.

  By referring to the heading list created based on the conference data index file 122, the user of the conference terminal can determine the number of important points (important scenes) of the conference and the time at which the scene occurred (or start of the conference). Elapsed time from) can be immediately known.

  Therefore, the heading list substantially serves as a minutes. Further, since the conference data index file 122 is automatically generated during the conference, it is possible to save the trouble of creating the minutes after the conference.

  Further, by referring to the conference data index file 122, it is possible to efficiently access the real-time conference data file 124 and reproduce the conference data at a desired location. Therefore, it is possible to effectively use the stored real-time conference data file.

FIG. 3 is a diagram for explaining a characteristic operation in the network conference system (a specific operation relating to setting of a headline by manual insertion). CP0 to CP14 shown at the top of FIG. 3 are time intervals (time chapters) provided at predetermined time intervals on the time axis.
This time delimiter (time chapter) serves as a reference for setting a manually inserted heading (indicated as “manual insertion chapter” or “headline by manual insertion”).

The upper part of FIG. 3 shows the operation during the real-time conference.
As shown in the figure, the screen is switched to scene 1, scene 2, and scene 3. Here, in the scene 2, presenter (a person who performs a presentation) is an A, in Scene 3, presenter is changed to B.

  It is necessary to automatically record such a change of the presenter and a page change of the reference material. Accordingly, at time t6, an automatic insertion chapter (sometimes referred to as “heading by automatic insertion”) ACP indicating the change of the presenter is set.

Also, in the scene 2, it is assumed that the presenter A makes an important statement. Participant B and Participant C have a chapter insertion button (see FIG. 3 ) provided in their own conference terminal at times t4 and t5 to set a headline (manual insertion chapter) in important scene 2 respectively. Is pressed (steps S1-1 and S1-2).

However, when the chapter insertion button is pressed, the already important scene 2 is a thing of the past.
Therefore, the conference server returns the time by a predetermined time (for example, 30 seconds) from the times t4 and t5 (steps S2-1 and S2-2), and specifies the time (t2, t3) at which the time is returned.

  If headings (manual insertion chapters) HCP2 and HCP3 are set at the time point (t2, t3) going back on this time axis, the headings are set before the scene 2 where the presenter A makes an important statement. Is possible.

  However, it is troublesome to set the heading at an arbitrary point in hardware processing (the burden on the hardware is heavy).

  Also, if a large number of participants send headline insertion requests at the same time with a slight shift, manual insertion headings (manual insertion chapters) will be set for the number of insertion requests. Can be said to be heavy and inefficient.

  Therefore, in a more preferable aspect, time delimiters (time chapters) CP0 to CP14 are provided on the time axis at predetermined time intervals in advance, and when there is a header insertion request, only a predetermined time (for example, 30 seconds) is provided. The time is returned, and a heading is set at a time section (time chapter) immediately before the time of return.

  That is, in FIG. 3, the time is further returned from the time point (time t2, t3) specified by the time return of the predetermined time (steps S3-1, S3-2), and the time point (time time) CP4 (time chapter) At t1), a manual insertion (manual insertion chapter) is set (step S4).

  Thereby, even when there is a headline insertion request from a plurality of participants, the headlines can be collected at one time point (time).

  In addition, since it is determined in the system that time breaks (time chapters) are inserted at predetermined time intervals, when setting headings by using the time breaks (time chapters) as a reference for headline setting. The burden on the hardware is also reduced.

  Manual insertion heading (manual insertion chapter) HCP1 (HCP2, HCP3), automatic insertion chapter (chapter automatically inserted to record changes such as presenter changes and page changes) The ACP and time delimiters (time chapters) CP0 to CP14 are recorded in the conference data index file 122 in the conference server 100 (see FIG. 1).

The lower part of FIG. 3 shows the operation at the time of reproducing the real-time conference data.
A person who reproduces the real-time conference data is presented with a headline list (this list includes time information with the headline) via the conference terminals 140a to 140n (see FIG. 2).

  This heading list is created based on chapter information excluding information on time breaks (time chapters) (that is, each information of “heading by manual insertion” and “heading by automatic insertion”). This heading list essentially functions as a minutes.

When the person designates a specific heading (manual insertion chapter) (step S5), the real-time conference data file 124 (see FIG. 2) after time t1 corresponding to the heading HCP1 designated by the person is stored in the conference server. 100 (see FIG. 2).
The read real-time conference data file is sent to the conference terminal and reproduced on the conference terminal (step S6).

  In this way, during a real-time conference, if there is a scene that the participant feels important, a manual header insertion request is sent from the conference terminal to the conference server, and a manual header (manually inserted) Insert chapters can be set at the appropriate time (ie, before the scene occurs).

  After the conference, the user of the conference terminal can reproduce the corresponding real-time conference data file by referring to the heading list and specifying a specific heading (manual insertion chapter or automatic insertion chapter). .

FIG. 4 shows an operation for recording time breaks (time chapters) and automatic insertion chapters (chapter automatically inserted to record changes such as presenter changes and page changes) in the index file, and the index file. It is a figure for demonstrating the correspondence of a real-time meeting data file.
As shown in the upper side of FIG. 4, time delimiters (time chapters) CP26 to CP29 are set at intervals of 10 seconds.

As shown in the figure, CP26 is set 10 minutes and 20 seconds after the start of the conference, and similarly, CP27 to CP29 are set at intervals of 10 seconds.
The automatic setting chapter ACP1 is set to record the presenter change at the time when 10 minutes and 26 seconds have elapsed since the start of the conference.

  The automatic setting chapter ACP2 is set to record a page change when 10 minutes and 47 seconds have elapsed since the start of the conference.

In the lower left of FIG. 4, the contents of the conference data index file 122 are shown.
As shown in the figure, the conference data index file 122 is associated with a number, time, event content, and reference destination information (for example, information indicating the number of bytes from the beginning of the real-time conference data file 124). It is recorded in the format.

  When a time segment (time chapter) is recorded, a time segment number (time chapter) is described in the “event contents” column, such as “CP26”.

  When the automatic setting chapters (ACP1, ACP2) are recorded, the “event contents” column includes items that cause the insertion of the automatic setting chapters such as “change presenter” and “page change”. be written.

As shown in the lower right of FIG. 4, the real-time conference data file 124 is a file in a format in which numbers, times, and conference data are associated with each other.
By referring to the conference data index file 122, it is possible to know when the presenter change or the page change is performed. Further, by following the link of the reference destination, it becomes possible to immediately access a file in which the content of the conference when the presenter is changed is recorded.

FIG. 5 is a diagram for explaining an operation of recording a headline (manual insertion chapter) by manual insertion in an index file and a correspondence relationship between the index file and the real-time conference data file.
Similar to FIG. 4, time delimiters (time chapters) CP44 to CP50 are set every 10 seconds from the start of the conference.

In addition, a presenter change occurs 28 minutes and 45 seconds after the start of the conference, and accordingly, an automatic insertion chapter ACP3 is set.
29 minutes 48 seconds after the start of the conference, the conference participant presses the chapter insertion button (see FIG. 6).
The conference server detects that the button is pressed and returns the time by 30 seconds from the time when the button is pressed. Thereby, it returns to the time of 29 minutes and 18 seconds after a meeting start.

  Next, the time segment (time chapter) CP46 immediately before that point is specified. Then, the time is returned from a time point 29 minutes and 18 seconds after the start of the conference to a time point corresponding to CP 46 (a time point 29 minutes and 10 seconds after the start of the conference). This time is the time when a manual insertion heading (manual insertion chapter) is set.

Thus, since the time return process is performed in the conference server, the headline by manual insertion can be set at an appropriate time.
Here, in the conference data index file 122, the time when the heading (manual insertion chapter) is set (information indicating the time when 29 minutes and 10 seconds have passed since the start of the conference) and the insertion request for the heading (manual insertion chapter) are received. The name of the participant who made the call and the access information to the real-time conference data file 124 are recorded in association with each other. The participant name is described in the “event content” column.

  The real-time conference data file 124 is a file in a format in which numbers, times, and conference data are associated with each other.

  Among the information held in the conference data index file 122, the information of the automatic insertion chapter regarding the change of the presenter and the information of the heading (manual insertion chapter) manually inserted to identify an important scene are the main points of the conference. By circulating this information after the meeting as a list, it is possible to obtain the same effect as circulating the minutes.

  That is, by referring to the heading list (chapter list), it is possible to know when the presenter change or the like was made and who set the heading (manual insertion chapter). Then, by following the link of the reference destination, it becomes possible to immediately access the real-time conference data file 124 in which the content of the conference at the time when those chapters are set is recorded.

Next, the “reproduction prohibition data” setting function at the time of reproducing the minutes, which is the first embodiment of the present invention, will be described.
FIG. 6 is a diagram for explaining a characteristic operation in the network conference system (specific operation relating to setting of reproduction prohibition data). CP0 to CP14 shown at the top of FIG. 6 are time intervals (time chapters) provided at predetermined time intervals on the time axis.
This time division (time chapter) is a reference when setting the reproduction prohibition start point.

The upper part of FIG. 6 shows the operation during the real-time conference.
As shown in the figure, the screen is switched to scene 1, scene 2, and scene 3. Here, in the scene 2, presenter (a person who performs a presentation) is an A, in Scene 3, presenter is changed to B.

It is necessary to automatically record such a change of the presenter and a page change of the reference material. Accordingly, at time t6, an automatic insertion chapter (sometimes referred to as “heading by automatic insertion”) ACP indicating the change of the presenter is set.
Up to this point, the description is the same as in FIG.

In scene 2, it is assumed that the presenter A makes a statement that he / she does not want to leave in the minutes (a statement such as a disclaimer (hereinafter referred to as a reproduction prohibited statement)). Participant B and participant C press the playback prohibition start button (see FIG. 6) provided in their conference terminals at times t4 and t5, respectively, in order to set the playback prohibition function for the scene 2 (see FIG. 6). Steps S1-1 and S1-2).

However, when the reproduction prohibition start button is pressed, the scene 2 that should be prohibited from being reproduced is a past thing.
Therefore, in the conference server of the present invention, the time is returned by a predetermined time (for example, 30 seconds) from the times t4 and t5 (steps S2-1 and S2-2), and the time (t2, t3) at which the time is returned is specified. .

  If the playback prohibition start time and HCP2 and HCP3 are set at the time point (t2, t3) going back on the time axis, the playback prohibition start time is set before the scene 2 to be prohibited from playback by the presenter A. Is possible.

  However, it is troublesome to set the heading at an arbitrary point in hardware processing (the burden on the hardware is heavy).

  Also, if a large number of participants make a playback prohibition start request at the same time with a slight deviation, it will set the playback prohibition start by the number of insertion requests, which is also heavy and inefficient. It can be said that.

  Therefore, in a more preferable aspect, time segments (time chapters) CP0 to CP14 are provided on the time axis at predetermined time intervals in advance, and when there is a reproduction prohibition start request, a predetermined time (for example, 30 seconds) is set. The head is set back at the point (time point) of the time break (time chapter) just before the time point of returning.

  That is, in FIG. 6, the time is further returned from the time point (time t2, t3) specified by the time return of the predetermined time (steps S3-1, S3-2), and the time point (time time) CP4 (time chapter) At t1), a reproduction prohibition start time is set (step S4).

  Thereby, even when there is a reproduction prohibition start request from a plurality of participants, headlines can be collected at one time point (time).

  In addition, since it is determined in the system that time breaks (time chapters) are inserted at predetermined time intervals, when setting headings by using the time breaks (time chapters) as a reference for headline setting. The burden on the hardware is also reduced.

Playback prohibition start time set in this way, HCP1 (HCP2, HCP3), automatic insertion chapter (chapter automatically inserted to record changes such as a presenter change and page change) ACP, and Time breaks (time chapters) CP0 to CP14 are recorded in the conference data index file 122 in the conference server 100 (see FIG. 1).
In the above description, it is described that the player B or C other than the speaker A presses the playback prohibition start button. However, it is clear that the speaker A himself may press the playback prohibition start button. It is.

The playback prohibition function set by the playback prohibition start button can be canceled by the playback prohibition release button.
The lower part of FIG. 6 shows the operation at the time of reproducing the real-time conference data.
Even if there is a request for reproduction of real-time conference data, it is reproduced except for the reproduction prohibited section.

FIG. 7 is a diagram for explaining the operation of recording the reproduction prohibition start and the reproduction prohibition end in the index file, and the correspondence relationship between the index file and the real-time conference data file.
Similar to FIG. 4, time delimiters (time chapters) CP26 to CP29 are set every 10 seconds from the start of the conference.

Also, a presenter change occurs 10 minutes and 20 seconds after the start of the conference, and accordingly, an automatic insertion chapter ACP1 is set.
After 10 minutes and 26 seconds from the start of the conference, the conference participant presses the reproduction prohibition start button (see FIG. 6).
The conference server detects that the button is pressed and returns the time by a predetermined time from the time when the button is pressed.
Then, the time interval (time chapter) CP26 immediately before that point is specified. The time point 10 minutes and 20 seconds after the start of the conference is the time point when the reproduction prohibition start is set.

Next, 10 minutes and 47 seconds after the start of the conference, the conference participant presses the reproduction prohibition end button (see FIG. 6).
The conference server detects that the button is pressed and returns the time by a predetermined time from the time when the button is pressed.
Then, the time segment (time chapter) CP28 immediately before that point is specified. The time point 10 minutes and 40 seconds after the start of the conference is the time point when the reproduction prohibition end is set.

This process is recorded in the attribute column of the conference data index file 122 of FIG.
This conference data index file 122 is obtained by adding an attribute column to the conference data index file 122 of FIG. 4, and the others are the same.

(Second Embodiment)
FIG. 8 is a block diagram showing a specific configuration of the network conference system (and each of the components of the system) of the present invention. 8, the same parts as those in FIGS. 1 and 2 are denoted by the same reference numerals.

8, the conference terminal 140c includes a communication unit 142, a video / audio processing unit 144, a conference processing unit 146, an input / output interface 148, a chapter setting button (heading by manual insertion). Setting means) 150, a monitor 152, a microphone 154, a reproduction prohibition start button 157, and a reproduction prohibition end button 158.
The conference terminals 140a and 140b have the same configuration as that of 140c.

Although not shown, a mouse for operating the point cursor and a camera for taking images of the participants themselves are also provided. The configuration of the other conference terminals (140a, 140b) is the same.
Each conference terminal 140 a to 140 c is connected to the conference server 100 via the network 130.

  The conference server 100 includes a communication unit 102, a video / audio processing unit 104, a conference management unit 106 that performs conference reservation and participant authentication, and a real-time conference processing unit 110 (data interface 111, command detection unit 112, A chapter insertion request detection unit 113 and a reproduction prohibition start / end button press detection unit 156), a real-time conference data file generation unit 114 (a data interface 115, a time stamp addition unit 116, a recording unit 117, and a chapter management unit 118). A clock unit 119, a user list file 121, a conference data index file 122, an index file generation unit 123 (having an index file information management unit 125, a time return unit 126, and a memory 127), and real-time conference data. File 1 With 4 storage section for storing the the (hard disk) 128, a search unit 129 for searching conference data index file 122, a reproduction control section 131 for controlling reproduction of the real-time conference data file 124.

  The data interface 111 of the real-time conference processing unit 110 transmits real-time conference data (multimedia data) to the real-time conference data file generation unit 114.

Further, the command detection unit 112 detects a command for notifying a presenter change, a document page change, and the like.
The chapter insertion request detection unit 113 functions to detect when a chapter insertion button 150 of the conference terminal (140a to 140n) is pressed and a setting request for a headline (manual insertion chapter) is transmitted.
Further, the reproduction prohibition start / end button pressing detection unit 156 detects that the reproduction prohibition start button or the reproduction prohibition end button has been pressed, and transmits it to the real-time conference data file generation unit 114.

  The data interface 115 of the real-time conference data file generation unit 114 receives the real-time conference data sent from the real-time conference processing unit 110, and the time stamp adding unit 116 adds a time stamp (time information) to the conference data. Then, the recording unit 117 records the conference data in the storage unit (hard disk or the like) 128.

  In addition, the chapter management unit 118 of the real-time conference data file generation unit 114 sets time divisions (time chapters), automatically inserted headings (automatic insertion chapters), and manually set headings (manual insertion chapters). ) Setting timing, and instructing the index file generation unit 123 to set each chapter.

  Further, the index file information management unit 125 in the index file generation unit 123 functions to centrally manage various information to be recorded in the conference data index file 122 and create an index file.

  The time return unit functions to execute the “time return process” described above. Note that the memory 127 serves to temporarily hold various types of information.

  The conference data index file 122 shown in FIG. 8 includes a number, time (time stamp), event contents, attributes, and pointers.

In the “event content” column, as described with reference to FIGS. 4, 5, and 7, the cause of the change in the conference content such as “change presenter” and “page change” is described.
In the “attribute” column, conditions at the time of reproduction of the conference content such as “reproduction prohibition start” and “reproduction prohibition end” are described.

  In the case of setting a headline (manual insertion chapter) by manual insertion, the “participant name” that first transmitted the headline insertion request is described.

  Note that information accompanying “event contents” may be written in the “additional information” column (not shown). For example, if “event content” is “change presenter”, the name of the new presenter after the change is described.

  In addition, when “event content” is set to a manual insertion (manual insertion chapter), “user identification flag” is described.

  This user identification flag is a flag that enables identification of all the participants who have transmitted the request when there are a plurality of header setting requests for the same scene.

  That is, one flag bit is assigned to each participant. For example, if there are three participants A to C, the number of bits of the flag is set to 3 bits, and the bit corresponding to the person who sent the setting request for the manual insertion (manual insertion chapter) is set to “1”. Other than that, “0” is set. Thereby, it is possible to easily record who desires to set a headline (manual insertion chapter) by manual insertion.

  The “pointer” is information indicating an accumulation address of real-time conference data corresponding to each chapter.

  In other words, this is information indicating what byte should be accessed from the top of the real-time conference data file 124. A pointer for video information and two pointers for audio information are required.

  In addition, when there is a request for reproducing conference data stored from the conference terminals (140a to 140n) after the conference ends, the playback control unit 131 first instructs the search unit 129 to store the conference data index file 122. To search other chapters (automatic insertion chapter and manual insertion chapter) excluding the time break (time chapter), extract time information, event contents and attached information, and create a heading list.

And it transmits to the conference terminal (140a-140n) which transmitted the reproduction | regeneration request | requirement of conference data via the communication part 102. FIG.
The heading list is displayed on the monitor 152 of the conference terminals (140a to 140n).

When a person who wants to reproduce conference data specifies a specific heading, the information is transmitted to the reproduction control unit 131 of the conference server 100, and the reproduction control unit 131 refers to the pointer (link) of the conference data index file 122. The real-time conference data corresponding to the designated headline is read out and transmitted to the conference terminals (140a to 140n). As a result, the desired conference content is reproduced on the monitor 152.
When the conference data is reproduced, the reproduction of the conference data from the reproduction prohibition start point to the reproduction prohibition end point is prohibited by referring to the “attribute”.

  As a result, the stored real-time conference data file 124 can be efficiently accessed, and its effective use can be promoted.

Next, a specific operation procedure of the network conference system shown in FIG. 8 will be described with reference to FIGS.
FIG. 9 is a timing chart showing an operation procedure in the case where a time segment (time chapter) is recorded in the index file in the conference server of the network conference system shown in FIG.

  Conference data is transmitted from each conference terminal (140a to 140b) as needed (S10), and the conference data is sent from the real-time conference processing unit 110 to the real-time conference data file generation unit 114 as needed (S11). The real-time conference data with the time stamp is stored in the storage unit 128.

  On the other hand, the chapter management unit 118 of the real-time conference data file generation unit 114 determines whether to record time breaks (time chapters) in the conference data index file 122 (S12).

  That is, since the time interval (time chapter) is set at an interval of 10 seconds from the start of the conference, the chapter management unit 118 refers to the time information output from the clock unit 119 and sets the time interval (time chapter). It is determined whether or not the time has come.

  Then, when it is time to set a time break (time chapter), a time chapter setting request is issued from the chapter management unit 118 of the real-time conference data file generation unit 114 (S13).

  The index file information management unit 125 of the index file generation unit 123 newly adds “time stamp (offset value from the conference start time)”, “event content”, and “pointer” to the conference data index file 122. The conference data index file 122 is updated (S14).

  Then, the index file information management unit 125 returns a time chapter setting response (including the setting result, time stamp information indicating the setting time point, etc.) to the chapter management unit 118 of the real-time conference data file generation unit 114 (S15).

The chapter management unit 118 of the real-time conference data file generation unit 114 temporarily holds the time stamp information as the latest time stamp information at that time (S16).
Thereafter, the same operation is repeated (S17, S18).

  FIG. 10 is a timing chart showing an operation procedure in the case of recording a heading (automatic insertion chapter) by automatic insertion in the index file in the conference server of the network conference system shown in FIG.

  When a situation such as a presenter change, system mode change, page change, file delivery, or participation of a speaker occurs in the middle (S20), a command indicating that is sent from the conference terminals (140a to 140c) to the conference server. 100 is sent to the real-time conference processing unit 110 (S21), and then the content of the command is sent to the real-time conference data file generation unit 114 (S22).

  Next, the chapter management unit 118 of the real-time conference data file generation unit 114 sends an automatic insertion chapter setting notification (including a time stamp, event contents, and attached information) to the index file generation unit 123 (S23).

  The index file information management unit 125 of the index file generation unit 123 newly adds “time stamp (offset value from the conference start time)”, “event content”, “attached information”, and “pointer” to the conference data index file 122. ”And the conference data index file 122 is updated (S24).

  Next, it is checked whether the current command is a command indicating mid-presenter participation (S25), and it is checked whether the mid-way participant is not yet registered in the user list file 121 (S26). At that time, the identification number (ID) of the participant is added to the user list file 121 (S27).

  FIG. 11 is a timing chart showing an operation procedure when a headline (manual insertion chapter) by manual insertion is recorded in the index file in the conference server of the network conference system shown in FIG.

  When the participant (for example, chairperson) determines that the scene is an important scene during the meeting, the chapter insertion button 150 is pressed. Accordingly, a setting request for manual insertion (manual insertion chapter) is transmitted from the conference terminals (140a to 140c) to the conference server 100 (S30).

  The fact of the request is notified from the real-time conference processing unit 110 to the real-time conference data file generation unit 114 (S31).

  The chapter management unit 118 of the real-time conference data file generation unit 114 instructs the index file generation unit 123 to set a headline (manual insertion chapter) by manual insertion (S32).

  The time return unit 126 of the index file generation unit 123 performs time return for a predetermined time (for example, 30 seconds) on the time axis (S33). That is, a subtraction process is performed for a predetermined time from the current time information.

  Then, the index file information management unit 125 identifies a time segment (time chapter) immediately before the time when the time is returned, and thereby determines a setting time point of a headline (manual insertion chapter) by manual insertion (S34). . At this time, the index file information management unit 125 refers to the conference data index file 122.

  Subsequently, information (time stamp and pointer) at the time of setting a headline (manual insertion chapter) by manual insertion is acquired (S35).

  Subsequently, it is checked whether or not a manual insertion chapter has already been set at the time of setting a headline (manual insertion chapter) by manual insertion (S36). In other words, when a plurality of participants send a headline setting request with a slight shift in timing, such a situation is assumed, and this is checked.

  If a headline by manual insertion (manual insertion chapter) has already been set, this means that there are a plurality of persons who have transmitted the headline insertion request.

  In this case, the bit of the corresponding person in the user identification flag recorded in the “attached information” column of the conference data index file 122 is changed from “0” to “1” (thereby setting the heading setting). Information on who requested is added), and the conference data index file 122 is overwritten and updated (S38).

If the result of S36 is No, the “event content” in the conference data index file 122 is set to “manual insertion” and the person is identified in order to identify the person who sent the heading setting request. One bit of the flag is changed from “0” to “1” (S37).
In this way, the conference data index file 122 is updated.

  FIG. 12 is a timing chart showing an operation procedure when recording the reproduction prohibition start and the reproduction prohibition end in the index file in the conference server of the network conference system shown in FIG.

  When a participant (for example, chairperson) determines that the scene is a reproduction prohibited scene during the meeting, the reproduction prohibition start button 157 is pressed. Along with this, a reproduction prohibition start setting request is transmitted from the conference terminals (140a to 140c) to the conference server 100 (S40).

  The fact of the request is notified from the real-time conference processing unit 110 to the real-time conference data file generation unit 114 (S41).

  The chapter management unit 118 of the real-time conference data file generation unit 114 instructs the index file generation unit 123 to set the reproduction prohibition start (S42).

  The time return unit 126 of the index file generation unit 123 performs time return for a predetermined time (for example, 30 seconds) on the time axis (S33). That is, a subtraction process is performed for a predetermined time from the current time information.

  Then, the index file information management unit 125 identifies a time segment (time chapter) immediately before the time when the time is returned, and thereby determines a setting time point for starting playback prohibition (S44). At this time, the index file information management unit 125 refers to the conference data index file 122.

  Subsequently, information (time stamp and pointer) at the time point when reproduction prohibition start is set is acquired (S45).

  Subsequently, it is checked whether or not the reproduction prohibition start has already been set at the time of setting the reproduction prohibition start (S46). In other words, when a plurality of participants send a headline setting request with a slight shift in timing, such a situation is assumed, and this is checked.

  If the reproduction prohibition start has already been set, this means that there are a plurality of persons who have transmitted a reproduction prohibition start request.

If the result of S46 is No, the “attribute” of the conference data index file 122 is set to “reproduction prohibition start”.
In this way, the conference data index file 122 is updated.

When the conference progresses and the participant (for example, the chairperson) determines that the portion corresponding to the reproduction prohibition scene has ended, the time when the participant presses the reproduction prohibition end button is set as the reproduction prohibition end time.
Note that even when the conference participant presses the reproduction prohibition end button, the time may be set to a time that is a predetermined time backward as in the case where the reproduction prohibition start button is pressed.

The configuration, operation, and procedure for updating the index file as needed have been described above, but the present invention is not limited to the above-described embodiment, and can be variously modified.
For example, the conference client application may be a dedicated application or an application that operates on a WEB browser.

  The real-time conference data file may be a single file or a divided file. However, by dividing into a plurality of files, one file can be read and written easily and quickly.

  Moreover, the part which accumulate | stores real-time meeting data may exist on a server different from a meeting server. However, in this case, it is necessary to exchange control information between the conference server and another server.

In addition, regarding the format of the index file, the time information (time stamp) is not recorded to reduce the amount of data, or the information that supplements the event content is added to access the real-time conference data file more accurately. You may be able to do it.
Further, a technique may be adopted in which an index file is assigned with an identification number unique to the conference for management.

  In addition, when a conference participant sets a headline (manual insertion chapter) by manual insertion, the time on the time axis is set according to the time the chapter insertion button is pressed or the number of times the unit is pressed. It is also possible to adjust the return amount when returning. In this case, user convenience is further improved.

Next, an operation procedure for reproducing stored real-time conference data will be described.
FIG. 13 is a flowchart showing an operation procedure when the stored real-time conference data file is reproduced on the conference terminal in the network conference system of FIG.

The users of the conference terminals (140a to 140c) display a menu on the monitor 152 (see FIG. 8) (S50) and select “Conference playback” (S51).
The conference terminal is connected to the conference server 100 in the conference playback mode (S52).

The reproduction control unit 131 of the conference server 100 first transmits a reproducible conference list to the conference terminal (S53).
The conference list is displayed on the monitor 152 on the conference terminal (S54), and when the user selects a conference to be reproduced (S55), the identification information of the selected conference is notified (S56).

  In response to this, the playback control unit 131 of the conference server 100 instructs the search unit 129 to search from the conference data index file 122 for necessary headline information (that is, a headline by automatic insertion excluding the time chapter (automatically). (Insert chapter) and headline (manual insertion chapter information) by manual insertion) are extracted, a list is created by collecting the extracted information, and the list of headlines is transmitted to the conference terminal (S57).

  The heading list is displayed on the monitor 152 (S58), and the user selects one heading from the list (S59).

  Accordingly, the conference name, the heading (chapter) desired to be reproduced, and the reproduction command are transmitted from the conference terminal to the conference server (S60).

The playback control unit 131 of the conference server 100 refers to the pointer (link information) of the conference data index file 122, searches the real-time conference data file 124 stored in the storage unit 128, and obtains the real-time conference data at the corresponding location. Read (S61).
When reading out the real-time conference data, the “attribute” of the conference data index file 122 is referred to and read out from “reproduction prohibition start” to “reproduction prohibition end”.

Next, the read real-time conference data is transmitted to the conference terminal (S62).
Then, on the conference terminal, the real-time conference data is reproduced except for the portion from “reproduction prohibition start” to “reproduction prohibition end” (S63).

  Thus, by utilizing the index file, the stored real-time conference data file can be easily accessed, and effective use of the conference data is promoted.

  In addition, the index file is updated as needed during the progress of the meeting, and the list of headlines extracted from the index file serves as the minutes, so that the trouble of creating the minutes can be saved.

The configuration and operation for reproducing the real-time conference data are not limited to the above-described embodiment, and can be variously modified.
For example, in FIG. 13, the conference list is first transmitted and then the heading list is transmitted, but these may be transmitted simultaneously.

  Further, when creating a list of headings, for example, only the headlines related to a specific event may be extracted and created, or only the headlines set by a specific participant may be extracted and created.

  In addition, when a plurality of participants wish to set a heading (chapter) for the same scene, it is considered that the importance of the scene is high. Therefore, only a headline that satisfies the condition that the number of persons who desire headline setting exceeds a predetermined threshold may be extracted to create a list of headlines.

In addition, regarding a method for transmitting conference data from the conference server to the conference terminal, a method may be adopted in which conference data is burst transmitted from the conference server side and the conference is reproduced on the conference client side according to the time stamp. .
In the above description, the method of prohibiting playback by storing it in the real-time conference data file is adopted for the portion from “reproduction prohibition start” to “reproduction prohibition end”. It is also possible to delete the “reproduction prohibition end” portion.

  In addition, during the reproduction of the real-time conference data, it is possible to display the heading list again on the conference terminal and designate a new conference reproduction start point. In this way, only the part that the user wants to see (the part of the headline that the user wants to see) can be reproduced one after another on the conference terminal, thereby realizing efficient reproduction.

As described above, the network conference system in the above-described embodiment is used for searching the real-time conference data file 124 configured by arranging the real-time conference data in time series, and the real-time conference data file 124. A conference server 100 having information, headline information, and a conference data index file 122 configured by associating information for accessing the real-time conference data file 124, and the conference server 100 via the network 130. The conference terminals 140a to 140n as connected clients are configured to access the real-time conference data file 124 based on the header information of the conference data index file 122 after the real-time conference is completed. This is a server-client network conference system that can read out desired real-time conference data and reproduce it on the conference terminals 140a to 140n. The conference terminals 140a to 140n are manually input for manually inputting a header insertion request. When the real-time conference participant inputs a headline insertion request via the manual input unit of the conference terminals 140a to 140n during the real-time conference, the conference server 100 starts from the input time of the headline insertion request. In addition, the time of going back to the previous time is specified, a headline by manual insertion is set at the specified time, and the information of the set headline is recorded in the conference data index file 122.
According to such a network conferencing system, a headline can be set at an appropriate time by sending a headline insertion request when a conference participant feels an important point during the conference. . That is, it is possible to set a headline (manual insertion chapter) by manual insertion. This makes it possible to easily access the stored real-time conference data file without creating the minutes (meeting minutes).

  In addition, the heading list can be distributed immediately after the conference. By looking at the heading list, it is possible to immediately know the number of important parts (important scenes) and the time at which the scene occurred (or the elapsed time from the start of the conference).

Participants of the conference can immediately access the important scenes of the conference after the conference and reproduce the scenes except for the set reproduction prohibited portion. Efficient circulation is possible because the search effort can be saved.
Since it is possible to reproduce without the reproduction prohibition portion, it is possible to avoid a situation in which active discussions cannot be made because of fear of disagreement during recording in the network conference system.
In addition, unnecessary statements can be automatically removed when creating the minutes of the meeting.
Further, a person who does not participate in the conference can grasp the content of the conference in a short time by using the circulation and playback functions of the present invention.
Therefore, the usability and convenience of the network conference system are improved.
In the above description, remarks that are not required to be reproduced are mainly subject to reproduction prohibition. However, the reproduction prohibition object in the present invention is not limited to remarks (speech) but also data other than sound (for example, carelessness). Simple memos and drawings, provision of materials, etc.).

It is a block diagram for demonstrating the outline | summary of the characteristic structure of the network conference system used as the premise of this invention, execution of a real-time conference, and the recording operation of real-time conference data. It is a figure for demonstrating the outline | summary of the operation | movement at the time of reproduction | regeneration of real-time meeting data It is a figure for demonstrating the characteristic operation | movement (specific operation | movement regarding heading setting) in the network conference system used as the premise of this invention. Recording time breaks (time chapters) and automatic insertion chapters (chapter inserted automatically to record changes such as presenter changes and page changes) in the index file, and index file and real-time meeting data It is a figure for demonstrating the correspondence with a file. It is a figure for demonstrating the operation | movement which records a headline (manual insertion chapter) in an index file, and the correspondence of an index file and a real-time meeting data file. It is a figure for demonstrating the specific operation | movement regarding the setting of the reproduction | regeneration prohibition data in the network conference system of this invention. It is a figure for demonstrating the operation | movement which records reproduction | regeneration prohibition start and reproduction | regeneration prohibition end in an index file, and the correspondence of an index file and a real-time meeting data file. It is a block diagram which shows the specific structure of the network conference system (and each of the component of a system) of this invention. FIG. 9 is a timing chart showing an operation procedure when a time break (time chapter) is recorded in an index file in the conference server of the network conference system shown in FIG. 8. FIG. 9 is a timing chart showing an operation procedure when a heading (automatic insertion chapter) by automatic insertion is recorded in an index file in the conference server of the network conference system shown in FIG. 8. FIG. 9 is a timing chart showing an operation procedure when a headline (manual insertion chapter) by manual insertion is recorded in an index file in the conference server of the network conference system shown in FIG. 8. FIG. 9 is a timing chart showing an operation procedure when recording a reproduction prohibition start and a reproduction prohibition end in an index file in the conference server of the network conference system shown in FIG. 8. FIG. 9 is a flowchart showing an operation procedure when a stored real-time conference data file is reproduced on a conference terminal in the network conference system of FIG. 8.

Explanation of symbols

100 Conference Server 102 Communication Unit 104 Video / Audio Processing Unit 106 Conference Management Unit 110 Real-Time Conference Processing Unit 111 Data Interface 112 Command Detection Unit 113 Chapter Insertion Request Detection Unit 114 Real-Time Conference Data File Generation Unit 115 Data Interface 116 Time Stamp Addition Unit 117 Recording unit 118 Chapter management unit 119 Clock unit 121 User list file 122 Conference data index file 123 Index file generation unit 124 Real-time conference data file 125 Index file information management unit 126 Time return unit 127 Memory 128 Storage unit (hard disk or the like)
129 Search unit 130 Network 131 Playback control unit 140a to 140n Conference terminal 142 Communication unit 144 Video / audio processing unit 146 Conference processing unit 148 Input / output interface 150 Chapter setting button 152 Monitor 154 Microphone 156 Playback prohibition start / end button press detection unit 157 Playback prohibition start button 158 Playback prohibition end button

Claims (6)

Real-time conference data file configured by arranging real-time conference data in time series,
A conference server that is used to search for the real-time conference data file, and includes an index file configured by associating time information, header information, and information for accessing the real-time conference data file; ,
A conference terminal as a client connected to the conference server via a network,
A server / client system capable of accessing the real-time conference data file based on the header information of the index file after the real-time conference is completed, and reading out desired real-time conference data and reproducing it on the conference terminal Network conferencing system
The conference terminal
A playback prohibition start button and a playback prohibition end button for setting the range of playback prohibition data are provided.
The conference server
On the time axis, when a time interval is set at a predetermined time interval from the start time of the real-time conference, and the playback prohibition start button of the conference terminal is pressed during the real-time conference , The time departed from the pressing time by a predetermined time, the time interval set immediately before the retroactive time is specified, and the reproduction prohibition start is set at the time corresponding to the specified time interval , and the set A network conferencing system, wherein reproduction prohibition start information is recorded in the index file. When the playback prohibition end button of the conference terminal is pressed while the real-time conference is in progress, a time that goes back before the time when the playback prohibition end button is pressed is specified, and playback is prohibited at the specified time. 2. The network conference system according to claim 1, wherein an end is set, and the set reproduction prohibition end information is recorded in the index file. The real-time conference data file is stored separately from voice data and data other than voice data, and the range of the reproduction prohibition data can be set for each data other than the voice data and voice data. The network conference system according to claim 1 or 2. After completion of the real-time conference, a person who wants to reproduce the real-time conference data file transmits a reproduction request from the conference terminal to the conference server.
  The conference server reads the real-time conference data file excluding the range of the reproduction prohibition data and sends it to the conference terminal,
  The network conference system according to any one of claims 1 to 3, wherein a real-time conference data file excluding the reproduction-prohibited data range is played on the conference terminal. A conference terminal comprising a reproduction prohibition start button and a reproduction prohibition end button used in the network conference system according to claim 1. 5. A real-time conference that includes a detection unit that detects pressing of a reproduction prohibition start button and a reproduction prohibition end button used in the network conference system according to claim 1 and excludes the reproduction prohibition data range. A conference server that transmits a data file to a conference terminal.

Images