The present invention relates to an information processing system, an information processing apparatus, and a screen-sharing terminal controlling method.
In recent years, there has been growing use of an electronic conference system, such as a paperless conference system using digitalized handouts, which is displayed on a terminal such as a tablet terminal and a laptop personal computer (PC) used by a participant at a conference or a seminar. In such an electronic conference system, a conference or a seminar can be conducted more effectively if a displayed page and memos of a terminal used by a presenter are synchronized on terminals used by participants.
For example, there is a display-sharing service providing system known in the art, in which information processing apparatuses prepare common display content in advance and transmit and receive information indicative of operations entered by users, so that the information processing apparatuses can share, by use of a small amount of data, a displayed screen that is updated based on the entered operation (see PTL 1, for example).
In the conventional electronic conference system that transmits and receives information indicative of operations, a handout to be used needs to be downloaded to a terminal before a conference or a seminar (hereinafter simply referred to as a conference) is started. To download a handout to a terminal, a participant needs to operate the terminal by him/herself or an organizer of the conference needs to directly operate the terminal of the participant. Further, in addition to downloading, the same is true for operations such as joining a conference, leaving a conference, or replacing a handout.
However, when asking participants to enter such operations, an organizer of the conference may have needed to give explanation about how to operate the terminal to participants who participate in a conference for the first time, which is troublesome to the organizer. Further, in a case where an organizer of a conference directly operates participants' terminals to enter such operations, a burden for the organizer of the conference is increased with the number of handouts or the number of participants.
The embodiments of the present invention are provided in view of the above problem, and therefore aim to provide an information processing system for controlling a screen-sharing terminal to perform a process based on an instruction provided from an administrator terminal.
As a solution to the above problem, one aspect of the present invention provides an information processing system including: an information processing apparatus configured to manage sharing of a screen performed by a plurality of screen-sharing terminals coupled communicably to the information processing apparatus; and an administrator terminal configured to have administrative authority and to be coupled to the information processing apparatus via a network. The information processing apparatus includes an information management unit configured to manage information related to the plurality of screen-sharing terminals coupled communicably to the information processing apparatus, and an instruction delivery unit configured to deliver, to an instruction destination, an instruction transmitted from the administrator terminal, the instruction causing the plurality of screen-sharing terminals to perform a process. The administrator terminal includes an accepting unit configured to accept an operation from a user to select, as the instruction destination, at least one screen-sharing terminal from among the plurality of screen-sharing terminals coupled communicably to the information processing apparatus and to select a process to be performed by the selected at least one screen-sharing terminal, and a communication control unit configured to transmit, to the information processing apparatus, an instruction for causing the at least one screen-sharing terminal to perform the process selected by the user, the at least one screen-sharing terminal having been selected as the instruction destination by the user.
According to the embodiments of the present invention, a burden for an organizer of a conference, etc., may be reduced, as a screen-sharing terminal is controlled to perform a process based on an operation provided from an administrator terminal.
The following description explains embodiments of the present invention in detail. Although a conference system is taken as an example in the embodiments, the present invention is applicable to another system for sharing a screen displaying a handout, such as a seminar system, a presentation system, an orientation system, or an education system.
<System Configuration>
The conference server device 10 accepts a request for registering a conference, a handout, etc., to be stored as conference information. Further, the conference server device 10 controls to start a conference or controls participation in a conference. The conference server device 10 may be actualized by a software program or a service that can be operated on one or more computers. Further, the conference server device 10 may be actualized in a format of what is referred to as a cloud service. The conference server device 10 may be actualized, for example, by a device dedicated to the conference system 1, a general work station or an information processing apparatus such as a PC, etc.
Client terminals 12 include an administrator terminal operated by an administrator of a conference and a participant terminal operated by a participant of a conference, which are explained in the following description. A client terminal 12 that is an administrator terminal is loaded with an administration tool for a conference. The administration tool has functions including a function for registering a conference or a handout in a conference server device 10, a function for registering a participant, a function for instructing a participant terminal to perform a process, etc.
Further, the administration tool may be provided with functions common to a participant terminal (e.g., a function for downloading handout data, a function for joining or leaving a conference, a function for displaying a handout in a synchronized manner during a conference). Nevertheless, the administration tool is only required to execute a function for assisting a conference, and therefore such functions common to a participant terminal as described above are not required to be provided.
As described above, the administration tool may be specialized in functions for assisting a conference (e.g., functions for providing an instruction to a participant terminal and for displaying a status), so as to be able to efficiently assist a conference without being required, while assisting a conference, to perform communication relating to processes for downloading a handout data, joining or leaving a conference, displaying a handout in a synchronized manner during a conference, etc.
Further, a client terminal 12 that is a participant terminal is provided with an application program for a conference (hereinafter simply referred to as conference application). The conference application is provided with a function for executing a process in response to an instruction (e.g., an instruction for joining a conference, an instruction for leaving a conference, an instruction for downloading a handout, an instruction for checking a status of a participant terminal, etc.) provided from an administration tool. Further, the conference application of a participant terminal displays a handout of a conference in which the participant terminal participates. At least one participant is a presenter. The screen (e.g., a displayed page, memos, etc.) of a participant terminal operated by a presenter is synchronized on participant terminals operated by participants other than the presenter.
A client terminal 12 may be a terminal device such as a PC, a tablet terminal, a smartphone, a mobile phone, a personal digital assistant (PDA), or a wearable terminal, or may be a virtual machine, a projector, an electric blackboard, a device dedicated for the conference system 1, etc. Further, the conference application, which is operated on a client terminal 12, may be a native application or may be configured with a web browser and a web application that is operated on the web browser.
Before starting a conference, an administrator registers conference information in a conference server device 10 through an administration tool provided on an administrator terminal, which is a client terminal 12. As the conference information, a handout used during a conference is set. An administrator may utilize the administration tool for instructing a participant terminal, which is a client terminal 12, to join a conference, to download a handout, etc.
The conference application of a participant terminal, which is a client terminal 12, performs a process for joining a conference upon an instruction provided from an administration tool. Further, the conference application performs a process for downloading a handout, upon an instruction provided from an administration tool. Through the above way, the conference application of a participant terminal, which is a client terminal 12, displays a handout of a conference in which the participant terminal participates.
During a conference, a handout displayed on a client terminal 12 operated by a presenter is also displayed on a client terminal 12 operated by a participant other than the presenter. A client terminal 12 operated by a participant other than the presenter receives, on a real-time basis, an input operation (e.g., turning a page, etc.) from a client terminal 12 operated by a presenter via a conference server device 10, such that a display screen is shared. For example, when a page of a handout is turned on a client terminal 12 operated by a presenter, the page of the handout is also turned on client terminals 12 operated by participants other than the presenter, such that the same screen is shared.
Further, when a handwriting memo such as a mark, a line, or a text, is added through an operation by use of a stylus pen or a mouse on a client terminal 12 operated by a presenter, the handwriting memo is also added on the screen of client terminals 12 operated by participants other than the presenter.
Further, in a first variation, a second variation, and a third variation of the present embodiments, client terminals 12 include an organizer terminal operated by an organizer of a conference and a participant terminal operated by a participant of a conference, which are explained in the following description. A client terminal 12 that is an organizer terminal is loaded with an administration tool for a conference. The administration tool is provided with a function for registering a conference or a handout in a conference server device 10, a function for registering an organizer or a participant, a function for accepting an operation of selecting a question to be delivered to participant terminals from among questions provided from participants.
Before a conference is started, an organizer registers conference information in a conference server device 10 through an administration tool of a client terminal 12 that is an organizer terminal. As conference information, a setting of a handout to be used during a conference is provided. The conference application of a client terminal 12 that is a participant terminal performs a process for joining a conference. Further, the conference application performs a process for downloading a handout. Through the above way, the conference application of a participant terminal, which is a client terminal 12, displays a handout of a conference in which the participant terminal participates.
Further, in a fourth variation of the present embodiments, client terminals 12 include an administrator terminal operated by an administrator (or an operator) of a conference and a participant terminal operated by a participant of a conference. A client terminal 12 that is an administrator terminal is loaded with an application program which is referred to as administration tool. The administration tool is provided with a function for registering a conference, handout data, a questionnaire in a conference server device 10, a function for registering a participant of a conference, etc.
Further, a client terminal 12 that is a participant terminal is provided with an application program for a conference (hereinafter simply referred to as conference application). The conference application is provided with a function for displaying a list of conferences, a handout, a questionnaire, etc.
Further, a client terminal 12 that is a participant terminal is provided with functions for acquiring conference information from a conference server device 10, for downloading handout data, for joining a conference, etc. Note that, in the conference system 1, any user participating in a conference may be allowed to become a presenter.
Before a conference is started, conference information, handout data, questionnaire information, etc., are registered in a conference server device 10 through a client terminal 12 by an administrator or a presenter. Each participant of the conference logs in to the conference server device 10 through a client terminal 12 that is a participant terminal. The conference server device 10 performs authentication, based on whether authentication information such as a login ID and a password, which is received from a client terminal 12 at the time of a login process, matches authentication information stored in a user information DB, which is explained in the following description.
Upon a success of the authentication, a session that is associated with the login ID is established between the client terminal 12 and the conference server device 10. Note that authentication information may not be required by the conference server device 10 when a client terminal 12 performs a login process. In the above case, the conference server device 10 issues a communication ID for specifying a communication-partner (i.e., a client terminal 12) to be assigned to the client terminal 12, so as to associate an established session with the communication ID.
Note that a client terminal 12 may be allowed to log in to the conference server device 10 using authentication information at a desired timing, after a session is established with the conference server device 10 without using authentication information. In the above case, a session associated with a login ID, instead of the communication ID, is established.
Then, a client terminal 12 of a participant designates a conference to join from among conferences included in conference information, which is received from the conference server device 10, so that a joining request with a conference ID of the selected conference is transmitted to the conference server device 10, in order for the client terminal 12 to join the conference.
Specifically, the conference server device 10 manages a participation status with respect to a conference, in association with a received login ID or communication ID corresponding to a client terminal 12 that has transmitted a joining request with a conference ID. With such management as explained above, the conference server device 10 can comprehend which client terminal 12 is participating in which conference. Note that in a case where a conference server device 10 receives a request for leaving a conference from a client terminal 12, the conference server device 10 updates the participation status of the client terminal 12 such that the login ID or communication ID is not associated with the conference ID. After the update of the participation status with respect to the conference, the conference server device 10 obtains handout data that is associated with the conference ID in the conference information DB and transmits the obtained handout data to each client terminal 12 from which a joining request is transmitted. A client terminal 12 that has received the handout data, which is operated by a participant of the conference, displays a screen based on the received handout data.
A screen displaying a handout is synchronized on a participant terminal participating in a conference, which is a client terminal 12, and on a participant terminal (hereinafter referred to as a presenter terminal) operated by a presenter of the conference. A presenter terminal is provided, as role information, with information indicative of authority as a presenter. The information indicative of authority for a presenter may be voluntarily obtained upon being provided with an operation, which is entered to a presenter terminal, or may be obtained from a conference server device 10 when being designated by another client terminal 12.
A participant terminal (hereinafter referred to as an audience terminal) operated by an audience member, not a presenter, receives operation information indicative of an input operation (i.e., turning a page, taking a memo, etc.), which is transmitted from the conference server device 10 upon an operation entered to the presenter terminal, through a session on a real-time basis. Further, the audience terminal updates the screen displaying a handout with the same operation, based on the received operation information, such that a display screen is shared with the presenter terminal. Transmission of operation information may be actualized such that the conference server device 10 transmits, through a session, to each participating client terminal 12 corresponding to a login ID or communication ID associated with a conference ID with which the presenter terminal is also associated. An audience terminal is not provided, as role information, with the information indicative of authority as a presenter. A client terminal 12 that is not provided with the information indicative of authority as a presenter may receive information indicative of an audience member from the conference server device 10. Note that the information indicative of authority as a presenter may be provided to multiple client terminals 12 at a conference.
For example, when a page represented by handout data is turned on a presenter terminal, the page of handout data is also turned on audience terminals, such that the same screen is shared. Further, when a presenter adds a handwriting memo such as a mark, a line or a text, through an operation by use of a stylus pen or a mouse on the presenter terminal, the screens of audience terminals are also updated.
Further, a questionnaire, which is registered in the conference server device 10 by a presenter in advance or registered in the conference server device 10 during a conference, may be delivered to audience terminals. An answering result of a questionnaire is processed by the conference server device 10 on a real-time basis, so as to update display of the presenter terminal. The presenter may end a questionnaire and cause audience terminals to display the result of the questionnaire, so as to share the result of the questionnaire with audience members. Note that delivering a questionnaire, ending a questionnaire, and sharing a result of a questionnaire may be performed through an administrator terminal as well.
An administrator (or an operator) of a conference as described above may provide a support to a presenter during a conference. With such a support from an administrator, a presenter can concentrate on explanation. In the conference system 1 according to the present variation, an operation for starting a questionnaire, ending a questionnaire, sharing a result of a questionnaire, etc., may be provided by either an administrator or a presenter.
In the conference system 1, a conference server device 10 and a client terminal 12 are able to perform data communication via the network N1. The network N1 may be a LAN, the internet, a leased line, etc., and may be wired or wireless.
<Hardware Configuration>
A conference server device 10 and a client terminal 12 may be actualized, based on such a hardware configuration as illustrated in
The client terminal 12 illustrated in
The input device 501 may include a keyboard, a mouse, a touchscreen, etc., so as to be used by a user for inputting various operation signals. The display device 502 may include a display, etc., so as to display a result of processing performed by a computer. The communication I/F 507 is an interface for connecting a computer with various types of networks, which enables the computer to perform data communication via the communication I/F 507.
Further, the HDD 508 is an example of a non-volatile memory device storing a program and data. The program and data stored in the HDD 508 may include an operation system (OS), which is a basic software program for entirely controlling a computer, and application software programs (hereinafter simply referred to as an application) operated on the OS for providing various functions, etc. Note that, instead of the 508, a computer may be provided with a drive device (e.g., a solid state drive (SSD)), in which a flash memory is employed as a recording medium.
The external I/F 503 is an interface to an external device. The external device may be a recording medium 503a, etc. The external I/F 503 enables a computer to perform read/write processing on the recording medium 503a via the external I/F 503. The recording medium 503a may be a flexible disk, a compact disk (CD), a digital versatile disk (DVD), a secure digital (SD) memory card, a universal serial bus (USB) memory, a subscriber identity module (SIM) card, etc.
The ROM 505 is an example of a non-volatile semiconductor memory (memory device) that is able to store a program and data even when the power is off. The ROM 505 stores a program and data relating to a basic input/output system (BIOS), a OS setting, a network setting, etc. The RAM 504 is an example of a volatile semiconductor memory (memory device) for temporarily storing a program and data.
The CPU 506 is an arithmetic device that retrieves a program and data from a memory device such as the ROM 505 or the HDD 508 onto the RAM 504 for executing processing for entirely controlling a computer and actualizing a function. The CPU 506 may be actualized by one processor or may be actualized by multiple processors. The client terminal 12 may execute a program for actualizing various processing explained in the following description, by use of the hardware configuration as described above, etc.
The conference server device 10 illustrated in
<Software Configuration>
In a conference system 1 according to the present embodiment, a conference server device 10, an administrator terminal 12A, which is a client terminal 12 operated by an administrator of a conference, a participant terminal 12B, which is a client terminal 12 operated by a participant of a conference, are actualized as illustrated in the functional block diagrams, which are explained in the following description.
<<Administrator Terminal>>
The administrator terminal 12A illustrated in
The communication unit 21 of the administrator terminal 12A controls communication with the conference server device 10. The operation accepting unit 22 accepts an operation entered by an administrator and performs control based on the entered operation. The administration tool unit 23 provides the administrator with functions for administrating a conference. For example, the administration tool unit 23 includes a function for registering a conference or a handout in the conference server device 10, a function for registering a participant, a function for instructing a participant terminal 12B to perform a process, etc.
The conference registering unit 31 performs a process, for example, for registering a conference or a handout in the conference server device 10, based on an operation entered by an administrator. The user setting unit 32 performs a process, for example, for registering user information of a participant in the conference server device 10, based on an operation entered by an administrator. The conference management unit 33 manages control of a participant terminal 12B, which is performed by an administrator through an administrator terminal 12A. The login processing unit 34 performs a login process for logging in to the conference server device 10.
Further, the communication control unit 41 of the conference management unit 33 transmits an instruction to a participant terminal 12B via the conference server device 10, based on an operation entered by an administrator, so as to cause the participant terminal 12B to execute a process for joining a conference, for downloading a handout, etc. The status acquiring unit 42 provides an instruction to a participant terminal 12B, based on an operation entered by an administrator, so as to acquire information indicative of a status such as a status of downloading a handout. The display control unit 35 controls display of a screen of the administration tool.
<<Participant Terminal>>
The participant terminal 12B illustrated in
The communication unit 51 of the participant terminal 12B controls communication with the conference server device 10. The operation accepting unit 52 accepts an operation entered by a participant and performs control based on the entered operation. The conference application unit 53 performs a process pertaining to a conference. For example, the conference application unit 53 may include functions executed based on an instruction provided by an administrator terminal 12A, such as a function for performing a process for joining a conference, downloading a handout, etc., or a function for displaying a handout of a conference at a conference in a synchronized manner with a participant terminal 12B of a presenter.
The server connecting unit 61 connects to a conference server device 10 to establish a session. The login processing unit 62 performs a login process to log in to a conference server device 10. The instructed item executing unit 63 performs a process for joining a conference, downloading a handout, etc., based on an instruction provided from an administrator terminal 12A. The display control unit 64 controls display of a handout of a conference, etc. The information management unit 65 manages necessary information in the participant terminal 12B.
<<Conference Server Device>>
The conference server device 10 illustrated in
The communication unit 81 controls communication with a client terminal 12. The conference management unit 82 performs management of a conference, as explained in the following description, by use of user information stored in the user information DB 84, conference information stored in the conference information DB 85, etc. The authentication unit 83 authenticates a user who operates a client terminal 12, by use of information such as user information stored in the user information DB 84. The information management unit 91 performs information processing such as registration of a conference and control of a conference.
The instruction delivery unit 92 delivers a destination-designated instruction provided from an administrator terminal 12A to the participant terminal 12B, which is designated as the destination. The status providing unit 93 delivers a destination-designated instruction provided from an administrator terminal 12A to the participant terminal 12B, which is designated as the destination, for checking a status of the participant terminal 12B. Further, the status providing unit 93 provides information indicative of the status acquired from the participant terminal 12B to the administrator terminal 12A.
Note that the conference server device 10 may be actualized by a single information processing apparatus and may be actualized by multiple information processing apparatuses. Further, the conference server device 10 and the administrator terminal 12A may be unified and actualized by a single information processing apparatus.
<Processing>
<<Overall Processing>>
In the conference system 1 according to the present embodiment, through such a sequence as illustrated in
After becoming connected, upon an operation entered to the participant terminal 12B, the login processing unit 62 may perform a login process by use of a user ID, which is explained in the following description. Note that authentication information such as a user ID and a password may be entered by a user at the time of establishing a session with the conference server device 10, such that the login processing unit 62 performs a login process by use of the user ID. Note that the authentication information may be information for specifying a terminal, not a user. That is to say, the authentication information includes a terminal ID, other than a user ID. In the above case, the conference server device 10 may associate a user ID or a terminal ID, for use as a communication ID, with a participant terminal 12B, such that the conference server device 10 manages a session established with the participant terminal 12B, as illustrated in
Note that the conference server device 10 may manage network address information of a participant terminal 12B, such as an IP address, in association with a communication ID, a user ID, or a terminal ID corresponding to the participant terminal 12B.
At Step S11, an administrator utilizes administrative authority to log into the conference server device 10 through an administration tool of an administrator terminal 12A. Specifically, the login processing unit 34 transmits a login request to the conference server device 10, via the communication unit 21. The login request includes authentication information of a user having the administrative authority. The authentication information may include, for example, a user ID and a password. The conference server device 10 stores the user ID and the password in the user information DB 84 in advance, as identification information of the user having the administrative authority. Further, when the conference server device 10 receives the login request via the communication unit 81, the authentication unit 83 determines whether the authentication information included in the received login request matches the authentication information of the user having the administrative authority, which is stored in the user information DB 84.
In a case of determining that the authentication information does not match, the authentication unit 83 transmits error information, which indicates that the login has failed, to the administrator terminal 12A via the communication unit 81. Contrarily, in a case of determining that the authentication information matches, processing proceeds to Step S12, where the administrator can utilize the administrative authority to check, on the screen of the administration tool, a list of participant terminals 12B connected to the conference server device 10. Here, a session is established between the conference server device 10 and the administrator terminal 12A, similarly to the participant terminal 12B as explained at Step S10, so as to manage the administrator terminal 12A in association with the user ID having the administrative authority. The conference server device 10 may manage the administrator terminal 12A by use of network address information, such as an IP address, associated with the user ID, similarly to the participant terminal 12B. Further, the administrator may select, on the screen of the administration tool, an instruction to a participant terminal 12B, so as to control the participant terminal 12B to perform a process. In the above way, the administrator is able to control a conference or control a participant terminal 12B through the administration tool of the administrator terminal 12A.
Specifically, the administrator controls a participant terminal 12B to perform a process through the administration tool, in such a flow as illustrated in
Note that communications protocol for transmitting and receiving a message may be, for example, one that is used for instant messenger, such as Extensible Messaging and Presence Protocol (XMPP), or Hypertext Transfer Protocol (HTTP). Further, another communications protocol for enabling communication of a message may be employed. Upon receiving the message through a session, the instructed item executing unit 63 of a participant terminal 12B performs a process, based on an instruction included in the received message.
In the conference system 1 according to the present embodiment, through such a processing flow as illustrated in
<<Screen of an Administration Tool>>
On the screen 1100 of the administration tool, an instruction directed to a participant terminal 12B is selected through “COMMAND-SELECT” on the top of the screen. On the screen 1100 illustrated in
On the screen 1100 of the administration tool, at least one conference, to which an instruction selected through “COMMAND-SELECT” is directed, is selected through “CONFERENCE-SELECT” on the middle of the screen. Further, on the screen 1100 of the administration tool, at least one participant terminal 12B, to which an instruction is directed, is selected through “USER-SELECT” near the bottom of the screen. The administrator may collectively control the at least one participant terminal 12B to perform a process, by pressing an enter button 1101 on the screen 1100 of the administration tool.
For example, when the enter button 1101 is pressed by the administrator on the screen 1100 of the administration tool illustrated in
<<Message>>
Configuration of a message transmitted by use of an administration tool from an administrator terminal 12A to a conference server device 10 through an established session is as illustrated in each example of
In
As illustrated in
Further, with respect to each message, a conference ID is designated. When a conference ID is designated, the administrator terminal 12A can transmit a message to participant terminals 12B participating in a conference corresponding to the conference ID. Note that designation of a conference ID is not required. That is to say, in a case where a conference ID is not designated, a message may be transmitted to all participant terminals 12B that have established a session with the conference server device 10.
Further, with respect to each message, a user ID of an administrator who has logged in to utilize the administration tool is designated. When a user ID of an administrator is designated, the conference server device 10 can detect the administrator from which a message is transmitted. Note that designation of a user ID of an administrator is not required. Further, with respect to each message illustrated in
Specifically, in
<<Downloading a Handout>>
In the conference system 1 according to the present embodiment, through the procedure as illustrated in
Upon receiving the message through the communication unit 81, the conference server device 10 transmits, by means of the instruction delivery unit 92, a message including an instruction for downloading a handout of “CONFERENCE A” to all of the connected participant terminals 12B via the communication unit 81. After the message is received via the communication unit 51 of a client terminal 12B, a process for downloading handout data of “CONFERENCE A” is performed by the instructed item executing unit 63, based on the instruction included in the message. The downloaded handout data of “CONFERENCE A” is stored and managed by the information management unit 65. When a conference is actually started, in a case of displaying a handout, the display control unit 64 of the participant terminal 12B utilizes the stored handout data to perform display control. Note that the participant terminal 12B performs the download process, based on information indicative of an instruction for downloading a handout, which is included in the message as illustrated in
Handout data may be electronic data in a format of, for example, PDF, PPT, WORD, EXCEL, JPEG, PNG, BMP, HTML, XML, or in another format. Further, handout data may be electronic data of either an image or a video. In the present embodiment, the following description explains a case where handout data is electronic data representing multiple pages.
In the conference system 1 according to the present embodiment, a delay of starting a conference due to waiting time for participant terminals 12B to download handout data can be prevented, as handout data is downloaded by participant terminals 12B in advance by means of an instruction provided from an administrator terminal 12A before the conference is started. Further, in the conference system 1 according to the present embodiment, a concentrated situation of downloading a handout at a time of starting a conference can be prevented. Further, the download process can be performed without requesting each participant to enter an operation for downloading a handout.
Further, in the conference system 1 according to the present embodiment, a load on the network N1 or on the conference server device 10 is not drastically increased at the time of starting a conference, as a handout is downloaded in advance by each of the participant terminals 12B that will join the conference. Consequently, even in a case where there is an additional participant terminal 12B that is suddenly joined to the conference, the handout is smoothly downloaded.
Further, in addition to downloading a handout, each participant terminal 12B acquires a handout ID, which is associated with handout data, for specifying a handout associated with the handout data. The conference server device 10 may manage handout IDs in association with conference IDs, so that, upon receiving a message designating a conference ID, the conference server device 10 is able to specify handouts that are registered for the conference. Note that, in a case where multiple handout IDs are associated with a conference ID, each participant terminal 12B may be controlled to download multiple items as handout data. Further, a handout ID is managed in association with information indicative of latest update date and time of corresponding handout data. Handout data registered in the conference server device 10 may be re-registered and overwritten. Upon being overwritten, latest update date and time is updated.
Further, a handout may be deleted through the same communication, by use of another message as illustrated in
In combination of such instructions for downloading a handout and for deleting a handout as described above, even in a case of a sudden need for replacing a handout, a process for replacement can be easily performed through the administration tool, without inconveniencing to participants.
An administrator operates a screen 1100 of an administration tool of an administrator terminal 12A before a conference is started, so as to provide an instruction for downloading a handout of the conference. At Step S101, the communication control unit 41 of the administrator terminal 12A transmits, via the communication unit 21, a message including an instruction for downloading a handout of the conference to the conference server device 10. Here, with respect to the message, a conference ID, a handout ID, and an address to which the instruction for downloading a handout is directed may be designated.
Upon receiving the message via the communication unit 81, in a case where the message includes a designated conference ID, the instruction delivery unit 92 of the conference server device 10 acquires, from the information management unit 91, a handout ID of handout data that is associated with the conference ID and information indicative of latest update date and time of the handout data, at Step S102.
Further, in a case where the message includes a designated handout ID, the instruction delivery unit 92 acquires information indicative of latest update date and time of the handout data corresponding to the handout ID. Further, in a case where the message does not include any designated conference ID or handout ID, the instruction delivery unit 92 acquires, from the information management unit 91, handout IDs of all items registered as handout data and information indicative of latest update date and time of the handout data.
At Step S103, the instruction delivery unit 92 transmits, via the communication unit 81, a message including an instruction for downloading a handout of a conference to all participant terminals 12B designated as destinations, based on the message. Note that, in a case where the message does not include any designated destination, the instruction delivery unit 92 transmits, via the communication unit 81, a message including an instruction for downloading a handout of a conference to all participant terminals 12B that are connected. The transmitted message includes the handout ID and the information indicative of latest update date and time of the handout data corresponding to the handout ID, which were acquired at Step S102.
When the message including an instruction for downloading a handout of a conference is received by a participant terminal 12B via the communication unit 51, the instructed item executing unit 63 determines, at Step S104, whether to download the handout, based on the handout ID and the information indicative of latest update date and time of the handout data corresponding to the handout ID, which are included in the message.
For example, the instructed item executing unit 63 determines whether to download the handout in such a way as described below. The instructed item executing unit 63 determines to download the handout, in a case where the handout data corresponding to the handout ID included in the message has not been downloaded. Further, the instructed item executing unit 63 determines to download the handout, even in a case where the handout data corresponding to the handout ID included in the message has been downloaded if information indicative of latest update date and time of the downloaded handout data differs from the information indicative of latest update date and time of the handout data included in the message. Note that the instructed item executing unit 63 determines not to download the handout, in a case where the handout data corresponding to the handout ID included in the message has been downloaded and information indicative of latest update date and time of the downloaded handout data is the same as the information indicative of latest update date and time of the handout data included in the message.
In a case of determining to download the handout data, the instructed item executing unit 63 performs, at Step S105, a process for downloading the handout data of the conference, in accordance with the instruction included in the message. Then, the information management unit 65 of the participant terminal 12B stores and manages the downloaded handout data of the conference.
Further, through Steps S111 to S113, a handout is deleted through the same communication, by use of another message as illustrated in
At Step S112, the instruction delivery unit 92 transmits, via the communication unit 81, a message including an instruction for deleting a handout of the conference to all participant terminals 12B designated as destinations, based on the message. Note that, in a case where the message does not include any designated destination, the instruction delivery unit 92 transmits, via the communication unit 81, the message including an instruction for deleting a handout of the conference to all participant terminals 12B that are connected.
At Step S113, upon receiving the message including an instruction for deleting a handout of the conference via the communication unit 51, the instructed item executing unit 63 of a participant terminal 12B performs a process for deleting handout data corresponding to a handout ID included in the message.
<<Login by a Participant Terminal>>
In the conference system 1 according to the present embodiment, in such a case where an administrator such as an operator or an administrating office hosting a conference offers participant terminals 12B for the conference, each participant terminal 12B may log in to a conference server device 10 as explained at Step S10 of
When the login with the number succeeds, the participant terminal 12B displays a login-success screen 1002. On the login-success screen 1002 illustrated in
Note that, in a case where the login button 1012 for logging in without specifying a user is pressed, the participant terminal 12B displays a login-success screen 1003. When an OK button 1022 on the login-success screen 1003 is pressed, the participant terminal 12B displays the portal screen 1004.
The login process for logging in with a number to specify a participant is performed through such a procedure as illustrated in
At Step S21, the display control unit 64 of a participant terminal 12B displays a login screen 1001 as illustrated in
A number to specify a participant is registered in the conference server device 10 as user information, in association with a user ID and a password, as illustrated in
At Step S24, the information management unit 91 of a conference server device 10 retrieves, from the user information DB 84, a user ID, a password and a name corresponding to the number provided at Step S23. At Step S25, the information management unit 91 of the conference server device 10 provides the user ID, the password and the name corresponding to the number to the participant terminal 12B via the communication unit 81.
At Step S26, the login processing unit 62 of the participant terminal 12B requests for login to the conference server device 10 via the communication unit 51, designating authentication information such as the user ID and the password provided at Step S25. At Step S27, the authentication unit 83 of the conference server device 10 determines whether the login succeeds or fails, based on an authentication process for determining whether the designated user ID and password match a pre-registered user ID and password. In a case where the login succeeds, at Step S28, the conference server device 10 transmits screen information of a portal screen 1004 to the participant terminal 12B via the communication unit 81, so that the display control unit 64 of the participant terminal 12B displays the portal screen 1004. Further, in a case where the login fails, the authentication unit 83 of the conference server device 10 provides information indicative of failure of login to the participant terminal 12B via the communication unit 81.
According to the login process as illustrated in
<<Joining a Conference>>
Next, the following description explains an example of controlling a participant terminal 12B to join a session for a conference, which is managed by a conference server device 10.
The communication control unit 41 of the administration tool transmits a message including an instruction for joining a conference, which is directed to each user designated on the screen 1100, to a conference server device 10 via the communication unit 21. Upon receiving the message via the communication unit 81, the instruction delivery unit 92 of the conference server device 10 transmits, via the communication unit 81, a message including an instruction for joining a conference to each participant terminal 12B designated as a destination of the message, so as to deliver the instruction to each participant terminal 12B. A participant terminal 12B performs a process for joining a conference, based on the instruction included in the message received via the communication unit 21. The message including the instruction for joining the conference is exemplified by the message illustrated in
For example, in
In the example of
In the conference system 1 according to the present embodiment, through such a procedure as illustrated in
Note that, although an example of controlling participant terminals 12B to preliminarily download a handout before a conference is started is explained in the above description with respect to the conference system 1 according to the present invention, there may be a case where download of a handout has failed or a case of using a participant terminal 12B that has not been provided with a download instruction from an administration tool. Therefore, a participant terminal 12B performs such a process as illustrated in
At Step S31, a participant terminal 12B receives a message including an instruction for joining a conference and performs a process for joining a conference, based on the message. At Step S32, the participant terminal 12B determines whether or not handout data of the conference, which is designated by the message, has been downloaded.
In a case where the handout data of the conference, which is designated by the message, has not been downloaded, at Step S33, the participant terminal 12B downloads the handout data of the conference from a conference server device 10. After the handout data of the conference is downloaded at Step S33, the participant terminal 12B displays a designated page of the handout at Step S34. Note that, in a case of having the handout date of the conference, which is designated by the message, the participant terminal 12B skips Step S33 and displays the designated page of the handout.
Note that, in the conference system 1 according to the present embodiment, a message including an instruction for responding back with a handout ID of downloaded handout data may be transmitted to a participant terminal 12B through an administration tool, so as to cause the participant terminal 12B to provide a response to the conference server device 10 along with a handout ID of handout data that has been successfully downloaded. Based on the response, an administrator is able to check, through an administration tool, participant terminals 12B that have failed to download the handout data or that have not downloaded the handout data.
As described above, in the conference system 1 according to the present embodiment, a mechanism for controlling a participant terminal 12B through an administration tool is achieved. The mechanism in the conference system 1 according to the present embodiment enables to control a participant terminal 12B to perform a process for downloading a handout, joining a conference, etc., based on an instruction provided through an administration tool of an administrator terminal 12A, such a process having conventionally been performed by a participant or an administrator by operating the participant terminal 12B. That is to say, in the conference system 1 according to the present embodiment, a burden on a participant or an administrator may be reduced.
Note that an instruction provided through an administration tool is not limited to downloading a handout, joining a conference, leaving a conference, deleting a handout and obtaining a status, which are taken as examples of the instruction in the present embodiment. Further, a message including an instruction provided through an administration tool may be replaced by any other form of processes that can be performed at each stage of a conference, such as before a conference, during a conference, or after a conference.
In the second embodiment, a memo function used by a participant terminal 12B during a conference is added to the conference system 1 according to the first embodiment. Note that the explanation of the conference system 1 according to the first embodiment is on the premise that handout data is downloaded to a participant terminal 12B. In a conference system 1 according to the second embodiment, a setting as to whether taking out of handout data is “allowed” or “not allowed” can be provided. Taking out of handout data means to download handout data that is registered to a conference to a device personally owned by a participant or to print out the handout data by use of a copy machine, etc. Note that the second embodiment is the same as the first embodiment for the most part, and therefore explanation of the second embodiment may be partly omitted where appropriate. The memo function used by a participant terminal 12B during a conference may be utilized through processing that follows Step S34 of
<Processing>
<<Preliminary Setting>>
The memo function used by a participant terminal 12B during a conference requires a preliminary setting as explained below, regarding taking out of handout data. The preliminary setting regarding taking out of handout data may be performed as a process performed at Step S12 of
Specifically, in the flow as illustrated in
An administrator may provide, on the screen 1100 of the administration tool illustrated in
Further, an administrator may operate a screen 1200 for registering handout data as illustrated in
Based on settings provided on the screen 1100 of an administration tool as illustrated in
Ina case where the setting item “ALLOWANCE FOR TAKING OUT OF HANDOUT OF CONFERENCE” of the conference information as illustrated in
<<Memo Function during a Conference>>
In the conference system 1 according to the second embodiment, processing as illustrated in
As described above, during a conference, a handout displayed on a participant terminal 12B operated by a presenter is also displayed on participant terminals 12B operated by participants other than the presenter. A participant terminal 12B operated by a participant other than the presenter includes a presenter mode, such that the participant terminal 12B operated by a participant other than the presenter receives, via the conference server device 10, an operation (i.e. turning a page, etc.) entered to the participant terminal 12B operated by the presenter on a real-time basis, so that the displayed is shared.
Additionally, a participant terminal 12B operated by a participant other than the presenter includes a personal mode, such that the participant terminal 12B operated by a participant other than the presenter does not cause the participant terminal 12B operated by the presenter to share the displayed screen. A participant other than the presenter may switch modes to the personal mode for personally providing an operation to a handout or for using the memo function.
A participant, other than a presenter, who uses the memo function during a conference, operates a participant terminal 12B at Step S201 to request for switching modes from the presenter mode to the personal mode. The conference application unit 53 of the participant terminal 12B switches modes from the presenter mode to the personal mode. At Step S202, the participant operates the participant terminal 12B, to request for the memo function. The conference application unit 53 of the participant terminal 12B accepts selection of the memo function.
At Step S203, the conference application unit 53 of the participant terminal 12B determines whether a setting as to taking out of handout data is “ALLOWED” or “NOT ALLOWED”, with respect to handout data on which the participant will use the memo function. Determination about the setting as to taking out of handout data may be performed by reference to conference information as illustrated in
Contrarily, in a case where the setting as to taking out of handout data on which the memo function is used is “NOT ALLOWED”, the conference application unit 53 of the participant terminal 12B displays, at Step S205, a screen 1400 including a blank memo area 1401 as illustrated in
For example, in a case of taking a memo on a handout as illustrated in
The memo area 1401 may be created on a basis of each page of a handout, a handout, or a conference. In a case of using one memo area 1401 for a conference, the memo area 1401 including memos taken in the conference is displayed, no matter which page of the memo function is used. Note that in a case where all space of the memo area 1401 is taken because of memos, a memo page may be added to obtain more space to take memos.
In a case of using one memo area 1401 for a page of a handout, for example, when the memo function is used while displaying the second page of the handout, a memo that was taken on the second page of the handout is displayed. When the memo function is used while displaying a page other than the second page, a memo corresponding to the page is displayed. On the memo area 1401, taking a memo, editing a memo, and deleting a memo can be performed.
The conference management unit 82 of the conference server device 10, which has received the conference ending request at Step S252, transmits the conference ending request to a participant terminal 12B. At Step S254, the conference application unit 53 of the participant terminal 12B receives the conference ending request. At Step S255, the conference application unit 53 of the participant terminal 12B transmits, to the conference server device 10, memo data of a memo taken by the participant by use of the memo function during the conference. The conference management unit 82 of the conference server device 10, which has received the memo data at Step S256, converts the memo data into PDF data, at Step S257. Note that conversion of the memo data into PDF data is an example of a process for electronically distributing, exchanging, and storing memo data. Note that the process at Step S257 may be performed as a background task (i.e. by use of a sub-thread) of the conference server device 10, as appropriate. The processes of Steps S255 through S257 are repeated as many times as the number of participants in the conference.
Conversion of memo data into PDF data at Step S257 is performed through a procedure as illustrated in
In a case where there is not a personal memo obtaining request from a participant corresponding to memo data, the conference management unit 82 of the conference server device 10 terminates the processing of the flowchart as illustrated in
In a case where there is a personal memo obtaining request from a participant corresponding to memo data, the conference management unit 82 of the conference server device 10 determines whether the setting as to taking out of handout data is “ALLOWED” or “NOT ALLOWED”, at Step S262. In a case where the setting as to taking out of handout data is “ALLOWED”, the conference management unit 82 of the conference server device 10 superimposes the memo data on the handout data and converts the memo data superimposed on the handout data into PDF data, at Step S263. In a case where the setting as to taking out of handout data is “NOT ALLOWED”, the conference management unit 82 of the conference server device 10 performs a process for converting the memo data into PDF data at Step S264.
As the process for converting into PDF data may be performed as a background task (i.e., by use of a sub-thread), a participant may transmit a personal memo obtaining request at a timing desired by the participant. For example, in a case where a participant, who has not transmitted a personal memo obtaining request, transmits a personal memo obtaining request, the conference management unit 82 of the conference server device 10 may perform the process for converting into PDF data, based on the newly received personal memo obtaining request, after processing all tasks of performing the process for converting into PDF data.
Distribution of a personal memo to a participant is performed through a procedure as illustrated in
At Step S271, the conference management unit 82 of the conference server device 10 determines whether there is a personal memo obtaining request. In a case where there is not a personal memo obtaining request from a participant, the conference management unit 82 of the conference server device 10 terminates the processing of the flowchart illustrated in
Note that distribution of a file converted into a PDF format may be performed in various ways. For example, in a case of immediately distributing a file converted into a PDF format, a participant may be informed of a URL, which is prepared for the purpose of distribution. Further, the file converted into a PDF format may be sent via an email. Further, in a need of distributing the file converted into a PDF format for a purpose of promoting a business, the file converted into a PDF format may be distributed via a person who is in charge of the promotion.
In the third embodiment, a log function for saving an operation history during a conference and a function for utilizing an operation history saved during a conference are added to the conference system 1 according to the first embodiment or the second embodiment. Note that the conference system 1 according to the third embodiment is the same as the conference system 1 according to the first embodiment or the second embodiment for the most part, and therefore explanation of the third embodiment may be partly omitted where appropriate.
<Processing>
<<Log Function for Saving an Operation History During a Conference>>
At Step S301, the conference application unit 53 of a participant terminal 12B performs a process for joining a conference and displaying a handout. Upon transition from presenter mode to personal mode, the processing proceeds from Step S302 to Step S303, at which the information management unit 65 of the participant terminal 12B starts a process for recording an operation history in the personal mode as an operation log. At S304, the information management unit 65 records such an operation log as illustrated in
At Step S306, the conference application unit 53 of the participant terminal 12B performs a process for ending and leaving the conference. At Step S307, the communication unit 51 of the participant terminal 12B transmits the operation log recorded at Step S304 to the conference server device 10 together with a user ID and a conference ID. The information management unit 91 of the conference server device 10 saves the received operation log in association with the user ID and the conference ID, as illustrated in
A numerical value 1502 displayed in the row of “TOTAL” is sum of numerical values 1501 per a page, which is indicative of a time (seconds). Note that the numerical value 1501 and the numerical value 1502 are not required to be indicative of time. That is to say, the numerical value 1501 and the numerical value 1502 may be values indicative of how much a participant is interested in a page. For example, the numerical value 1501 and the numerical value 1502 may be replaced with values that are calculated from parameters, each of which is weighted, such as a time during which a participant was viewing a page in the personal mode, whether the participant took a note on the page, and whether the participant provided an operation of zooming in on the page.
When a participant took a memo on a page, a pen icon 1503 is displayed right next to a numerical value 1501 of the page. When a participant provides an operation of zooming in on a page, a magnifier icon 1504 is displayed right next to a numerical value 1501 of the page. When a pen icon 1503 is clicked on, a conference server device 10 utilizes an operation log as illustrated in
A numerical value 1505 displayed in the row of “NUMBER OF MEMOS” is indicative of the number of participants who took a memo, with respect to a page. An administrator or an organizer of a conference may refer to the UI screen 1500 as illustrated in
(Variations 1 through 3)
In recent years, there has been growing use of an electronic conference system, such as a paperless conference system using digitalized handouts, which is displayed on a terminal such as a tablet terminal and a laptop personal computer (PC) used by a participant at a conference or a seminar. In such an electronic conference system, a conference or a seminar can be conducted more effectively if a displayed page and memos of a terminal used by a presenter are synchronized on terminals used by participants.
For example, conventionally, there has been an information displaying system in which a participant can submit a question or an opinion to a presenter at a presentation and the question or the opinion is displayed on a real-time basis at the presentation (see PTL 2, for example).
In the conventional information displaying system, there may be a chance of disturbing progress of a conference because a question or an opinion from a participant is displayed even though the question or the opinion is inappropriate, incomplete, duplicated, etc.
The first variation, the second variation, and the third variation of the above embodiments are provided in view of the above issue, and therefore aim to provide an information processing system in which, from among information entered by one or more screen-sharing terminals, information to be delivered to another screen-sharing terminal can be selected through an administrator terminal.
According to the present variations, a conference or a seminar may be smoothly progressed, as information to be delivered to another screen-sharing terminal can be selected through an administrator terminal from among information entered by one or more screen-sharing terminals.
(First Variation)
<Software Configuration>
A conference server device 10, an organizer terminal 12C, which is a client terminal 12 operated by an organizer of a conference, and a participant terminal 12D, which is a client terminal 12 operated by a participant of a conference, may be actualized as illustrated in the functional block diagrams that are explained in the following description.
<<Organizer Terminal>>
The organizer terminal 12C as illustrated in
The login processing unit 221 performs a process for the organizer terminal 12C to log in to a conference server device 10. The question-list display processing unit 222 performs a process for displaying a list of questions received from the conference server device 10.
The question select processing unit 223 accepts an input by an organizer to select a question from the displayed list of questions. The question select processing unit 223 performs a process for sending a question selected by the organizer from the list of questions to the conference server device 10. The message transmit-receive processing unit 224 performs communication with the conference server device 10. The questioning item information storing unit 225 stores questioning item information as explained in the following description.
<<Participant Terminal>>
The participant terminal 12D as illustrated in
The login processing unit 231 performs a process for the participant terminal 12D to log in to the conference server device 10. The question creation processing unit 232 performs a process for accepting an input of a question from a participant and for sending the question to the conference server device 10. The question display processing unit 233 performs a process for displaying a question sent from the conference server device 10.
The conference control unit 234 controls processes for joining a conference, leaving a conference, downloading a handout, displaying a handout at a conference to synchronize with the screen of a presenter terminal, etc. The message transmit-receive processing unit 235 performs communication with the conference server device 10.
<<Conference Server Device>>
The communication control unit 241 performs communication control performed to have a conference or to join a conference, communication control for delivering an operation entered to a presenter terminal on a real-time basis to participant terminals 12D participating in a conference, communication control for forwarding a question provided from a participant to an organizer terminal 12C and for delivering a question selected by the organizer terminal 12C to the participant terminals 12D, etc. The information management unit 242 performs management of conference information, role information, user information, question information, etc. The message transmit-receive processing unit 243 performs communication with an organizer terminal 12C and a participant terminal 12D.
Further, the conference information storing unit 244 stores conference information, which is explained in the following description. The role information storing unit 245 stores role information, which is explained in the following description. The user information storing unit 246 stores user information, which is explained in the following description. The question information storing unit 247 stores question information, which is explained in the following description.
Note that a conference server device 10 may be actualized by a single information processing apparatus and may be actualized by multiple information processing apparatuses. Further, a conference server device 10 and an organizer terminal 12C may be unified and actualized by a single information processing apparatus.
<<Information>>
<Processing>
<<Login Process>>
<<Process for Creating a Conference>>
<<Question Process>>
For example, in the sequence diagram illustrated in
At Step S2013, the communication control unit 241 of the conference server device 10, which has received the question sending message, assigns the question with a question ID, which is unique to the question, and a conference ID, which is unique to a conference, and stores the question in the question information storing unit 247. At Step S2014, the communication control unit 241 of the conference server device 10 accesses conference information as illustrated in
At Step S2016, the question-list display processing unit 222 of the organizer terminal 12C stores the question received by means of the question forwarding message in the questioning item information storing unit 225, and then displays the question additionally on a question selecting screen 4700 as illustrated in
At Step S2023, the organizer operates the organizer terminal 12C to select, from the list 4701 of questions on the question selecting screen 4700 as illustrated in
At Step S2024, the message transmit-receive processing unit 224 of the organizer terminal 12C creates such a selection information transmitting message as illustrated in
The communication control unit 241 of the conference server device 10, which has received the selection information transmitting message, retrieves a question ID defined in the selection information transmitting message and acquires a question corresponding to the question ID from the question information as illustrated in
The question display processing unit 233 of a participant terminal 12D that has received the selected question sending message retrieves a question defined by the selected question sending message and displays a question display screen 5000 as illustrated in
Note that the timing of transmitting a question forwarding message to an organizer terminal 12C is not limited to each time a conference server device 10 receives a question sending message, which is taken as an example of the timing in the sequence diagram illustrated in
In the conference system 1 according to the present variation, questions from participants are displayed on an organizer terminal 12C, so that an organizer can select a question to be delivered to participants. Hence, in the conference system 1 according to the present variation, in a case where a question from a participant is inappropriate, incomplete, duplicated, etc., such a message is prevented from being undesirably displayed.
(Second Variation)
The question sending message as illustrated in
In a case of the question sending message illustrated in
The question sending message as illustrated in
In a case of the question sending message illustrated in
The question sending message as illustrated in
In a case of the question sending message illustrated in
(Third Variation)
In the conference system 1 according to the present variation, questions entered by participants during a conference may be stored in the question information storing unit 247, as a function for an organizer to review the questions at a later time.
An organizer terminal 12C illustrated in
The login processing unit 221 performs a process for an organizer terminal 12C to log in to a conference server device 10. The message transmit-receive processing unit 224 performs communication with a conference server device 10. The question history obtainment processing unit 226 performs a process for obtaining, from a conference server device 10, a history of questions accepted at a conference, in a selected display format. The question history display processing unit 227 performs a process for displaying a history of questions received from a conference server device 10.
An organizer selects a conference ID and a display format from the question history obtaining screen 6000 at a desired timing (e.g., after a conference, etc.) and presses the obtain button. In the case of
Upon receiving the question-list obtainment requesting message as illustrated in
Note that
The question history display processing unit 227 of an organizer terminal 12C that has received the question history transmitting message displays such a question history screen as illustrated in
Note that, on the question history screen as illustrated in
In the conference system 1 according to the present variation, an organizer is able to review questions from participants, which are entered during a conference, at a later time. Thus, the organizer may analyze frequently asked questions, etc., and utilizes the analysis for improving procedures and contents of a next conference. More specifically, in a case of a seminar hosted by a corporation, analyzing who asked what types of questions, etc., may be helpful for marketing and effective client-contacting activities (e.g. suggestions, etc.).
(Variation 4)
In recent years, there has been a growing use of an electronic conference system, such as a paperless conference system, for the purpose of reducing a cost and a load for printout and for the purpose of conducting an effective conference operation or discussion.
For example, there is an electronic conference system, in which information processing apparatuses prepare common display content in advance and transmit and receive information indicative of operations entered by users, so that the information processing apparatuses can share, by use of a small amount of data, a displayed screen that is updated based on the entered operation. In some of such electronic conference systems, a questionnaire in association with a handout, which is set by use of an information processing apparatus of a presenter, is delivered to audience members' information processing apparatuses to be answered by use of the audience members' information processing terminals (see PTL 3, for example).
In the conventional electronic conference systems, a client terminal of a conference obtains, at the time of joining the conference, questionnaire information associated with the handout information, as well as the handout information. Therefore, in the conventional electronic conference systems, handout information and questionnaire information associated with the handout information need to be registered by the time of starting a conference. Further, once questionnaire information is delivered at a conference, questionnaire information cannot be added or edited independently from handout information.
The fourth variation of the above embodiments is provided in view of the above issue, and therefore aims to provide an information processing system for providing an operation with respect to a questionnaire in a flexible manner, independently from handout information.
According to the present variation, an operation with respect to a questionnaire may be provided in a flexible manner, independently from handout information.
(Fourth Variation)
<Software Configuration>
A conference server device 10 and a client terminal 12 in a conference system 1 according to the present variation may be actualized as illustrated in a functional block diagram, which is explained in the following description.
The conference server device 10 as illustrated in
The communication unit 320 of the conference server device 10 controls communication with a client terminal 12. The information processing unit 322 performs information processing for registering a conference, controlling a conference, etc. The authentication unit 324 performs a process relating to authentication. The information management unit 326 manages a user information DB, a conference information DB, etc. The user information DB stores user information. Specifically, the user information may be, for example, authentication information such as a login ID and a password, which is required for authentication. Note that a login ID includes a user ID and a terminal ID. The client terminal 12 may log in to the conference server device 10 and access the user information DB for editing or adding user information. Further, the conference information DB stores conference information.
The conference information as illustrated in
The UI control unit 330 of a client terminal 12 includes a display control unit 340, an input operation control unit 342, etc., and performs control relating to display of a UI. The display control unit 340 performs display control of a UI. The input operation control unit 342 accepts an operation entered by a user and performs control based on the entered operation. The communication unit 332 controls communication with the conference server device 10. The information processing unit 334 performs information processing such as processing for joining a conference as described above and processing of operation information that is received during a conference. The login requesting unit 336 accepts a login request from a user and transmits a login request to the conference server device 10 for the purpose of authentication of a user or a terminal. The information management unit 338 of the client terminal 12 manages necessary information.
The display control unit 340, communication unit 332, information processing unit 334, and information management unit 338 of a client terminal 12 as illustrated in
Further, the communication unit 320 and the information processing unit 322 of the conference server device 10 as illustrated in
Note that the functional block diagrams illustrated in
An administrator (or an operator) of a conference operates an administration tool provided on an administrator terminal to register questionnaire information. Registration of questionnaire information may be performed by a presenter through a conference application provided in a presenter terminal, etc. When a questionnaire is started, a participant terminal operated by a participant of a conference generates a screen corresponding to above-described role information (i.e., as a presenter or an audience member). For example, a presenter terminal may generate a questionnaire registration screen, a questionnaire-list screen, or a questionnaire-result screen. An audience terminal may generate a questionnaire answering screen or a questionnaire-result screen.
An audience member answers a questionnaire through a questionnaire answering screen. An audience terminal transmits an answering result of a questionnaire, which is provided by an audience member, to the conference server device 10. The conference server device 10 transmits answering results of a questionnaire, which are provided by audience members, to a presenter terminal on a real-time basis. The presenter terminal updates a questionnaire-result screen, based on the answering results of a questionnaire, which are received from the conference server device 10 on a real-time basis. Further, the conference server device 10 stores the answering results of a questionnaire, which are provided by audience members, in the conference information DB as answering information, in association with questionnaire information.
Thus, the conference server device 10 is able to cause a presenter terminal and an audience terminal to display a questionnaire-result screen after conducting a questionnaire. Further, an administrator (or an operator) of a conference may operate an administration tool provided on an administrator terminal to download, from the conference server device 10, an answering result of a questionnaire provided by audience members.
<<Questionnaire Information>>
Questionnaire information, which is included in conference information as illustrated in
A conference ID is an example of identification information for identifying a conference. A questionnaire ID is an example of identification information for identifying a questionnaire. A questionnaire title is a title of a questionnaire. A question is a body of a question in a questionnaire. A question corresponds to “EXPLANATION” provided as an item on a questionnaire registration screen 7100 illustrated in
A selectable number is indicative of the number of options that can be selected by an audience member as an answer to a question. Note that the selectable number corresponds to “SELECTABLE NUMBER” provided as an item on the questionnaire registration screen 7100 illustrated in
A display format is a designated display format for generating a questionnaire-result screen. For example, “PIE”, which is indicative of a pie graph, or “BAR”, which is indicative of a bar graph, may be designated. A “USER WHO CAN CONDUCT” is a designated user who can introduce (i.e., conduct) a questionnaire. In a case where “ANY” is designated as “USER WHO CAN CONDUCT”, the questionnaire can be introduced by any user. Note that any questionnaire can be introduced through an administration tool. Note that setting of a display format and a user who can introduce a questionnaire may be performed through a screen for registering or editing a questionnaire, such as the questionnaire registration screen 7100 illustrated in
As a status, “NOT CONDUCTED YET”, “BEING CONDUCTED”, or “CONDUCTED” is set, so as to indicate a conducting status of a questionnaire. Questionnaire information of a questionnaire with a conducting status of “NOT CONDUCTED YET” or “CONDUCTED” may be edited. However, questionnaire information of a questionnaire with a conducting status of “BEING CONDUCTED” cannot be edited. Note that, in a case where questionnaire information with a conducting status of “CONDUCTED” is selected, a presenter terminal generates and displays questionnaire-result information of the questionnaire.
Further, the reason that questionnaire information of a questionnaire with a conducting status of “CONDUCTED” is editable is to modify a simplified questionnaire that is created during a conference (e.g., a questionnaire with simplified questions or options) after the conference. In the conference system 1 according to the present variation, in a case where a questionnaire with options “A”, “B”, “C”, and “D” may be created during a conference, the options “A”, “B”, “C”, and “D” may be modified into more accurate options “Red”, “Blue”, “Yellow”, and “Green”.
The questionnaire information as illustrated in
<Processing>
<<Registration and Edit of a Questionnaire>>
A process for registering and editing a questionnaire may be performed through screens as illustrated in
On a conference management/register new conference screen 7000 as illustrated in
Note that questionnaire information without a conducting status “BEING CONDUCTED” may be edited by an administrator of a conference through the questionnaire registration screen 7100. In other words, questionnaire information without a conducting status “BEING CONDUCTED” may be edited by an administrator of a conference at any time whether before the conference, during the conference, or after the conference. An administrator of a conference may press the save button 7101 on the questionnaire registration screen 7100 as illustrated in
The conference management/register new conference screen 7000 illustrated in
The process for registering or editing a questionnaire may be also performed through a screen as illustrated in
The questionnaire registration screen 7300 as illustrated in
Note that, in a case of conducting a questionnaire created during a conference, entering all of the required information may be troublesome. Therefore, by pressing the start button 7301, a presenter terminal may start a questionnaire even without a title or an explanation. Alternatively, for conducting a questionnaire, a presenter may enter simple texts, such as A, B, C and D, as options, and then orally explain what each option represents. In the above case, to prevent difficulty of recalling what the questionnaire was about afterwards, questionnaire information such as a title, an explanation, or an option of the conducted questionnaire can be edited.
<<Conducting a Questionnaire>>
A process for conducting a questionnaire may be performed through a procedure as illustrated in a sequence diagram of
At Step S3011, the questionnaire information transmit-receive unit 361 of the presenter terminal 12E transmits a questionnaire-list obtaining request to a conference server device 10. At Step S3012, the conference server device 10 receives the questionnaire-list obtaining request from the presenter terminal 12E.
At Step S3013, the conference server device 10, which has received the questionnaire-list obtaining request, transmits to the presenter terminal 12E questionnaire information associated with a conference in which the presenter terminal 12E participates. Note that, in a case where the presenter terminal 12E has logged in to the conference server device 10, the conference server device 10 may transmit to the presenter terminal 12E questionnaire information designating the presenter as a user who can conduct the questionnaire.
At Step S3014, the questionnaire information management unit 381 of the presenter terminal 12E stores and manages the questionnaire information received by the questionnaire information transmit-receive unit 361. The questionnaire-list screen generating unit 372 of the presenter terminal 12E generates a questionnaire-list screen 7500 as illustrated in
At Step S3015, the questionnaire information transmit-receive unit 361 of the presenter terminal 12E transmits to the conference server device 10 a questionnaire starting request to start a questionnaire selected by the presenter. At Step S3016, the conference server device 10 receives the questionnaire starting request.
At Step S3017, the conference server device 10, which has received the questionnaire starting request from the presenter terminal 12E, transmits questionnaire information corresponding to the questionnaire starting request to the presenter terminal 12E and audience terminals 12F participating in the conference.
At Step S3018, the questionnaire information transmit-receive unit 361 of each audience terminal 12F receives the questionnaire information corresponding to the questionnaire starting request from the conference server device 10. Further, the questionnaire information transmit-receive unit 361 receives reference information from the conference server device 10. The questionnaire information management unit 381 stores and manages the questionnaire information and reference information received by the questionnaire information transmit-receive unit 361. The questionnaire answering screen generating unit 373 of the audience terminal 12F generates a questionnaire answering screen 7600 as illustrated in
An audience member may select an option from the option list 7601 of the questionnaire answering screen 7600 on the audience terminal 12F and press the send-answer button 7603, to send an answer to the questionnaire to the conference server device 10. Further, as illustrated in the reference information of
When the reference information button 7602 is pressed by an audience member, an audience terminal 12F displays reference information on a difference window or in a multi-window format. On the questionnaire answering screen 7600 illustrated in
Further, at Step S3019, the questionnaire information transmit-receive unit 361 of the presenter terminal 12E receives the questionnaire information corresponding to the questionnaire starting request from the conference server device 10. The questionnaire information management unit 381 stores and manages the questionnaire information received by the questionnaire information transmit-receive unit 361. The questionnaire-result screen generating unit 374 of the presenter terminal 12E generates a questionnaire-result screen 7700 as illustrated in
The questionnaire-result screen illustrated in
When the share-result button 7702 is pressed by the presenter, the presenter terminal 12E may request the conference server device 10 to share a questionnaire-result, so that the questionnaire-result screen 7700 is displayed on audience terminals 12F. Further, when the end button 7703 is pressed by the presenter, the presenter terminal 12E requests the conference server device 10 to end a questionnaire, so that the questionnaire is ended.
At Step S3020, the audience member selects an option from the option list 7601 on the questionnaire answering screen 7600 as illustrated in
At Step S3022, the conference server device 10 transmits information indicative of completion of receiving the answering result of the questionnaire, back to the questionnaire information transmit-receive unit 361 of the audience terminal 12F that has sent the answering result of the questionnaire. The questionnaire information management unit 381 stores and manages the answering result of the questionnaire received by the questionnaire information transmit-receive unit 361. The questionnaire answering screen generating unit 373 and the questionnaire answering screen displaying unit 353 of the audience terminal 12F, which has received the information indicative of completion of receiving the answering result of the questionnaire, displays a questionnaire-answered screen 7800 as illustrated in
Further, at Step S3022, the conference server device 10 transmits the answering result of the questionnaire to the presenter terminal 12E. At Step S3024, the questionnaire information transmit-receive unit 361 of the presenter terminal 12E receives the answering result of the questionnaire from the conference server device 10. The questionnaire information management unit 381 of the presenter terminal 12E stores and manages the answering result of the questionnaire, which is received by the questionnaire information transmit-receive unit 361. The questionnaire-result screen generating unit 374 and the questionnaire-result screen displaying unit 354 update display of the answering result information 7701 on the questionnaire-result screen 7700 as illustrated in
When the presenter presses the share-result button 7702 on the questionnaire-result screen 7700, the processing proceeds to Step S3025, at which the questionnaire information transmit-receive unit 361 of the presenter terminal 12E requests the conference server device 10 to share a questionnaire-result for causing audience terminals 12F to display the questionnaire-result screen 7700. At Step S3026, the conference server device receives a request for sharing the questionnaire-result.
At Step S3027, the conference server device 10 transmits answering results of the questionnaire to the audience terminals 12F participating in the questionnaire. At Step S3028, the questionnaire information transmit-receive unit 361 of the audience terminal 12F receives the answering results of the questionnaire from the conference server device 10. The questionnaire information management unit 381 of the audience terminal 12F stores and manages the answering results of the questionnaire, which are received by the questionnaire information transmit-receive unit 361. The questionnaire-result screen generating unit 374 of the audience terminal 12F generates the questionnaire-result screen 7700 as illustrated in
Further, when the presenter presses the end button 7703 on the questionnaire-result screen 7700, the processing proceeds to Step S3029, at which the presenter terminal 12E requests the conference server device 10 to end the questionnaire. At Step S3030, the conference server device 10 receives a request for ending the questionnaire from the presenter terminal 12E. At Step S3031, the conference server device 10 transmits to the presenter terminal 12E and the audience terminals 12F a request for performing display transition from the questionnaire-result screen 7700 to a handout viewing screen.
At Step S3032, the presenter terminal 12E performs display transition from the questionnaire-result screen 7700 to a handout viewing screen. Further, at Step S3033, the audience terminal 12F performs display transition from the questionnaire-result screen 7700 to a handout viewing screen. When display of the presenter terminal 12E and audience terminal 12F returns to the handout viewing screen, the whole processing of conducting a questionnaire ends.
After conducting a questionnaire, a questionnaire-result as illustrated in
In the conference system 1 according to the present variation, a questionnaire is registered in association with a conference, not with a handout of a conference. Further, in the conference system 1 according to the present variation, questionnaire information is not delivered from a conference server device 10 to a participant terminal together with handout information at a time of starting a conference. Instead, questionnaire information is delivered from a conference server device 10 to a participant terminal at a timing directed by a presenter, etc., independently from handout information. With such a mechanism as described above, in the conference system 1 according to the present variation, a questionnaire may be flexibly conducted, as questionnaire information may be added or edited at any timing such as before a conference, during a conference, or after a conference.
Further, the present invention is not limited to the above embodiments and variations, but other variations and modifications may be made without departing from the scope of the present invention. A participant terminal 12B, a participant terminal 12D, a presenter terminal 12E, and an audience terminal 12F are examples of a screen-sharing terminal as described in the scope of the present invention. A conference server device 10 is an example of an information processing apparatus. An administrator terminal 12A and an organizer terminal 12C are examples of an administrator terminal. An administration tool is an example of an administration program.
Further, although a question is entered by a participant in the example of the conference system 1 according to the first, second, or third variations, the question may be replaced with any types of information that are entered by a participant, such as an opinion or an evaluation.
Further, although an organizer selects a question that is delivered to all participants participating in a conference in the example of the conference system 1 according to the first variation, second variation, or the third variation, an organizer may select a question that is not delivered to all participants participating in a conference. Further, although an organizer selects a question that is delivered to all participants participating in a conference in the example of the conference system 1 according to the first variation, second variation, or the third variation, the question is not required to be delivered to all of the participants. For example, the question may be delivered to a presenter.
Note that a conference system 1 including a conference server device 10 and at least one client terminal 12 is an example. Needless to say, there may be various system configuration examples, in accordance with a purpose and a goal.
Each function in the embodiments and variations as explained as explained above may be actualized by one processing circuit or multiple processing circuits. Here, a “processing circuit” in the description of the present application may include a processor that is programmed as a software program to perform each function, such as a processor implemented as an electric circuit, and may include a device designed for performing each function as explained above, such as an application specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), or a conventional circuit module.
Further, a concept of a conference in the embodiments and variations as explained above include one-way communication and two-way communication between users, such as a seminar, a class, or a brainstorming, in addition to a conference in the regularly-used meaning.
Number | Date | Country | Kind |
---|---|---|---|
2016-202785 | Oct 2016 | JP | national |
2016-202830 | Oct 2016 | JP | national |
2016-202831 | Oct 2016 | JP | national |
2017-168503 | Sep 2017 | JP | national |
2017-181109 | Sep 2017 | JP | national |
The present application is a continuation application of U.S. patent application Ser. No. 16/339,855, filed on Apr. 5, 2019 with the U.S. Patent and Trademark Office, which is a national phase application of International Application PCT/JP2017/037062 filed on Oct. 12, 2017, and designated the U.S., which claims priority based on Japanese priority application No. 2017-181109 filed on Sep. 21, 2017, with the Japanese Patent Office, Japanese application No. 2017-168503 filed on Sep. 1, 2017, with the Japanese Patent Office, Japanese application No. 2016-202831 filed on Oct. 14, 2016, with the Japanese Patent Office, Japanese application No. 2016-202830 filed on Oct. 14, 2016, with the Japanese Patent Office, and Japanese application No. 2016-202785 filed on Oct. 14, 2016, with the Japanese Patent Office. The entire contents of each of the foregoing applications are incorporated herein by reference.
Number | Date | Country | |
---|---|---|---|
Parent | 16339855 | Apr 2019 | US |
Child | 17445864 | US |