JP2018032097A - Information processing apparatus, conference system, method, and program - Google Patents

Abstract

[PROBLEMS] To efficiently discuss multiple agenda items. An information processing apparatus connected to a terminal device used by a user via a network and supporting discussion by a plurality of users at a conference, wherein at least one of the information to be discussed at the conference prior to the conference The agenda registration section for registering the agenda and the users who will participate in discussions for each agenda, and if a change in the agenda is accepted, the participating agenda will start for users who will participate in the changed agenda And an agenda processing unit that transmits agenda start information to be provided. [Selection] Figure 3

Description

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

  2. Description of the Related Art A conference support device that supports a conference held by a plurality of users by connecting to a plurality of terminal devices used by the user via a network is known. There is also known a conference support device that transmits an image displayed on an interactive whiteboard installed in a conference room to a terminal device of a remote user via a network. According to such a conference support apparatus, it is possible to provide the content displayed on the interactive whiteboard in the conference room to users at remote locations, so that the discussion can proceed smoothly.

  Patent Document 1 describes a system including a whiteboard device used for a conference and an information processing device that stores drawing data drawn on the whiteboard device. In this system, drawing data can be managed in cooperation between the whiteboard device and the information processing device.

  By the way, a plurality of agenda items may be discussed in a meeting. In such a meeting, there may be a user who participates in discussion on one agenda item but does not participate in discussion on other agenda items.

  However, in the conventional conference support apparatus, even if the agenda includes users who do not participate in the discussion, the processing is performed on the assumption that all the users participate in the discussion. For this reason, it is difficult for the conventional conference support apparatus to participate in the discussion from the middle of the conference or to participate in the discussion at the timing when the discussion related to itself is started. In particular, users who participated in conferences from remote locations had to always check the status of the conference via the terminal device, even when participating in only a part of the agenda, which was inefficient .

  The present invention has been made in view of the above, and an object thereof is to provide an information processing apparatus, a conference system, a method, and a program that can efficiently discuss a plurality of agenda items.

  In order to solve the above-described problems and achieve the object, the present invention is an information processing apparatus that supports a discussion by a plurality of users in a conference by connecting to a terminal device used by a user via a network. Prior to the meeting, at least one agenda to be discussed at the meeting, and an agenda registration unit for registering users to participate in discussions for each agenda, and if an agenda change is accepted, participate in the changed agenda And an agenda processing unit that transmits agenda start information indicating that the participating agenda starts.

  According to the present invention, there is an effect that it is possible to efficiently discuss a plurality of agenda items.

FIG. 1 is a diagram illustrating a conference system according to an embodiment. FIG. 2 is a diagram illustrating a functional configuration of the conference system. FIG. 3 is a diagram illustrating the functional configuration of the conference processing unit together with the information storage unit. FIG. 4 is a diagram illustrating an example of project information. FIG. 5 is a diagram illustrating an example of user information. FIG. 6 is a diagram illustrating an example of device information. FIG. 7 is a diagram illustrating an example of conference information. FIG. 8 is a diagram illustrating an example of agenda information. FIG. 9 is a diagram illustrating an example of file information. FIG. 10 is a diagram illustrating an example of the drawing data information. FIG. 11 is a diagram illustrating an example of action item information. FIG. 12 is a diagram illustrating an example of conclusion information. FIG. 13 is a flowchart showing a process flow of the conference system. FIG. 14 is a sequence diagram illustrating an example of a process flow of the conference system during preparation. FIG. 15 is a diagram illustrating an example of a preparation screen. FIG. 16 is a diagram illustrating an example of the agenda input screen. FIG. 17 is a diagram illustrating an example of a preparation screen including a file icon. FIG. 18 is a diagram illustrating an example of a preparation screen in a state where a file icon is dragged and dropped. FIG. 19 is a sequence diagram showing a flow of processing of the conference system at the start of the conference. FIG. 20 is a diagram illustrating an example of the start screen. FIG. 21 is a diagram illustrating an example of a device conference screen. FIG. 22 is a sequence diagram showing a flow of processing of the conference system at the time of drawing and saving of drawing data. FIG. 23 is a diagram illustrating an example of a device conference screen on which drawing data is displayed. FIG. 24 is a sequence diagram illustrating a process flow of the conference system when changing the agenda. FIG. 25 is a diagram illustrating an example of a device conference screen in a state in which an agenda changing operation is performed. FIG. 26 is a diagram illustrating an example of the device conference screen after changing the agenda. FIG. 27 is a sequence diagram showing a flow of processing of the conference system at the time of file output. FIG. 28 is a diagram illustrating an example of the device conference screen in a state where the file list screen is displayed. FIG. 29 is a diagram illustrating an example of a device conference screen in a state where a file is displayed. FIG. 30 is a sequence diagram illustrating a process flow of the conference system when an action item is input. FIG. 31 is a diagram illustrating an example of the device conference screen in a state where the action item input screen is displayed. FIG. 32 is a sequence diagram showing a flow of processing of the conference system at the time of conclusion input. FIG. 33 is a diagram illustrating an example of the device conference screen in a state where the conclusion input screen is displayed. FIG. 34 is a sequence diagram showing the flow of processing of the conference system at the end of the conference. FIG. 35 is a sequence diagram showing the flow of processing of the conference system after the conference. FIG. 36 is a diagram illustrating an example of the result screen. FIG. 37 is a diagram illustrating an example of a detail screen. FIG. 38 is a diagram illustrating a hardware configuration of the IWB. FIG. 39 is a diagram illustrating a hardware configuration of the terminal device. FIG. 40 is a diagram illustrating a hardware configuration of the conference support apparatus.

  Hereinafter, the conference system 10 according to the embodiment will be described in detail with reference to the drawings. The conference system 10 is a system for supporting discussion by a plurality of users in a conference. For example, the conference system 10 supports communication between a user who participates in a conference in a predetermined place (for example, a conference room in a company) and a user who participates in a conference in a remote location (for example, the home of a telecommuter). To do.

  FIG. 1 is a diagram illustrating a conference system 10 according to the embodiment. The conference system 10 includes a plurality of terminal devices 20 used by each of a plurality of users, an interactive whiteboard (IWB) 22, and a conference support device 30.

  Each of the plurality of terminal devices 20 can be connected to the conference support device 30 via a network. The network is, for example, a LAN (Local Area Network), a VPN (Virtual Private Network), or a WAN (Wide Area Network) in which LANs are connected via a router. The network may include the Internet or a telephone communication line. Further, the network may be configured by wire, or a part or all of the network may be configured by radio.

  The terminal device 20 is a device having an information processing function, an information input function, an information output function, a communication function, and the like. The terminal device 20 may be a general computer such as a notebook type or a desktop type, a tablet terminal, a smartphone, or the like. The terminal device 20 may be a dedicated device for conducting an electronic conference.

  The terminal device 20 accesses the conference support device 30 by executing a predetermined application program. The terminal device 20 outputs information provided from the conference support device 30 using a predetermined application program.

  The terminal device 20 has a microphone and collects voices uttered by a user or the like during a meeting to generate voice data. The terminal device 20 includes a camera, captures a user or the like during a meeting, and generates moving image data. The terminal device 20 transmits the generated audio data and moving image data to the conference support device 30.

  The IWB 22 generates drawing data in response to a user operation on the display using an electronic pen or a hand, and stores the generated drawing data. Then, the IWB 22 displays the generated drawing data on the display. Thereby, the user can draw a character or a figure on IWB22 like drawing a character or a figure using a pen on a wall.

  Furthermore, the IWB 22 has a communication function and can be connected to the conference support apparatus 30 via a network. The IWB 22 accesses the conference support apparatus 30 by executing a dedicated application program, for example. The IWB 22 outputs a screen corresponding to the information provided from the conference support device 30. The IWB 22 operates based on information provided from, for example, a dedicated application program and the conference support apparatus 30.

  Further, the IWB 22 captures an image displayed on the display and generates device image data representing the captured image. For example, the IWB 22 generates device image data each time an image displayed on the display changes. The IWB 22 transmits the generated device image data to the conference support apparatus 30.

  Note that the conference system 10 may include a device other than the IWB 22 as long as it can receive an input operation of characters or graphics and display the input characters or graphics. For example, the conference system 10 may include an information processing apparatus having a large display.

  The conference support apparatus 30 is a computer such as a general server having an information processing function and a communication function. Moreover, the meeting assistance apparatus 30 may be comprised by one server etc., and may be comprised by the some server etc.

  The meeting support device 30 receives access from the plurality of terminal devices 20 and the IWB 22 via the network. Then, the conference support device 30 provides the requested information to each of the plurality of terminal devices 20 and the IWB 22 via the network.

  In addition, the conference support apparatus 30 collects audio data and moving image data from each of the plurality of terminal apparatuses 20 via a network. The conference support apparatus 30 stores the collected audio data and moving image data. Thereby, the meeting assistance apparatus 30 can record a user's voice and moving image during the meeting, and can reproduce them later.

  In addition, the conference support apparatus 30 can transmit the collected audio data and moving image data to the terminal apparatus 20 that has requested acquisition. For example, the conference support apparatus 30 can transmit audio data of a designated channel among the collected audio data of a plurality of channels to the terminal apparatus 20 that has requested acquisition. Further, for example, the conference support apparatus 30 can transmit the moving image data of the designated channel among the collected moving image data of the plurality of channels to the terminal device 20 that has requested acquisition. The terminal device 20 outputs audio data or displays moving image data via a predetermined application program. Thereby, the meeting support apparatus 30 can provide the audio | voice or moving image of a predetermined place (a meeting room etc.) to the user of a remote place, for example.

  Further, the conference support apparatus 30 collects device image data from the IWB 22 via a network. The conference support apparatus 30 stores the collected device image data. Thereby, the conference support apparatus 30 can record the image displayed on the IWB 22 during the conference and display it later.

  In addition, the conference support apparatus 30 transmits the collected device image data to each terminal apparatus 20. The terminal device 20 displays device image data representing an image displayed on the IWB 22 via a predetermined application program. Thereby, the meeting assistance apparatus 30 can provide the image currently displayed on IWB22 to a user, for example.

  Here, in the conference system 10, each of a plurality of users participating in the conference uses one of the terminal devices 20. When the meeting support apparatus 30 receives a login request from the terminal apparatus 20 via the network, the meeting support apparatus 30 authenticates the user who is using the terminal apparatus 20. Thereby, the meeting assistance apparatus 30 can specify the user who is using the terminal device 20.

  The IWB 22 is installed in a predetermined place (for example, a conference room). When the meeting support apparatus 30 receives a login request from the IWB 22 via the network, the meeting support apparatus 30 authenticates the IWB 22. Thereby, the conference support apparatus 30 can specify the IWB 22 and can also specify the meeting place (the installation location of the IWB 22).

  Also, in the conference system 10, prior to the conference, any of direct participation, remote participation, and semi-participation is registered as a participation mode for each user participating in the conference. Direct participation is a participation form registered for a user who participates in a conference at a predetermined location (for example, a conference room) where the IWB 22 is installed.

  Remote participation is a participation form registered for a user who participates in a conference using the terminal device 20 in a place different from a predetermined place. For example, remote participation is registered for a user who works from home and participates in a conference at home or the like.

  The semi-participation is a participation form that is registered for a user who participates in a conference using the terminal device 20 at a place different from a predetermined place for some agenda items in the conference. For example, semi-participation is registered for a user who works from home while raising a child and confirms the contents of the discussion on the agenda related to himself / herself.

  In the conference system 10, non-participation may be included in the participation form. Non-participation is a form of participation that is registered for a user who refers to related information later, but does not participate in the meeting in real time due to sick leave or business trip.

  FIG. 2 is a diagram illustrating a functional configuration of the conference system 10.

  The IWB 22 includes a first communication unit 42, an operation input unit 44, a screen display unit 46, and an image generation unit 48. The IWB 22 functions as a first communication unit 42, an operation input unit 44, a screen display unit 46, and an image generation unit 48, for example, when a processor executes a predetermined application program.

  The first communication unit 42 communicates with the conference support apparatus 30 via a network. The operation input unit 44 receives an input operation on the display by using an electronic pen or a hand. The screen display unit 46 displays information on the display based on the data acquired from the conference support apparatus 30. For example, the screen display unit 46 displays a predetermined screen on the display based on the screen data received from the conference support apparatus 30 via the first communication unit 42. Further, the screen display unit 46 displays characters or figures on the display in accordance with the input operation received by the operation input unit 44. The screen display unit 46 changes the screen displayed on the display in accordance with the input operation received by the operation input unit 44.

  The image generation unit 48 captures an image displayed on the display, and generates device image data representing the image displayed on the display. For example, the image generation unit 48 generates device image data each time an image displayed on the display changes. The first communication unit 42 transmits the device image data generated by the image generation unit 48 to the conference support apparatus 30.

  The terminal device 20 includes a second communication unit 50, a sound collection unit 52, an imaging unit 54, an input unit 56, a display unit 58, and an audio output unit 60. The terminal device 20 functions as the second communication unit 50, the sound collection unit 52, the imaging unit 54, the input unit 56, the display unit 58, and the audio output unit 60, for example, when the processor executes a predetermined application program.

  The second communication unit 50 communicates with the conference support apparatus 30 via the network. The sound collection unit 52 generates sound data representing the surrounding sound based on the sound signal obtained by collecting the surrounding sound. The imaging unit 54 generates moving image data representing an image of a surrounding subject based on an imaging signal obtained by imaging the surrounding subject. The input unit 56 receives user input operations. The second communication unit 50 transmits the generated voice data, the generated moving image data, and user operation information to the conference support apparatus 30.

  The display unit 58 displays information on the display based on the data acquired from the conference support apparatus 30. For example, the display unit 58 displays a predetermined screen on the display based on the screen data received from the conference support apparatus 30 via the second communication unit 50. For example, the display unit 58 displays the moving image data acquired from the conference support apparatus 30 on the display. For example, the display unit 58 displays the device image data representing the image displayed on the IWB 22 acquired from the conference support apparatus 30 on the display. The display unit 58 changes the screen displayed on the display in accordance with the input operation received by the input unit 56. The audio output unit 60 outputs sound corresponding to the audio data received from the conference support apparatus 30 via the second communication unit 50 from the speaker.

  The conference support device 30 includes a third communication unit 62, an information storage unit 64, a device screen providing unit 70, a terminal screen providing unit 72, a device operation receiving unit 74, a terminal operation receiving unit 76, and a device image collection. Unit 78, device image providing unit 80, audio collecting unit 82, audio providing unit 84, moving image collecting unit 86, moving image providing unit 88, and conference processing unit 90. The conference support apparatus 30 includes a third communication unit 62, a device screen providing unit 70, a terminal screen providing unit 72, a device operation receiving unit 74, a terminal operation receiving unit 76, a device, and the like when a processor executes a predetermined application program, for example. It functions as an image collecting unit 78, a device image providing unit 80, an audio collecting unit 82, an audio providing unit 84, a moving image collecting unit 86, a moving image providing unit 88, and a conference processing unit 90.

  The 3rd communication part 62 communicates with IWB22 and each terminal device 20 via a network. The information storage unit 64 stores various screen data used in the conference support apparatus 30 and management data used in the conference.

  The device screen providing unit 70 transmits screen data to the IWB 22 and causes the IWB 22 to display various operation screens. The terminal screen providing unit 72 transmits screen data to each terminal device 20 to display various operation screens on the terminal device 20.

  The device operation reception unit 74 receives operation information from the IWB 22 and receives a user operation on a screen provided to the IWB 22. The terminal operation reception unit 76 receives operation information from the terminal device 20 and receives a user operation on a screen provided to the terminal device 20.

  The device image collection unit 78 collects device image data representing an image displayed on the display of the IWB 22 from the IWB 22. The device image collection unit 78 adds the time stamp or the like to the collected device image data and stores it in the information storage unit 64.

  The device image providing unit 80 transmits the device image data collected by the device image collecting unit 78 to each terminal device 20. Thereby, the apparatus image provision part 80 can display the image displayed on IWB22 on each terminal device 20 during a meeting. When the device image providing unit 80 receives an acquisition request for past device image data from the terminal device 20, the device image providing unit 80 reads out the device image data at the specified time from the information storage unit 64, and requests the requesting terminal device. 20 to send. Thereby, the device image providing unit 80 can display the past image displayed on the IWB 22 on the terminal device 20 after the meeting or during the meeting.

  The sound collection unit 82 collects sound data representing the surrounding sound generated by the sound collection unit 52 of each terminal device 20. The voice collection unit 82 stores the collected voice data in the information storage unit 64 with a time stamp or the like added thereto.

  When the voice providing unit 84 receives a voice data acquisition request from the terminal device 20, the voice providing unit 84 transmits the designated voice data among the voice data collected by the voice collecting unit 82 to the requesting terminal device 20. Thereby, the audio | voice provision part 84 can output the audio | voice collected by one of the terminal devices 20 from the other terminal device 20 during a meeting.

  When the voice providing unit 84 receives a request for acquisition of past voice data from the terminal device 20, the voice providing unit 84 reads the voice data at the specified time from the information storage unit 64 and transmits it to the requesting terminal device 20. To do. Thereby, the audio | voice provision part 84 can output the audio | voice collected by any of the terminal devices 20 in the past after the meeting or during the meeting from the terminal device 20.

  The moving image collection unit 86 collects moving image data representing the moving image collected by the sound collection unit 52 of each terminal device 20. The moving image collection unit 86 stores the collected moving image data in the information storage unit 64 with a time stamp added.

  When receiving the moving image data acquisition request from the terminal device 20, the moving image providing unit 88 transmits the specified moving image data among the moving image data collected by the moving image collection unit 86 to the terminal device 20. Thereby, the moving image providing unit 88 can cause the moving image captured by any one of the terminal devices 20 to be output from the other terminal devices 20 during the conference.

  Further, when the moving image providing unit 88 receives an acquisition request for past moving image data from the terminal device 20, the moving image providing unit 88 reads out the moving image data at the designated time from the information storage unit 64, and requests the requesting terminal device. 20 to send. Accordingly, the moving image providing unit 88 can output past moving images from the terminal device 20 after or during the meeting.

  The conference processing unit 90 executes a process related to the conference in response to a request from the IWB 22 or the terminal device 20.

  FIG. 3 is a diagram illustrating the functional configuration of the conference processing unit 90 together with the information storage unit 64.

  The information storage unit 64 stores project information, user information, device information, conference information, agenda information, file information, drawing data information, action item information, and conclusion information as management information related to the conference. Such information will be described later with reference to FIGS. 4 to 12.

  The conference processing unit 90 includes a preparation unit 102, a progression unit 104, and a result providing unit 106. The preparation unit 102 performs processing related to preparation before the meeting. The progress unit 104 performs processing related to progress during the conference. The result providing unit 106 provides a result and the like after the meeting.

  The preparation unit 102 includes a user registration unit 110, a conference registration unit 112, an agenda registration unit 114, a participation form registration unit 116, and a file registration unit 118.

  Prior to the conference, the user registration unit 110 registers user information including information about users who can participate in the conference in the information storage unit 64 in accordance with an instruction from the terminal device 20. Prior to the conference, the conference registration unit 112 registers conference information including information related to the conference in the information storage unit 64 in accordance with an instruction from the terminal device 20. Prior to the meeting, the agenda registration unit 114 stores at least one agenda to be discussed in the meeting and agenda information including users who participate in the discussion for each agenda in accordance with an instruction from the terminal device 20. Register with.

  Prior to the meeting, the participation form registration unit 116 registers the participation form in the information storage unit 64 for each user participating in the meeting in accordance with an instruction from the terminal device 20. Specifically, the participation form registration unit 116 registers, for each user, whether to participate in the conference according to any participation form of direct participation, remote participation, or semi-participation. Furthermore, the participation form registration unit 116 may register non-participation as a participation form for any user.

  Prior to the meeting, the file registration unit 118 registers file information including the file to be displayed on the IWB 22 and the file creator in the information storage unit 64 in accordance with an instruction from the terminal device 20.

  The progression unit 104 includes a start notification unit 120, an agenda processing unit 122, a file processing unit 124, a drawing data processing unit 126, an action item generation unit 128, a conclusion generation unit 130, and an end processing unit 132. .

  The start notification unit 120 transmits start screen data to the IWB 22 when the meeting start time is reached, and notifies the start of the meeting.

  The agenda processing unit 122 executes processing related to the agenda currently under discussion among the agendas registered in advance during the conference. The agenda processing unit 122 executes processing related to the first agenda immediately after the start of the conference. Thereafter, when a predetermined operation is performed on the IWB 22, the agenda processing unit 122 next changes the agenda currently under discussion.

  When the agenda change is accepted during the meeting, the agenda processing unit 122 transmits agenda start information indicating that the participating agenda starts to the user who participates in the changed agenda. In this case, the agenda processing unit 122 may transmit agenda start information to all users who participate in the started agenda. Instead of this, the agenda processing unit 122 may transmit agenda start information to users who participate in the agenda by semi-participation among users who participate in the started agenda. Thereby, the agenda process part 122 can make the user who participates in an agenda by semi-participation perform other work in periods other than the agenda relevant to self.

  The file processing unit 124 acquires a registered file and transmits it to the IWB 22 in response to a request from the IWB 22 while any agenda in the conference is in progress. As a result, the file processing unit 124 can cause the IWB 22 to output a file registered in advance.

  Furthermore, when the file processing unit 124 outputs a file to the IWB 22 while any agenda in the meeting is in progress, the file processing unit 124 transmits file output information indicating that the file has been output to the file creator. In this case, the file processing unit 124 may transmit file output information to the creator who participates in the agenda by semi-participation. As a result, the file processing unit 124 allows a user who participates in the agenda by semi-participation to participate in the discussion when the discussion about the file created by the user is started, and to perform other work in other periods.

  The drawing data processing unit 126 receives a drawing data storage request and drawing data from the IWB 22 while any agenda of the meeting is in progress. When the drawing data processing unit 126 receives a drawing data storage request and drawing data from the IWB 22, the drawing data processing unit 126 generates drawing data information including drawing data and information for specifying the current agenda, and the generated drawing data information is stored in the information storage unit. 64 is stored.

  The action item generation unit 128 receives an instruction to generate action item information from the IWB 22 while any agenda of the meeting is in progress. The action item information is information describing an action to be performed by the user.

  The action item generation unit 128 represents the sound collected during the first operation, which is a predetermined operation for the IWB 22, when generation of action item information is instructed while any agenda of the meeting is in progress. The first voice data and the person-in-charge information indicating the person in charge in charge of the action item are acquired from the IWB 22. Then, the action item generation unit 128 generates action item information including the acquired first voice data, person-in-charge information, and information for specifying the current agenda, and stores the generated action item information in the information storage unit 64.

  Furthermore, the action item generation unit 128 may acquire first device image data representing an image displayed on the IWB 22 during the first operation. Then, the action item generation unit 128 may generate action item information that further includes the first device image data.

  Further, the action item generation unit 128 may acquire first text data obtained by converting the first audio data into text, and may generate action item information further including the acquired first text data. In this case, the action item generation unit 128 may have a voice recognition function, and may generate first text data from the first voice data using the voice recognition function. Further, in this case, the action item generation unit 128 may acquire the first text data converted into text from the voice recognition server by transmitting the first voice data to an external voice recognition server.

  The conclusion generation unit 130 receives an instruction to generate a conclusion from the IWB 22 while any agenda of the meeting is in progress. The conclusion generation unit 130 is a second sound representing the sound collected during the second operation, which is a predetermined operation for the IWB 22 when generation of a conclusion is instructed while any agenda of the meeting is in progress. Data is acquired from the IWB 22. Then, the conclusion generation unit 130 generates conclusion information including the acquired second audio data and information for specifying the current agenda, and stores the generated conclusion information in the information storage unit 64.

  Furthermore, the conclusion generation unit 130 may acquire second device image data representing an image displayed on the IWB 22 during the second operation. And the conclusion production | generation part 130 may produce | generate the conclusion information which further contains 2nd apparatus image data.

  Furthermore, the conclusion generation unit 130 may acquire second text data obtained by converting the second audio data into text, and may generate conclusion information further including the acquired second text data. In this case, the conclusion generation unit 130 may have a voice recognition function, and may generate second text data from the second voice data using the voice recognition function. In this case, the conclusion generation unit 130 may acquire the second text data that has been converted into text from the voice recognition server by transmitting the second voice data to an external voice recognition server.

  The end processing unit 132 receives a conference end instruction from the IWB 22 while the conference is in progress. If the end processing unit 132 receives a conference end instruction while the conference is in progress, the end processing unit 132 performs a conference end process. For example, the end processing unit 132 gives a data erasure instruction to the IWB 22. Receiving the data erasure instruction, the IWB 22 erases the stored file, drawing data, and the like.

  The result providing unit 106 receives selection of information related to the past conference from the terminal device 20 used by any user after the conference is ended. When the result providing unit 106 receives information regarding past conferences after the conference is completed, the result providing unit 106 reads out the action item information and the conclusion information generated in the conference from the information storage unit 64. Then, the result providing unit 106 causes the terminal device 20 to display a result screen including at least one of action item information and conclusion information generated in the meeting.

  Further, in this case, the result providing unit 106 displays the action item information in which the user who uses the terminal device 20 is the person in charge at the upper level. For example, the result providing unit 106 displays action item information whose user who uses the terminal device 20 is a person in charge on the upper side of the display of the terminal device 20.

  FIG. 4 is a diagram illustrating an example of project information. The project information is information regarding the project. A project is a unit that controls one or more meetings. Under one project, multiple users hold one or more meetings.

  The project information includes a project account and a project name. The project account is identification information for identifying a project. The project name is the name of the project.

  FIG. 5 is a diagram illustrating an example of user information. The user information is information regarding users who can participate in the conference.

  The user information includes a project account, a user ID, a user name, and contact information. The project account is information for identifying the project to which the user belongs. For example, a user may be able to participate in a conference that takes place under the project to which he belongs. The user ID is information for identifying the user. The user name is the name of the user. The contact information is an address for transmitting information from the conference support apparatus 30 to the user. The contact information may be, for example, an e-mail address, a social network service account, or a telephone number.

  FIG. 6 is a diagram illustrating an example of device information. The device information is information regarding devices that can be used for the conference. A device that can be used for the conference is, for example, the IWB 22.

  The device information includes a device ID and an installation location. The device ID is identification information for identifying a device. The installation location is a location where equipment is installed.

  FIG. 7 is a diagram illustrating an example of conference information. The meeting information is information related to the meeting.

  The conference information includes a project account, a conference account, a device ID, a date and time, a conference name, participants, and a facilitator name. The project account is information for identifying the project to which the conference belongs. The conference account is information for identifying a conference. The device ID is information for identifying a device used in the conference. The date and time is the date and time when the meeting is held. The conference support apparatus 30 can specify the location of the conference from the device ID.

  The meeting name is the name of the meeting. Participants are users who participate in the conference. The participant also includes a participation form. The facilitator name is the conference facilitator.

  FIG. 8 is a diagram illustrating an example of agenda information. The agenda information is information relating to the agenda.

  The agenda information includes a conference account, an agenda number, an agenda name, detailed information, a schedule, and participants. The conference account is information for identifying the conference to which the agenda belongs. The agenda number is a value indicating the progression order of the agenda items. The agenda numbers are assigned in ascending order from 1 for example.

  The agenda name is the name of the agenda. The detailed information is a text representing the content to be discussed on the agenda. The schedule is a period for discussing the agenda. Participants are users who participate in discussions on the agenda.

  FIG. 9 is a diagram illustrating an example of file information. The file information is information for managing files to be output at the conference.

  The file information includes a conference account, an agenda number, a creator, and a file link destination. The conference account is information for identifying a conference that uses a file. The agenda number is a number for identifying an agenda scheduled to use the file. The creator is the creator of the file. The file link destination is an address where the file is stored. Note that the file may be stored in an external server other than the conference support apparatus 30.

  FIG. 10 is a diagram illustrating an example of the drawing data information. The drawing data information is information for managing drawing data created during the meeting.

  The drawing data information includes a conference account, an agenda number, a creation date and time, and a drawing data link destination. The conference account is information for identifying the conference that created the drawing data. The agenda number is a number for identifying the agenda for which drawing data has been created. The creation date and time is the date and time when drawing data was created. The drawing data link destination is an address where drawing data is stored. The drawing data may be stored in an external server other than the conference support apparatus 30.

  FIG. 11 is a diagram illustrating an example of action item information. The action item information is information describing an action to be performed by the user.

  The action item information includes a conference account, an agenda number, a person in charge, a time limit, a voice data link destination, text data, an image data link destination, and a creation date and time.

  The conference account is information for identifying the conference that generated the action item information. The agenda number is a number that identifies the agenda that generated the action item information. The person in charge is a user who acts. The deadline is the date and time when the user should complete the action.

  The voice data link destination is an address where the first voice data indicating the content of the action to be performed by the user is stored. The first audio data may be stored in an external server other than the conference support apparatus 30.

  The text data is first text data obtained by converting the first voice data into text. That is, the text data is first text data indicating the content of the action to be performed by the user. The image data link destination is an address at which first device image data representing an image displayed on the device (IWB 22) during recording of the first audio data is stored. The first device image data may be stored in an external server other than the conference support apparatus 30. The creation date / time is the date / time when the action item information is created.

  FIG. 12 is a diagram illustrating an example of conclusion information. The conclusion information is information describing the conclusion of the discussion.

  The conclusion information includes a conference account, an agenda number, an audio data link destination, text data, an image data link destination, and a creation date and time.

  The conference account is information for identifying the conference that generated the conclusion information. The agenda number is a number that identifies the agenda that generated the conclusion information.

  The voice data link destination is an address where the second voice data indicating the content of the conclusion is stored. The second audio data may be stored in an external server other than the conference support apparatus 30.

  The text data is second text data obtained by converting the second voice data into text. That is, the text data is second text data indicating the content of the conclusion. The image data link destination is an address at which second device image data representing an image displayed on the device (IWB 22) during recording of the second audio data is stored. The second device image data may be stored in an external server or the like other than the conference support apparatus 30. The creation date / time is the date / time when the conclusion information is created.

  FIG. 13 is a flowchart showing a flow of processing of the conference system 10 according to the embodiment. The conference system 10 executes processing according to the flow shown in FIG.

  First, the conference system 10 executes conference preparation processing prior to the conference (S211). Specifically, the conference system 10 generates and registers conference information and agenda information in the preparation process. Furthermore, the conference system 10 may acquire a file used for the conference and generate and register file information in the preparation process.

  Next, the conference system 10 performs conference support processing during the conference (S212). For example, the conference system 10 transmits conference start information to a device (for example, IWB 22) when the conference start time is reached. Further, for example, the conference system 10 generates and records audio data, moving image data, and device image data during the conference. Furthermore, the conference system 10 manages the progress of each agenda item during the conference. Specifically, when the agenda is started, the conference system 10 transmits agenda start information to the participants. In addition, the conference system 10 performs drawing data storage processing and file output for each agenda item. In addition, the conference system 10 generates and stores action item information and conclusion information for each agenda item.

  Subsequently, the conference system 10 executes a process for providing information related to the conference after the conference is over (S213). For example, the conference system 10 provides audio data, moving image data, and device image data recorded during the conference to users who have participated in the conference. Furthermore, the conference system 10 provides action item information and conclusion information generated in the conference to users who have participated in the conference.

  As described above, the conference system 10 executes processing in three stages before, during, and after the conference.

  FIG. 14 is a sequence diagram illustrating an example of a process flow of the conference system 10 during preparation. The conference system 10 executes processing in accordance with the flow shown in FIG.

  First, the facilitator performs a login operation to the conference support device 30 using the terminal device 20. When the login operation is performed, the terminal device 20 of the facilitator transmits login information to the conference support device 30 (S221). When the authentication of the facilitator is successful, the conference support device 30 transmits the preparation screen data to the terminal device 20 of the facilitator (S222). When receiving the preparation screen data, the terminal device 20 of the facilitator displays a preparation screen 510 (details will be described later) (S223).

  Subsequently, the facilitator operates the preparation screen 510 to input conference information including a conference name, participants, devices to be used, date and time of holding, and the like. Subsequently, the terminal device 20 of the facilitator transmits information such as the input conference name to the conference support device 30 (S224). When the conference support device 30 receives the input information such as the conference name, the conference support device 30 generates and registers conference information based on the received information (S225).

  Subsequently, the facilitator inputs information related to the agenda to be discussed in the conference, such as the agenda name. Subsequently, the terminal device 20 of the facilitator transmits information such as the input agenda name to the conference support device 30 (S226). When the meeting support apparatus 30 receives the input information such as the agenda name, it generates agenda information based on the received information and registers it (S227). When a plurality of agenda items are discussed in the meeting, the facilitator inputs information such as the agenda name for each agenda item. Then, the terminal device 20 and the conference support device 30 of the facilitator repeat the processes of S226 and S227 for each agenda item.

  When the conference information and at least one agenda information are registered, the user can access the conference information and the agenda information registered using the terminal device 20.

  First, the user performs a login operation to the conference support device 30 using the terminal device 20. When the login operation is performed, the user terminal device 20 transmits the login information to the conference support device 30 (S228). When the user authentication is successful, the conference support device 30 transmits the preparation screen data to the terminal device 20 of the user (S229). When receiving the preparation screen data, the user terminal device 20 displays the preparation screen 510 (S230).

  By operating the preparation screen 510, the user can input his / her participation form in the conference. When the participation form is input by the user, the user's terminal device 20 transmits the participation form to the conference support apparatus 30 (S231). Upon receiving the participation form, the meeting support apparatus 30 registers the user's participation form in the conference information (S232).

  In addition, the user can input the agenda to participate by operating the preparation screen 510. When the agenda to participate is input by the user, the user terminal device 20 transmits the number of the agenda to participate to the conference support apparatus 30 (S233). Upon receiving the participating agenda number, the conference support apparatus 30 registers the user as a participant of the corresponding agenda information (S234).

  Further, the user can transmit a file used for the conference by operating the preparation screen 510. When a file transmission operation is performed by the user, the user terminal device 20 transmits the file to the conference support apparatus 30 (S235). When the meeting support apparatus 30 receives the file, the meeting support apparatus 30 saves the received file in a predetermined storage area and generates and registers file information (S236). The meeting support apparatus 30 may store the file on an external server or the like.

  Subsequently, the user can associate the file used for the meeting with any agenda by operating the preparation screen 510. When the user performs an operation for associating the file with the agenda, the user's terminal device 20 transmits the agenda number using the file to the conference support device 30 (S237). Upon receiving the agenda number, the conference support apparatus 30 updates the corresponding file information (S238).

  The information input procedure at the time of conference preparation shown in FIG. 14 is an example. The conference support apparatus 30 can accept various types of information other than the order shown in FIG. Note that the conference support device 30 may accept an operation performed by each user from the terminal device 20 of the facilitator.

  As described above, according to the conference support apparatus 30, it is possible to register conference information related to the conference, agenda items discussed in the conference, participants, and files used in the conference prior to the conference. Thereby, according to the meeting assistance apparatus 30, a meeting can be advanced efficiently.

  FIG. 15 is a diagram illustrating an example of the preparation screen 510. When the user performs a login operation from the terminal device 20, the conference support device 30 transmits the preparation screen data to the terminal device 20 and causes the terminal device 20 to display a preparation screen 510 as illustrated in FIG. 15.

  The preparation screen 510 includes, for example, a project area 512, a meeting information area 514, a user information area 516, and an agenda information area 518.

  A project name is displayed in the project area 512. In the project area 512, one or more conference buttons 520 are displayed. The conference button 520 is a button for selecting a past conference or a conference to be held belonging to the project. When any conference button 520 is selected, information on the corresponding conference is displayed in the conference information area 514, the user information area 516, and the agenda information area 518.

  In addition, a conference addition button 522 is displayed in the project area 512. The facilitator presses the conference addition button 522 when holding a new conference. When the conference addition button 522 is pressed, the conference support apparatus 30 generates new conference information and displays the conference button 520 corresponding to the new conference in the project area 512.

  In the meeting information area 514, meeting information about the meeting selected in the project area 512 is displayed. For example, in the conference information area 514, the conference name, date and time, and venue are displayed. The holding place is a place where a device (for example, IWB 22) used in the conference is installed.

  For example, the facilitator can newly input or change information displayed in the conference information area 514. The conference support apparatus 30 updates the conference information when information displayed in the conference information area 514 is newly input or changed.

  In the user information area 516, information related to users participating in the conference is displayed. For example, the user information area 516 includes a user individual area 524 for each user participating in the conference. In each user individual area 524, an icon such as a face of the target user, a user name of the target user, a participation form of the target user, and an agenda in which the target user participates are displayed.

  For example, the target user or facilitator can change the participation mode displayed in the user individual area 524. When the participation form displayed in the user individual area 524 is changed, the conference support apparatus 30 updates the participation form of the participant in the conference information.

  Further, for example, the target user or facilitator can newly input or change the agenda to be displayed displayed in the user individual area 524. When the agenda to be displayed displayed in the user individual area 524 is newly input or changed, the conference support apparatus 30 updates the participants in the corresponding agenda information.

  In the agenda information area 518, information related to the agenda discussed in the conference is displayed. For example, the agenda information area 518 includes an agenda individual area 526 for each agenda discussed in the meeting. In each agenda individual area 526, the number, detailed information, and schedule of the target agenda are displayed.

  For example, the facilitator can press the agenda individual area 526. When any one of the agenda individual areas 526 is pressed, the conference support apparatus 30 displays an agenda input screen 530 (details will be described later). The facilitator can newly input or change information on the agenda for the agenda individual area 526.

  An agenda information button 528 is displayed in the agenda information area 518. The facilitator presses the agenda addition button 528 when adding a new agenda. When the agenda addition button 528 is pressed, the conference support apparatus 30 generates new agenda information and forms a new agenda individual area 526 in the agenda information area 518.

  FIG. 16 is a diagram illustrating an example of the agenda input screen 530. When the agenda individual area 526 shown in FIG. 15 is pressed or the add agenda button 528 shown in FIG. 15 is pressed, the conference support device 30 transmits the agenda input screen data to the terminal device 20, An agenda input screen 530 as shown in FIG. 16 is displayed on the terminal device 20.

  On the agenda input screen 530, the agenda name, detailed information, file, and schedule are displayed. The file indicates a file used in the agenda. The facilitator can input or change the agenda name, detailed information, file, and schedule by operating the agenda input screen 530. When such information is input or changed by the facilitator, the conference support apparatus 30 updates the corresponding agenda information.

  FIG. 17 is a diagram illustrating an example of a preparation screen 510 including a file icon 532. A facilitator or a user can use the terminal device 20 to transmit a file used for the conference to the conference support device 30. Further, when the facilitator or the user transmits a file to the conference support device 30, the file creator is registered using the terminal device 20. Then, when receiving the file and the creator of the file, the conference support apparatus 30 stores the file in a predetermined storage area and generates file information related to the file.

  In the user information area 516 on the preparation screen 510, a file icon 532 indicating the existence of a file is displayed. In this case, the file icon 532 is displayed in the user individual area 524 of the file creator. Thereby, the meeting assistance apparatus 30 can make a user recognize the creator of a file.

  FIG. 18 is a diagram showing an example of the preparation screen 510 in a state where the file icon 532 is dragged and dropped.

  The facilitator or the user can move the file icon 532 displayed in the user individual area 524 to any one of the agenda individual areas 526 by drag and drop. When the file icon 532 is moved to any one of the agenda individual areas 526, the meeting support apparatus 30 uses the file indicated by the file icon 532 as a file corresponding to the agenda corresponding to the destination agenda individual area 526. As a result, the file information is updated. Thereby, the meeting assistance apparatus 30 can receive registration of the agenda which uses a file.

  FIG. 19 is a sequence diagram showing the flow of processing of the conference system 10 at the start of the conference. FIG. 20 is a diagram illustrating an example of the start screen 540. The conference system 10 executes processing in the flow shown in FIG. 19 at the start of the conference.

  First, the conference support apparatus 30 determines whether or not it is a conference start time (S241). When the meeting start time comes, the meeting support apparatus 30 transmits start screen data to the IWB 22 registered as a device used for the meeting (S242). When the IWB 22 receives the start screen data, for example, the IWB 22 displays a start screen 540 as shown in FIG. 20 (S243). The start screen 540 displays the project name of the project to which the conference belongs, the conference name, the date and place of the conference, and the like.

  When starting a conference, any user performs a predetermined start operation on the start screen 540 displayed on the IWB 22 (S244). For example, the user presses a start button or the like displayed on the start screen 540. When a predetermined operation is performed, the IWB 22 transmits a start instruction to the conference support apparatus 30 (S245).

  When receiving the start instruction, the conference support apparatus 30 transmits the device conference screen data to the IWB 22 (S246). When receiving the device conference screen data, the IWB 22 displays a device conference screen 550 (details will be described later) for supporting the progress of the conference (S247).

  In addition, when receiving the start instruction, the conference support device 30 transmits the terminal conference screen data to each terminal device 20 used by the user participating in the conference (S248-1 and S248-2). Upon receiving the terminal conference screen data, each terminal device 20 displays a terminal conference screen for supporting the progress of the conference (S249-1 and S249-2).

  Subsequently, the conference support device 30 receives the recording of the audio data and the moving image data transmitted from each terminal device 20, and starts the recording (S250). Further, the conference support apparatus 30 receives device image data representing an image displayed on the IWB 22 and starts recording.

  Thereafter, the conference system 10 supports the progress of the discussion for each agenda according to the operation on the device conference screen 550 displayed on the IWB 22.

  FIG. 21 is a diagram showing an example of the device conference screen 550. When the conference is started, the IWB 22 displays a device conference screen 550 as shown in FIG. 21, for example.

  For example, the device conference screen 550 includes a drawing button 561, a save button 562, a next agenda button 563, a previous agenda button 564, a file button 565, an action item button 566, a conclusion button 567, a setting button 568, and a user button 569. Is displayed. These buttons are buttons for operation. The device conference screen 550 may display other operation buttons. In addition, the device conference screen 550 may not be displayed by default, but a part of the buttons may be displayed when a predetermined operation is performed.

  The drawing button 561 is pressed when drawing in the work area of the device conference screen 550. A save button 562 is pressed to save drawing data in the work area.

  The next agenda button 563 is pressed to advance the agenda. The previous agenda button 564 is pressed when returning the agenda to the previous one.

  The file button 565 is pressed when outputting a file. The action item button 566 is pressed when generating action item information. The conclusion button 567 is pressed when generating conclusion information.

  A setting button 568 is pressed when confirming and changing various settings. The user button 569 is pressed when confirming the status of the participant.

  FIG. 22 is a sequence diagram showing a processing flow of the conference system 10 at the time of drawing and saving of drawing data. FIG. 23 is a diagram illustrating an example of the device conference screen 550 on which drawing data is displayed.

  For example, the user can draw characters, graphics, and the like in the work area of the device conference screen 550 by pressing a drawing button 561 as shown in FIG. The IWB 22 displays characters and figures drawn by pressing the drawing button 561 in the work area of the device conference screen 550. When storing drawing data representing drawn characters, graphics, and the like, the conference system 10 executes processing according to the flow shown in FIG.

  First, the IWB 22 accepts a save operation (S261). For example, the IWB 22 accepts a pressing operation of the save button 562. When the save operation is accepted, the IWB 22 generates drawing data representing characters and graphics drawn in the work area of the device conference screen 550 and transmits the drawing data to the conference support apparatus 30 (S262).

  Subsequently, the conference support apparatus 30 stores the received drawing data in a predetermined storage area (S263). Subsequently, the conference support apparatus 30 specifies the current agenda (S264). Subsequently, the conference support apparatus 30 registers drawing data information including the agenda number, the creation date and time, and the drawing data link destination (S265).

  As described above, the conference system 10 can store the drawing data representing the characters, figures, and the like drawn at the time of examining the agenda, corresponding to the agenda.

  FIG. 24 is a sequence diagram showing the flow of processing of the conference system 10 when changing the agenda. FIG. 25 is a diagram illustrating an example of the device conference screen 550 in a state where an agenda changing operation is performed. FIG. 26 is a diagram illustrating an example of the device conference screen 550 after changing the agenda.

  The conference support apparatus 30 sets the agenda of the agenda number 1 immediately after the conference is started. Thereafter, the conference support apparatus 30 changes the agenda each time an agenda change operation (for example, a press operation of the next agenda button 563 or a press operation of the previous agenda button 564) is performed. When changing the agenda, the conference system 10 executes processing in the flow shown in FIG.

  First, the IWB 22 accepts an agenda change operation (S271). For example, as shown in FIG. 25, the IWB 22 accepts a pressing operation of the next agenda button 563 or a pressing operation of the previous agenda button 564. When the agenda change operation is accepted, the IWB 22 switches the display of the work area on the device conference screen 550 as shown in FIG. 26 (S272). Thereby, the IWB 22 can change the display content of the work area for each agenda item.

  Subsequently, the IWB 22 transmits an agenda number indicating the changed agenda to the conference support apparatus 30 (S273). Subsequently, the conference support device 30 identifies participants who participate in the changed agenda (S274). Subsequently, the conference support device 30 transmits the agenda start information to the terminal device 20 used by the participants who participate in the changed agenda (S275). Thereby, the conference system 10 can notify the participant that discussion of the agenda has started each time the agenda is started or changed.

  Moreover, the meeting assistance apparatus 30 may transmit agenda start information with respect to the user who participates in the agenda by semi-participation among the participants who participate in the agenda. Thereby, the conference system 10 can notify the user who participates in the discussion on the agenda related to the user that the discussion on the agenda related to the user has started.

  FIG. 27 is a sequence diagram showing the flow of processing of the conference system 10 when outputting a file. FIG. 28 is a diagram showing an example of the device conference screen 550 in a state where the file list screen 580 is displayed. FIG. 29 is a diagram showing an example of the device conference screen 550 in a state where a file is displayed.

  Prior to the conference, the conference support apparatus 30 registers files used for the conference. When outputting the file, the conference system 10 executes the process according to the flow shown in FIG.

  First, the IWB 22 accepts a file output operation (S281). For example, the IWB 22 accepts pressing of the file button 565. When the file output operation is accepted, the IWB 22 displays a file list screen 580 as shown in FIG. 28 (S282). The file list screen 580 displays file names indicating files that can be output. The file list screen 580 may display file names collectively for each associated agenda item. The user can select a file to be output by selecting a file name displayed on the file list screen 580.

  Subsequently, the IWB 22 accepts selection of a file to be output (S283). For example, the IWB 22 accepts selection of any one of the file names displayed on the file list screen 580.

  When receiving the selection of the file to be output, the IWB 22 transmits the file name of the file to be output (S284). When the file name is received, the conference support apparatus 30 reads the file corresponding to the file name from the storage area where the file is stored (S285). Subsequently, the conference support apparatus 30 transmits the read file to the IWB 22 (S286). Subsequently, the IWB 22 outputs the received file (S287). For example, the IWB 22 displays the received file in the work area of the device conference screen 550 as shown in FIG. Thereby, IWB22 can show a file to the user who has participated in the meeting.

  Further, the conference support apparatus 30 identifies the creator of the output file (S288). Subsequently, the conference support device 30 transmits file output information to the terminal device 20 used by the creator (S289). Thereby, every time a file is output, the conference system 10 can notify the creator of the file that a discussion with reference to the file has started.

  In addition, the conference support device 30 may transmit the agenda start information when the file creator is participating in the conference by semi-participation. Thereby, the conference system 10 can notify the user who participates in the discussion on the agenda related to the user that the discussion on the file related to the user has started.

  FIG. 30 is a sequence diagram illustrating a process flow of the conference system 10 when an action item is input. FIG. 31 is a diagram showing an example of the device conference screen 550 in a state where the action item input screen 590 is displayed.

  The conference system 10 generates action item information for each behavior when the behavior to be performed after the conference is determined by discussion. When generating the action item information, the conference system 10 executes the process according to the flow shown in FIG.

  First, the IWB 22 accepts an action item information generation operation (S291). For example, the IWB 22 accepts a pressing operation of the action item button 566.

  When receiving the action item information generation operation, the IWB 22 displays an action item input screen 590 as shown in FIG. 31 (S292). The action item input screen 590 displays a person-in-charge input box 591, a time limit input box 592, a first voice recording button 593, a first OK button 594, and a first cancel button 595.

  Subsequently, the IWB 22 receives an input of a person in charge who should execute the action (S293). For example, the IWB 22 accepts input of a person-in-charge name in the person-in-charge input box 591.

  Subsequently, the IWB 22 receives an input of a time limit for completing the action (S294). For example, the IWB 22 receives an input of a time limit in the time limit input box 592.

  Subsequently, the IWB 22 accepts voice input and generates and records first voice data representing the input voice (S295, S296). For example, the IWB 22 accepts an input of audio during a period in which the first audio recording button 593 is pressed, and generates first audio data representing the input audio. Thereby, IWB22 can provide the content of the action which should be performed with an audio | voice. Further, the IWB 22 captures an image displayed on the IWB 22 during a period in which the first audio recording button 593 is pressed, and generates first device image data representing the image displayed on the IWB 22. To do. Thereby, IWB22 can include the image currently displayed on IWB22 in the content of the action which should be performed in addition to an audio | voice.

  The IWB 22 may accept the processes of S293, S294, and S295 (S296) in any order.

  Subsequently, the IWB 22 performs voice recognition processing on the recorded first voice data, and generates first text data representing the content of the utterance included in the first voice data (S297). The IWB 22 may acquire the first text data by transmitting the first voice data to the conference support apparatus 30 or the voice recognition server. Further, the IWB 22 may display the obtained first text data on the action item input screen 590. Thereby, the IWB 22 can check whether the recognition result is correct, and can correct the recognition result if the recognition result is incorrect.

  Subsequently, the IWB 22 accepts a creation operation (S298). For example, the IWB 22 accepts pressing of the first OK button 594. The IWB 22 ends the generation of the action item information when the first cancel button 595 is pressed.

  Subsequently, the IWB 22 transmits the input person in charge, the input deadline, the recorded first voice data, the recognized first text data, and the recorded first device image data to the conference support apparatus 30 (S299). . Subsequently, the conference support apparatus 30 stores the received first audio data and first device image data in a predetermined storage area (S300).

  Subsequently, the conference support device 30 identifies the current agenda (S301). Subsequently, the conference support apparatus 30 registers action item information (S302). The action item information includes the agenda number, the person in charge, the time limit, the voice data link destination indicating the address of the first voice data, the first text data, the image data link destination indicating the address of the first device image data, and the creation date and time. It is.

  As described above, the conference system 10 can generate, for each agenda, action item information indicating actions to be performed after the conference. Thereby, according to the meeting system 10, the action which each user should perform after a meeting can be made to recognize reliably.

  FIG. 32 is a sequence diagram showing a flow of processing of the conference system 10 at the time of conclusion input. FIG. 33 is a diagram illustrating an example of the device conference screen 550 in a state where the conclusion input screen 600 is displayed.

  The conference system 10 generates conclusion information when the conclusion of the agenda is determined through discussion. When generating the conclusion information, the conference system 10 executes the process according to the flow shown in FIG.

  First, the IWB 22 accepts a conclusion information generation operation (S311). For example, the IWB 22 accepts a pressing operation of the conclusion button 567.

  When receiving the conclusion information generation operation, the IWB 22 displays a conclusion input screen 600 as shown in FIG. 33 (S312). On the conclusion input screen 600, a second sound recording button 601, a text display box 602, a second OK button 603, and a second cancel button 604 are displayed.

  Subsequently, the IWB 22 accepts voice input, and generates and records second voice data representing the input voice (S313, S314). For example, the IWB 22 accepts voice input during a period in which the second voice recording button 601 is pressed, and generates second voice data representing the input voice. Thereby, IWB22 can provide the content of the conclusion with an audio | voice. Further, the IWB 22 captures an image displayed on the IWB 22 during a period in which the second sound recording button 601 is pressed, and generates second device image data representing the image displayed on the IWB 22. To do. Thereby, IWB22 can include the image currently displayed on IWB22 in the content of a conclusion in addition to an audio | voice.

  Subsequently, the IWB 22 performs voice recognition processing on the recorded second voice data, and generates second text data representing the content of the utterance included in the second voice data (S315). The IWB 22 may acquire the second text data by transmitting the second voice data to the conference support apparatus 30 or the voice recognition server. Subsequently, the IWB 22 displays the obtained second text data in the text display box 602 (S316). Thereby, the IWB 22 can check whether the recognition result is correct, and can correct the recognition result if the recognition result is incorrect.

  Subsequently, the IWB 22 accepts a creation operation (S317). For example, the IWB 22 accepts pressing of the second OK button 603. Note that the IWB 22 ends the generation of the conclusion information when the second cancel button 604 is pressed.

  Subsequently, the IWB 22 transmits the recorded second audio data, the recognized second text data, and the recorded second device image data to the conference support apparatus 30 (S318). Subsequently, the conference support apparatus 30 stores the received second audio data and second device image data in a predetermined storage area (S319).

  Subsequently, the conference support device 30 identifies the current agenda (S320). Subsequently, the conference support apparatus 30 registers conclusion information (S321). The conclusion information includes the agenda number, the audio data link destination indicating the address of the second audio data, the second text data, the image data link destination indicating the address of the second device image data, and the creation date and time.

  As described above, the conference system 10 can generate conclusion information indicating a conclusion determined by discussion for each agenda item. Thereby, according to the conference system 10, the conclusion about each agenda can be reliably recognized after a meeting.

  FIG. 34 is a sequence diagram showing the flow of processing of the conference system 10 at the end of the conference. The conference system 10 executes processing in the flow shown in FIG. 34 at the end of the conference.

  When ending the conference, one of the users performs an end operation on the device conference screen 550 displayed on the IWB 22 (S331). When the termination operation is performed, the IWB 22 transmits a termination instruction to the conference support apparatus 30 (S332).

  When the meeting support device 30 receives the end instruction, the conference support device 30 ends the recording of the audio data and the moving image data transmitted from each terminal device 20 (S333). In addition, the conference support device 30 ends the recording of the device image data.

  Subsequently, the conference support apparatus 30 transmits end information to the IWB 22 (S334). Upon receiving the end information, the IWB 22 deletes the stored information (S335). Thereby, IWB22 can avoid that information is known to an outsider.

  Moreover, the meeting assistance apparatus 30 transmits completion | finish information to the terminal device 20 which the user who has participated in the meeting uses (S336-1, S336-2). Thereby, the meeting support apparatus 30 can notify the end of the meeting to the users participating in the meeting.

  FIG. 35 is a sequence diagram showing the flow of processing of the conference system 10 after the conference. FIG. 36 is a diagram illustrating an example of the result screen. FIG. 37 is a diagram illustrating an example of a detail screen.

  In the conference system 10, after the conference ends, the user can refer to the action item information and the conclusion information generated in the conference using the terminal device 20. The conference system 10 executes the process according to the flow shown in FIG. 35 after the conference ends.

  First, the user performs a login operation to the conference support device 30 using the terminal device 20. When the login operation is performed, the terminal device 20 transmits login information to the conference support device 30 (S341). When the user authentication is successful, the conference support apparatus 30 transmits main screen data to the terminal apparatus 20 (S342). When receiving the main screen data, the terminal device 20 displays the main screen (S343).

  The user selects a conference that has been held on the main screen (S344). When a conference that has been held is selected by the user, the terminal device 20 transmits an information acquisition request regarding the selected conference to the conference support device 30 (S345).

  When the meeting support apparatus 30 receives an acquisition request for information related to the meeting, the meeting support apparatus 30 transmits result screen data (S346). The result screen data includes index information of action item information and conclusion information generated in the meeting.

  Upon receiving the result screen data, the terminal device 20 displays a result screen 610 as shown in FIG. 36, for example (S347). The result screen 610 displays index information of action item information and conclusion information determined in the selected meeting. The index information of the action item information is, for example, a summary of actions to be executed, a person in charge, and a time limit. The index information of the conclusion information is, for example, a summary of the content of the conclusion.

  In addition, the terminal device 20 displays the action item information in which the user who uses the terminal device 20 is the person in charge as the person in charge. For example, the terminal device 20 displays action item information in which the user using the terminal device 20 is the person in charge on the upper side of the screen. If all information cannot be displayed in the monitor, the terminal device 20 may refer to the information by scrolling. In this case, the terminal device 20 displays the result screen 610 so that the action item information in which the user using the terminal device 20 is the person in charge is referred to in the initial state.

  Subsequently, the user selects any index information displayed on the result screen 610 (S348). When any index information is selected, the terminal device 20 transmits an acquisition request for detailed screen data corresponding to the selected index information to the conference support device 30 (S349). When the meeting support apparatus 30 receives the acquisition request, the meeting support apparatus 30 transmits the corresponding detailed screen data (S350).

  When receiving the detailed screen data, the terminal device 20 displays a detailed screen 630 as shown in FIG. 37, for example (S351). The detailed screen 630 includes an index area 641, an image area 642, and a detailed area 643. The index area 641 displays a summary of the corresponding action item information and a person in charge, or a summary of the corresponding conclusion information.

  In the image area 642, device image data read from the image data link destination included in the corresponding action item information or the corresponding conclusion information is displayed. The detailed area 643 displays the creation date and time, the deadline, the agenda number, and text data.

  When the play button 644 displayed on the detailed screen 630 is pressed, the terminal device 20 reads out and reproduces audio data from the audio data link destination included in the corresponding action item information or the corresponding conclusion information.

  As described above, the conference system 10 can allow the user to confirm the action item information and the conclusion information generated in the conference after the conference.

  FIG. 38 is a diagram illustrating an example of the hardware configuration of the IWB 22. The IWB 22 includes a CPU (Central Processing Unit) 721, a ROM (Read Only Memory) 722, a RAM (Random Access Memory) 723, a flash memory 724, an SSD (Solid State Drive) 725, and an HD (Hard Disk) 726. A hard disk drive (HDD) 727, a network I / F 728, a media drive 729, an audio input / output I / F 731, an image input I / F 732, a capture device 733, a GPU (Graphics Processing Unit) 734, A display 720, a display controller 735, a contact sensor 736, a sensor controller 737, an electronic pen controller 738, and a bus line 740.

  The CPU 721 controls the overall operation of the IWB 22. The ROM 722 stores a program executed by the CPU 721. The RAM 723 is used as a work area for the CPU 721. The flash memory 724 stores various data such as a control program for the IWB 22. The IWB 22 may include an EEPROM or the like instead of the flash memory 724. The SSD 725 controls reading or writing of various data with respect to the flash memory 724 according to the control of the CPU 721.

  The HD 726 stores data and programs executed by the CPU 721. The HDD 727 controls reading or writing of various data with respect to the HD 726 according to the control of the CPU 721.

  The network I / F 728 controls communication via the network. The media drive 729 controls reading or writing (storage) of data with respect to a recording medium such as a flash memory that can be attached to and detached from the IWB 22. The voice input / output I / F 731 processes input / output of a sound signal with a microphone speaker or the like according to the control of the CPU 721.

  The image input I / F 732 inputs an image captured by the camera. The capture device 733 captures a still image or a moving image displayed on the display 720. The GPU 734 executes graphics processing. The GPU 734 executes an image drawing process according to information input by the user. Further, the GPU 734 executes processing for combining the drawn image with an image displayed when the CPU 721 executes the program and an image input from the camera. Display 720 displays information. For example, the display 720 is a flat panel display. The display controller 735 controls and manages screen display in order to output an output image from the GPU 734 to the display 720.

  The contact sensor 736 detects a touch operation on the display 720 and an input of information by an electronic pen or a user's hand. The sensor controller 737 controls processing of the contact sensor 736 according to the control of the CPU 721.

  The electronic pen controller 738 determines whether or not there is a pen tip touch or a pen butt touch on the display 720 by communicating with the electronic pen. It should be noted that the electronic pen controller 738 may determine whether there is a touch not only on the pen tip and the pen butt of the electronic pen, but also on the part held by the user of the electronic pen or other electronic pen part.

  The bus line 740 is an address bus, a data bus, or the like for connecting each component.

  FIG. 39 is a diagram illustrating an example of a hardware configuration of the terminal device 20. The terminal device 20 includes a CPU 821, ROM 822, RAM 823, flash memory 824, SSD 825, power switch 826, network I / F 831, camera 832, image sensor I / F 833, microphone 834, and speaker 835. A voice input / output I / F 836, a touch panel display 820, a display I / F 838, an input I / F 839, and a bus line 840.

  The CPU 821 controls the overall operation of the terminal device 20. The ROM 822 stores a program executed by the CPU 821. The RAM 823 is used as a work area for the CPU 821. The flash memory 824 stores various data such as a control program for the terminal device 20 and image data. The terminal device 20 may include an EEPROM or the like instead of the flash memory 824. The SSD 825 controls reading or writing of various data with respect to the flash memory 824 according to the control of the CPU 821. The power switch 826 is a button for switching on / off the power of the terminal device 20.

  The network I / F 831 controls communication via the network. The camera 832 captures a subject according to the control of the CPU 821 and obtains image data. The image sensor I / F 833 controls driving of the camera 832. The microphone 834 inputs sound. The speaker 835 outputs sound. The voice input / output I / F 836 processes input / output of a sound signal between the microphone 834 and the speaker 835 according to the control of the CPU 821.

  The touch panel display 820 displays an image corresponding to the image data, an operation icon, and the like. Furthermore, touch panel display 820 accepts operation inputs made on the screen. The display I / F 838 transmits image data to the touch panel display 820 under the control of the CPU 821. The input I / F 839 detects an operation input made on the touch panel display 820. The bus line 840 is an address bus, a data bus, or the like for connecting each component.

  When the terminal device 20 is a notebook computer or the like, the terminal device 20 may include a display that does not have an input function instead of the touch panel display 820. In this case, the terminal device 20 has input devices such as a keyboard and a mouse.

  FIG. 40 is a diagram illustrating an example of a hardware configuration of the conference support apparatus 30. The meeting support apparatus 30 is an information processing apparatus such as a computer or a server apparatus.

  The conference support apparatus 30 includes a CPU 921, a ROM 922, a RAM 923, a network I / F 924, and a storage device 925. The CPU 921 controls the overall operation of the conference support apparatus 30. The ROM 922 stores a program executed by the CPU 921. The RAM 923 is used as a work area for the CPU 921.

  The network I / F 924 controls communication via the network. The storage device 925 is, for example, a hard disk drive. The storage device 925 stores a control program for the conference support device 30 and various data referred to by the conference support device 30. In addition, the storage device 925 stores various management data necessary for supporting the conference, and audio data, moving image data, and device image data recorded in the conference.

  The program executed by the conference support apparatus 30 according to the present embodiment is an installable format or executable format file, and is a computer-readable recording such as a CD-ROM, a flexible disk (FD), a CD-R, and a DVD. Provided by being recorded on a medium.

  In addition, the program executed by the conference support apparatus 30 of the present embodiment may be provided by being stored on a computer connected to a network such as the Internet and downloaded via the network. In addition, the program executed by the conference support apparatus 30 of the present embodiment may be configured to be provided or distributed via a network such as the Internet. Further, the program of the present embodiment may be configured to be provided by being incorporated in advance in the ROM 922 or the like.

  A program for causing a computer to function as the conference support apparatus 30 includes a device screen providing module, a terminal screen providing module, a device operation receiving module, a terminal operation receiving module, a device image collecting module, a device image providing module, It has a voice collection module, a voice provision module, a moving picture collection module, a moving picture provision module, and a conference processing module. The conference processing module includes a user registration module, a conference registration module, an agenda registration module, a participation form registration module, a file registration module, a start notification module, an agenda processing module, a file processing module, and a drawing data processing module. An action item generation module, a conclusion generation module, a termination processing module, and a result providing module.

  In the conference support apparatus 30, as the actual hardware, the processor (CPU 921) reads out and executes a program from a storage medium (such as the storage device 925), so that the above-described units are loaded onto the main storage device (RAM 923). Then, the processor (CPU 921) includes a device screen providing unit 70, a terminal screen providing unit 72, a device operation receiving unit 74, a terminal operation receiving unit 76, a device image collecting unit 78, a device image providing unit 80, a sound collecting unit 82, and a sound. Providing unit 84, moving image collecting unit 86, moving image providing unit 88, conference processing unit 90 (user registration unit 110, conference registration unit 112, agenda registration unit 114, participation form registration unit 116, file registration unit 118, start notification unit 120, an agenda processing unit 122, a file processing unit 124, a drawing data processing unit 126, an action item generating unit 128, a conclusion generating unit 130, an end processing unit 132, and a result providing unit 106).

  As mentioned above, although embodiment of this invention was described, embodiment is shown as an example and is not intending limiting the range of invention. These novel embodiments can be implemented in various other forms.

10 Conference System 20 Terminal Device 22 IWB
30 Conference support device 42 First communication unit 44 Operation input unit 46 Screen display unit 48 Image generation unit 50 Second communication unit 52 Sound collection unit 54 Imaging unit 56 Input unit 58 Display unit 60 Audio output unit 62 Third communication unit 64 Information Storage unit 70 Device screen providing unit 72 Terminal screen providing unit 74 Device operation receiving unit 76 Terminal operation receiving unit 78 Device image collecting unit 80 Device image providing unit 82 Audio collecting unit 84 Audio providing unit 86 Moving image collecting unit 88 Moving image providing unit 90 Conference processing unit 102 Preparation unit 104 Progression unit 106 Result providing unit 110 User registration unit 112 Conference registration unit 114 Agenda registration unit 116 Participation form registration unit 118 File registration unit 120 Start notification unit 122 Agenda processing unit 124 File processing unit 126 Drawing data Processing unit 128 Action item generation unit 130 Conclusion generation unit 132 End processing unit 510 Preparation screen 512 Project area 514 Conference information area 516 User information area 518 Agenda information area 520 Conference button 522 Conference addition button 524 User individual area 526 Agenda individual area 528 Agenda addition button 530 File icon 540 Start screen 550 Device conference screen 561 Drawing Button 562 Save button 563 Next agenda button 564 Previous agenda button 565 File button 566 Action item button 567 Conclusion button 568 Setting button 569 User button 580 File list screen 590 Action item input screen 591 Person in charge input box 592 Time limit input box 593 First voice Record button 594 First OK button 595 First cancel button 600 Conclusion input screen 601 Second voice record button 602 Text display box 03 The 2OK button 604 second cancel button 610 results screen 630 detail screen 641 the index area 642 the image region 643 details area 644 play button

JP 2010-28389 A

Claims (17)

An information processing apparatus connected to a terminal device used by a user via a network and supporting discussion by a plurality of users in a conference,
Prior to the meeting, at least one agenda to be discussed at the meeting, and an agenda registration unit for registering users who participate in the discussion for each agenda;
An agenda processing unit for transmitting agenda start information indicating that a participating agenda starts, to a user who participates in the changed agenda when accepting the agenda change;
An information processing apparatus comprising: Prior to the conference, for each user who participates in the conference, direct participation to participate in the conference at a predetermined location, or remote participation in the conference using the terminal device at a location different from the predetermined location Register whether to participate in the conference according to the participation mode of participation or semi-participation that participates in the conference using the terminal device at a location different from the predetermined location for some agenda items in the conference And a participation form registration unit
The information processing apparatus according to claim 1, wherein the agenda processing unit transmits the agenda start information to a user who participates in the agenda by the semi-participation among users who participate in the started agenda. The information processing apparatus according to claim 2, wherein the participation form registration unit registers, as a participation form, any user who does not participate in the conference in real time but refers to related information later. The device is installed at the predetermined location, and further connected to a device for displaying information,
The information processing apparatus according to claim 2, wherein the agenda processing unit receives a change in agenda from the device. Prior to the meeting, a file registration unit for registering a file to be displayed on the device and a creator of the file;
A file processing unit that transmits file output information indicating that the file has been output to the creator when the file is output to the device during the progress of any agenda in the meeting;
The information processing apparatus according to claim 4, further comprising: The information processing apparatus according to claim 5, wherein the file processing unit transmits the file output information to the creator who participates in the agenda by the semi-participation. When the generation of action item information is instructed during the progress of any agenda item in the conference, the first voice data representing the voice collected during the first operation, which is a predetermined operation, and the person in charge An action for acquiring person-in-charge information indicating a person, generating the action item information including the acquired first voice data, the person-in-charge information, and information specifying the current agenda, and storing the generated action item information The information processing apparatus according to claim 4, further comprising an item generation unit. The action item generation unit acquires first device image data representing an image displayed on the device during the first operation, and generates the action item information further including the acquired first device image data. Item 8. The information processing device according to Item 7. The information according to claim 7 or 8, wherein the action item generation unit acquires first text data obtained by converting the first audio data into text, and generates the action item information further including the acquired first text data. Processing equipment. When generation of a conclusion is instructed during the progress of any agenda item in the conference, second voice data representing the voice collected during the second operation, which is a predetermined operation, is acquired and acquired. 10. The information processing according to claim 7, further comprising: a conclusion generation unit that generates conclusion information including information specifying the second audio data and the current agenda, and stores the generated conclusion information. apparatus. 11. The conclusion generation unit acquires second device image data representing an image displayed on the device during the second operation, and generates the conclusion information further including the acquired second device image data. The information processing apparatus described in 1. The information processing apparatus according to claim 10 or 11, wherein the conclusion generation unit acquires second text data obtained by converting the second audio data into text, and generates the conclusion information further including the acquired second text data. . When at least one of the action item information and the conclusion information generated in the conference is received when the selection of information related to the past conference is received from the terminal device used by any of the users after the conference ends The information processing apparatus according to claim 10, further comprising a result providing unit that displays a result screen on the terminal device. The information processing apparatus according to claim 13, wherein the result providing unit displays the action item information, in which the user who uses the terminal device is the person in charge, at a higher rank. A terminal device used by users participating in the conference;
Equipment installed in place,
An information processing apparatus that is connected to the terminal device and the device via a network and supports discussion by a plurality of users in the meeting,
The information processing apparatus includes:
Prior to the meeting, at least one agenda to be discussed at the meeting, and an agenda registration unit for registering users who participate in the discussion for each agenda;
An agenda processing unit for transmitting agenda start information indicating that a participating agenda starts, to a user who participates in the changed agenda when accepting the agenda change;
Conference system. A method that is executed in an information processing apparatus that supports a discussion by a plurality of users in a conference by connecting to a terminal device used by a user via a network,
The information processing apparatus is
Prior to the meeting, register at least one agenda item to be discussed at the meeting, and users who participate in the discussion for each agenda item,
A method of executing a process of transmitting agenda start information indicating that a participating agenda starts to a user who participates in the agenda after the change when a change of the agenda is accepted. A program for connecting an information processing device to a terminal device used by a user via a network and functioning as a device that supports discussion by a plurality of users at a conference,
The information processing apparatus;
Prior to the meeting, at least one agenda to be discussed at the meeting, and an agenda registration unit for registering users who participate in the discussion for each agenda;
An agenda processing unit for transmitting agenda start information indicating that a participating agenda starts, to a user who participates in the changed agenda when accepting the agenda change;
Program to make it work.