JP2017134735A - Information processing device, participant number confirmation method, program and information processing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information processing device capable of confirming whether to reach the required minimum number of participants.SOLUTION: An information processing device 10 for managing screen sharing performed in a plurality of terminal devices 12 includes control means for controlling screen sharing, registration means for receiving the registration of the required minimum number of participants necessary to start the screen sharing, participation reception means for receiving a participation request to the screen sharing from the terminal devices, and determination means for determining whether the number of participants for receiving a participant request to the screen sharing from the terminal devices reaches the required minimum number of participants necessary to start the screen sharing receiving the registration.SELECTED DRAWING: Figure 1

Description

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

  In recent years, electronic conference systems such as paperless conference systems have come to be used for the purpose of reducing printing costs and labor, and effective conference management and discussion.

  For example, a screen sharing service providing system that can share a display screen reflecting an input operation with a small amount of data by sharing display contents between information processing apparatuses in advance and exchanging user operation information has been known. (See, for example, Patent Document 1).

  For example, in an important meeting such as an audit, a quorum (the minimum number of participants necessary to establish a meeting) may be set as a condition for establishing the meeting. In such a meeting, for example, the secretariat or the like has to manually determine whether the meeting has been established by checking the number of participants who have participated in the meeting.

  Embodiments of the present invention have been made in view of the above points, and an object of the present invention is to provide an information processing apparatus capable of confirming whether the required minimum number of participants has been reached.

  In order to achieve the above object, claim 1 of the present application is an information processing apparatus that manages screen sharing performed in a plurality of terminal devices, and starts the screen sharing with control means that controls the screen sharing. Registration means for accepting registration of the minimum necessary number of participants required for participation, participation acceptance means for accepting a request for participation in the screen sharing from the terminal device, and acceptance request for participation in the screen sharing from the terminal device Determining means for determining whether or not the number of participants has reached the minimum number of participants necessary for starting the screen sharing for which registration has been accepted.

  According to the embodiment of the present invention, it can be confirmed whether the necessary minimum number of participants has been reached.

It is a lineblock diagram of an example of a conference system concerning this embodiment. It is a hardware block diagram of an example of the computer which comprises the conference system which concerns on this embodiment. It is a functional block diagram of an example of a conference system. It is a functional block diagram of an example of an information processing part. It is a block diagram of an example of user information DB. It is a block diagram of an example of meeting information DB. It is a flowchart of an example of a meeting registration process. It is an image figure of an example of the meeting registration screen after login. It is a flowchart of an example of a meeting list display process. It is an image figure of an example of the meeting list screen after login. It is a flowchart of an example of a meeting holding process. It is a flowchart of an example of meeting holding condition judgment processing. It is a screen image figure of an example of the client terminal in which the number of participants required for a quorum is displayed. It is a block diagram of an example of log information. It is a functional block diagram of the other example of a conference system. It is a block diagram of an example of meeting information DB. It is an image figure of the other example of the meeting registration screen after login. It is a flowchart of the other example of meeting holding condition judgment processing. It is a screen image figure of an example of the client terminal in which the meeting holding conditions which are not satisfy | filled were displayed. It is a block diagram of the other example of log information.

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

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

  The client terminal 12 has a function of registering conference information in the conference server device 10 and a function of displaying a list of conferences and agenda items and materials. The client terminal 12 may be a terminal device such as a PC, a tablet terminal, a smartphone, a mobile phone, or a PDA, a virtual machine, a projector, an electronic blackboard, or a device dedicated to the conference system 1. The application that runs on the client terminal 12 may be a native application, a web browser, and a web application that runs on the web browser.

  The client terminal 12 has a function of acquiring conference information from the conference server device 10, downloading material data, and participating in the conference. In the conference system 1, any user who participates in the conference may be a presenter.

  Before the conference, the organizer and participants register the conference information in the conference server device 10 from the client terminal 12. In addition to the agenda and materials, the minimum number of participants (quorum) necessary for the establishment of the conference and the correspondence when the quorum is not reached are set in the conference information to be registered.

  After the conference is held, the conference system 1 starts the conference when the number of participants in the conference reaches a quorum. Further, the conference system 1 displays on the client terminal 12 visual information (such as a comment) that indicates that the conference is not started or that the quorum has not been reached if the number of participants in the conference has not reached the quorum. Continue to start the meeting.

  The conference system 1 can prevent the start of the conference by not accepting operations such as page turning of the material displayed on the client terminal 12 from the participants. After the conference is ended, the conference system 1 stores the number of participants in the conference, the judgment result (OK / NG) on whether or not the quorum has been reached, the name of the participant, and the like as log information.

  Participants in the conference log in to the conference server device 10 from their client terminals 12. Thereafter, the participant can participate in the conference by designating the conference he / she wishes to participate in and performing the participation process. On the client terminal 12 of the conference participant, the materials of the conference that participated are displayed.

  While the client terminal 12 participates in the conference, the same material as the other client terminals 12 is displayed. The client terminal 12 can receive an input operation (page turning or the like) from another client terminal 12 such as a presenter from the conference server apparatus 10 in real time, and can share a display screen with the other client terminal 12. For example, when the document page is turned on the client terminal 12 of the presenter, the page of the document is turned on the client terminal 12 other than the presenter, and the same screen is shared.

  Further, when a handwritten memo is drawn on the presenter's client terminal 12 to draw a mark or line or add a character by operating a touch pen or a mouse, it is also reflected on the screen of the participant's client terminal 12.

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

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

  The client terminal 12 shown in FIG. 2 includes an input device 501, a display device 502, an external I / F 503, a RAM 504, a ROM 505, a CPU 506, a communication I / F 507, an HDD 508, and the like, which are mutually connected by a bus B. The client terminal 12 may have a configuration including a camera, a microphone, a speaker, and the like.

  The input device 501 includes a keyboard, a mouse, a touch panel, and the like, and is used by a user to input each operation signal. The display device 502 includes a display and the like, and displays a processing result by the computer. A communication I / F 507 is an interface for connecting the computer to various networks. Thus, the computer can perform data communication via the communication I / F 507.

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

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

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

  The CPU 506 is an arithmetic unit that realizes control and functions of the entire computer by reading a program and data from a storage device such as the ROM 505 and the HDD 508 onto the RAM 504 and executing processing. The client terminal 12 can implement various processes as described later by executing the program with the above hardware configuration, for example.

  The conference server apparatus 10 shown in FIG. 2 includes an input device 601, a display device 602, an external I / F 603, a RAM 604, a ROM 605, a CPU 606, a communication I / F 607, an HDD 608, and the like. Yes. The hardware configuration of the conference server device 10 is the same as the hardware configuration of the client terminal 12, but the input device 601 and the display device 602 may be connected and used when necessary. The conference server device 10 can implement various processes as described later by executing a program with the above hardware configuration, for example.

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

  FIG. 3 is a functional block diagram of an example of a conference system. In addition, the functional block of FIG. 3 has shown about the function required for description of this embodiment among the functions which the conference server apparatus 10 and the client terminal 12 provide, and another function may exist.

  The conference server apparatus 10 of FIG. 3 implements the communication unit 20, the information processing unit 22, the authentication unit 24, and the information management unit 26 by executing a program. Further, the client terminal 12 implements a UI display unit 30, a communication unit 32, an information processing unit 34, an authentication unit 36, and an information management unit 38 by executing a program.

  The communication unit 20 of the conference server device 10 controls communication with the client terminal 12. The information processing unit 22 performs information processing such as conference registration and conference control. The authentication unit 24 performs processing related to authentication. The information management unit 26 manages a user information DB, a conference information DB, and the like. The user information DB stores user information. The conference information DB stores conference information.

  The conference information shown in FIG. 3 is information related to a conference registered in advance from the client terminal 12 by the conference organizer or participants. The conference information in FIG. 3 includes a conference ID, a conference name, materials, agenda information, conference holding conditions, log information, and the like. The meeting holding condition includes a quorum and an essential flag.

  The essential flag is information indicating whether or not reaching a quorum is an essential condition for starting a conference. For example, when reaching a quorum is an essential condition for starting a conference, the conference server apparatus 10 does not start the conference until the quorum is reached. Further, when reaching the quorum is not an essential condition for starting the conference, the conference server device 10 can display the visual information on the client terminal 12 that indicates that the quorum has not been reached even if the quorum is not reached. To start.

  The log information stores the number of participants in the conference, the determination result whether or not the quorum has been reached (OK / NG), the name of the participant, and the like after the conference ends. The number of participants in the conference can be confirmed by, for example, the simultaneous access peak number (session number). That is, in the conference system 1 in FIG. 3, it is determined whether or not the quorum has been reached depending on whether or not the number of connections between the conference server device 10 and the client terminal 12 for the conference satisfies the quorum.

  Note that a conference for which no conference holding condition item is set in the conference information starts the conference without determining whether or not the quorum has been reached. The log information does not store the determination result (OK / NG) of whether or not the quorum has been reached.

  The UI display unit 30 of the client terminal 12 includes a display control unit 40, an input operation control unit 42, and the like, and performs control related to UI display. The display control unit 40 performs UI display control. The input operation control unit 42 receives an input operation from the user and performs control based on the input operation. The communication unit 32 controls communication with the conference server device 10. The information processing unit 34 performs information processing such as conference participation and conference processing. The authentication unit 36 receives a login request from the user, and requests the conference server device 10 for user authentication. The information management unit 38 manages information necessary for the client terminal 12.

  The information processing unit 22 of the conference server apparatus 10 illustrated in FIG. 3 is realized by, for example, functional blocks illustrated in FIG. FIG. 4 is a functional block diagram of an example of the information processing unit. The information processing unit 22 includes a conference registration unit 51, a participation reception unit 52, a holding determination unit 53, a conference control unit 54, and a log storage unit 55.

  In response to the conference registration request received from the client terminal 12, the conference registration unit 51 sets conference information in the conference information DB and registers the conference. The participation reception unit 52 receives a request for participation in the conference from the user. The holding determination unit 53 determines whether or not to start the meeting by a meeting holding condition determination process described later.

  The conference control unit 54 uses the information such as conference information and user information stored in the information management unit 26 to provide a conference list screen, provide materials, hold, start, end, and participate in the conference. Control such as display screen sharing in the terminal 12 is performed. After the conference is finished, the log storage unit 55 uses the log information such as the number of participants in the conference, the determination result whether or not the quorum has been reached (OK / NG) and the participant name as the conference information of the information management unit 26. save.

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

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

<< User information DB >>
FIG. 5 is a configuration diagram of an example of the user information DB. The user information shown in FIG. 5 stores a user name and a password in association with each other. The user name is an example of identification information that uniquely identifies the user. The password is an example of secret information associated with the user name.

<< Conference Information DB >>
FIG. 6 is a configuration diagram of an example of the conference information DB. In the conference information DB of FIG. 6, conference information that is information related to the conference is set. The conference information DB shown in FIG. 6 stores a conference ID, a conference name, a quorum, an essential flag, a start date and time, a participation password, materials, and the like in association with each other.

  The conference ID is an example of identification information for uniquely identifying a conference. The meeting name is the name of the meeting. The quorum is the minimum number of participants required for a conference to be established. The essential flag is information indicating whether or not reaching a quorum is an essential condition for starting a conference. The start date and time is the date and time when the conference starts. The participation password is an example of secret information necessary for participating in the conference. The material is the material used at the meeting. Although FIG. 6 shows an example in which one material is registered for each conference, a plurality of materials may be registered.

《Conference registration process》
FIG. 7 is a flowchart of an example of the conference registration process. The meeting organizer or presenter needs to register the meeting information in the meeting server device 10 before holding the meeting. In the conference system 1 of the present embodiment, the conference organizer and the presenter perform conference registration after login processing, for example.

  In step S <b> 11, the conference organizer or presenter inputs a user name and password to the client terminal 12 and instructs login. The authentication unit 36 of the client terminal 12 makes a login request to the conference server device 10.

  In step S <b> 12, the authentication unit 24 of the conference server device 10 performs authentication based on the login request from the client terminal 12. If the authentication is successful, the information processing unit 22 of the conference server apparatus 10 proceeds to step S13. The information processing unit 22 creates a conference registration screen after login. Details of the conference registration screen after login will be described later. In step S <b> 14, the information processing unit 22 transmits the screen information of the created conference registration screen after login to the client terminal 12.

  In step S <b> 15, the display control unit 40 of the client terminal 12 displays the post-login conference registration screen shown in FIG. 8 based on the screen information of the post-login conference registration screen received from the conference server device 10.

  The conference registration screen 1000 after login shown in FIG. 8 is an example of a screen displayed after the conference organizer or presenter logs in. The conference registration screen 1000 includes an input column for conference information such as a conference name, quorum, required flag, start date and time, and an additional column for adding agenda / material.

  Proceeding to step S16, the conference organizer or presenter inputs information necessary for conference registration on the conference registration screen 1000 after login in FIG. 8, and instructs conference registration. The client terminal 12 requests conference registration from the conference server device 10 based on information necessary for conference registration input on the conference registration screen 1000.

  In step S <b> 17, the information processing unit 22 of the conference server apparatus 10 receives a conference registration request specifying information necessary for conference registration input on the conference registration screen 1000, and stores information necessary for conference registration in the conference information DB. Then, register the conference.

  As described above, the conference organizer and the presenter perform conference registration from the conference registration screen 1000 after login shown in FIG. You can register. The conference registration may be performed by the conference administration office.

《Conference list display processing》
FIG. 9 is a flowchart of an example of the conference list display process. In step S51, the meeting organizer or presenter operates the client terminal 12 to input a user name and password and instruct login. The authentication unit 36 of the client terminal 12 makes a login request to the conference server device 10.

  In step S <b> 52, the authentication unit 24 of the conference server device 10 performs authentication based on the login request from the client terminal 12. If the authentication is successful, the information processing unit 22 of the conference server apparatus 10 proceeds to step S53. Since the user is logged in, the information processing unit 22 creates a conference list screen after login.

  In step S <b> 54, the information processing unit 22 transmits the screen information of the created conference list screen after login to the client terminal 12. In step S55, the display control unit 40 of the client terminal 12 displays the conference list screen after login shown in FIG. 10 based on the screen information of the conference list screen after login received from the conference server device 10.

  FIG. 10 is an image diagram of an example of a conference list screen after login. A conference list screen 1200 displays a list 1201 of conferences in which users who have succeeded in authentication can participate. A conference presenter or participant can confirm a conference that can be joined by referring to the conference list 1201 on the conference list screen 1200 after login.

《Meeting》
For example, the meeting organizer instructs to hold a meeting selected from the meeting list 1201 on the meeting list screen 1200 after login as shown in FIG. The client terminal 12 requests the conference server apparatus 10 to hold the instructed conference. The conference server apparatus 10 performs, for example, a process as shown in FIG. 11 in response to a conference request received from the client terminal 12.

  FIG. 11 is a flowchart of an example of the conference holding process. When the information processing unit 22 of the conference server apparatus 10 accepts a meeting holding request, the information processing unit 22 performs the process of step S102. In step S102, the information processing section 22 performs a meeting holding condition determination process described later. After the conference is held, the conference holding condition determination process accepts a request for participation in the conference from the client terminal 12, and based on the number of participants in the conference, the quorum set in the conference information in FIG. This is a process for determining whether or not to start a conference.

  In step S103, when the information processing unit 22 determines to start a conference, the process proceeds to step S104, and processing for starting the conference is started. After the conference is started, the presenter's client terminal 12 transmits a page turning operation and a memo writing operation by the presenter to the conference server apparatus 10. The information processing unit 22 of the conference server apparatus 10 transmits the received page turning operation and memo writing operation by the presenter to the client terminals 12 participating in the conference. Thus, each client terminal 12 participating in the conference shares a display screen with the client terminal 12 of the presenter. The process of step S104 is repeated until the conference ends.

  When the conference ends, the information processing unit 22 of the conference server device 10 stores log information in step S106. The stored log information includes the number of participants in the conference, the judgment result (OK / NG) whether or not the quorum has been reached, the name of the participant, and the like. Even when it is determined in step S103 that the meeting is not started, the information processing unit 22 stores log information in step S106. In this case, the determination result of whether or not the quorum included in the log information has been reached is NG.

  The meeting holding condition determination process in step S102 is performed, for example, according to the procedure shown in FIG. FIG. 12 is a flowchart of an example of a meeting holding condition determination process.

  In step S <b> 121, the participation reception unit 52 included in the information processing unit 22 of the conference server apparatus 10 determines whether or not the client terminal 12 has accepted participation in the conference. If it is determined that participation in the conference has been accepted, the holding determination unit 53 of the information processing unit 22 determines whether the quorum included in the conference information satisfies the number of sessions in step S122.

  The process of step S122 is a process of confirming the number of participants in the current conference based on the simultaneous access peak number and determining whether the number of participants in the conference has reached a quorum. When determining that the number of participants in the conference has reached the quorum, the holding determination unit 53 determines that the conference can be started in step S125 and notifies the conference control unit 54 of the determination. Therefore, the conference control unit 54 can start the conference based on the result that the holding determination unit 53 determines that the conference can be started.

  If it is determined that the number of participants in the conference has not reached the quorum, the holding determination unit 53 proceeds to step S123, and determines whether the essential flag included in the conference information is ON. If the mandatory flag is ON, the conference cannot be started until the conference participants reach a quorum, and therefore the holding determination unit 53 returns to step S121 and continues the process.

  On the other hand, if the mandatory flag is OFF, since reaching the quorum is not an essential condition for starting the conference, the holding determination unit 53 proceeds to step S124 and displays visual information indicating that the quorum is not satisfied on the client terminal 12. Let In step S <b> 125, the holding determination unit 53 determines that the conference can be started and notifies the conference control unit 54 if the visual information indicating that the quorum is not satisfied is still displayed.

  If it is determined in step S121 that participation in the conference is not accepted, the holding determination unit 53 determines in step S126 whether or not the end date / time included in the conference information has elapsed. In addition, although the example which determines whether the end date was passed was shown in step S126 of FIG. 12, you may determine whether predetermined time passed from the start date, for example.

  If the end date / time included in the conference information has not elapsed, the holding determination unit 53 displays the number of conference participants up to a quorum in step S128 on the client terminal 12, for example, as shown in FIG. 13, and returns to the processing in step S121.

  FIG. 13 is a screen image diagram of an example of a client terminal on which the number of participants necessary for a quorum is displayed. The screen image 1400 in FIG. 13 displays visual information 1402 “Person after the quorum”. The visual information 1402 is displayed in the middle of the screen image 1400 because the conference is not started.

  Note that the visual information to be displayed on the client terminal 12 in step S124 continues to be displayed even after the conference is started, so that it is displayed at a place that does not interfere with the conference, such as the upper or lower part of the screen. If the end date / time included in the conference information has elapsed in step S126, the holding determination unit 53 determines that the conference cannot be started in step S127 and notifies the conference control unit 54 of the determination.

  If the meeting system 1 according to the present embodiment determines that reaching a quorum is an essential condition for starting the meeting, the meeting is not started until the number of participants in the meeting reaches the quorum. can do.

  Further, in the conference system 1 of the present embodiment, if reaching the quorum is not an essential condition for starting the conference, visual information indicating that the quorum has not been reached is displayed on the client terminal 12 even if the quorum is not reached. The conference can be started without any change.

  The log information stored in step S106 in FIG. 11 is configured as shown in FIG. 14, for example. FIG. 14 is a configuration diagram of an example of log information. The log information in FIG. 14 includes the set quorum, the number of participants, the quorum determination, and the participant name. In the set quorum, the quorum included in the conference information is written. As the number of participants, the number of participants in the conference (simultaneous access peak number) is written.

  In the determination of the quorum, a determination result as to whether or not the quorum has been reached is written. In the judgment result of whether or not the quorum has been reached, “OK” indicating that the quorum has been reached, “NG” indicating that the quorum has not been reached, or “none” in which no quorum is set, Is written. As the participant name, for example, the user name of the participant in the conference is written.

Note that the log information shown in FIG. 14 may be given a time stamp or may be encrypted and stored in order to improve evidence and reliability. In the conference system 1 of the present embodiment, the number of participants in the conference, the determination result of whether or not the conference has been established, and the participant name are recorded as log information. Therefore, for example, the secretariat of the conference operation can easily determine whether or not the conference has been established by referring to the log information in FIG.
[Second Embodiment]
In the second embodiment, a process for determining whether or not to start a meeting is added to the meeting holding condition determination process in the first embodiment based on whether or not all essential participants are participating. It is. Note that the second embodiment is the same as the first embodiment except for a part thereof, and thus description thereof will be omitted as appropriate.

  FIG. 15 is a functional block diagram of another example of the conference system. The functional block of FIG. 15 is different from the functional block of FIG. 3 in that an essential participant is added to the conference holding condition of the conference information. An essential participant is a participant who must participate in order to start a conference. For example, the conference server apparatus 10 does not start the conference until it accepts the participation of all the essential participants. Moreover, the conference server apparatus 10 can also set the response | compatibility until it accepts participation of all the essential participants to meeting information similarly to 1st Embodiment.

  Note that both the quorum and the required participants may be set as the meeting holding condition, or one of them may be set. The meeting server device 10 starts the meeting when the meeting holding condition is satisfied. If the meeting system 1 does not satisfy the meeting holding conditions, the meeting system 1 does not start the meeting or the visual information (such as a comment) that indicates that the meeting holding conditions are not satisfied is displayed on the client terminal 12. To start.

  FIG. 16 is a configuration diagram of an example of the conference information DB. The conference information DB in FIG. 16 has a configuration in which an essential participant is added to the conference information in FIG. An essential participant represents a participant who is required to participate in order to establish a conference.

  In step S15 of FIG. 7, the display control unit 40 of the client terminal 12 displays the conference registration screen after login shown in FIG. 17 based on the screen information of the conference registration screen after login received from the conference server device 10.

  The conference registration screen 1000 after login shown in FIG. 17 is an example of a screen displayed after the conference organizer or presenter logs in. The conference registration screen 1000 is obtained by adding an input field for an essential participant to the conference information input column of the conference registration screen 1000 after login shown in FIG.

  The conference organizer and the presenter perform conference registration from the conference registration screen 1000 after login shown in FIG. 17, so that the conference server device 10 receives the conference in which the quorum, the required flag, and the required participants are set as the conference holding conditions. You can register.

  The meeting holding condition determination process in step S102 is performed, for example, according to the procedure shown in FIG. FIG. 18 is a flowchart of another example of the meeting holding condition determination process. In the flowchart of FIG. 18, the processes of steps S155 and S156 are added to the flowchart of FIG. If it is determined in step S152 that the number of participants in the conference has reached the quorum, the holding determination unit 53 proceeds to step S155.

  In step S155, the holding determination unit 53 determines whether all the essential participants included in the conference information are participating in the conference. If all the essential participants have participated in the conference, the holding determination unit 53 determines that the conference can be started in step S157 and notifies the conference control unit 54 of the determination. If there is an essential participant who has not participated in the conference, the holding determination unit 53 proceeds to step S156 and causes the client terminal 12 to display visual information indicating that the essential participant has not participated.

  Since all the required participants have not participated in the conference, the conference cannot be started, and therefore the holding determination unit 53 returns to step S151 and continues the process. If it is determined in step S151 that participation in the conference is not accepted, the holding determination unit 53 determines in step S158 whether or not the end date / time included in the conference information has elapsed.

  If the end date / time included in the conference information has not elapsed, the holding determination unit 53 causes the client terminal 12 to display the meeting holding conditions not satisfied in step S160, for example, as shown in FIG. 19, and returns to the processing in step S151.

  FIG. 19 is a screen image diagram of an example of a client terminal on which a meeting holding condition that is not satisfied is displayed. The screen image 1500 in FIG. 19 displays visual information 1502 that “there is no required participant”. Since the screen image 1500 in FIG. 19 is before the conference is started, visual information 1502 is displayed in the middle of the screen.

  Note that the visual information displayed in steps S154 and S156 continues to be displayed even after the conference is started, and is therefore displayed, for example, on the upper or lower part of the screen. If the end date / time included in the conference information has elapsed in step S158, the holding determination unit 53 determines that the conference cannot be started in step S159 and notifies the conference control unit 54 of the determination. By the meeting holding condition determination process of FIG. 12, the meeting system 1 of the present embodiment can prevent the meeting from starting until all the essential participants participate in the meeting.

  The log information stored in step S106 in FIG. 11 is configured as shown in FIG. 20, for example. FIG. 20 is a configuration diagram of another example of log information. The log information in FIG. 20 has a configuration in which the mandatory participant and the judgment of the mandatory participant are added to the log information in FIG. As for the judgment of the essential participant, a judgment result indicating whether or not all the essential participants participated in the conference is written.

  The judgment result of whether or not all the mandatory participants have participated in the meeting includes “OK” indicating that all the essential participants have participated in the meeting, or “NG” indicating that there were the mandatory participants who did not participate in the meeting. Or “None” with no mandatory participant setting is written.

  Note that the log information shown in FIG. 20 may be given a time stamp or may be encrypted and stored in order to improve evidence and reliability. In the conference system 1 of the present embodiment, the number of participants in the conference, the determination result of whether or not the quorum has been reached, and the determination result of whether the participant name and all the required participants have participated in the conference are recorded as log information. To do. Therefore, for example, the conference management office can easily determine whether or not the conference has been established by referring to the log information in FIG.

(Summary)
According to the conference system 1 of the present embodiment, the secretariat of the conference administration that holds the conference in which the conditions for establishing the conference (conference holding conditions) are set can easily determine whether or not the conference has been established. Will be able to. Further, according to the conference system 1 of the present embodiment, information on whether or not the conference satisfies the conference holding condition is automatically stored as the log information of the conference in which the condition for establishing the conference (conference holding condition) is set. it can.

  In the present embodiment, an example in which participation in a conference is accepted after login has been described. However, if the participant name is not recorded as conference log information, the first embodiment may not necessarily log in.

  The present invention is not limited to the specifically disclosed embodiments, and various modifications and changes can be made without departing from the scope of the claims. In the present embodiment, the conference system 1 is shown as an example. However, the present invention can be applied to other systems that share a display screen of materials for information (lectures and classes) created by a seminar system or an education system.

  The client terminal 12 is an example of a terminal device described in the claims. The conference server device 10 is an example of an information processing device. The conference control unit 54 is an example of a control unit. The conference registration unit 51 is an example of a registration unit. The participation reception unit 52 is an example of a participation reception unit. The holding determination unit 53 is an example of a determination unit.

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

DESCRIPTION OF SYMBOLS 1 Conference system 10 Conference server apparatus 12 Client terminal 20 Communication part 22 Information processing part 24 Authentication part 26 Information management part 30 UI display part 32 Communication part 34 Information processing part 36 Authentication part 38 Information management part 40 Display control part 42 Input operation control Unit 51 Conference registration unit 52 Participation acceptance unit 53 Event determination unit 54 Conference control unit 55 Log storage unit 501, 601 Input device 502, 602 Display device 503, 603 External I / F
503a, 603a Recording medium 504, 604 RAM (Random Access Memory)
505, 605 ROM (Read Only Memory)
506, 606 CPU (Central Processing Unit)
507, 607 Communication I / F
508, 608 HDD (Hard Disk Drive)
1000 Conference registration screen 1200 Conference list screen 1400, 1500 Screen image 1402, 1502 Visual information B bus N1 network

JP2015-103131A

Claims (10)

An information processing apparatus for managing screen sharing performed in a plurality of terminal devices,
Control means for controlling the screen sharing;
Registration means for accepting registration of the minimum number of participants necessary to start the screen sharing;
Participation acceptance means for accepting a participation request for the screen sharing from the terminal device;
Determining means for determining whether the number of participants who have received a request for participation in the screen sharing from the terminal device has reached a minimum number of participants necessary for starting the screen sharing for which registration has been received; ,
An information processing apparatus comprising: If the number of participants who have received the request for participation in screen sharing reaches the minimum number of participants necessary to start the screen sharing, the determination unit may send the screen sharing to the control unit. The information processing apparatus according to claim 1, wherein the information processing apparatus notifies that it can be started. If the number of participants who have received the request for participation in screen sharing has not reached the minimum number of participants necessary to start the screen sharing, the determination means is the minimum number of participants required Is the required condition for starting the screen sharing, and if reaching the minimum required number of participants is the required condition for starting the screen sharing, the minimum required number of participants is set. 3. The information processing apparatus according to claim 2, wherein the control means is not notified that the screen sharing can be started until it reaches. If the number of participants who have received the request for participation in screen sharing has not reached the minimum number of participants necessary to start the screen sharing, the determination means is the minimum number of participants required To reach the minimum required number of participants if reaching the minimum required number of participants is not the required condition to start the screen sharing. 4. The information processing apparatus according to claim 2 or 3, wherein visual information that it has not been reached is displayed on the terminal device, and then the control means is notified that the screen sharing can be started. . As the log information of the screen sharing started by the control means, the number of participants who have accepted a request to participate in the screen sharing, and the minimum number of participants necessary for the number of participants to start the screen sharing The information processing apparatus according to any one of claims 2 to 4, further comprising log storage means for storing a determination result as to whether or not the number has been reached. The registration means further accepts registration of required participants that are required to accept a request to participate in the screen sharing in order to start the screen sharing;
6. The information processing apparatus according to claim 1, wherein the determination unit further determines whether a request for participation in the screen sharing has been received from all of the essential participants. In the determination means, the number of participants who have accepted the request for participation in the screen sharing has reached the minimum number of participants necessary to start the screen sharing, and all of the essential participants 7. The information processing apparatus according to claim 6, wherein if the request for participation in screen sharing is received from the control unit, the control unit is notified that the screen sharing can be started. A method for confirming the number of participants in an information processing device that manages screen sharing performed in a plurality of terminal devices,
A registration step for accepting registration of a minimum number of participants necessary to start the screen sharing;
A participation reception step for receiving a request for participation in the screen sharing from the terminal device;
A determination step of determining whether the number of participants who have received a request for participation in the screen sharing from the terminal device has reached the minimum number of participants necessary to start the screen sharing for which registration has been received; ,
A method for confirming the number of participants. An information processing device that manages screen sharing performed in a plurality of terminal devices,
Control means for controlling the screen sharing;
Registration means for accepting registration of the minimum number of participants necessary to start the screen sharing;
Participation acceptance means for accepting a participation request for the screen sharing from the terminal device,
Determining means for determining whether the number of participants who have received a request for participation in screen sharing from the terminal device has reached the minimum number of participants necessary to start the screen sharing for which registration has been received,
Program to function as. An information processing system having a plurality of terminal devices and an information processing device that manages screen sharing performed in the plurality of terminal devices,
Control means for controlling the screen sharing;
Registration means for accepting registration of the minimum number of participants necessary to start the screen sharing;
Participation acceptance means for accepting a participation request for the screen sharing from the terminal device;
Determining means for determining whether the number of participants who have received a request for participation in the screen sharing from the terminal device has reached a minimum number of participants necessary for starting the screen sharing for which registration has been received; ,
An information processing system comprising:

Images