JP2013232123A - Electronic conference system, terminal, and file providing server - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a conference system that, irrespective of the resolution of a display unit of a terminal, displays a page of conference material on the display unit in the same manner.SOLUTION: A meeting client 4a requests a Deep Zoom data piece having resolution corresponding to the resolution of a display unit 42 among a plurality of Deep Zoom data pieces different in resolution from each other to a file providing server 18. Then, a page of conference material is displayed on the display unit 42 using the Deep Zoom data piece received from the file providing server 18.

Description

  The present invention relates to an electronic conference system for conducting an electronic conference, and a terminal and a file providing server constituting the electronic conference system.

  Conventionally, many systems for conducting an electronic conference have been proposed. As an example, Patent Document 1 discloses a multimedia document conference participation system including a data communication network connected to a plurality of client stations, a meeting server, and a presentation server.

Special table hei 11-506595 (announced June 8, 1999)

  In the technique of Patent Document 1, a common presentation image is transmitted from a presentation server to all client stations. Therefore, when the resolutions of the screens at the client stations are different from each other, there is a problem that a difference occurs in the way images are displayed at the client stations.

  The present invention has been made to solve the above problems. And the objective is to provide the conference system which can display the page of a conference material on a display part similarly regardless of the resolution on the display part of a terminal.

  In order to solve the above problems, an electronic conference system according to the present invention is an electronic conference system for conducting an electronic conference, comprising a file providing server and a plurality of terminals provided with a display unit. The providing server provides each of the plurality of terminals with data requested from each of the plurality of terminals among the plurality of data having different resolutions representing the meeting material used for the electronic conference, Each of the terminals requests the file providing server for data corresponding to the resolution from the plurality of data having different resolutions, and uses the data provided from the file providing server, The conference material is displayed on the display unit.

  According to said structure, each terminal requests | requires the data showing the meeting material according to the resolution of the display part with which it is provided to a file provision server. The file providing server provides each terminal with data requested from each terminal, among the data representing the same conference material and having different resolutions. As a result, each terminal displays the conference material on the display unit using optimal data corresponding to the resolution on the display unit. Therefore, each terminal can display high-quality conference material on the display unit in the same manner regardless of the resolution of the display unit.

  In the electronic conference system according to the present invention, data having a resolution that greatly exceeds the resolution is not provided from the file providing server to a terminal including a display unit having a low resolution. Therefore, the time required for data transfer can be shortened, and as a result, the display speed of the conference material on the display unit of the terminal is improved.

  Furthermore, in the electronic conference system according to the present invention, each terminal requests required data from the file providing server. Therefore, the file providing server need only provide the data requested from each terminal to each terminal. This eliminates the need to transmit excessive data to all terminals, thereby reducing the burden on the file providing server.

In the electronic conference system according to the present invention, further,
Each of the plurality of terminals, when the user performs an operation for enlarging the page of the conference material displayed on the display unit, the enlargement rate of the page of the conference material, the resolution of the display unit, When the determination value is larger than the resolution of the data currently used for displaying the conference material page, the resolution at the level one level higher than the data is obtained. It is preferable to request the data from the file providing server, and display the enlarged meeting material on the display unit using the data of the resolution one level higher provided from the file providing server. .

  According to the above configuration, each terminal displays a resolution one higher than the currently used data if the enlargement rate is larger than a certain standard when the page of the conference material is enlarged and displayed according to the user's operation. Is obtained from the file providing server, and the page is enlarged and displayed using the data. Therefore, the image quality of the enlarged page is not deteriorated regardless of the enlargement ratio.

  In the electronic conference system according to the present invention, each of the plurality of data is configured by at least one fixed-size partial data, and each of the terminals includes the at least one partial data constituting the data. And requesting the file providing server for at least one partial data corresponding to a location displayed on the display unit in the meeting material page, and providing the at least one part provided from the file providing server. It is preferable to display the conference material page on the display unit using data.

  According to said structure, each terminal acquires the minimum partial data required when displaying the page of a meeting material from a file provision server. Therefore, the conference material page can be displayed at higher speed.

  In the electronic conference system according to the present invention, it is preferable that the plurality of data is deep zoom data.

  In order to solve the above problems, a terminal according to the present invention is a terminal that constitutes an electronic conference system for conducting an electronic conference together with a file providing server, includes a display unit, and includes the same page of conference materials Among the plurality of data having different resolutions, requesting the file providing server for data corresponding to the resolution of the display unit, and using the data provided from the file providing server, It displays on the said display part.

  According to the above configuration, high-quality conference materials can be displayed on the display unit in the same manner regardless of the resolution of the display unit.

  A file providing server according to the present invention is a file providing server that constitutes an electronic conference system for conducting an electronic conference together with a plurality of terminals provided with a display unit in order to solve the above-described problem. Among the plurality of pieces of data having different resolutions representing the same page of the conference material used in the above, the display unit receives data corresponding to the resolution requested from each of the plurality of terminals to each of the plurality of terminals. It is characterized by providing.

  According to said structure, the burden in a file provision server can be reduced.

  According to the electronic conference system of the present invention, it is possible to provide a conference system that displays the page of the conference material on the display unit in the same manner regardless of the resolution of the display unit of the terminal.

It is a block diagram which shows the principal part structure of the electronic conference system which concerns on one Embodiment of this invention. It is a block diagram which shows the principal part structure of the 1st-3rd client terminal which comprises the electronic conference system which concerns on one Embodiment of this invention. It is a figure showing an example of the window containing the list | wrist of the meeting which the user of a client terminal can participate. It is a figure which shows an example of the meeting creation window for inputting information in order to create a meeting. It is a figure which shows a mode that the window containing the user list of an electronic conference system was overwritten and displayed on the meeting creation window. It is a figure which shows the meeting creation window where the name of the participant of a meeting is displayed. It is a figure which shows a mode that the window containing the list | wrist of the data for the preservation | save of the meeting which the meeting creator participated in the past was overwritten and displayed on the meeting creation window. It is a figure which shows the meeting creation window where the name of the meeting material used in a meeting is displayed. It is a figure which shows an example of the meeting creation window for inputting the information for setting an agenda and a vote. It is a figure which shows the other example of the meeting creation window for inputting the information for setting an agenda and a vote. (A) is a figure which shows an example of the Deep Zoom data of the level 12 in this embodiment. (B) is a figure which shows an example of the Deep Zoom data of the level 11 in this embodiment. (C) is a figure which shows an example of the Deep Zoom data of the level 10 in this embodiment. (D) is a figure which shows an example of the Deep Zoom data of the level 9 in this embodiment. It is a figure which shows the meeting window containing the user interface for a presenter immediately after joining a meeting. It is a figure which shows the meeting window containing the user interface for a presenter displayed during the meeting using a meeting material. It is a figure which shows the meeting window containing the user interface for a participant displayed during the meeting using a meeting material. It is a figure which shows a mode that the tool bar was overwritten and displayed on the meeting window. It is a figure which shows a mode that the icon for selecting the thickness and color of a line was overwritten and displayed on the meeting window. It is a figure which shows the meeting window which displays the meeting material in which the annotation was written. It is a figure which shows a mode that the "eraser" sub icon and the "erasure" icon were overwritten and displayed on the meeting window. It is a figure which shows a mode that the window for selecting a meeting material or a whiteboard was overwritten and displayed on the meeting window. It is a figure which shows a mode that the document addition window was overwritten and displayed on the meeting window. It is a figure which shows a mode that the memo input window for inputting a keyboard memo was overwritten and displayed on the meeting window. It is a figure which shows a mode that the dynamic window containing the location selected by the user is overwritten and displayed on the meeting window.

  Embodiments of the present invention will be described below with reference to FIGS.

(Configuration of electronic conference system 1)
FIG. 1 is a block diagram showing a main configuration of an electronic conference system 1 according to an embodiment of the present invention. As shown in this figure, the electronic conference system 1 includes a cloud system 2, a client terminal 4, a client terminal 6, and a client terminal 8. The cloud system 2 includes a web server 12, a file conversion server 14, a meeting server 16 (conference control server), a file providing server 18, a video conference server 20, a database 22, and a file system 24. The meeting server 16 includes a meeting controller 16a (conference control unit). The meeting controller 16a controls the conference in the electronic conference system 1 in an integrated manner.

  In the electronic conference system 1, the client terminals 4, 6, and 8 are connected to each other via the cloud system 2 and the communication line 10. The communication line 10 is, for example, an internet line. With such a configuration, the electronic conference system 1 provides a network-type electronic conference to the user.

(Client terminals 4, 6, 8)
FIG. 2 is a block diagram showing a main configuration of the client terminals 4, 6, and 8 constituting the electronic conference system 1 according to the embodiment of the present invention. As shown in this figure, the client terminal 4 includes a meeting client 4a, an input unit 40, and a display unit 42. On the other hand, the client terminal 6 includes a meeting client 6a, an input unit 60, and a display unit 62. The client terminal 8 includes a meeting client 8a, an input unit 80, and a display unit 82. In the present embodiment, the client terminal 4 is a terminal used by a conference presenter. On the other hand, the client terminal 6 and the client terminal 8 are terminals used by conference participants.

  The meeting client 4 a is in charge of processing on the client terminal 4 side in the conference in the electronic conference system 1. The input unit 40 is an input device such as a keyboard, a mouse, and a touch panel. The user uses the input unit 40 when operating the client terminal 4 or inputting predetermined information into the client terminal 4. The display unit 42 is a display device such as a liquid crystal display device or an organic EL display device. The meeting client 4 a displays a conference screen on the display unit 42. In addition, the function of each member with which the client terminal 6 and the client terminal 8 are provided is the same as the function of each member with which the client terminal 4 is provided.

(Outline of electronic conference system 1)
The electronic conference system 1 is a network system for conducting an electronic conference. Each server in the cloud system 2 and each client terminal connected to the cloud system 2 can cooperate with each other to perform an electronic conference. The main function for performing the conference is provided by the cloud system 2. Therefore, the user of the electronic conference system 1 does not need to install special hardware for holding a conference. The user uses the electronic conference system 1 simply by installing special software for accessing the electronic conference system 1 in a terminal device that is generally distributed in the market such as a personal computer, a smartphone, or a tablet terminal. can do.

  In the electronic conference system 1, participants of the conference participate in the conference using a client terminal that can be connected to the cloud system 2. Therefore, each participant can participate in the conference at a desired place without gathering in a specific conference room.

  In the electronic conference system 1, materials used for the conference are provided as electronic data. Each participant in the conference can share the conference material in real time during the conference. Specifically, during the conference, each participant can view the same location in the same conference material at the same time on the screen of his / her client terminal. In addition, if a specific user (user with presenter authority) during the meeting changes the display state of the conference material, the screen of the client terminal of another user (user who does not have presenter authority) follows it. The display state of the conference material is changed in the same way. That is, the operation performed by the presenter on the client terminal is also reproduced in real time on the participant's client terminal. Accordingly, each attendee of the conference can participate in the conference without preparing paper materials.

  Data necessary for the conference is basically provided from the cloud system 2 to each client terminal. In addition, the writing to the conference material, the writing to the whiteboard, and the keyboard memo input by the user through each client terminal during the meeting are all provided to the cloud system 2 and stored in the cloud system 2. After the conference, all data used by each client terminal during the conference is deleted from the client terminal. In order to view data related to the conference after the conference ends, it is necessary to separately access the electronic conference system 1 and download the data.

  For each user who uses the electronic conference system 1, an authority corresponding to the role of the user in the conference is set for each conference. In the present embodiment, there are three types of roles: a moderator, a presenter, and a participant. The moderator has the authority to create a meeting. The presenter has the authority to present using specific meeting materials during the meeting. Participants do not have any of these powers and are in a position to hear the presenters present during the meeting.

  In a memory (not shown) of the client terminals 4, 6, and 8, a role table that defines functions that can be executed for each role is stored. This role table contains information that identifies the functions that the moderator, presenter, and participant can perform. For example, the moderator can add conference participants, but the presenter and participants include information indicating that conference participants cannot be added. In addition, presenters can present, but presenters and participants include information indicating that they are unable to present.

  The database 22 stores personal information of each user registered in the electronic conference system 1. This personal information includes at least an identifier (user ID) for uniquely identifying the user, an authentication password for logging in to the electronic conference system 1, a user's e-mail address, and a user's name.

(Conference flow)
When a conference is performed in the electronic conference system 1, the following procedure is followed. First, a conference organizer creates a conference in the electronic conference system 1. Any user registered in the electronic conference system can be a conference organizer. The role of the moderator is automatically set for the user who created the meeting. A user (moderator) who creates a conference inputs information regarding the conference, uploads conference materials used for the conference to the cloud system 2, and selects a user to participate in the conference. The moderator sets the role (authority) of each user in the conference.

  After the creation of the conference is completed, when it is time to start the conference, each user logs in to the electronic conference system 1 using his / her client terminal and participates in the conference. Even during the meeting, the user can participate in the meeting. Each user can write to the meeting material during the meeting. Writing to the conference material may be referred to as annotation in the present embodiment.

  Writing to the conference material by the presenter is automatically shared by the client terminals of all participants in the conference. On the other hand, writing on the conference material by the participant is handled as information unique to the participant. That is, it is not shared with other participants. Writing to the conference material by the presenter (shared annotation) is automatically performed in the database 22 in association with information (meeting ID, material ID, page ID) for identifying the corresponding conference, the conference material, and the page of the conference material. Saved in. On the other hand, the writing (individual annotation) on the conference material by the participant is automatically stored in the database 22 in association with the corresponding conference ID and the user ID of the participant.

  During the meeting, each attendee (including presenters and participants) of the meeting can enter a keyboard note on each page of the meeting material. A keyboard memo is text information input using a keyboard. The keyboard memo entered by the presenter is handled as information included in the minutes, and is distributed to each participant in the form included in the minutes after the meeting. On the other hand, the keyboard memo entered by the participant is stored in the database 22 and can be downloaded only by the entered participant.

  The electronic conference system 1 can also hold a conference using a whiteboard instead of the conference material. In this meeting, a whiteboard is displayed on the screen of each client terminal. Each user can write on the whiteboard during the meeting.

  Writing on the whiteboard by the presenter is automatically shared by the client terminals of all participants in the conference. On the other hand, writing on a whiteboard by a participant is treated as information unique to the participant. That is, it is not shared with other participants. The writing (shared annotation) on the whiteboard by the presenter is automatically stored in the database 22 in association with information (meeting ID, page ID) that specifies the corresponding conference and the corresponding whiteboard page. On the other hand, the writing (individual annotation) on the whiteboard by the participant is automatically associated with the information (meeting ID, page ID) for identifying the corresponding conference and the corresponding whiteboard page, and the user ID of the participant. Are stored in the database 22.

  During the meeting, each attendee (including presenters and participants) of the meeting can enter keyboard notes on each page of the whiteboard. A keyboard memo is text information input using a keyboard. The keyboard memo entered by the presenter is handled as information included in the minutes, and is distributed to each participant in the form included in the minutes after the meeting. On the other hand, the keyboard memo entered by the participant is stored in the database 22 and can be downloaded only by the entered participant.

  After the meeting, the cloud system 2 creates a minutes of the meeting. In addition, the conference material, writing to the conference material, writing to the whiteboard, and the keyboard memo of the presenter are managed in association with the minutes. By logging into the electronic conference system 1 after the conference ends, the user of the client terminal can download and browse the minutes of conferences that have participated in the past to his / her client terminal.

(Conference creation flow)
When a conference is performed in the electronic conference system 1, first, a conference organizer creates a conference in the electronic conference system 1. Any user registered in the electronic conference system can be a conference organizer. The role of the moderator is automatically set for the user who created the meeting. The moderator can select participants in the conference and can give the moderator or presenter authority to the attendee.

  Below, the flow of processing at the time of conference creation in the electronic conference system 1 will be described by taking as an example the case where the user of the client terminal 4 creates a conference. In this embodiment, the user of the client terminal 4 may be described as a conference creator.

(Login)
When a user of the client terminal 4 tries to participate in a conference held in the electronic conference system 1, first, the user starts the meeting client 4 a that is software for using the electronic conference system 1. After the meeting client 4a is activated, the user performs an operation for logging in to the electronic conference system 1 on the client terminal 4. Specifically, the user ID is input to the input unit 40. The meeting client 4a transmits the input user ID to the web server 12. The web server 12 acquires all conference information stored in the database 22 in association with the received user ID from the database 22 and transmits it to the meeting client 4a.

  In response to this, the meeting client 4a displays the window shown in FIG. FIG. 3 is a diagram illustrating an example of a window including a list of conferences in which the user of the client terminal 4 can participate. As illustrated in FIG. 3, the meeting client 4 a displays a screen including a list of conferences in which the user of the client terminal 4 can participate using the received conference information on the display unit 42. In the example of FIG. 3, three conferences are displayed vertically. The meeting client 4a displays the name of the meeting, the date and time of the meeting, and the name of the organizer for each meeting. These pieces of information are included in the conference information acquired from the meeting controller 16a.

  The window shown in FIG. 3 includes a button labeled “Create”. The conference creator presses this button when creating a new conference. As a result, the meeting client 4a displays the window shown in FIG. FIG. 4 is a diagram illustrating an example of a conference creation window for inputting information for creating a conference. The conference creator inputs various types of information necessary for creating a conference to the input unit 40 while viewing the conference creation window of FIG. Specifically, for example, the name of the conference, the date of the conference, the scheduled start time of the conference, the scheduled end time of the conference, and the purpose of the conference are input.

  The meeting client 4a displays a calendar on the display unit 42 so that the conference creator can input the date and time. The conference creator can easily input the date of the conference by selecting a desired date and time from the calendar. The input unit 40 outputs each input information to the meeting client 4a.

(Participant selection)
The meeting creator then selects a user to attend the meeting. The conference creator himself is automatically selected as an attendee for this conference. The window shown in FIG. 4 includes a button labeled “Select Participant”. The conference creator first presses this button when selecting a participant in the conference. The meeting client 4a informs the web server 12 that the “participant selection” button has been pressed.

  In response to this, the web server 12 reads the personal information stored in the database 22 and transmits it to the meeting client 4a. The meeting client 4a refers to the personal information and displays a window including a list of users of the electronic conference system 1 on the display unit 42 as shown in FIG. FIG. 5 is a diagram illustrating a state in which a window including a list of users of the electronic conference system 1 is overwritten and displayed on the conference creation window. In the example of FIG. 5, the names of the users are arranged in a list in the vertical direction.

  The meeting creator selects a user who wants to attend the meeting from the list of users displayed in FIG. A plurality of users can be selected simultaneously. The meeting client 4a acquires the user ID of each user selected as a participant by the conference creator from the personal information. Further, the user ID of the conference creator is acquired from the personal information.

  In the database 22, a group ID for identifying a group of attendees may be prepared in advance. This group ID is associated with each user ID of a plurality of users. If the user selects a group ID, a plurality of users belonging to the group are selected at a time as participants in the conference. This makes it possible to easily select a plurality of participants who attend a regularly held conference.

(Role setting)
The conference creator then sets the role of each user selected as a participant in the conference. In the present embodiment, the participants of the conference have a role of “presenter”, “participant”, or “moderator”. The meeting creator has the role of presenter in advance. The conference creator sets one of these roles for each participant in the conference. In the present embodiment, the user of the client terminal 6 and the user of the client terminal 8a attend the meeting. The conference creator sets the role of the user of the client terminal 6 to the participant. Similarly, the role of the user of the client terminal 8 is set to the participant.

  The meeting client 4a displays the name of the conference creator and the name of the user selected by the conference creator as a participant in the conference as shown in FIG. FIG. 6 is a diagram showing a conference creation window in which names of conference participants are displayed. In the example of FIG. 6, the name of one user is displayed side by side in the conference creation window. Further, a window showing detailed information about this user is displayed. In this window, in addition to the user name, the mail address is also displayed. The conference creator can also delete the selected user in the window of FIG.

(Selection of meeting materials)
The meeting creator selects meeting materials to be used in the meeting after selecting attendees of the meeting. The meeting creation window shown in FIG. 6 includes a button labeled “Select Content”. The conference creator first presses this button when selecting conference materials. The meeting client 4a informs the web server 12 that the “content selection” button has been pressed.

In response to this, the web server 12 acquires a list of data for storing conferences in which the conference creator has participated in the past, and transmits the list to the meeting client 4a. The meeting client 4a displays a window including the received list on the display unit 42 as shown in FIG. FIG. 7 is a diagram illustrating a state in which a window including a list of conference storage data that the conference creator has participated in the past is overwritten and displayed on the conference creation window. In the example of FIG. 7, the storage data are arranged in the vertical direction. The meeting client 4a may display a dedicated folder on the screen of the display unit 42, and further display a list of storage data in the folder.

  The conference creator selects conference materials to be used for the conference from the displayed list. As a result, the meeting client 4a displays the name of the selected conference material in the conference creation window as shown in FIG. FIG. 8 is a diagram showing a conference creation window in which names of conference materials used in the conference are displayed. In the example of FIG. 8, the name of one conference material is displayed in the conference creation window. As described above, in the electronic conference system 1, the data for storing the conference that the conference creator has joined in the past can be reused for a new conference.

  The conference creator can also select data stored in the client terminal 4 as conference material. When a file to be used as a conference material is dragged and dropped under the “content selection” label shown in FIG. 8, the file can be selected as a conference material to be used in the conference. The meeting creator can select a plurality of data as meeting materials used for one meeting. In this case, the individual meeting materials are used in order in the meeting. The input unit 40 outputs the data selected by the conference creator to the meeting client 4a.

(Agenda setting)
After the conference creator has selected the conference material, the conference creator sets who uses the conference material in what order in the conference. In the present embodiment, one presentation schedule using one meeting material in a certain meeting is denoted as “Agenda”.

  The meeting creation window shown in FIG. 6 and the like includes a tab labeled “Agenda & Vote”. The conference creator selects this tab when setting the agenda for the conference. Thereby, the meeting client 4a changes the display in the conference creation window as shown in FIG. FIG. 9 is a diagram showing an example of a meeting creation window for inputting information for setting an agenda and voting.

  The conference creator can set at least one agenda for one conference. At that time, information for setting the agenda is input to the window shown in FIG. The window shown in FIG. 9 includes a button labeled “Add Agenda”. The conference creator presses this button when setting a new agenda. As a result, the meeting client 4a displays a setting field corresponding to the new agenda in the conference creation window. The user inputs information necessary for setting the agenda in this setting field. In the example of FIG. 9, the presentation order, the name of the agenda, the description of the agenda, the presenter, and the conference material used for the presentation are set for each agenda. The setting of the agenda is arbitrary, and the conference creator does not necessarily need to set the agenda. That is, the electronic conference system 1 can also hold a conference for which an agenda is set.

  As shown in FIG. 9, a list of conference participants is displayed in the presenter input field in the agenda item. The conference creator can easily select an agenda presenter from this list.

  As shown in FIG. 10, a list of conference materials uploaded by the conference creator is displayed in the file selection field in the agenda item. FIG. 10 is a diagram showing another example of a meeting creation window for inputting information for setting an agenda and voting. The conference creator can easily select conference materials to be used in the agenda from this list. In addition, the list includes a character string “Request File”. When the conference creator selects this character string, the agenda presenter can be requested to upload the conference material. At that time, for example, an e-mail including a text requesting the uploader to upload the conference material is transmitted to the presenter.

(Voting settings)
The meeting creator sets a vote for the meeting being created. The window shown in FIG. 10 includes a button labeled “Add Vote”. The conference creator presses this button when setting a vote. As a result, a setting field corresponding to the new vote is displayed in the conference creation window. The user inputs a question sentence in this setting field. Multiple votes can be set for one meeting.

  When the input of information necessary for creating the conference is finished, the conference creator inputs an instruction to complete the creation of the conference to the input unit 40. For example, a “save” button at the upper right of the conference creation window is pressed. In response to this, the meeting client 4a executes a process for completing the creation of the conference. Specifically, all the information input or set by the conference creator during the conference creation process is transmitted to the web server 12. Also, the conference material data selected by the conference creator is uploaded to the web server 12.

(Generation of meeting information, etc.)
The web server 12 generates conference information, participant information, conference material information, page information, agenda information, and voting item information based on each information and conference material received from the meeting client 4a, and associates them with each other. Store in database 22.

  The conference information indicates the conference ID, the conference creator's user ID, the conference title, the conference date, the scheduled start time of the conference, the scheduled end time of the conference, the purpose of the conference, the status of the conference, and whether it is a confidential conference. Contains information and conference access code. The conference ID is an identifier for identifying a conference, and is given for each conference. The web server 12 generates and includes an individual and unique conference ID for each conference information. The information indicating the status of the conference indicates a status of creation, non-held, being held, or ended. Information indicating whether it is a confidential meeting takes a value of either true or false.

  The participant information includes at least a user ID of each user who participates in the conference and role information indicating the role of the participant. The role information indicates at least one of a presenter, a participant, and a presenter. A user may have the roles of presenter and participant in a conference. For example, there is a plurality of agendas for one conference, and a user has a presenter role in one agenda and a participant role in another agenda.

  The meeting material information includes at least a meeting material ID. The conference material ID is information for uniquely identifying the conference material uploaded to the web server 12. The conference material information is created when the conference material is uploaded to the web server 12 when the conference is created.

  The page information includes at least a page ID. The page ID is an identifier for uniquely identifying each page of the conference material uploaded to the web server 12.

  The agenda information includes, for each agenda set in the conference, the presentation order, the name of the agenda, the description of the agenda, the user ID of the presenter of the agenda, the announcement time, and the conference material ID of the conference material used for the announcement. Yes.

  The voting item information includes at least a question (voting item) set for each announcement. At the end of the presentation, the presenter presents the questions included in the voting item information to each participant and prompts them to vote whether or not they agree with the questions. The voting results by each participant are aggregated and stored in the database 22 in association with the corresponding conference ID as voting result information including the voting results.

(Creation of Deep Zoom data)
The web server 12 stores the conference material information and the conference information in the file system 24 in association with the conference material received from the meeting client 4a. The file conversion server 14 monitors the file system 24 and checks whether new data is stored in the file system 24 at regular intervals. When it is detected that new data (conference material) is stored in the file system 24 from the web server 12, the data is converted into deep zoom data. The electronic conference system 1 uses Deep Zoom data created at this time as conference material.

  The conference material (original conference material) stored in the file system 24 by the web server 12 is data of a format specified by the application, created by some application. Examples of applications include, but are not limited to, word processing software, spreadsheet software, or presentation software. The file conversion server 14 reads the original meeting material from the file system 24 and first converts it into vector format data (vector data). The vector format includes, for example, XPS format or PDF format.

  The file conversion server 14 divides the vector data obtained from the original data for each page. At this time, a page ID for identifying each page is created.

  The file conversion server 14 converts vector data for each page into JPEG data of level 12. In the present embodiment, the number of dots in the horizontal direction of this JPEG data is 4096. On the other hand, the number of dots in the vertical direction in the JPEG data is a number corresponding to the aspect ratio in the original data. Specifically, the ratio between the number of vertical dots and the number of horizontal dots in the JPEG data is equal to the ratio between the vertical length and the horizontal length in the original data. This JPEG data is level 12 data in Deep Zoom data.

  In the majority of cases, the number of horizontal dots in the original data is less than 4096. Therefore, JPEG data at level 12 is usually expanded from the original data.

  The file conversion server 14 creates level 11 JPEG data, which is one level below, from the level 12 JPEG data. The resolution of level 11 JPEG data is half that of level 12 JPEG data. That is, the number of horizontal dots in the level 11 JPEG data` is 2048.

  The file conversion server 14 further creates level 10 JPEG data, which is two levels below, from the level 12 JPEG data. The resolution of level 10 JPEG data is a quarter of the resolution of level 12 JPEG data. That is, the number of horizontal dots in the level 10 JPEG data is 1024.

  The file conversion server 14 further creates level 9 JPEG data, which is three levels below, from the level 12 JPEG data. The resolution of level 9 JPEG data is one-eighth the resolution of level 12 JPEG data. That is, the number of horizontal dots in the level 9 JPEG data is 512.

(Divided into tiles)
The file conversion server 14 divides each level of JPEG data into tiles (partial data) of a certain size. Thereby, Deep Zoom data is created from each JPEG data. In the present embodiment, the size of the tile is 1/8 of the size of the JPEG data at level 12. That is, it is equal to the size of level 9 JPEG data. Therefore, the number of horizontal dots of the tile is 512. However, this is only an example, and the tile size can be set arbitrarily. Individual tiles are preferably similar to the original JPEG data.

  FIG. 11A is a diagram showing an example of deep zoom data of level 12 in the present embodiment. FIG. 11B is a diagram illustrating an example of deep zoom data of level 11 in the present embodiment. FIG. 11C is a diagram showing an example of level 10 deep zoom data in the present embodiment. FIG. 11D is a diagram showing an example of level 10 deep zoom data in the present embodiment.

(Save Deep Zoom data)
The file conversion server 14 creates Deep Zoom data from all meeting materials newly detected from the file system 24. All the created deep zoom data (tiles of JPEG data) are stored in the file system 24 in association with the conference ID. At that time, each Deep Zoom data is associated with a corresponding material ID and page ID.

  The file conversion server 14 also stores level 12 JPEG data in the file system 24 in association with the corresponding material ID and page ID. This JPEG data is used when creating conference storage data after the conference ends.

  The file providing server 18 stores a copy of the Deep Zoom data stored in the file system 24 in the file providing server 18. The file providing server 18 manages each provided Deep Zoom data in association with the corresponding conference ID, the corresponding material ID, and the corresponding page ID.

  The file providing server 18 creates page information including all page IDs created when each vector data is divided into data for each page, and stores the page information in association with the corresponding conference information in the database 22.

(Advantages of Deep Zoom data)
The file conversion server 14 once converts the original data of the conference material into vector data, and generates JPEG data of 4096 dots in width from the vector data. Thereby, it is possible to generate JPEG data of an image that is displayed clearly without jaggedness.

  Deep Zoom data used at the time of a conference in the electronic conference system 1 is JPEG format data. Therefore, it can be used universally regardless of the type of operating system of the client terminal.

(How to use Deep Zoom data)
The client terminal 4 acquires conference material data to be displayed on the display unit 42 from the file providing server 18. At that time, the file providing server 18 provides the Deep Zoom data of the conference material to the client terminal 4. The client terminal 4 may acquire a tile that covers a part actually displayed on the screen of the display unit 42 from the file providing server 18 among the plurality of tiles constituting the Deep Zoom data. For example, when the conference material is displayed using the level 11 deep zoom data shown in FIG. 11B, it is necessary to display the conference material in an enlarged manner. At this time, if the enlargement ratio is within 2 times, only 16 tiles indicated by reference numeral 100 in FIG. This is because if the enlargement ratio is within 2 times, the entire image shown in FIG. 11B is completely covered by 16 tiles indicated by reference numeral 100 in FIG.

  In this way, the client terminal 4 acquires only deep zoom data necessary for display from the file providing server 18. Therefore, since the amount of data to be downloaded can be reduced, the display of the conference material can be switched more quickly.

  In the electronic conference system 1 according to the present embodiment, the conference creator can input or select information necessary for creating a conference within one screen. Therefore, a meeting can be created efficiently.

  In response to an instruction from the conference creator, the web server 12 can transmit an e-mail requesting uploading of the conference material to each user set as a conference participant.

  In the electronic conference system 1 of the present embodiment, the conference material does not necessarily need to be uploaded. That is, the conference creator can create a conference that does not use conference materials. In a meeting in which no meeting material is uploaded, a whiteboard is displayed on the screen of each client terminal instead of the meeting material. Then, the conference is held in such a manner that the attendees share the whiteboard during the conference.

(Conference using conference materials)
How to proceed with the conference using the conference material in the electronic conference system 1 will be described. Below, the case where the user of the client terminal 4 announces as a presenter is mentioned as an example. Note that both the user of the client terminal 6 and the user of the client terminal 8 participate as participants in this conference.

  FIG. 12 is a diagram showing a conference window including a user interface for the presenter immediately after joining the conference. Immediately after the user of the client terminal 4 joins the conference, the meeting controller 4a displays the conference window shown in FIG.

  FIG. 13 is a diagram showing a conference window including a user interface for a presenter displayed during a conference using conference materials. The user of the client terminal 4 has a presenter role. Therefore, the meeting client 4a displays the conference window shown in FIG. 12 on the display unit 42 during the conference using the conference material. In the conference window of FIG. 13, the color of the “presentation” button in the user interface is the one corresponding to the presenter (orange). In addition, an “up share” button is displayed below the “announce” button.

  FIG. 14 is a diagram showing a conference window including a user interface for participants displayed during a conference using conference materials. The user of the client terminal 6 has a participant role. Therefore, the meeting client 6a displays a conference window shown in FIG. 13 on the display unit 62 during the whiteboard conference. In the conference window of FIG. 13, the color of the “presentation” button in the user interface is in accordance with the presenter (gray). In addition, a “Raise Hand Button” is displayed below the “Announcement” button. When the user of the client terminal 6 has a role of a participant and a moderator, the color of the “presentation” button is a color (blue) corresponding to the role. Accordingly, the user of each client terminal can easily know his / her role by confirming the color of the “presentation” button.

(Page switching in the client terminal 4)
In the case of a conference using conference materials, the same page of the same conference materials is displayed on the screens of the client terminals of all the participants of the conference at the start of the conference. The presenter performs an operation for switching the page of the conference material on the input unit 40 in the client terminal 4. When the input unit 40 accepts this operation, the meeting client 4a transmits a signal (page request signal) for requesting the file providing server 18 for Deep Zoom data of the page after switching. At the same time, a signal (instruction signal) for instructing page switching of the conference material is transmitted to the meeting controller 16a.

  The meeting client 4a executes the following process when transmitting the page request signal. First, the meeting client 4a acquires the resolution of the display unit 42, and determines the level of Deep Zoom data requested from the file providing server 18 based on the resolution. Specifically, the level of Deep Zoom data having a resolution one step higher than the resolution of the display unit 42 is determined as the level of Deep Zoom data requested from the file providing server 18. For example, when the resolution of the display unit 42 is 1080 dots vertically and 1920 dots horizontally, the resolution of Deep Zoom data that is one step higher than this resolution is a resolution of 2048 dots horizontally. Therefore, in this case, the level of the requested deep zoom data is determined to be level 11.

  Further, the meeting client 4a calculates the row number and column number of the tile in the Deep Zoom data requested to the file providing server 18. At that time, among all the tiles constituting the Deep Zoom data, the tiles necessary for the screen display of the display unit 42 are first identified, and the next row number and column number are calculated.

  The meeting client 4a includes the conference request ID, the document ID of the conference material currently used for the presentation, the page ID of the page after switching, the level of the Deep Zoom data, and the tile matrix number in the page request signal. Transmit to the providing server 18. At that time, HTTP (or TCP) is used as a communication protocol.

  The file providing server 18 specifies the deep zoom data requested from the meeting client 4a based on the received page request signal. Since the Deep Zoom data is stored in the file providing server 18 in advance, the file providing server 18 does not need to acquire the Deep Zoom data from the file system 24.

  The file providing server 18 obtains the conference ID, material ID, page ID, deep zoom data level, and tile matrix number included in the received page request signal. Then, first, Deep Zoom data corresponding to the conference ID, material ID, page ID, and level is specified. Next, the tile indicated by the matrix number of the tile is acquired from the specified Deep Zoom data.

  The file providing server 18 transmits the acquired Deep Zoom data tile to the meeting client 4a. The meeting client 4a displays the tile of the received Deep Zoom data on the display unit 42. Thereby, the page of the meeting material displayed on the screen of the client terminal 4 is switched. Usually, since the resolution of the received deep zoom data is larger than the resolution of the display unit 42, the meeting client 4a displays the received deep zoom data after reducing it so as to match the resolution of the display unit 42.

(Synchronization processing in the client terminal 6)
In parallel with the transmission of the page request signal to the file providing server 18, the meeting client 4a transmits an instruction signal for instructing the meeting controller 16a to switch pages of the conference material. At that time, the meeting client 4a includes the material ID of the conference material currently used for the presentation and the page ID of the page after switching in the instruction signal. The meeting controller 16a transmits the received instruction signal to the client terminals of all participants other than the presenters participating in the conference. In this embodiment, the destination is the meeting client 6a and the meeting client 8a.

  When the meeting client 6a receives the instruction signal, the meeting client 6a requests the file providing server 18 for Deep Zoom data of the page after switching. The details of the processing at that time are the same as the processing when the meeting client 4a requests the Deep Zoom data from the file providing server 18. As a result, the meeting client 6 a transmits a page request signal for requesting an optimum level of deep zoom data according to the resolution of the display unit 62 to the file providing server 18.

  Based on the received page request signal, the file providing server 18 specifies the deep zoom data requested from the meeting client 6a. The processing at that time is the same as the processing at the time of specifying Deep Zoom data requested from the meeting client 4a. Therefore, detailed description is omitted. As a result, the file providing server 18 specifies deep zoom data at an optimum level according to the resolution of the display unit 62. Therefore, when the resolution of the display unit 62 is significantly different from the resolution of the display unit 42, the file providing server 18 transmits Deep Zoom data at a level different from the level of Deep Zoom data transmitted to the meeting client 4a to the meeting client 6a. Will do.

  For example, when the resolution of the display unit 42 is 1980 dots wide, the file providing server 18 transmits the level 11 deep zoom data to the meeting client 4a. On the other hand, when the resolution of the display unit 62 is 800 dots wide, the file providing server 18 transmits level 10 deep zoom data to the meeting client 6a. Even if the levels are different from each other, the Deep Zoom data transmitted from the meeting client 4a and the meeting client 6a by the file providing server 18 is the same page data of the same conference material.

  The file providing server 18 transmits the acquired Deep Zoom data tile to the meeting client 6a. The meeting client 6a displays the received deep zoom data tile on the display unit 62. Thereby, the page of the meeting material displayed on the screen of the client terminal 6 is switched. At this time, the same page as that displayed on the screen of the client terminal 4 is displayed on the screen of the client terminal 6.

(Synchronization processing in the client terminal 8)
When the meeting client 8a receives the instruction signal, the meeting client 8a requests the file providing server 18 for Deep Zoom data of the page after switching. The details of the processing at that time are the same as the processing when the meeting client 4a requests the Deep Zoom data from the file providing server 18. As a result, the meeting client 8a transmits a page request signal for requesting an optimum level of deep zoom data according to the resolution of the display unit 82 to the file providing server 18.

  The file providing server 18 specifies the deep zoom data requested from the meeting client 8a based on the received page request signal. The processing at that time is the same as the processing at the time of specifying Deep Zoom data requested from the meeting client 4a. Therefore, detailed description is omitted. As a result, the file providing server 18 specifies deep zoom data at an optimum level according to the resolution of the display unit 82. Therefore, when the resolution of the display unit 82 is significantly different from the resolution of the display unit 42, the file providing server 18 transmits Deep Zoom data at a level different from the level of Deep Zoom data transmitted to the meeting client 8a to the meeting client 8a. Will do.

  For example, when the resolution of the display unit 42 is 1980 dots wide, the file providing server 18 transmits the level 11 deep zoom data to the meeting client 4a. On the other hand, when the resolution of the display unit 62 is 512 dots in the horizontal direction, the file providing server 18 transmits level 9 deep zoom data to the meeting client 8a. Even if the levels are different from each other, the Deep Zoom data transmitted by the file providing server 18 from the meeting client 4a and the meeting client 8a remains the same page data of the same conference material.

  The file providing server 18 transmits the acquired Deep Zoom data tile to the meeting client 8a. The meeting client 8a displays the tile of the received deep zoom data on the display unit 62. Thereby, the page of the meeting material displayed on the screen of the client terminal 8 is switched. At this time, the same page as that displayed on the screen of the client terminal 4 is displayed on the screen of the client terminal 8.

(Function and effect)
As described above, in the electronic conference system 1, when the presenter switches the conference material page displayed on the screen of the client terminal 4, the conference material page displayed on the screen of the client terminal 6 or 8 of each participant. Can be switched in the same way. That is, the conference material page switching in the presenter's client terminal 4 is reproduced synchronously in the participant's client terminals 6, 8. Therefore, even if a participant does not switch the conference material page by himself / herself, the conference material page is automatically switched following the progress of the presentation by the presenter. This allows each participation to focus on the presentation by the presenter.

  Further, in the electronic conference system 1, the file providing server 18 does not uniformly provide the Deep Zoom data having the same resolution to the client terminals 4, 6, 8, but for each client terminal 4, 6, 8. Deep zoom data closest to the resolution of the display unit included in the terminals 4, 6 and 8 is provided. Therefore, unnecessary large resolution Deep Zoom data is not provided to a client terminal having a display unit with a small resolution. Thereby, the speed | rate at the time of transmitting Deep Zoom data to each client terminal can be improved. As a result, the display speed of the conference material page in each of the client terminals 4, 6, and 8 can be improved. Also, each client terminal 4, 6, 8 can use optimum deep zoom data according to the resolution of the display unit.

  Further, in the electronic conference system 1, each client terminal 4, 6, 8 requests deep zoom data required for display from the file providing server 18, and the file providing server 18 responds to the request by the deep zoom data. Provided to each client terminal 4, 6, 8. In other words, Deep Zoom data is not pushed from the file providing server 18 to each client terminal. As a result, the Deep Zoom data transmitted from the file providing server 18 can be cached using a content delivery network or the like, so that the speed when transmitting the Deep Zoom data can be greatly improved.

(Enlarge page)
The meeting client 4a can enlarge and display the currently displayed page of the conference material according to the operation by the presenter. When the conference material is enlarged and displayed on the client terminal 4, the same conference material is also enlarged and displayed on the client terminal 6 and the client terminal 8 synchronously. The processing flow at that time will be described below.

  First, the presenter performs an operation on the input unit 40 for enlarging and displaying the page of the conference material currently displayed on the display unit 42. The input unit 40 informs the meeting client 4a of the content of the user operation. The meeting client 4a calculates the expansion rate of the conference material based on the notification from the input unit 40.

  Based on the calculated enlargement ratio and the resolution of the display unit 42, the meeting client 4 a determines whether or not it is necessary to acquire deep zoom data at a different level from the deep zoom data currently used for displaying the conference material. judge. At that time, a predetermined determination value obtained by multiplying the enlargement ratio and the resolution of the display unit 42 is first obtained. Then, the determination value is compared with the resolution of Deep Zoom data that is one level higher than the level of Deep Zoom data currently used.

  When the determination value is larger than the resolution of the deep zoom data of the next level, the meeting client 4a determines that it is necessary to acquire deep zoom data of a level one higher than the current deep zoom data. To do. Therefore, the file providing server 18 is requested for Deep Zoom data that is one level higher. Then, the conference material is enlarged and displayed using the acquired one-level deep zoom data.

  For example, it is assumed that the resolution of the display unit 42 is 1280 dots in width and the meeting client 4a is currently displaying the conference material without expanding at all using the deep zoom data of level 11 (2064 dots in width). Here, if the presenter performs an operation for enlarging the page of the conference material, and the calculated enlargement ratio is 2 (200% enlargement), the meeting client 4a obtains 1280 dots × 2 = 2560 dots as a determination value. . This determination value is larger than the resolution of deep zoom data currently used (horizontal 2560 dots) and smaller than the resolution of deep zoom data of level 12 that is one level higher than level 11 (horizontal 4096 dots). At this time, the meeting client 4a determines that it is necessary to acquire Deep Zoom data of the next higher level.

  On the other hand, when the enlargement ratio is small, that is, when the determination value is smaller than the resolution of the deep zoom data of the next higher level, the meeting client 4a does not need to acquire the deep zoom data of the higher level. Is determined. Therefore, the conference material is enlarged and displayed by using the current deep zoom data.

  By enlarging and displaying the meeting material, a part of the whole displayed before being enlarged is displayed. Therefore, the meeting client 4a calculates the position and range of the part actually displayed on the display unit 42 after the enlarged display in the entire page. Specifically, the upper left coordinates of the enlarged display location and the vertical and horizontal sizes of the enlarged display location are calculated. Thereby, the meeting client 4a creates position information indicating the position of the enlarged display location and range information indicating the range.

  The meeting client 4a transmits an instruction signal instructing to change the display state of the conference material to the meeting controller 16a. At that time, the instruction signal includes the enlargement ratio, position information, and range information, the material ID of the conference material currently displayed, and the page ID of the currently displayed page. The meeting controller 16a transmits the received instruction signal to the client terminals of all participants other than the presenters participating in the conference. In this embodiment, the destination is the meeting client 6a and the meeting client 8a.

  The meeting client 6a first obtains a determination value obtained by multiplying the enlargement ratio included in the received instruction signal and the resolution of the display unit 62. Then, the determination value is compared with the resolution of Deep Zoom data that is one level higher than the level of Deep Zoom data currently used. Based on the comparison result, the meeting client 6a determines whether to use the current Deep Zoom data as it is, or whether it is necessary to acquire Deep Zoom data that is one level higher. Since the method of determination at this time is the same as the method of determination performed by the meeting client 4a using the determination value, detailed description is omitted.

  The meeting client 6a uses the position information and the range information included in the instruction signal when the page of the conference material is enlarged and displayed using the Deep Zoom data. Specifically, first, with reference to the position information and the range information, a location in the page to be displayed on the display unit 62 after being enlarged is specified. Then, the specified portion is enlarged to a size corresponding to the enlargement ratio and displayed on the display unit 62. As a result, the same portion of the page displayed on the display unit 42 of the client terminal 4 is enlarged in the display unit 62 in the same manner. That is, the enlarged display of the page on the client terminal 4 is also reproduced on the client terminal 6 in synchronization.

  When the meeting client 8a receives the instruction signal, the meeting client 8a enlarges and displays the conference material page. Since the processing performed at that time is the same as the processing when the client terminal 6 enlarges and displays the page of the conference material, detailed description thereof is omitted.

  As described above, in the electronic conference system 1, when the client terminal 4 enlarges and displays the conference material page according to the operation by the presenter, the client terminal 6 and the client terminal 8 also synchronize with the same conference material. Zoom in on the same page in the same way. Further, each client terminal always uses the optimum deep zoom data according to the enlargement ratio and resolution when attempting to enlarge the page. Therefore, the image quality of the enlarged page does not deteriorate.

  In the electronic conference system 1, if the presenter performs any operation for changing the display state of the page, such as reduction, vertical scrolling, horizontal scrolling, etc., not limited to the enlargement of the page, the page of the page is also displayed on the participant's client terminal. The display state is similarly changed in synchronization.

(Independent mode)
In the electronic conference system 1, the client terminals 6 and 8 of the participants can operate in the independent mode. While the client terminals 6 and 8 are operating in the independent mode, even if the display state of the conference material is changed in the client terminal 4 of the presenter, it is not reflected in the client terminals 6 and 8. That is, the display state change synchronization processing is not performed. Instead, the client terminals 6 and 8 can change the display state of the conference material independently of the client terminal 4. Thus, the participant can browse another page of the conference material that the presenter is currently using for the presentation, or browse another conference material.

  The flow of processing in the electronic conference system 1 when the client terminal 6 is operating in the independent mode will be described below.

  A user (participant) of the client terminal 6 first performs an operation on the input unit 60 for operating the client terminal 6 in the independent mode. When the input unit 60 is a touch panel, the participant presses the screen of the client terminal 6. In response, the meeting client 6a changes the operation mode of the client terminal 6 to the independent mode. As a result, the meeting client 6a displays on the display unit 62 a message notifying that the operation mode of the client terminal 6 has been changed to the independent mode.

  The participant performs an operation of changing the display state of the conference material displayed on the display unit 62. For example, the current page is switched to the next page or the current page is enlarged. The meeting client 6a changes the display state of the conference material according to the content of the operation by the participant. At that time, if necessary, Deep Zoom data is requested from the file providing server 18. The file providing server 18 transmits the requested Deep Zoom data to the meeting client 6a. The meeting client 6a does not transmit an instruction signal for instructing to change the display state of the conference material to the meeting controller 16a. That is, the change in the display state of the conference material in the client terminal 6 operating in the independent mode is not reflected at all in the client terminal 4 and the client terminal 8.

  The meeting controller 16a does not know whether the client terminal 6 and the client terminal 8 are operating in the independent mode. Therefore, when an instruction signal instructing to change the display state of the conference material is received from the meeting client 4a, the instruction signal is transmitted to the meeting client 6a even when the client terminal 6 is operating in the independent mode. That is, the meeting client 6a continues to receive the instruction signal while the client terminal 6 operates in the independent mode.

  However, when the meeting client 6a is operating in the independent mode, even if it receives an instruction signal from the meeting controller 16a, the meeting client 6a does not immediately execute the process for changing the display state of the conference material based on the instruction signal. Instead, the received instruction signal is held inside the meeting client 4a. Thereby, when the client terminal 6 is operating in the independent mode, the display state of the conference material displayed on the display unit 62 is changed to the display state on the conference material displayed on the display unit 42 of the client terminal 4. It can be prevented from being changed synchronously.

  When the participant wants to cancel the independent mode, the participant performs an operation for canceling the independent mode on the input unit 60 of the client terminal 6. For example, the “independent mode” button in the conference window displayed on the display unit 62 is pressed. In response, the meeting client 6a cancels the independent mode. At this time, the meeting client 6a changes the display state of the conference material based on the most recently received instruction signal held in itself. For example, when this instruction signal is a signal for instructing page switching of the conference material, the page of the conference material is switched. As a result, as soon as the independent mode of the client terminal 6 is canceled, the same page as the conference material page displayed on the display unit 42 of the client terminal 4 is displayed on the display unit 62 of the client terminal 6. That is, the synchronous display of the conference material is resumed.

(Write to meeting materials)
In the electronic conference system 1, the presenter can write in the conference material during the conference. In this embodiment, writing to the conference material may be expressed as annotation. The writing of the conference material by the presenter is displayed synchronously on the client terminals of all participants other than the presenters participating in the conference.

  The flow of processing in the electronic conference system 1 when the presenter writes in the conference material during the conference will be described below. Note that both the user of the client terminal 6 and the user of the client terminal 8 participate as participants in this conference. The input unit 40 is a touch panel.

  When the presenter writes an annotation on the conference material page, the presenter first presses the “toolbar” button in the user interface of the conference window. As a result, the meeting client 4a displays a toolbar as shown in FIG. FIG. 15 is a diagram illustrating a state where the toolbar is overwritten and displayed on the conference window. The toolbar includes a pen icon, an eraser icon, a cancel icon, a cut icon, and a dynamic window icon in order from the top. When the presenter selects the pen icon, the meeting client 4a displays three icons for selecting the line thickness and color as shown in FIG. FIG. 16 is a diagram illustrating a state in which an icon for selecting a line thickness and a color is overwritten and displayed on the conference window. The user selects any one of these icons. Then, handwriting input is performed on the screen of the client terminal 4 using a pen or a finger. The input unit 40 receives this input.

(Annotation display on client terminal 4)
The input unit 40 informs the meeting client 4a of the coordinate information of the location handwritten by the user. Based on the received coordinate information, the meeting client 4a handles one continuous line generated by a series of continuous handwritten input from when the user touches the screen until it is released as one annotation. Then, annotation data representing the annotation is created. In the present embodiment, the annotation data has vector information. The vector information includes, for example, information on the start point, end point, thickness, and color of the line. The starting and ending values of the line indicate relative coordinates on the page where the annotation is written.

  As shown in FIG. 17, the meeting client 4 a displays the annotation written by the presenter on the conference material on the display unit 42 using the annotation data. FIG. 17 is a diagram showing a conference window that displays conference material in which annotations are written. In the present embodiment, the layer in which the conference material is displayed and the layer in which the annotation is displayed are separated separately, and the latter is arranged on the former. The meeting client 4a displays the annotation written in the conference material by the presenter on a layer above the layer for displaying the conference material. As a result, the annotation is overwritten and displayed on the conference material on the display unit 42. When displaying the annotation, the meeting client 4a does not process any Deep Zoom data on the conference material page. That is, the display of the conference material and the display of the annotation are performed independently using different data.

  The meeting client 4a transmits the created annotation data to the meeting controller 16a. At that time, the corresponding material ID and page ID are associated with the transmission annotation data. The meeting controller 16a holds the received annotation data inside and transmits it to the client terminals of all participants other than the presenters participating in the conference. In this embodiment, the destination is the meeting client 6a and the meeting client 8a.

(Display of annotation on the client terminal 6)
The meeting client 6a displays the annotation represented by the annotation data on the display unit 62 using the received annotation data. At that time, the meeting client 6a uses the resolution (level) of the Deep Zoom data currently used for displaying the conference material and the position of the annotation to be displayed on the layer by using the starting point and ending point information included in the annotation data. Is calculated. Then, the annotation is displayed at the calculated position on the layer. As a result, the display positions of the annotations on the conference material page are the same between the client terminal 4 and the client terminal 6. Even if the resolution of the display unit 42 and the resolution of the display unit 62 are different from each other, there is no substitute for the display position of the annotation. That is, the display of the annotation on the client terminal 4 is reflected on the client terminal 6 synchronously.

  When displaying the presenter's annotation, the meeting client 6a does not process any Deep Zoom data on the conference material page. That is, the display of the conference material and the display of the annotation are performed independently using different data.

(Annotation display on client terminal 8)
The meeting client 8a displays the annotation represented by the annotation data on the display unit 82 using the received annotation data. The details of the processing performed at that time are the same as the processing when the client terminal 6 displays the annotation using the annotation data, and thus detailed description thereof is omitted. Also in the client terminal 4 and the client terminal 8, the display positions of the annotations on the conference material page match each other.

(Add annotation)
When the presenter newly writes an annotation in the conference material, the meeting client 4a creates new annotation data corresponding to the new annotation and stores it in the inside thereof. While continuing to display the same page of the conference material, the meeting client 4a continues to accumulate newly created annotation data. For example, when the presenter performs three separate writings on a page, the meeting client 4a holds three annotation data corresponding to these three writings.

  Each time the meeting client 4a newly creates annotation data, the meeting client 4a transmits only the annotation data to the meeting controller 16a. That is, annotation data accumulated before that time is not transmitted to the meeting controller 16a.

  While the same page of the conference material is continuously displayed, the annotation data newly received from the meeting controller 16a is continuously accumulated. For example, when the presenter performs three writings for a certain page, the meeting client 6a holds three annotation data corresponding to these three writings.

(Eraser function)
The presenter can partially erase the annotation displayed on the display unit 42. At that time, the presenter selects the “eraser” icon in the toolbar. As a result, the meeting client 4a displays the “eraser” sub-icon and the “erase” icon on the display unit 42 as shown in the figure. FIG. 18 is a diagram showing a state where the “eraser” sub-icon and the “erase” icon are overwritten and displayed on the conference window. The presenter presses the “eraser” sub-icon. Thereafter, the user selects a portion to be erased on the screen of the display unit 42. For example, use your fingertip to trace the part of the screen where you want to delete the annotation. The input unit 40 receives this input.

  The input unit 40 informs the meeting client 4a of coordinate information of a location traced by the user with the fingertip. Based on the received coordinate information, the meeting client 4a creates a delete command for instructing deletion of a location selected by the user on the screen. In the present embodiment, the delete command includes position information and range information of the selected location. The meeting client 4a uses the delete command to delete the annotation displayed in the range selected by the presenter from the display unit 42. At that time, the meeting client 4a does not delete any annotation data accumulated so far. That is, the annotation display in the range selected by the presenter is simply deleted from the layer for displaying the annotation. This is a measure for redoing the annotation deletion process later.

  The meeting client 4a accumulates the created delete command in its own association with the corresponding material ID and page ID. The delete command is transmitted to the meeting controller 16a in association with the corresponding material ID and page ID. The meeting controller 16a accumulates the received deletion command in association with the corresponding material ID and page ID. Furthermore, it transmits to the client terminal of all the participants other than the presenter who is participating in the meeting. In this embodiment, the destination is the meeting client 6a and the meeting client 8a.

  Using the received delete command, the meeting client 6a deletes the annotation displayed in the range selected by the presenter from the display unit 62. At that time, the meeting client 6a does not delete any annotation data accumulated so far. That is, the annotation display in the range selected by the presenter is simply deleted from the layer for displaying the annotation. This is a measure for redoing the annotation deletion process later.

  The meeting client 8a deletes the annotation displayed in the range selected by the presenter from the display unit 82 using the received delete command. At that time, the meeting client 8a does not delete any annotation data accumulated so far. That is, the annotation display in the range selected by the presenter is simply deleted from the layer for displaying the annotation. This is a measure for redoing the annotation deletion process later.

(Delete all annotations)
When the presenter selects the “erase” icon in the tool bar, the meeting client 4a creates an instruction command for instructing to erase the display of all annotations displayed on the corresponding page. The meeting client 4a stores the created instruction command. Further, all the annotations currently displayed on the display unit 42 are deleted using the instruction command. At that time, the meeting client 4a does not delete any annotation data accumulated so far. That is, the annotation display is simply deleted from the layer for displaying the annotation. This is a measure for redoing the “erase” process later.

  The meeting client 4a transmits the created instruction command to the meeting controller 16a. At that time, the corresponding material ID and page ID are included in the instruction command. The meeting controller 16a accumulates the received instruction command in itself and transmits it to the client terminal 6 and the client terminal 8.

  The client terminal 6 erases all annotations currently displayed on the display unit 62 using the received instruction command. At that time, the meeting client 6a does not delete any annotation data accumulated so far. That is, the annotation display is simply deleted from the layer for displaying the annotation. This is a measure for redoing the “erase” process later.

  The client terminal 8 erases all annotations currently displayed on the display unit 82 using the received instruction command. At that time, the meeting client 8a does not delete any annotation data accumulated so far. That is, the annotation display is simply deleted from the layer for displaying the annotation. This is a measure for redoing the “erase” process later.

(Redo annotation)
When the presenter selects the “redo icon” in the toolbar, the meeting client 4a creates an instruction command that instructs to redo the annotation display. At that time, the presenter can specify the level of the annotation display to be redone. The meeting client 4a includes information indicating the stage designated by the presenter in the instruction command. The meeting client 4a stores the created instruction command. Further, using the instruction command, a process of redoing the annotation display to the stage designated by the presenter is executed. Note that the above-described annotation deletion (eraser function) and all annotation deletion (erasure function) are also included in the “redo” target.

  The meeting client 4a transmits the created instruction command to the meeting controller 16a. At that time, the corresponding material ID and page ID are included in the instruction command. The meeting controller 16a accumulates the received instruction command in itself and transmits it to the client terminal 6 and the client terminal 8.

  Using the received instruction command, the client terminal 6 executes a process of redoing the annotation display until the stage designated by the presenter. Thereby, the redo of the annotation display on the client terminal 4 is also reproduced on the client terminal 6 in synchronization. The client terminal 6 stores the received instruction command in association with the corresponding material ID and page ID.

  Using the received instruction command, the client terminal 8 executes processing for redoing the annotation display to the stage designated by the presenter. Thereby, the redoing of the annotation display on the client terminal 4 is also reproduced on the client terminal 8 in synchronization. The client terminal 8 stores the received instruction command in association with the corresponding material ID and page ID.

(Save annotation)
When the presenter performs an operation of switching the page of the conference material, the meeting client 4a uses the annotation data for one page currently displayed on the display unit 42 using all the annotation data and instruction commands currently stored. One annotation basic data representing is generated. At that time, individual annotations and instruction commands are calculated in order from the oldest accumulated annotation data.

  The meeting client 4a executes the page switching process and deletes all annotation data and instruction commands stored in itself. The meeting client 4a transmits the created annotation basic data to the meeting controller 16a together with the page switching signal in association with the corresponding material ID and page ID.

  The meeting controller 16a stores the received annotation basic data in the database 22 in association with the corresponding conference ID, material ID, and page ID, and also holds it itself. The meeting controller 16a transmits the received page switching signal to the meeting client 6a and the meeting client 8a. However, the annotation basic data is not transmitted to the meeting client 6a and the meeting client 8a.

  When the meeting client 6a receives the page switching signal, the meeting client 6a executes page switching processing. When the meeting client 8a receives the page switching signal, the meeting client 8a also executes page switching processing.

  Through the above processing, when the presenter performs an operation of switching the page of the conference material, annotation basic data representing the annotation for one page displayed on the current page is stored in the database 22.

(Independent mode)
When the client terminals 6 and 8 are operating in the independent mode, the participants can write annotations independently on the conference material. Annotations that participants write on meeting materials are not shared with presenters and other participants. That is, it is treated as an annotation unique to the participant. In the following, the annotation that the participant wrote in the conference material may be referred to as personal annotation.

  The flow of processing in the electronic conference system 1 when the participant writes personal annotations in the conference material will be described below. Hereinafter, a case where the user of the client terminal 6 writes a personal annotation in the conference material when the client terminal 6 is operating in the independent mode will be described as an example.

  When the participant writes a new personal annotation in the conference material, the meeting client 6a creates new personal annotation data corresponding to the written personal annotation, associates it with the corresponding material ID and page ID, and creates his own personal annotation data. Accumulate inside. In addition, the meeting client 4a displays the personal annotation on the layer for displaying the personal annotation using the created personal annotation data. This layer is separated from the layer for displaying the shared annotation and the layer for displaying the conference material, and is between these layers. That is, in the client terminal 6 operating in the independent mode, the layers have a three-layer structure. First, there is a meeting material layer, on top of which there is a personal annotation layer, on top of which there is a shared annotation layer.

  The meeting client 6a does not transmit the created personal annotation data to the meeting controller 16a. Therefore, this personal annotation data is not provided to the client terminal 4 and the client terminal 8. As a result, the personal annotation written by the user of the client terminal 6 is displayed only on the display unit 62.

  The meeting client 6a continues to receive the annotation data and the instruction command transmitted from the meeting controller 16a while the client terminal 6 operates in the independent mode. In the independent mode, when the page displayed on the client terminal 6 and the page displayed on the client terminal 4 of the presenter are the same, the client terminal 6 displays the participant's annotation and presents the presenter. Display the annotations in sync.

(Page switching by participants)
When the client terminal 6 operates in the independent mode and the participant performs an operation to switch the page of the conference material, the meeting client 6a uses all the personal annotation data and instruction commands currently stored, One piece of personal annotation basic data representing one page of personal annotation displayed on the display unit 62 is created. At that time, the individual annotations and instruction commands are calculated in order from the oldest accumulated personal annotation data.

  The meeting client 6a transmits the created personal annotation basic data to the web server 12 in association with the user ID of the user of the client terminal 6 and the corresponding conference ID, material ID, and page ID. The web server 12 stores the received personal annotation basic data in the database 22 in association with the corresponding user ID, conference ID, material ID, and page ID.

(Release independent mode)
When the participant performs an operation of canceling the independent mode, the meeting client 6a uses the personal annotation data for one page currently displayed on the display unit 62 using all the personal annotation data and instruction commands currently stored. One piece of personal annotation basic data representing the above is created. At that time, the individual annotations and instruction commands are calculated in order from the oldest accumulated personal annotation data.

  The meeting client 6a transmits the created personal annotation basic data to the web server 12 in association with the user ID of the user of the client terminal 6 and the corresponding conference ID, material ID, and page ID. The web server 12 stores the received personal annotation basic data in the database 22 in association with the corresponding user ID, conference ID, material ID, and page ID.

  The client terminal 6 switches the page of the conference material based on the page switching signal received most recently when operating in the independent mode. Furthermore, the shared annotation data and instruction commands stored inside itself when operating in the independent mode are processed in order from the oldest. Thus, the annotation written by the presenter on the conference material while the client terminal 6 is operating in the independent mode is reflected in the conference material displayed on the screen of the client terminal 6.

(Participation during the meeting)
Other participants can join the conference on the way. For example, it is assumed that the user (other participant) of the client terminal 6 ′ participates in the conference on the way. The presenter may have annotated the meeting material before other participants join the meeting. In the electronic conference system 1 of this embodiment, this annotation is also automatically reflected on the client terminal 6 ′. At that time, the meeting controller 16a, when other participants join the conference, the annotation stored in the meeting controller 16a corresponding to the conference material page displayed on the display unit 42 of the client terminal 4. The basic data is transmitted to the meeting client 6a ′ provided in the client terminal of another participant. Further, individual annotation data and instruction commands stored in the meeting controller 16a when other participants join the conference are also transmitted to the meeting client 6a ′. The meeting client 6a ′ is displayed on the screen of the client terminal 4 when other participants join the conference halfway using the annotation basic data, individual annotations, and individual instruction commands received from the meeting controller 16a. The shared annotation for one page is reproduced on the screen of the client terminal 6 ′.

(Adding meeting materials during the meeting)
In the electronic conference system 1, the presenter can add conference materials during the conference. Hereinafter, a case where the user of the client terminal 4 adds conference materials will be described as an example.

  The user of the client terminal 4 presses the “Content & Whiteboard” button in the user interface during the meeting. As a result, the meeting client 4a displays a window for selecting conference material or whiteboard on the display unit 42 as shown in FIG. FIG. 19 is a diagram illustrating a state in which a window for selecting a conference material or a whiteboard is displayed by being overwritten on the conference window. The user of the client terminal 4 can select a whiteboard or conference material used for the presentation through the window shown in FIG.

  The window shown in FIG. 19 includes a “+” button. When the user presses the “+” button, the meeting client 4a displays a material addition window as shown in FIG. FIG. 20 is a diagram illustrating a state in which the document addition window is overwritten and displayed on the conference window.

  As shown in FIG. 20, the material addition window includes an “upload” button. When the user presses the “upload” button, the conference ID and the user ID are transmitted to the meeting controller 16a.

  Based on the received user ID, the meeting controller 16a acquires a list of data stored in the file system 24 in association with the user ID. This data includes conference material uploaded to the cloud system 2 by the user in the past, and information (annotation) written on the conference material or whiteboard in the conference in which the user has participated in the past. The meeting controller 16a transmits the acquired list to the meeting client 4a.

  The meeting client 4a displays the received list on the display unit 42. At that time, a predetermined folder (my content folder) for displaying the list is displayed on the screen of the display unit 42, and a list of data is displayed in the my content folder. The user can select conference materials to be added to the conference from the list in the My Contents folder. Alternatively, data stored in the client terminal 4 in the client terminal 4 can also be selected as the conference material. The meeting client 4a uploads the conference material selected by the user to the web server 12. At that time, the user ID and conference ID of the user of the client terminal 4 are transmitted to the web server 12.

(Creation of Deep Zoom data)
The web server 12 stores the conference material information and the conference information in the file system 24 in association with the conference material received from the meeting client 4a. The meeting material information includes at least a meeting material ID. The conference material ID is information for uniquely identifying the conference material uploaded to the web server 12. The web server 12 generates a conference material ID having a value that does not match the other conference materials stored in the database 22 or the file system 24 for the conference material uploaded from the meeting client 4a.

  The file conversion server 14 monitors the file system 24 and checks whether new data is stored in the file system 24 at regular intervals. When it is detected that new data (conference material) is stored in the file system 24 from the web server 12, the data is converted into deep zoom data. Since the conversion method to Deep Zoom data has already been described, detailed description thereof is omitted here.

(Save Deep Zoom data)
The file conversion server 14 creates Deep Zoom data from all meeting materials newly detected from the file system 24. All the created deep zoom data (tiles of JPEG data) are stored in the file system 24 in association with the conference ID. At that time, each Deep Zoom data is associated with a corresponding material ID and page ID.

  The file providing server 18 stores a copy of the Deep Zoom data stored in the file system 24 in the file providing server 18. The file providing server 18 manages each provided Deep Zoom data in association with the corresponding conference ID, the corresponding material ID, and the corresponding page ID.

  The file providing server 18 creates page information including all page IDs created when each vector data is divided into data for each page, and stores the page information in association with the corresponding conference information in the database 22.

  With the above processing, the addition of meeting materials during the meeting is completed. Thereby, the presenter of the meeting can use the added new meeting material during the meeting. The presenter and the presenter can add conference materials during the conference through the meeting client 4a for conducting the conference. Therefore, it is not necessary to execute another program different from the meeting client 4a in order to add the conference material. Thereby, meeting materials can be added quickly.

(Keyboard memo input)
When the user of the client terminal 4 presses the “My Note” button in the user interface, the meeting client 4a displays a window for inputting a keyboard memo to the conference material. FIG. 21 is a diagram illustrating a state in which a memo input window for inputting a keyboard memo is overwritten and displayed on the conference window. A keyboard memo is text information input using a keyboard.

  The user of the client terminal 4 who is the presenter inputs a keyboard memo on each page of the conference material during the conference through the memo input window of FIG. This keyboard memo is handled as information included in the minutes, and is distributed to each participant in the form included in the minutes after the meeting.

  The user of the client terminal 6 and the user of the client terminal 8 can also input a keyboard memo. These memos are stored in the input client terminal, but are not transmitted to other client terminals. That is, in the electronic conference system 1 of this embodiment, the keyboard memo input by the user at each client terminal 4 is never shared with other client terminals.

(Dynamic window display)
The meeting client 4a can display a part of the conference material independently in another window different from the conference window. Hereinafter, this other window is referred to as a dynamic window.

  At the bottom of the annotation toolbar, there is an icon for displaying a dynamic window. In order to display the dynamic window, the user of the client terminal 4 presses this icon. As a result, the meeting client 4a asks the user to select an area to be displayed in the dynamic window.

  The user of the client terminal 4 selects an area to be displayed in the dynamic window from the displayed conference material page. For example, using the mouse, a part of the conference material page is selected in a rectangular shape. At that time, the meeting client 4a creates coordinate information and range information of the location selected by the user. Next, based on these pieces of information, a dynamic window including a selected part in the conference material is displayed on the display unit 42. As a result, as shown in FIG. 22, the dynamic window including the location selected by the user is overwritten and displayed on the conference window. FIG. 22 is a diagram illustrating a state in which a dynamic window including a portion selected by the user is overwritten and displayed on the conference window.

  The meeting client 4a transmits an instruction signal including the above-described coordinate information and range information and instructing to display a dynamic window to the meeting controller 16a. The meeting controller 16a transmits the received instruction signal to the client terminals of all participants other than the presenters participating in the conference. In this embodiment, the destination is the meeting client 6a and the meeting client 8a.

  The meeting client 6a acquires coordinate information and range information from the received instruction signal. Next, based on these pieces of information, a dynamic window including a selected part in the conference material is displayed on the display unit 62. As a result, the dynamic window including the part selected by the user of the client terminal 4 is overwritten and displayed on the conference window displayed on the display unit 62. At this time, the client terminal 4 and the client terminal 6 have the same display position and display range of the dynamic window in the conference window. That is, the dynamic window display on the client terminal 4 is reproduced on the client terminal 6 synchronously.

  The meeting client 8a acquires coordinate information and range information from the received instruction signal. Next, based on these pieces of information, the matrix number of the tile of Deep Zoom data corresponding to the selected location is calculated. Then, a page request signal for requesting the deep zoom data at the selected location is transmitted to the file providing server 18.

  The file providing server 18 specifies deep zoom data to be provided to the meeting client 8a based on the received page request signal. Then, the requested deep zoom data tile is transmitted to the meeting client 8a.

  The meeting client 8a displays a dynamic window including tiles of the received deep zoom data on the display unit 62. As a result, the dynamic window including the portion selected by the user of the client terminal 4 is overwritten and displayed on the conference window displayed on the display unit 82. At this time, the display position and display range of the dynamic window in the conference window are the same between the client terminal 4 and the client terminal 8. In other words, the dynamic window display on the client terminal 4 is reproduced on the client terminal 8 synchronously.

  In the electronic conference system 1, the dynamic window can be fixed to a specific page. The dynamic window includes a “pin” icon. When the user presses this “pin” icon, the dynamic window is fixed to the currently displayed page.

  When the dynamic window is fixed to the page, when the page is switched to another page, the display of the dynamic window disappears accordingly. That is, the dynamic window is not displayed on the page after switching. On the other hand, when the dynamic window is not fixed to the page, the display of the dynamic window is continued even if the page is switched to another page. That is, the dynamic window continues to be displayed at the same position on the conference window only by switching the conference material page. Thereby, in the electronic conference system 1, it is possible to create a dynamic window including a part of a page with the conference material and display the dynamic window on another page.

  The present invention is not limited to the embodiments described above. Those skilled in the art can make various modifications to the present invention within the scope of the claims. That is, a new embodiment can be obtained by combining appropriately changed technical means within the scope of the claims.

  The present invention can be widely used as various electronic conference systems for conducting an electronic conference.

DESCRIPTION OF SYMBOLS 1 Electronic conference system 2 Cloud system 4 Client terminal 4a Meeting client 6 Client terminal 6a Meeting client 8 Client terminal 8a Meeting client 10 Communication line 12 Web server 14 File conversion server 18 File providing server 16 Meeting server 16a Meeting controller (conference control part)
20 video conference server 42 display unit 40 input unit

Claims (6)

An electronic conferencing system for conducting an electronic conference, comprising a file providing server and a plurality of terminals equipped with a display unit,
The file providing server
Representing the conference material used for the electronic conference, among the plurality of data having different resolutions, the data requested from each of the plurality of terminals is provided to each of the plurality of terminals,
Each of the plurality of terminals
Among the plurality of data having different resolutions, the display unit is requested to request data corresponding to the resolution from the file providing server,
An electronic conference system, wherein the conference material is displayed on the display unit using the data provided from the file providing server. Each of the plurality of terminals
When the user performs an operation for enlarging the page of the conference material displayed on the display unit, a predetermined determination value obtained by multiplying the enlargement ratio of the page of the conference material by the resolution of the display unit Seeking
If the determination value is larger than the resolution of the data currently used for displaying the conference material page, the file providing server is requested for data having a resolution one level higher than the data,
2. The electronic conference system according to claim 1, wherein the conference material after the enlargement is displayed on the display unit by using the data of the resolution one level higher provided from the file providing server. . Each of the plurality of data includes at least one fixed-size partial data,
Each of the above terminals
Of the at least one partial data constituting the data, request the file providing server for at least one partial data corresponding to a location displayed on the display unit in the conference material page,
3. The electronic conference system according to claim 1, wherein the conference material page is displayed on the display unit using the at least one partial data provided from the file providing server.   The electronic conference system according to any one of claims 1 to 3, wherein the plurality of data are deep zoom data. A terminal that constitutes an electronic conference system for conducting an electronic conference together with a file providing server,
With a display,
Requesting the file providing server for data corresponding to the resolution of the display unit from among a plurality of data having different resolutions representing the conference material used for the electronic conference,
A terminal characterized in that the conference material is displayed on the display unit using the data provided from the file providing server. A file providing server constituting an electronic conference system for conducting an electronic conference together with a plurality of terminals having a display unit,
Among the plurality of data having different resolutions representing the conference material used for the electronic conference, the data corresponding to the resolution requested by each of the plurality of terminals is sent to each of the plurality of terminals. A file providing server characterized by providing.

Images