Conference support system, conference support method, and conference support program

Abstract

To provide a conference support system, a conference support method, and a conference support program capable of easily starting conferences.SOLUTION: A conference support system includes: an acquisition processing unit that, by letting a user terminal communicate with a communication medium installed in a conference room, acquires medium information corresponding to the communication medium; and a permission processing unit that, based on user information for identifying a user acquired from the user terminal and the medium information, identifies a conference in which the user is supposed to participate, and permits login to a conference support application of the identified conference.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present invention relates to a meeting support system, a meeting support method, and a meeting support program.

Background Art

[0002] In recent years, a meeting system (online meeting) has been introduced that transmits and receives audio, video, files, etc. via a network at locations separated from each other. Conventionally, technologies have been proposed such as a technology for making a meeting room available by collating user information read from an IC card with reservation information of the meeting room (see, for example, Patent Document 1), and a technology for acquiring user information read from an IC card and the entry / exit times of a meeting room and managing them as meeting results (see, for example, Patent Document 2).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0004] Here, when starting a meeting, the user has to perform operations such as starting a meeting support application for conducting an online meeting on a meeting room terminal (PC) installed in the meeting room, and inputting login information (for example, user ID, password) on the meeting support application screen. Therefore, there is a problem that it takes time to start a meeting.

[0005] An object of the present invention is to provide a meeting support system, a meeting support method, and a meeting support program that can easily start a meeting.

Means for Solving the Problems

[0006] A conference support system according to one aspect of the present invention includes user terminals of users participating in a conference in a conference room, and is a conference support system that executes a conference support application for the conference. An acquisition processing unit that acquires media information corresponding to the communication medium by communicating with the communication medium installed in the conference room; and a permission processing unit that identifies a conference in which the user participates based on user information for identifying the user and the media information, and permits login to the conference support application of the identified conference.

[0007] A conference support method according to another aspect of the present invention includes user terminals of users participating in a conference in a conference room, and is a conference support method that executes a conference support application for the conference. One or more processors perform an acquisition step of acquiring media information corresponding to the communication medium by communicating with the communication medium installed in the conference room; and a permission step of identifying a conference in which the user participates based on user information for identifying the user and the media information, and permitting login to the conference support application of the identified conference.

[0008] A conference support program according to another aspect of the present invention includes user terminals of users participating in a conference in a conference room, and is a conference support program that executes a conference support application for the conference. A program for causing one or more processors to execute an acquisition step of acquiring media information corresponding to the communication medium by communicating with the communication medium installed in the conference room; and a permission step of identifying a conference in which the user participates based on user information for identifying the user and the media information, and permitting login to the conference support application of the identified conference.

Advantages of the Invention

[0009] According to the present invention, it is possible to provide a conference support system, a conference support method, and a conference support program that can easily start a conference.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Embodiments for Carrying Out the Invention

[0011] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. Note that the following embodiments are an example of embodying the present invention and do not have the character of limiting the technical scope of the present invention.

[0012] The conference support system according to the present invention can be applied to, for example, an online conference in which a plurality of users participate at different locations (conference rooms). The conference system according to the present embodiment is an example of the conference support system of the present invention. For example, in the conference system according to the present embodiment, in a conference room, there are arranged a user terminal used by a user participating in the conference, a conference room terminal installed with a conference support application, a display for displaying a conference screen such as materials used in the conference, and a communication medium (for example, a communication tag) capable of communicating with the user terminal. Further, the conference system includes a management server for managing information such as conferences, conference rooms, and devices used in the conference.

[0013] [Conference System 100] FIG. 1 is a diagram showing a schematic configuration of a conference system 100 according to an embodiment of the present invention. The conference system 100 includes a management server 1, user terminals 2, conference room terminals 3, displays 4, and communication tags Tg. FIG. 1 shows conference room 1 and conference room 2. Here, an example is shown in which users U1, U2, U3, U4 participate in a conference in conference room 1, users U5, U6, U7, U8 participate in a conference in conference room 2, and an online conference is held by connecting conference room 1 and conference room 2. In conference room 1, a user terminal 2 owned by user U1, a conference room terminal 3, a display 4, and a communication tag Tg1 are arranged. In conference room 2, a user terminal 2 owned by user U5, a conference room terminal 3, a display 4, and a communication tag Tg2 are arranged. The conference system 100 can hold an online conference in conference room 1 and conference room 2 by executing a conference support application installed on the conference room terminal 3 in conference room 1 and a conference support application installed on the conference room terminal 3 in conference room 2. Note that the conference system 100 has a microphone, a speaker, and a camera connected to each conference room terminal 3, and is configured to enable two-way communication of audio and camera video.

[0014] The management server 1 is constructed by, for example, one or more server devices (for example, virtual servers). The user terminal 2 may be the user's own terminal device (for example, a smartphone) that the user participating in the conference brings into the conference room. Here, for example, the representative user U1 who participates in the conference in conference room 1 brings in the user terminal 2, and the representative user U5 who participates in the conference in conference room 2 brings in the user terminal 2. Note that in each conference room, each user may own a user terminal 2.

[0015] The management server 1, the user terminal 2, and the conference room terminal 3 are connected to each other via the network N1. The network N1 is a communication network such as the Internet, a LAN, a WAN, or a public telephone line. Also, the conference room terminal 3 and the display 4 are connected by a wired LAN or a wireless LAN. Further, the user terminal 2 and the communication tag Tg can be connected by short-range wireless communication. The communication tag Tg is installed in the conference room. For example, the communication tag Tg1 for conference room 1 is attached to the housing (outer frame) of the display 4 in conference room 1, and the communication tag Tg2 for conference room 2 is attached to the housing (outer frame) of the display 4 in conference room 2. Note that the communication medium of the present invention is not limited to the communication tag Tg, and may be a one-dimensional code, a two-dimensional code, or the like. For example, an image of a two-dimensional code for conference room 1 may be displayed on the display 4 in conference room 1, and an image of a two-dimensional code for conference room 2 may be displayed on the display 4 in conference room 2. Also, the medium information of the present invention may be the tag ID of the communication tag Tg, or may be the two-dimensional code image of the two-dimensional code.

[0016] [Management Server 1] As shown in FIG. 2, the management server 1 includes a control unit 11, a storage unit 12, an operation display unit 13, a communication unit 14, and the like. The management server 1 may be one or more virtual servers (cloud servers), or may be one or more physical servers.

[0017] The communication unit 14 is a communication unit that connects the management server 1 to the network N1 by wire or wirelessly, and performs data communication according to a predetermined communication protocol with other devices (for example, the user terminal 2, the conference room terminal 3) via the network N1.

[0018] The operation display unit 13 is a user interface including a display unit such as a liquid crystal display or an organic EL display that displays various information, and an operation unit such as a mouse, a keyboard, or a touch panel that accepts operations. The operation display unit 13 accepts, for example, operations by the administrator of the management server 1.

[0019] The storage unit 12 is a non-volatile storage unit such as an HDD (Hard Disk Drive), an SSD (Solid State Drive), or a flash memory that stores various types of information. The storage unit 12 stores control programs such as a conference support program for causing the control unit 11 to execute the conference support process (see FIG. 13) described later. For example, the conference support program is non-temporarily recorded on a computer-readable recording medium such as a CD or a DVD, and is read by a reading device (not shown) such as a CD drive or a DVD drive provided in the management server 1 and stored in the storage unit 12. Note that the conference support program may be distributed from a cloud server and stored in the storage unit 12.

[0020] In addition, the storage unit 12 stores a management table including various types of information for supporting conferences. Specifically, the storage unit 12 stores data such as a meeting reservation information management table T1 that manages meeting information related to meeting reservations, a meeting room information management table T2 that manages meeting room information related to meeting rooms, a device information management table T3 that manages device information related to devices installed in the meeting room, and a user information management table T4 that manages user information related to users.

[0021] FIG. 3 is a diagram showing an example of a meeting reservation information management table T1. In the meeting reservation information management table T1, for each meeting, meeting information in which information such as the holding date, holding time, meeting room ID, meeting name, reserving person ID, meeting URL, attendees, and attached materials are associated with each other is registered. The meeting room ID is identification information of a meeting room which is a place where the meeting is held (an example of the meeting room identification information of the present invention). The reserving person ID is identification information for identifying a user who reserved the meeting (an example of the user information of the present invention). The meeting URL is access information (connection information) for connecting when starting the meeting. For example, the meeting support application accesses the meeting URL to start an online meeting application (such as a general-purpose meeting application) corresponding to the meeting URL and connect to a connection destination ID (meeting ID). The attached materials are materials used in the meeting. For example, when the holding of the meeting is determined, the reserving person performs a reservation operation of inputting meeting information including the above-mentioned respective information on his / her own PC (such as user terminal 2). The control unit 11 registers the meeting information in the meeting reservation information management table T1 in response to the user's reservation operation. Note that the function of managing the meeting reservation information including the meeting information may not be included in the management server 1. For example, when an external server different from the management server 1 provides a service for managing the meeting reservation information (such as a calendar service), the management server 1 may access the external server, refer to the meeting reservation information, and acquire the meeting information corresponding to the meeting room ID and the reserving person ID.

[0022] FIG. 4 is a diagram showing an example of a conference room information management table T2. In the conference room information management table T2, for each conference room, conference room information in which information such as a tag ID, a conference room ID, a conference room name, a conference room terminal ID, and a device ID are associated with each other is registered. The tag ID is identification information of a communication tag Tg installed in the conference room (an example of the media information and media identification information of the present invention). The conference room terminal ID is identification information of the conference room terminal 3 installed in the conference room. The device ID is identification information of devices (display 4, screen sharing device, printer, lighting, air purifier, air conditioner, etc.) installed in the conference room. In the conference room information management table T2, conference room information for each conference room is registered in advance by a registration operation by an administrator or the like.

[0023] In the example shown in FIG. 4, the tag ID "N001" is identification information of the communication tag Tg1 installed in conference room 1, and the tag ID "N002" is identification information of the communication tag Tg2 installed in conference room 2. Also, the conference room terminal ID "PC0001" is identification information of the conference room terminal 3 installed in conference room 1, and the conference room terminal ID "PC0002" is identification information of the conference room terminal 3 installed in conference room 2. Also, the device ID "D0011" is identification information of the display 4 installed in conference room 1, and the device ID "D0021" is identification information of the display 4 installed in conference room 2.

[0024] FIG. 5 is a diagram showing an example of a device information management table T3. In the device information management table T3, for each device installed in the conference room, device information in which information such as a device ID, a device name, and an IP address are associated with each other is registered. In the device information management table T3, device information for each device is registered in advance by a registration operation by an administrator or the like.

[0025] FIG. 6 is a diagram showing an example of the user information management table T4. In the user information management table T4, user information in which information such as user ID, user name, and authentication information is associated with each other for each user is registered. The user ID and authentication information (such as a password) are used as login information when logging in to the meeting support application (see FIG. 9). In the user information management table T4, user information for each user is registered in advance by the user's registration operation.

[0026] Note that part or all of the meeting reservation information management table T1, the meeting room information management table T2, the device information management table T3, and the user information management table T4 may be stored in a server accessible from the management server 1.

[0027] The control unit 11 includes control devices such as a CPU, a ROM, and a RAM. The CPU is a processor that executes various arithmetic processes. The ROM stores in advance control programs such as BIOS and OS for causing the CPU to execute various processes. The RAM stores various information and is used as a temporary storage memory (working area) for various processes executed by the CPU. Then, the control unit 11 controls the management server 1 by causing the CPU to execute various control programs stored in advance in the ROM or the storage unit 12.

[0028] Specifically, the control unit 11 includes various processing units such as a registration processing unit 111, a permission processing unit 112, and a transmission processing unit 113. Note that the control unit 11 functions as the various processing units by executing various processes according to the meeting support program. Also, part or all of the processing units included in the control unit 11 may be configured by electronic circuits. Note that the meeting support program may be a program for causing a plurality of processors to function as the various processing units.

[0029] The registration processing unit 111 registers the meeting reservation information management table T1 (see FIG. 3), the meeting room information management table T2 (see FIG. 4), the device information management table T3 (see FIG. 5), and the user information management table T4 (see FIG. 6). For example, when a user makes a meeting reservation on the user terminal 2, the registration processing unit 111 registers the meeting information in the meeting reservation information management table T1.

[0030] The permission processing unit 112 permits login to the meeting support application for holding an online meeting. Specifically, the permission processing unit 112 identifies the meeting in which the user participates based on the user information and the tag ID acquired from the user terminal 2, and permits login to the meeting support application of the identified meeting. When the permission processing unit 112 permits the user's login, it transmits the login permission information, the meeting information of the identified meeting, and the meeting room information corresponding to the meeting room ID associated with the tag ID to the user terminal 2 of the user.

[0031] For example, the permission processing unit 112 refers to the meeting room information management table T2 (see FIG. 4) to identify the meeting room corresponding to the tag ID acquired from the user terminal 2. For example, when the user U1 brings the user terminal 2 close to the communication tag Tg1 installed in the meeting room 1, the user terminal 2 communicates with the communication tag Tg1 and reads the tag ID "N001". When the permission processing unit 112 acquires the tag ID "N001" from the user terminal 2, it refers to the meeting room information management table T2 (see FIG. 4) to acquire the meeting room ID "R0001" corresponding to the tag ID "N001". Further, the permission processing unit 112 identifies the meeting corresponding to the meeting room ID "R0001" from the meeting reservation information management table T1 (see FIG. 3) and acquires the meeting information. Here, the permission processing unit 112 acquires the meeting information of the meeting held on the opening date of the day (here, "April 10, 2021") and corresponding to the meeting room ID "R0001" (the "regular meeting" and the "budget meeting"). The permission processing unit 112 transmits the login permission information, the meeting information of the identified meeting (the "regular meeting" and the "budget meeting"), and the meeting room information corresponding to the meeting room ID "R0001" to the user terminal 2 of the user U1.

[0032] The transmission processing unit 113 transmits the meeting information designated by the user from among a plurality of pieces of meeting information displayed on the user terminal 2, the meeting room information, and the user information to the meeting room terminal 3. For example, as shown in FIG. 8, when the user U1 designates the meeting information D1 of the "regular meeting" among the meeting information D1 of the "regular meeting" and the meeting information D2 of the "budget meeting" displayed on the user terminal 2, the transmission processing unit 113 transmits the meeting information D1 of the "regular meeting", the meeting room information corresponding to the meeting room ID "R0001", and the user information of the user U1 to the meeting room terminal 3 installed in the meeting room 1 corresponding to the meeting room ID "R0001".

[0033] [User Terminal 2] As shown in FIG. 2, the user terminal 2 includes a control unit 21, a storage unit 22, an operation display unit 23, a communication unit 24, a tag reading unit 25, and the like. The user terminal 2 is an information processing device (for example, a mobile terminal) such as a smartphone, a mobile phone, a tablet terminal, or a personal computer (PC). FIG. 2 illustrates the user terminal 2 of the user U1 (see FIG. 1) participating in a meeting in the meeting room 1.

[0034] The tag reading unit 25 communicates with the communication tag Tg1 to read the tag ID. For example, the tag reading unit 25 performs data communication with the communication tag Tg1 by short-range wireless communication. As another embodiment, for example, when a two-dimensional code is installed in the meeting room 1 instead of the communication tag Tg1, the camera mounted on the user terminal 2 may read the two-dimensional code.

[0035] The communication unit 24 is a communication unit that connects the user terminal 2 to the network N1 by wire or wirelessly and performs data communication according to a predetermined communication protocol with other devices (for example, the management server 1, the meeting room terminal 3) via the network N1.

[0036] The operation display unit 23 is a user interface including a display unit such as a liquid crystal display or an organic EL display that displays various types of information, and an operation unit such as a mouse, a keyboard, or a touch panel that accepts operations. The operation display unit 23 accepts, for example, the operations of the user U1 of the user terminal 2.

[0037] The storage unit 22 is a non-volatile storage unit such as an HDD, an SSD, or a flash memory that stores various types of information. The storage unit 22 stores control programs such as a conference support program for causing the control unit 21 to execute the conference support process (see FIG. 12) described later. For example, the conference support program is non-temporarily recorded on a computer-readable recording medium such as a CD or a DVD, and is read by a reading device (not shown) such as a CD drive or a DVD drive provided in the user terminal 2 and stored in the storage unit 22. Note that the conference support program may be distributed from a cloud server and stored in the storage unit 22.

[0038] The control unit 21 includes control devices such as a CPU, a ROM, and a RAM. The CPU is a processor that executes various arithmetic processes. The ROM stores in advance control programs such as a BIOS and an OS for causing the CPU to execute various processes. The RAM stores various types of information and is used as a temporary storage memory (working area) for various processes executed by the CPU. Then, the control unit 21 controls the user terminal 2 by causing the CPU to execute various control programs stored in advance in the ROM or the storage unit 22.

[0039] Specifically, the control unit 21 includes various processing units such as a display processing unit 211, an acquisition processing unit 212, and a reception processing unit 213. Note that the control unit 21 functions as the various processing units by causing the CPU to execute various processes according to the control program. Also, some or all of the processing units included in the control unit 21 may be configured by electronic circuits. Note that the control program may be a program for causing a plurality of processors to function as the various processing units.

[0040] The display processing unit 211 causes various information to be displayed on the operation display unit 23. For example, the display processing unit 211 causes various screens to be displayed, such as the menu screen of the conference support application (see FIG. 7), the conference information screen for displaying conference information acquired from the management server 1 (see FIG. 8), and the operation screen for receiving user setting operations in a conference (see FIG. 10).

[0041] The acquisition processing unit 212 acquires the tag ID corresponding to the communication tag Tg by communicating with the communication tag Tg installed in the conference room of the user terminal 2. Here, the acquisition processing unit 212 acquires the tag ID "N001" corresponding to the communication tag Tg1 read by communicating with the communication tag Tg1 installed in the conference room 1 by the tag reading unit 25.

[0042] When the acquisition processing unit 212 acquires the tag ID, it transmits the tag ID and the user information of the user terminal 2 to the management server 1. Here, the acquisition processing unit 212 transmits the tag ID "N001", the user ID "U001" of the user U1, and the authentication information "pass-u1" (see FIG. 6) to the management server 1.

[0043] Here, the permission processing unit 112 of the management server 1 identifies the conference in which the user participates based on the user information and the tag ID acquired from the user terminal 2, and permits the user to log in to the conference support application of the identified conference. For example, the permission processing unit 112 refers to the conference room information management table T2 (see FIG. 4) and acquires the conference room ID "R0001" corresponding to the tag ID "N001" acquired from the user terminal 2. Further, the permission processing unit 112 acquires the conference information of the conferences ("regular meeting" and "budget meeting") corresponding to the conference room ID "R0001" from the conference reservation information management table T1 (see FIG. 3). The permission processing unit 112 transmits the login permission information, the conference information of the identified conferences ("regular meeting" and "budget meeting"), and the conference room information corresponding to the conference room ID "R0001" to the user terminal 2 of the user U1.

[0044] When the display processing unit 211 of the user terminal 2 acquires the meeting information from the management server 1, as shown in FIG. 8, it displays a meeting information screen including the meeting information D1 of the "regular meeting" and the meeting information D2 of the "budget meeting".

[0045] The reception processing unit 213 receives various operations from the user. For example, the reception processing unit 213 receives a menu selection operation on the menu screen shown in FIG. 7. For example, when conducting a meeting, the user U1 selects the "Meeting" menu button. Also, when the user U1 wants to display the screen of the user terminal 2 on the display 4 installed in the meeting room 1, the user U1 selects the "Screen Sharing" menu button.

[0046] Also, on the meeting information screen shown in FIG. 8, the reception processing unit 213 receives an operation in which the user U1 designates either the meeting information D1 or the meeting information D2. For example, the user U1 selects the meeting information (here, the meeting information D1 of the "regular meeting") of the meeting to start now and presses the "Start" button. The reception processing unit 213 transmits the meeting information D1 designated by the user U1 to the management server 1, and the management server 1 receives the said meeting information D1. When the transmission processing unit 113 of the management server 1 receives the meeting information D1, it transmits the meeting information D1, the meeting room information corresponding to the meeting room ID "R0001", and the user information of the user U1 to the meeting room terminal 3 in the meeting room 1.

[0047] Also, when the login to the meeting support application for the meeting is permitted and the meeting starts, the reception processing unit 213 receives an instruction from the user U1 to display the materials available for the meeting. When the reception processing unit 213 receives the said display instruction, it transmits the display instruction of the materials to the meeting room terminal 3 in the meeting room 1. When the meeting room terminal 3 receives, for example, an instruction to display Material A from the user terminal 2, it displays Material A on the meeting support application screen of the display 4 shown in FIG. 11, for example. Also, the meeting support application displays Material A on the display 4 in the meeting room 2 via the meeting room terminal 3 in the meeting room 2.

[0048] In addition, the reception processing unit 213 receives various control instructions from the user U1 during the meeting. For example, the reception processing unit 213 receives control instructions regarding various applications controlled by the meeting support application (such as screen sharing, camera, volume, etc. of the online meeting application) (see FIG. 10). Also, the reception processing unit 213 receives control instructions regarding the devices installed in Conference Room 1 (such as Display 4, screen sharing device, printer, lighting, air purifier, air conditioner, etc.). The control unit 21 executes various control processes based on the control instructions received by the reception processing unit 213.

[0049] In addition, the reception processing unit 213 receives an instruction to end the meeting from the user U1. When the reception processing unit 213 receives an instruction to end the meeting from the user U1, it transmits the meeting end instruction to the conference room terminal 3. When the conference room terminal 3 receives the meeting end instruction from the user terminal 2, it ends the meeting and logs off from the meeting support application.

[0050] [Conference Room Terminal 3] As shown in FIG. 2, the conference room terminal 3 includes a control unit 31, a storage unit 32, an operation unit 33, a communication unit 34, etc. The conference room terminal 3 is an information processing device such as a personal computer (PC) for example. In FIG. 2, the conference room terminal 3 installed in Conference Room 1 is illustrated. A Display 4 is connected to the conference room terminal 3 by a wired LAN, for example.

[0051] The communication unit 34 is a communication unit that connects the conference room terminal 3 to the network N1 by wire or wirelessly and performs data communication according to a predetermined communication protocol with other devices (such as the management server 1 and the user terminal 2) via the network N1.

[0052] The operation unit 33 is composed of a mouse, a keyboard, or a touch panel, etc., and receives the operations of the users U1 to U4 in Conference Room 1, for example.

[0053] The storage unit 32 is a non-volatile storage unit such as an HDD, an SSD, or a flash memory that stores various types of information. The storage unit 32 stores control programs such as a conference support program for causing the control unit 31 to execute the conference support process (see FIG. 14) described later. For example, the conference support program is non-temporarily recorded on a computer-readable recording medium such as a CD or a DVD, and is read by a reading device (not shown) such as a CD drive or a DVD drive provided in the conference room terminal 3 and stored in the storage unit 32. Note that the conference support program may be distributed from a cloud server and stored in the storage unit 32.

[0054] The control unit 31 includes control devices such as a CPU, a ROM, and a RAM. The CPU is a processor that executes various arithmetic processes. The ROM stores in advance control programs such as a BIOS and an OS for causing the CPU to execute various processes. The RAM stores various types of information and is used as a temporary storage memory (working area) for various processes executed by the CPU. Then, the control unit 31 controls the conference room terminal 3 by causing the CPU to execute various control programs stored in advance in the ROM or the storage unit 32.

[0055] Specifically, the control unit 31 includes various processing units such as a display processing unit 311, a login processing unit 312, and a conference processing unit 313. Note that the control unit 31 functions as the various processing units by causing the CPU to execute various processes according to the control program. Also, some or all of the processing units included in the control unit 31 may be configured by electronic circuits. Note that the control program may be a program for causing a plurality of processors to function as the various processing units.

[0056] The display processing unit 311 causes various information to be displayed on the display 4. For example, the display processing unit 311 causes the meeting schedule received from the management server 1 to be displayed on the display 4. For example, when the management server 1 transmits the meeting schedule scheduled to be held in Conference Room 1 on the same day to the conference room terminal 3, the display processing unit 311 of the conference room terminal 3 causes the meeting schedule received from the management server 1 to be displayed on the display 4.

[0057] In addition, when the meeting starts, the display processing unit 311 causes various meeting support application screens to be displayed on the display 4. For example, when the display processing unit 311 receives a display instruction for Material A available for the meeting from the user terminal 2, it causes Material A to be displayed on the meeting support application screen of the display 4 (see Fig. 11).

[0058] When the permission processing unit 112 of the management server 1 permits login to the meeting support application of the meeting, the login processing unit 312 executes the login processing to the meeting support application based on the user information. Specifically, when the management server 1 permits login to the meeting support application and transmits the meeting information D1 of the meeting (the "regular meeting") designated by the user U1, the conference room information of Conference Room 1, and the user information (user ID "U001" and authentication information "pass-u1") to the conference room terminal 3, the login processing unit 312 starts the meeting support application and executes the login processing using the user information (see Fig. 9). Note that the display processing unit 311 does not necessarily need to display the login screen shown in Fig. 9 on the display 4.

[0059] When the login processing by the login processing unit 312 is executed, the meeting by the meeting support application starts. In this embodiment, since the management server 1 transmits the meeting information D1, the conference room information, and the user information to the conference room terminal 3 after approving the user information corresponding to the meeting, the meeting starts automatically when the login processing unit 312 executes the login processing using the user information. In this way, the meeting can be started without the user performing a login operation.

[0060] When the meeting starts, the conference processing unit 313 receives and executes control instructions regarding various applications controlled by the conference support application from the user (see FIG. 10). For example, the conference processing unit 313 executes processes such as changing the display file, turning on / off screen sharing on the online conference application, turning on / off the camera, adjusting the volume, and ending the meeting.

[0061] Also, during the meeting, the conference processing unit 313 displays the conference support screen P1 on the conference support application screen shown in FIG. 11. The conference processing unit 313 displays the progress of the meeting, the remaining time until the meeting end time, etc. on the conference support screen P1. Also, the conference processing unit 313 receives various setting operations of the user and receives an extension instruction for the meeting on the conference support screen P1.

[0062] [Conference Support Processing] Hereinafter, an example of the procedure of the conference support process executed in the conference system 100 will be described with reference to FIGS. 12, 13, and 14.

[0063] Note that the present invention can be regarded as an invention of a conference support method (an example of the conference support method of the present invention) that executes one or more steps included in the conference support process. Also, one or more steps included in the conference support process described here may be appropriately omitted. Also, the execution order of each step in the conference support process may be different within the range that produces the same operational effects.

[0064] Furthermore, here, the case where the control unit 11 of the management server 1, the control unit 21 of the user terminal 2, and the control unit 31 of the conference room terminal 3 execute each step in the conference support process is taken as an example for explanation. However, in other embodiments, one or more processors may execute each step in the conference support process in a distributed manner.

[0065] FIG. 12 shows an example of the procedure of the conference support process executed by the control unit 21 of the user terminal 2, FIG. 13 shows an example of the procedure of the conference support process executed by the control unit 11 of the management server 1, and FIG. 14 shows an example of the procedure of the conference support process executed by the control unit 31 of the conference room terminal 3.

[0066] [Conference Support Process in User Terminal 2] In step S1 shown in FIG. 12, the control unit 21 of the user terminal 2 determines whether the tag ID has been read. For example, when the user U1 brings the user terminal 2 close to the communication tag Tg1 (see FIG. 1) attached to the display 4 in conference room 1, the control unit 21 causes the tag reading unit 25 of the user terminal 2 to communicate with the communication tag Tg1, thereby acquiring the tag ID "N001".

[0067] Next, in step S2, the control unit 21 transmits the acquired tag ID and user information to the management server 1. Here, the control unit 21 transmits the tag ID "N001", the user ID "U001" of the user U1, and the authentication information "pass-u1" (see FIG. 6) to the management server 1.

[0068] Next, in step S3, the control unit 21 determines whether login permission information has been received from the management server 1. If the control unit 21 receives the login permission information (S3: Yes), the process proceeds to step S4. On the other hand, if the control unit 21 does not receive the login permission information (S3: No), the process ends. For example, when the meeting information of the meeting in which the user U1 participates in conference room 1 associated with the tag ID "N001" is registered (reserved) in the meeting reservation information management table T1 (see FIG. 3), the control unit 31 of the management server 1 transmits the login permission information to the user terminal 2, and when the said meeting information is not registered in the meeting reservation information management table T1, the login permission information is not transmitted to the user terminal 2, or login-disabled information (login rejection information) is transmitted to the user terminal 2.

[0069] In step S4, the control unit 21 acquires meeting information and meeting room information from the management server 1. Here, the control unit 21 acquires the meeting room information of the meeting room with the meeting room ID "R0001" corresponding to the tag ID "N001" (see FIG. 4) and the meeting information of "regular meeting" and "budget meeting" associated with the meeting room ID "R0001" (see FIG. 3) from the management server 1.

[0070] The control unit 21 causes the operation display unit 23 to display the meeting information acquired from the management server 1 (see FIG. 8). Further, the control unit 21 accepts an operation in which the user U1 designates either the meeting information D1 or the meeting information D2 on the meeting information screen shown in FIG. 8.

[0071] Next, in step S5, the control unit 21 transmits the meeting information of the meeting designated by the user U1 to the management server 1. Here, the user U1 designates the meeting information D1 of the "regular meeting" that is about to start. When the user U1 designates a meeting, the management server 1 transmits the meeting information, meeting room information, and user information related to the meeting to the meeting room terminal 3 at the venue (meeting room 1) of the meeting. The meeting room terminal 3 starts the meeting by logging in to the meeting support application using the user information.

[0072] When the meeting is started, in step S6, the control unit 21 transmits a display instruction for the materials used in the meeting (for example, material A) to the meeting room terminal 3. The control unit 31 of the meeting room terminal 3 causes the material A to be displayed on the display 4 based on the display instruction (see FIG. 11).

[0073] Next, in step S7, the control unit 21 causes the operation display unit 23 to display an operation screen (see FIG. 10) for accepting the setting operation of the user U1 in the meeting.

[0074] Next, in step S8, the control unit 21 determines whether it has received a control instruction from the user U1. For example, the control unit 21 receives control instructions regarding various operations (such as screen sharing, camera, volume, etc.) included in the online meeting application controlled by the meeting support application, and control instructions regarding devices (such as display 4, screen sharing device, printer, lighting, air purifier, air conditioner, etc.) installed in meeting room 1. When the control unit 21 receives a control instruction from the user U1 (S8: Yes), the process proceeds to step S9. On the other hand, when the control unit 21 does not receive a control instruction from the user U1 (S8: No), the process proceeds to step S10.

[0075] In step S9, the control unit 21 executes control processing according to the control instruction. For example, the control unit 21 sets the screen sharing of the online meeting application controlled by the meeting support application to ON. Also, for example, the control unit 21 causes a printer (not shown) installed in meeting room 1 to execute a printing process for materials.

[0076] In step S10, the control unit 21 determines whether it has received an end operation for the meeting. For example, when the user U1 presses the end ("End") button on the operation screen (see FIG. 10), the control unit 21 receives the meeting end operation. When the control unit 21 receives the meeting end operation, it sends a meeting end instruction to the meeting room terminal 3.

[0077] The control unit 21 of the user terminal 2 executes the above-mentioned meeting support processing in this way.

[0078] [Meeting Support Processing in Management Server 1] In step S21 shown in FIG. 13, the control unit 11 of the management server 1 determines whether it has received a tag ID and user information from the user terminal 2. Here, the control unit 11 receives the tag ID "N001", the user ID "U001", and the authentication information "pass-u1" from the user terminal 2 of the user U1.

[0079] Next, in step S22, the control unit 11 identifies the conference room corresponding to the tag ID. Specifically, the control unit 11 refers to the conference room information management table T2 (see FIG. 4), identifies the conference room 2 corresponding to the tag ID "N001" acquired from the user terminal 2, and acquires the conference room ID "R0001" corresponding to the conference room 2.

[0080] Next, in step S23, the control unit 11 determines whether the conference information of the conference that user U1 plans to participate in is registered (reserved) in the conference reservation information management table T1 (see FIG. 3). If the conference information is registered in the conference reservation information management table T1 (S23: Yes), the process proceeds to step S24. On the other hand, if the conference information is not registered in the conference reservation information management table T1 (S23: No), the process ends.

[0081] In step S24, the control unit 11 transmits the login permission information to the user terminal 2 of user U1. Also, in step S25, the control unit 11 transmits the conference information and the conference room information to the user terminal 2 of user U1. Here, the control unit 11 transmits the conference room information (see FIG. 4) of the conference room ID "R0001" corresponding to the tag ID "N001" and the conference information (see FIG. 3) of "regular meeting" and "budget meeting" associated with the conference room ID "R0001" to the user terminal 2 of user U1.

[0082] Next, in step S26, the control unit 11 receives the conference information of the conference designated by user U1 from the user terminal 2. Here, the control unit 11 receives the conference information D1 of the "regular meeting" designated by user U1 (see step S5 in FIG. 12).

[0083] Next, in step S27, the control unit 11 transmits the conference information, the conference room information, and the user information regarding the conference designated by user U1 to the conference room terminal 3 at the venue (conference room 1) of the conference.

[0084] The control unit 11 of the management server 1 executes the above-mentioned conference support process.

[0085] [Meeting Support Processing on the Conference Room Terminal 3] In step S31 shown in FIG. 14, the control unit 31 of the conference room terminal 3 determines whether it has received conference information, conference room information, and user information from the management server 1. Here, the control unit 31 receives conference information regarding the "regular meeting" designated by the user U1, the conference room information of conference room 2, and user information (user ID "U001" and authentication information "pass-u1").

[0086] Next, in step S32, the control unit 31 activates the meeting support application. Next, in step S33, the control unit 31 executes a login process to the meeting support application based on the user information. For example, the control unit 31 executes a login process using the user ID "U001" and the authentication information "pass-u1" (see FIG. 9). Note that the control unit 31 may execute the login process without displaying the login screen shown in FIG. 9 on the display 4. Thereby, it is possible to prevent the leakage of personal information due to the display of the user information on the display 4.

[0087] Next, in step S34, the control unit 31 starts an online meeting using the meeting support application. Specifically, in step S35, the control unit 31 displays a meeting material (here, material A) on the display 4 based on a display instruction received from the user terminal 2 (see step S6 in FIG. 12) (see FIG. 11). Also, the control unit 31 displays a meeting support screen P1 on the meeting support application screen shown in FIG. 11. Further, the control unit 31 transmits and receives audio, video, and display screens by connecting to the conference room terminal 3 in conference room 2.

[0088] Next, in step S36, the control unit 31 determines whether it has received a control instruction from the user terminal 2 (see step S9 in FIG. 12). When the control unit 31 receives a control instruction from the user terminal 2, in step S37, it executes a control process according to the control instruction. For example, when the control unit 31 receives an instruction for screen sharing of material B from the user terminal 2, it displays material B on the display 4.

[0089] Next, in step S38, the control unit 31 determines whether or not it has received an end-of-meeting instruction from the user terminal 2 (see step S11 in FIG. 12). When the control unit 31 receives an end-of-meeting instruction from the user terminal 2, it ends the meeting (S39). The control unit 31 repeats the processes of steps S36 to S37 until it receives an end-of-meeting instruction from the user terminal 2 (S38: No).

[0090] Finally, in step S40, the control unit 11 logs off from the meeting support application.

[0091] The control unit 31 of the conference room terminal 3 executes the above-described conference support process.

[0092] As described above, the conference system 100 identifies the user's location (conference room) and the conference on the condition that the user terminal 2 reads the communication tag Tg installed in the conference room, permits login to the conference support application for the conference, and starts the conference.

[0093] Specifically, the conference system 100 according to the present embodiment includes a user terminal 2 of a user participating in a conference in a conference room and a management server 1 that manages conference reservation information and conference room information regarding the conference room, and executes a conference support application. Further, the conference system 100 communicates with the communication tag Tg installed in the conference room by the user terminal 2, obtains the tag ID corresponding to the communication tag Tg, identifies the conference in which the user participates based on the user information and the tag ID obtained from the user terminal 2, and permits login to the conference support application of the identified conference.

[0094] As a result, a user participating in a meeting can start a meeting by the meeting support application by reading the communication tag Tg installed in the meeting room with his / her user terminal 2. Therefore, since the user does not need to perform an operation of inputting login information (e.g., user ID, password) to the meeting support application when starting the meeting, the trouble when starting the meeting can be saved. Thus, the user can easily start the meeting and conduct the meeting efficiently.

[0095] In addition, in the present embodiment, an example is given of a configuration in which in meeting room 1, user U1 reads communication tag Tg1 with user terminal 2, and logs in to the meeting support application on the meeting room terminal 3 installed in meeting room 1. However, the meeting system 100 executes the same process in meeting room 2 as well. Specifically, in meeting room 2 (see FIG. 1), when user U5 reads communication tag Tg2 with user terminal 2, the meeting system 100 logs in to the meeting support application on the meeting room terminal 3 installed in meeting room 2. By logging in to the meeting support application in each of meeting room 1 and meeting room 2, the meeting system 100 realizes an online meeting in meeting room 1 and meeting room 2.

[0096] Also, in the present embodiment, the meeting system 100 includes a meeting room terminal 3 installed in the meeting room. When the management server 1 permits login to the meeting support application of the meeting, the management server 1 transmits user information to the meeting room terminal 3. The meeting room terminal 3 executes a login process to the meeting support application based on the user information received from the management server 1, and when the login process is completed, displays a meeting support application screen (meeting screen) on the display 4 installed in the meeting room.

[0097] The present invention is not limited to the above-described embodiments. As another embodiment, in the conference system 100, the conference room terminal 3 may be omitted. Specifically, the user terminal 2 may have the functions of the conference room terminal 3. For example, when the user terminal 2 receives login permission information from the management server 1, it starts a conference support application and executes a login process. Then, the user terminal 2 displays a conference support application screen (see, for example, FIG. 11) on its own operation display unit 23 to start a conference. Note that the user terminal 2 may display the conference support application screen on the display 4.

[0098] Also, as another embodiment, the user terminal 2 may have the functions of the management server 1 and the conference room terminal 3. For example, the user terminal 2 identifies a conference that the user plans to participate in based on the tag ID and user information read from the communication tag Tg. Note that the user terminal 2 may access, for example, a server that manages the conference schedule to identify a conference corresponding to the tag ID and user information, and determine whether to allow login to the conference support application. Then, when the user terminal 2 determines that login is possible, it starts the conference support application and executes a login process.

[0099] As described above, the conference support system of the present invention may be configured by the management server 1, the user terminal 2, and the conference room terminal 3 as shown in FIG. 2, or may be configured by the management server 1 and the user terminal 2, or may be configured by the user terminal 2 alone.

[0100] In addition, the conference support system of the present invention can also be configured by freely combining the above-described embodiments within the scope of the invention described in each claim, or by appropriately modifying or partially omitting each embodiment.

Explanation of Reference Numerals

[0101] 1: Management server 2: User terminal 3: Conference room terminal 4: Display 25: Tag Reading Unit 100: Conference System 111: Registration Processing Unit 112: Permission Processing Unit 113: Transmission Processing Unit 211: Display Processing Unit 212: Acquisition Processing Unit 213: Reception Processing Unit 311: Display Processing Unit 312: Login Processing Unit 313: Conference Processing Unit T1: Conference Reservation Information Management Table T2: Conference Room Information Management Table T3: Equipment Information Management Table T4: User Information Management Table Tg: Communication Tag

Claims

1. A meeting support system that includes a user terminal of a user participating in a meeting in a meeting room and executes a meeting support application for the meeting, a storage unit that pre-stores meeting reservation information in which one or more pieces of meeting information including user information for identifying a user and meeting room identification information for identifying the meeting room associated with the communication medium installed in the meeting room are registered, an acquisition processing unit that, when the user terminal communicates with the communication medium, acquires the medium identification information corresponding to the communication medium in the user terminal, a permission processing unit that refers to the storage unit, identifies the meeting in which the user participates based on the user information for identifying the user acquired from the user terminal and the medium identification information, and permits login to the meeting support application of the identified meeting, a login processing unit that, when login to the meeting support application of the meeting is permitted by the permission processing unit, executes a login process to the meeting support application based on the user information in a meeting room terminal installed in the meeting room, A meeting support system comprising:

2. When login to the meeting support application of the meeting is permitted by the permission processing unit, the user terminal further includes a reception processing unit that receives an instruction to display materials available for the meeting. The meeting support system according to claim 1.

3. The user terminal includes a reading unit that reads medium identification information for identifying the communication medium, and the acquisition processing unit of the user terminal acquires the medium identification information read by the reading unit. The meeting support system according to claim 1 or 2.

4. When the permission processing unit permits login to the meeting support application, the permission processing unit transmits the meeting information corresponding to the user information and the medium identification information to the user terminal. The meeting support system according to claim 3.

5. The meeting support system further includes a transmission processing unit that transmits the meeting information designated by the user from among the plurality of pieces of meeting information displayed on the user terminal and the user information to the meeting room terminal including the login processing unit. The meeting support system according to claim 4.

6. A management server that manages meeting reservation information and meeting room information regarding the meeting room and includes the permission processing unit, and the meeting room terminal including the login processing unit, further comprising: When the management server permits login to the meeting support application for the meeting, the management server transmits the user information to the conference room terminal. Based on the user information received from the management server, the conference room terminal executes a login process to the meeting support application, and when the login process is completed, the conference room terminal causes a meeting screen to be displayed on a display installed in the conference room. The meeting support system according to claim 1.

7. When the conference room terminal receives a display instruction for materials available for the meeting from the user terminal, the conference room terminal causes the materials to be displayed on the display. The meeting support system according to claim 6.

8. A meeting support method including a user terminal of a user participating in a meeting in a conference room and executing a meeting support application for the meeting, wherein one or more processors perform a storage step of preliminarily storing in a storage unit meeting reservation information in which one or more pieces of meeting information including user information for identifying a user and meeting room identification information for identifying the conference room associated with media identification information for identifying a communication medium installed in the conference room are registered; an acquisition step of, when the user terminal communicates with the communication medium, acquiring, at the user terminal, the media identification information corresponding to the communication medium; a permission step of referring to the storage unit to identify a meeting in which the user participates based on the user information for identifying the user acquired from the user terminal and the media identification information, and permitting login to the meeting support application for the identified meeting; a login step of, when login to the meeting support application for the meeting is permitted in the permission step, executing, at a conference room terminal installed in the conference room, a login process to the meeting support application based on the user information; A meeting support method for performing the above.

9. A meeting support program including a user terminal of a user participating in a meeting in a conference room and executing a meeting support application for the meeting, wherein one or more processors perform a storage step of preliminarily storing in a storage unit meeting reservation information in which one or more pieces of meeting information including user information for identifying a user and meeting room identification information for identifying the conference room associated with media identification information for identifying a communication medium installed in the conference room are registered; An acquisition step of acquiring, in the user terminal, the media identification information corresponding to the communication medium when the user terminal communicates with the communication medium; A permission step of referring to the storage unit, specifying a meeting in which the user participates based on the user information for identifying the user acquired from the user terminal and the media identification information, and permitting login to a meeting support application for the specified meeting; A login step of, when login to the meeting support application for the meeting is permitted in the permission step, executing login processing to the meeting support application based on the user information in a conference room terminal installed in the conference room; A meeting support program for causing one or more processors to execute.

Images