JP2016099773A - Terminal device, reproduction method, program, and image sharing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a terminal device that can reproduce an operation performed to information on a shared screen at an arbitrary timing.SOLUTION: There is provided a terminal device sharing a screen with another terminal device via an information processing apparatus that distributes the details of an operation that has been performed, to information on a shared screen, by a user having authority fo perform an operation to the information on the shared screen, the terminal device including: requesting means for requesting operation history information from the information processing apparatus that stores, as the operation history information, the details of the operation that has been performed by the user having the authority to the information on the shared screen; and reproduction means for reproducing the details of the operation that has been performed by the user having the authority to the information on the shared screen on the basis of the operation history information received from the information processing apparatus.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a terminal device, a playback method, a program, and a screen sharing system.

  For example, in order to reproduce a meeting or a presentation, it is generally performed to record a meeting situation or a presentation with a video camera, and also record a voice during a meeting and a voice of a presentation collected by a microphone.

  Conventional information playback devices store electronic documents of materials presented at meetings and presentations, and when moving images and audio are played back, electronic document materials can be stored at the same timing as presented at meetings. Some of them are displayed synchronously (for example, see Patent Document 1).

  A screen sharing system that performs screen sharing in a plurality of terminal devices does not have the authority of the participant or the like for the operation performed by the user on the information displayed on the terminal device of the user who has the authority of the presenter or the like There is a case where the user terminal device is synchronously displayed. In such a conventional screen sharing system, it is convenient if an authorized user or an unauthorized user can reproduce an operation performed on information by an authorized user at an arbitrary timing.

  Embodiments of the present invention have been made in view of the above points, and an object thereof is to provide a terminal device that can reproduce an operation performed on information on a shared screen at an arbitrary timing.

  In order to achieve the above object, claim 1 of the present application provides information processing for distributing, as operation information, the content of an operation performed on information on a shared screen by a user who has the authority to operate on the information on the shared screen The information processing, which is a terminal device that performs screen sharing with another terminal device via the device, and that stores the contents of operations performed on information on the shared screen by the authorized user as operation history information Based on the operation history information received from the information processing apparatus and the request means for requesting the operation history information to the apparatus, the content of the operation performed on the information on the shared screen by the authorized user is reproduced. And a reproducing means.

  According to the embodiment of the present invention, an operation performed on information on a shared screen can be reproduced at an arbitrary timing.

It is a lineblock diagram of an example of a conference system concerning this embodiment. It is a hardware block diagram of an example of the computer which concerns on this embodiment. It is a functional block diagram of an example of a conference server apparatus. It is a functional block diagram of an example of a client terminal. It is a block diagram of an example of a presentation information table. It is an image figure which shows an example of the process outline | summary of the conference system which concerns on this embodiment. It is a flowchart of an example of a presentation information registration process. It is a flowchart of an example of the reproduction process of the operation which the presenter performed. It is an image figure of an example of the meeting screen displayed on a client terminal. It is a flowchart of the other example of the reproduction | regeneration processing of operation which the presenter performed. It is a flowchart of the other example of the reproduction | regeneration processing of operation which the presenter performed. It is a flowchart of an example in the case of performing the reproduction | regeneration process of the operation which the presenter performed after the meeting. It is a flowchart of the other example when performing the reproduction | regeneration process of the operation which the presenter performed after the meeting.

Next, embodiments of the present invention will be described in detail. In the present embodiment, the conference system 1 as an example of the screen sharing system will be described, but the present invention is not limited to the conference system 1.
[First Embodiment]
<System configuration>
FIG. 1 is a configuration diagram of an example of a conference system according to the present embodiment. The conference system 1 in FIG. 1 shows an example of a configuration in which a conference server device 10 and a plurality of client terminals 12 are connected to a network N1 such as a LAN.

  The conference server device 10 accepts a conference registration request, a material registration request, and the like, and stores conference information and material information. In addition, the conference server device 10 performs conference holding and participation control. The conference server apparatus 10 can be realized by software or services that operate on one or more computers. The conference server device 10 can also take the form of a so-called cloud service. The conference server device 10 is realized by, for example, a device dedicated to the conference system 1 or an information processing device such as a general workstation or PC.

  The client terminal 12 has a function of registering conference information in the conference server device 10 and a function of displaying a conference list and materials. Note that the client terminal 12 may limit functions that can be used depending on the authority of the user.

  The client terminal 12 may be a PC, a tablet terminal, a smartphone, a mobile phone, a terminal device such as a PDA, a virtual machine, a projector, an electronic blackboard, or a device dedicated to the conference system 1. The application that runs on the client terminal 12 may be a native application, a web browser, and a web application that runs on the web browser.

  The client terminal 12 has a function of acquiring conference information from the conference server device 10 and participating in the conference. Note that in the conference system 1, any user participating in the conference may be a presenter.

  During the conference, the client terminal 12 displays the material. While the client terminal 12 participates in the conference, the same material as the other client terminals 12 is displayed. The client terminal 12 can receive the operation performed by the presenter at the other client terminal 12 from the conference server device 10 in real time, and can share the display screen with the other client terminal 12. The operations performed by the presenter on the display screen include page turning, enlargement / reduction of the display range, movement of the display range, handwriting input, and the like.

  For example, when the document page is turned on the client terminal 12 of the presenter, the page of the document is turned on the client terminal 12 other than the presenter, and the same screen is shared. When the display range of the material is enlarged or reduced at the client terminal 12 of the presenter, the display range of the material is also enlarged or reduced at the client terminal 12 other than the presenter, and the same screen is shared.

  Further, when a handwriting input such as drawing a mark or a line or adding a character by a touch pen or mouse operation is performed on the client terminal 12 of the presenter, it is reflected on the screen of the client terminal 12 of the participant.

  In the conference system 1, the conference server device 10 and the client terminal 12 can perform data communication via the network N1. The network N1 may be the Internet, a dedicated line, a wired line, or a wireless line in addition to the LAN.

<Hardware configuration>
The conference server device 10 and the client terminal 12 are realized by a computer 100 having a hardware configuration as shown in FIG. 2, for example. FIG. 2 is a hardware configuration diagram of an example of a computer according to the present embodiment.

  The computer 100 shown in FIG. 2 includes an input device 101, a display device 102, an external I / F 103, a RAM 104, a ROM 105, a CPU 106, a communication I / F 107, an HDD 108, and the like, which are connected to each other via a bus B. . The input device 101 and the display device 102 may be connected and used when necessary.

  The input device 101 includes a keyboard, a mouse, a touch panel, and the like, and is used by a user to input each operation signal. The display device 102 includes a display and the like, and displays a processing result by the computer 100.

  The communication I / F 107 is an interface that connects the computer 100 to various networks. Thereby, the computer 100 can perform data communication via the communication I / F 107.

  The HDD 108 is an example of a nonvolatile storage device that stores programs and data. The stored programs and data include an OS that is basic software for controlling the entire computer 100, and application software that provides various functions on the OS (hereinafter simply referred to as an application). The computer 100 may use a drive device (for example, a solid state drive: SSD) that uses a flash memory as a storage medium instead of the HDD 108.

  The external I / F 103 is an interface with an external device. The external device includes a recording medium 103a. Accordingly, the computer 100 can read and / or write the recording medium 103a via the external I / F 103. Examples of the recording medium 103a include a flexible disk, a CD, a DVD, an SD memory card, and a USB memory.

  The ROM 105 is an example of a nonvolatile semiconductor memory (storage device) that can retain programs and data even when the power is turned off. The ROM 105 stores programs and data such as BIOS, OS settings, and network settings that are executed when the computer 100 is started up. The RAM 104 is an example of a volatile semiconductor memory (storage device) that temporarily stores programs and data.

  The CPU 106 is an arithmetic unit that realizes control and functions of the entire computer 100 by reading a program and data from a storage device such as the ROM 105 and the HDD 108 onto the RAM 104 and executing processing.

  The conference server apparatus 10 and the client terminal 12 can implement various processes as described later by executing a program on the computer 100 having the above-described hardware configuration, for example.

<Software configuration>
The conference server device 10 and the client terminal 12 of the conference system 1 according to the present embodiment are realized by the following functional blocks.

<Conference server device>
The conference server device 10 is realized by functional blocks as shown in FIG. 3, for example. FIG. 3 is a functional block diagram of an example of the conference server apparatus. In addition, the functional block of FIG. 3 has shown about the function required for description of this embodiment among the functions which the conference server apparatus 10 provides, and another function may exist.

  The conference server apparatus 10 implements the communication server unit 20 and the database 30 by executing the program. The communication server unit 20 includes a conference management unit 21 and a presentation information management unit 22. The database 30 includes a conference information storage unit 31 and a presentation information storage unit 32.

  The communication server unit 20 communicates with the client terminal 12. The conference management unit 21 provides conference information to the client terminal 12. In addition, the conference management unit 21 uses the conference information to control the provision of materials, the holding and termination of the conference, the sharing of the display screen on the client terminal 12 participating in the conference, and the like.

  The presentation information management unit 22 receives operation information (presentation information) performed by the presenter at the client terminal 12 from the presenter's client terminal 12 and stores it in the database 30. In addition, when the presentation information management unit 22 receives a request for presentation information from the client terminal 12 of the presenter or participant, the presentation information is read from the database 30 and transmitted to the client terminal 12 of the presenter or participant.

  The database 30 stores various information necessary for the conference server device 10. The meeting information storage unit 31 stores meeting information. The presentation information storage unit 32 stores presentation information. Details of the presentation information will be described later.

<Client terminal>
The client terminal 12 is realized by, for example, functional blocks as shown in FIG. FIG. 4 is a functional block diagram of an example of a client terminal. Note that the functional blocks in FIG. 4 show the functions necessary for the description of the present embodiment among the functions provided by the client terminal 12, and other functions may exist.

  The client terminal 12 implements an event detection unit 40, an information management unit 41, a communication client unit 42, and a drawing management unit 43 by executing a program. The communication client unit 42 includes a request execution unit 51 and a response reception unit 52.

  The event detection unit 40 detects a user operation on the client terminal 12 as an event. The information management unit 41 manages information such as conference information necessary for screen sharing. The communication client unit 42 communicates with the conference server device 10.

  The request execution unit 51 executes a request to the conference server device 10. For example, the request execution unit 51 requests presentation information. The response receiving unit 52 receives a response to the request from the conference server device 10. For example, the response receiving unit 52 receives presentation information from the conference server device 10 as a response to the request.

  The drawing management unit 43 changes display contents. For example, the drawing management unit 43 shares the screen by changing the display content according to the presentation information of the operation performed on the client terminal 12 of the presenter received from the conference server device 10 during the conference. In addition, the drawing management unit 43 reproduces the operation performed on the material on the shared screen at an arbitrary timing by changing the display content according to the presentation information acquired from the conference server device 10 at an arbitrary timing. it can.

  Note that the functional blocks shown in FIGS. 3 and 4 are examples. For example, some of the functional blocks included in the conference server apparatus 10 in FIG. 3 may operate on another information processing apparatus. In that case, the functional blocks communicate with each other as necessary to exchange information.

《Presentation information》
For example, presentation information shown in FIG. 5 is stored in the presentation information storage unit 32. FIG. 5 is a configuration diagram of an example of the presentation information table. The presentation table of FIG. 5 stores presentation information that is information on operations performed on materials on the shared screen.

  The presentation information in FIG. 5 includes items such as conference ID, page number, coordinates, type, and elapsed time. The conference ID is an example of identification information for uniquely identifying a conference. The page number is a serial number representing the page of the material that is screen-shared at the conference. The coordinates represent coordinates on the shared screen. Note that the contents of coordinates differ depending on the type of operation. The type represents the type of operation performed on the client terminal 12 of the presenter. The elapsed time represents the start time and duration of the operation.

  In the presentation information of FIG. 5, the conference ID and page number are examples of information (operation target specifying information) for specifying a target operated by the presenter. The coordinates, type, and elapsed time are examples of information (operation content specifying information) that specifies the content of the operation performed by the presenter.

For example, the presentation information in FIG. 5 represents the following operations performed at the client terminal 12 of the presenter.
(1) The presenter displays the page of the page number “1” of the conference material with the conference ID “1001”, and is at the coordinate position on the upper left of the screen over 0.5 seconds after 3.0 seconds (0, Zoom in to a magnification of 1.2 using 0) as a fulcrum.
(2) Display the page with the page number “1”, and move the display position of the material by 10 vertically and horizontally to the lower right of the screen over 0.5 seconds after 4.0 seconds.
(3) The page number “1” is displayed, and after 10.0 seconds, the coordinate positions (100, 112), (110, 114), (119, 113) on the material are taken over 0.5 seconds. A line (stroke) passing through (125, 113) and (134, 114) is drawn.

  As described above, the presentation information stores information for reproducing the operation performed by the presenter on the client terminal 12 with respect to the material specified by the conference ID and the page number at an arbitrary timing.

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

<< Outline of processing of conference system according to this embodiment >>
FIG. 6 is an image diagram showing an example of a processing outline of the conference system according to the present embodiment. FIG. 6 shows the conference server device 10, the presenter's client terminal 12a, the participant's client terminal 12b whose screen is not shared, and the participant's client terminal 12c whose screen is shared.

  The presenter's client terminal 12 a transmits operation information performed by the presenter to the conference server apparatus 10 for the material whose screen is being shared. The conference server apparatus 10 transmits the received operation information to the client terminal 12c of the participant who is sharing the screen in real time. The client terminal 12c of the participant who is sharing the screen can share the screen with the client terminal 12a of the presenter by changing the display contents according to the received operation information.

  The conference server apparatus 10 stores the received operation information as presentation information as shown in FIG. The client terminal 12b of the participant who is not sharing the screen requests presentation information from the conference server apparatus 10 at an arbitrary timing, and receives the presentation information from the conference server apparatus 10. The client terminal 12b of the participant who is not sharing the screen can reproduce the operation performed by the presenter on the material sharing the screen at any timing by changing the display content according to the received presentation information.

<< Presentation information registration process >>
The presenter's client terminal 12a registers the presentation information in the conference server apparatus 10 in the procedure as shown in FIG. FIG. 7 is a flowchart of an example of the presentation information registration process.

  In step S11, when the event detection unit 40 detects an operation by the user, the client terminal 12a performs the processing from step S12 onward. In step S12, the information management unit 41 of the client terminal 12a determines whether the user who performed the operation is a presenter.

  Since the operation by the user is invalid if the presenter is not a presenter, the processing in FIG. 7 is terminated. Here, since an example in which an operation by a user is detected in the presenter's client terminal 12a is described, it is determined that the user who performed the operation is a presenter, and the processes in and after step S13 are performed.

  In step S <b> 13, the request execution unit 51 of the communication client unit 42 makes an operation information transmission request to the conference server device 10. In step S14, the drawing management unit 43 changes the display content according to the operation performed by the presenter.

  In response to the operation information transmission request made in step S13, the presentation information management unit 22 of the conference server apparatus 10 can store the presenter's operation information as presentation information in the presentation information storage unit 32. In addition, the conference management unit 21 of the conference server apparatus 10 transmits the operation information of the presenter to the client terminal 12c that is sharing the screen to share the screen.

《Playback of operations performed by the presenter》
The client terminal 12b of the participant who is not sharing the screen can reproduce the operation performed by the presenter on the material sharing the screen at any timing by receiving presentation information from the conference server device 10 at any timing. . Various timings may be considered when the client terminal 12b of the participant who is not sharing the screen receives the presentation information from the conference server device 10.

  FIG. 8 is a flowchart of an example of a reproduction process of an operation performed by the presenter. In the flowchart shown in FIG. 8, the client terminal 12b receives the presentation information at the timing when the display state is switched from screen sharing to screen non-sharing, and the client terminal 12b reproduces the operation performed by the presenter.

  In step S21, the event detection unit 40 of the client terminal 12b detects switching of the display state from screen sharing to screen non-sharing. In step S <b> 22, the information management unit 41 notifies the communication client unit 42 of the conference ID and page number for specifying the page of the currently displayed material. The request execution unit 51 specifies the conference ID and the page number, and requests the conference server device 10 for presentation information on the page of the currently displayed material.

  In step S23, the presentation information management unit 22 of the conference server apparatus 10 receives a request for presentation information specifying the conference ID and page number from the client terminal 12b. The presentation information management unit 22 selects presentation information that matches the designated conference ID and page number from the presentation information of FIG. Then, the presentation information management unit 22 of the conference server device 10 transmits the selected presentation information as a response to the client terminal 12b.

  In step S24, the response receiving unit 52 of the client terminal 12b receives presentation information from the conference server apparatus 10 as a response. The drawing management unit 43 of the client terminal 12b changes the display content according to the presentation information of the currently displayed document page.

  According to the processing of the flowchart of FIG. 8, the client terminal 12b performs an operation performed on the currently displayed material by the presenter at the timing when the display state is switched from screen sharing to screen non-sharing during the conference. Can play.

  The process of the flowchart of FIG. 8 receives presentation information from the conference server device 10 at the timing when the display state is switched from screen sharing to screen non-sharing. Reception of presentation information from the conference server apparatus 10 may be performed at a timing when a playback button provided on the conference screen is pressed as shown in FIG. 9, for example. FIG. 9 is an image diagram of an example of a conference screen displayed on the client terminal.

  FIG. 9A shows an example of a conference screen on which a playback button 1001 is provided. FIG. 9B is an example of a conference screen on which a stop button 1002 is provided. The conference screens in FIGS. 9A and 9B are provided with a screen sharing / non-sharing switching button 1003 and a material display area 1004.

  FIG. 9A shows a state before the reproduction of the operation performed by the presenter on the material displayed in the material display area 1004 is started. FIG. 9B shows a state after the reproduction of the operation performed by the presenter on the material displayed in the material display area 1004 is started.

  When the play button 1001 in FIG. 9A is pressed by the participant, the client terminal 12b transitions to the conference screen in FIG. 9B, and the presenter displays the material displayed in the material display area 1004. Start playing the performed operation. When the stop button 1002 in FIG. 9B is pressed by the participant, the client terminal 12b transitions to the conference screen in FIG. 9A and announces the material displayed in the material display area 1004. Stops playback of operations performed by the user.

  When the playback button 1001 is used, a flowchart of the playback process of the operation performed by the presenter is as shown in FIG. FIG. 10 is a flowchart of another example of the reproduction process of the operation performed by the presenter. Note that the flowchart of FIG. 10 is the same as the flowchart of FIG.

  In the flowchart of FIG. 10, the process of step S32 is provided between steps S31 and S33 corresponding to steps S21 and S22 of the flowchart of FIG. The process of step S32 determines whether or not the playback button 1001 shown in FIG. 9A has been pressed, for example.

  When the play button 1001 is pressed by the participant, the client terminal 12b performs the processing after step S33, and the material displayed in the material display area 1004 is processed in the same procedure as the processing after step S22 in FIG. Playback of the operation performed by the presenter is started. According to the processing of the flowchart of FIG. 10, when a participant explicitly presses the playback button 1001 during a conference, playback of an operation performed by the presenter on the currently displayed material can be started. . In addition, during the conference, at the timing when the participant explicitly presses the stop button 1002, playback of the operation performed by the presenter on the currently displayed material can be stopped.

  Further, after the processing of the flowcharts of FIGS. 8 and 10, presentation information from the conference server device 10 may be received at the page turning timing as shown in FIG. 11, for example. FIG. 11 is a flowchart of another example of the reproduction process of the operation performed by the presenter. The flowchart in FIG. 11 is the same as the flowchart in FIG.

  When the participant turns the page of the material displayed on the client terminal 12b and switches the page of the material, the event detection unit 40 of the client terminal 12b detects the page turning by the participant in step S41.

  When the event detection unit 40 detects a page turn by a participant, the client terminal 12b performs the processing from step S42 onward, and performs the same procedure as the processing from step S22 onward in FIG. Playback of the operation performed by the presenter is started.

  According to the processing of the flowchart of FIG. 11, reproduction of an operation performed by the presenter on the switched material page can be started each time a page turning by a participant is detected during a conference.

  8, 10, and 11 receives presentation information from the conference server device 10 during a conference. Reception of presentation information from the conference server apparatus 10 may be performed after the conference as shown in FIG. 12, for example.

  FIG. 12 is a flowchart illustrating an example of a case where the reproduction process of the operation performed by the presenter is performed after the conference. Note that the flowchart of FIG. 12 is the same as the flowchart of FIG.

  After the meeting, the participant requests the client terminal 12 to reproduce the operation performed by the presenter on the material during the meeting. Note that the reproduction of the operation performed by the presenter on the material may be started, for example, by pressing the reproduction button 1001 or turning the page.

  In step S51, the event detection unit 40 of the client terminal 12 detects a request for reproduction of an operation performed by the presenter on the material. The information management unit 41 of the client terminal 12 notifies the communication client unit 42 of the conference ID and page number for specifying the page of the currently displayed material.

  In step S <b> 52, the presentation information management unit 22 of the conference server apparatus 10 receives a request for presentation information specifying the conference ID and page number from the client terminal 12. The presentation information management unit 22 selects presentation information that matches the designated conference ID and page number from the presentation information of FIG. Then, the presentation information management unit 22 of the conference server device 10 transmits the selected presentation information to the client terminal 12 as a response.

  In step S <b> 53, the response receiving unit 52 of the client terminal 12 receives presentation information as a response from the conference server device 10. The drawing management unit 43 of the client terminal 12 changes the display content according to the presentation information of the currently displayed document page.

  According to the processing of the flowchart of FIG. 12, even after the meeting, the operation performed by the presenter on the currently displayed material can be reproduced. In the processing of the flowchart of FIG. 12, presentation information is received from the conference server device 10 for each page of the material. Reception of presentation information from the conference server apparatus 10 may be performed for each document as shown in FIG.

  FIG. 13 is a flowchart of another example when the reproduction process of the operation performed by the presenter is performed after the conference. The flowchart in FIG. 13 is the same as the flowchart in FIG.

  After the meeting, the participant requests the client terminal 12 to reproduce the operation performed by the presenter on the material during the meeting. Note that the reproduction of the operation performed by the presenter on the material may be started, for example, by pressing the reproduction button 1001 or turning the page.

  In step S61, the event detection unit 40 of the client terminal 12 detects a request for reproduction of an operation performed by the presenter on the material. The information management unit 41 of the client terminal 12 notifies the communication client unit 42 of a conference ID for identifying the currently displayed document page.

  In step S <b> 62, the presentation information management unit 22 of the conference server apparatus 10 receives a request for presentation information specifying a conference ID from the client terminal 12. The presentation information management unit 22 selects presentation information that matches the designated conference ID from the presentation information of FIG. Then, the presentation information management unit 22 of the conference server device 10 transmits the selected presentation information to the client terminal 12 as a response.

  In step S63, the response receiving unit 52 of the client terminal 12 receives presentation information as a response from the conference server device 10 for each material. The drawing management unit 43 of the client terminal 12 changes the display content at a timing corresponding to the elapsed time of the presentation information of the currently displayed material.

  According to the process of the flowchart of FIG. 13, even after the meeting, the operation performed by the presenter on the currently displayed material can be reproduced. In the process of the flowchart of FIG. 13, presentation information is received from the conference server device 10 for each document, and the display content is changed at a timing corresponding to the elapsed time of the presentation information on the client terminal 12 side.

  For example, in the conference system 1 according to the present embodiment, if the operation information is distributed to the client terminals 12 participating in the conference as the conference server device 10 is performing during the conference, according to the presentation information in FIG. You can create an action by the presenter even after the meeting.

  Note that the conference system 1 according to the present embodiment can share the display screen by distributing the operation performed by the presenter from the conference server device 10 to the client terminals 12 participating in the conference. For example, the conference server apparatus 10 and the client terminal 12 exchange information necessary for sharing the display screen using the established communication path. A typical example of such a communication path is a protocol called XMPP.

  XMPP is standardized as RFC 3920 (Extensible Messaging and Presence Protocol: Core) and RFC 3921 (Extensible Messaging and Presence Protocol: Instant Messaging and Presence) in IETF, and the extended specification is documented as XEP.

  XMPP can provide a service called group chat (Multi-User Chat [XEP-0045]). The group chat is a message sent from the client terminal 12 participating in the conference room (room) provided by XMPP to the conference server device 10 and all the client terminals 12 participating in the conference room from the conference server device 10. It is a function delivered to. In addition to XMPP, for example, protocols such as BOSH, WebSocket, and Comet, which are extensions of XMPP, can be used as such communication paths.

  BOSH (Bidirectional-streams Over Synchronous HTTP) [XEP-0206] is a technique for transmitting and receiving messages using HTTP in XMPP. These protocols can realize the Push function from the conference server device 10. The Push function is a function of receiving information from the conference server apparatus 10 asynchronously to the client terminal 12 and receiving the information at the client terminal 12 instead of receiving information from the client terminal 12 and sending information. In general HTTP communication, a similar function can be realized by periodically retrieving information from the client terminal 12.

(Summary)
In the conference system 1 according to the present embodiment, presentation information in which operations performed by a presenter on a material whose screen is shared during a conference is stored in the conference server device 10. When the client terminal 12 accepts an operation such as turning the page or pressing the play button 1001, the client terminal 12 can obtain presentation information from the conference server device 10 and reproduce the operation by the presenter.

  In the conference system 1 of the present embodiment, as shown in FIG. 5, the operation information and the elapsed time are stored in association with the conference ID and the page number, so that presentation information can be transmitted to the client terminal 12 for each page. . Therefore, in the conference system 1 of the present embodiment, the client terminal 12 can acquire presentation information page by page (partial) and reproduce operations performed by the presenter on the material during the conference.

  Further, in the conference system 1 of the present embodiment, presentation information is stored in the conference server device 10 every time the presenter performs an operation on the material for which the screen is shared, so that the client terminal 12 receives the presentation information during the conference. Acquire and play the presenter's operations.

  As described above, according to the conference system 1 of the present embodiment, the operations performed by the presenter on the materials sharing the screen can be reproduced and confirmed at an arbitrary timing, so that the understanding of the content of the conference can be deepened. It can be carried out.

  The present invention is not limited to the specifically disclosed embodiments, and various modifications and changes can be made without departing from the scope of the claims. Although the conference system 1 is shown as an example in the present embodiment, the present invention can be applied to other systems that display information such as lectures and classes such as seminar systems and education systems.

  For example, the conference server device 10 is an example of an information processing device. The client terminal 12 is an example of a terminal device described in the claims. The presenter is an example of a user who has the authority to operate information on the shared screen. Presentation information is an example of operation history information. The request execution unit 51 is an example of a request unit. The drawing management unit 43 is an example of a reproducing unit. The elapsed time is an example of time information.

  Note that the conference system 1 having the conference server device 10 and one or more client terminals 12 is merely an example, and it goes without saying that there are various system configuration examples depending on applications and purposes.

DESCRIPTION OF SYMBOLS 1 Conference system 10 Conference server apparatus 12, 12a-12c Client terminal 20 Communication server part 21 Conference management part 22 Presentation information management part 30 Database 31 Conference information storage part 32 Presentation information storage part 40 Event detection part 41 Information management part 42 Communication Client unit 43 drawing management unit 51 request execution unit 52 response reception unit 100 computer 101 input device 102 display device 103 external I / F
103a Recording medium 104 RAM (Random Access Memory)
105 ROM (Read Only Memory)
106 CPU (Central Processing Unit)
107 Communication I / F
108 HDD (Hard Disk Drive)
1001 Play button 1002 Stop button 1003 Screen sharing / non-sharing switching button 1004 Document display area B Bus N1 Network

Japanese Patent No. 3637937

Claims (11)

Screen sharing with other terminal devices is performed via an information processing device that distributes the contents of operations performed on the information on the shared screen as operation information by a user who has the authority to operate the information on the shared screen. A terminal device,
Requesting means for requesting the operation history information to the information processing apparatus that stores, as operation history information, the contents of an operation performed by the authorized user on the information on the shared screen;
A terminal device comprising: reproduction means for reproducing the content of an operation performed on information on a shared screen by an authorized user based on the operation history information received from the information processing apparatus. The operation history information includes operation target specifying information for specifying an object operated by the authorized user, and operation content specifying information for specifying the content of the operation performed by the authorized user,
The reproduction means reproduces the content of an operation performed on information on a shared screen by an authorized user based on time information when the operation was performed included in the operation content specifying information. The terminal device according to claim 1.   The requesting unit detects when a switching from a shared screen that shares a screen with another terminal device to a non-shared screen that does not share a screen with another terminal device is detected until the distribution of the operation information ends. The terminal device according to claim 1, wherein the operation history information is requested.   After the request means detects a switching from a shared screen that shares a screen with another terminal device to a non-shared screen that does not share a screen with another terminal device until distribution of the operation information ends. The terminal device according to claim 1, wherein the operation history information is requested at a timing when an instruction to start reproduction by the reproduction unit is explicitly indicated by a user.   2. The request unit requests the operation history information at a timing when an instruction to start reproduction by the reproduction unit is explicitly indicated by a user after distribution of the operation information is completed. Or the terminal device of 2.   The terminal device according to claim 5, wherein the request unit requests the operation history information until the distribution of the operation information is finished or for each page.   The requesting unit requests the operation history information of the displayed page at a timing when a page turning operation by a user operating the terminal device is detected with respect to information operated by the authorized user. The terminal device according to claim 1, wherein:   The shared screen is a conference screen, and the reproduction means reproduces the contents of an operation performed by a user having the authority to change the display of the material on the conference screen. The terminal device according to claim 1. Screen sharing with other terminal devices is performed via an information processing device that distributes the contents of operations performed on the information on the shared screen as operation information by a user who has the authority to operate the information on the shared screen. A playback method executed in a terminal device,
Requesting the operation history information to the information processing apparatus that stores, as operation history information, the contents of an operation performed by the authorized user on information on a shared screen;
A reproduction method comprising: a reproduction step of reproducing the content of an operation performed on information on a shared screen by an authorized user based on the operation history information received from the information processing apparatus. Screen sharing with other terminal devices is performed via an information processing device that distributes the contents of operations performed on the information on the shared screen as operation information by a user who has the authority to operate the information on the shared screen. Terminal device
Request means for requesting the operation history information to the information processing apparatus that stores the contents of operations performed on the information on the shared screen by the authorized user as operation history information;
A program for causing a user having the authority to function as a playback unit that plays back content of an operation performed on information on a shared screen based on the operation history information received from the information processing apparatus. An information processing apparatus that distributes the contents of an operation performed on information on the shared screen as operation information by a user who has authority to operate the information on the shared screen, and another terminal via the information processing apparatus A screen sharing system having a device and a terminal device for screen sharing,
Operation history information management means for storing, as operation history information, contents of operations performed by the authorized user on information on a shared screen received as operation information from a terminal device operated by the authorized user;
Request means for requesting the operation history information to the operation history information management means;
A screen sharing system having playback means for playing back the content of an operation performed on information on a shared screen by the authorized user on the terminal device based on the operation history information received from the operation history information management means .

Images