JP7020314B2 - Communication system, communication method, information processing device, program - Google Patents

Description

The present invention relates to communication systems, communication methods, information processing devices, and programs.

Facilities such as conference rooms where multiple participants gather to hold a meeting may be reserved and used in advance. In recent years, it has become possible for users such as participants to reserve facilities using a schedule management system or the like.

In addition, a participant at his / her own base may hold a remote conference with a participant in a conference room at a remote location, and a technique for supporting a conference held at such a remote location is known (for example, a patent). See Document 1). Patent Document 1 discloses a system for sharing a whiteboard screen among a plurality of terminal devices.

However, in the conventional technique, there is a problem that a user who wants to start using the facility needs to perform an operation for starting to use the electronic information board. For example, even if a participant reserves a conference room in advance and checks in to the conference room, the participant needs to create an electronic information board separately from the check-in for the terminal device, so it is not always necessary. It wasn't convenient.

In view of the above problems, it is an object of the present invention to provide a communication system in which a user who intends to start using a facility can start using an electronic information board.

In view of the above problems, the present invention is a communication system including an information processing device that can use a service for managing screen information of an electronic information board and a terminal device that communicates with the information processing device via a network.
The information processing apparatus obtains information acquisition means for acquiring information on the schedule from a second information processing apparatus that manages a schedule for use of the facility in which the terminal apparatus is arranged, and the information acquisition means obtains information on the schedule. When acquired, the board creation request means for requesting the service to create the electronic information board, and
It has a transmission means for transmitting information for accessing the electronic information board created by the service to the terminal device.
The terminal device first accesses the electronic information board by using an acquisition means for acquiring information for accessing the electronic information board and information for accessing the electronic information board received by the acquisition means. It has a communication means of.

It is possible to provide a communication system in which a user who wants to start using the facility can start using the electronic information board.

It is an example of the figure schematically explaining the operation of the communication system. This is an example of a schematic configuration diagram of a communication system. It is a hardware block diagram of an example of a computer system. This is an example of a functional block diagram showing the functions of a WB system, a conference reservation system, a schedule management system, a user terminal, and a terminal device in a block shape. It is an example of the figure explaining the reservation of a conference room and the reservation information. This is an example of a sequence diagram showing a procedure for a communication system to create and display a whiteboard. It is a figure which shows an example of the reservation information confirmation screen displayed by the organizer terminal. It is a figure which shows an example of the check-in screen which a terminal apparatus displays. It is a figure which shows an example of the initial screen of a whiteboard. It is a figure which shows an example of the end reception column of a whiteboard. This is an example of a sequence diagram showing a procedure for a communication system to create and display a whiteboard. This is an example of a flowchart or the like explaining the process of creating a whiteboard in response to a reminder response. It is an example of the figure explaining the method of sharing the URL of the whiteboard. It is a figure which shows an example of the mail address input screen at the time of registering the URL of a whiteboard in a participant's schedule. This is an example of a functional block diagram showing the functions of the WB system, the conference reservation system, the schedule management system, the user terminal, and the terminal device in a block shape (Example 2). It is an example of a sequence diagram showing a procedure in which a communication system creates and displays a whiteboard (Example 2). This is an example of a schematic configuration diagram of a communication system (Example 3). It is an example of the figure explaining the communication path between systems or terminals of a communication system. This is an example of a functional block diagram showing the functions of the WB system, the conference reservation system, the schedule management system, the user terminal, the conference room terminal, and the WB terminal in a block shape (Example 3). It is a figure which shows an example of the reservation information stored in the reservation information DB. This is an example of a sequence diagram showing a procedure in which the communication system 1 creates a whiteboard at the time of reservation and displays it at the time of check-in. It is a figure which shows an example of the reservation information screen displayed by a WB terminal. It is an example of a sequence diagram showing a procedure for displaying a participant to which a communication system has been added. It is an example of another sequence diagram of the procedure for displaying the participants to which the communication system has been added. This is an example of a sequence diagram showing a procedure in which a communication system creates a URL of a whiteboard at check-in and the whiteboard displays reservation information.

Hereinafter, a communication system and a communication method performed by the communication system will be described as an example of a mode for carrying out the present invention.

<Outline of operation of communication system>
First, the outline of the operation of the communication system 1 of the present embodiment will be described with reference to FIG. FIG. 1 is an example of a diagram schematically illustrating the operation of the communication system 1. First, the terminal device 10 is set in the conference room 9. The terminal device 10 can communicate with the conference reservation system 50 and the whiteboard system (hereinafter referred to as WB system 40) that provides the functions of the conference reservation system 50 and the electronic blackboard to the terminal device 10 via a network. Further, the conference reservation system 50 can communicate with the schedule management system 60 and the WB system 40 in which the participants reserve the conference room 9 via the network. The conference room B has the same configuration as the conference room A, but is omitted in FIG. 1.
(1) The conference reservation system 50 periodically acquires reservation information of the conference room 9 from the schedule management system 60, for example.
(2) The conference reservation system 50 requests the WB system 40 to create a whiteboard for use in the reserved conference room, and acquires the URL of the whiteboard from the WB system 40.
(3) The conference reservation system 50 assigns a reservation ID to the acquired reservation information, and registers the reservation ID and the URL of the whiteboard in the schedule management system 60.
(4) Participants operate the terminal device 10 of the conference room 9 to check in. In response to this operation, the terminal device 10 transmits a check-in request to the conference reservation system 50.
(5) When the terminal device 10 acquires the notification that the check-in is successful, the terminal device 10 acquires the URL of the whiteboard from the conference reservation system 50.
(6) As a result, the terminal device 10 sets the URL of the whiteboard as the communication destination and communicates with the WB system 40, so that the initial screen of the whiteboard is displayed on the terminal device 10.

Similarly, on the conference room B side, the terminal device 10 specifies the same whiteboard URL and communicates with the WB system 40, so that the participants in the conference room A and the conference room B can participate in the conference while viewing the same screen. .. However, it is not necessary to hold a remote conference for the explanation of the communication system 1 of the present embodiment. The method for creating a whiteboard according to the present embodiment can be suitably applied to a situation in which a user simply reserves one conference room and wants to create a whiteboard according to the conference.

In this way, when the participant checks in, the terminal device 10 acquires the URL of the whiteboard from the conference reservation system 50, communicates with the WB system 40, and displays the initial screen of the whiteboard, so that the participant checks. You can use the whiteboard by operating in. Further, since the whiteboard URL is registered in the schedule management system 60, if the participants obtain the whiteboard URL from the schedule management system 60 after the meeting is completed, the drawing handwritten on the terminal device 10 during the meeting is drawn. You can display the image data etc. on your participant terminal again.

<Terminology>
In the present embodiment, the whiteboard refers to the function of the electronic blackboard provided from the server to the client. In other words, there is no device called an electronic blackboard, and the client and the server communicate with each other to realize the same function as the electronic blackboard on the client side. The description of creating a whiteboard also means that the same functions as the electronic blackboard can be used on the client side. Any electronic blackboard with a browser function can operate as a client. Further, the electronic blackboard has a function of allowing the user to add information such as characters, figures, images, handwritten images, and stamps to the displayed screen.

The start of use of a facility means that a person who can use the reserved facility by reservation starts. In this embodiment, the term check-in will be used. The start-of-use request is described by the term check-in request.

The schedule for the use of the facility is the schedule of when and how the facility will be used. Information about the schedule is the specific content of the schedule. The schedule may be called a timetable, a schedule, a schedule, or the like. Information about the schedule will be described in the present embodiment by the term reservation information. In addition, the information about the schedule includes the registration of the schedule, the reminding of the schedule, and the start (check-in) of the use (schedule) of the facility. A facility is a facility for a certain purpose. For example, there are conference rooms, booths, classrooms, etc.

The information for accessing the whiteboard refers to a communication destination for the terminal device 10 or the like to display (identify) the whiteboard. In this embodiment, it is described by the term of the URL of the whiteboard. The IP address and port number of the whiteboard may be used. Instead of identifying the whiteboard by IP address alone, the whiteboard may be identified by adding the directory name to one or more fixed IP addresses. Part or all of the information for accessing the whiteboard such as the directory name may be a user ID, a conference date and time, a conference room ID, a conference name, a whiteboard ID, or a combination thereof.

The screen of the whiteboard can be displayed by accessing the URL of the whiteboard by the terminal device 10. By displaying the whiteboard screen, participants can start using the whiteboard. Note that access means communicating and connecting.

<System configuration example>
FIG. 2 shows an example of a schematic configuration diagram of the communication system 1. The communication system 1 has a WB system 40, a conference reservation system 50, a schedule management system 60, a user terminal 30 (participant terminal or organizer terminal), and a terminal device 10 connected via the Internet i. ing. The user terminal 30 and the terminal device 10 are arranged in an in-house network such as a LAN as an example. However, the user terminal 30 can be connected to the Internet i from a mobile phone network or the like without going through a LAN.

The WB system 40, the conference reservation system 50, and the schedule management system 60 exist on the cloud side and communicate with the user terminal 30 and the terminal device 10 via the Internet i. The WB system 40, the conference reservation system 50, and the schedule management system 60 may actually be built in a data center or the like.

The configuration shown in FIG. 2 is only an example, and the WB system 40, the conference reservation system 50, and the schedule management system 60 may all be arranged in the in-house network, and one or more of them may be in the in-house network. It may be arranged in.

The schedule management system 60 is, for example, one or more information processing devices that manage the schedule of an arbitrary user on the cloud. The schedule management system 60 provides a service for managing a user's schedule. One of the management of this schedule includes the management of the reservation of the conference room 9. As the schedule management system 60, Google Calendar (registered trademark), Office365 (registered trademark) and the like are known. The schedule management system 60 may be any as long as it satisfies the technical specifications.

The conference reservation system 50 is one or more information processing devices that manage the use of the conference room 9 and reservation information. First, the conference reservation system 50 acquires the reservation information of the conference room 9 reserved in the schedule management system 60 from the schedule management system 60. The conference reservation system 50 does not need to use an external schedule management system 60, and the conference reservation system 50 may also use the schedule management system 60. One of the reasons why the external schedule management system 60 is used in this embodiment is that the development cost can be suppressed by using the external schedule management system 60.

The conference reservation system 50 communicates with one or more terminal devices 10 arranged in each conference room 9, and transmits, for example, reservation information of the day to the terminal device 10. The reservation information is updated regularly, and the status indicating the status of the meeting is managed for each meeting. For example, it manages from check-in to check-out.

The WB system 40 is a Web server (Web server) that acquires strokes handwritten by a participant on the terminal device 10 from the terminal device 10 and further transmits screen information including drawing image data generated from one or more strokes to the terminal device 10. Or one or more information processing devices having a function as an HTTP server). The WB system 40 provides a service that allows users to use the functions of the whiteboard. The screen information is described in HTML, a script language, CSS (Cascade Style Sheet), etc., and is provided as a Web page generated by the WB system 40. By executing the Web application, the terminal device 10 and the WB system 40 enable the participant to use the terminal device 10 like an electronic blackboard (whiteboard). A web application is software that operates by coordinating a program in a script language (for example, JavaScript (registered trademark)) that operates on a browser application and a program on the web server side, and is used on the browser or its mechanism. To tell.

In this embodiment, the Web application provided by the WB system 40 is referred to as a whiteboard application. The whiteboard application can be used as long as the terminal device 10 operates the browser application. The whiteboard or electronic blackboard may be referred to as an electronic information board, an electronic whiteboard, a copy board, an electronic board, or the like. The whiteboard may be realized by a projector and a whiteboard (a normal blackboard type without a display) in addition to a type that captures strokes handwritten by a touch panel.

The conference reservation system 50 may have the function of at least one of the schedule management system 60 and the WB system 40. The schedule management system 60 and the WB system 40 may be integrated and provided as one service. Further, even if the conference reservation system 50, the schedule management system 60, and the WB system 40 are provided as separate services, the three services may be realized by one or two devices, or realized by different devices. One service may be realized by two or more devices.

The terminal device 10 of the present embodiment is an information processing device having three functions. That is, the function related to the use of the conference room 9, the function related to the whiteboard, and the function of the browser. These are provided by separate application software as an example. First, the terminal device 10 serves as a user interface for participants to the conference reservation system 50 in each conference room 9. For example, the terminal device 10 acquires reservation information regarding the reservation of the conference room 9 from the conference reservation system 50 by transmitting the identification information of the conference room 9 managed by itself, and the latest conference or the day of the conference room 9. Display the reservation status of. The terminal device 10 displays the information transmitted from the conference reservation system 50 by the application software on the display device.

Further, the terminal device 10 has a function of accepting a check-in operation by a participant into the conference room 9 and causing the participant to check in into the conference room 9. When the participant performs the check-in operation (input of the reservation ID described later), the conference reservation system 50 is notified of the check-in request including the reservation ID. The conference reservation system 50 authenticates the check-in request, and if the authentication is successful, the check-in is permitted.

The functions related to the whiteboard cooperate with the functions of the browser so that the participants can use the terminal device 10 as the whiteboard. For example, it accepts a user's operation or causes a browser to communicate with the WB system 40.

Further, the terminal device 10 has a browser, and can display a Web page transmitted from a general Web server and execute a Web application. It is the browser that displays the screen information transmitted by the WB system 40.

The terminal device 10 is a general information processing device such as a smartphone, a tablet device, and a notebook PC (Personal Computer). Any information processing device having a communication function, a display function, and an input function may be used. Further, the terminal device 10 may be one or more of an electronic blackboard, a video conference terminal, or a projector.

The user terminal 30 is an information processing device brought into the conference room 9 by the user of the communication system 1. However, it is not always necessary to bring it to the conference room 9. Here, the user is mainly a participant, but may be a conference organizer and a mere participant. The conference organizer is the person who booked the conference. However, there is no need to make a strict distinction between conference organizers and mere participants. The user terminal 30 used by the conference organizer may be referred to as an organizer terminal, and the user terminal 30 used by a mere participant may be referred to as a participant terminal.

The user terminal 30 is a general information processing device such as a smartphone, a tablet device, or a notebook PC. In the present embodiment, any information processing device may be used as long as the browser operates.

<Hardware configuration example>
Next, the hardware configurations of the WB system 40, the conference reservation system 50, the schedule management system 60, the user terminal 30, and the terminal device 10 in the communication system 1 of the present embodiment will be described.

<< Hardware configuration example of WB system, conference reservation system, schedule management system, user terminal, and terminal device >>
The WB system 40, the conference reservation system 50, the schedule management system 60, the user terminal 30, and the terminal device 10 are realized by, for example, a computer system having a hardware configuration shown in FIG. FIG. 3 is a hardware configuration diagram of an example of the computer system 100 according to the present embodiment.

The computer system 100 shown in FIG. 3 includes an input device 201, a display device 202, an external I / F 203, a RAM (Random Access Memory) 204, a ROM (Read Only Memory) 205, a CPU (Central Processing Unit) 206, and a communication I /. It includes an F207, an HDD (Hard Disk Drive) 208, and the like, and each is connected to each other by a bus B.

The input device 201 includes a keyboard, a mouse, a touch panel, and the like, and is used by the user to input each operation signal. The display device 202 includes a display and the like, and displays the processing result by the computer system 100.

The communication I / F 207 is an interface for connecting the computer system 100 to an in-house network, the Internet, and the like. As a result, the computer system 100 can perform data communication via the communication I / F 207.

The HDD 208 is a non-volatile storage device that stores programs and data. The stored programs and data include, for example, an OS (Operating System) which is basic software for controlling the entire computer system 100, application software which provides various functions on the OS, and the like. The HDD 208 manages the stored programs and data by a predetermined file system and / or a DB (database).

The external I / F 203 is an interface with an external device. The external device includes a recording medium 203a and the like. As a result, the computer system 100 can read and / or write to the recording medium 203a via the external I / F 203. The recording medium 203a includes a flexible disk, a CD (Compact Disk), a DVD (Digital Versatile Disk), an SD memory card (SD Memory card), a USB memory (Universal Serial Bus memory), and the like.

The ROM 205 is a non-volatile semiconductor memory (storage device) capable of holding programs and data even when the power is turned off. The ROM 205 stores programs and data such as BIOS (Basic Input / Output System), OS settings, and network settings that are executed when the computer system 100 is started. The RAM 204 is a volatile semiconductor memory (storage device) that temporarily holds programs and data.

The CPU 206 is an arithmetic unit that realizes control and functions of the entire computer system 100 by reading programs and data from a storage device such as the ROM 205 and the HDD 208 onto the RAM 204 and executing processing.

The WB system 40, the conference reservation system 50, and the schedule management system 60 are preferably compatible with cloud computing. Cloud computing refers to a usage mode in which resources on a network are used without being aware of specific hardware resources.

<About functions>
Next, the functions of the WB system 40, the conference reservation system 50, the schedule management system 60, the user terminal 30, and the terminal device 10 will be described with reference to FIG. FIG. 4 is an example of a functional block diagram showing the functions of the WB system 40, the conference reservation system 50, the schedule management system 60, the user terminal 30, and the terminal device 10 in a block shape.

<< User terminal functions >>
The user terminal 30 has a first display control unit 31, a first operation reception unit 32, and a first communication unit 33. Each of these functional units possessed by the user terminal 30 is a function realized by operating any of the components shown in FIG. 3 by a command from the CPU 206 according to a program expanded from the HDD 208 to the RAM 204. It is a means. This program is distributed from a server for program distribution or stored in a storage medium.

The first communication unit 33 mainly transmits and receives various information to and from the schedule management system 60 and the WB system 40. In the present embodiment, the reservation information of the conference room 9 is registered in the schedule management system 60, and the URL of the whiteboard is acquired from the schedule management system 60. In addition, the URL of the whiteboard is specified to communicate with the WB system 40, and screen information including drawing image data is received.

The first display control unit 31 displays various screens on the display device 202. For example, the screen information received by the first communication unit 33 is analyzed and a reservation screen or a Web page serving as a whiteboard is displayed on the display device 202.

The first operation receiving unit 32 receives various operations of the user with respect to the user terminal 30. For example, it accepts operations such as pressing a button displayed on a menu, inputting characters, and scrolling the screen.

It should be noted that these functions possessed by the user terminal 30 may be provided by the browser analyzing and executing the screen information transmitted from the schedule management system 60 and the WB system 40.

<< Functions of WB system >>
The WB system 40 has a WB creating unit 41, a third communication unit 42, and a WB providing unit 43. Each of these functional units included in the WB system 40 has a function realized by operating any of the components shown in FIG. 3 by an instruction from the CPU 206 according to a program expanded from the HDD 208 to the RAM 204. It is a means. This program is distributed from a server for program distribution or stored in a storage medium. Further, the WB system 40 has a WB object DB 44 held in a RAM 204, an HDD 208, or the like.

The third communication unit 42 mainly transmits and receives various information to and from the conference reservation system 50 and the terminal device 10. In the present embodiment, a whiteboard creation request is received from the conference reservation system 50, a whiteboard URL is returned, coordinate data constituting a stroke is received from the terminal device 10, and drawing image data created from the stroke is included. Provides screen information for the whiteboard.

The WB creation unit 41 creates a whiteboard. For example, when there is a request from the conference reservation system 50 to create a new whiteboard, the whiteboard is created. For ease of explanation, assuming that one URL corresponds to one whiteboard, a new URL is assigned to the whiteboard. Creating a whiteboard means accepting stroke writing and preparing screen information having functions such as distribution of drawn image data. A template of such screen information (sometimes called a Web application) is created in advance, and this is copied and assigned to the URL of the whiteboard.

The WB provider 43 generates screen information for the whiteboard. The WB provider 43 manages data for each whiteboard. Since the data is data displayed on the whiteboard, for example, drawing image data composed of strokes, text, menus, image data pasted on the whiteboard, and the like. These contents and display positions are managed by the WB object DB 44 for each whiteboard.

The WB providing unit 43 generates screen information using the managed object. For example, when a plurality of strokes overlap, the plurality of strokes are combined into one object to generate drawing image data. This will improve the quality of the image for enlargement, reduction, rotation, etc.

There is a Canvas element as an HTML element suitable for providing a whiteboard as screen information. The Canvas element is used to draw a figure or the like by scripting with JavaScript (registered trademark). The WB providing unit 43 updates the screen information every time data such as handwriting is added.

When a remote conference is being held, the third communication unit 42 notifies each terminal device 10 connected to the URL of the whiteboard of the update when the screen information is updated. Since the terminal device 10 goes to the URL of the whiteboard to get the screen information, the data displayed on the screen of the whiteboard can be shared in almost real time.

<< Functions of schedule management system >>
The schedule management system 60 includes a fifth communication unit 61, a reservation information registration reception unit 62, and a URL registration reception unit 63. Each of these functional units included in the schedule management system 60 is a function realized by operating any of the components shown in FIG. 3 by an instruction from the CPU 206 according to a program expanded from the HDD 208 to the RAM 204. Or it is a means. This program is distributed from a server for program distribution or stored in a storage medium. Further, the schedule management system 60 has a reservation information DB 64 held in the HDD 208, the RAM 204, or the like.

The fifth communication unit 61 mainly transmits and receives various information to and from the user terminal 30 and the conference reservation system 50. In the present embodiment, the reservation information regarding the reservation of the conference room 9 is acquired from the user terminal 30, and the reservation information is transmitted to the conference reservation system 50.

The reservation information registration reception unit 62 acquires reservation information regarding the reservation of the conference room 9 from the user terminal 30 and registers it in the reservation information DB. Further, the URL registration reception unit 63 acquires the URL of the whiteboard from the conference reservation system 50 and registers it in association with the reservation information.

<< Functions of the conference reservation system >>
The conference reservation system 50 includes a conference room management unit 51, a fourth communication unit 52, a WB creation instruction unit 53, a reservation ID generation unit 54, a reservation information acquisition unit 55, and a URL registration unit 56. Each of these functional units included in the conference reservation system 50 is a function realized by operating any of the components shown in FIG. 3 by a command from the CPU 206 according to a program expanded from the HDD 208 to the RAM 204. Or it is a means. This program is distributed from a server for program distribution or stored in a storage medium. Further, the conference reservation system 50 has a reservation information DB 57 held in the HDD 208, the RAM 204, or the like.

The fourth communication unit 52 mainly transmits and receives various data to and from the terminal device 10, the schedule management system 60, and the WB system 40. In the present embodiment, at least the reservation information of the day is transmitted to the terminal device 10, and the check-in request is received from the terminal device 10. Further, the URL of the whiteboard is acquired from the WB system 40, and the URL of the whiteboard is transmitted to the schedule management system 60.

The reservation information acquisition unit 55 acquires reservation information from the schedule management system 60. Since the reservation information of each company of the schedule management system 60 is registered, the reservation information acquisition unit 55 logs in by designating the account (user name and password) of the schedule management system 60 registered in advance for each company, and logs in to this. Acquire the reservation information registered in association with the account having the domain included in the account. For example, if the user name of the account in the schedule management system 60 registered in advance for each company is "a@xfood.com", the reservation registered in the account "xxx@xfood.com" (xxx is optional). Get information.

The reservation information acquisition unit 55 receives a notification at the timing when new reservation information is registered in the schedule management system 60, and goes to the schedule management system 60 to obtain the reservation information. Alternatively, the reservation information acquisition unit 55 may periodically (for example, once an hour, etc.) go to the schedule management system 60 to acquire the reservation information.

The reservation information acquired by the reservation information acquisition unit 55 is stored in the reservation information DB 57. The reservation information will be described later. Further, in the present embodiment, the reservation information DB 64 of the schedule management system 60 and the reservation information DB 57 of the conference reservation system 50 are handled without particular distinction. Actually, there is a possibility that the two are different depending on the information for managing the reservation information and the like, but it is assumed that there is no problem in the explanation of the present embodiment.

The reservation ID generation unit 54 generates (numbers) a reservation ID that does not overlap with the reservation information acquired by the reservation information acquisition unit 55. The reservation ID is also set in the reservation information of the schedule management system 60. Therefore, the reservation ID can be confirmed by the user terminal 30 communicating with the schedule management system 60. The conference organizer or participants (either one is fine) check in with this reservation ID.

Upon receiving the check-in request from the terminal device 10, the conference room management unit 51 determines whether or not the participant can be checked in by authenticating with the reservation ID or the like (whether or not the use of the conference room can be permitted). .. If it is determined that check-in is possible, the status of the reservation information in the reservation information DB 57 is updated to checked-in. The status is, for example, check-in impossible, check-in possible, check-in completed, and the like.

The WB creation instruction unit 53 requests the WB system 40 to create a whiteboard. The timing of creating the whiteboard may be between the registration of the reservation information and the end of the meeting. By creating the whiteboard, the WB creation instruction unit 53 acquires the URL of the whiteboard from the WB system 40.

The URL registration unit 56 transmits the URL of the whiteboard acquired by the WB creation instruction unit 53 to the schedule management system 60, and registers the URL in association with the reservation information.

<< Terminal device >>
The terminal device 10 includes a second display control unit 11, a second operation reception unit 12, a browser unit 13, a conference reservation client unit 14, a second communication unit 15, and a WB client unit 16. Each of these functional units included in the terminal device 10 has a function or a function realized by operating any of the components shown in FIG. 3 by a command from the CPU 206 according to a program expanded from the HDD 208 to the RAM 204. It is a means. This program is distributed from a server for program distribution or stored in a storage medium.

The second communication unit 15 mainly transmits and receives various information to and from the conference reservation system 50 and the WB system 40. In the present embodiment, one's own conference room 9 is designated by identification information or the like, the reservation information of the conference room 9 is requested from the conference reservation system 50, and the reservation information is received. In addition, the screen information of the whiteboard is acquired from the WB system 40.

The second display control unit 11 displays various screens on the display device 202. For example, the reservation information received by the second communication unit 15 is displayed on the display device 202, and the screen information of the whiteboard is analyzed to display the Web page functioning as the whiteboard on the display device 202.

The second operation reception unit 12 receives various operations of the participants with respect to the terminal device 10. For example, it accepts check-in operations (input of reservation ID), check-out operations, and the like.

The conference reservation client unit 14 is a client application of the conference reservation system 50, and notifies check-in and check-out via the second communication unit 15.

The WB client unit 16 requests the conference reservation client unit 14 for the URL of the whiteboard in response to the operation of using the whiteboard by the user, and notifies the browser unit 13 of the acquired URL of the whiteboard. It mediates between the conference reservation client unit 14 and the browser unit 13.

The browser unit 13 has the same function as general browser software, and makes the terminal device 10 function as a whiteboard by communicating with the WB system 40 using the URL of the whiteboard as a communication destination.

<Registration of reservation information>
The reservation and the reservation information of the conference room 9 will be described with reference to FIG. 5 (a) is an example of the conference room reservation screen 501, FIG. 5 (b) shows an example of reservation information transmitted to the conference reservation system 50, and FIG. 5 (c) is stored in the reservation information DB 57. This is an example of reserved information.

As shown in FIG. 5A, the conference room reservation screen 501 has a conference name column 502, a place column 503, a time column 504, a participant column 505, an OK button 506, and a cancel button 507. The name, title, agenda, etc. of the conference are set in the conference name column 502. The name of the conference room 9 or the like is set in the place column 503. Since the conference room 9 that can be used for each company is registered in the schedule management system 60 in advance, the conference organizer sets the conference room 9 by selecting the conference room 9. In the time column 504, the conference start time (reservation start time) and the conference end time when the conference room 9 is reserved are set. The date is omitted. Participants of the conference are set in the participant column 505.

As shown in FIG. 5B, the reservation information input in this way is transmitted and received between the communication systems 1 as data in the character string format. Although FIG. 5B shows a JSON format, it may be an XML format, a CSV format, or the like.

When the conference room 9 is reserved by the conference room reservation screen 501, the reservation information as shown in FIG. 5C is registered in the schedule management system 60 and the conference reservation system 50. In FIG. 5 (c), the time zone and the participants are registered in association with the conference room name. Other information such as the status of the conference room 9 is also included in the reservation information, but is omitted in FIG.

<Flow of operation>
Next, a procedure for creating a whiteboard in the communication system 1 will be described with reference to FIG. FIG. 6 is an example of a flowchart showing a procedure in which the communication system 1 creates and displays a whiteboard.

S1: The conference organizer operates the organizer terminal to communicate the organizer terminal with the schedule management system 60, and performs an operation of reserving the conference room 9. The conference organizer also inputs the operation to create a new whiteboard. When a new whiteboard is automatically created by the reservation of the conference room 9, the operation of creating a new whiteboard is unnecessary.

S1.1: The first operation reception unit 32 of the organizer terminal accepts the operation of the organizer, and the first communication unit 33 transmits various information for reserving the conference room 9. As described in FIG. 5, the conference room 9, the participants, and the time zone are transmitted. In addition, it sends a request to create a whiteboard. The fifth communication unit 61 of the schedule management system 60 receives these, and the reservation information registration reception unit 62 registers the reservation information in the reservation information DB 64.

S2: The reservation information acquisition unit 55 of the conference reservation system 50 inquires of the schedule management system 60 for new reservation information. Inquire regularly, for example by polling. In response to this, the reservation information acquisition unit 55 acquires reservation information.

S3: The WB creation instruction unit 53 of the conference reservation system 50 requests the WB system 40 to create a whiteboard because the reservation information includes a whiteboard creation request. The third communication unit 42 of the WB system 40 receives the whiteboard creation request, and the WB creation unit 41 creates a new whiteboard at a new URL. The fifth communication unit 61 transmits the URL of this whiteboard to the conference reservation system 50. The URL of the whiteboard may be sent to each participant by e-mail.

S4: The fourth communication unit 52 of the conference reservation system 50 receives the URL of the whiteboard. Further, the reservation ID generation unit 54 generates (numbers) the reservation ID. The reservation ID may be generated when the reservation information is received.

S5: Since the URL of the whiteboard has been received, the URL registration unit 56 of the conference reservation system 50 requests the schedule management system 60 to register the URL of the whiteboard and the reservation ID by designating the conference room 9 and the date and time. Instead of using the conference room 9 and the date and time as keys, some identification information that uniquely identifies the reservation of the conference room 9 may be used as a key. By registering the URL of the whiteboard in the schedule management system 60 in this way, necessary information can be centrally managed in the conference room.

When the conference reservation system 50 also serves as the schedule management system 60, when the reservation information is registered in the conference reservation system 50, the WB creation instruction unit 53 requests the WB system 40 to create a whiteboard.

S6: As described above, the URL of the whiteboard and the reservation ID are registered in the schedule management system 60, so that the conference organizer can confirm the reservation ID required for check-in. The conference organizer inputs the operation of viewing the reservation information by designating the conference room 9 and the date and time to the organizer terminal.

S6.1: The first operation reception unit 32 of the organizer terminal accepts the operation, and the first communication unit 33 specifies the conference room 9 and the date and time, and requests the reservation information from the schedule management system 60. The fifth communication unit 61 of the schedule management system 60 receives the request for the reservation information, acquires the reservation information specified by the conference room 9 and the date and time from the reservation information DB 64, and transmits the reservation information to the organizer terminal.

The first communication unit 33 of the organizer terminal receives the reservation information, and the first display control unit 31 displays the reservation information on the display device 202. FIG. 7 shows an example of the displayed reservation information. This allows the conference organizer to confirm the reservation ID and the URL of the whiteboard.

Next, the processing at the start of the conference will be described.
S7: The conference organizer goes to the conference room 9 and performs a check-in operation (input of a reservation ID) for the terminal device 10. Participants can also check in. An example of the check-in screen is shown in FIG.

S7.1: The second operation reception unit 12 of the terminal device 10 accepts the input of the reservation ID as an operation required for check-in, and the conference reservation client unit 14 of the terminal device 10 checks including the conference room name, the date and time, and the reservation ID. The in-request is sent to the conference reservation system 50. The fourth communication unit 52 of the conference reservation system 50 receives the check-in request, and the conference room management unit 51 determines whether or not the check-in is successful. That is, it is determined whether or not the check-in is successful depending on whether or not the reservation ID of the reservation information specified by the conference room name and the date and time matches the reservation ID transmitted from the terminal device 10. It is assumed that the explanation of FIG. 6 is successful. Instead of using the conference room 9 and the date and time as keys, some identification information that uniquely identifies the reservation of the conference room 9 may be used as a key. The same applies to the subsequent processing.

S8: Since the conference organizer uses the whiteboard, press the icon to activate the whiteboard. If the check-in is successful, such an icon is displayed on the terminal device 10. If the check-in is successful, the following processing (steps S8.1 to S8.2.1) may be performed without accepting the user to press the icon for activating the whiteboard.

S8.1: The second operation reception unit 12 of the terminal device 10 accepts the activation of the whiteboard, and the WB client unit 16 specifies the conference room name and the date and time of the conference where the check-in is successful, and reserves the URL of the whiteboard. Request to system 50.

The request for the URL of the whiteboard may be made directly from the terminal device 10 to the conference reservation system 50 as in step S8.1. You may also get the URL of the whiteboard as follows. First, when a check-in request is made from the terminal device 10 to the conference reservation system 50 in step S7.1, the whiteboard URL received by the conference reservation system 50 from the schedule management system 60 is successfully checked in. It is transmitted to the terminal device 10 together with the notification. The timing at which the conference reservation system 50 receives the URL of the whiteboard from the schedule management system 60 may be received in advance, or may be acquired at the timing when the check-in request is received. Next, the terminal device 10 activates the whiteboard using the URL of the whiteboard stored when the user requests the activation of the whiteboard (pressing the icon).

S8.1.1: The fourth communication unit 52 of the conference reservation system 50 receives the request for the whiteboard URL, and the reservation information acquisition unit 55 specifies the conference room name and date and time of the conference and schedules the whiteboard URL. Request to 60.

The fifth communication unit 61 of the schedule management system 60 receives the request for the URL of the whiteboard, and reads out the URL of the whiteboard of the reservation information specified by the conference room name and the date and time from the reservation information DB 64. The fifth communication unit 61 transmits the URL of the whiteboard to the conference reservation system 50. The fourth communication unit 52 of the conference reservation system 50 receives the URL of the whiteboard and transmits it to the terminal device 10.

In step S8.1, the conference reservation system 50 requests the schedule management system 60 for the URL of the whiteboard, but the conference reservation system 50 transmits the URL of the whiteboard acquired in step S7.1 to the terminal device 10. You may. If the conference reservation system 50 acquires the URL of the whiteboard from the schedule management system 60, the conference reservation system 50 does not need to hold the URL of the whiteboard, and if the conference reservation system 50 holds the URL, the communication time can be shortened.

S8.2: The second communication unit 15 of the terminal device 10 receives the URL of the whiteboard, and the WB client unit 16 sends the URL of the whiteboard to the browser unit 13.

S8.2.1: The browser unit 13 accesses the URL of the whiteboard. As a result, the browser unit 13 of the terminal device 10 can display the whiteboard created in step S3. FIG. 9 shows an example of the initial screen of the whiteboard.

S9: The conference organizer can handwrite on the whiteboard screen displayed by the browser unit 13.

S9.1: The second operation reception unit 12 of the terminal device 10 accepts handwriting, and the WB client unit 16 transmits the handwritten content to the WB system 40.

S10: When the conference is completed, the conference organizer performs a checkout operation on the terminal device 10. Participants can also check out. The second operation reception unit 12 of the terminal device 10 accepts the checkout, and the conference reservation client unit 14 notifies the conference reservation system 50 of the checkout.

Next, the process of viewing the whiteboard by the participants after the meeting will be described.

S11: The participant inputs an operation for confirming the whiteboard (for example, specifying the conference room 9 and the date and time) to the participant terminal.

S11.1: The first operation reception unit 32 of the participant terminal accepts the operation, and the first communication unit 33 communicates with the conference room 9 by designating the date and time and communicates with the schedule management system 60. Since the URL of the whiteboard is registered in the reservation information managed by the schedule management system 60, the fifth communication unit 61 of the schedule management system 60 transmits the URL of the whiteboard to the participant terminal. This allows participants to know the URL of the whiteboard. The screen displayed by the terminal device 10 in step S11.1 may be the same as in FIG. 7. FIG. 7 is a screen for confirming the reservation, but the information registered after the meeting is almost the same.

S12: Participants press the URL of the whiteboard.

S12.1: The first operation reception unit 32 of the participant terminal accepts the operation, and the first communication unit 33 communicates with the WB system 40 using the URL of the whiteboard as the communication destination. The WB provider 43 of the WB system 40 identifies an object by the URL of the whiteboard, generates screen information using the object, and sends it to the participant terminal. As described above, since the URL of the whiteboard is registered in the schedule management system 60 in the present embodiment, the participants can display the drawing information of the whiteboard after the meeting.

In the process of FIG. 6, the terminal device 10 acquires the whiteboard URL from the conference reservation system 50, but the terminal device 10 itself that accepts check-in does not display the whiteboard, and the terminal device 10 is in the conference room. The whiteboard URL may be transmitted to another device (eg, an electronic blackboard, a display, etc.) and the other device may display the whiteboard (access the WB system 40).

<Screen example>
<< Reservation information including reservation ID and whiteboard URL >>
FIG. 7 shows an example of the reservation information confirmation screen 511 displayed by the organizer terminal in step S6.1 of FIG. FIG. 7 mainly describes the difference from FIG. 5 (a). The meeting name column 512, the place column 513, the time column 514, and the participant column 515 may be the same as in FIG. 5A.

Since the reservation ID and the URL of the whiteboard are registered in the schedule management system 60, the reservation information has the reservation ID column 516 and the URL column 517 of the whiteboard. In this way, the conference organizer and the like can acquire the reservation ID and the URL of the whiteboard from the schedule management system 60.

The reservation information confirmation screen 511 has a reservation deletion button 518. When the reservation deletion button 518 is pressed, the schedule management system 60 deletes the reservation information. Further, the conference reservation system 50 is notified that the reservation information has been deleted. Such a mechanism is called reservation cancellation. When the reservation information is confirmed, the OK button 519 is pressed.

<< Check-in screen >>
FIG. 8 is an example of the check-in screen 521 displayed by the terminal device 10 in step S7 of FIG. The check-in screen 521 is a screen that waits for the check-in of the next conference with respect to the current time. For example, it has a conference name field 522 and a reservation ID input field 523. When the conference organizer goes to the conference room 9, the conference name is confirmed on such a check-in screen 521, and the reservation ID is input in the reservation ID input field 523. When the OK button 524 is pressed, the terminal device 10 transmits a check-in request including the reservation ID to the conference reservation system 50.

<< Initial screen of whiteboard >>
FIG. 9 shows an example of the initial screen 531 of the whiteboard displayed in step S8.2 of FIG. The initial screen 531 of the whiteboard has a URL display field 532, a board name field 533, a reservation information field 534, a menu field 535, and the like. The URL of the whiteboard is displayed in the URL display field 532. Participants and the like can enter any name (for example, conference name) in the board name field 533. In the reservation information field 534, for example, the participant name and the meeting time are displayed. The information in the reservation information column 534 is the information transmitted from the terminal device 10 or the conference reservation system 50 by the WB system 40 in step S8.2.1 or S3 of FIG. The menu column 535 has one or more buttons for the participant to set the color and thickness of the stroke.

Participants can arbitrarily handwrite on the initial screen 531 of such a whiteboard, and can discuss while looking at the same information as other participants.

<< Whiteboard end screen >>
FIG. 10 shows an example of the end reception column 541 of the whiteboard. In the description of FIG. 10, the difference from FIG. 9 will be described. When the participant presses the predetermined end button, the second operation reception unit 12 accepts the operation, and the WB client unit 16 causes the second display control unit 11 to pop up the end reception column 541. The end reception column 541 displays an end button 542 and a cancel button 543.

When the participant presses the end button 542, the WB client unit 16 notifies the WB system 40 of the end of the whiteboard via the browser unit 13. Further, the conference reservation client unit 14 receives the notification of the end of the whiteboard from the WB client unit 16 and notifies the conference reservation system 50 of the check-out of the conference room 9. Therefore, participants do not need to perform a checkout operation separately from the end of the whiteboard.

<Example of starting a whiteboard>
In the procedure of FIG. 6, the conference organizer performed an explicit operation to start the whiteboard after check-in. However, even without such an operation, the terminal device 10 can automatically start the whiteboard. This eliminates the need to start the whiteboard upon successful check-in.

FIG. 11 is an example of a sequence diagram showing a procedure in which the communication system 1 creates and displays a whiteboard. In the description of FIG. 11, the difference from FIG. 6 will be mainly described. The processing from steps S1 to S7.1 is the same as in FIG. However, in FIG. 11, after step S7.1, the terminal device 10 displays the whiteboard.

S7.2: When the check-in is successful, the conference reservation client unit 14 of the terminal device 10 sends the URL of the whiteboard to the browser unit 13.

S7.2.1: The browser unit 13 starts communication with the WB system 40 using the URL of the whiteboard as the communication destination. As a result, the initial screen of the whiteboard as shown in FIG. 9 is displayed as described in step S8.2.1 of FIG. The processing of steps S8 to S9.1 may be the same as that of S11 to S12.1 of FIG.

<About the timing of creating other whiteboards>
In FIGS. 6 and 11, a whiteboard was created at the time of booking the meeting. In addition, the conference reservation system 50 can create a whiteboard at the following timing.
・ Remind before the start of the meeting At the time of response ・ At check-in ・ During the meeting Remind before the start of the meeting is that the meeting reservation system 50 reminds the meeting organizer of the reservation of the meeting room 9 by chat system or e-mail and makes an empty reservation. Is a mechanism to reduce. If there is no change in the schedule of the meeting, the meeting organizer responds to that effect (to hold the meeting). Therefore, the conference reservation system 50 can prevent the created whiteboard from being wasted due to the cancellation of the conference by creating the whiteboard at the time of the remind response before the start of the conference. If the whiteboard is created at the time of reminding, the URL of the whiteboard is transmitted to the terminal device 10 at the time of check-in in the same manner as when the whiteboard is created at the time of registration of the reservation information.

The same effect is obtained at the time of check-in, and the conference reservation system 50 creates a whiteboard only when a conference is actually held, such as at the time of check-in, so that it is possible to reduce unnecessary creation of a whiteboard. If a whiteboard is created at the time of check-in, the URL of the whiteboard is transmitted from the WB system 40 to the conference reservation system 50 at the time of check-in, and is transmitted from the conference reservation system 50 to the terminal device 10.

In addition, the conference reservation system 50 can create a whiteboard during the conference. In this case, the conference organizer or the like inputs an operation to start the whiteboard on the terminal device 10. Such usage can be used when the conference room 9 is not reserved. The creation of the whiteboard during the meeting will be described in Example 2.

FIG. 12A is an example of a flowchart illustrating a process of creating a whiteboard in response to a reminder response. The conference room management unit 51 of the conference reservation system 50 transmits a reminder to the participants before the predetermined time of the conference start time (S101). Reminders may be sent via chat system or email. Reminding is performed together with identification information such as a reservation ID that can identify the reservation information.

The conference room management unit 51 determines whether or not there is a response that the conference will be held as scheduled (S102). Participants will endeavor to respond to either confirmation or cancellation, but if there is no response within the specified time from the transmission of the reminder, the conference room management unit 51 may consider it as cancellation. If the determination in step S102 is No, the process of FIG. 12A ends.

If the determination in step S102 is Yes, the WB creation instruction unit 53 requests the WB system 40 to create a whiteboard (S103).

The URL of the generated whiteboard may be included in the email or chat at the time of reminding. This makes it easy to access the whiteboard from the individual user terminal 30 instead of displaying the whiteboard only by the terminal device 10.

The conference room management unit 51 may remind the user a plurality of times. For example, it may be held three times, one week before the meeting, one day before, and 10 minutes before the meeting. In this case, the URL of the whiteboard may be created at the time of responding to a specific predetermined reminding (second reminding, etc.) (limited to the response of holding a meeting). You may also create a whiteboard when responding to the final reminder. Especially when the whiteboard is created when responding to the final reminding, it is unlikely that the meeting will be canceled, so it is possible to prevent the created whiteboard from being wasted.

FIG. 12B is an example of a flowchart illustrating a process of creating a whiteboard at check-in. The conference room management unit 51 of the conference reservation system 50 receives the check-in request (S201).

The conference room management unit 51 determines whether or not the check-in is successful (S202). If the determination in step S202 is No, the process of FIG. 12B ends. Therefore, no whiteboard is created.

If the determination in step S202 is Yes, the WB creation instruction unit 53 requests the WB system 40 to create a whiteboard (S203).

<Timing to start using other whiteboards>
If the whiteboard has been created, the terminal device 10 can start using the whiteboard at any time.
-At the time of meeting reservation-before the start of the meeting Participants can acquire the URL of the whiteboard registered in the schedule management system 60 from their own user terminal 30 and start using the whiteboard.
-At check-in The conference organizer starts using the whiteboard at the time of check-in to the conference room 9 with the terminal device 10 (explained in FIG. 11).
-During the conference The conference organizer or the like operates the terminal device 10 to instruct the start of the whiteboard.

<Automatic deletion of whiteboard>
Conference room 9 has been reserved, but the reservation may be cancelled. If the created whiteboard remains unused, the unused whiteboard may increase and accumulate, which may put pressure on the resources of the WB system 40. Therefore, in order to release unused resources, the WB system 40 deletes the whiteboard.

If the whiteboard is unused (the initial screen remains), delete the whiteboard at the following timing.
-When canceling a conference reservation-When the reservation time has passed without check-in to the conference room 9 By doing this, unused whiteboards increase and accumulate, which puts pressure on the resources of the WB system 40. Can be suppressed.

FIG. 12C is an example of a flowchart illustrating a process of deleting the whiteboard. The conference room management unit 51 of the conference reservation system 50 determines whether or not the cancellation of the reservation has been received (S301). The cancellation of the reservation may be notified by the response of the reminder, or may be notified from the schedule management system 60 to the conference reservation system 50 by pressing the delete button 518 in FIG. 7.

If the determination in step S301 is Yes, the process proceeds to step S303.

If the determination in step S301 is No, the conference room management unit 51 determines whether or not the conference start time has passed (S302).

If the determination in step S302 is No, the process of FIG. 12C ends. If the determination in step S302 is Yes, the WB creation instruction unit 53 specifies the URL of the whiteboard and requests the WB system 40 to delete the whiteboard. The URL of the whiteboard is acquired by the conference reservation system 50 from the WB system 40 when the whiteboard is created.

<How to share the URL of the whiteboard>
If the information processing device on which the browser operates accesses the URL of the whiteboard, the whiteboard can be displayed, so that the screen of the whiteboard can be shared. Therefore, the browser unit 13 of the terminal device 10 has a mechanism for easily sharing the URL of the whiteboard with, for example, participants.

FIG. 13 is an example of a diagram illustrating a method of sharing a URL of a whiteboard. When a participant or the like presses a predetermined share button on the screen of the whiteboard, the pop-up screen 551 of FIG. 13 is displayed. The browser unit 13 may acquire the pop-up screen 551 from the conference reservation system 50, or may acquire it in advance.

On the pop-up screen 551, the message 552 "If you want to share the whiteboard, please enter the following URL" and the URL 553 of the whiteboard are displayed. Since the URL of the whiteboard is specified in this way, it becomes easy for participants to share the whiteboard.

The following means can be used as a means for sharing.
-Participants manually describe and send the URL of the whiteboard using chat or mailer.
-The conference reservation system 50 uses an information sharing service (chat service, etc.) to transmit to participants and the like.
-Automatically send an e-mail to the participants registered in the schedule management system 60.

Further, instead of simply sharing the URL of the whiteboard, the screen of the whiteboard may be shared as a file (for example, PDF).

<Register the URL of the whiteboard in the participant's schedule>
In the present embodiment, the URL of the whiteboard is registered in the reservation information of the conference room 9, but the terminal device 10 can also register the URL of the whiteboard in the schedule of the participants.

FIG. 14 shows an email address input screen 561 when registering a whiteboard URL in a participant's schedule. When a participant or the like presses a predetermined button on the screen of the whiteboard, the e-mail address input screen 561 of FIG. 14 is displayed. The browser unit 13 pops up the e-mail address input screen 561.

The e-mail address input screen 561 has a message 562 "If you want to register a URL in a participant's schedule, enter an e-mail address" and an e-mail address input field 563. Participants enter the email address of themselves or other participants with whom they want to share the URL of the whiteboard in the email address input field 563. This e-mail address is used as identification information by the conference reservation system 50 to identify the user.

The URL of the whiteboard can be registered in the participant's schedule at the following timing.

[At the time of meeting reservation]
1. 1. The conference organizer registers the participants at the time of booking the conference room 9.
2. 2. The conference reservation system 50 detects that the conference room 9 has been reserved.
3. 3. The conference reservation system 50 acquires the email addresses of the participants of the conference reserved in the email address input field 563.
4. The conference reservation system 50 registers the URL of the whiteboard in the schedule of the participants.

[When pressing the share button while the whiteboard is in use]
1. 1. Participants press the share button on the whiteboard screen.
2. 2. In the e-mail address input field 563, enter the e-mail address of the participant who registers the schedule.
3. 3. The WB system 40 transmits the participant's e-mail address and the URL of the whiteboard to the conference reservation system 50.
4. The conference reservation system 50 transmits the participant's e-mail address and the whiteboard URL to the schedule management system 60, and registers the whiteboard URL in the participant's schedule.

[When pressing the end button on the whiteboard]
1. 1. Participants press the end button on the whiteboard screen.
2. 2. In the e-mail address input field 563, enter the e-mail address of the participant who registers the schedule.
3. 3. The WB system 40 transmits the participant's e-mail address and the URL of the whiteboard to the conference reservation system 50.
4. The conference reservation system 50 transmits the participant's e-mail address and the whiteboard URL to the schedule management system 60, and registers the whiteboard URL in the participant's schedule.

<Summary>
As described above, in the communication system 1 of the present embodiment, when the participant checks in, the terminal device 10 acquires the URL of the whiteboard from the conference reservation system 50 and communicates with the WB system 40 to display the initial screen. Since it is displayed, participants can use the whiteboard by checking in. Further, since the URL of the whiteboard is registered in the schedule management system 60, if the participants obtain the URL of the whiteboard from the schedule management system 60 after the meeting is completed, the handwritten information displayed by the terminal device 10 during the meeting is obtained. Etc. can be displayed on your participant terminal again.

In this embodiment, when the conference room 9 is not reserved in the schedule management system 60 but the conference starts, how to start the whiteboard will be described. For example, in the case of a sudden meeting, the meeting may be held without making a reservation for the meeting. Even in such a case, the conference reservation system 50 can start the whiteboard.

The function of the communication system 1 of this embodiment will be described with reference to FIG. FIG. 15 is an example of a functional block diagram showing the functions of the WB system 40, the conference reservation system 50, the schedule management system 60, the user terminal 30, and the terminal device 10 in a block shape. In the description of FIG. 15, the difference from FIG. 4 will be described.

The difference in this embodiment is that the terminal device 10 has the WB creation instruction unit 53 instead of the conference reservation system 50. The function of the WB creation instruction unit 53 may be the same as that of the first embodiment.

FIG. 16 is an example of a sequence diagram showing a procedure in which the communication system 1 creates and displays a whiteboard. In the description of FIG. 16, the difference from FIG. 11 will be mainly described. The processing from step S1 to S1.2.1 is the same as that of steps S7 to S7.2.1 in FIG. However, in FIG. 16, since the conference room 9 is not reserved, there is no need to check in. Therefore, in step S1, the conference organizer presses the icon for activating the whiteboard. The second operation reception unit 12 of the terminal device 10 accepts the activation of the whiteboard. Then, in step S2, the WB creation instruction unit 53 requests the WB system 40 to create a whiteboard. As a result, the terminal device can acquire the URL of the whiteboard.

Steps S2 and S2.1 in FIG. 16 are step S9 in FIG. Same as S9.1.

S3: The conference organizer inputs an operation to end the whiteboard to the terminal device 10.

S3.1: The second operation reception unit 12 of the terminal device 10 accepts the operation of terminating the whiteboard, and the WB client unit 16 notifies the conference reservation client unit 14 of the URL of the whiteboard.

S3.2: The WB client unit 16 notifies the conference reservation client unit 14 of the checkout in response to the operation of terminating the whiteboard.

S3.2.1: The conference reservation client unit 14 requests the conference reservation system 50 to register the URL of the whiteboard in the schedule management system 60. At this time, the conference room name and date and time of the conference are specified. The registration of the URL of the whiteboard in the schedule management system 60 is not limited to the end of the meeting, and may be performed at the start of the whiteboard. For example, when the conference room is not reserved as in the process of FIG. 16, and the mechanism is such that some action (operation to start using the conference room, check-in, etc.) is performed at the start of the conference, this is the case. The URL of the whiteboard may be registered in the schedule management system 60 according to the action.

S3.2.1.1: The fourth communication unit 52 of the conference reservation system 50 receives the URL of the whiteboard, etc., and the URL registration unit 56 specifies the conference room name and the date and time of the conference, and the schedule management system 60 is connected to the whiteboard. Request URL registration.

Steps S4 to S5.1 may be the same as steps S8 to S9.1 in FIG.

<Summary>
As described above, in the communication system 1 of the present embodiment, the conference reservation system 50 can start the whiteboard even if the conference is suddenly held. Further, when the participant finishes the meeting, the URL of the whiteboard is registered in the schedule management system 60. Therefore, after the meeting is finished, the participant can display the screen of the whiteboard used in the meeting from the schedule management system 60. can.

In the first and second embodiments, the terminal device 10 executes two applications, the conference reservation client unit 14 and the WB client unit 16, but in this embodiment, the terminal device (hereinafter, the conference room) that executes the conference reservation client unit 14 The communication system 1 in which the terminal device (WB terminal 10A) that executes the WB client unit 16 (referred to as the terminal 10B) is another device will be described. Another device means that the housing is separated.

FIG. 17 is an example of a schematic configuration diagram of the communication system 1 of this embodiment. In the description of FIG. 17, the difference from FIG. 2 will be mainly described. In FIG. 17, the WB terminal 10A and the conference room terminal 10B are connected to the Internet i, respectively.

Similar to the terminal device 10, the WB terminal 10A and the conference room terminal 10B are general information processing devices such as a smartphone, a tablet device, and a notebook PC (Personal Computer). Any information processing device having a communication function, a display function, and an input function may be used. The WB terminal 10A may be composed of an electronic blackboard, a video conference terminal, or a device having a whiteboard function such as a projector.

FIG. 18 is an example of a diagram illustrating a communication path between systems or terminals of communication system 1. As shown in FIG. 18, in this embodiment, the user terminal 30 and the WB terminal 10A communicate with the WB system 40, and the conference room terminal 10B communicates with the conference reservation system 50. Further, the WB terminal 10A and the conference room terminal 10B communicate with each other. Further, the conference reservation system 50 communicates with the schedule management system 60. Although the WB system 40 and the conference reservation system 50 do not communicate in FIG. 18, they may be able to communicate in the same manner as in the first embodiment.

In the first and second embodiments, the conference reservation client unit 14 and the WB client unit 16 in the terminal device 10 cooperate (communicate) in the terminal device 10, but in this embodiment, the WB terminal 10A and the conference room terminal 10B are networks. Communicate via. The network is, for example, a LAN, and in the case of a wireless LAN, communication is performed via an access point. In the case of a wired LAN, communication is performed via a hub or router. In the case of wireless LAN, communication may be performed by a peer-to-peer method such as direct Wi-Fi. In addition, communication may be performed by Bluetooth (registered trademark).

In this embodiment, the communication system 1 in which the WB client unit 16 can display the reservation information managed by the conference reservation system 50 on the whiteboard will be described using the configuration of the communication system 1 of FIGS. 17 and 18. The configuration in which the WB terminal 10A and the conference room terminal 10B communicate with each other as shown in FIG. 18 can also be applied to the first and second embodiments.

<About functions>
FIG. 19 is an example of a functional block diagram showing the functions of the WB system 40, the conference reservation system 50, the schedule management system 60, the user terminal 30, the conference room terminal 10B, and the WB terminal 10A in a block shape. In the description of FIG. 19, the difference from FIG. 4 will be mainly described. FIG. 19 differs from FIG. 4 in that the conference room terminal 10B and the WB terminal 10A each have a function. Further, the computer system of FIG. 3 is applied to the hardware configurations of the conference room terminal 10B and the WB terminal 10A.

First, the function of the conference room terminal 10B will be described. The conference room terminal 10B has a sixth communication unit 21, a third display control unit 22, a third operation reception unit 23, a conference reservation client unit 14, and a terminal communication unit 28. Each of these functional units included in the conference room terminal 10B is a function realized by operating any of the components shown in FIG. 3 by a command from the CPU 206 according to a program expanded from the HDD 208 to the RAM 204. Or it is a means.

The sixth communication unit 21 mainly transmits and receives various information to and from the conference reservation system 50. In this embodiment, one's own conference room 9 is designated by identification information or the like, the reservation information of the conference room 9 is requested from the conference reservation system 50, and the reservation information is received. In addition, a check-in request (reservation ID, conference room, date and time) is sent, and the success or failure of check-in and the URL of the whiteboard are received.

The third display control unit 22 displays various screens on the display device 202. For example, the reservation information received by the sixth communication unit 21 is displayed on the display device 202. The third operation reception unit 23 receives various operations of the participants with respect to the conference room terminal 10B. For example, it accepts check-in operations (input of reservation ID), check-out operations, and the like. The third display control unit 22 and the third operation reception unit 23 may be realized by browser software or application software.

The conference reservation client unit 14 is a client application of the conference reservation system 50, and notifies check-in and check-out via the sixth communication unit 21.

The terminal communication unit 28 is a terminal application that communicates with the server unit 27 of the WB terminal 10A. For example, information is transmitted to the WB terminal 10A by a communication procedure such as HTTP and HTTPs provided by a general server, and information is received from the WB terminal 10A. The IP address and port number of the server unit 27 of the WB terminal 10A are set in the terminal communication unit 28.

Next, the function of the WB terminal 10A will be described. The WB terminal 10A has a seventh communication unit 24, a fourth display control unit 25, a fourth operation reception unit 26, a browser unit 13, a WB client unit 16, and a server unit 27. Each of these functional units included in the WB terminal 10A is a function realized by operating any of the components shown in FIG. 3 by a command from the CPU 206 according to a program expanded from the HDD 208 to the RAM 204. It is a means.

The seventh communication unit 24 mainly transmits and receives various information to and from the WB system 40. In this embodiment, the URL of the whiteboard is transmitted to the WB system 40, and the screen information of the whiteboard is acquired from the WB system 40.

The browser unit 13 has the same function as general browser software, communicates with the WB system 40 using the URL of the whiteboard as a communication destination, and receives the screen information of the whiteboard received by the seventh communication unit 24. A web page (also referred to as a web application) that analyzes and functions as a whiteboard is displayed on the display device 202.

The fourth display control unit 25 displays various screens and information on the display device 202. Information that cannot be displayed by the browser unit 13 can be displayed, but the functions of the fourth display control unit 25 and the browser unit 13 do not have to be strictly distinguished.

The WB client unit 16 performs processing for realizing the function of the whiteboard with respect to the whiteboard displayed by the browser unit 13. For example, the handwritten stroke is displayed on the display device 202. It also performs a process of transmitting stroke data to the WB system 40. Further, the drawn image drawn by the stroke on the display device 202 is converted into a PDF file and saved.

The server unit 27 functions as a server for the conference room terminal 10B. It is not necessary to provide screen information such as HTML as a Web server, and information is received by a request from the conference room terminal 10B in a communication procedure such as HTTP and HTTPs, and information is transmitted as a response to the request.

As described above, since the WB terminal 10A has the server unit 27, the conference room terminal 10B and the WB terminal 10A can communicate with each other. The conference room terminal 10B may have a server unit 27, and the WB terminal 10A may have a terminal communication unit 28.

<Reservation information>
FIG. 20 is an example of the reservation information stored in the reservation information DB 57 in this embodiment. The reservation information of this embodiment has each item of the conference room name, the conference name, the time zone, the participants, and the email addresses of the participants. Such reservation information is transmitted from the schedule management system 60 to the conference reservation system 50 as described in the first embodiment, and further transmitted from the conference reservation system 50 to the conference room terminal 10B. Further, in this embodiment, the conference room terminal 10B transmits the reservation information to the WB terminal 10A.

Note that FIG. 20 is an example, and other information related to the conference such as the reserved date and time when the conference was reserved, whether or not the conference was held suddenly, the title of the participant, or the role of the participant in the conference, etc. May be included. FIG. 20 does not limit the reservation information of the conference. In addition, the information displayed in this way may be referred to as bibliographic information in the sense of bibliographic information of the conference.

<Processing until the WB terminal displays the reservation information>
FIG. 21 is an example of a flowchart showing a procedure in which the communication system 1 creates a whiteboard at the time of reservation and displays it at the time of check-in. In the description of FIG. 21, the difference from FIG. 6 will be mainly described. The processing of steps S31 to S36 may be the same as that of S1 to S5 of FIG.

As described in the first embodiment, since the reservation ID is registered in the schedule management system 60, the conference organizer can confirm the reservation ID required for check-in. Since this process is the same as steps S6 to S6.1 in FIG. 6, it is omitted in FIG. 21.

Next, the processing at the start of the conference will be described.

S37: The conference organizer goes to the conference room 9 and performs a check-in operation (input of a reservation ID) for the conference room terminal 10B. Participants can also check in.

S38: The third operation reception unit 23 of the conference room terminal 10B accepts the input of the reservation ID as an operation necessary for check-in, and the conference reservation client unit 14 of the conference room terminal 10B checks including the conference room name, the date and time, and the reservation ID. The in-request is transmitted to the conference reservation system 50 via the sixth communication unit 21. It is not always necessary to accept the reservation ID, and it is sufficient to simply accept the pressing of the "start" or "enter room" button indicating the start of the conference. The fourth communication unit 52 of the conference reservation system 50 receives the check-in request, and the conference room management unit 51 determines whether or not the check-in is successful. That is, it is determined whether or not the check-in is successful depending on whether or not the reservation ID of the reservation information specified by the conference room name and the date and time matches the reservation ID transmitted from the terminal device 10. It is assumed that the explanation of FIG. 21 is successful. Upon successful check-in, the fourth communication unit 52 of the conference reservation system 50 transmits the URL of the whiteboard specified by the reservation ID to the conference room terminal 10B. The reservation information is not transmitted in step S38 because the conference room terminal 10B has acquired it from the conference reservation system 50 in advance in order to accept check-in, but it may be transmitted again. The conference room terminal 10B periodically acquires reservation information from the conference reservation system 50 at least once a day, and displays the reservation status of the conference room (whether or not there is a reservation for each time zone, etc.) on the check-in screen. ..

Instead of using the conference room and the date and time as keys, some identification information that uniquely identifies the reservation of the conference room may be used as a key. The same applies to the subsequent processing.

S39: The terminal communication unit 28 of the conference room terminal 10B transmits a conference start notification to the WB terminal 10A because the check-in is successful. That is, the process of making the whiteboard available to the participants is performed. The meeting start notification includes the URL of the whiteboard and reservation information. When the pressing of the "start" or "entry" button indicating the start of the conference is accepted in step S38, the notification indicating the start of the conference may be transmitted in step S39 as well, instead of the reservation ID.

S40: The server unit 27 of the WB terminal 10A activates the browser when the server unit 27 receives the conference start notification.

S41: The activated browser unit 13 accesses the URL of the whiteboard. As a result, the whiteboard created in step S34 can be accessed.

S42: Further, the browser unit 13 (or the fourth display control unit 25 may be used) displays the reservation information on the whiteboard. Various display methods can be considered. For example, the fourth display control unit 25 may superimpose on the whiteboard and display a pop-up. Alternatively, the fourth display control unit 25 may display it as a notification message such as a balloon balloon. Alternatively, the fourth display control unit 25 may display a notification icon and display it when the notification icon is pressed. Alternatively, the browser unit 13 may display the reservation information included in the screen information created by the WB system 40. That is, the reservation information is embedded in a part of the screen information by HTML, JavaScript (registered trademark), CSS, etc. that constitute the screen information. In this case, the 7th communication unit 24 of the WB terminal 10A transmits the reservation information to the WB system 40. The WB creation unit 41 uses the received reservation information to generate screen information (also referred to as a Web page or Web application) using HTML, JavaScript (registered trademark), CSS, or the like. Since the 7th communication unit 24 of the WB terminal 10A receives the screen information, the browser unit 13 can display the reservation information as a part of the whiteboard.

The reservation information is not limited to the case where the conference room terminal 10B acquires the reservation information after the start of the conference and transmits it to the WB terminal 10A. The system 40 may generate screen information including reservation information, and the WB terminal 10A may display the screen information after the conference starts.

As described above, in the communication system 1 of the present embodiment, the WB terminal 10A can display the reservation information together with the whiteboard.

<Display example of reservation information>
FIG. 22 is an example of the reservation information screen 601 displayed by the browser unit 13 of the WB terminal 10A. The reservation information screen 601 mainly has a reservation information display button 602 and a reservation information display field 603. The reservation information display button 602 is a button for displaying the reservation information, and the reservation information display field 603 is a field for displaying the reservation information.

When the browser unit 13 of the WB terminal 10A receives the screen information including the reservation information, the whiteboard is in the initial state and the reservation information display field 603 is not displayed. When the participant presses the reservation information display button 602, the fourth operation reception unit 26 accepts the operation, and the browser unit 13 displays the reservation information display field 603. The reservation information display field 603 once displayed may remain displayed, or may be automatically deleted (even if the participant does not operate) after a lapse of time.

By displaying the reservation information on the whiteboard, participants can determine which conference the whiteboard is associated with. Simply displaying the whiteboard did not confirm that the whiteboard was associated with the upcoming conference.

Further, when the 7th communication unit 24 of the WB terminal 10A receives the screen information including the reservation information, the browser unit 13 may automatically display the reservation information display field 603. In this case as well, the displayed reservation information display field 603 may remain displayed, or may be automatically deleted (even if the participant does not operate) after a lapse of time.

The example shown in FIG. 22 is merely an example, and the input information may be described as text data directly on the whiteboard. Further, it may be displayed in combination with image data of a photograph or a drawing. FIG. 22 does not limit the display method.

The screen as shown in FIG. 22 can be saved as a PDF file or the like by the function of the WB client unit 16. Therefore, the WB terminal 10A of this embodiment can save the reservation information and the drawn image in the same PDF file, and when the participant opens the PDF file later to see the drawn image, the PDF file is saved in which conference. It can be easily determined from the reservation information whether it has been done.

<When participants are added after the meeting starts>
Unscheduled participants may join the meeting after the meeting starts. In this embodiment, the conference reservation system 50 can acquire the reservation information added by the participants, and the participants to which the WB terminal 10A is added later can also be displayed.

FIG. 23 is an example of a flowchart showing a procedure for displaying the participants to which the communication system 1 is added. The process of FIG. 23 is executed during the holding of the conference after the process of FIG. 21.
S51: When a participant who is not registered in the reservation information participates in the conference, the conference organizer performs an operation to add the participant to the organizer terminal.

S52: The first operation reception unit 32 of the organizer terminal accepts the operation of the organizer, and the first communication unit 33 transmits a participant addition request for adding a participant to the reservation information of the conference room 9. For example, send the meeting room, date and time, and participants. The fifth communication unit 61 of the schedule management system 60 receives these, and the reservation information registration reception unit 62 adds a participant to the reservation information DB 64.

S53: The reservation information acquisition unit 55 of the conference reservation system 50 periodically inquires about changes in reservation information by polling. For example, send the meeting room and the date and time. In response to this, the reservation information acquisition unit 55 acquires the changed portion of the reserved information that has been changed. In this embodiment, it is assumed that the participants have changed. Instead of acquiring the changed reservation information, the reservation information may be acquired again and the conference reservation system 50 may specify the changed portion.

S54: The conference reservation client unit 14 of the conference room terminal 10B periodically inquires of the conference reservation system 50 via the sixth communication unit 21 to change the reservation information by designating the conference room and the date and time. The interval between regular inquiries is preferably as short as every minute. This allows the WB terminal 10A to display additional participants as soon as an unscheduled participant joins the meeting. Therefore, it is preferable to make regular inquiries about changes during the meeting at shorter intervals than before the meeting. In this case, it is necessary that the interval at which the conference reservation system 50 inquires of the schedule management system 60 for the change of the reservation information is as short as every minute.

When there is a change in the conference reservation information, the fourth communication unit 52 of the conference reservation system 50 transmits the content of the change to the conference room terminal 10B. In FIG. 23, it is assumed that the participants have changed. Therefore, the added participants are sent.

S55: When the sixth communication unit 21 of the conference room terminal 10B receives an additional participant, the terminal communication unit 28 transmits the additional participant to the WB terminal 10A.

S56: The server unit 27 of the WB terminal 10A receives an additional participant. As a result, the 7th communication unit 24 sends an additional participant to the URL of the whiteboard and requests the WB system 40 to update the reservation information. The third communication unit 42 of the WB system 40 receives the update of the reservation information, and the WB creation unit 41 updates the screen information of the whiteboard.

S57: The third communication unit 42 of the WB system 40 transmits the updated screen information of the whiteboard to the WB terminal 10A. Since the 7th communication unit 24 of the WB terminal 10A has received the screen information, the browser unit 13 displays the added participant. As the method of displaying the reservation information, various methods described in step S42 of FIG. 21 may be adopted. However, it is preferable that the added participants are displayed without any operation of the participants in order to indicate that the additional participants have been accepted.

In this way, the added participants can be displayed on the whiteboard. Also, if the whiteboard screen is saved in the PDF file, the added participants can also be recorded.

In FIG. 23, the conference organizer had to register additional participants in the schedule management system 60, but it would be convenient if the participants could add the participants as shown in FIG. 23 from the WB terminal 10A.

FIG. 24 is an example of another flowchart of the procedure for displaying the participants to which the communication system 1 is added.
S61: When a participant who is not registered in the reservation information participates during the conference, the participant holds the IC card over the WB terminal 10A. The IC card contains information (ID, name, e-mail address, etc.) that identifies the participant.

S62: The WB terminal 10A has an IC card reader, and the IC card reader reads information identifying the participant from the IC card of the participant. Actually, in order to authenticate the information of the IC card, the WB terminal 10A transmits the information for identifying the participant to the authentication server, and acquires the success or failure of the authentication and the name of the participant.

The seventh communication unit 24 of the WB terminal 10A requests the WB system 40 to update the reservation information together with the additional participants. As a result, screen information including additional participants is transmitted to the WB terminal 10A.

S63: Since the 7th communication unit 24 of the WB terminal 10A has received the screen information, the browser unit 13 displays the added participant.

S64: In order to register the additional participants in the schedule management system 60, the server unit 27 of the WB terminal 10A transmits the additional participants to the conference room terminal 10B.

S65: The terminal communication unit 28 of the conference room terminal 10B receives the additional participants and transmits the participant additional notification including the participants, the conference room, and the reservation ID to the conference reservation system 50.

S66: Since the fourth communication unit 52 of the conference reservation system has received the participant addition notification, the URL registration unit 56 transmits the participant addition notification to the schedule management system 60. As a result, additional participants are registered in the reservation information of the schedule management system 60. In addition, additional participants may be sent to each participant by e-mail.

According to the procedure of FIG. 24, a participant can be added by a simple operation of holding the IC card over the participant.

In FIG. 24, the participant holds the IC card over the WB terminal 10A, but the participant may hold the IC card over the conference room terminal 10B. In this case, the conference room terminal 10B transmits an additional participant to the WB terminal 10A. Participant authentication may be performed by either the conference room terminal 10B or the WB terminal 10A. Further, the information for identifying the participants and the information for identifying the conference (meeting room, date and time) are transmitted from the conference room terminal 10B to the conference reservation system 50 and registered in the schedule management system 60.

<Procedure to create a whiteboard URL at check-in>
In FIG. 21, the URL of the whiteboard was created at the time of reservation, but the URL of the whiteboard may be created at the time of check-in.

FIG. 25 is an example of a flowchart showing a procedure in which the communication system 1 creates a URL of a whiteboard at check-in and the whiteboard displays reservation information. In the description of FIG. 25, the difference from FIG. 21 will be mainly described.

S71 to S75: In FIG. 25, since the URL of the whiteboard is not created at the time of reservation, there is no process corresponding to step S34 in FIG. Further, in step S75, the reservation ID is registered in the schedule management system 60.

S76 to S78: The same as steps S37 to S39 in FIG. 21 may be used.

S79: When the 7th communication unit 24 of the WB terminal 10A receives the conference start notification, the WB client unit 16 requests the WB system 40 to create a whiteboard together with the reservation information. The third communication unit 42 of the WB system 40 receives the whiteboard creation request, and the WB creation unit 41 creates a new whiteboard at a new URL. The fifth communication unit 61 transmits the URL of this whiteboard to the conference reservation system 50.

S80 to S82: The same as steps S40 to S42 in FIG. 21 may be used. However, in order to register the URL of the whiteboard in the schedule management system 60, the seventh communication unit 24 of the WB terminal 10A transmits the URL of the whiteboard to the conference room terminal 10B.

S83: In order to register the URL of the whiteboard in the schedule management system 60, the sixth communication unit 21 of the conference room terminal 10B transmits a whiteboard registration request to the conference reservation system 50 together with the conference room and the date and time.

S84: The fourth communication unit 52 of the conference reservation system 50 receives the whiteboard registration request, and the URL registration unit 56 registers the whiteboard URL in the schedule management system 60.

As described above, also in this embodiment, the URL of the whiteboard can be created at the time of reservation, and the WB terminal 10A can display the reservation information.

<Summary>
As described above, according to the communication system 1 of the present embodiment, it was not possible to confirm whether the whiteboard was associated with the conference to be held just by displaying the whiteboard. By displaying the reservation information on the board, you can confirm which conference this whiteboard was associated with.

<Other application examples>
Although the best mode for carrying out the present invention has been described above with reference to examples, the present invention is not limited to these examples, and various modifications are made without departing from the gist of the present invention. And substitutions can be made.

For example, a meeting on the same agenda may be resumed on another day. In such cases, participants may want to use the whiteboard that has already been created. Therefore, it is effective for the WB creation instruction unit 53 to determine the similarity of the reservation information of the conference, and if the similarity is equal to or higher than the threshold value, acquire the URL of the whiteboard from the reservation information and provide it to the terminal device 10. be. The degree of similarity is calculated based on whether the conference name is the same or the participants are the same.

Further, although it has been explained that the terminal device 10 has three functions (a function related to the use of the conference room 9, a function related to the whiteboard, and a function of the browser), a separate terminal device 10 may be prepared for each function. .. The terminal devices 10 communicate with each other via an in-house network or the like.

Further, the configuration examples shown in FIG. 4 and the like correspond to the main functions in order to facilitate the understanding of the processes of the WB system 40, the conference reservation system 50, the schedule management system 60, the user terminal 30, and the terminal device 10. It is divided. The present invention is not limited by the method of dividing the processing unit or the name. The functions of the WB system 40, the conference reservation system 50, the schedule management system 60, the user terminal 30, and the terminal device 10 can be further divided into more processing units according to the processing contents. Further, one processing unit can be divided so as to include more processing.

Further, the WB system 40, the conference reservation system 50, and the schedule management system 60 may each be plural, or these functions may be distributed and mounted in a plurality of information processing devices.

The reservation information acquisition unit 55 is an example of information acquisition means, the WB creation instruction unit 53 is an example of whiteboard creation request means, the fourth communication unit 52 is an example of transmission means, and the WB client unit 16 is. The second communication unit 15 and the seventh communication unit 24 are examples of the first communication means, the WB system 40 is an example of the service, and the schedule management system 60 is the second information processing device. The conference reservation system 50 is an example of an information processing device.

The URL registration unit 56 is an example of registration means, the first communication unit 33 is an example of a second communication means, the conference room management unit 51 is an example of facility management means, and the second operation reception unit 12 is a reception unit. This is an example of means. The browser unit 13 is an example of display processing means.

1 Communication system 1
9 Meeting room 10 Terminal device 30 User terminal 40 WB system 50 Meeting reservation system 60 Schedule management system 100 Computer system

Japanese Unexamined Patent Publication No. 2012-0433380

Claims (17)

A communication system having an information processing device that can use a service for managing screen information of an electronic information board and a terminal device that communicates with the information processing device via a network.
The information processing device is
An information acquisition means for acquiring information related to the schedule from a second information processing device that manages a schedule related to the use of the facility in which the terminal device is arranged.
When the information acquisition means acquires information about the schedule, the board creation request means for requesting the service to create the electronic information board and the board creation request means.
It has a transmission means for transmitting information for accessing the electronic information board created by the service to the terminal device.
The terminal device is
An acquisition means for acquiring information for accessing the electronic information board, and
A first communication means for accessing the electronic information board by using the information received by the acquisition means for accessing the electronic information board.
Communication system with. The information processing device is
It has a registration means for registering information for accessing the electronic information board created by the service in the second information processing apparatus in association with information related to the schedule.
The acquisition means is characterized in that information for accessing the electronic information board acquired by the information processing apparatus from the second information processing apparatus is acquired from the information processing apparatus based on the information regarding the schedule. The communication system according to claim 1. Further, it has a user terminal used by the user of the facility, and has a user terminal.
The user terminal is
Based on the information about the schedule, the information for accessing the electronic information board is acquired from the second information processing apparatus.
The communication system according to claim 2, further comprising a second communication means for accessing the electronic information board using information for accessing the electronic information board. The terminal device is
The reception means for accepting the start of use of the facility and
It has a communication means for transmitting a request for start of use received by the reception means to the information processing apparatus.
The information processing device is
If the authentication of the request to start using the facility is successful, the facility management means for permitting the use of the facility is provided.
When the facility management means permits the use of the facility
The acquisition means acquires information for accessing the electronic information board from the information processing apparatus, and obtains information from the information processing apparatus.
The first communication means according to any one of claims 1 to 3, wherein the first communication means accesses the electronic information board by using the information for accessing the electronic information board acquired by the acquisition means. The communication system described. When the reservation to use the facility is canceled, or when the reservation start time of the facility has passed without the facility management means acquiring the request to start the use.
The communication system according to claim 4, wherein the board creation requesting means requests the service to delete the electronic information board. When the facility management means permits the use of the facility, the board creation requesting means requests the service to create the electronic information board.
The communication system according to claim 4, wherein the transmission means transmits information for accessing the electronic information board created by the service to the terminal device. The facility management means transmits information to remind the user terminal of the facility to remind the reservation of the facility before a predetermined time of the reservation start time of the facility based on the information about the schedule acquired by the information acquisition means. death,
When the board creation requesting means obtains a response to the information to remind the reservation to use the facility, the board creation request means requests the service to create an electronic information board.
The communication system according to claim 4, wherein the transmission means transmits information for accessing the electronic information board created by the service to the terminal device. The communication system according to any one of claims 1 to 7, wherein the information acquisition means acquires information related to the schedule by accepting registration of information related to the schedule to the information processing apparatus. The transmission means transmits information about the schedule acquired by the information acquisition means to the terminal device.
The acquisition means of the terminal device acquires information about the schedule from the information processing device.
The communication system according to claim 1, wherein the terminal device has a display processing means for displaying information related to the schedule on the display device. The schedule is for meeting room reservations and
The communication system according to claim 9, wherein the information regarding the schedule includes at least one of a conference name, a conference room name, a date and time, or a participant. The display processing means of the terminal device uses the information for the first communication means to access the electronic information board to access the electronic information board to obtain a white board as a display device. The communication system according to claim 9 or 10, wherein the communication system is displayed and information about the schedule is displayed on the whiteboard. The first communication means of the terminal device accesses the electronic information board using the information for accessing the electronic information board, and transmits information about the schedule to the service.
The claim is characterized in that the display processing means displays information on the schedule on the whiteboard by displaying a whiteboard based on screen information including information on the schedule created by the service on a display device. The communication system according to 9 or 10. The terminal device has a receiving means for receiving stroke drawing on the whiteboard.
12. The communication system according to claim 12, wherein the information regarding the schedule and the drawn stroke are stored in the same file. The transmission means transmits information about the participants of the conference acquired by the information acquisition means to the terminal device after the start of the conference.
The acquisition means of the terminal device acquires information about the participant from the information processing device.
The communication system according to any one of claims 9 to 13, wherein the display processing means of the terminal device displays information about the participant acquired after the start of the conference on the display device. It is a communication method performed by a communication system having an information processing device that can use a service for managing screen information of an electronic information board and a terminal device that communicates with the information processing device via a network.
The information processing device is
A step in which the information acquisition means acquires information on the schedule from a second information processing device that manages the schedule on the use of the facility.
When the board creation requesting means acquires the information regarding the schedule, the step of requesting the service to create the electronic information board and the step of requesting the service.
The transmitting means has a step of transmitting information for accessing the electronic information board created by the service to the terminal device.
The terminal device is
A step in which the acquisition means acquires information for accessing the electronic information board, and
A step of accessing the electronic information board by the first communication means using the information for accessing the electronic information board acquired by the acquisition means.
Communication method with. A service that manages the screen information of the electronic information board is available, and it is an information processing device that communicates with a terminal device that displays the screen information of the electronic information board via a network.
An information acquisition means for acquiring information related to the schedule from a second information processing device that manages the schedule related to the use of the facility, and
When the information acquisition means acquires information about the schedule, the board creation request means for requesting the service to create the electronic information board and the board creation request means.
An information processing device having a transmission means for transmitting information for accessing the electronic information board created by the service to the terminal device. An information processing device that can use the service that manages the screen information of the electronic information board and communicates with the terminal device that displays the screen information of the electronic information board via the network.
An information acquisition means for acquiring information related to the schedule from a second information processing device that manages the schedule related to the use of the facility, and
When the information acquisition means acquires information about the schedule, the board creation request means for requesting the service to create the electronic information board and the board creation request means.
A transmission means for transmitting information for accessing the electronic information board created by the service to the terminal device,
A program to function as.

Images