JP7301193B2 - Terminal device and program - Google Patents

Description

The present invention relates to a management server connectable to a plurality of service servers that provide communication services, and a terminal device connectable to a file server that stores files used in the communication services.

In recent years, the use of conference systems has become widespread. By using a conference system, for example, materials used in a conference can be stored in a file server in advance, and when the conference is held, the materials can be displayed on a large display. In addition, techniques have been proposed to further facilitate information sharing and understanding of meetings according to the form of the meeting.

For example, a remote conferencing system that enables collaboration between conferencing systems by interconnecting conferencing systems installed at multiple sites with a shared workspace server for connection and information sharing between conferencing systems. is proposed. A workspace server enables information sharing by managing reference information to files and resources (for example, Patent Document 1).

Also, a conference management apparatus has been proposed that can obtain past conference information with a simple operation. The meeting information includes file information related to meeting materials distributed in past meetings, and when a file is specified, its contents are displayed. Therefore, it is easy to grasp the entire conference, and omissions can be prevented (for example, Patent Document 2).

In addition, file management using online storage (cloud storage) is spreading. Also, when reserving a conference by a conference reservation service, it is possible to attach a file to be used in the conference. At this time, the attached file may be stored in the online storage. In this way, a plurality of services are used to efficiently share conference information.

JP 2004-171526 A JP 2016-197285 A

However, when a plurality of services for reserving conferences are used, the devices and locations where files are stored differ for each service. In addition, when reusing a file that was used in a previous meeting, it was necessary to attach the file again when reserving the meeting. As described above, there is a problem that it takes time and effort to obtain a file desired to be used in a meeting or to download it from an online storage.

SUMMARY OF THE INVENTION In view of the problems described above, it is an object of the present invention to provide a terminal device or the like capable of providing necessary information even if a conference is reserved from a plurality of services.

In order to solve the above-described problems, the terminal device of the present invention includes:
A terminal device connectable to a management server connectable to a plurality of service servers providing communication services and a file server storing files used in the communication services,
a meeting information receiving means for receiving meeting information, which is information about a meeting reserved on the communication service, from the management server;
file acquisition destination identification means for identifying a storage destination of a file used in the communication service from the conference information as a file acquisition destination;
a file acquisition means for acquiring the file from the specified file acquisition destination;
characterized by comprising

The conference management system of the present invention is
A conference management system including a management server connectable to a plurality of service servers providing communication services, a file server storing files used in the communication services, and terminal devices,
The management server is
Acquisition means for acquiring information about a conference reserved on the communication service;
conference information transmission means for transmitting conference information including information specifying a communication service of the reserved conference to the terminal device, in information about the reserved conference;
with
The terminal device
a meeting information receiving means for receiving meeting information, which is information about a meeting reserved on the communication service, from the management server;
file acquisition destination identification means for identifying a storage destination of a file used in the communication service from the conference information as a file acquisition destination;
a file acquisition means for acquiring the file from the specified file acquisition destination;
characterized by comprising

The program of the present invention is
A computer connectable to a management server connectable to a plurality of service servers providing communication services and a file server storing files used in the communication services,
a conference information reception function for receiving conference information, which is information about a conference reserved on the communication service, from the management server;
A file acquisition destination specifying function for specifying a storage location of a file used in the communication service from the meeting information as a file acquisition destination;
a file acquisition function for acquiring the file from the specified file acquisition destination;
It is characterized by realizing

The conference management method of the present invention includes:
A conference management method in a conference management system including a management server connectable to a plurality of service servers providing communication services, a file server storing files used in the communication services, and a terminal device,
The management server is
a obtaining step of obtaining information about a meeting booked on the communication service;
a conference information transmission step of transmitting, to the terminal device, conference information including information specifying a communication service of the reserved conference in the information about the reserved conference;
including
The terminal device
a meeting information receiving step of receiving meeting information, which is information about a meeting reserved on the communication service, from the management server;
a file acquisition destination specifying step of specifying, as a file acquisition destination, a storage location of a file used in the communication service from the meeting information;
a file acquisition step of acquiring the file from the specified file acquisition destination;
characterized by comprising

According to the present invention, the file acquisition destination is specified based on the conference information reserved on the service, and the file is acquired from the file acquisition destination. Therefore, conference participants can acquire files without being aware of which service the conference was reserved for.

It is a figure for demonstrating the whole block diagram in 1st Embodiment. FIG. 2 is a diagram for explaining an outline of a conference reservation service according to the first embodiment; FIG. 4 is a diagram for explaining the functional configuration of a conference information management server according to the first embodiment; FIG. It is the figure which showed an example of the data structure of the meeting information in 1st Embodiment. It is the figure which showed an example of the data structure of the participant information in 1st Embodiment. It is the figure which showed an example of the data structure of the service allocation information in 1st Embodiment. 4 is a diagram for explaining the functional configuration of a conference room client according to the first embodiment; FIG. 4 is a diagram showing an example of the data structure of file acquisition destination information in the first embodiment; FIG. 4 is a diagram showing an example of the data configuration of acquisition file information in the first embodiment; FIG. FIG. 4 is a diagram for explaining a sequence in the first embodiment; FIG. FIG. 4 is a diagram for explaining processing of a conference room client in the first embodiment; FIG. 5 is a diagram for explaining initial screen display processing in the first embodiment; FIG. It is a figure for demonstrating the conference screen display process in 1st Embodiment. FIG. 4 is a diagram for explaining screen transition in the first embodiment; FIG. It is a figure for explaining an example of operation in a 1st embodiment. It is a figure for explaining an example of operation in a 1st embodiment. It is a figure for explaining an example of operation in a 1st embodiment. It is a figure for demonstrating the initial screen display process in 2nd Embodiment. FIG. 12 is a diagram for explaining the functional configuration of a conference room client according to the third embodiment; FIG. FIG. 13 is a diagram showing an example of the data structure of file usage history information in the third embodiment; FIG. 13 is a diagram showing an example of the data structure of file storage destination information in the third embodiment; It is a figure for demonstrating the sequence in 3rd Embodiment. It is a figure for demonstrating the conference screen display process in 3rd Embodiment. It is a figure for explaining an example of operation in a 4th embodiment. It is a figure for explaining an example of operation in a 5th embodiment.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described with reference to the drawings. In this embodiment, as an example, a conference management system including a conference room client to which the present invention is applied will be described. The term "meeting" in the present embodiment means that predetermined participants gather at a predetermined place at a predetermined time to share information and discuss topics, including meetings, discussions, classes, etc. .

[1. First Embodiment]
[1.1 Overall configuration]
The overall configuration of the conference management system 1 of this embodiment will be described with reference to FIG. As shown in FIG. 1, the conference management system 1 includes a conference information management server 10, a conference room client 20 that is a terminal device, cloud storages 30 (30a and 30b) that are file servers, and services that provide communication services. A server 40 is included and is communicable via a network NW.

The network NW may be an internal network such as LAN or an external network such as the Internet. Also, each device may be connected to the network NW regardless of whether it is wired or wireless.

The conference information management server 10 is a management server that acquires information about conference reservations from a service server 40 that has a function of making conference reservations, and manages the information as conference information. The conference room client 20 is a device that receives conference information from the conference information management server 10 and displays files used in the conference based on the conference information.

Here, the cloud storage is one of file servers, and is an online storage (storage area) provided using the cloud. A user can store files (contents) in a file server provided by a service provider as needed. Also, each user may be assigned a unique storage area (for example, a storage device, a directory, or an area that can be set with a predetermined capacity). Each user can refer to the files stored in the shared area among the areas.

Also, although FIG. 1 can connect to cloud storages 30a and 30b and two services, only one cloud storage service may be provided, or more than one may be provided.

In this embodiment, a cloud storage is used as an example of a file storage location, but a single file management server or NAS (Network Attached Storage) may be used as a file server.

[1.2 Service description of this embodiment]
Here, basic services used in this embodiment will be described with reference to FIG. FIG. 2 shows screen examples of two communication services with different features. Here, referring to FIG. 2, a method of reserving a conference on the service will be described.

Here, the communication service is a comprehensive service that provides users with various means of communication. For example, it includes a service in which messages of one-to-one or multiple participants are displayed on a timeline, and various services such as e-mail, bulletin board, and conference reservation. In this embodiment, the following service A and service B will be described.

The communication service may be provided as a conference management system, or may use an external service. Also, in this embodiment, the communication service is simply referred to as a service.

Communication service A (hereinafter referred to as service A) in FIG. 2A is a service for making conference reservations. For example, there is a screen for reserving a conference, and it is possible to input the name of the conference, the location, the date and time of the conference, participants, attached files, and the like. Also, when a meeting is reserved, the attached file is stored in the file server, which is the storage location associated with the service A. FIG. The file server may be the service server itself or a shared folder of another computer. For example, in service A described with reference to FIG. Alternatively, a conference may be reserved by e-mail, for example, without providing a screen for reserving a conference.

Communication service B (hereinafter referred to as service B) in FIG. 2B is a conference service that allows conversation such as chat. Service B provides a timeline function that displays conversational messages in chronological order, and users of service B can post messages and texts. Furthermore, files can be uploaded to the timeline, and users using the conference service can refer to the uploaded files.

Files uploaded to these timelines are stored in a storage destination associated with service B (for example, cloud storage 30).

In service B, it is possible to reserve a meeting on the timeline. For example, service B may be able to input a message for setting the date and time, meeting place, etc. within a conversation, or may be able to invoke and execute a reservation function.

Also, the user of service B can attach a file when reserving a conference. Here, the file uploaded on the timeline is uploaded to the conference information management server 10 because it is a file used in the conference. Note that the attached file may also be stored in the location associated with service B (storage area of cloud storage 30).

Depending on the type of service and reservation method, the location (device) for storing the file transmitted from the user (uploaded file) may differ. Therefore, when a conference participant starts a conference service, it has been necessary to confirm the service for which the conference has been reserved, and obtain the file according to the service.

In this embodiment, the conference information management server 10 acquires information (hereinafter referred to as “reservation information”) regarding conference reservations from one or a plurality of communication services. In addition, the file can be obtained from the file storage destination associated with the communication service. As a result, the file can be acquired at the start of the conference without being aware of the service reserved for the conference.

It should be noted that although the file storage location is assigned according to the service, a plurality of locations may be assigned within the service. For example, in service B, files may be stored in the cloud storage 30a when a plurality of people are having a conversation, and in the cloud storage 30b when a one-to-one conversation is being held.

[1.3 Functional configuration]
[1.3.1 Conference information management server]
The conference information management server 10 will be explained with reference to FIG. The conference information management server 10 includes a control section 100 , a communication section 110 , a storage section 120 and a conference information acquisition section 130 .

The control unit 100 is a functional unit for controlling the conference information management server 10 as a whole. The control unit 100 implements various functions by reading and executing various programs, and is configured by, for example, a CPU (Central Processing Unit).

The communication unit 110 is a functional unit that allows the conference information management server 10 to connect to the network NW and communicate with other devices (clients, cloud storage, etc.). For example, it is implemented by a NIC (Network Interface Card) used in a wired/wireless LAN, or a communication module connectable to a 3G/LTE line.

The storage unit 120 is a functional unit that stores various programs and various data necessary for the operation of the conference information management server 10 . The storage unit 120 is configured by, for example, a semiconductor memory such as an SSD (Solid State Drive) or an HDD (Hard Disk Drive).

The storage unit 120 stores conference information 122, participant information 124, and service allocation information 126, and furthermore, an attached file storage area 128 is secured for storing files attached to the conference information. there is

As the conference information 122, when a conference is reserved from another service acquired by the conference information acquisition unit 130, which will be described later, reservation information that is information relating to the reservation of the conference is stored. For example, as shown in FIG. 4, a service ID (for example, "service A") for identifying a service when a conference is reserved and a reserved conference name (for example, "2019 model information sharing") , the start date and time of the meeting (eg, "2017/11/14 15:00"), the end date and time of the meeting (eg, "2017/11/14 16:00"), and the participants of the meeting (eg, " User1, User3, User4, User6") and additional information that is added information about the conference is stored.

This conference information 122 is reservation information when a conference is reserved from a service used by a user of the conference management system 1 created when the conference information acquisition unit 130 reserves a conference in each service. Collected and generated. That is, it is generated by extracting the conference name, start date and time, end date and time, and participant information from the reservation information, and storing the service ID of the reservation service and, if necessary, additional information.

Here, the additional information is, for example, a team name when a team to hold a meeting is designated, or a timeline topic (channel name) when a meeting is reserved from the timeline. The additional information may store all of the reservation information other than the meeting name, start date and time, end date and time, and participants. You can do it.

Also, if a file is attached to the acquired reservation information, the attached file is stored in the attached file storage area 128, which will be described later.

In the present embodiment, the participant ID of the participant information 124, which will be described later, is stored as the participant. good too. For example, participants' names and employee numbers may be stored.

Furthermore, in addition to the information described above, the conference information 122 may store attributes related to the conference, such as the organizer of the conference, the place where the conference is held, and the department.

The participant information 124 stores information necessary for authentication and notification of conference participants and attributes of the participants. For example, as shown in FIG. 5, a participant ID (for example, "User1") for identifying a participant and a password (for example, , “aaa12345”), an e-mail address used for notification of information (for example, “user1@example.com”), and attributes that are information about the participant are stored. As attributes, for example, attributes such as name (eg, "Sato") and title (eg, "section manager") are stored. In addition to the attributes described above, attributes such as department and employee number may be stored.

Information other than the password may be used as the information for authenticating the participant. For example, when biometric authentication is used for participant authentication, a fingerprint pattern or face pattern may be stored according to the biometric authentication method.

The service allocation information 126 is information that stores information about file storage areas in association with service types and the like. Details will be described later.

The attached file storage area 128 is an area for storing files attached to reservation information. If the reservation information includes an attached file, for example, a folder is created for each service and each meeting name, and the attached file is stored in the folder.

In addition, information that associates the meeting information stored in the meeting information 122 with the attached file stored in the attached file storage area 128 is stored in the service allocation information 126 . For example, as shown in FIG. 6, the service allocation information 126 includes a service ID for specifying a service (for example, "service A"), a conference name for specifying a meeting (for example, "AAA meeting"), The storage location of the file attached to the reservation information of the conference (for example, "/files/service A/AAA meeting") is stored.

The conference information acquisition unit 130 is a functional unit that connects to a service server capable of making conference reservations, acquires reservation information that is information related to conference reservations, and stores the reservation information in the conference information 122 . Information on the service server to be connected (for example, connection destination, authentication information for logging in to the service server, etc.) may be stored in the storage unit 120, or may be managed by the conference management system 1 when reservation information is acquired. may be specified by a person or the like.

After obtaining the reservation information, the name of the conference, the start date and time of the conference, the end date and time of the conference, the participants of the conference, and additional information are extracted and stored in the conference information 122 together with the service ID of the acquired service.

Acquisition of the reservation information may be performed periodically, or may be performed by the operation of the administrator of the conference management system 1 or the like.

In addition to collecting reservation information by the method described above, when the service server transmits conference information to the conference information management server 10, the transmitted reservation information is received and stored in the conference information 122. good too. For example, when a meeting is reserved for a service server, if the reservation information is sent to the meeting information management server 10 by e-mail, the meeting information 122 is based on the content of the e-mail received by the meeting information management server 10. Store meeting information.

[1.3.2 Meeting room client]
Next, the functional configuration of the conference room client 20 will be explained with reference to FIG. In this embodiment, a display device capable of touch operation is used as the conference room client 20, but the conference room client 20 may be configured by a display control device and a display device. The conference room client 20 of this embodiment includes a control section 200 , a display section 210 , an operation detection section 220 , an image processing section 230 , a communication section 240 and a storage section 250 .

The control unit 200 is a functional unit for controlling the conference room client 20 as a whole. The control unit 200 implements various functions by reading and executing various programs, and is configured by, for example, a CPU.

The display unit 210 is a functional unit that displays files such as meeting materials. For example, it is configured by an LCD (Liquid Crystal Display), an organic EL display (OELD: Organic Electroluminescence Display), or the like.

The operation detection unit 220 is a functional unit that detects touch positions and touch operations performed on the conference room client 20 . For example, by overlapping the operation detection unit 220 on the display unit 210, a touch panel is configured. As a touch system, any system such as a capacitive system, a resistive film system, and an infrared system may be used.

The image processing unit 230 is a functional unit that performs various types of image processing on image data. For example, sharpening processing of image data is performed.

The communication unit 240 is a functional unit for the conference room client 20 to communicate with external devices. For example, it is implemented by a NIC used in a wired/wireless LAN or a communication module connectable to a 3G/LTE line.

The storage unit 250 is a functional unit that stores various programs and various data necessary for the operation of the conference room client 20 . The storage unit 250 is configured by, for example, a semiconductor memory such as an SSD, an HDD, or the like.

The storage unit 250 particularly stores meeting information 252 and file acquisition destination information 254, and further secures a file storage area 256 for storing files received from the meeting information management server 10 and the cloud storage 30. ing. Acquired file information 258 is stored as information about the files stored in the file storage area 256, and an extension application related list 260 is stored.

As the conference information 252, among the conference information stored in the conference information 122, the conference information related to the conference to be handled by the conference room client 20 is stored.

The file acquisition destination information 254 stores information necessary for determining the acquisition destination of the files to be used in the conference based on the conference information 252 . For example, as shown in FIG. 8, a service ID (for example, "service A") for specifying a service, a priority (for example, "1"), and a file type stored in a file acquisition destination are shown. A file type (for example, "attached file") and a file acquisition destination (for example, "meeting information management server/[ service ID]/[meeting name]”) are stored.

The file type is information used to specify the file acquisition destination. In this embodiment, the following information is stored.
・Attached file: When a file is attached to the reservation information ・Past meeting file: When showing a file used in a meeting held in the past ・Shared file: When a file is shared by the user・Files of logged-in participants: In the case of shared files of participants who are logged in to the conference management system 1 ・Shared files of participants: In the case of shared files of participants of the conference being held by the conference management system 1 ・Channel files: When showing files uploaded to the timeline in service B

The file acquisition destination indicates the location (folder or the like) from which the conference room client 20 actually acquires the file. The file acquisition destination may be the storage location of the file associated with the communication service, or the location where the shared file of the participants is stored. Here, the part surrounded by "[ ]" indicates the place where the information according to the situation such as the attribute corresponding to the meeting information, the additional information, and the date is inserted.

For example, if the file acquisition destination is "meeting information management server/[service ID]/[meeting name]", assume that the service ID of the meeting information 252 is "service A" and the meeting name is "AAA meeting". In this case, the conference room client 20 acquires the file from "conference information management server/service A/AAA meeting". That is, the files are stored in a folder (directory) called "service A/AAA meeting" in the conference information management server 10 .

Also, the conference room client 20 may be able to specify the file acquisition destination according to the participants. For example, if a shared folder used by a participant participating in a conference is to be the file acquisition destination, specify "Cloud3/[Users]/[participant ID]". If there are four participants in the conference, the conference room client 20 acquires the files from the shared folders of the four participants. Also, a shared folder of a logged-in participant or a shared folder of a participant having a specific attribute (for example, a participant whose job title is section manager) may be specified as a file acquisition destination.

Although the file acquisition destination is set for each reservation service, the file acquisition destination may be set for any service. For example, if it is desired to acquire "files of logged-in participants" in any conference, the file acquisition destination with the service ID set to "all" may be included.

The priority indicates the order in which files to be obtained are presented to conference participants. For example, if the service ID of the meeting information 252 is "service A", the attached file is preferentially presented to the participants. By setting the priority, it is possible to present to the participants the files having the highest relevance to the conference among the files related to the conference.

The file acquisition destination information 254 may be preset in the conference room client 20, or the conference information management server 10 stores the file acquisition destination information, and the conference room client 20 receives the file acquisition destination information from the conference information management server 10. The file acquisition destination information may be stored.

Files acquired based on the file acquisition destination information 254 are stored in the file storage area 256 . Also, information about files to be acquired is stored in the acquired file information 258 .

For example, as shown in FIG. 9, the acquired file information 258 includes a file type corresponding to the acquired file (eg, "attached file"), a file name of the file (eg, "meetings.pptx"), A thumbnail file name (for example, “meetings.pptx.png”), which is the file name of the thumbnail corresponding to the file, is stored.

In this embodiment, the conference room client 20 receives the thumbnail data from the file delivery destination and stores it as a thumbnail file in the file storage area. Further, the file name of the thumbnail is made to correspond to the file by adding a specific character string to the end of the corresponding file name. Note that this configuration does not have to be used, and any configuration may be used as long as files and thumbnails are associated with each other.

In addition, in this embodiment, before acquiring the file (actual file) stored in the file acquisition destination, thumbnail display of the file is performed instead of the actual file. In the present embodiment, an area called a recommendation area is displayed on the display unit 210, and thumbnails and file names are arranged vertically in close proximity based on the obtained file information 258 in the recommendation area. In addition to thumbnail display, for example, a list of file names may be displayed, or file icons, image captures, and the like may be displayed as substitutes for thumbnail display.

Further, in this embodiment, a list for selecting a file type (file type selection list) is displayed in the recommendation area. It is assumed that the recommended area displays thumbnails of files acquired from file acquisition sources corresponding to the file types selected in the file type selection list.

The extension application related list 260 stores file extensions (for example, “.pptx”) and applications (for example, presentation applications) to be started when using files that include the extension in the file name. . When using the acquired file, if the extension of the file is stored in the extension application related list 260, the file is displayed by the corresponding application.

It should be noted that an application to be started when using a file can be specified as long as the application can be specified, and the application name, the path of the application name, and the like are stored.

[1.4 Flow of processing]
[1.4.1 Overall processing]
Processing in this embodiment will be described. First, with reference to FIG. 10, data transmitted and received between each device will be described.

First, the conference room client 20 transmits authentication information to the conference information management server 10 (S1002). The authentication information is sent for the conference information management server 10 to perform the process of authenticating the participants. The authentication information includes a participant ID and password.

Here, as a method for a conference participant to input authentication information, there is a method of using a card reader connected to the conference room client 20 to read a card in which the participant ID and password are stored, or a method of or a method of entering a password. When biometric authentication is used to authenticate a participant, a device such as a fingerprint sensor or a camera may be used to read physical characteristics according to the biometric authentication method, and the physical characteristics may be read and transmitted as authentication information.

The conference information management server 10 performs authentication processing based on the authentication information transmitted from the conference room client 20 and the authentication information (for example, participant ID and password) stored in the participant information 124 (S1004). For example, if the authentication information sent from the conference room client 20 matches the authentication information stored in the participant information 124, the conference information management server 10 sets the authentication result as "successful authentication". If the authentication information sent from the conference room client 20 and the authentication information stored in the participant information 124 do not match, or if the authentication information is not registered, the authentication result will be "authentication failure". . Also, the conference information management server 10 transmits the authentication result described above to the conference room client 20 (S1006).

The conference room client 20 that has received the authentication result transmits a conference information request to the conference information management server 10 if the authentication result is "successful authentication" (S1008). The conference information management server 10 extracts, from the conference information 122, conference information in which the participant ID corresponding to the conference information request is included in the participants (S1010). The conference information management server 10 then transmits the extracted conference information to the conference room client 20 (S1012).

The conference room client 20 that has received the conference information selects one conference information from the received conference information (S1014). Also, the conference room client 20 stores the selected conference information as the conference information 252 .

Next, based on the meeting information 252 and the file acquisition destination information 254, the control unit 200 transmits file requests to the file acquisition destinations in descending order of priority.

For example, if the conference information management server 10 is the device having the file acquisition destination with the highest priority, the control unit 200 sends a file request requesting the conference information management server 10 to transmit the file stored in the file acquisition destination. is transmitted (S1016). The conference information management server 10 that has received the file request transmits the file name and thumbnail data stored in the area specified as the file acquisition destination to the conference room client 20 (S1018). Then, the controller 200 of the conference room client 20 receives the file name and thumbnail from the conference information management server 10 .

Subsequently, if there is a file acquisition destination with the next highest priority, a file request is transmitted in the same manner as in S1016 (S1020). In FIG. 10, a file request is sent to the cloud storage 30. FIG. The device that received the file request transmits the file name and thumbnail data to the conference room client 20 (S1022), as in S1018.

As described above, the control unit 200 of the conference room client 20 transmits a file request based on the file acquisition destination. Also, information (for example, file name and/or thumbnail) regarding the acquired file is displayed in the recommendation area for each file (S1024). Also, the file data may be received at the same time as the thumbnail data, or may be received separately (S1026).

When the participant performs an operation for displaying a file such as selecting a thumbnail, the controller 200 of the conference room client 20 performs processing for displaying the selected file (S1028). If acquisition of the file data to be displayed is not completed when the file is selected, the file data may be acquired after the file is selected.

[1.4.2 Processing of conference room client]
Next, the flow of processing of the conference room client 20 will be described with reference to FIG. First, the control unit 200 authenticates the participants (step S102). If the participant is successfully authenticated, the conference information corresponding to the participant ID is acquired from the conference information management server 10 (step S104).

Subsequently, the control unit 200 stores one meeting information among the acquired meeting information as the meeting information 252 (step S106). This determination of one conference information to be stored as the conference information 252 may be determined by having the participants select from the conference information, or may be determined by the conference room client 20 .

As a method for the conference room client 20 to determine one piece of conference information, if there is conference information in which the current time is included in the time zone of the conference, the conference information is related to the conference currently being held. , a method of determining one piece of conference information is conceivable. Considering that the participants are authenticated before the conference starts, the conference information whose current time is within a predetermined time (for example, within 30 minutes) from the start date and time of the conference information is determined as one conference information. You may

If no conference information can be acquired from the conference information management server, the participants may be notified that there is no selectable conference information.

Subsequently, the control unit 200 performs processing for displaying the conference details screen on the display unit 210 (step S108). Here, the conference details screen is a screen that displays information such as the name of the conference, the start date and time, the end date and time, and the file to be acquired based on the conference information 252 . Also, the participants of the conference select whether or not to start the conference after confirming the conference details screen.

When the conference participant selects to start the conference, the control unit 200 performs processing (initial screen display processing) for displaying an initial screen to be displayed on the display unit 210 at the start of the conference (step S110; Yes → step S112). Here, the initial screen display processing will be described with reference to FIG.

First, from the service ID of the conference information 252, the control unit 200 reads out the file acquisition destination where the file related to the conference is stored from the file acquisition destination information 254, and selects the file acquisition destination (step S152).

Subsequently, the control unit 200 transmits file requests to the devices corresponding to the file acquisition destinations in order of priority among the selected file acquisition destinations (step S154).

Subsequently, the control unit 200 receives the file name and thumbnail transmitted as a response to the file request from the file acquisition destination device (step S156). Also, the received service ID, file name, and thumbnail file name are stored in the acquired file information 258 .

Subsequently, based on the information stored in the acquired file information 258, the control unit 200 displays the file name and thumbnail acquired from the file acquisition destination with the highest priority in the recommendation area for each file corresponding to the thumbnail ( step S158). Also, the file is acquired from the file acquisition destination and stored in the file storage area 256 (step S160).

In the flow shown in FIG. 12, the process of displaying the file name and thumbnail and the process of acquiring the file are performed in parallel. Some or all of the processing may be performed in parallel. For example, if there are multiple file acquisition destinations, a series of processes of sending a file request to each file acquisition destination, acquiring the file name and thumbnail, and acquiring the file can be executed in parallel. good.

By the above-described processing, files that can be used during the conference can be displayed in the recommendation area based on the priority of the file acquisition source information 254 .

Subsequently, returning to FIG. 11, the conference screen display processing is performed. The conference screen display process is a process of displaying a screen during the conference on the display unit 210 while the conference is being held. The conference screen display process will be described with reference to FIG.

First, the control unit 200 determines whether or not the participant has performed an operation to display the file acquired from the file acquisition destination (step S172). Here, the operation of displaying a file is specifically an operation of tapping a thumbnail displayed in the recommendation area or clicking a thumbnail with a mouse.

Subsequently, when an operation to display a file is performed, the control unit 200 displays the file on the display unit 210 according to the operation performed by the participant (step S172; Yes→step S174). Specifically, the control unit 200 identifies the corresponding file name from the obtained file information 258 based on the file type displayed in the recommendation area and the thumbnail file name of the selected thumbnail. Further, control unit 200 extracts the file corresponding to the file name from file storage area 256 and displays it on display unit 210 .

Next, whether or not the participant performed an operation to change the file type displayed in the recommendation area, that is, whether or not the participant performed an operation to change the file type selected in the file type selection list to another file type. The control unit 200 determines whether or not (step S176).

If it is determined that the participant has performed an operation to change the file type displayed in the recommendation area, the control unit 200 displays the thumbnail corresponding to the selected file type among the thumbnails received in step S154 in the recommendation area. (step S178).

Subsequently, the control unit 200 determines whether or not it is time to end the conference (step S180). The case of ending the conference is, for example, when the participant selects to end the conference, or when the current time has passed the end date and time of the conference information. When ending the conference, the control unit 200 deletes the file acquired from the file acquisition source from the file storage area 256 and ends the conference screen display process (step S180; Yes→step S182). Also, the meeting information 252 and the acquired file information 258 are deleted (step S184). If end of conference is not selected (step S180; No), the process returns to step S172.

Returning to FIG. 11, the control unit 200 determines whether or not the participant has performed a logout operation (step S116). If it is determined that a logout operation has been performed, the process returns to participant authentication (step S114; Yes→step S102). If it is not determined that the logout operation has been performed, the process returns to the meeting information acquisition process (step S116; No→step S104).

[1.5 Operation example]
[1.5.1 Screen transition example]
An operation example of this embodiment will be described with reference to the drawings. First, screen transition of screens displayed on the display unit 210 of the conference room client 20 will be described with reference to FIG. First, a screen prompting for participant authentication is displayed (FIG. 14(a)). The screen may display an authentication method or display a text box for entering authentication information. Also, when authentication is unnecessary, a start button or the like may be displayed.

Subsequently, when the authentication result sent from the conference information management server 10 indicates successful authentication, the conference room client 20 manages the authenticated participant as a logged-in state, and stores the conference information in which the participant participates as the conference information. Acquired from the management server 10 . If no authentication is required, this step is skipped and the process proceeds to the step of acquiring conference information.

When the conference information acquired from the conference information management server 10 includes conference information whose current time is included in the time zone of the conference, the control unit 200 stores the conference information as the conference information 252, and stores the conference information as the conference information 252. 252 is displayed on the display unit 210 (FIG. 14(c)).

If there is no conference information corresponding to the time zone of the conference, the control unit 200 displays the conference information acquired from the conference information management server 10 in a list on the display unit 210, and makes it possible for the participants to select the conference information. (FIG. 14(b)). When the conference information is selected by the participant, the control unit 200 stores the selected conference information as the conference information 252 and displays the conference details screen based on the conference information 252 on the display unit 210 (FIG. 14 ( c)).

Subsequently, when the participant selects to start the conference on the conference details screen, the control unit 200 displays a conference screen on the display unit 210 (FIG. 14(d)). Also, if the conference has not started, a screen for selecting conference information is displayed.

If the participant selects to end the conference while the screen for the conference is being displayed, the control unit 200 displays a screen for confirming the end of the conference on the display unit 210, and instructs the participant how to end the conference. is selected (FIG. 14(e)). In the present embodiment, it is assumed that canceling, starting another meeting, and logging out can be selected as the ending method.

If the participant selects logout, a screen prompting the participant to authenticate is displayed (FIG. 14(a)). If the participant selects to start another conference, a screen for selecting conference information is displayed so that the participant can select a new conference (FIG. 14(b)). If the participant selects cancellation, the conference screen is displayed (FIG. 14(d)).

[1.5.2 Operation screen example]
Next, screens displayed in this embodiment will be described with reference to the drawings. First, the conference screen will be described with reference to FIG. FIG. 15(a) is an example of a display screen W1000 in this embodiment. W1000 displays a conference application and a recommendation area R1000 so as to overlap the conference application. The recommendation area R1000 includes an area R1002 displaying thumbnails and file names for each file, a file type selection list B1000, and a button B1002 for ending the conference. It also includes an update button B1004 for updating the display of the region R1002 and a button B1006 for shrinking the recommended area.

A thumbnail and a file name are displayed for each file in the area R1002. For example, an area R1004 displays the file name "Chart.pptx" and the thumbnail of the file. A conference participant can select a desired file to use based on the display in area R1002.

FIG. 15B is an example of the display screen W1100 when the region R1004 is selected on the display screen W1000. At this time, the file corresponding to "Chart.pptx" among the files stored in the file storage area 256 is displayed (W1102).

Next, the file type selection list will be explained with reference to FIG. FIGS. 16A and 16B are display examples when a conference participant operates the file type selection list B1000 of FIG. 15 to expand the list. Here, the service IDs stored in the meeting information 252 are different between FIGS. 16(a) and 16(b). The types of files that can be acquired are different depending on the service ID, and in particular the items indicated by M2000 and M2002 are different.

Next, an example of a screen for displaying files of past conferences will be described with reference to FIG. First, the participant selects the item "files of past meetings" (M3000) from the file type selection list (FIG. 17(a)). At this time, the control unit 200 displays a date display L3000 and buttons B3000 and B3002 for selecting the date in the file type selection list on the display unit 210 (FIG. 17(b)).

Note that the date display L3000 may display the most recent date among the dates that can be specified as the file acquisition destination of the files of the past conference, or the date of the day when the conference is being held. good.

Also, when the participant selects button B3000 or B3002, control unit 200 changes the date displayed in L3000 (FIG. 17(b)). For example, when the button B3000 is selected, a date earlier than the currently selected date is displayed, and when the button B3002 is selected, a later date than the currently selected date is displayed. If the date displayed in L3000 cannot be changed to a future or past date, buttons B3000 or B3002 may be displayed so that they cannot be selected by the participants.

When a past conference file is selected or when the date is changed by the participant's operation, control unit 200 changes the thumbnail displayed in the recommendation area based on the date displayed in L3000. For example, in FIG. 17B, the date displayed in L3000 is "2018/04/27", so the file of the meeting held on April 20, 2018 is displayed in the recommendation area. Here, it is assumed that B3000 is selected by the participant, resulting in the state shown in FIG. 17(c). At this time, in FIG. 17C, the date displayed in L3000 is "2018/04/20", so the file of the meeting held on April 20, 2018 is displayed in the recommendation area.

Here, whether or not to display the date selection list in B2000 in the file type selection list may be determined by whether or not [date] is included in the file acquisition location of the file acquisition location information 254 . That is, when the date can be included in the file acquisition destination corresponding to the file type, the date is displayed so that the participant can select the date to be included in the file acquisition destination.

The date that can be specified may be obtained at the start of the conference, or may be inquired of the file acquisition source of the material of the past conference each time the button B3000 or B3002 for selecting the date is operated.

In particular, when past conferences have been held many times, it takes time to acquire all thumbnails of the materials of the past conferences. Therefore, it is possible to reduce the time required to acquire thumbnails by setting the behavior to acquire thumbnails when a date is selected.

Instead of acquiring thumbnails each time a date is selected, thumbnails of meeting materials up to a predetermined number of times before may be acquired at the start of the meeting. In this case, it is possible to shorten the processing time required to refer to the materials about the recent meeting.

According to this embodiment, it is possible to acquire files based on the meeting information 252 and the file acquisition destination information 254 regardless of the service that has reserved the meeting. Therefore, the participants can use the file without being aware of the service that made the reservation for the conference, and an improvement in convenience can be expected.

Also, by setting the priority of the file acquisition destination for each service, even if there are multiple types of files, at the start of the conference, files highly relevant to the conference will be displayed in the recommendation area.

Furthermore, by obtaining the file in the background while the participant is checking the thumbnails displayed in the recommendation area, it is possible to reduce the waiting time until the file is obtained.

In this embodiment, the file request is sent to all the file acquisition destinations in the order of priority of the file acquisition destinations. You may send. In this case, when the file type is changed, if a file acquisition destination that has not yet been acquired is selected, a file request is made to the file acquisition destination and the recommendation area is updated. In this way, since a file request is requested only when necessary, it is possible to prevent files that the conference room client 20 does not want to use from being received in the background.

Further, in the present embodiment, the file acquisition destination is determined based on the conference information 252 and the file acquisition destination information 254, but the conference information acquired from the conference information management server 10 does not include the file acquisition destination. may be Since the file acquisition destination is included in the meeting information, it is possible to omit the process of selecting the file acquisition destination by the control unit 200 in step S152.

Further, in this embodiment, the service ID is used to specify the service, but if the service can be determined using information other than the service ID, it is possible not to store the service ID. For example, if a channel name is set as additional information, it may be determined as service B. In this case, the service is determined based on the information that allows the service to be determined. Also, the file acquisition destination may be determined based on information by which the service can be identified or additional information. For example, when a channel name is included in the additional information of the conference information 252, file acquisition destination information may be stored such that a file is acquired from a predetermined file acquisition destination.

Also, the conference information may include information about the venue of the conference. Here, since the conference room client 20 includes location information, it is possible to detect in advance a conference to be held using the conference room client 20 . Therefore, by acquiring the file from the file acquisition destination before the start of the conference, it is possible to reduce the waiting time for acquiring the file.

At this time, based on the extension application related list 260, the file obtained in advance may be put in a usable state. By doing so, the file to be used is already displayed at the start of the conference, and the operation of selecting a thumbnail can be omitted.

In this embodiment, the conference information management server 10 acquires reservation information and manages it as conference information, but the conference room client 20 may acquire reservation information and manage it as conference information. In this case, the information of the service server to which the conference room client 20 connects (for example, connection destination, authentication information for logging in to the service server, etc.) is stored in the storage unit 250 of the conference room client 20 . The acquisition of reservation information may be performed periodically by the conference room client 20, or may be performed after the participants are authenticated.

[2. Second Embodiment]
Next, a second embodiment will be described. In this embodiment, a thumbnail obtained from a file obtaining source where a file exists is displayed as a thumbnail displayed in the recommendation area at the start of a conference. Since the overall configuration and functional configuration are the same as those of the first embodiment, the description thereof will be omitted.

In this embodiment, the flow of initial screen display processing of the conference room client 20 in the first embodiment shown in FIG. 12 is replaced with the flow shown in FIG. Initial screen display processing in this embodiment will be described with reference to FIG.

First, the control unit 200 selects, from the service ID of the conference information 252, the file acquisition destination with the highest priority among the file acquisition destinations storing files related to the conference from the file acquisition destination information 254 (step S252).

Subsequently, for the file acquisition destination selected in step S252, the control unit 200 transmits a file request to the device corresponding to the file acquisition destination (step S254). Also, the control unit 200 receives the file name and thumbnail transmitted as a response to the file request from the file acquisition destination device (step S256).

Subsequently, the control unit 200 determines whether or not the file exists at the file acquisition destination (step S258). For example, if one or more thumbnails or file names can be acquired from the file acquisition source, it may be determined that the file exists.

If the control unit 200 determines that the file does not exist at the file acquisition destination, it selects the file acquisition destination with the next highest priority among the file acquisition destinations stored in the file acquisition destination information 254 (step S258). ; No→step S260). Further, the control unit 200 transmits a file request to the selected file acquisition destination (step S254).

If it is determined in step S258 that the file exists at the file acquisition destination (step S258; Yes), the control unit 200 displays the file name and thumbnail acquired from the file acquisition destination in the recommendation area (step S262). Furthermore, the file of the file acquisition destination is acquired in the background and stored in the file storage area 256 (step S264).

With the above-described processing, the thumbnails displayed in the recommendation area at the start of the conference can be set according to the status of the file acquisition destination. For example, referring to the file acquisition destination information 254 shown in FIG. 8, if the service when the conference is reserved is service A, the conference room client 20 first sends the file to the file acquisition destination where the attached file is stored. Submit your request.

If a file is attached when a conference is reserved, the thumbnail of the attached file is displayed in the recommendation area. If the file is not attached when the conference is reserved, the file request is transmitted to the file acquisition destination having the next highest priority and the file acquisition destination where the files of the past conference are stored. If files of past conferences are stored, thumbnails of the files of the past conferences are displayed in the recommendation area.

In the embodiment of the present application, thumbnails are acquired from file acquisition sources based on priority and displayed in the recommendation area. Files can be displayed.

[3. Third Embodiment]
Next, a third embodiment will be described. In this embodiment, when a file acquired from a file acquisition destination is updated, the updated file is stored in a predetermined storage destination.

In this embodiment, since the functional configuration of the conference room client differs from that of the first embodiment, the conference management system 2 of this embodiment includes a conference information management server 10, a conference room client 22, and a cloud storage 30. are connected. 7 to 18 from the first embodiment, the sequence shown in FIG. 10 is replaced with the sequence diagram of FIG. 20, and the conference screen display of FIG. The flow of processing is replaced with the flow of FIG. Note that the same reference numerals are assigned to the same functional units and processes as in the first embodiment, and the description thereof is omitted.

[3.1 Functional Configuration of Meeting Room Client]
A functional configuration of the conference room client 22 will be described with reference to FIG. The storage unit 250 of the conference room client 22 stores conference information 252, file acquisition destination information 254, a file storage area 256, acquired file information 258, an extension application related list 260, file usage history information 262, File storage location information 264 is included.

In the file usage history information 262, when a file stored in the file storage area 256 is used, the used file and the state of the file are stored in association with each other. For example, as shown in FIG. 19, the file name of the file stored in the file storage area 256 (eg, "meetings.pptx") and the status of the file (eg, "updated") are stored.

Here, the file is used when the file stored in the file storage area 256 is displayed by the participant, or when the file is updated by an operation such as writing to the file. Say the case. If the file is displayed, the state is stored as "open", and if the file is updated, the state is stored as "updated".

The file save destination information 264 stores the save destination of the updated file for each service. For example, as shown in FIG. 20, a service ID for identifying a service (for example, "service A") and a storage destination of an updated file (for example, "files of past meetings") are stored. .

The file storage destination may store the file type stored in the file acquisition destination information, or may store information indicating the location of the storage destination such as a path. Once the file type is stored, the same location as the file destination for that file type in that service is used as the file save destination.

Note that, in this embodiment, the part enclosed in "[ ]" included in the save destination is the corresponding attribute of the conference information, additional information, participant attribute, similar to the file acquisition destination of the file acquisition destination information 254. Indicates where to insert contextual information such as , date.

[3.2 Flow of processing]
[3.2.1 Overall flow]
Next, processing in this embodiment will be described. First, with reference to FIG. 22, data transmitted and received between each device will be described. Note that the file acquisition processing shown in FIG. 22 refers to the processing from S1002 to S1026 in FIG.

Subsequently, when the participant performs an operation to select a thumbnail, the control section 200 of the conference room client 20 displays the file corresponding to the selected thumbnail on the display section 210 . Further, when the participant edits the displayed file, the control unit 200 updates the edited file stored in the file storage area 256 (S2002).

Also, when the file is displayed, the control unit 200 stores the file name and the file usage history information whose status is “open” in the file usage history information 262 . Also, when the file is updated, the control unit 200 stores the file name and the file usage history information whose status is “updated” in the file usage history information 262 . (S2004).

Subsequently, the control unit 200 determines whether or not the conference has ended (S2006). When the conference ends, based on the file usage history information 262, the file data of the updated file and the data of the participants of the conference are sent to the file storage destination (for example, cloud storage) corresponding to the service (S2008). In addition, the device of the file storage destination allows the file transmitted to the conference participant to be browsed by granting the conference participant the authority to browse the file received from the conference room client 22 (S2010).

In addition, the conference room client 22 transmits the information of the saved file, such as the name of the saved file and the link address from which the sent file can be obtained, and the data of the participants of the conference to the conference information management server 10 ( S2012). The conference information management server 10, which has received the information of the saved file and the data of the participants of the conference, extracts the email addresses of the participants from the participant information 124 based on the data of the participants, and sends to the email addresses, Send information about submitted files.

S2008-S2014 allow the conference participants to share the updated file. It should be noted that when the file transmission is completed, the file stored in the conference room client 20 is deleted (S2016).

[3.2.2 Flow of conference screen display processing]
Next, the conference screen display processing in this embodiment will be described with reference to FIG. First, when the participant performs an operation to display a file (step S172), the control unit 200 displays the file on the display unit 210 (step S174), and sets the file name and status of the file to "open". ” is stored in the file use history information 262 (step S202). As for the file name, the file name corresponding to the thumbnail selected as the file display operation is obtained from the acquired file information 258 .

Subsequently, the control unit 200 determines whether or not the participant has performed an operation to update the file (step S204). An operation for updating a file may be, for example, an operation for a participant to write in a displayed file by a touch operation, or an operation for editing the contents.

When it is determined that an operation to update the file has been performed, the updated file is stored in the file storage area 256 (step S204; Yes→step S206). Also, for the file, the file name and the file usage history information whose status is "updated" are stored in the file usage history information 262 (step S208).

Subsequently, the control unit 200 determines whether or not the conference has ended (step S180). When the control unit 200 determines that the conference has ended (step S180; Yes), the control unit 200 transmits the file updated in the conference to the file storage destination corresponding to the service of the conference information 252. FIG. First, from the service ID stored in the meeting information 252, the control unit 200 determines the storage destination corresponding to the service based on the file storage destination information 264 (step S210). Also, the control unit 200 extracts the updated file based on the file usage history information 262, and transmits the updated file to the storage destination determined in step S210 (step S212).

After the transmission of the updated file is completed, the control unit 200 subsequently transmits the information of the transmitted file and the information of the participants to the conference information management server 10 (step S214). After the transmission is completed, the control unit 200 deletes the file acquired from the file acquisition destination (step S182). Also, the meeting information 252 and the acquired file information 258 are deleted (step S184). Furthermore, the file usage history information 262 is deleted (step S216).

According to this embodiment, it is possible to transmit the updated file at the end of the conference to the storage destination according to the reservation service. Therefore, the participants of the conference do not have to select the storage destination of the updated file by themselves at the end of the conference, which can be expected to improve convenience.

When the same conference is held at multiple bases, it is possible to avoid conflicts by adding the log-in participant ID to the end of the save destination so that conflicts do not occur in the files to be stored. Whether or not the same conference is held at a plurality of bases may be given as an attribute to the conference information, or may be determined based on whether or not the save destination already exists.

Also, when a file is displayed, the displayed file and the application used when displaying the file may be stored. By doing so, when using a specific file, it is possible to display and edit it with a specific application. For example, when a file whose main purpose is viewing and a file whose main purpose is editing, it is possible to specify the application to be used for each file.

[4. Fourth Embodiment]
4th Embodiment is embodiment which can select the application which starts at the time of a meeting start in a meeting details screen. For example, it is conceivable to start a voice conversation application or a web conference system at the start of a conference in order to hold a conference smoothly between multiple sites.

For example, as shown in FIG. 24A, a button for designating an application to be started at the start of the conference is displayed in the area surrounded by B4000 on the conference details screen. Participants can select the application they wish to launch. Also, by highlighting the selected button, the participants can check the application that will be started when the conference starts.

When the participant selects the conference start button, as shown in FIG. View applications.

Note that the conference room client 20 may store the selectable applications and the correspondence between the services and the applications to be activated at the start of the conference. In particular, if the application to be started at the start of each meeting is decided, the improvement of convenience can be expected.

[5. Fifth Embodiment]
The fifth embodiment is an embodiment in which, on a screen displaying a list of conference information, each piece of conference information is displayed by distinguishing from which reservation service the conference was reserved.

For example, as shown in FIG. 25, an icon capable of distinguishing the reservation service is displayed next to the conference name in the conference information, as surrounded by R5000. Note that the background color of the panel and the character color of the conference name may be displayed in a color corresponding to the service so that the distinction can be made.

This embodiment is suitable when it is necessary to be conscious of the reservation service. For example, when there are conditions such as file acquisition destinations, file storage destinations, and applications used in the conference are limited, it is possible to estimate the behavior of the conference management system 1 before the conference starts.

[6. Sixth Embodiment]
5th Embodiment is embodiment which can extend a meeting. For example, a conference extension button is displayed in the recommendation area. When the participant selects the conference extension button, the control unit 200 delays the end date and time of the conference information by a predetermined time (for example, 15 minutes). Also, when the conference is extended, the control unit 200 corrects the end time of the conference information corresponding to the conference information 252 . Further, the control unit 200 transmits a request to delay the end time of the conference information corresponding to the conference information 252 to the conference information management server 10 .

This embodiment can delay the execution of the processing when the processing is performed based on the end date and time, such as when the end of the conference is determined based on the end date and time of the conference information. Also, when referring to the conference information after the conference ends, it is possible to know the date and time of the actual conference ending.

When extending the conference, the conference information management server 10 may be inquired as to whether or not the conference can be extended. For example, if the end date and time of a conference is delayed and the end date and time of the conference overlap with the start time of another conference held at the same place, it is determined that the conference cannot be extended. When the conference room client 20 receives this determination, it may notify the participants that the conference cannot be extended.

[7. Modification]
Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and designs and the like within the scope of the scope of the claims can be applied without departing from the gist of the present invention. include.

Moreover, it goes without saying that the above-described embodiments can be executed in combination with each other. For example, by executing the third embodiment and the fourth embodiment in combination, it becomes possible to specify an application to be started at the start of a conference and to transmit an updated file.

In addition, the program that operates in each device in the embodiment is a program that controls the CPU and the like (a program that causes the computer to function) so as to implement the functions of the above-described embodiments. The information handled by these devices is temporarily stored in a temporary storage device (for example, RAM) during processing, and then stored in a storage device such as an HDD or SSD (solid state drive). It is read, modified, and written by the CPU.

When distributed to the market, the program can be stored in a portable recording medium for distribution, or transferred to a server computer connected via a network such as the Internet. In this case, of course, the storage device of the server computer is also included in the present invention.

10 conference information management server 100 control unit 110 communication unit 120 storage unit 122 conference information 124 participant information 126 service allocation information 128 attached file storage information 130 conference information acquisition unit 20 conference room client 200 control unit 210 display unit 220 operation detection unit 230 Image processing unit 240 Communication unit 250 Storage unit 252 Meeting information 254 File acquisition destination information 256 File storage area 258 Obtained file information 260 Extension application related list 30 Cloud storage

Claims (7)

a meeting information acquisition unit that acquires meeting information of one or more meetings reserved by the communication service based on the login information;
a display control unit for displaying a list of conference information;
with
The display control unit is a terminal device that displays, for each piece of conference information, an image showing the communication service for which a conference corresponding to the conference information is reserved. When one of the conference information displayed in the list is selected by the user, or when the conference information includes conference information including the current time, the display control unit controls the display for the corresponding conference. 2. The terminal device according to claim 1, which displays a screen. a file acquisition destination identification unit that identifies, as a file acquisition destination, a storage location of a file attached at the time of reservation of the conference or a file posted in the communication service from the conference information of the corresponding conference;
a file information acquisition unit that acquires the file name of the file specified from the file acquisition source and the thumbnail image corresponding to the file from the file acquisition source;
further comprising
3. The terminal device according to claim 1, wherein the display control unit displays a list of acquired file names and thumbnail images. when the conference ends, sending the file data of the updated file and the data of the participants of the conference to the file acquisition destination;
4. The terminal device according to claim 3, further comprising a transmission unit that transmits the information of the transmitted file and the data of the participants of the conference to the conference information management server. a file acquisition unit that acquires a file attached when reserving a meeting selected from the acquired meeting information or a file posted in a communication service;
When the conference ends, the file data of the updated file and the data of the participants of the conference are transmitted to the acquisition destination of the file, and the information of the transmitted file and the data of the participants of the conference are sent to the conference information management server. a transmitter for transmitting;
The terminal device according to claim 1 or 2, further comprising: 6. The terminal device according to any one of claims 1 to 5, wherein the display control unit displays an image showing a reserved communication service, a conference name, a start date and time, and participant information for each piece of conference information. to the computer,
a meeting information acquisition step of acquiring meeting information of one or more meetings reserved by the communication service based on the login information;
a display control step for displaying a list of conference information;
A program that executes
The display control step displays, for each piece of conference information, an image showing the communication service for which a conference corresponding to the conference information is reserved.

Images