JP6508009B2 - Terminal device, screen recording method, program, and information processing system - Google Patents

Description

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

  For example, in a meeting, each participant records the contents of a printed document, a document image projected on a projector device, the contents of a board on a white board, etc., records the contents of discussion, and records the state of the meeting There is something to do.

  On the other hand, a paperless conference in which materials are held as image data by the spread of wireless communication using a tablet computer and a tablet computer, and each participant shares image data with each other by a tablet computer to present the material An information presentation system such as a system has also been put to practical use (see, for example, Patent Document 1).

  In the conventional conference system, there is a conference client device capable of switching between the shared mode and the personal mode. In the conference client device in the sharing mode, the screen is updated so as to be synchronized with the screen (the shared screen) of the conference client device of the presenter in conjunction with the operation of the presenter such as page turning.

  Also, in the conference client device in the personal mode, it is possible to display a screen (personal screen) asynchronous to the shared screen without interlocking with the operation of the presenter such as page turning. In the conference client device in the personal mode, the operator of the conference client device can freely perform operations such as page turning.

  In a conference system having a conference client device capable of switching between such shared mode and personal mode, there is a problem that switching from shared mode to personal mode can not be made when an operator of the conference client device tries to record a shared screen. there were.

  The embodiment of the present invention has been made in view of the above-described point, and an object of the present invention is to provide a terminal device capable of recording a screen for each mode without being affected by a change in display screen due to mode switching. .

  In order to achieve the above object, claim 1 of the present application is a first mode in which a first screen synchronized with another terminal device is displayed by a switching operation by the operator, and the second mode asynchronously with the other terminal device A terminal device for switching between the second mode of displaying the screen and the mode switching operation of the first mode and the second mode by the operator, the mode switching operation being switched A screen display input means for displaying the first screen of the first mode or the second screen of the second mode, and a screen recording operation by the operator, the screen display input means Instead of displaying the first screen of the first mode or the second screen of the second mode, the first screen or the first screen is displayed for each of the first mode or the second mode. 2 It characterized by having a a screen recording means for recording the screen.

  According to the embodiment of the present invention, the screen can be recorded for each mode without being affected by the change of the display screen due to the mode switching.

It is a block diagram of an example of the meeting system concerning this embodiment. It is a hardware block diagram of an example of the computer which comprises the meeting system which concerns on this embodiment. It is a functional block diagram of an example of a meeting client apparatus. It is a functional block diagram of an example of a conference server apparatus. It is a block diagram of an example of screen information memorized by a screen information storage part. It is a flow chart of an example of processing which displays a meeting screen in a meeting client device of this embodiment. It is an image figure of an example of the personal screen of a non-recording state. It is an image figure of an example of the personal screen of a recording state. It is a flowchart of an example of shared screen generation processing. It is a flowchart of an example of shared screen update processing. It is a flow chart of an example of recording control processing at the time of changing from a non-recording state to a recording state. It is a flowchart of an example of a moving image generation process. It is a block diagram of an example of metadata inserted in animation. It is a flowchart of an example of video recording control processing at the time of changing from a video recording state to a non-video recording state. It is an image figure of an example of a meeting record list screen. It is an image figure of an example of a reproduction screen. It is a block diagram of the other example of the meeting system which concerns on this embodiment. It is a functional block diagram of the other example of a meeting client apparatus. It is a functional block diagram of the other example of a meeting server apparatus. It is a block diagram of an example of group information. It is a block diagram of an example of user information. It is a block diagram of an example of meeting information. It is a block diagram of an example of meeting video recording information. It is a flowchart of an example of a meeting registration process. It is an image figure of an example of the meeting registration screen after login. It is a sequence diagram of an example of processing which records a meeting. FIG. 6 is a sequence diagram of an example of a process of controlling access to recording data. It is an image figure of an example of a recording list screen. It is a flow chart of an example of processing which a user who succeeded in authentication chooses information on reproducible recorded data. It is a block diagram of an example of meeting information. It is a block diagram of an example of agenda information. It is a block diagram of an example of meeting video recording information. It is a block diagram of an example of the command of XMPP. It is a flowchart of the other example of a share screen update process. It is a flowchart of the other example of a moving image generation process. It is an image figure of an example of an agenda selection screen.

  Next, embodiments of the present invention will be described in detail.

First Embodiment
<System configuration>
FIG. 1 is a block diagram of an example of a conference system according to the present embodiment. The conference system 1 of FIG. 1 shows, as an example, a configuration in which a plurality of conference client devices 10, a conference server device 12, and a conference display device 14 are connected to a network N1 such as a LAN.

  The conference server device 12 manages conference information, conference materials, etc., and also has functions such as holding a conference and controlling participation, and delivering in real time the input operation of the presenter to the conference client device 10 participating.

  The conference server device 12 can be realized by software or service operating on one computer. Also, the conference server device 12 may be software or a service operating on a plurality of computers. Also, the conference server device 12 may take the form of, for example, a so-called cloud service. The conference server device 12 may have a conference server function, and can be realized by various hardware configurations.

  The conference client device 10 acquires conference information, conference materials, and the like from the conference server device 12 and accepts operations necessary for the progress of the conference from operators such as the presenter and participant of the conference, and allows the conference materials to be viewed. Function etc. Operators such as a meeting presenter and a participant can join the meeting from the meeting client device 10.

  The conference client device 10 may be a PC, a tablet terminal, a smartphone, a mobile phone, a portable information terminal such as a PDA, a conference dedicated terminal, an electronic whiteboard, or an image forming device such as an MFP or a printer. The conference client device 10 can receive an input operation of a presenter from the conference server device 12 in real time while participating in a conference, and can share a display screen with another conference client device 10.

  Note that one of the conference client devices 10 can be operated by the presenter to request the conference server device 12 to start the conference and end the conference. The conference client device 10 can be switched to two types of modes: shared mode and personal mode. For example, in the sharing mode, the meeting material on the screen of the participant's meeting client device 10 is displayed synchronously with the meeting material on the screen of the presenter's meeting client device 10 along the progress of the presenter's meeting. The shared screen to be synchronized includes, for example, a page display of the meeting material, a display of a writing on the meeting material (handwritten memo), and a display of a pointer to the meeting material.

  Further, in the individual mode, it is possible to freely (asynchronously) display a personal screen in which the meeting material on the screen is not synchronized with the meeting material on the screen of the presenter's meeting client device 10 regardless of the progress of the presenter's meeting. The meeting material is an example of the content that receives an input operation from the presenter (for example, change of a display page, addition of a handwritten memo, and the like).

  The conference display device 14 is, for example, installed in a conference room, and is an example of an output device for browsing conference material on a large screen. The conference display device 14 may be a display device such as an electronic whiteboard or a projection device such as a projector.

  The conference system 1 shown in FIG. 1 is an example, and not all the devices shown in FIG. 1 are necessarily required. For example, the conference system 1 may have a configuration in which one or more conference client devices 10 perform the function of the conference server device 12 instead. In addition, the conference system 1 may be configured without the conference display device 14.

<Hardware configuration>
The conference client device 10 and the conference server device 12 are realized, for example, by the hardware configuration shown in FIG.

  FIG. 2 is a hardware block diagram of an example of a computer that constitutes the conference system according to the present embodiment. The conference client device 10 in FIG. 2 includes an input device 501, a display device 502, an external I / F 503, a RAM 504, a ROM 505, a CPU 506, a communication I / F 507, an HDD 508, etc. The conference client device 10 may be configured to have a camera, a microphone, a speaker, and the like.

  The input device 501 includes a keyboard, a mouse, a touch panel, and the like, and is used to input each operation signal to the conference client device 10. Further, the display device 502 includes a display and the like, and displays the processing result by the conference client device 10. The communication I / F 507 is an interface for connecting the conference client device 10 to the network N1. The conference client device 10 can perform data communication with the conference server device 12 via the communication I / F 507.

  The HDD 508 is a non-volatile storage device storing programs and data. The stored programs and data include an OS which is basic software for controlling the entire conference client device 10 and application software which provides various functions on the OS. Also, the HDD 508 manages stored programs and data by a predetermined file system and / or DB.

  An external I / F 503 is an interface with an external device. The external device is, for example, a recording medium 503a. Thus, the conference client device 10 can read and / or write the recording medium 503 a via the external I / F 503. The recording medium 503a includes a flexible disk, a CD, a DVD, an SD memory card, a USB memory, and the like.

  The ROM 505 is a non-volatile semiconductor memory (storage device) capable of holding programs and data even after the power is turned off. The ROM 505 stores programs and data such as a BIOS, an OS setting, and a network setting that are executed when the conference client device 10 is started. The RAM 504 is a volatile semiconductor memory that temporarily holds programs and data.

  The CPU 506 is an arithmetic device that implements control and functions of the entire conference client device 10 by reading programs and data from a storage device such as the ROM 505 or the HDD 508 onto the RAM 504 and executing processing.

  The conference client device 10 can realize various processes as described later, for example, by executing the program with the above-described hardware configuration.

  The conference server device 12 shown in FIG. 2 includes an input device 601, a display device 602, an external I / F 603, a RAM 604, a ROM 605, a CPU 606, a communication I / F 607, an HDD 608, etc. There is. Note that the input device 601 and the display device 602 may be connected and used as needed.

  The input device 601 includes a keyboard, a mouse and the like, and is used to input each operation signal to the conference server device 12. The display device 602 includes a display and the like, and displays the processing result by the conference server device 12.

  The communication I / F 607 is an interface for connecting the conference server apparatus 12 to the network N1. The conference server device 12 can perform data communication with the conference client device 10 via the communication I / F 607.

  The HDD 608 is a non-volatile storage device storing programs and data. The stored programs and data include an OS which is basic software for controlling the entire conference server apparatus 12 and application software which provides various functions on the OS. Further, the HDD 608 manages stored programs and data by a predetermined file system and / or DB.

  The external I / F 603 is an interface with an external device. The external device is, for example, a recording medium 603a. Thus, the conference server apparatus 12 can read and / or write the recording medium 603 a via the external I / F 603. The recording medium 603a includes a flexible disk, a CD, a DVD, an SD memory card, a USB memory, and the like.

  The ROM 605 is a non-volatile semiconductor memory (storage device) capable of holding programs and data even after the power is turned off. The ROM 605 stores programs and data such as a BIOS, an OS setting, and a network setting that are executed when the conference server device 12 is started. The RAM 604 is a volatile semiconductor memory that temporarily holds programs and data.

  The CPU 606 is an arithmetic device that implements control and functions of the entire conference server device 12 by reading programs and data from a storage device such as the ROM 605 and the HDD 608 onto the RAM 604 and executing processing.

  The conference server apparatus 12 can realize various processes as described later by executing a program with the above-described hardware configuration, for example. The description of the hardware configuration of the conference display device 14 is omitted.

<Software configuration>
The conference client device 10 and the conference server device 12 of the conference system 1 according to the present embodiment are realized by, for example, the following functional blocks. In addition, the functional block shown below shows a structure required for description, and is abbreviate | omitting suitably about a structure unnecessary for description.

<< Conference client device >>
The conference client device 10 is realized by, for example, functional blocks as shown in FIG. FIG. 3 is a functional block diagram of an example of the conference client apparatus. The conference client device 10 shown in FIG. 3 executes a program to execute the control unit 51, the communication unit 52, the terminal screen display input unit 53, the conference information storage unit 54, the conference recording information storage unit 55, and the screen information storage unit 56. Is realized. The control unit 51 includes a conference recording unit 58 and a conference recording start end unit 59. The program executed by the conference client device 10 is, for example, an application installed in the conference client device 10.

  The conference recording unit 58 of the control unit 51 records a shared screen of the participating conference. The meeting recording start end unit 59 controls the start and end of recording of the shared screen by the meeting recording unit 58. The communication unit 52 communicates with the conference server device 12 via the network N1. The terminal screen display input unit 53 performs screen display and input reception from the operator.

  For example, the terminal screen display input unit 53 displays the conference material using the conference information, the conference material, and the like acquired from the conference server device 12. The terminal screen display input unit 53 receives various operations from an operator such as a presenter or a participant of a meeting, and displays a meeting screen according to the operation. The conference information storage unit 54 stores the conference information and the material information received from the conference server device 12. The conference recording information storage unit 55 stores conference recording information on the recording of the shared screen. The screen information storage unit 56 stores information (screen information) of the current shared screen and personal screen as described later.

  As the meeting material, for example, a file in PDF (Portable Document Format) format can be used. In the case of the conference client device 10 executed on the Web browser, screen data may be received from the conference server device 12 every time instead of the file in PDF format.

  Also, in the conference system 1, the functions can be made different depending on the role of the conference client device 10. For example, the conference system 1 can be provided with roles such as a conference facilitator, a presenter, and a participant. The facilitator can decide the presenter and meeting materials. The presenter can perform page turning of the meeting material in the sharing mode, a handwritten memo, and an operation of scaling. Participants can view meeting material in shared mode. In the present embodiment, an example will be described in which the conference system 1 is provided with roles of a presenter and a participant of the conference.

<< Conference server device >>
The conference server device 12 is realized by, for example, functional blocks as shown in FIG. FIG. 4 is a functional block diagram of an example of the conference server apparatus. The conference server device 12 implements the information management unit 61, the communication unit 62, and the conference information storage unit 63 by executing a program.

  The information management unit 61 manages conference information and conference materials such as conference name, conference material, conference date and time, and conference attendance users. The communication unit 62 communicates with the conference client device 10 via the network N1. The meeting information storage unit 63 stores meeting information and meeting materials to be transmitted to the meeting client device 10.

  In the conference system 1 of the present embodiment, a conference client who participates in a conference using Extensible Messaging and Presence Protocol (XMPP) information related to the input operation of the presenter such as page turning, handwritten memos, and scaling with respect to conference materials. It is distributed to the device 10. In addition, XMPP is an example and may use another protocol.

  The conference system 1 distributes information related to the presenter's input operation such as page turning by a presenter, handwritten memos, enlargement / reduction, etc. to the meeting client device 10 participating in the meeting by XMPP, thereby presenting the presenter's meeting client device 10 It is possible to share the input operation on the meeting material on the screen (shared screen) of.

<< Data structure >>
FIG. 5 is a block diagram of an example of screen information stored in the screen information storage unit. As shown in FIG. 5, the screen information separately stores information on the shared screen and information on the personal screen. The screen information in FIG. 5 is configured to include a material ID, a page number, a material display area, and handwritten memo information. The screen information of FIG. 5 stores information of the current shared screen and personal screen.

  Therefore, by using the screen information of FIG. 5, the conference client device 10 can switch and display the personal screen and the shared screen by mode switching between the personal mode and the sharing mode.

<Details of processing>
Below, the detail of the process of the conference system 1 which concerns on this embodiment is demonstrated.

Conference processing
A conference presenter and a participant operate the conference client device 10 and request access to the conference participation screen of the conference server device 12. The conference client device 10 makes a conference information acquisition request by accessing, for example, the URI of the conference participation screen of the conference server device 12.

  The conference server device 12 transmits, to the conference client device 10, conference information of a conference that can be held or joined at present. The conference client device 10 displays a conference participation screen on the display device 502 or the like based on the received conference information. The meeting participation screen includes a meeting list based on meeting information of a meeting that can be held or can be joined. The presenter of the meeting and the participant select the meeting to be held or joined from the meeting list on the meeting participation screen. The conference client device 10 requests the conference server device 12 to participate in the conference selected by the conference presenter and the participant.

  The conference server device 12 establishes a communication path (session) with the conference client device 10 based on the participation request from the conference client device 10. The conference server apparatus 12 and the conference client apparatus 10 participating in the conference use the established communication path to exchange information necessary for displaying the shared screen or the personal screen.

  As described above, the conference system 1 according to the present embodiment transmits the message indicating the input operation of the presenter from the conference client device 10 of the presenter to the conference client device 10 of the participant via the conference server device 12 through the established communication path. Deliver in real time. In the present embodiment, XMPP is used as an example of a protocol for delivering a message in real time using such a communication path. As such a communication path, besides XMPP, for example, protocols such as BOSH and WebSocket, which are extensions of XMPP, and methods such as Commet can be used.

  The conference client device 10 participating in the conference performs a process of displaying the conference screen according to the procedure as shown in FIG. 6, for example. FIG. 6 is a flowchart of an example of processing for displaying a conference screen in the conference client device of the present embodiment.

  In step S11, the terminal screen display input unit 53 of the conference client device 10 determines whether it is in the sharing mode. If in the sharing mode, the terminal screen display input unit 53 performs a sharing screen generation process of step S12 described later.

  In step S13, the terminal screen display / input unit 53 displays the shared screen generated in step S12. In step S14, the terminal screen display input unit 53 updates the shared screen in accordance with the input operation of the presenter accepted by the presenter's conference client device 10. Details of the shared screen update process in step S14 will be described later.

  In step S15, the terminal screen display input unit 53 determines whether the recording button provided on the shared screen is pressed. When the record button is pressed, the terminal screen display input unit 53 calls a record control process of step S16 described later. The depression of the recording button in step S15 is to switch between the unrecorded state and the recorded state. The unrecorded state and the recorded state are switched each time the recording button is pressed.

  When switching from the unrecorded state to the recorded state by pressing the record button, in the recording control process of step S16, the conference recording unit 58 records the shared screen of the conference under the control of the conference recording start end unit 59 of the control unit 51. . On the other hand, when the recording state is switched to the non-recording state by pressing the recording button, in the recording control process of step S16, the conference recording unit 58 records the shared screen of the conference under the control of the conference recording start end unit 59 of the control unit 51. Finish. Details of the recording control process of step S16 will be described later.

  If the recording button is not pressed in step S15, the terminal screen display / input unit 53 proceeds to the process of step S17 without calling the recording control process of step S16.

  Then, the terminal screen display input unit 53 proceeds to step S17, and determines whether or not a mode switching operation from the sharing mode to the personal mode has been received from the operator. If the mode switching operation from the sharing mode to the personal mode is not received from the operator, the terminal screen display input unit 53 returns to step S14 and continues the processing. If the mode switching operation from the sharing mode to the personal mode is received from the operator, the terminal screen display / input unit 53 returns to step S11 and continues the process.

  If the mode is not the sharing mode in step S11, the terminal screen display input unit 53 performs the personal screen generation process of step S18. In the personal screen generation process of step S18, the material ID, the page number, and the material display area of the personal screen are acquired from the screen information of FIG. 5, and the personal screen is generated from the conference material. Further, in the personal screen generation process of step S18, handwritten memo information is acquired from the screen information of FIG. 5, and the personal handwritten memo is added on the personal screen.

  In step S19, the terminal screen display input unit 53 displays the personal screen generated in step S18. In step S20, the terminal screen display input unit 53 receives an input operation by the operator, and updates the personal screen according to the input operation.

  In step S21, the terminal screen display input unit 53 determines whether the recording button provided on the personal screen is pressed. When the recording button is pressed, the terminal screen display input unit 53 calls a recording control process of step S22 described later. The depression of the recording button in step S21 is to switch between the non-recording state and the recording state. The unrecorded state and the recorded state are switched each time the recording button is pressed.

  When switching from the unrecorded state to the recorded state by pressing the record button, in the recording control process of step S22, the conference recording unit 58 records the shared screen of the conference under the control of the conference recording start end unit 59 of the control unit 51. . On the other hand, when the recording state is switched to the non-recording state by pressing the recording button, in the recording control process of step S22, the conference recording unit 58 records the shared screen of the conference under the control of the conference recording start end unit 59 of the control unit 51. Finish. Details of the recording control process of step S22 will be described later.

  If the recording button is not pressed in step S21, the terminal screen display input unit 53 proceeds to the process of step S23 without calling the recording control process of step S22.

  Then, the terminal screen display input unit 53 proceeds to step S23, and determines whether a mode switching operation from the personal mode to the sharing mode has been received from the operator. If the mode switching operation from the personal mode to the sharing mode has not been received from the operator, the terminal screen display input unit 53 returns to step S20 and continues the processing. If the mode switching operation from the personal mode to the sharing mode is received from the operator, the terminal screen display / input unit 53 returns to step S11 and continues the process.

  For example, the personal screen provided with the recording button is as shown in FIG. 7 and FIG. FIG. 7 is an image diagram of an example of the unrecorded personal screen. FIG. 8 is an image diagram of an example of the personal screen in the recording state.

  The personal screen 1000 in FIG. 7 includes a recording button 1001, a mode switching button 1002, and a presenter switching button 1003. The operator of the conference client device 10 can switch from the non-recording state to the recording state and start recording of the shared screen by pressing the recording button 1001 of the personal screen 1000 of FIG. 7. The terminal screen display input unit 53 calls a recording control process of step S22 described later by pressing the recording button 1001 provided on the personal screen 1000 of FIG. 7.

  The operator of the conference client device 10 can switch the mode between the personal mode and the sharing mode by operating the mode switching button 1002 of the personal screen 1000. The terminal screen display input unit 53 switches between the personal mode and the sharing mode by the operation of the mode switching button 1002 provided on the personal screen 1000.

  In addition, the operator of the conference client device 10 can switch between the participant and the presenter by operating the presenter switching button 1003 of the personal screen 1000. The terminal screen display input unit 53 switches the role of the conference client device 10 between the participant and the presenter by the operation of the presenter switching button 1003 provided on the personal screen 1000.

  Since the personal screen 1000 of FIG. 8 is switched from the non-recording state to the recording state by pressing the recording button 1001 of the personal screen 1000 of FIG. 7 and the shared screen is being recorded, the display of the recording button 1001 changes ( For example, it glows red. By changing the display of the recording button 1001, the conference client device 10 can cause the operator to visually recognize that the shared screen is being recorded.

  The operator of the conference client device 10 can switch from the recording state to the non-recording state and stop the recording of the shared screen by pressing the recording button 1001 of the personal screen 1000 of FIG.

  7 and 8 show an example of the personal screen 1000 provided with the recording button 1001, the same applies to the shared screen provided with the recording button 1001. Therefore, the description of the shared screen provided with the record button 1001 is omitted.

<< S12: Shared screen generation process >>
The shared screen generation process of step S12 is performed, for example, as shown in FIG. FIG. 9 is a flowchart of an example of shared screen generation processing. In step S31, the terminal screen display input unit 53 of the conference client device 10 acquires screen information (material ID, page number, material display area, handwritten memo information) of the shared screen from the screen information storage unit 56.

  In step S32, the terminal screen display input unit 53 generates an image from the conference material identified by the material ID, the page number of the shared screen, and the material display area. In step S33, the terminal screen display input unit 53 generates a shared screen by adding a handwritten memo drawn from the handwritten memo information to the image generated in step S32.

  As described above, according to the sharing screen generation process of step S12, the current sharing screen is displayed on the conference client device 10 by acquiring the information of the current sharing screen stored in the screen information storage unit 56. Can.

<< S14: Shared screen update process >>
The shared screen update process in step S14 is performed, for example, as shown in FIG. FIG. 10 is a flowchart of an example of shared screen update processing. In step S41, when the input operation of the presenter is received by XMPP, the terminal screen display / input unit 53 checks whether there is a change in the page number constituting the screen information of the shared screen, the material display area and the handwritten memo information.

  In step S42, if there is a change in the screen information of the shared screen, the terminal screen display / input unit 53 proceeds to step S43, and updates the screen information of the shared screen stored in the screen information storage unit 56. In step S44, the terminal screen display input unit 53 stores the update time and the update content of the shared screen in the conference recording information storage unit 55.

<< S16 and S22: Recording control process >>
The recording control process in steps S16 and S22 differs between when the unrecorded state is switched to the recorded state and when the recorded state is switched to the unrecorded state. When the unrecorded state is switched to the recorded state, the process shown in FIG. 11 is performed. When the recording state is switched to the non-recording state, the processing shown in FIG. 14 is performed. FIG. 11 is a flowchart of an example of the recording control process when the unrecorded state is switched to the recorded state. FIG. 14 is a flowchart of an example of the recording control process when the recording state is switched to the non-recording state.

  In step S51, the conference recording unit 58 included in the control unit 51 of the conference client device 10 performs initialization for recording the shared screen of the conference. In step S52, the conference recording unit 58 starts recording.

  In step S53, the conference recording unit 58 stands by until the shared screen is updated, and performs the moving image generation process of step S54 each time the shared screen is updated. The moving image generation process of step S54 is performed, for example, according to the procedure shown in FIG.

  FIG. 12 is a flowchart of an example of the moving image generation process. In step S61, the conference recording unit 58 generates an image of the updated shared screen. In step S62, the conference recording unit 58 inserts the image generated in step S61 into the moving image at the timing of the update time of the shared screen stored in step S44.

  In the process of step S62, the generated moving image becomes the image generated in step S61 from the update time of the shared screen stored in step S44 to the next update of the shared screen.

  In step S63, the meeting recording unit 58 inserts the metadata as shown in FIG. 13 into the moving image at the timing of the update time of the shared screen stored in step S44. FIG. 13 is a block diagram of an example of metadata inserted into a moving image. The metadata in FIG. 13 has chapter name, order, and start time as items. The start time of the metadata in FIG. 13 is the update time of the shared screen stored in step S44. The metadata in FIG. 13 is used as chapter information for dividing a recorded moving image.

  When the recording state is switched to the non-recording state, the conference recording unit 58 included in the control unit 51 of the conference client device 10 stops the moving image generation process of the shared screen of the conference in step S71 of FIG. In step S72, the conference recording unit 58 stops the recording. In step S73, the conference recording unit 58 combines the generated moving image and the recorded voice, and stores the resultant as a moving image of the shared screen of the conference, for example, in the meeting recording information storage unit 55.

<< Video playback processing >>
The moving image on the shared screen of the conference stored as described above can be selected and reproduced from the conference record list as shown in FIG. 15, for example. FIG. 15 is an image diagram of an example of the meeting record list screen. On the conference record list screen 1100 of FIG. 15, a list of moving images of the shared screen of the conference recorded by the operation of the operator of the conference client apparatus 10 pressing the video recording button as described above is displayed.

  The operator of the meeting client device 10 can reproduce the moving picture of the conference sharing screen on the reproduction screen as shown in FIG. 16 by selecting the moving picture of the meeting sharing screen to be reproduced from the meeting record list screen 1100 of FIG. . FIG. 16 is an image diagram of an example of the reproduction screen. On the reproduction screen 1200 of FIG. 16, a moving image display area 1201 for displaying the reproduced moving image and chapter information 1202 are displayed.

  The chapter information 1202 is generated based on the metadata inserted into the moving image in step S63, and includes the thumbnail of the shared screen displayed in each chapter. For example, when the operator of the conference client device 10 selects the thumbnail of the chapter information 1202, the chapter corresponding to the thumbnail can be pointed out.

<Summary>
In the conference system 1 of the present embodiment, even when switching from the non-recording state to the recording state in the sharing mode or when switching from the non-recording state to the recording state in the personal mode, recording of the conference shared screen It can be performed.

  Moreover, in the conference system 1 of the present embodiment, as shown in the flowchart of FIG. 6, even if there is mode switching after switching to the recording state, the recording state of the shared screen of the conference is maintained. Therefore, in the conference system 1 of the present embodiment, the shared screen of the conference can be recorded without being affected by the change of the display screen displayed on the conference client device 10.

[Other embodiments]
In the first embodiment, as shown in FIG. 1, the conference server apparatus 12 is used. As another embodiment, the conference server apparatus 12 may be omitted as shown in FIG. FIG. 17 is a block diagram of another example of the conference system according to the present embodiment. In the conference system 1 of FIG. 17, one or more conference client devices 10 perform the function of the conference server device 12 instead.

  In the first embodiment, as shown in the flowchart of FIG. 6, an example of recording a shared screen of a conference has been described. However, for example, recording of a personal screen of a conference may be performed. Recording may be performed for each personal screen. Furthermore, in the first embodiment, the operator is asked whether to record the shared screen of the conference, record the personal screen of the conference, or record each shared screen of the conference and personal screen at the timing of starting recording. It may be selected.

Second Embodiment
In the second embodiment, a user who can record a conference is managed by the recording authority. In the second embodiment, access control to the shared screen of the recorded conference and the moving image of the personal screen is performed. The second embodiment is the same as the first embodiment except for a part of the second embodiment, and thus the description will be appropriately omitted.

  FIG. 18 is a functional block diagram of another example of the conference client device. The conference client device 10 shown in FIG. 18 executes a program to execute the control unit 51, the communication unit 52, the terminal screen display input unit 53, the conference information storage unit 54, the conference recording temporary storage unit 55a, and the screen information storage unit 56. , And the login information request unit 57 is realized. The control unit 51 includes a conference recording unit 58 and a conference recording start end unit 59. Details of the meeting recording temporary storage unit 55a and the login information request unit 57 will be described later.

  FIG. 19 is a functional block diagram of another example of the conference server apparatus. The conference server device 12 illustrated in FIG. 19 executes a program to execute an information management unit 61, a communication unit 62, a conference information storage unit 63, a group information storage unit 64, a user information storage unit 65, and a conference recording information storage unit 66. To achieve.

  For example, the group information storage unit 64 stores group information as shown in FIG. FIG. 20 is a block diagram of an example of group information. The group information in FIG. 20 associates and stores a group name and a user list. The group name is an example of identification information that uniquely identifies a group. The user list is an example of a list of identification information that uniquely identifies users belonging to a group.

  In the group information shown in FIG. 20, a plurality of users can be set to belong to one group. Further, in the group information shown in FIG. 20, one user can be set to belong to a plurality of groups.

  The user information storage unit 65 also stores user information as shown in FIG. FIG. 21 is a block diagram of an example of user information. The user information shown in FIG. 21 stores the user name and the password in association with each other. The user name is an example of identification information that uniquely identifies the user. The password is an example of secret information associated with the user name.

  The meeting information storage unit 63 also stores meeting information as shown in FIG. FIG. 22 is a block diagram of an example of the conference information.

  The meeting information in FIG. 22 stores the meeting ID, the meeting name, the start date and time, the meeting material, the accessible group, and the recordable group in association with one another. The conference ID is an example of identification information that uniquely identifies a conference. The meeting name is the name of the meeting. The start date and time is the date and time to start the meeting. The meeting material indicates the meeting material used in the meeting.

  Also, the accessible group indicates the group name of the group that can access the conference. Users who belong to the group indicated in the accessible group can access the conference. Also, in the meeting information DB, a plurality of groups may be set as an accessible group for one meeting. Also, the recordable group indicates the group name of the group that can record the meeting. Users belonging to a group shown in the recordable group can record the conference.

  In addition, the conference recording information storage unit 66 stores the conference recording information as shown in FIG. FIG. 23 is a block diagram of an example of conference recording information.

  The meeting recording information in FIG. 23 stores the recording ID, the recording user, the meeting ID, the recording start date, the recording end date, the type, and the recording data in association with one another. The recording ID is an example of identification information for uniquely identifying a recording. The recording user is the user name of the user who made the recording. The conference ID is an example of identification information that uniquely identifies a conference. The recording start date and time is the date and time when the recording was started. The recording end date is the date when the recording was ended. The type is information indicating whether the recording of the shared screen or the recording of the personal screen. Recorded data is information indicating a file of a recorded moving image.

  FIG. 24 is a flowchart of an example of the conference registration process. The organizer or the presenter of the conference needs to register conference information such as conference information and conference materials in the conference server apparatus 12 before holding the conference.

  In step S101, the organizer or the presenter of the conference operates the conference client device 10 to instruct display of the conference registration screen. The terminal screen display input unit 53 of the conference client device 10 requests the conference server device 12 for a conference registration screen.

  In step S102, the information management unit 61 of the conference server device 12 creates a conference registration screen before login because the user is not logged in. In step S103, the information management unit 61 transmits the screen information of the created conference registration screen before login to the conference client device 10.

  In step S104, the terminal screen display input unit 53 of the conference client device 10 displays the conference registration screen before login based on the screen information of the conference registration screen before login received from the conference server device 12. The organizer or the presenter of the conference can register the conference information in the conference information storage unit 63 of the conference server device 12 by designating the conference information or the document information on the conference registration screen before login and instructing the conference registration.

  When it is desired to register a meeting in which the accessible group and the recordable group are set, the organizer or presenter of the meeting performs the meeting registration after the login process. In step S105, the organizer or presenter of the conference operates the conference client apparatus 10, inputs a user name and a password, and instructs login. The login information request unit 57 of the conference client device 10 makes a login request to the conference server device 12.

  In step S106, the information management unit 61 of the conference server device 12 performs authentication based on the login request from the conference client device 10. If the authentication is successful, the information management unit 61 of the conference server device 12 proceeds to step S107. Since the user is logged in, the information management unit 61 creates a conference registration screen after login. In step S108, the information management unit 61 transmits the screen information of the created conference registration screen after login to the conference client device 10.

  In step S109, the terminal screen display input unit 53 of the conference client device 10 displays the conference registration screen 1300 after login as shown in FIG. 25 based on the screen information of the conference registration screen after login received from the conference server device 12. .

  FIG. 25 is an image diagram of an example of the conference registration screen after login. The conference registration screen 1300 includes input fields such as a conference name, start date and time, conference material, accessible group, recordable group, and the like. In step S110, the organizer or the presenter of the conference performs conference registration from the conference registration screen 1300 after login. Meeting registration performed in step S110 includes selection of accessible groups and recordable groups. In step S111, the organizer or the presenter of the conference instructs conference registration from the conference registration screen after login.

  The terminal screen display input unit 53 sends a conference registration request specifying information such as the conference name, start date and time, conference material, accessible group, and recordable group to the conference server apparatus 12. In step S112, the information management unit 61 of the conference server device 12 receives a conference registration request specifying conference information such as conference name, start date and time, conference material, accessible group, recordable group, and the conference information is stored in the conference information storage unit. Register to 63.

  FIG. 26 is a sequence diagram of an example of a process of recording a conference. In step S121, the presenter or participant operates the conference client device 10, inputs a user name and a password, and instructs login. The login information request unit 57 of the conference client device 10 issues a login request to the conference server device 12 and receives an authentication result. Here, the explanation is continued assuming that the authentication is successful.

  In step S122, the terminal screen display / input unit 53 of the conference client device 10 requests the conference server device 12 for conference information of a conference to which the presenter and participant of the successfully authenticated conference can participate. The information management unit 61 of the conference server apparatus 12 refers to the conference information shown in FIG. 22 and determines that the group name to which the presenter or participant (user) who succeeded in authentication belongs is set as an accessible group, and access restriction Select a meeting that has not been set.

  Then, the information management unit 61 of the conference server device 12 returns the conference information of the selected conference to the conference client device 10. The conference information returned to the conference client device 10 includes information necessary for joining the conference, information about the presence or absence of the recording authority, and the like as the conference information of FIG. The conference recording start / termination unit 59 of the conference client device 10 can determine the presence or absence of the recording authority of the user who has succeeded in the authentication by referring to the recordable group included in the conference information. For example, when the group name to which the user who has succeeded in authentication belongs is set as a recordable group, the conference recording start end unit 59 determines that the user has the recording authority.

  Here, it is assumed that the user operates the conference client apparatus 10 and participates in a conference with recording authority. For example, the user can request recording of the personal screen 1000 by pressing the recording button 1001 of the personal screen 1000 shown in FIG. 7. The user can also request recording of the shared screen by pressing the recording button 1001 of the shared screen.

  When recording is requested from a user with recording authority, the meeting recording unit 58 of the meeting client device 10 starts recording of the personal screen 1000 or shared screen of the participating meeting in step S123, and recording the recording data into the meeting It stores in the temporary storage unit 55a.

  Further, the user can request the recording stop of the personal screen 1000 by pressing the recording button 1001 of the personal screen 1000 shown in FIG. 8, for example. Also, the user can request to stop the recording of the shared screen by pressing the recording button 1001 of the shared screen.

  When a recording stop is requested, the meeting recording unit 58 of the meeting client device 10 stops the recording of the personal screen 1000 or the shared screen of the participating meeting. In step S124, the meeting recording start / termination unit 59 of the meeting client device 10 uploads the recording data stored in the meeting recording temporary storage unit 55a to the meeting server device 12.

  The information management unit 61 of the conference server apparatus 12 stores the uploaded recording data in the conference recording information storage unit 66 as the conference recording information shown in FIG. In step S125, the meeting recording start / termination unit 59 of the meeting client device 10 deletes the uploaded recording data from the meeting recording temporary storage unit 55a.

  In this way, the user with recording authority can record the personal screen 1000 or the shared screen of the participating conference. The determination of the presence or absence of the recording authority can be performed after the recording button 1001 is pressed. Further, the determination of the presence or absence of the recording authority can be performed before the recording button 1001 is pressed. In the case where the determination of the presence or absence of the recording authority is performed before the recording button 1001 is pressed, for example, when the user is not the recording authority, the pressing of the recording button 1001 may not be accepted.

  FIG. 27 is a sequence diagram of an example of a process of controlling access to recording data. In step S131, the user operates the conference client device 10, inputs a user name and a password, and instructs login. The login information request unit 57 of the conference client device 10 issues a login request to the conference server device 12 and receives an authentication result. Here, the explanation is continued assuming that the authentication is successful.

  In step S132, the terminal screen display input unit 53 of the conference client device 10 requests the conference server device 12 for information on the recorded data that can be reproduced by the user who has succeeded in the authentication. The information management unit 61 of the conference server device 12 returns, to the conference client device 10, information on the video recording data that can be reproduced by the user who has succeeded in authentication, which is selected from the conference video recording information in FIG. The details of the process of the information management unit 61 for selecting the information of the recorded data that can be reproduced by the user who has succeeded in the authentication will be described later.

  The terminal screen display input unit 53 of the conference client device 10 that has returned the information of the recorded data that can be reproduced by the user who has succeeded in authentication displays a recorded image list screen 1400 as shown in FIG. 28, for example. FIG. 28 is an image diagram of an example of the recording list screen. The recording list screen 1400 displays a list 1401 of recordings.

  The recording list 1401 is a list of information of recorded data that can be reproduced by a user who has succeeded in authentication. The recording list 1401 of FIG. 28 includes a recording ID, a meeting name, a recording user, a recording start date and time, and a type.

  In step S133, the user operates the conference client device 10, selects video recording data from the video recording list 1401, and presses, for example, a playback button. The terminal screen display input unit 53 of the conference client device 10 requests the conference server device 12 for the recording data selected by the user. The information management unit 61 of the conference server device 12 returns the requested recording data to the conference client device 10.

  In step S 134, the terminal screen display input unit 53 of the conference client device 10 reproduces the recorded data returned from the conference server device 12. As described above, the conference client device 10 can acquire and reproduce the video recording data stored in the conference video recording information storage unit 66 of the conference server device 12.

  After playing back the recorded data, the user operates the conference client device 10 and logs out by requesting the conference server device 12 to log out. In step S136, the terminal screen display input unit 53 of the conference client device 10 deletes the recorded data acquired from the conference server device 12.

  The process of the information management unit 61 for selecting the information of the recorded data that can be reproduced by the user who has succeeded in the authentication is performed, for example, according to the procedure shown in FIG. FIG. 29 is a flowchart of an example of processing for selecting information of reproducible video data that a user who succeeded in authentication can reproduce.

  In step S151, the information management unit 61 of the conference server device 12 refers to the conference recording information in FIG. 23, and selects a record of the conference recording information set as the recording user by the user who has succeeded in authentication.

  In step S152, the information management unit 61 refers to the group information shown in FIG. 20, and specifies the group name to which the user who has succeeded in authentication belongs. For example, in the group information of FIG. 20, if the user name successfully authenticated is "AA", the group name "Group 1" is specified.

  In step S153, the information management unit 61 refers to the conference information in FIG. 22, and identifies the conference ID in which the group name identified in step S152 is set as the accessible group.

  In step S154, the information management unit 61 refers to the conference recording information in FIG. 23, and selects a record of the type “shared” among the records in which the conference ID identified in step S153 is set. The record selected in step S154 is information of recorded data that can be reproduced by the user who has succeeded in authentication.

  According to the flowchart of FIG. 29, the user who has succeeded in authentication can acquire and reproduce the recording data in which the shared screen is recorded among the records of the meeting recording information in which the group to which the user belongs is set as the accessible group. .

  Further, according to the flowchart of FIG. 29, the user who has succeeded in authentication can acquire and reproduce the recorded data of the personal screen 1000 recorded by the user. However, according to the flowchart of FIG. 29, the user who has succeeded in the authentication can not acquire and reproduce the recorded data of the personal screen 1000 recorded by others.

  In the recording list screen 1400 of FIG. 28, recording data of types “shared” and “individual” are mixed in the recording list 1401, but for example, a switching button changes the type of recording data displayed each time the button is pressed. May be provided. Further, the recording list screen 1400 in FIG. 28 may display a list of recordings of the type “shared” and a list of recordings of the type “personal” by, for example, a tag.

  In the sequence diagrams of FIGS. 26 and 27, recording data can be deleted from the meeting client device 10 by storing the recording data in the meeting server device 12. Since the conference client device 10 deletes the recorded data from its own device after logging out or uploading the recorded data, security is improved, for example, when the conference client device 10 is shared.

<Summary>
In the conference system 1 of the second embodiment, since the user who can record a conference can be controlled by the recording authority, the security can be improved. Further, in the conference system 1 of the second embodiment, access control to a moving image of a shared screen of a recorded conference or a personal screen can be performed. For example, in the conference system 1 of the second embodiment, the user can reproduce the video recording data recorded by another user belonging to the same group. Furthermore, in the conference system 1 of the second embodiment, the user can play back the recorded data with the conference client device 10 other than the conference client device 10 that has recorded the conference.

Third Embodiment
In the third embodiment, when an agenda is set for a meeting, management is performed to record a conference for each agenda. The third embodiment is the same as the first embodiment except for a part of the first embodiment, and thus the description will be appropriately omitted.

  FIG. 30 is a block diagram of an example of the conference information. The meeting information in FIG. 30 is stored in association with the meeting ID, the meeting name, the start date and time, the meeting state, and the presence or absence of an agenda. The conference ID is an example of identification information that uniquely identifies a conference. The meeting name is the name of the meeting. The start date and time is the date and time to start the meeting. The conference status indicates the status of the conference such as before, during or after the conference. The presence or absence of an agenda indicates the presence or absence of an agenda registration for the meeting.

  FIG. 31 is a block diagram of an example of the agenda information. The agenda information of FIG. 31 is stored, for example, in the meeting information storage unit 54. The agenda information in FIG. 31 includes an agenda ID, a meeting ID, an agenda name, a presenter, a presentation time, and the like. The agenda ID is an example of identification information that uniquely identifies an agenda. The conference ID is an example of identification information that uniquely identifies a conference.

  Each record of the agenda information is associated with the conference information of FIG. 30 by this conference ID. The agenda name is the name of the agenda. The presenter is the name of the presenter associated with the subject. The presentation time is the presentation time associated with the agenda.

  FIG. 32 is a block diagram of an example of meeting recording information. The meeting recording information in FIG. 32 stores the recording ID, the agenda ID, the recording user, the meeting ID, the recording start date, the recording end date, the type, and the recording data in association with one another. The meeting recording information of FIG. 32 is obtained by adding an agenda ID to the meeting recording information of FIG. The agenda ID is an example of identification information that uniquely identifies an agenda. Each record of the meeting recording information is associated with the agenda information of FIG. 31 by this agenda ID.

  In the third embodiment, the input operation of the presenter is notified, for example, by the reception of the XMPP command shown in FIG. FIG. 33 is a block diagram of an example of an XMPP instruction. The XMPP command in FIG. 33 includes an agenda ID. Therefore, the conference client device 10 that has received the XMPP command of FIG. 33 can detect that the agenda has changed due to the change of the agenda ID.

<< S14: Shared screen update process >>
The shared screen update process of step S14 is performed, for example, as shown in FIG. FIG. 34 is a flowchart of another example of shared screen update processing. In step S201, when the terminal screen display input unit 53 receives the input operation of the presenter by the XMPP command, the terminal screen display input unit 53 confirms whether there is a change in the agenda according to the agenda ID included in the XMPP command.

  If there is a change in the agenda, the terminal screen display input unit 53 proceeds to step S203 and updates the conference recording information of FIG. For example, the terminal screen display input unit 53 updates the record of the conference recording information corresponding to the agenda ID before the change. Further, the terminal screen display input unit 53 updates the record of the conference recording information corresponding to the changed agenda ID.

  After the process of step S203, or when there is no change in the agenda in step S202, the terminal screen display input unit 53 proceeds to step S204, and the page number constituting the screen information of the shared screen, the material display area, the handwritten memo Check if the information has changed.

  In step S205, if there is a change in the screen information of the shared screen, the terminal screen display / input unit 53 proceeds to step S206, and updates the screen information of the shared screen stored in the screen information storage unit 56. In step S207, the terminal screen display input unit 53 stores the update time and the update content of the shared screen in the conference recording information storage unit 55.

<< S54: Movie generation processing >>
The moving image generation process of step S54 is performed, for example, according to the procedure shown in FIG. FIG. 35 is a flowchart of another example of the moving image generation process. In step S210, the conference recording unit 58 generates an image of the updated shared screen.

  In step S211, the meeting recording unit 58 acquires the meeting recording information of FIG. 32 associated with the current agenda. In step S212, the conference recording unit 58 inserts the image generated in step S210 into the moving image at the timing of the update time of the shared screen stored in step S207.

  In the process of step S212, the generated moving image becomes the image generated in step S210 from the update time of the shared screen stored in step S207 to the next update of the shared screen. In step S213, the conference recording unit 58 inserts the metadata as shown in FIG. 13 into the moving image at the timing of the update time of the shared screen stored in step S207.

<< Video playback processing >>
The moving image on the shared screen of the conference stored as described above can be selected and reproduced from the conference record list as shown in FIG. 15, for example. On the conference record list screen 1100 of FIG. 15, a list of moving images of the shared screen of the conference recorded by the operation of the operator of the conference client apparatus 10 pressing the video recording button as described above is displayed.

  The operator of the conference client device 10 can display the agenda selection screen 1500 as shown in FIG. 36 by selecting the moving image of the shared screen of the conference to be reproduced from the conference recording list screen 1100 of FIG.

  FIG. 36 is an image diagram of an example of the agenda selection screen. The agenda selection screen 1500 of FIG. 36 displays a list of agendas corresponding to the meeting selected from the meeting record list screen 1100. The operator of the conference client device 10 can select an agenda on which a moving image of the conference sharing screen is to be reproduced on an agenda selection screen 1500 as shown in FIG. As described above, the operator of the conference client device 10 can select and play the moving image of the shared screen of the conference to be reproduced from the agenda selection screen 1500 of FIG. In the third embodiment, an example in which the moving image of the shared screen of the meeting is recorded on an agenda basis is described, but the moving image of the personal screen 1000 may be recorded on an agenda basis.

<Summary>
In the conference system 1 of the third embodiment, by switching the recording data for each agenda of the conference, it is possible to record the moving image of the shared screen of the conference and the personal screen 1000 for each agenda.

  The present invention is not limited to the above specifically disclosed embodiments, and various modifications and changes are possible without departing from the scope of the claims. The conference client device 10 is an example of a terminal device. The terminal screen display input unit 53 is an example of a screen display input unit. The conference recording unit 58 is an example of a screen recording unit. The conference system 1 is an example of an information processing system.

  The conference system 1 having the conference client device 10, the conference server device 12, and the conference display device 14 is merely an example, and it goes without saying that there are various system configuration examples depending on the application and purpose. The operation of pressing the recording button is an example of the screen recording operation. The input operation of the presenter distributed by XMPP is an example of operation information distributed to display the first screen. The presenter is an example of the first operator. The participant is an example of a second operator.

1 conference system 10 conference client device 12 conference server device 14 conference display device 51 control unit 52 communication unit 53 terminal screen display input unit 54 conference information storage unit 55 conference recording information storage unit 55a conference recording temporary storage unit 56 screen information storage unit 57 Login information request unit 58 conference recording unit 59 conference recording start end unit 61 information management unit 62 communication unit 63 conference information storage unit 64 group information storage unit 65 user information storage unit 66 conference recording information storage unit 501, 601 input device 502, 602 Display 503, 603 External I / F
503a, 603a Recording medium 504, 604 RAM (Random Access Memory)
505, 605 ROM (Read Only Memory)
506, 606 CPU (Central Processing Unit)
507, 607 Communication I / F
508, 608 HDD (Hard Disk Drive)
1000 personal screen 1001 recording button 1002 mode switching button 1003 presenter switching button 1100 meeting recording list screen 1200 playback screen 1201 video display area 1202 chapter information 1300 meeting registration screen 1400 recording list screen 1401 recording list 1500 agenda selection screen N1 network

JP, 2014-219807, A

Claims (12)

Switching between a first mode for displaying a first screen synchronized with another terminal device and a second mode for displaying a second screen asynchronously with the other terminal device by switching operation by the operator A terminal device,
When the mode switching operation between the first mode and the second mode by the operator is received, the first screen of the first mode or the second mode switched by the mode switching operation Screen display input means for displaying the second screen;
The screen recording operation by the operator is accepted, and the first screen of the first mode or the second screen of the second mode by the screen display input means is not displayed, but the first screen Screen recording means for recording the first screen or the second screen in each mode or the second mode;
A terminal device characterized by having. The screen recording means records the first screen of the mode 1, when the screen recording operation by the operator is received from the first screen or the second screen displayed by the screen display input means. The terminal device according to claim 1, wherein the terminal device is started. The screen recording means is a content for the screen display input means to display the first screen, and a distribution for displaying the first screen synchronized with the other terminal device in the first mode. The terminal device according to claim 2, wherein the first screen to be recorded is generated from the content based on operation information to be recorded. The screen recording means records the updated first screen and records a moving image from the time when the first screen of the first mode is updated to the time of the next update. The terminal device according to claim 3, characterized in that 5. The terminal device according to claim 4, wherein chapter information is inserted at a time when the first screen of the first mode is updated. When the screen recording unit receives the screen recording operation from the operator capable of performing the screen recording operation based on the information indicated by the operator capable of performing the screen recording operation, The terminal device according to any one of claims 1 to 5, wherein the screen of 1 or the second screen is recorded. The screen display input means displays the first screen and the second screen based on information indicated by the operator capable of displaying the first screen and the second screen. When the display request for the recorded first screen or the second screen is received from the operator that can be performed, the recorded first screen or the second screen is displayed. The terminal device according to any one of claims 1 to 6, wherein The screen display input means displays the first screen and the second screen based on information indicated by the operator capable of displaying the first screen and the second screen. When the display request for the second screen recorded by the operator is received by the screen recording operation from the operator that can be performed, the recorded second screen is displayed. The terminal device according to any one of 1 to 6. The screen recording unit is configured to receive the screen recording operation of the first screen or the second screen of a meeting in which one or more agendas are registered from the operator. The terminal device according to any one of claims 1 to 5, wherein the screen of is recorded in the unit of the agenda. Switching between a first mode for displaying a first screen synchronized with another terminal device and a second mode for displaying a second screen asynchronously with the other terminal device by switching operation by the operator A screen recording method executed in a terminal device, comprising:
When the mode switching operation between the first mode and the second mode by the operator is received, the first screen of the first mode or the second mode switched by the mode switching operation A screen display input step of displaying the second screen;
The screen recording operation by the operator is received, and the first screen of the first mode or the second screen of the second mode is not displayed by the screen display input step. A screen recording step of recording the first screen or the second screen in each mode or the second mode;
A screen recording method characterized by comprising: Switching between a first mode for displaying a first screen synchronized with another terminal device and a second mode for displaying a second screen asynchronously with the other terminal device by switching operation by the operator Terminal device,
When the mode switching operation between the first mode and the second mode by the operator is received, the first screen of the first mode or the second mode switched by the mode switching operation Screen display input means for displaying the second screen;
The screen recording operation by the operator is accepted, and the first screen of the first mode or the second screen of the second mode by the screen display input means is not displayed, but the first screen Screen recording means for recording the first screen or the second screen for each mode or the second mode,
Program to function as. Switching between a first mode for displaying a first screen synchronized with another terminal device and a second mode for displaying a second screen asynchronously with the other terminal device by switching operation by the operator An information processing system including one or more terminal devices, wherein
A first terminal device operated by a first operator capable of updating the first screen;
A second terminal device operated by a second operator other than the first operator;
The second terminal device is
The first screen or the second of the first mode in the first mode switched by the mode switching operation upon receiving a mode switching operation between the first mode and the second mode by the second operator. Screen display input means for displaying the second screen in the mode of
The screen recording operation by the second operator is received, and the first screen of the first mode or the second screen of the second mode by the screen display input means is not displayed Screen recording means for recording the first screen or the second screen in each of the first mode or the second mode;
An information processing system characterized by having.

Images