JP2005190314A - Network conference server, network conference method, and program thereof - Google Patents

Network conference server, network conference method, and program thereof Download PDF

Info

Publication number
JP2005190314A
JP2005190314A JP2003432794A JP2003432794A JP2005190314A JP 2005190314 A JP2005190314 A JP 2005190314A JP 2003432794 A JP2003432794 A JP 2003432794A JP 2003432794 A JP2003432794 A JP 2003432794A JP 2005190314 A JP2005190314 A JP 2005190314A
Authority
JP
Japan
Prior art keywords
conference
attendance
information
step
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
JP2003432794A
Other languages
Japanese (ja)
Inventor
Shoji Ishibashi
Haruhiko Kato
Kenichi Suzuki
晴彦 加藤
昭次 石橋
健一 鈴木
Original Assignee
Canon Sales Co Inc
キヤノン販売株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Canon Sales Co Inc, キヤノン販売株式会社 filed Critical Canon Sales Co Inc
Priority to JP2003432794A priority Critical patent/JP2005190314A/en
Publication of JP2005190314A publication Critical patent/JP2005190314A/en
Application status is Pending legal-status Critical

Links

Images

Abstract

<P>PROBLEM TO BE SOLVED: To provide a network conference server, a network conference method, and a program thereof which can perform attendance management of a network conference. <P>SOLUTION: A Web conference server 200 accepts reservation of conference using virtual conference room from client terminals 300 of those who hold conference, stores in a storage means as conference reservation information including information concerning attendance and absence to the conference of the prospective attendants, transmits holding notification of conference to each of client terminals 400 of the prospective attendants referring the conference reservation information from the storage means, and manages information concerning attendance and absence to the conference of the prospective attendants by updating the conference reservation information in the storage means during the period from the transmission of the holding notification to holding the conference at the holding date. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a network conference server, a network conference method, and a program thereof that provide a communication environment (for example, a web conference environment) between a plurality of client terminals via a network.

  In recent years, software that can hold a conference (hereinafter referred to as a network conference) between a plurality of PCs (personal computers) via a network has been released. This is considered as a means for reducing business trip costs and effectively utilizing time. Conventionally, a distributed system using a network has been considered as one of communication tools for people existing in a distributed space (see, for example, Patent Document 1). This Patent Document 1 discloses a distributed system that can identify the situation of each user scattered in a distributed office by displaying them together with an image as a virtual private office and can communicate by sending a message or the like. It can be used as a web conference tool for people in distributed offices and suggests a conference room reservation function.

  Further, a technique relating to conference room reservation with improved convenience is disclosed (for example, see Patent Document 2). In this patent document 2, a conference room reservation is possible in an environment where a conference can be performed over a network, and a mechanism for notifying participants by e-mail when a conference room reservation is made is provided. It also suggests reserving network conferencing system resources as a common resource. As another technique, there is disclosed a conference system for storing video conference minutes so that a person absent from a video conference held on a network can be referred to later (see, for example, Patent Document 3).

JP 2001-186490 A JP 2000-020626 A Japanese Patent Laid-Open No. 11-069331

  However, in the distributed system described in Patent Document 1, although the conference room reservation button is disclosed in the drawing (FIG. 9 of Patent Document 1) in the control panel portion, the detailed operation is not disclosed and how it is implemented. It is unknown whether it will be done. Further, the system related to the notification of the conference room reservation described in Patent Document 2 has a problem that it is merely a notification of the conference holding and the attendance status of the prospective participants cannot be confirmed as a system. Furthermore, even if video and audio as conference minutes are accumulated for absentees as in Patent Document 3, whether or not the conference organizer distributes the minutes to the absentees or views the minutes after delivery. There is a problem that can not be managed.

The present invention has been made to solve the above-described problems, and an object of the present invention is to provide a network conference server, a network conference method, and a program thereof that can perform attendance management of a network conference.
In addition, it is preferable to provide a network conference server, a network conference method, and a program thereof that can prompt a person who is absent from a network conference to view the minutes of the conference, and manage the status of viewing the minutes after the reminder. The purpose is to do.

  The present invention has been made to solve the above-mentioned problems. In the network conference server according to the present invention, a network that provides a virtual conference room capable of real-time communication to a plurality of client terminals connected to the network. Reservation means for receiving and accepting reservation data for a conference using a virtual conference room that includes at least the date and time of the conference and information related to the prospective participants of the conference, which is a conference server and input at a client terminal used by the conference organizer And storage means for storing conference reservation information including at least information input by the reservation means and information on attendance of attendees' meetings, and client terminals of each prospective participant with reference to the conference reservation information from the storage means For sending a meeting notice to the meeting and a sender for sending the notice And attendance management means for managing conference reservation information in the storage means and managing information on attendance of attendees for the period from when the event notification is sent until the conference is held on the date and time. It is characterized by that.

  Further, in one embodiment of the network conference server according to the present invention, the attendees who are absent from the conference are requested to browse the minutes of the conference by referring to the information regarding the attendance of the conference included in the conference reservation information after the conference ends. The apparatus further comprises means for prompting minutes.

  The network conference method according to the present invention is a network conference method using a network conference server that provides a virtual conference room capable of real-time communication to a plurality of client terminals connected to a network, Reservation step that receives and accepts reservation data for conferences that use virtual conference rooms, including at least the date and time of the conference, and information on the prospective participants of the conference, entered at the client terminal used by the user, and entered at the reservation step An event notification sending step of transmitting a conference opening notice to each participant's client terminal by referring to the conference reservation information from storage means for storing conference reservation information including at least information on attendance of the prospective participant and the conference. And send the event notification in the event notification transmission step. From, conference until it is held in the held date and time, and characterized in that it has an attendance management step of managing the information about the attendance to the meeting of prospective participants to update the conference reservation information stored in the storage means.

  Moreover, the program by this invention is a program for making a network conference server perform the network conference method of Claims 10-13.

The network conference server, the network conference method, and the program thereof according to the present invention refers to conference reservation information, transmits a conference notification to each prospective client terminal, transmits the conference notification, and then the conference is held. By managing information related to attendance at conferences until the day and time, it is possible to manage attendance at network conferences.
As a result, the attendance management of the network meeting can be grasped by performing the above attendance management. Therefore, the process of prompting the absence attendant to view the minutes of the meeting and the management of the viewing status of the minutes after the reminder are managed. it can.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
First, a schematic configuration of a network conference system including a Web conference server (network conference server) and a client terminal (user terminal) according to an embodiment of the present invention will be described. FIG. 1 is a diagram showing a schematic configuration of a network conference system including a Web conference server and a client terminal according to an embodiment of the present invention.

  In FIG. 1, reference numeral 100 denotes a Web conference system, which has a configuration in which a Web conference server 200 and a plurality of client terminals 300 and 400 (to be described later) are connected via a network such as LANs 101 and 102 and WAN 103. Reference numeral 200 denotes a Web conference server that provides an environment for using a Web conference to users of a plurality of client terminals 300 and 400 connected to the network and an environment that enables communication between the users. Here, the web conference is realized by displaying a virtual conference room on a browser screen started up by each of the client terminals 300 and 400. The virtual conference room is a conference room in which videos of a plurality of attendees as shown in FIG. The description of the example web conference screen shown in FIG. 14-2 will be described later.

  As shown in FIG. 1, the Web conference server 200 and the client terminals 300 and 400 are connected to each other via a network (LAN 101, 102 and WAN 103). In this embodiment, the client terminal 300 is a terminal used by a user who hosts a web conference, and the client terminal 400 is a terminal used by a user who participates in the web conference via the LAN 102 and the WAN 103. . The configuration of various terminals connected to the network in FIG. 1 is an example, and it goes without saying that there are various configuration examples depending on the application and purpose.

  With the above-described configuration, the web conference system 100 including the web conference server 200 can be used to manage attendance until the web conference is held, web conference holding processing, reminder processing for viewing the minutes for the absence after the web conference is completed, and the like. The characteristic processing of this embodiment is performed.

Next, a hardware configuration example of the Web conference server 200 illustrated in FIG. 1 will be described.
FIG. 2 is a diagram illustrating a hardware configuration example of the Web conference server 200 illustrated in FIG. 1. In FIG. 2, a CPU (Central Processing Unit) 201 comprehensively controls each device and controller connected to the system bus 204. Further, the ROM (read only memory) 202 or the external memory 211 has a BIOS (BaSic Input / Output System) (operating system program (hereinafter referred to as OS)) that is a control program of the CPU 201 and various types of web conference server 200 described later. Various programs and the like necessary for realizing the functions are stored. A RAM (Random Access Memory) 203 functions as a main memory, work area, and the like for the CPU 201. The CPU 201 implements various operations by loading a program necessary for execution of processing into the RAM 203 and executing the program.

  An input controller (input C) 205 controls input from a pointing device such as a keyboard 209 or a mouse (not shown). A video controller (VC) 206 controls display on a display device such as a CRT display (CRT) 210. The display is not limited to the CRT 210 but may be a liquid crystal display or the like. These are used by the user as necessary, and are not directly related to the essence of the present invention. The memory controller (MC) 207 is an adapter to a hard disk (HD), flexible disk (FD) or PCMCIA card slot for storing boot programs, browser software, various applications, font data, user files, editing files, various data, and the like. Controls access to an external memory 211 such as a compact flash (R) memory connected via the.

  A communication I / F (interface) controller (communication I / FC) 208 is connected to and communicates with an external device via the network 100, and executes communication control processing in the network 100. For example, the communication I / FC 208 can perform Internet communication using TCP / IP. Note that the CPU 201 enables display on the CRT 210 by executing outline font rasterization processing on a display information area in the RAM 203, for example. Further, the CPU 201 enables an instruction from the user with a mouse cursor (not shown) on the CRT 210.

  A web conference program 212 for realizing various functions of the web conference server 200 in the present embodiment is recorded in the external memory 211 and is executed by the CPU 201 by being loaded into the RAM 202 as necessary. It is. Further, the definition file 213 and various information tables 214 used by the web conference program 212 are stored in the external memory 211, and detailed description thereof will be described later.

  The hardware configurations of the client terminals 300 and 400 are the same as the hardware configuration of the Web conference server 200 shown in FIG. Further, the client terminals 300 and 400 further have a local interface (not shown), and for example, a general-purpose technology such as USB (Universal Sal Serial BuS) can be used. The client terminals 300 and 400 have a configuration capable of capturing an image using a USB camera (not shown), and images captured by the USB camera are captured at a predetermined interval (for example, 5 frames per second). , JPEG compression in QCIF format or H.264. It has a configuration capable of performing compression encoding such as H.263 and transmitting it to the Web conference server 200. Thereby, the Web conference server 200 receives real-time images from the client terminals 300 and 400.

Next, an outline of a processing flow of the web conference system 100 including the web conference server 200 illustrated in FIG. 1 will be described.
FIG. 3 is a diagram showing a processing flow of the Web conference system 100 including the Web conference server 200 shown in FIG. As described above, in the web conference system 100, the client terminal 300, the client terminal 400, and the web conference server 200 are connected to each other via a network. Then, the client terminals 300 and 400 execute various processes related to the Web conference via various operation screens provided from the Web conference server 200. An example of this will be described below, but details of each process in FIG. 3 will be described later. In the following description, an outline of each process shown in FIG. 3 will be described.

  As shown in FIG. 3, first, in step S001, the web conference system 100 performs conference reservation processing. As a result, when the web conference is held, the organizer can store the basic information such as reservation of the virtual conference room and the conference schedule, time, registration of the conference participant, etc. in the conference room reservation master prepared in the web conference server 200. A registration screen (for example, GUI) for registering the reservation data is displayed on the client terminal 300. At that time, information registration such as setting of automatic attendance confirmation processing of a person who intends to participate in the Web conference (who the organizer wants to participate) and setting of conference minutes recording for absentees is also performed. At this time, when the conference reservation on the registration screen is completed, the web conference system 100 delivers the conference opening guidance to the prospective participants of the web conference by an instant message. The instant message window has a function for a prospective participant to answer a meeting attendance. Note that instant message generally indicates a function that enables messages to be directly exchanged between terminals connected to a network. In the present embodiment, a message that is transmitted between client terminals via the Web server 200 is used. Include interaction.

  Next, in step S002, the web conference system 100 performs a process related to the attendance of the conference based on a reply from a prospective participant of the web conference. Specifically, this is a processing process in response to an operation in which a meeting participant who has received a meeting opening notification (the instant message) inputs an answer of attendance at the client terminal 400. Participants who have received the meeting notice will check their schedule, content, etc., make an attendance or absence decision, and use the attendance / absence reply function included in the meeting notice to confirm that they will Can communicate the intention to the meeting organizer. Note that the meeting holding notification is also a meeting attendance request for a person who is scheduled to attend the meeting.

  Next, in step S003, the Web conference system 100 performs automatic management of the reply status and automatic management of the attendance status in response to the conference opening notification (conference attendance request). For example, the Web conference organizer automatically receives information from the Web conference server 200 at a preset time, such as whether or not there is a reply from attendees who are scheduled to attend the conference and whether there are any absentees. Processing is performed.

  Next, in step S004, the web conference system 100 manages the reply state and attendance state manually at an arbitrary timing separately from the reply state and attendance state management processing automatically performed in step S003. Perform processing to provide an environment to perform.

  Next, in step S005, the Web conference system 100 performs processing for providing an environment in which the prospective participant can change his / her attendance after the prospective participant in the conference returns the attendance in step S002. Needless to say, the change procedure to be performed is reflected in steps S003 and S004.

  Next, in step S006, the web conference system 100 performs a process of actually holding the web conference when the date and time of the conference is actually reached. For example, when a web conference is held, if the conference organizer has set a minutes saving status for absentees in advance during the conference reservation process in step S001, and if there are absentees, Recording is automatically performed. Also, if there are absent persons, after the Web conference ends, an instant message for prompting the end of the meeting and browsing the meeting minutes is transmitted to the client terminal 400 of the absent person.

  Next, in step S007, the Web conference system 100 performs processing for providing an environment in which a person absent from the Web conference uses the client terminal 400 to browse the meeting minutes. Next, in step S008, the Web conference system 100 performs a process of instructing and managing a browsing status as to whether or not a conference absentee has browsed the minutes of the conference. For example, the web conferencing server 200 monitors the browsing state of the absence attendant's view of minutes, and the meeting organizer displays a list of unviewed persons by inputting instructions from the client terminal 300, and the absent person is displayed as necessary. Can send a message prompting them to view the minutes.

  Next, in step S009, the Web conference system 100 performs a process for deleting the minutes data. For example, when the Web conference server 200 determines that all meeting absentees have finished browsing the meeting minutes so that the hard disk capacity of the Web conference server 200 (in the external memory 211) is not compressed, the conference Delete recorded data. Whether or not to delete the minutes data at the discretion of the meeting organizer who operates the client terminal 300 when there is an unviewed person (unread absentee) even though two weeks have passed since the meeting ended. It has a function that can be determined.

  As described above, the web conference system 100 according to the present embodiment is a management function for attendance until the web conference is held, a web conference holding processing function, and browsing of minutes for those who are absent after the web conference ends. The dunning process and the browsing status of minutes after dunning can be managed.

Next, details of each process shown in FIG. 3 will be described.
First, the details of the conference reservation process in step S001 in FIG. 3 will be described. FIG. 4 is a diagram showing a detailed flow of the process of step S001 in FIG. As illustrated in FIG. 4, in step S <b> 112, the client terminal 300 requests the web conference server 200 for a conference reservation screen for reserving a web conference according to an instruction from a user (organizer) of the client terminal 300.

  Thereby, the web conference server 200 creates an information table (conference reservation table) for managing each status when the web conference is held in step S102. Specifically, the web conference server 200 creates a conference room reservation master 40 as shown in FIG. 5 as a conference reservation table, and manages each status when the web conference is held. In addition, the web conference server 200 transmits conference room reservation screen information to the client terminal 300. Thereby, in step S113, the client terminal 300 displays the conference room reservation screen 50 shown, for example in FIG.

  Here, FIG. 5 and FIG. 6 described above will be described. FIG. 5 is a diagram showing an example of a conference room reservation master in the present embodiment. As shown in FIG. 5, the following information is stored in association with the conference reservation number that specifies the conference reservation. Note that the conference reservation number is automatically assigned by the Web conference server 200 sequentially. The “conference room number” is information for specifying a conference room in which a web conference is held. “Meeting start date / time” is information relating to the date and time when the Web conference is started. “Meeting end date / time” is information relating to the date and time when the Web conference ends.

  The “participant ID” is information including at least a plurality of IDs for specifying a prospective participant (usually determined by the organizer) of the web conference. The “reply presence / absence flag” is information indicating the presence / absence of an attendance reply to the meeting opening notice distributed to all the prospective participants of the web conference, and 0 = no reply, 1 = reply. The “participation nonparticipation flag” is information indicating whether or not to participate in the web conference, and 0 = nonparticipation, 1 = participation. The “reply presence / absence flag” and “participation nonparticipation flag” are information stored in association with the “participant ID”. That is, for each prospective participant of the Web conference, information regarding the presence or absence of a reply and participation non-participation is stored.

  “Meeting recording flag” is information indicating whether or not to record the video and audio of the Web conference as the minutes of the Web conference, and 0 = not record, 1 = record. “Non-participant recorded data reference, unreferenced flag” is information indicating whether or not a person absent from the Web conference has viewed the minutes of the conference, and 0 = not referenced (unviewed), 1 = referenced (Browsed). The “participation / non-participation reply management flag” is information indicating whether the reply of participation / nonparticipation (attendance / absence) to the web conference is automatically managed or manually managed. 0 = not automatically managed, 1 = Manage automatically. “Participation / non-participation confirmation timing” is the above-mentioned “participation / non-participation reply management flag” flag = 1 (when automatically managing), the participation / non-participation reply is automatically confirmed. This is information for designating times t1 and t2.

  FIG. 6 is a diagram showing an example of a conference room reservation screen in the present embodiment. As shown in FIG. 6, the conference reservation date and time, the conference room number, the conference name (title), the selection of attendees (participants scheduled to participate) (selection of participant ID in this embodiment), and automatic management of attendance responses are performed. The organizer can specify whether or not to specify the confirmation time for reply / attendance status, whether or not to record minutes for absentees, and the like. However, it goes without saying that when there is only one virtual conference room, there is no particular need for a conference room number for identifying the conference room.

  Next, the description returns to FIG. In step S104, the Web conference server 200 initializes all the flags of the conference room reservation master 40 by setting them to 0. Next, in the client terminal 300, the organizer inputs the conference room reservation screen 50 displayed in step S113 (steps S115 to S118). As a result, the client terminal 300 transmits the reservation information input by the organizer on the conference room reservation screen 50 to the Web conference server 200.

  As a result, the Web conference server 200 receives the reservation information from the client terminal 300, and in step S103, based on the received reservation information, details of the Web conference to be implemented are stored in the conference room reservation master in the external memory 211. 40. Next, if there is an instruction to automatically manage attendance responses based on the reservation information received from the client terminal 300 (YES in step S105), the web conference server 200 proceeds to step S106, and the conference room reservation master 40 As “participation / non-participation reply management flag” = 1, the process proceeds to step S107. On the other hand, if there is no instruction to automatically manage attendance / reply based on the reservation information received from the client terminal 300 (NO in step S105), the web conference server 200 proceeds to step S109.

  Next, in step S <b> 107, the Web conference server 200 determines whether or not a reply / attendance check time is specified on the conference room reservation screen 50. Here, when the confirmation time of the reply / attendance status is designated, the Web conference server 200 proceeds to Step S108, and the designated confirmation time is set in the “participation / non-participation reply” of the conference room reservation master 40. Register at t1 and t2 of “presence / absence confirmation timing”, and proceed to step S109. If the confirmation time for the reply / attendance status is not specified, the web conference server 200 proceeds to step S109.

  In step S109, the Web management server 200 determines whether or not it has been instructed to record the minutes for absentees on the conference room reservation screen 50. Here, when the recording of the minutes for absentees is instructed (YES in Step S109), the process proceeds to Step S110, and the Web management server 200 sets “Recording flag for minutes” in the conference room reservation master 40 = Set to 1 and proceed to step S111. When the absence recording for the absentee is not instructed (NO in step S109), the Web management server 200 proceeds to step S111. Next, in step S <b> 111, the Web management server 200 delivers a conference opening notice to the client terminal 400 of the prospective participant selected as an attendee on the conference room reservation screen 50 by an instant message.

Thereby, the conference opening notification screen 60 shown in FIG. 8A is displayed on the client terminal 400 of each prospective participant (step S209 in FIG. 7 described later). FIG. 8A is a diagram showing an example of a conference opening notification screen in the present embodiment. As shown in FIG. 8A, on the conference holding notification screen 60, the date and time of the conference, the conference room number, the conference name, the content of the conference, etc. are notified to the prospective participants. In addition, the conference opening notification screen 60 prompts the attendees to reply to the attendance at the Web conference, and further includes an input field for inputting the reason for absence.
Thus, the detailed description of the conference reservation process in step S001 of FIG.

  Next, details of the reply process for the prospective participant in step S002 in FIG. 3 will be described. FIG. 7 is a diagram showing a detailed flow of the process of step S002 in FIG. As illustrated in FIG. 7, in step S <b> 201, in the Web management server 200, the CPU 201 controls the memory controller 207 to read the conference room reservation master 40 in the external memory 211. Further, as described above, in step S209, the client terminal 400 displays the conference opening notification screen 60 as shown in FIG. Here, in step S210, when a prospective participant of the web conference using the client terminal 400 performs an operation of specifying attendance or absence on the conference opening notification screen 60, the client terminal 400 displays the specified attendance information on the web. Transmit to the conference server 200. Thereby, the web conference server 200 receives attendance information from the client terminal 400.

  Next, in step S <b> 202, the web conference server 200 determines whether the prospective participant who is the transmission source of attendance information attends or is absent from the web conference based on the received attendance information. If it is determined that the prospective participant who is the sender of the attendance information is absent from the web conference, the process advances to step S205, and the web conference server 200 sets “participation nonparticipation flag” = 0 in the conference room reservation master 40. Set. In step S206, the web conference server 200 transmits a absence notice message to the conference organizer. In step S207, the Web conference server 200 transmits a conference minutes browsing password to the client terminal 400 that has returned the absence. As a result, the password notification screen 72 shown in FIG. 8C is displayed on the client terminal 400 that made the reply of absence. FIG. 8C is a diagram showing an example of a password notification screen for viewing the meeting minutes in the present embodiment.

  On the other hand, if it is determined that the prospective participant who is the sender of attendance information attends the web conference, the process proceeds to step S203, and the web conference server 200 sets “participation nonparticipation flag” = 1 in the conference room reservation master 40. In step S204, the web conference server 200 transmits an attendance message to the conference organizer. Next, in step S212, the web conference server 200 transmits a conference participation password to the client terminal 400 that has returned the attendance. As a result, the password notification screen 71 shown in FIG. 8B is displayed on the client terminal 400 that has returned the attendance. FIG. 8B is a diagram showing an example of a password notification screen for conference participation in the present embodiment.

Next, in step S <b> 208, the Web conference server 200 sets “reply presence / absence flag” = 1 related to the prospective participant (participant ID) who is the transmission source of attendance information in the conference room reservation master 40.
Thus, the attendance reply process in step S002 of FIG. 3 is completed.

  Next, the details of the automatic management of the reply status and the automatic management processing of the attendance status for the conference opening notification in step S003 in FIG. 3 will be described. FIG. 9 is a diagram showing a detailed flow of the process of step S003 in FIG. As shown in FIG. 9, in step S <b> 003, the Web conference server 200 reads the conference room reservation master 40 stored in the external memory 211 by the CPU 201. Next, in step S301, the Web conference server 200 refers to the “conference start year / month / date / time” of the read conference room reservation master 40 to determine whether or not the conference date / time has arrived. If yes, the reply / attendance status management process is terminated. If the meeting date has not arrived, the process advances to step S302, and the Web conference server 200 refers to the conference room reservation master 40 and sets the “participation / nonparticipation reply management flag” = 0 for the Web conference. If there is, the process ends. If “participation / non-participation reply management flag” = 1, the process proceeds to step S303.

  In step S303, the Web conference server 200 monitors the system timer, and the process of step S318, step S304, or step S305 causes the “return / participate reply” of the conference room reservation master 40 while the conference date / time has not arrived. The process advances to step S306 when the times t1 and t2 set in the “presence / absence confirmation timing” arrive. Note that the processes in steps S303 to S305 and S318 are daemon processes.

  Next, in step S306, the Web conference server 200 refers to the “reply presence / absence flag” of the conference room reservation master 40, and if there is a person who has not made an attendance reply, the process proceeds to step S307. A list of non-responders is generated and transmitted to the client terminal 300 of the meeting organizer. As a result, the client terminal 300 of the meeting organizer displays a list screen 75 of respondents who have not responded as shown in FIG. 10 in step S313. As shown in FIG. 10, the list screen 75 displays a list of absentees (persons scheduled to be absent) together with a list of non-repeaters, because it is treated as non-repeaters = absent.

  Next, in step S308, the Web conference server 200 selects whether or not to send a message prompting a reply operation to the client terminal 400 of the person who has not returned attendance information to the client terminal 300 of the meeting organizer. Send screen information. As a result, the client terminal 300 of the meeting organizer displays a selection screen that prompts the user to select whether or not to send a message prompting the reply work to the person who has not returned the attendance information in step S314. Thereby, the meeting organizer can transmit a message prompting a reply to the unreplyed person as necessary in step S315. Here, a transmission instruction according to whether the meeting organizer has selected a method for sending a message prompting a reply to a non-reply person or a method for not sending a message prompting a reply to a non-reply person. 200.

  Next, in step S309, the web conference server 200 determines whether or not to send a reply prompting instant message to the non-replyer in response to the transmission instruction described above. If it is determined to be transmitted, the process proceeds to step S310, an instant message for prompting a reply is transmitted to the client terminal 300 of the non-replyer, and the process proceeds to step S311. If it is determined not to transmit, the process proceeds to step S311.

Next, in step S <b> 311, the Web conference server 200 confirms whether “participation nonparticipation flag” = 0 exists in the conference room reservation master 40 (whether there are absent persons). Here, when there is no absentee, the Web conference server 200 returns to Step S303. If there are absent persons, the web conference server 200 proceeds to step S312 to generate information (for example, a list of absentees) for confirming the attendance status and transmits the information to the client terminal 300 of the meeting organizer. Thereby, the client terminal 300 of the meeting organizer displays the list screen 75 including the absentee list as shown in FIG.
Thus, the reply / attendance state automatic management process in step S003 of FIG. 3 is completed.

Next, details of the manual management of the reply state and the attendance state manual management process for the meeting opening notification in step S004 of FIG. 3 will be described. FIG. 11 is a diagram showing a detailed flow of the process of step S004 in FIG. As illustrated in FIG. 11, by the operation of the organizer, the client terminal 300 transmits an instruction to display a screen for confirming a reply state to the meeting opening notification to the web conference server 200 in step S403. As a result, in the Web conference server 200, the CPU 201 reads the conference room reservation master 40 stored in the external memory 211 in step S401, and in step S402, the “return presence / absence flag” and “participation nonparticipation” of the conference room reservation master 40 are read. Each status display data for displaying the list screen 75 as shown in FIG. 10 described above is generated with reference to the “flag” information, and is transmitted to the client terminal 300 of the organizer. Thereby, in step S404, the list screen 75 which can confirm a reply state as shown in FIG. 10 is displayed on the client terminal 300 of the meeting organizer.
As described above, the reply / attendance state manual management process in step S004 of FIG. 3 is completed.

  Next, the details of the change process for the attendance of the conference planner in step S005 of FIG. 3 will be described. FIG. 12 is a diagram showing a detailed flow of the process of step S005 in FIG. As illustrated in FIG. 12, in step S <b> 511, an instruction to display the conference room reservation screen 50 illustrated in FIG. 6 is transmitted from the client terminal 400 to the web conference server 200 by the operation of the prospective participant. Accordingly, in step S501, the Web conference server 200 reads the conference room reservation master 40 stored in the external memory 211 by the CPU 201, and sends the information on the conference room reservation screen 50 to the client terminal 400 based on the read information. Send. Thereby, as shown in step S512, the conference room reservation screen 50 is displayed on the client terminal 400. In this conference room reservation screen 50, the prospective participant changes the attendance returned to the requester.

  Next, in step S502, the Web conference server 200 determines whether there is a change in the status of participation / non-participation (attendance / absence). Here, if the attendance change described above has been performed, it is determined that the attendance status has changed, and the process advances to step S503, and the Web conference server 200 determines whether or not the attendance is changed to absence. If the attendance is changed from attendance to absence, the process proceeds to step S505, and the Web conference server 200 transmits a message to that effect to the meeting organizer, and the process proceeds to step S506, where the absentee client who has changed from attendance to absence is displayed. A password for browsing the meeting minutes is transmitted to the terminal 400. In step S507, the Web conference server 200 changes the “participation nonparticipation flag” of the conference room reservation master 40 to 0 (absence).

If it is a change from absence to attendance, the process advances to step S508, and the Web conference server 200 transmits a message to the conference organizer that the change from absence to attendance is made. In step S509, the change from absence to attendance is made. A password for entering the conference room is transmitted to the client terminal 400 of the attendee. Next, in step S510, the attendance absence status of the conference room reservation master 40 is changed to attendance.
Thus, the attendance change process in step S005 in FIG. 3 is completed.

  Next, details of the Web conference implementation process in step S006 of FIG. 3 will be described. FIG. 13 is a diagram showing a detailed flow of the process of step S006 in FIG. As shown in FIG. 13, first, in step S610, an entry operation from the client terminal 400 of the prospective participant to the web conference room is performed. Specifically, in response to an entry request from the client terminal 40 to the web conference room, the web conference server 200 returns information on the web conference entry screen to the client terminal 400 that has requested entry. As a result, the client terminal 400 displays a Web conference entrance screen 80 as shown in FIG. On this Web conference entry screen 80, the prospective participant performs an entry operation.

  FIG. 14A is a diagram illustrating an example of a web conference entrance screen according to the present embodiment. As shown in FIG. 14A, the web conference entrance screen 80 displays a list of conference room names of web conference rooms, and can be selected from a conference room name list area 81 and a conference room name list area 81 that can be selected. A usage status display area 82 that displays the current usage status of the conference room that has been selected, a room entry instruction area 83 in which a prospective participant indicates whether or not to enter the conference room selected in the conference room name list area 81, and A password input area 84 including an input field for inputting a password for authentication required for entering the room, a conference room information display area 85 for displaying information on the conference room selected in the conference room name list area 81, and the like. Yes. Further, as shown in FIG. 14A, information regarding the Web conference room being held, the current reservation status of the conference room selected in the conference room name list area 81, and the like may also be displayed.

  Next, in step S <b> 602, the web conference server 200 reads data regarding the corresponding conference from the conference room reservation master 40 in response to a room entry request from a prospective participant. Here, the password is also checked, and if it is OK, the screen information for displaying the Web conference screen is transmitted to the client terminal 400 that has requested entry. Thereby, in step S611, the client terminal 400 displays a Web conference screen 90 as shown in FIG.

  FIG. 14B is a diagram illustrating an example of a web conference screen according to the present embodiment. As shown in FIG. 14B, the Web conference screen 90 includes a self-display area 91 for displaying a video of a participant who uses the client terminal 400, a GUI, a GUI for adjusting the volume of the speaker, and the like. A message display area 92 for providing text communication (so-called chat function) by other web conference attendees, and another attendee display area 93 for displaying images of other attendees participating in the web conference Consists of The attendee's own video and other attendee's video are taken by a USB camera provided in the client terminals 300 and 400. In addition, attendees attending the Web conference can talk with each other through the microphone and the speaker in the client terminals 300 and 400 used by the attendees.

  Here, the description returns to FIG. In the following description, it is assumed that all prospective participants who can attend the Web conference have finished entering the room. In steps S <b> 603 and S <b> 609, the Web conference server 200 determines whether there is a participant who has not entered the room (not attended the conference) even though “participation nonparticipation flag” = 1 in the conference room reservation master 40. If so, the participant's “participation nonparticipation flag” is changed to zero. Next, in step S614, the Web conference server 200 determines whether there is a participant who has entered the room (participated in the conference) even though the “participation nonparticipation flag” = 0 in the conference room reservation master 40. If it is determined, the participant's “participation nonparticipation flag” is changed to 1 (step S615).

  Next, in step S <b> 616, the Web conference server 200 determines whether or not “recording processing flag for minutes” = 1 in the conference room reservation master 40. If the “recording flag for minutes” = 1, the process proceeds to step S617 to determine whether “participation nonparticipation flag” = 1 in the conference room reservation master 40 is determined. If “recording flag for minutes” is not 1, the process proceeds to step S605.

  Next, when it is determined in step S617 that “participation nonparticipation flag” = 1, the Web conference server 200 proceeds to step S604 and starts recording the meeting minutes in the external memory 211. If it is determined that “participation nonparticipation flag” = 1 is not true, the Web conference server 200 proceeds to Step S605.

  Next, in step S605, the Web conference server 200 performs a Web conference start process. Here, when each attendee performs a leaving operation from the web conference room, each client terminal 400 transmits a leave request to the web conference server 200. Thereby, in step S606, the Web conference server 200 performs a Web conference end process. Next, in step S618, the web conference server 200 determines whether or not the minutes are being recorded.

If it is determined that the minutes are being recorded, the process proceeds to step S607, and the web conference server 200 ends the process of recording the meeting minutes, and the process proceeds to step S608. If the Web conference server 200 determines that the minutes are not being recorded, the Web conference server 200 proceeds to step S608 to inform the client terminal 400 of the absent person (participant with “participation nonparticipation flag” = 0) and the conference end guidance. Send a record reading guide. As a result, the minutes terminal browsing guidance screen 151 as shown in FIG. 15 is displayed on the client terminal 400 of the absent person (step S619). FIG. 15 is a diagram showing an example of a minutes browsing guidance screen in the present embodiment. As shown in FIG. 15, the minutes browsing guide screen 151 includes means for selecting information on the meeting and whether to play the recorded minutes immediately or later. As a result, absentees can be actively encouraged to view the minutes.
Thus, the Web conference implementation process in step S006 of FIG. 3 is completed.

  Next, the details of the meeting minutes browsing process for the absent person in step S007 in FIG. 3 will be described. FIG. 16 is a diagram showing a detailed flow of the process of step S007 in FIG. As shown in FIG. 16, first, in step S <b> 708, the client terminal 400 transmits a minutes browsing start request to the web conference server 200 by a meeting attendance start operation of the absent person. Thereby, the Web conference server 200 receives the minutes browsing start request, proceeds to step S701, refers to the conference room reservation master 40 stored in the external memory 211, and responds to the minutes browsing start request. Read information about the meeting.

  Next, in step S <b> 702, the Web conference server 200 determines whether or not the “participation nonparticipation flag” of the absent person who has requested the minutes browsing start is “0”. Thereby, it is possible to prevent the useless reading of the minutes from being performed when the attendance request for starting the minutes has been transmitted even though the attendance is forgotten.

  Here, if the “participation nonparticipation flag” is 1, it is determined that the person is not absent, so the Web conference server 200 proceeds to step S707 and indicates that the person is not a person concerned for viewing the minutes (= absent). Is transmitted to the client terminal 400 that has requested to start reading the minutes. Thereby, in step S714, the client terminal 400 displays that it is not necessary to browse the minutes.

  In step S702, if the “participation nonparticipation flag” is 0, it is determined that the person is absent, so the Web conference server 200 proceeds to step S703 and displays a list of minutes in response to a request to start reading minutes. Information is transmitted to the client terminal 400. As a result, a minutes binder screen 110 as shown in FIG. 17 for displaying a list of minutes is displayed on the client terminal 400. FIG. 17 is a diagram showing an example of a minutes list display screen in the present embodiment. The absentee selects the minutes to be viewed from the list of minutes displayed on the minutes binder screen 110 (step S710). As a result, the client terminal 400 transmits information regarding the minutes selected by the absentee to the Web conference server 200. As a result, the Web conference server 200 receives information that the user wishes to browse the specific minutes, and is absent from the user of the user terminal 400 to input the password for authenticating the browsing of the specific minutes. Ask the person. Accordingly, when the absent person inputs the password at the user terminal 400 (step S711), the user terminal 400 transmits the input password to the web conference server 200.

  Next, in step S704, the Web conference server 200 performs authentication processing of the received password. If the password can be authenticated, the process advances to the next step S 705, and the Web conference server 200 performs a reproduction process of the recorded minutes stored in the external memory 211. As a result, the Web conference screen shown in FIG. 14B is played back and displayed on the client terminal 400 as the video of the minutes that have been played back.

Next, when the absent person finishes browsing the minutes at the client terminal 400 (step S713), the client terminal 400 transmits a browsing end signal to the web conference server 200. Thereby, the Web conference server 200 sets “non-participant recorded data reference, unreferenced flag” = 1 in the conference room reservation master 40 in step S706.
As described above, the minutes browsing process for the absent person in step S007 in FIG. In the process shown in FIG. 7, the meeting attendee is prevented from viewing the minutes by the process in step S707. However, the present invention is not limited to this, and the attendee may be allowed to view the minutes. .

  Next, the details of the state management process for viewing / unreading the minutes of meeting absentees in step S008 in FIG. 3 will be described. FIG. 18 is a diagram showing a detailed flow of the process of step S008 in FIG. As shown in FIG. 18, first, in step S805, the meeting organizer performs an operation of requesting a check screen for a person who has not read the minutes (unreferenced person) of the meeting absent person, so that the client terminal 300 performs the Web The conference server 200 is requested to check a screen of a person who has not read the minutes of the meeting absent. As a result, the web conference server 200 receives a request for a check screen for a person who has not read the minutes of the conference absent from the client terminal 300.

  Next, in the web conference server 200, in step S801, the CPU 201 reads the conference room reservation master 40 stored in the external memory 211, and in step S802, “Refer to recorded data of non-participants” in the conference room reservation master 40. With reference to the “unreferenced flag”, information for causing the client terminal 300 to display a list screen (check screen) of unread users is created and transmitted to the client terminal 300. Thereby, the client terminal 300 displays a check screen 120 as shown in FIG. 19 in step S806. FIG. 19 is a diagram showing an example of a check screen for those who have not read the minutes in the present embodiment. As shown in FIG. 19, the check screen 120 displays a list of participant IDs and participant names identified by the participant ID as a list of minutes unreaders. On the check screen 120, the meeting organizer who operates the client terminal 300 can select whether or not to send a message prompting the minutes unviewed person displayed on the check screen 120 to view the minutes. Selection means (“Yes” and “No” in FIG. 19) is included.

  Next, if there is no absentee in the list of the check screen 120 (NO in step S807), the process proceeds to step S809, and the check screen 120 is terminated. In addition, if there are absent persons in the list of the check screen 120 (YES in step S807) that the conference organizer wants to prompt the user to read the minutes, the process proceeds to step S808, and the instant message prompting the non-viewer to read the message. Is transmitted to the Web conference server 200.

Thereby, when the instruction | indication which transmits the said instant message from the client terminal 300 is received (YES of step S803), it progresses to step S804 and the web conference server 200 browses to a non-browser with a non-browser. Send a prompt message. As a result, in step S811, a browsing reminder message 130 as shown in FIG. 20 is displayed on the client terminal 400 of the unviewed person. FIG. 20 is a diagram illustrating an example of a browsing reminder message in the present embodiment. As shown in FIG. 20, the browsing reminder message 130 includes information regarding the conference such as the date and time of the conference, the conference room number, the conference name, and the content of the conference, and selection means for selecting whether or not to view the minutes immediately. including. If the instruction to transmit the instant message has not been received from the client terminal 300 (NO in step S803), the web conference server 200 ends the process.
Thus, the Web conference implementation process in step S008 of FIG. 3 is completed.

  Next, details of the minutes data erasing process in step S009 of FIG. 3 will be described. FIG. 21 is a diagram showing a detailed flow of the process of step S009 in FIG. As shown in FIG. 21, first, in step S901, the Web conference server 200 reads the conference room reservation master 40, and in step S902, the read “non-participant recorded data reference, unreferenced flag” of the conference room reservation master 40. ”To determine whether there is a person who has not read the minutes. If there is no unviewed person (NO in step S902), the process advances to step S905, and the web conference server 200 deletes the minutes data.

  If there is an unviewed person (YES in step S902), the web conference server 200 proceeds to step S903, and determines whether or not the minutes data has passed since the end of the conference. If the minutes data has passed two weeks (YES in step S903), the Web conference server 200 proceeds to step S906, and a message including that two weeks or more has passed to the client terminal 300 of the conference organizer. Send. If the minutes data has not passed for two weeks (NO in step S903), the web conference server 200 ends the process.

  Next, the client terminal 300 of the meeting organizer receives a message from the web conference server 200 in accordance with the process of step S906, and displays the message screen 140 as shown in FIG. 22 in step S908. . FIG. 22 is a diagram showing an example of a message screen in the case where there are minutes data after two weeks in the present embodiment. As shown in FIG. 22, the message screen 140 is composed of a message field that reports that there are minutes that have passed two weeks or more, a field that displays a list of unread users, and a field that displays the number of minutes. Has been. The message screen 140 also includes selection means for allowing the conference organizer to select whether or not to delete the minutes data.

  Here, when the conference organizer using the client terminal 300 inputs the data deletion permission / inhibition by the selection means, the client terminal 300 receives the data deletion permission / inhibition input in step S909, and the information is sent to the Web conference server. 200.

  Thereby, in step S904, the Web conference server 200 determines whether the information received from the client terminal 300 is erasable or not erasable of the minutes data. If it is possible to delete the minutes data (YES in step S904), the process proceeds to step S905, and the web conference server 200 performs a process for deleting the minutes data stored in the external memory 211. If the minutes data cannot be deleted (NO in step S904), the web conference server 200 ends the process.

  When the client terminal 300 holds the minutes data (instructed not to delete it), the client terminal 300 once ends this process and then starts this process again on the next day. Further, step S901 described above is a step in which the web conference server 200 is automatically activated.

  As described above, the Web conference server 200 according to the present embodiment participates by updating the “participation non-participation flag” in the conference room reservation master 40 from when the conference is notified to when the conference is held. Can manage the attendance of the prospective person. As a result, the web conference server 200 can display the web conference entrance screen 80 that prompts the prospective participants who are scheduled to attend the conference to enter the web conference room at the time when the conference is held, and the conference is efficiently held. It can be performed. Further, the Web conference server 200 confirms whether or not a prospective participant who is scheduled to attend at the time of the meeting is present, and determines the final attendance. As a result, absentees can be accurately grasped, and thereafter a message prompting the user to view the minutes can be reliably transmitted. In addition, since the Web conference server 200 can manage the viewing status of minutes by absentees, it is possible to prompt unread absentees to browse the minutes. In addition, since the Web conference server 200 automatically deletes the minutes that have been viewed by all absentees or the data of minutes that have passed a predetermined period of time, the storage capacity can be saved. In addition, as a method of attendance management described above, the Web conference server 200 includes a reply means for performing attendance replies in the conference opening notification, and collects attendance information by replies from meeting participants. Since the reply status can be managed, it is possible to send a reminder to a participant who has not yet attended.

  Although the embodiments have been described in detail above, the present invention can take an embodiment as, for example, a system, an apparatus, a method, a program, or a storage medium, and specifically includes a plurality of devices. The present invention may be applied to a system that is configured, or may be applied to an apparatus that includes a single device.

The above-described Web conference server 200 reads out programs for realizing various processing functions from the memory and executes them by the CPU 201, but this function is not limited to this. All or some of the functions may be realized by dedicated hardware.
The above-mentioned memory is a non-volatile memory such as a magneto-optical disk device or a flash memory, a recording medium such as a CD-ROM that can only be read, a volatile memory other than a RAM, or a computer read by a combination thereof. The recording medium may be a writable recording medium.

  Further, the above-described web conference server 200 records a program for realizing various functions shown in FIGS. 4, 7, 9, 11, 12, 13, 16, 18, and 21 on a computer-readable recording medium. Then, each processing may be performed by causing the computer system to read and execute the program recorded on the recording medium. Here, the “computer system” includes an OS and hardware such as peripheral devices.

  The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Further, the “computer-readable recording medium” refers to a volatile memory (RAM) in a computer system serving as a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. In addition, those holding a program for a certain period of time are also included.

The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the “transmission medium” for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line.
The program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, and what is called a difference file (difference program) may be sufficient.

A program product such as a computer-readable recording medium in which the above program is recorded can also be applied as an embodiment of the present invention.
The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes designs and the like that do not depart from the gist of the present invention.

It is a figure which shows schematic structure of the network conference system comprised from the web conference server and client terminal in one Embodiment of this invention. It is a figure which shows the hardware structural example of the web conference server 200 shown in FIG. It is a figure which shows the processing flow of the web conference system 100 containing the web conference server 200 shown in FIG. It is a figure which shows the processing flow of the network conference system shown in FIG. 1 in 2nd Embodiment. It is a figure which shows the meeting room reservation master example in this embodiment. It is a figure which shows the example of a conference room reservation screen in this embodiment. It is a figure which shows the detailed flow of a process of step S002 in FIG. It is a figure which shows the example of a meeting holding notification screen in this embodiment, and the example of a password notification screen for meeting participation and meeting minutes browsing. It is a figure which shows the detailed flow of a process of step S003 in FIG. It is a figure which shows the example of a list screen of the non-responder of attendance information in this embodiment. It is a figure which shows the detailed flow of a process of step S004 in FIG. It is a figure which shows the detailed flow of a process of step S005 in FIG. It is a figure which shows the detailed flow of a process of step S006 in FIG. It is a figure which shows the example of a web conference entrance screen in this embodiment. It is a figure which shows the example of a web conference screen in this embodiment. It is a figure which shows the example of a minutes browsing guidance screen in this embodiment. It is a figure which shows the detailed flow of a process of step S007 in FIG. It is a figure which shows the example of a minutes list display screen in this embodiment. It is a figure which shows the detailed flow of a process of step S008 in FIG. It is a figure which shows the example of a check screen of the minutes unread person in this embodiment. It is a figure which shows the example of a browsing reminder message in this embodiment. It is a figure which shows the detailed flow of a process of step S009 in FIG. It is a figure which shows the example of a message screen when the minutes data which passed for two weeks in this embodiment exist.

Explanation of symbols

100 Web conference system 101, 102 LAN
103 WAN
200 Web conference server 300, 400 Client terminal

Claims (14)

  1. A network conference server that provides a virtual conference room capable of real-time communication to a plurality of client terminals connected to a network,
    Reservation means for receiving and accepting reservation data for the conference using the virtual conference room including at least the date and time of the conference input by the client terminal used by the conference organizer and information related to the prospective participants of the conference; ,
    Storage means for storing conference reservation information including at least information input by the reservation means and information on attendance of the prospective participants for the conference;
    An event notification transmission unit that refers to the conference reservation information from the storage unit and transmits an event notification to the client terminal of each prospective participant,
    The conference reservation information in the storage unit is updated and the attendee's attendance to the conference is updated until the conference is held on the date and time after the event notification transmission unit transmits the event notification. An attendance management means for managing information on the network conference server.
  2. The holding notification means includes attendance notification means for sending back attendance information on attendance of the conference by the client terminal of each prospective participant included in the conference notification,
    The attendance management means updates the information related to attendance of the conference included in the conference reservation information each time it receives attendance information returned by the attendance reply means from the client terminal of the prospective participant. The network conference server according to claim 1, wherein information on attendance of prospective participants is managed.
  3.   The network conference server according to claim 1, wherein the attendance management unit confirms absentees at the time of the conference.
  4.   4. The network conference server according to claim 1, wherein the attendance management unit manages a reply status by the attendance reply unit. 5.
  5. In response to a request from the client terminal of the prospective participant, it further comprises attendance changing means for providing the client terminal with change instruction means for instructing change of the attendance information,
    5. The attendance management unit updates information on attendance of the conference included in the conference reservation information in accordance with an instruction of the change instruction unit provided by the attendance change unit. The network conference server according to claim 1.
  6.   It further comprises minutes reminding means for reminding the absentees of the meeting to browse the minutes of the meeting with reference to the attendance information of the meeting included in the meeting reservation information after the meeting is over. The network conference server according to claim 1, wherein the network conference server is a network conference server.
  7.   The network conference server according to claim 1, further comprising browsing management means for managing browsing history information regarding whether or not the absentee has browsed the minutes.
  8.   8. The network conference server according to claim 1, wherein the browsing management unit prompts a absentee who has not browsed the minutes based on the browsing history information to browse. 9.
  9.   Data of the minutes when it is determined that all the absentees have browsed the minutes by referring to the browsing history information, or when it is determined that a predetermined period has elapsed since the reading of the minutes was started The network conference server according to any one of claims 1 to 8, further comprising a minutes deleting means for deleting the minutes.
  10. A network conference method using a network conference server that provides a virtual conference room capable of real-time communication to a plurality of client terminals connected to a network,
    Reservation step for receiving and accepting reservation data for the conference using the virtual conference room including at least the date and time of the conference input by the client terminal used by the conference organizer and information on the prospective participants of the conference; ,
    From the storage means for storing conference reservation information including at least the information input in the reservation step and information on attendance of the prospective participant for the conference, the client terminal of each prospective participant is referred to the conference reservation information. Sending a meeting notice for sending the meeting notice;
    The conference reservation information in the storage means is updated and the attendee's attendance to the conference is updated until the conference is held on the date and time after the event notification is transmitted in the event notification transmission step. An attendance management step for managing information on the network conferencing method.
  11. In the holding notification step, each of the prospective participant's client terminals sends attendance return means for returning attendance information related to attendance of the conference included in the conference notification,
    The attendance management step updates the information on attendance of the conference included in the conference reservation information every time the attendance information returned by the attendance reply means is received from the client terminal of the prospective participant. The network conference method according to claim 10, wherein information on attendance of prospective participants is managed.
  12.   12. The network conference method according to claim 10, wherein the attendance management step confirms absentees at the time of the conference.
  13.   It further includes a minutes reminding step for reminding the absentees of the conference to view the minutes of the conference with reference to information on the attendance of the conference included in the conference reservation information after the conference ends. The network conference method according to any one of claims 10 to 12.
  14.   A program for causing a network conference server to execute the network conference method according to claim 10.
JP2003432794A 2003-12-26 2003-12-26 Network conference server, network conference method, and program thereof Pending JP2005190314A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2003432794A JP2005190314A (en) 2003-12-26 2003-12-26 Network conference server, network conference method, and program thereof

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2003432794A JP2005190314A (en) 2003-12-26 2003-12-26 Network conference server, network conference method, and program thereof

Publications (1)

Publication Number Publication Date
JP2005190314A true JP2005190314A (en) 2005-07-14

Family

ID=34790389

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2003432794A Pending JP2005190314A (en) 2003-12-26 2003-12-26 Network conference server, network conference method, and program thereof

Country Status (1)

Country Link
JP (1) JP2005190314A (en)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008066794A (en) * 2006-09-04 2008-03-21 Ntt Bizlink Inc Video conference reservation/execution control/recording control unit, video conference reservation/execution control/recording control method, and video conference reservation/execution control/recording control program
JP2012150768A (en) * 2011-01-21 2012-08-09 Nippon Telegr & Teleph Corp <Ntt> Service provision server, service provision system, service provision method, service provision program, and recording medium with service provision program recorded thereon
JP2014109811A (en) * 2012-11-30 2014-06-12 Konica Minolta Inc Conference material distribution system
US8867707B2 (en) 2011-03-23 2014-10-21 International Business Machines Corporation Automatically updating meeting information
JP2015035787A (en) * 2013-08-09 2015-02-19 株式会社リコー Communication system, management device, communication method, and program
JP2015061242A (en) * 2013-09-19 2015-03-30 株式会社ナカヨ Main device and notification method
JP2016533587A (en) * 2013-09-03 2016-10-27 インターナショナル・ビジネス・マシーンズ・コーポレーションInternational Business Machines Corporation Resolving the social networking information consumption gap
KR20180016514A (en) * 2015-10-21 2018-02-14 텐센트 테크놀로지(센젠) 컴퍼니 리미티드 Session initiation method and device

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008066794A (en) * 2006-09-04 2008-03-21 Ntt Bizlink Inc Video conference reservation/execution control/recording control unit, video conference reservation/execution control/recording control method, and video conference reservation/execution control/recording control program
JP2012150768A (en) * 2011-01-21 2012-08-09 Nippon Telegr & Teleph Corp <Ntt> Service provision server, service provision system, service provision method, service provision program, and recording medium with service provision program recorded thereon
US8867707B2 (en) 2011-03-23 2014-10-21 International Business Machines Corporation Automatically updating meeting information
JP2014109811A (en) * 2012-11-30 2014-06-12 Konica Minolta Inc Conference material distribution system
JP2015035787A (en) * 2013-08-09 2015-02-19 株式会社リコー Communication system, management device, communication method, and program
JP2016533587A (en) * 2013-09-03 2016-10-27 インターナショナル・ビジネス・マシーンズ・コーポレーションInternational Business Machines Corporation Resolving the social networking information consumption gap
JP2015061242A (en) * 2013-09-19 2015-03-30 株式会社ナカヨ Main device and notification method
KR20180016514A (en) * 2015-10-21 2018-02-14 텐센트 테크놀로지(센젠) 컴퍼니 리미티드 Session initiation method and device
JP2018518864A (en) * 2015-10-21 2018-07-12 ▲騰▼▲訊▼科技(深▲セン▼)有限公司 Session initiation method and device
KR102041172B1 (en) 2015-10-21 2019-11-06 텐센트 테크놀로지(센젠) 컴퍼니 리미티드 Session Initiation Method and Device

Similar Documents

Publication Publication Date Title
CN1694528B (en) Systems and methods for novel real-time audio-visual communication and data collaboration
EP1207650B1 (en) Method and apparatus for opening electronic conference
EP1596546B1 (en) Method and device for sharing data within an instant mesaging session
US7197544B2 (en) Voice and video greeting system for personal advertisement and method
US5907324A (en) Method for saving and accessing desktop conference characteristics with a persistent conference object
EP1589722A1 (en) Method, system, and apparatus for enabling near real time collaboration on an electronic document
US7016935B2 (en) Network conferencing system, equipment management method and data presentation method
TWI377832B (en) Command based group sms with mobile message receiver and server
US7451181B2 (en) Apparatus for controlling a shared screen
US6335739B1 (en) Terminal operation system
US20020169832A1 (en) Network conferencing system and proceedings preparation method, and conference management server and proceedings preparation method
RU2144283C1 (en) Method and device for controlling access of participants into conference call system
US8498396B2 (en) Notification to absent teleconference invitees
US20040117194A9 (en) Network conferencing system, attendance authentication method and presentation method
KR20110100638A (en) Synchronizing presentation states between multiple applications
US20140168350A1 (en) Audio/Video Conferencing System
US6714965B2 (en) Group contacting system, and recording medium for storing computer instructions for executing operations of the contact system
JP5799301B2 (en) Instant messaging service and method for providing multiple services extended from instant messaging service
JP2007280235A (en) Electronic conference support program, electronic conference suppot method, and information terminal for electronic conference system
JP4182464B2 (en) Video conferencing system
CN1971551B (en) Methods, apparatus for achieving text summarization
KR101721270B1 (en) Communications application having conversation and meeting environments
US9111263B2 (en) Adaptive meeting management
US20140317302A1 (en) Virtual collaboration session access
AU2002315877B2 (en) Multimedia information communication service system, user terminal program, and recording medium