JP2019016343A - Information processing device, apparatus control system, and apparatus control method - Google Patents

Abstract

To provide an information processing device capable of managing use of an electronic apparatus.SOLUTION: An information processing device 30 that is connected via a network with a reservation management device 20 that manages reservation of a facility, includes: control information generation means 35 that detects timing at which use of an electronic apparatus arranged in the facility is started and generates first control information of the electronic apparatus, on the basis of the reservation information of the facility obtained from the reservation management device; and control information transmission means 36 that transmits the first control information to a facility terminal arranged in the facility.SELECTED DRAWING: Figure 33

Description

  The present invention relates to an information processing apparatus, a device control system, and a device control method.

  Equipment reservation systems such as conference rooms are known. A prospective participant of the conference can reserve the conference room with a browser operating on the terminal device by communicating the terminal device with the reservation management server. The prospective participants of the conference can operate the terminal device to communicate with the reservation management server, respectively, and confirm the schedule and location of the conference.

  In such a facility reservation system, there may be a case where an empty reservation is made in which a conference room that is not actually used remains reserved. In order to reduce vacant reservations, conventionally, a technique for notifying an attendee of a conference schedule by e-mail is known (for example, see Patent Document 1). Patent Document 1 discloses a system that notifies a participant of each conference in advance by e-mail when the meeting date and time approaches.

  However, the conventional technique has a problem that whether or not to use an electronic device arranged in a conference room is entrusted to a conference participant. In the conference room, electronic devices such as an electronic blackboard, a multi-function device, and a projector are arranged, and participants can hold a meeting using them. However, for participants who use these devices, the power of the electronic device must be controlled to be turned on in order to use them, and depending on the participant, it takes time to activate the electronic device. On the other hand, if the power of the electronic device can be freely turned on and off until the conference starts, those who have not reserved the conference room can also use the electronic device. In either case, if the participant forgets to turn off the power, the power consumption increases.

  In view of the above problems, an object of the present invention is to provide an information processing apparatus that can manage use of an electronic device.

  The present invention is an information processing apparatus connected via a network to a reservation management apparatus that manages a reservation of equipment, and is arranged in the equipment based on reservation information of the equipment acquired from the reservation management apparatus The timing at which use of the electronic device is started is detected, and the first control information is transmitted to the control information generating means for generating the first control information of the electronic device and the equipment terminal arranged in the equipment. Control information transmission means.

  An information processing apparatus that can manage use of an electronic device can be provided.

It is an example of the figure explaining the prior registration work regarding an equipment reservation system. It is an example of the figure explaining the procedure in which a meeting management server notifies the information regarding reservation of a conference room to a prospective participant. It is an example of the system block diagram of an equipment reservation system. It is an example of the system block diagram of an equipment reservation system. It is an example of the hardware block diagram of a meeting management server. It is a hardware block diagram of an example of a meeting room terminal. It is an example of the hardware block diagram of an electronic blackboard as an example of an electronic device. It is an example of the functional block diagram which shows the function of a reservation management server, a chat server, a meeting management server, and a terminal device in a block form. It is an example of the functional block diagram which shows the function of a terminal device, a conference room terminal, and an electronic device in block shape. It is an example of the reservation screen of the conference room which a reservation management server provides and a terminal device displays. It is an example of the registration work initial screen displayed on a registration terminal or a terminal device. It is an example of the notification robot registration screen displayed on a registration terminal. It is an example of the domain management screen displayed on a registration terminal. It is an example of the account corresponding | compatible screen displayed on a terminal device. It is an example of the sequence diagram which shows the procedure of registration of a notification robot. It is an example of the sequence diagram which shows the procedure which registers the account of a customer's reservation management server. It is an example of the sequence diagram which shows the procedure which matches the group of a chat system, and the account of a reservation management server. It is an example of the figure explaining the timing of the notification of the information regarding a conference room reservation. It is an example of the sequence diagram which shows the procedure in which a conference management server notifies the information regarding the reservation of a conference room. It is an example of the flowchart figure of the procedure which judges whether the notification judgment part notifies the information regarding the reservation of a conference room. It is an example of the sequence diagram in which a conference management server notifies the prospective participant of the information regarding a conference room reservation. It is a figure which shows an example of the information regarding the reservation of the conference room displayed on a terminal device. It is an example of the flowchart figure which shows the procedure in which a meeting management server notifies the information regarding the reservation of a meeting room. It is an example of the sequence diagram regarding the initial setting of a conference room terminal. It is an example of the sequence diagram at the time of a general user confirming a reservation situation. It is an example of a sequence diagram showing a check-in procedure using a two-dimensional code. It is an example of the sequence diagram which shows the procedure of check-in when a prospective participant forgets to carry a terminal device. It is an example of the sequence diagram in which a prospective participant checks in by near field communication. It is an example of the sequence diagram in which a prospective participant checks out. It is an example of the sequence diagram explaining the process at the time of starting of a meeting room terminal. It is an example of the flowchart figure regarding the process in which a meeting management server cancels a reservation automatically, and the check-in and check-out process of a meeting management server. It is a figure which shows an example of the example of a screen of a conference room terminal. It is an example of the figure explaining the outline of the control by the equipment reservation system of the electronic device arrange | positioned in the meeting room. It is an example of the figure explaining the outline of the control by the equipment reservation system of the electronic device arrange | positioned in the meeting room. It is an example of the sequence diagram which shows the procedure in which a meeting management server controls the power supply of an electronic device to ON in response to check-in. It is an example of the sequence diagram which shows the procedure in which a meeting management server controls the power supply of an electronic device to ON before the predetermined time of start time. It is an example of the sequence diagram which shows the procedure which controls the power supply of an electronic device to OFF after a meeting room terminal is checked out. It is an example of the figure explaining the process of a meeting management server in the case of controlling the power supply of an electronic device to ON in response to a check-in, and a meeting room terminal. It is an example of the flowchart figure which shows the procedure in which a meeting management server transmits control information before the predetermined time of start time. It is an example of the flowchart figure which shows the procedure in which a meeting room terminal controls the power supply of an electronic device to ON before the predetermined time of a start time.

  Hereinafter, as an example of an embodiment for carrying out the present invention, an equipment reservation system and an information notification method performed by the equipment reservation system will be described with reference to the drawings.

<Pre-registration work>
First, a description will be given of pre-registration work for operating an equipment reservation system capable of reducing empty reservations.

  FIG. 1 is an example of a diagram illustrating a prior registration work related to the facility reservation system 100 of the present embodiment. The network N includes a chat server 10 (information providing device) that controls the chat system, a reservation management server 20 (reservation management device) that manages reservations for facilities such as conference rooms, and conference management performed in conference rooms. The conference management server 30 to be performed is connected so that it can communicate as necessary.

  A chat system is a system that performs transmission and reception of information such as text on a one-to-one basis or in groups in real time. In FIG. 1, the accounts of Mr. A, Mr. B, Mr. C, and Mr. D are associated with the group 1, and Mr. A, Mr. B, Mr. C, and Mr. D form the group 1. The text input by Mr. A is displayed on the terminal device 60 of Mr. A and transmitted to the terminal devices 60 of Mr. B, Mr. C, and Mr. D. The same applies to texts entered by Mr. B, Mr. C, and Mr. D. In the present embodiment, such a chat system is used, and the conference management server 30 notifies the prospective participants (Mr. A, Mr. B, Mr. C, and Mr. D) of information related to conference room reservation. It is connected.

  The reservation management server 20 is a server (information processing apparatus) that provides a Web service for managing the overall schedule. The reservation management server 20 receives a reservation for a conference room, and a prospective participant can confirm the conference schedule at an arbitrary timing. The facility reservation system 100 uses the account of the reservation management server 20 to associate the chat system group with the prospective participant of the conference (the prospective participant of the conference that has reserved the conference with the reservation management server 20). This is one of the features of the embodiment. Hereinafter, an outline of the prior registration work will be described.

  (1) An administrator of the facility reservation system 100 operates the registration terminal 50 to communicate with the chat server 10 and obtain an account for the notification robot. The notification robot is a program conventionally called “bot”, and speaks to the group as an agent of the conference management server 30 registered in the chat system. Although registered in group 1 in FIG. 1, the group in which the notification robot is registered is a group of prospective participants who will participate in the conference. That is, group 1 is composed of prospective participants who participate in the conference.

  (2) Further, the administrator of the facility reservation system 100 operates the registration terminal 50 to communicate with the conference management server 30 and registers a domain for notifying information such as text. This domain is a domain common to accounts issued to the prospective participants by the reservation management server 20 (if the account is an email address, the domain portion of the email address). For example, a domain is issued for each company. In principle, conference room reservation information can be searched by this domain. In addition, not only the domain is used for acquiring the reservation information, but also the account information (address and password) of an administrator with administrator authority is used. Reservation information within a range in which this administrator has authority (for example, the entire domain if the administrator has authority over the entire domain) is acquired.

  (3) Next, one of the prospective participants associates Group 1 with A, B, C, and D, respectively. Specifically, the terminal device 60 is operated to communicate with the conference management server 30, and the account of the user (planned participant) of the facility reservation system 100 issued by the reservation management server 20 and the group name of the group 1 (specifically, Is a group name, etc., information for specifying a message notification destination in the chat system (for example, a slack (registered trademark) requires a channel name and a team name) and registers them in association with each other.

  Through the above-described pre-registration work, the conference management server 30 can use the chat server 10 to notify the prospective participants of information related to conference room reservation.

<Outline of notification>
FIG. 2 is an example of a diagram for explaining a procedure for the conference management server 30 to notify a prospective participant of information related to conference room reservation.

  (4) At least one of the prospective participants communicates with the reservation management server 20 using the terminal device 60 and reserves the conference room. Reservation information related to the conference room reservation is recorded in the reservation management server 20. In the reservation information, at least the account of the prospective participant who made the reservation (reserver account) is recorded.

  (5) The conference management server 30 determines an arbitrary domain. This is to notify a prospective participant who has an account including this domain. The conference management server 30 periodically communicates with the reservation management server 20 and acquires reservation information from the reservation management server 20.

  (6) Here, for example, it is assumed that the reservation information of Mr. A is found. Thereby, the conference management server 30 can specify the destination of the notification robot associated with Mr. A. Here, it is assumed that group 1 associated with Mr. A is specified.

  (7) The conference management server 30 communicates with the chat server 10 to notify the prospective participants of the group 1 of information related to the conference room reservation as a notification robot registered in the group 1. That is, an appropriate text is transmitted to other prospective participants.

  (8) The chat system transmits the text input by the notification robot to all members in the group. Thereby, it is possible to notify all of the prospective participants of information related to the conference room reservation.

  Therefore, the facility reservation system 100 according to the present embodiment can notify an attendee of information related to conference room reservation using a chat system without using e-mail. There is a statistic that chat system texts have a very high browsing rate compared to e-mail, which can reduce the risk of overlooked prospective participants. Further, the chat system makes it easy to create a group, and the administrator of the facility reservation system 100 or the prospective participant can easily create a group of prospective participants of the conference.

<Terminology>
Participants who are scheduled to participate become participants when they check in.

  The information related to the facility reservation may be information accompanying the facility reservation. For example, it may be only that the reservation has been made, or may include the reservation target, the start time of use of the facility, and the like. Sending information related to the reservation of equipment is sometimes referred to as “remind”.

  A customer refers to a company that uses the facility reservation system 100, and a prospective participant is assumed to be an employee of this customer. However, the customer may be an individual.

  Equipment is something that is necessary for a certain purpose. In this embodiment, the term “meeting room” will be used.

  A group is a group of people. A target person belonging to a group refers to a person belonging to an arbitrary group in the chat server 10. Or it is a member of the group to which notification information is notified. The group specifies which member in the chat system, generally called a room or a room, is to be notified. In slack (registered trademark) as an example of a chat system, a “group” is called a channel. In another chat system, it may be called a group as it is.

  The notification information is information transmitted from the conference management server 30 to the chat server 10 and refers to information shared by the group.

  The equipment terminal may be an information processing apparatus that is disposed in the equipment and has a function of communicating with the conference management server 30. Preferably, it has a communication function with a display and the terminal device 60.

<System configuration example>
FIG. 3 is an example of a system configuration diagram of the facility reservation system 100. The facility reservation system 100 can be mainly divided into an external network N2 and an internal network N1. Here, the internal network N1 is a network inside the firewall, and the external network N2 is a network (including the Internet) through which an unspecified number of communications are transmitted.

  A reservation management server 20, a conference management server 30, and a chat server 10 are connected to the external network N2, and each server can communicate as necessary. In addition, a registration terminal 50 operated by an administrator of the facility reservation system 100 and a terminal device 60 operated by a conference participant are connected to the external network N2 as necessary. Note that the registration terminal 50 and the terminal device 60 can be connected to the external network from the internal network N1.

The reservation management server 20 can be realized by one or more information processing apparatuses (computer systems) equipped with a general server OS or the like. A system related to a facility reservation provided by the reservation management server 20 is referred to as a reservation management system. The reservation management server 20 has a calendar system and provides a web application for managing various schedules. Specifically, for example, it has the following functions.
・ Receiving appointments and confirming appointments from anywhere at any time ・ E-mail notification at the set date and time, such as 30 minutes before the appointment ・ One person manages appointments with multiple calendars (work, home, etc.) Yes-Share calendar with people in the same group The reservation management server 20 manages users with accounts. An account is a right for a user to use a service. In many systems, a user logs into the system using an account. For this reason, the account has a function (identification information function) in which the system uniquely identifies the user. In the present embodiment, the conference management server 30 can acquire the conference room reservation information by using the account of the reservation management server 20 by the conference management server 30. The account may be e-mail, ID, telephone number, or the like. The conference management server 30 logs in to the reservation management server 20 using, for example, an account and a password.

  In the present embodiment, a conference is managed as a schedule, but the reservation management server 20 is not limited to a conference and can manage various schedules. In addition to conference rooms, it can be used to reserve various facilities such as rental of various electronic devices and reservation of parking lots. As a reservation management system, G Suite (registered trademark), Office365 (registered trademark), and the like are known. However, any reservation management server having a function described in the present embodiment may be used.

  In the present embodiment, information related to the conference room 6 of the in-house network N1 is registered in advance in the reservation management server 20. That is, the web application of the reservation management server 20 is customized according to the meeting room name, meeting room ID, reservation available time, reservation unit, etc. of each meeting room 6 in the company internal network using the facility reservation system 100. ing. Accordingly, the conference room 6 of the company that uses the facility reservation system 100 is associated with the reservation information.

  The chat server 10 can be realized by one or more information processing apparatuses (computer systems) equipped with a general server OS or the like. A real-time sharing system for information such as text for a plurality of users provided by the chat server 10 is called a chat system. The chat server 10 notifies the terminal device 60 of information related to the conference room reservation.

  Information to be shared includes images, sounds, and the like, and is not limited to text. In the present embodiment, for convenience of explanation, it is assumed that text is mainly used for notification. For example, the chat system may provide a voice call function between groups. The voice call may be one-to-one or one-to-N (≧ 2). Therefore, when the chat system notifies the information related to the conference room reservation in this embodiment, a voice message may be output in addition to the text display. Note that although LINE (registered trademark), Slack (registered trademark), and the like are known as chat systems, any chat system that can notify one or more users from a notification robot may be used.

  Similarly, the chat server 10 manages users with an account (different from the reservation management server account), but the conference management server 30 need not be aware of the account of the chat server 10.

  The conference management server 30 can be realized by one or more information processing apparatuses (computer systems) on which a general server OS or the like is mounted. As a process related to the external network N2, the conference management server 30 obtains conference room reservation information from the reservation management server 20, and if a prospective participant is detected in the reservation information, it is associated with the prospective participant at the set timing. The notification is transmitted to the group of the chat server 10 that has been sent. Further, as processing related to the in-house network N1, check-in and check-out to the conference room are managed, and the power supply of the electronic device 70 is controlled based on the conference room reservation information acquired from the reservation management server 20.

The terminal device 60 and the registration terminal 50 can be realized by one or more information processing devices (computer systems) on which a general OS or the like is mounted. Although the registration terminal 50 has been described as a terminal operated by an administrator of the facility reservation system 100 and the terminal device 60 is an apparatus operated by a prospective participant, the two need not be clearly distinguished. The terminal device 60 is, for example, a smartphone, a tablet terminal, a PC (Personal Computer), a PDA (Personal Digital Assistant), a wearable PC (sunglass type, wristwatch type, etc.). However, it is sufficient that browser software having a communication function or application software dedicated to the chat server 10 or the reservation management server 20 operates. For example, a car navigation system, a game machine, a television receiver, or the like can be the terminal device 60.
In the terminal device 60, dedicated application software (hereinafter referred to as a chat application) operates on the chat server 10, and furthermore, dedicated application software (hereinafter referred to as a conference application) operates on the facility reservation system 100. However, these may be substituted with browser software.

  An AP 80 (access point), a conference room terminal 90, and an electronic device 70 are connected to the in-house network N1, and the conference room terminal 90 and the electronic device 70 can communicate as needed via the AP 80. . The in-house network N1 is, for example, a LAN (Local Area Network). The terminal device 60 is brought into the in-house network N1 by a prospective participant.

  The AP 80 is a base station for the conference room terminal 90 and the electronic device 70 to communicate via a wireless LAN. The AP 80 may have a router function, and the AP 80 determines whether the destination is the external network N2 or the internal network N1 based on the communication destination IP address and switches the communication transfer destination. Since the internal network N1 is inside the firewall, direct communication from the external network N2 to the internal network N1 is difficult.

  The conference room terminal 90 is an information processing apparatus (equipment terminal) operated by a prospective participant who uses the conference room. The conference room terminal 90 is arranged on the desk of the conference room 6 or is arranged at the entrance of the conference room 6. A plurality of conference room terminals 90 may be arranged in one conference room 6. The conference room terminal 90 can be realized by one or more information processing apparatuses (computer systems) equipped with a general OS or the like. The conference room terminal 90 displays a menu for check-in, check-out, etc., and communicates with the conference management server 30 to inform the conference management server 30 of the check-in or check-out. Further, for example, the conference room ID is transmitted to the conference management server 30, and reservation information of the conference room currently being performed in the conference room is displayed. Further, control information such as power ON / OFF of the electronic device 70 is acquired from the conference management server 30. As a result, the conference room terminal 90 turns the power of the electronic device 70 on and off.

  As an example, the conference application that operates on the terminal device 60 communicates with the conference room terminal 90 by short-range wireless communication. As will be described later, the information regarding the conference room reservation acquired by the terminal device 60 includes conference identification information. The conference room terminal 90 acquires conference identification information by short-range wireless communication, manual input, a two-dimensional code, etc., and transmits it to the conference management server 30. As a result, the conference room terminal 90 can determine whether or not the prospective participant who reserved the conference room in the most recent time zone from the current time has checked in.

  Since the conference room terminal 90 transmits the conference identification information and the conference room ID to the conference management server 30, the conference management server 30 uses the conference identification information and the conference room ID to identify the prospective participant who reserved the conference room or this prospective participant. It is possible to confirm that the conference room reserved by the prospective participants who will participate in the conference together is used.

  The electronic device 70 is various office devices that can be used in a conference room. For example, an electronic blackboard, a multifunction machine, a projector, a digital signage, a digital camera, and the like. The electronic blackboard has a large display with a touch panel, detects the coordinates of the board surface designated by the user, connects the coordinates, and displays the stroke. In addition, it is possible to display an image of a connected PC, or to communicate with an electronic blackboard at another site to synchronize strokes. The electronic blackboard may be called an electronic information board or an electronic whiteboard.

  The multifunction machine has functions such as a copy machine, a scanner, a printer, and a fax transmission / reception, and is used for printing materials during a meeting, copying materials, digitizing materials, sending materials, and the like. A projector is a device that projects an image. For example, it is possible to share the video displayed on the display by the terminal device 60 among the prospective participants by projecting it onto a screen or the like. Digital signage is a large display that is used to display any still or moving image. The digital camera is used by each prospective person to capture and store paper materials and materials displayed on an electronic blackboard.

  The conference room terminal 90 includes a type without a UI (User Interface) and a type with a UI as shown in FIG. 3 (FIG. 4). UI means a display. The function of the conference room terminal 90 is slightly different depending on whether or not there is a UI. For example, since there is no UI, a user's direct operation cannot be accepted, so there is a restriction on the check-in method. In the present embodiment, for convenience of explanation, the conference room terminal 90 with UI in FIG. 4 is assumed.

<Hardware configuration>
<< Hardware configuration of conference management server 30 >>
FIG. 5 is an example of a hardware configuration diagram of the conference management server 30. 2 is an example of a schematic hardware configuration diagram of a conference management server 30. FIG. The conference management server 30 includes a CPU 201 and a memory 202 that enables high-speed access to data used by the CPU 201. The CPU 201 and the memory 202 are connected to other devices or drivers of the conference management server 30, for example, a graphics driver 204 and a network driver (NIC) 205 via the system bus 203.

  The graphics driver 204 is connected to an LCD (display device) 206 via a bus and monitors a processing result by the CPU 201. The network driver 205 connects the conference management server 30 to the external network N2 at the transport layer level and the physical layer level to establish a session with another device.

  An I / O bus bridge 207 is further connected to the system bus 203. On the downstream side of the I / O bus bridge 207, a storage device such as an HDD (hard disk drive) 209 is provided by IDE, ATA, ATAP80I, serial ATA, SCSI, USB, etc. via an I / O bus 208 such as PCI. Is connected. The HDD 209 stores a program 209p for controlling the entire conference management server 30. The HDD 209 may be an SSD (Solid State Drive). The program 209p may be distributed in a state stored in a storage medium, or may be distributed from a program distribution server.

  An input device 210 such as a keyboard and a mouse (referred to as a pointing device) is connected to the I / O bus 208 via a bus such as a USB, and receives input and commands from an operator such as a system administrator. Yes.

  Note that the hardware configuration of the conference management server 30 shown in the drawing shows hardware elements that the conference management server 30 preferably includes.

  The hardware configuration diagram of the reservation management server 20, the chat server 10, the registration terminal 50, and the terminal device 60 is the same as or different from the conference management server 30, and the description of the facility reservation system 100 of the present embodiment. It is assumed that there will be no hindrance. In addition, since the conference management server 30, the reservation management server 20, and the chat server 10 support cloud computing, these hardware configurations dynamically connect / disconnect hardware resources according to the load. May be configured. Cloud computing refers to a usage mode in which resources on a network are used without being aware of specific hardware resources.

<< Conference room terminal 90 >>
FIG. 6 is a hardware configuration diagram of an example of the conference room terminal 90. Note that the conference room terminal 90 in FIG. 6 is assumed to be a tablet device. The conference room terminal 90 in FIG. 6 takes the type having the UI in FIG. 4 as an example. The conference room terminal 90 includes a CPU 601, ROM 602, RAM 603, EEPROM 604, CMOS sensor 605, acceleration / direction sensor 606, and media drive 608.

  The CPU 601 controls the overall operation of the conference room terminal 90. The ROM 602 stores basic input / output programs. The RAM 603 is used as a work area for the CPU 601. The EEPROM 604 reads or writes data according to the control of the CPU 601. The CMOS sensor 605 captures a subject according to the control of the CPU 601 and obtains image data. The acceleration / direction sensor 606 is an electronic magnetic compass, a gyrocompass, an acceleration sensor, or the like that detects geomagnetism.

  The media drive 608 controls reading or writing (storage) of data with respect to the medium 607 such as a flash memory. The media drive 608 is configured to be detachable from the media 607 on which data that has already been recorded is read or data is newly written and stored.

  The EEPROM 604 stores a program 604p executed by the CPU 601. The program 604p is application software or an OS for executing various processes in the embodiment. The program 604p may be distributed in a state stored in the medium 607 or the like, or may be distributed from a server for program distribution.

  The CMOS sensor 605 is a charge-coupled element that converts light into electric charge and digitizes the image of the subject. The CMOS sensor 605 may be, for example, a CCD (Charge Coupled Device) sensor as long as it can image a subject. The CMOS sensor 605 can read a barcode or a two-dimensional barcode.

  Furthermore, the conference room terminal 90 includes an RF tag reader / writer 622, an antenna I / F 623, and a vibration actuator 624. The RF tag reader / writer 622 performs communication according to a standard such as NFC (Near Field Communication).

  The vibration actuator 624 is a motor that vibrates the conference room terminal 90. For example, when the conference end time approaches, the conference room terminal 90 can vibrate to notify the prospective participant.

  Further, the conference room terminal 90 includes an audio input unit 609, an audio output unit 610, an antenna 611, a communication unit 612, a wireless LAN communication unit 613, a short-range wireless communication antenna 614, a short-range wireless communication unit 615, a display 616, and a touch panel 617. And a bus line 619.

  The voice input unit 609 converts voice into a voice signal. The audio output unit 610 converts the audio signal into audio. The communication unit 612 uses the antenna 611 to communicate with the nearest base station Na device by a wireless communication signal. The wireless LAN communication unit 613 performs wireless LAN communication conforming to the IEEE 802.11 standard.

  The short-range wireless communication unit 615 is a communication device that uses a short-range wireless communication antenna 614 and conforms to a communication standard such as Bluetooth (registered trademark) or Bluetooth Low Energy (registered trademark).

  The display 616 is a liquid crystal, an organic EL, or the like that displays a subject image, various icons, and the like. The touch panel 617 is placed on the display 616 and configured by a pressure-sensitive or electrostatic panel, and detects a touch position on the display 616 by touching with a finger, a touch pen, or the like. A bus line 619 is an address bus, a data bus, or the like for electrically connecting the above parts.

  The conference room terminal 90 includes a dedicated battery 618 and can be driven by either the battery 618 or a commercial power source. Note that the voice input unit 609 includes a microphone for inputting voice. The audio output unit 610 includes a speaker that outputs audio.

<< Hardware configuration diagram of electronic device 70 >>
FIG. 7 is an example of a hardware configuration diagram of an electronic blackboard as an example of the electronic device 70. As shown in FIG. 7, the electronic blackboard includes a CPU 101 that controls the operation of the entire electronic blackboard, a ROM 102 that stores a program used to drive a CPU such as an IPL, a RAM 103 that is used as a work area for the CPU 101, a program It includes an SSD 104 that stores 104p, a network controller 105 that controls communication with the internal network, and an external storage controller 106 that controls communication with the USB memory 5.

  The electronic blackboard also has an external video interface 111 that captures a still image or a moving image displayed on the display of the PC 6 by the PC 6. In addition, the GPU 112 that specializes in graphics (image processing of a screen displayed on the display 3), and a display controller 113 that controls and manages screen display in order to output video from the GPU 112 to the display 3 and the video conference terminal 7. It has.

  The electronic blackboard further includes a sensor controller 114 that controls the processing of the touch panel, and a touch panel 115 that detects that the indicator 4 and the hand H are in contact with the display 3. The electronic blackboard also includes an electronic pen controller 116. The electronic pen controller 116 communicates with the indicator 4 to determine whether or not the pen 4 of the indicator 4 touches the display 3 or touches the bottom of the pen. The electronic pen controller 116 may determine not only the pen tip and the pen butt, but also the presence or pressure of the portion of the indicator 4 that is gripped by the user or the other indicator 4 portion.

  Further, the electronic blackboard is electrically connected to the CPU 101, ROM 102, RAM 103, network controller 105, external storage controller 106, external video interface 111, GPU 112, sensor controller 114, and electronic pen controller 116 as shown in FIG. A bus line 120 such as an address bus or a data bus for connection is provided.

<About functions>
FIG. 8 is an example of a functional block diagram illustrating the functions of the reservation management server 20, the chat server 10, the conference management server 30, and the terminal device 60 in a block form.

<< Reservation management server 20 >>
The reservation management server 20 includes a communication unit 21 and a reservation information management unit 22. Each of these functional units included in the reservation management server 20 is realized by any one of the components shown in FIG. 5 operating according to a command from the CPU 201 according to the program 209p expanded from the HDD 209 to the memory 202. Function or means.

  The communication unit 21 transmits / receives various information to / from the conference management server 30. In the present embodiment, a request for reservation information is received from the conference management server 30, and this reservation information is transmitted to the conference management server 30. The communication unit 21 is realized by the CPU 201 in FIG. 5 executing the program 209p and controlling the network driver 205, and the like.

  The reservation information management unit 22 manages reservation information registered by the user. The reservation information management unit 22 reads the reservation information of the conference room requested from the conference management server 30 from the reservation information DB 291 and transmits it to the conference management server 30. It is assumed that a general Web application is used as a method for a prospective participant to reserve a conference room in the reservation management server 20. An example of a screen displayed on the terminal device 60 of the prospective participant of the Web application is shown in FIG. The reservation information management unit 22 is realized by the CPU 201 in FIG. 5 executing the program 209p.

  In addition, the reservation management server 20 has a storage unit 29. The storage unit 29 is realized by the memory 202 and the HDD 209 in FIG. The storage unit 29 stores a reservation information DB 291 (Data Base).

表１は予約情報ＤＢ２９１に記憶されている予約情報の一例を示す。予約情報は会議室の予約状況を管理するための情報である。予約情報には、予約ＩＤに対応付けて予約者アカウント、会議名、会議室ＩＤ、開始時刻、終了時刻、及び、参加予定者アカウントの各項目が登録されている。予約ＩＤは予約情報の１レコードを識別する識別情報（予約識別情報）である。ＩＤはIdentificationの略であり識別子や識別情報という意味である。ＩＤは複数の対象から、ある特定の対象を一意的に区別するために用いられる名称、符号、文字列、数値又はこれらのうち１つ以上の組み合わせをいう。予約ＩＤ以外のＩＤについても同様である。予約者アカウントは会議室を予約した参加予定者のアカウントである。会議名は参加予定者が任意に付与した会議の名称である。会議室ＩＤは社内ネットワークにある会議室を識別する識別情報であり会議管理サーバ３０により付与されている。開始時刻は会議室が予約された時間帯の始期（会議が開始される時刻）であり、終了時刻は会議室が予約された時間帯の周期（会議が終わる時刻）である。参加予定者アカウントは会議に参加する予定の参加予定者のアカウントである。なお、表１のアカウントはいずれも予約管理サーバ２０が発行したアカウントである。

Table 1 shows an example of reservation information stored in the reservation information DB 291. The reservation information is information for managing the reservation status of the conference room. In the reservation information, items of a reservation person account, a meeting name, a meeting room ID, a start time, an end time, and a prospective participant account are registered in association with the reservation ID. The reservation ID is identification information (reservation identification information) for identifying one record of the reservation information. ID is an abbreviation for Identification and means an identifier or identification information. ID refers to a name, a code, a character string, a numerical value, or a combination of one or more of these used to uniquely distinguish a specific target from a plurality of targets. The same applies to IDs other than the reservation ID. The reservation account is an account of a prospective participant who reserved the conference room. The conference name is the name of the conference arbitrarily given by the prospective participant. The conference room ID is identification information for identifying a conference room in the in-house network and is given by the conference management server 30. The start time is the start of the time zone when the conference room is reserved (the time when the conference is started), and the end time is the cycle of the time zone when the conference room is reserved (the time when the conference ends). The prospective participant account is an account of a prospective participant who is scheduled to participate in the conference. The accounts in Table 1 are all issued by the reservation management server 20.

<< Chat server 10 >>
The chat server 10 includes a communication unit 11 and a text processing unit 12. Each of these functional units included in the chat server 10 is realized by any one of the constituent elements shown in FIG. 5 operating according to a command from the CPU 201 according to the program 209p expanded from the HDD 209 to the memory 202. It is a function or means.

  The communication unit 11 transmits and receives various types of information to and from the conference management server 30. In the present embodiment, the conference management server 30 receives information related to conference room reservation, information for identifying a notification robot, and information for specifying a group to notify (the information for identifying this notification robot is the conference management server 30). When the notification robot is created, it is notified in advance from the chat server 10 as identification information of the notification robot). The prospective participant transmits information indicating that the conference room reservation has been read, or a response of the prospective participant to the displayed conference room reservation information, to the conference management server 30. The communication unit 11 is realized by the CPU 201 in FIG. 5 executing the program 209p and controlling the network driver 205, and the like.

  The text processing unit 12 identifies a group to be notified from the group information DB 191 in Table 2 based on the information for identifying the notification robot notified from the conference management server 30 and the information for specifying the notification destination group, and the group is designated as the notification robot. Send information about conference room reservations to prospective participants. Therefore, in principle, notifications are made for the number of participants. The text processing unit 12 can perform a so-called push notification. Examples of the mechanism include the following. The chat application 60a receives a push notification ID (token) from a server operated by an OS (Operating System) maker. In this server, a token and a device (terminal device 60) are linked. The chat application 60a registers the token and the account of the chat application 60a in the chat server 10. When the chat server 10 makes a push notification, the account of the chat application 60a is specified, so the associated token can be specified. The chat system designates a token and transmits notification contents to a server operated by the OS manufacturer. This server sends a push notification to the device (terminal device 60) associated with the token.

  The chat server 10 also has a storage unit 19. The storage unit 19 is realized by the memory 202 and the HDD 209 of FIG. The storage unit 19 stores a group information DB 191.

表２はグループ情報ＤＢ１９１に記憶されているグループ情報の一例を示す。グループ情報は同じグループに属するメンバのアカウントが登録された情報である。グループ情報には、チームＩＤに対応付けて、グループ名、メンバアカウント１〜ｎ（表２ではｎ＝４）、及び、通知ロボットアカウントが登録されている。

Table 2 shows an example of group information stored in the group information DB 191. Group information is information in which accounts of members belonging to the same group are registered. In the group information, a group name, member accounts 1 to n (n = 4 in Table 2), and a notification robot account are registered in association with the team ID.

  The team ID is an ID for identifying a team. In this embodiment, a plurality of members belong to a team (for example, a team for company A), and the team has a plurality of groups according to purposes (for example, a group for product A and a group for product B). Etc.), any one of the members belonging to the team belongs to the group (1 to all members belonging to the group). That is, the notification destination is specified by the team ID and the group name. However, since the identification method of the notification destination differs depending on the chat system, if there is identification information that can uniquely identify the group, only that information may be specified, or three or more pieces of information may be specified.

  The group name is the name of the group with which the chat system shares text, and its uniqueness is guaranteed. The member accounts 1 to n are group member accounts, which are issued by the chat server 10. In this embodiment, a notification robot is registered as a member for notifying information related to conference room reservation. The notification robot can be said to be an agent of the conference management server 30 or a fictitious member. A notification (text) of the notification robot is transmitted to the terminal devices 60 of the member accounts 1 to n.

<< Conference Management Server 30 >>
The conference management server 30 includes a communication unit 31, an information association unit 32, a reservation information acquisition unit 33, a notification determination unit 34, a control information generation unit 35, a control information response unit 36, a conference information notification unit 37, and a check-in management unit 38. And an initial setting unit 39. Each of these functional units included in the conference management server 30 is realized by any one of the constituent elements illustrated in FIG. 5 operating according to a command from the CPU 201 according to the program 209p loaded from the HDD 209 to the memory 202. Function or means. The program 209p is distributed from a program distribution server or distributed in a state stored in a storage medium.

  The communication unit 31 transmits / receives various information to / from the reservation management server 20, the chat server 10, the registration terminal 50, and the terminal device 60. In the present embodiment, the reservation information is received from the reservation management server 20, the information regarding the conference room reservation is transmitted to the chat server 10, the group in which the notification robot is registered is received from the registration terminal 50, and the chat system of the chat system is received from the terminal device 60. Accepts associations between groups and accounts. In addition, it communicates with the conference room terminal 90. The communication unit 31 is realized by the CPU 201 in FIG. 5 executing the program 209p and controlling the network driver 205, and the like.

  The information association unit 32 mainly performs processing related to pre-registration work. In other words, the registration of the domain is accepted from the registration terminal 50 and registered in the customer domain DB 495, and the group name of the chat system transmitted from the terminal device 60 and the account of the reservation management server 20 are associated with each other and registered in the association information DB 491. Details will be described later. The information association unit 32 is realized by the CPU 201 in FIG. 5 executing the program 209p.

  The reservation information acquisition unit 33 specifies an account of a customer who uses the facility reservation system 100, acquires reservation information from the reservation management server 20, and registers it in the reservation information DB. Of the reservation information held by the reservation management server 20, reservation information for a predetermined period from the present is acquired. The predetermined period is determined by how far ahead the conference room reservation information is notified. The reservation information acquisition unit 33 is realized by the CPU 201 in FIG. 5 executing the program 209p.

  The notification determination unit 34 determines whether there is a reservation with a start time that satisfies the conditions to be notified in the reservation information. For example, the notification setting DB 496 is referred to, and it is determined that the notification is made when the set date and time comes back from the start time of the reservation. For example, when a notification robot is divided for each role, such as a reminder notification robot or a reservation reception notification robot, the notification robot is specified according to the process. The notification determination unit 34 is realized by the CPU 201 in FIG. 5 executing the program 209p.

  When it is determined that the notification determination unit 34 notifies, the conference information notification unit 37 designates information for identifying the notification robot and information for specifying the notification destination group, and notifies the chat server 10 of the information related to the conference room reservation. To request. In addition, although notification is performed by dividing into several times, meeting identification information is included in at least one of the notifications. The conference identification information is information for the conference management server 30 to confirm that the prospective participant has the right to use in the time slot when the reserved conference room is reserved. The conference information notification unit 37 generates conference identification information at least before final notification. The conference identification information is registered in the conference identification information DB 494. The conference information notification unit 37 is realized by the CPU 201 in FIG. 5 executing the program 209p.

  The control information generation unit 35 refers to the reservation information, generates control information for the electronic device 70, and registers the control information in the control information DB 497. For example, control information for turning on the power of the electronic device 70 is generated a few minutes before the start time of the conference, and control information for turning off the power of the electronic device 70 is generated when a checkout is detected. The control information is stored in the control information DB 497. The control information generation unit 35 is realized by the CPU 201 in FIG. 5 executing the program 209p.

  The control information response unit 36 receives an inquiry as to whether there is control information from the conference room terminal 90 of the conference room, refers to the control information DB 497, and transmits control information corresponding to the conference room to the conference room terminal 90. The control information response unit 36 is realized by the CPU 201 in FIG. 5 executing the program 209p.

  The check-in management unit 38 communicates with the conference room terminal 90 to determine whether or not the check-in is permitted, and registers the status of the conference in the conference management information DB 493. Check-in is recognized when a set of a conference room ID and conference identification information is registered in the conference identification information DB 494 and is 5 to 10 minutes before the start time of the conference specified by the reservation ID. The check-in management unit 38 is realized by the CPU 201 in FIG. 5 executing the program 209p.

  The initial setting unit 39 performs processing related to the initial setting of the conference room terminal 90. For example, the conference room list is provided to the registration terminal 50 of the manager of the facility reservation system 100, the conference room ID and the conference room name of the conference room selected by the manager of the facility reservation system 100 are specified, and the conference management The URL (Uniform Resource Locator. Address information of the conference management server 30) of the server 30 is transmitted to the registration terminal 50. The check-in management unit 38 is realized by the CPU 201 in FIG. 5 executing the program 209p.

  The conference management server 30 also has a storage unit 49. The storage unit 49 is realized by the memory 202 and the HDD 209 in FIG. The storage unit 49 stores a correspondence information DB 491, a conference management information DB 493, a conference identification information DB 494, a customer domain DB 495, a notification setting DB 496, and a control information DB 497.

表３は対応付情報ＤＢ４９１に記憶されている対応付情報の一例を示す。対応付情報は予約管理システムのアカウントとチャットシステムのグループ名を対応付ける情報である。対応付情報は、グループ名、チームＩＤ及びメンバアカウント１〜ｎ（図ではｎ＝４）の各項目を有する。グループ名はチャットシステムのグループ名である。メンバアカウント１〜ｎには予約管理サーバ２０が発行した各参加予定者のアカウントが登録される。また、表３に示すようにチャットシステムのアカウントが登録されてよい。グループに対して通知を行うためには予約管理サーバに対して会議を予約したユーザの予約管理サーバのアカウントと通知先のグループ及びチャンネルを特定するための情報（本実施形態ではチームＩＤとグループ（チャンネル）名）があればよく、必ずしもグループに所属するすべてのメンバのアカウントが登録されている必要はない。ただし、個人ユーザ宛に通知する場合、それぞれのチャットシステムのアカウント情報が必要なため、表３のように登録されていてもよい。

Table 3 shows an example of the association information stored in the association information DB 491. The association information is information that associates an account of the reservation management system with a group name of the chat system. The association information includes items of group name, team ID, and member accounts 1 to n (n = 4 in the figure). The group name is the group name of the chat system. The account of each prospective participant issued by the reservation management server 20 is registered in the member accounts 1 to n. Also, as shown in Table 3, a chat system account may be registered. In order to notify the group, the reservation management server account of the user who reserved the conference with the reservation management server and information for specifying the group and channel of the notification destination (in this embodiment, the team ID and group ( There is no need to register the accounts of all members who belong to the group. However, when notification is made to an individual user, account information of each chat system is required, so registration may be made as shown in Table 3.

表４は会議管理サーバ３０の会議管理情報ＤＢ４９３が記憶する予約情報の一例を示す。表４では表１の予約情報ＤＢ２９１との相違を説明する。表４の予約情報はステータスの項目を有する。ステータスは、予約の状況を意味する。例えば、会議室の予約に関する情報の通知済み、利用確定、チェックイン済み、チェックアウト、又は、キャンセル（取り消し）等の状況が登録される。

Table 4 shows an example of reservation information stored in the conference management information DB 493 of the conference management server 30. Table 4 explains differences from the reservation information DB 291 in Table 1. The reservation information in Table 4 has a status item. The status means the reservation status. For example, a status such as notified of conference room reservation, confirmed use, checked in, checked out, or canceled (cancelled) is registered.

表５は会議識別情報ＤＢ４９４に記憶されている会議識別情報管理情報の一例を示す。会議識別情報管理情報は会議室の予約ごとに会議識別情報を管理する情報である。会議識別情報管理情報は、予約ＩＤ、会議室ＩＤ、及び、会議識別情報の各項目を有する。これらについては既出であるため説明は省略する。なお、予約ＩＤが登録されているのは、同じ会議室の予約を識別するためである。

Table 5 shows an example of conference identification information management information stored in the conference identification information DB 494. Conference identification information management information is information for managing conference identification information for each conference room reservation. The conference identification information management information includes items of reservation ID, conference room ID, and conference identification information. Since these have already been described, description thereof will be omitted. The reservation ID is registered in order to identify reservations for the same conference room.

表６は顧客ドメインＤＢ４９５に記憶されている顧客ドメイン情報の一例を示す。顧客ドメイン情報は顧客のドメインと顧客の管理者のアカウントを管理する情報である。顧客ドメイン情報には顧客のドメイン名と顧客の管理者アカウントが対応付けて登録されている。表６の顧客のドメインは予約管理サーバ２０が発行したアカウント（メールアドレス）のドメインである。また、管理者アカウントは、顧客の管理者（代表する）のアカウントである。なお、表６のアカウントは予約管理サーバ２０が発行したものである。

Table 6 shows an example of customer domain information stored in the customer domain DB 495. Customer domain information is information for managing customer domains and customer administrator accounts. In the customer domain information, a customer domain name and a customer administrator account are registered in association with each other. The customer domain in Table 6 is a domain of an account (email address) issued by the reservation management server 20. The administrator account is an account of a customer administrator (representative). The accounts in Table 6 are issued by the reservation management server 20.

表７は通知設定ＤＢ４９６に記憶されている通知設定情報の一例を示す。通知設定情報は顧客ごとに通知に関する設定を保持する。通知設定情報には、顧客ドメイン名と通知設定が対応付けて登録されている。通知設定には、会議の開始時刻のどのくらい前に、会議室の予約に関する情報を通知するかのタイミングが設定されている。あるいは決まった日時が設定されていてもよい。また、タイミングは１つである必要はなく、１つの顧客に複数回の通知設定が登録されていてもよい。

Table 7 shows an example of notification setting information stored in the notification setting DB 496. The notification setting information holds a setting regarding notification for each customer. In the notification setting information, the customer domain name and the notification setting are registered in association with each other. In the notification setting, the timing of notifying the information related to the conference room reservation is set how long before the start time of the conference. Alternatively, a fixed date and time may be set. Also, the timing need not be one, and a plurality of notification settings may be registered for one customer.

表８は制御情報ＤＢ４９７に記憶されている制御情報の一例を示す。制御情報は会議室の電子機器７０を制御するための情報である。制御情報は、会議室ＩＤ、及び、制御内容の各項目を有する。制御内容は、電子機器７０の具体的な制御方法である。会議管理サーバ３０は電子機器７０ごとに詳細な制御内容を設定できる。また、制御する時刻が登録されないのは、社外ネットワークの会議管理サーバ３０から会議室端末９０に送信することが困難であり、会議室端末９０が会議管理サーバ３０にアクセスし、この時、制御情報が生成されていれば制御内容を送信するからである。

Table 8 shows an example of the control information stored in the control information DB 497. The control information is information for controlling the electronic device 70 in the conference room. Control information has each item of meeting room ID and control content. The control content is a specific control method of the electronic device 70. The conference management server 30 can set detailed control contents for each electronic device 70. In addition, it is difficult to transmit the time to be controlled from the conference management server 30 of the external network to the conference room terminal 90, and the conference room terminal 90 accesses the conference management server 30, and at this time, the control information This is because the control content is transmitted if is generated.

<< Registered terminal 50 >>
The registration terminal 50 includes a communication unit 51, an operation reception unit 52, and a display control unit 53. Each of the functional units included in the registration terminal 50 is realized by any one of the constituent elements illustrated in FIG. 5 operating according to a command from the CPU 201 according to the program 209p expanded from the HDD 209 to the memory 202. It is a function or means. The program 209p is distributed from a program distribution server or distributed in a state stored in a storage medium.

  The functions of the communication unit 51, the operation reception unit 52, and the display control unit 53 are the same as those of the terminal device 60, and details will be described together with the terminal device 60.

<< Terminal device 60 >>
FIG. 9 is an example of a functional block diagram illustrating the functions of the terminal device 60, the conference room terminal 90, and the electronic device 70 in a block shape. For convenience of explanation, the functional block diagram of the conference management server 30 is shown again.

  The terminal device 60 includes a communication unit 61a, an operation reception unit 61b, a chat communication unit 62, a text display unit 63, an application communication unit 67, a server communication unit 65, a display control unit 66, an application communication unit 67, and a terminal communication unit 68. Have Each of these functional units included in the terminal device 60 is realized by any one of the constituent elements illustrated in FIG. 5 operating according to a command from the CPU 201 according to the program 209p expanded from the HDD 209 to the memory 202. It is a function or means. The program 209p is distributed from a program distribution server or distributed in a state stored in a storage medium. Since the chat application 60a and the conference application 60b are operating on the terminal device 60, the program 209p includes the chat application 60a and the conference application 60b.

  The communication unit 61a transmits and receives various types of information to and from the conference management server 30. The communication unit 61a is realized by the CPU 201 in FIG. 5 executing the program 209p and controlling the network driver 205, and the like.

  The operation accepting unit 61 b accepts various operations of the prospective participant for the terminal device 60. The operation receiving unit is realized by the CPU 201 in FIG. 5 executing the program 209p to control the input device 210, and the like.

  The chat communication unit 62 of the chat application 60a transmits and receives various types of information to and from the chat server 10. In the present embodiment, information related to conference room reservation is received from the chat server 10 and the chat server 10 is notified whether the conference room is used or cancelled. The chat communication unit 62 is realized by the CPU 201 in FIG. 5 executing the program 209p and controlling the network driver 205, and the like.

  The text display unit 63 of the chat application 60a displays text (information related to conference room reservation) transmitted from the chat server 10. For example, the message origin is a notification robot, and text is displayed as if the notification robot had input. The text display unit 63 is realized by the CPU 201 in FIG. 5 executing the chat application 60a.

  The application communication unit 64 of the chat application 60a calls the conference application 60b and transmits the conference identification information to the conference application 60b. Since the chat server 10 transmits information identifying the conference application 60b to the terminal device 60 when notifying the information related to the conference room reservation, the chat application 60a designates the conference application 60b to the OS, and the conference identification information. Request notification of. The OS can start the conference application 60b. The application communication unit 64 is realized by the CPU 201 in FIG. 5 executing the chat application 60a.

  The server communication unit 65 of the conference application 60 b communicates with the conference management server 30. In the present embodiment, a two-dimensional code including conference identification information is acquired from the conference management server 30. The server communication unit 65 is realized by the CPU 201 in FIG. 5 executing the conference application 60b.

  The display control unit 66 of the conference application 60 b displays the above two-dimensional code and the like notified from the conference management server 30 on the LCD 206. The display control unit 66 is realized by the CPU 201 in FIG. 5 executing the conference application 60b and controlling the graphics driver.

  The application communication unit 67 of the conference application 60b acquires various types of information (such as conference identification information included in information related to conference room reservation) from the chat application 60a via the OS. The application communication unit 67 is realized by the CPU 201 in FIG. 5 executing the conference application 60b.

  The terminal communication unit 68 communicates with the conference room terminal 90 and transmits conference identification information and the like. The terminal communication unit 68 detects the presence of the conference room terminal 90 by short-range wireless communication such as Bluetooth (registered trademark), and transmits conference identification information when the conference room terminal 90 is detected. In addition, a function of displaying a two-dimensional code for the conference room terminal 90 is provided. The terminal communication unit 68 is realized by the CPU 201 in FIG. 5 executing the conference application 60b.

<< Conference room terminal 90 >>
The conference room terminal 90 includes a server communication unit 91, a terminal device communication unit 92, an operation reception unit 93, a display control unit 94, and an electronic device communication unit 95. Each of these functional units included in the conference room terminal 90 is realized by any one of the constituent elements shown in FIG. 6 operating according to a command from the CPU 601 according to the program 604p expanded from the EEPROM 604 to the RAM 603. Function or means. The program 604p is distributed from a server for program distribution or distributed in a state stored in a storage medium.

  The server communication unit 91 communicates with the conference management server 30. Since the conference room terminal 90 exists in the in-house network, it is difficult to communicate with the conference room terminal 90 from the conference management server 30. For this reason, the server communication unit 91 communicates with the conference management server 30 by a communication technique such as polling (periodically communicating with the conference management server 30) or WebSocket. The server communication unit 91 of the present embodiment transmits the conference identification information and the conference room ID received by the terminal device communication unit 92 from the terminal device 60 to the conference management server 30. In addition, it is possible to receive information such as the current time and conference room reservation information for the day. Further, the server communication unit 91 receives control information from the conference management server 30. The server communication unit 91 is realized by the CPU 601 in FIG. 6 executing the program 604p and controlling the wireless LAN communication unit 613.

  The terminal device communication unit 92 communicates with the terminal device 60. In this embodiment, meeting identification information and the like are received. The terminal device communication unit 92 is realized by the CPU 601 in FIG. 6 executing the program 604p and controlling the short-range wireless communication unit 615 or the RF tag reader / writer 622.

  The electronic device communication unit 95 communicates with the electronic device 70. In the present embodiment, the control information received by the server communication unit 91 is transmitted to the electronic device 70. The electronic device communication unit 95 is realized by the CPU 601 in FIG. 6 executing the program 604p and controlling the wireless LAN communication unit 613.

  The display control unit 94 displays a screen generated by the terminal application 90 a on the display 616. Menus such as check-in and check-out are displayed on this screen. The display control unit 94 is realized by the CPU 601 in FIG. 6 executing the program 604p to control the display 616, and the like.

  The operation reception unit 93 receives various operations on the conference room terminal 90. The operation receiving unit 93 is realized by the CPU 601 in FIG. 6 executing the program 604p and controlling the touch panel 617, and the like.

  The conference room terminal 90 has a storage unit 99. The storage unit 99 is realized by the ROM 602 and the EEPROM 604 in FIG. The storage unit 99 stores the conference room ID and the IP address of the electronic device 70.

<< Electronic equipment 70 >>
The electronic device 70 includes a basic function unit 71, a control unit 72, and a communication unit 73. Each of these functional units included in the electronic device 70 is a function realized by any one of the constituent elements shown in FIG. 7 operating according to a command from the CPU 101 according to the program 104p expanded from the SSD 104 to the RAM 103. Or means. The program 104p is distributed from a server for program distribution or distributed in a state stored in a storage medium.

  The communication unit 73 communicates with the conference room terminal 90. In this embodiment, control information is received. The communication unit 73 is realized by the CPU 101 in FIG. 7 executing the program 104p and controlling the network controller 105, and the like.

  The control unit 72 controls the entire electronic device 70. In the present embodiment, the power supply of the electronic device 70 is controlled to be turned on or off according to the control information. The control unit 72 is realized by the CPU 101 in FIG. 7 executing the program 104p.

  The basic function unit 71 provides basic functions of the electronic device 70. That is, the user's handwritten stroke is displayed, or the video of the PC is displayed on the display 3. The basic function unit 71 is realized by the CPU 101 in FIG. 7 executing the program 104p and controlling the hardware elements in FIG.

<Reservation of conference room>
The conference room reservation will be described with reference to FIG. FIG. 10 is an example of a conference room reservation screen 401 provided by the reservation management server 20 and displayed by the terminal device 60. The reservation screen 401 includes a conference name input field 402, a start time input field 403, an end time input field 404, and a conference room input field 405. The prospective participant logs in to the reservation management server 20 with the account of the reservation management server 20 and inputs necessary items on the reservation screen 401. Since the conference room input column 405 displays the conference room name and conference room ID that can be selected from the pull-down menu, the user can select the conference room by selecting the conference room name.

  In the conference room input field 405, “connection ID: XXX... X” is set. The connection ID is connection destination information for the electronic device 70 at one site to connect to the other site. In terms of telephone, it corresponds to a telephone number. That is, it is information for connecting the electronic device 70 at one site and the electronic device 70 at the other site. The connection destination information is information for identifying the remote conference device as the connection destination, and the connection between the remote conference devices is performed using the connection destination information. The connection destination information may be information that can identify the connection destination, may be identification information of the remote conference device itself, may be identification information on the network of the remote conference device itself, such as an IP address, or a remote conference such as a user ID. Identification information associated with a user who uses the apparatus may be used.

  The prospective participant sets the connection ID of the electronic device 70 installed in the other (connection destination) conference room on the reservation screen 401 of one conference room. Since one of the electronic devices 70 may be connected to the connection destination, it is not necessary to set the connection ID of the electronic device 70 installed in one conference room on the reservation screen 401 of the other conference room. However, the connection ID may be set on the reservation screen 401 of both conference rooms where the remote conference is performed.

  In addition, a calendar selection field 406 is displayed on the reservation screen 401. A calendar selection column 406 is a column in which the user selects a calendar shared by the group. Therefore, the user can use different calendars.

<Pre-registration screen example>
An example of a screen that is input by the administrator or the prospective participant of the facility reservation system 100 in the prior registration work described in FIG. 1 will be described.

  FIG. 11 is an example of a registration work initial screen 411 displayed on the registration terminal 50 or the terminal device 60. The registration work initial screen 411 is a Web page provided by the conference management server 30, for example. The registration work initial screen 411 includes a notification robot addition button 412, an administrator login button 413, and a reservation management server login button 414. When the add notification robot button 412 is pressed, a transition is made to the notification robot registration screen 421 of FIG. 12, and when the administrator login button 413 is pressed, the transition is made to the domain management screen 431 of FIG. When is pressed, the screen shifts to the account association screen 441 in FIG.

  FIG. 12 shows an example of the notification robot registration screen 421 displayed on the registration terminal 50. The notification robot registration screen 421 is provided by the chat server 10. The notification robot registration screen 421-1 in FIG. 12A has a chat system team ID input field 422 and a button 423 that follows. The administrator of the facility reservation system 100 inputs the team ID to which the notification robot is added in the team ID input field 422 and presses the subsequent button 423. The group name of the addition destination is a group of prospective participants who will hold the conference.

  The notification robot registration screen 421-2 in FIG. 12B has an account input field 424 and a password input field 425. The administrator of the facility reservation system 100 inputs the account and password of the member belonging to the team ID input in FIG. That is, the authority to add a notification robot to the team is authenticated.

  The notification robot registration screen 421-3 in FIG. 12C includes a notification destination account display field 426 and an authentication button 427 that are notified by the notification robot. The notification destination account display field 426 may select a specific account address or a group. By pressing the pull-down key 426a, accounts of other members of the group are also displayed. When the authentication button 427 is pressed, a notification robot is added.

  The notification robot registration screen 421-4 in FIG. 12D has a message input field 428. The message input column 428 is a column in which the administrator of the facility reservation system 100 inputs the text that the notification robot speaks on a trial basis. Thereby, the manager (and each member) of the facility reservation system 100 can confirm whether or not the text input by the notification robot is notified to the members of the group.

  FIG. 13 shows an example of the domain management screen 431 displayed on the registration terminal 50. The domain management screen 431 is provided by the conference management server 30. The domain management screen 431 is a screen for an administrator of the facility reservation system 100 to set a customer domain that can use the facility reservation system 100. The facility reservation system 100 is used by a customer who has an account including a registered domain in part. The domain management screen 431-1 in FIG. 13A has an administrator account input field 432 and a password input field 433. The administrator of the facility reservation system 100 logs into the conference management server 30 with the administrator account and password of the facility reservation system 100.

  13B and 13C are domain management screens 431-2, and FIG. 13C is an enlarged view of FIG. 13B. The domain management screen 431-2 includes a domain name input field 435, an account input field 436, and a registration button 437. In the domain name input field 435, the domain of the customer who uses the reservation management server 20 is input. In the account input field 436, an account of an administrator of a customer who uses the reservation management server 20 is input.

  That is, the domain and account of the customer reservation management server 20 are registered in the conference management server 30. The customer logs in to the conference management server 30 using this account (issued by the reservation management server 20), and the conference management server 30 logs in to the reservation management server 20 with the registered account to obtain the reservation information and is registered. Notify booking account that includes domain.

  In FIGS. 13B and 13C, the domain is already registered as indicated by the check mark. As a result, the administrator of the facility reservation system 100 can register the domain simply by checking the check mark, and it is possible to avoid the occurrence of a domain spelling error.

  FIG. 14 shows an example of the account association screen 441 displayed on the terminal device 60. The account association screen 441 is a Web page provided by the conference management server 30. The account association screen 441 is a screen for associating the chat system group name with the reservation management system account. In the account correspondence screen 441-1 in FIG. 14A, an account of a reservation management system of a specific user is input. This account is issued by the reservation management server 20. The prospective participant selects the account of the manager of the company (customer) to which he belongs and logs in.

  The account correspondence screen 441-2 in FIG. 14B is an account 443 of the logged-in customer administrator (account of the reservation management server 20), a chat system selection field 444, an account input field 445 of the chat system, It has a team ID input field 446 and a chat system group name selection field 446-2. The prospective participant selects the chat system to which the notification robot is added in the chat system selection field 444. Enter your own account of the chat system in the account input field 445 of the chat system. The team ID of the chat system to which the notification robot is added is input to the team ID input field 446 of the chat system, and the group name is input to the group name selection field 446-2.

  An account association screen 441-3 in FIG. 14C shows a group name input screen of the chat system, and an account association screen 441-4 in FIG. 14D shows a login screen to the chat system. As shown in FIG. 12, the prospective participant designates the group name in the group name field 447, enters the chat system account in the account input field 448, and enters the password in the password input field 449 to log in to the chat system. FIG. 14B confirms that the input content is appropriate. If it can be confirmed, the conference management server 30 registers the group name and the account of the customer administrator in association with each other.

<Pre-registration sequence>
First, the token of the notification robot will be described. One notification robot may be present on the conference management server. The conference management server 30 performs the process of acquiring the notification robot token before the operation of the conference management server 30 is started.

  For example, in response to a request for adding a notification robot from the conference management server 30, the chat server 10 generates a notification robot and gives a unique token to the notification robot. The communication unit 11 of the chat server 10 transmits the token of the notification robot to the conference management server 30. The information association unit 32 of the conference management server 30 manages the token of the notification robot. Thereby, the conference management server 30 can transmit a notification as a notification robot.

  This token is information for the conference management server 30 to perform notification as a notification robot in the chat system, and serves as identification information for the notification robot.

  FIG. 15 is an example of a sequence diagram illustrating a procedure for registering the notification robot.

  S1: The server communication unit 91 of the registration terminal 50 transmits a notification robot addition request to the conference management server 30. This addition request is transmitted when the add button 412 is selected on the registration work initial screen 411 of FIG. 11 displayed by the conference management server 30.

  S2: The communication unit 31 of the conference management server 30 transmits the identification information of the notification robot to the chat server 10 together with the request for adding the notification robot to the team.

  S3: Thereby, the chat server 10 displays the notification robot registration screen 421-1 on the registration terminal 50.

  S4: The administrator of the equipment reservation system 100 inputs a group name on the notification robot registration screen 421-1. The operation reception unit 52 of the registration terminal 50 receives an input of the team ID, and the communication unit 51 transmits it to the chat server 10.

  S5: The chat server 10 receives the team ID and transmits a notification robot registration screen 421-2 to the registration terminal 50.

  S6: The communication unit 51 of the registration terminal 50 receives the notification robot registration screen 421-2 and the display control unit 53 displays it. The administrator of the facility reservation system 100 inputs the account name and password (one of the group members) of the chat system. The operation accepting unit 52 of the registration terminal 50 accepts the input of the account name and password of the chat system, and the communication unit 51 transmits to the chat server 10.

  S7: The chat server 10 authenticates when the account name and password of the chat system are received, and transmits a notification robot registration screen 421-3 to the registration terminal 50 when the authentication is established.

  S8: The communication unit 51 of the registration terminal 50 receives the notification robot registration screen 421-3, and the display control unit 53 displays it. The administrator of the equipment reservation system 100 presses the authentication button 427. The operation accepting unit 52 of the registration terminal 50 accepts pressing of the authentication button 427 and transmits authentication OK to the chat server 10.

  S9: The communication unit 11 of the chat server 10 receives the authentication OK and transmits the team ID input by the administrator of the facility reservation system 100 to the conference management server 30.

  S10: The information association unit 32 of the conference management server 30 manages the team ID and the token of the notification robot in association with each other.

  FIG. 16 is an example of a sequence diagram illustrating a procedure for registering an account of the customer reservation management server 20.

  S1: The administrator of the facility reservation system 100 operates the registration terminal 50 to access the conference management server 30, and displays the domain management screen 431-1.

  S2: The administrator of the facility reservation system 100 inputs the account name and password of the administrator of the facility reservation system 100 on the domain management screen 431-1. The operation reception unit 52 of the registration terminal 50 receives these inputs, and the communication unit 51 transmits the input to the conference management server 30.

  S3: When the authentication with the account name and password is established, the communication unit 31 of the conference management server 30 transmits the domain management screen 431-2 to the registration terminal 50.

  S4: The communication unit 51 of the registration terminal 50 receives the domain management screen 431-2 and the display control unit 53 displays it. The administrator of the facility reservation system 100 inputs the customer domain of the reservation management server 20 and the account of the customer administrator. The operation reception unit 52 of the registration terminal 50 receives the customer domain and account of the reservation management server 20, and the communication unit 51 transmits to the conference management server 30.

  S5: The communication unit 31 of the conference management server 30 receives the domain and account of the customer reservation management server 20, and the information association unit 32 associates the domain and account of the customer reservation management server 20 with the customer domain DB 495. sign up.

  FIG. 17 is an example of a sequence diagram illustrating a procedure for associating a chat system group with an account of the reservation management server 20.

  S1: The prospective participant operates the terminal device 60 to access the conference management server 30, and displays the account correspondence screen 441-1.

  S2: The prospective participant logs in by selecting the account name registered in FIG. Therefore, an account in the reservation management server 20 of the customer administrator is specified in the conference management server 30.

  S3: When the conference management server 30 permits the login, the account correspondence screen 441-2 is transmitted to the terminal device 60.

  S4: The prospective participant inputs the account name and group name of the chat system on the account correspondence screen 441-2. The operation reception unit 61 b of the terminal device 60 receives input of an account name, a group name, and a team ID, and the communication unit 61 a transmits these to the conference management server 30. The notification destination of the conference reserved for the reservation management server 20 by the account selected in step S2 is specified by the group name and the team ID.

  S5: The communication unit 31 of the conference management server 30 receives these, and the information association unit 32 redirects the terminal device 60 to the chat server 10 for verification of the account name and group name. As a result, the terminal device 60 displays the account association screen 441-3. This account correspondence screen 441 includes a team ID.

  S6: The operation accepting unit 61b of the terminal device 60 accepts the operation when the prospective participant operates, and the communication unit 61a transmits the team ID to the chat server 10.

  S7: The chat server 10 transmits the account correspondence screen 441-4 to the terminal device 60 in order to acquire the account of the member included in this team ID.

  S8: Participants will enter their chat system account name and password. The operation reception unit 61b of the terminal device 60 receives the input, and the communication unit 61a transmits the account name and password to the chat server 10.

  S9: The chat server 10 authenticates the account name and password of the chat system, and transmits to the conference management server 30 that it has been confirmed that the authentication has been established. In the figure, the redirect process in this case is omitted.

  S10: The information association unit 32 of the conference management server 30 associates information for identifying the group including the team ID and the group name with the account of the reservation management server 20 specified in step S2 in the association information DB 491.

  When the customer reserves the conference room with the reservation management server 20 through the above processing, the reservation management server 20 can notify each terminal device 60 of the prospective participant via the chat server 10 of the information related to the conference room reservation.

<Timing for notification of conference room reservation>
FIG. 18 is an example of a diagram illustrating the timing of notification of information related to conference room reservation.
Timing 1: When the notification timing registered in the notification setting DB 496 is reached, first, the conference information notification unit 37 of the conference management server 30 notifies the terminal device 60 of information related to conference room reservation.
Timing 2: When there is no response from the prospective participant for 10 minutes, the conference information notification unit 37 automatically cancels the reservation management server 20.
Timing 3: When there is a response that the conference room is used, the conference information notification unit 37 of the conference management server 30 notifies the information regarding the conference room reservation again 10 minutes before the start time of the conference. In this embodiment, meeting identification information is transmitted as an example.
Timing 4: Conference start time Timing 5: When the conference management server 30 does not receive a check-in notification from the conference room terminal 90 even after 10 minutes have elapsed from the start time, the check-in management unit of the conference management server 30 38 automatically cancels the reservation management server 20.

  If one of the prospective participants of the conference responds to the information related to the conference room reservation, the reservation is not canceled. However, the response of all the prospective participants may be required, and more than half of the responses may be required.

<Processing notification of information related to conference room reservation>
FIG. 19 is an example of a sequence diagram illustrating a procedure in which the conference management server 30 notifies information related to conference room reservation.

  S1: The reservation information acquisition unit 33 of the conference management server 30 acquires an arbitrary customer domain from the customer domain DB 495.

  S2: Next, the reservation information acquisition unit 33 reads the notification setting of the customer from the notification setting DB 496.

  S3: The reservation information acquisition unit 33 acquires the reservation information from the reservation management server 20 by logging in with the account of the customer domain DB 495 input in FIG. The acquisition period is a period set as a notification timing in the notification setting. For example, when notifying information on conference room reservation one month in advance, reservation information for one month ahead is acquired.

  S4: The reservation information acquisition unit 33 stores the reservation information acquired from the reservation management server 20 in the conference management information DB 493.

  S5: The notification determination unit 34 refers to the reservation information to determine whether it is time to notify (remind) information related to the conference room reservation. Details will be described with reference to the flowchart of FIG.

  FIG. 20 is an example of a flowchart of a procedure in which the notification determining unit 34 determines whether to notify information related to conference room reservation.

  The notification determination unit 34 searches the reservation information for the domain name of the customer in the customer domain DB 495 (S10). Since the reservation information is acquired by designating the domain of the customer, all the reservation person accounts or the prospective participant accounts of the reservation information include the domain. However, any reservation information for a predetermined period may be acquired and the notification determination unit 34 may search in the customer domain. Here, it is assumed that the reservation information includes the reservation user account or the prospective participant account including the customer domain name in the customer domain DB 495.

  Next, the notification determination unit 34 determines whether there is reservation information at a notification timing (S20). In other words, it is determined that the notification is to be made if it is calculated backward from the conference room reservation start time and matches the notification setting (or if it has passed but has not been notified). If the determination in step S20 is No, no notification is given, and the process in FIG. 20 ends.

  When the determination in step S20 is Yes, the notification determination unit 34 searches the association information DB 491 for the reservation person account acquired from the reservation information, and specifies information for identifying the group including the team ID and the group name (S30). The conference management server 30 can notify the group by specifying the team ID, the group name (information for identifying the group), and the token of the notification robot.

  The meeting information notifying unit 37 notifies information on the conference room reservation to the prospective participants as a notification robot using information for identifying the group including the identified team ID and group name (S40).

  FIG. 21 is an example of a sequence diagram in which the conference management server 30 notifies the prospective participants of information related to conference room reservation.

  S1: The conference information notification unit 37 sends a message (information regarding conference room reservation) to the chat server 10 by specifying the team ID and group name specified together with the token indicating that the conference management server 30 is a notification robot. . In addition, since meeting identification information should just be produced before the notification regarding the information regarding a conference room reservation, you may transmit at this timing (timing 1 of FIG. 18). In addition, a reservation ID is included in order to specify which reservation the response from the terminal device 60 is for. The conference information notification unit 37 sets the status of the conference management information DB 493 as notified.

  S2: The text processing unit 12 of the chat server 10 is a designated token notification robot, and transmits a message to the terminal device 60 of the member specified by the team ID and the group name.

  S3: The chat communication unit 62 of the terminal device 60 receives the message, and the text display unit 63 displays the message. This message includes a button used as a display component and a cancel button as shown in FIG. When the prospective participant presses the button used by the message or the cancel button, the operation receiving unit 61b of the terminal device 60 receives the press.

  S4: The communication unit 61a of the terminal device 60 transmits to the chat server 10 that the button to be used has been pressed or that the cancel button has been pressed and the reservation ID.

  S5: The communication unit 21 of the chat server 10 transmits to the notification robot of the conference management server 30 that the button to be used has been pressed or that the cancel button has been pressed and the reservation ID. The communication unit 31 of the conference management server 30 receives that the button to be used has been pressed and the reservation ID, and the conference information notification unit 37 detects that the reservation specified by the reservation ID has been confirmed by the prospective participant. The conference information notification unit 37 sets “confirmed” in the status of the conference management information DB 493. When the cancel button is pressed, the conference information notifying unit 37 sets the cancel in the status of the conference management information DB 493.

  S6: Step S6 is executed when the reservation is canceled. The conference information notifying unit 37 designates the reservation ID and transmits the reservation ID to the reservation management server 20. This prevents empty reservations.

  Furthermore, the conference information notification unit 37 can notify the prospective participant via the notification robot that the reservation has been confirmed or canceled.

<Text display screen>
FIG. 22 shows an example of information related to conference room reservation displayed on the terminal device 60. FIG. 22A is an example of information regarding conference room reservation notified at the timing of the notification setting DB 496. Such a message is displayed, for example, at timing 1 in FIG.
"2017-05-18 20:47:00 A meeting (regular) is reserved in the conference room A. Select" Use "to use it as reserved," Cancel "otherwise. Please note that if there is no response for 10 minutes, the reservation will be canceled automatically. "
The prospective participant can take an appropriate action such as pressing a button 451 or a cancel button 452 to be used by viewing the message. If neither the button 451 to be used nor the cancel button 452 is pressed, the conference information notification unit 37 of the conference management server 30 automatically cancels the reservation of the conference room in 10 minutes, so that the empty reservation can be reduced.

  Note that pressing of the button 451 to be used and the cancel button 452 is notified to the conference management server 30. The button 451 to be used and the cancel button 452 are respectively associated with the contents of the button, the URL (address information) of the conference management server 30 and the reservation ID (embedded and linked). The meeting information notification unit 37 of the server 30 can detect what kind of response to which reservation information.

  In addition, when the button 451 used by the prospective participant is pressed, the conference information notification unit 37 transmits to the chat application 60 a of the terminal device 60 a message 453 that is confirmed via the chat server 10. When the prospective participant presses the cancel button 452, the conference information notification unit 37 transmits a cancellation message 454 to the chat application 60 a of the terminal device 60 via the chat server 10.

FIG. 22B shows a message that the reservation has been canceled without pressing the cancel button.
"Reserved conference room" Conference (regular) 2017-05-18 20:47:00 Conference room A has been canceled. "
The prospective participant can see that the conference room has been canceled by looking at the message.

FIG. 22C shows information related to conference room reservation displayed on the terminal device 60 after the use button 451 is pressed and the use is confirmed.
"Conference (regular) 2017-05-18 20:47:00 Conference room A" has been confirmed.
Please check in from the following URL.
XXXX: //XXX.tk? ReceptID = NNN ... N "
N is an arbitrary number or alphabet. Such a message is displayed, for example, at timing 3 in FIG. When the use has already been confirmed, in this embodiment, the message includes the conference identification information “NNN... N”. The prospective participant inputs this conference identification information into the conference room terminal 90 (transmitted by the terminal device 60). Note that the conference identification information “NNN... N” may be included in the information regarding the conference room reservation in FIG. Moreover, the same meeting identification information may be notified several times.

  Note that the prospective participant can cancel the reservation by pressing the cancel button 452 even after confirmation. Also in this case, the conference information notification unit 37 transmits a cancellation message 454 to the chat application 60 a of the terminal device 60 via the chat server 10.

  “XXXX: //XXX.tk” in FIG. 22C is the URL of the conference management server 30. Since “NNN... N” is specified by the parameter, the terminal device 60 can access the conference management server 30 together with the conference identification information. Accordingly, the check-in management unit 38 of the conference management server 30 generates a two-dimensional code including the conference identification information, and the terminal device 60 can hold the two-dimensional code. This two-dimensional code may be used for check-in.

FIG. 22D shows a message indicating that check-in has been accepted. Details of the check-in will be described later.
"Reserved meeting room" Regular meeting 2017-05-18 20:47:00 Meeting room A "
Check-in was accepted. "
The prospective participant can grasp that one or more of the prospective participants have checked in by looking at the message. It may be displayed who has checked in.

<Operation procedure of conference management server>
FIG. 23 is an example of a flowchart illustrating a procedure in which the conference management server 30 notifies information related to conference room reservation.

  As described above, first, the conference information notification unit 37 notifies the conference robot of information related to the conference room reservation (S10).

  The conference information notification unit 37 determines whether a response “use” or “cancel” has been received (S20).

  When the response to cancel is received, the conference information notification unit 37 notifies the cancel from the notification robot again (S30). The reservation account can be specified by the reservation ID included in the response, and the group can be specified from the reservation account. Cancel is registered in the status of the conference management information DB 493.

  When the response to use is received, the conference information notification unit 37 notifies the use confirmation again from the notification robot (S40). Usage confirmation is registered in the status of the conference management information DB 493.

  Next, the conference information notification unit 37 determines whether or not a predetermined time has passed before the start time (S50). Wait until a predetermined time before.

  When a predetermined time has passed, the conference information notification unit 37 notifies the conference identification information and the URL of the conference management server from the notification robot (S60). The conference information notification unit 37 generates conference identification information and registers it in the conference identification information DB 494 in association with the reservation ID and conference room ID. This makes it easier to suppress empty reservations and allows the user to acquire a two-dimensional code or the like.

  On the other hand, when the response of “use” or “cancel” is not received (No in S20), the conference information notification unit 37 determines whether or not a predetermined time has elapsed since the notification based on the notification setting DB 496 (S70). . The determinations in steps S20 and S70 are repeated until a predetermined time has elapsed.

  If the response “use” or “cancel” is not received even after a predetermined time has elapsed (Yes in S70), the conference information notification unit 37 notifies the cancel from the notification robot (S80). Cancel is registered in the status of the conference management information DB 493.

<Notification to individual participants>
The notification robot of the chat server 10 can send a message to all members of the same group in real time. However, the facility reservation system 100 according to the present embodiment can limit the message transmission destination to some members in the group. In this case, it is necessary to specify the account of the reservation management server 20 of all the prospective participants who wish to be notified on the reservation screen 401 in FIG.

<< Method 1 >>
For example, a notification destination of information related to conference room reservation may be determined in advance. In this case, the conference information notification unit 37 only has to notify the information regarding the conference room reservation only to the predetermined prospective participants. For example, it is possible to notify a prospective participant of the reservation account. In the chat server 10, the notification robot generally transmits a message to all the members of the group. Therefore, when the conference information notification unit 37 notifies the notification robot of the chat server 10, the member is designated and notified. Request to do. In this case, the conference management server 30 needs to store the account of the chat management server 10 and the account of the reservation management server 20 in association with all the prospective participants who wish to be notified.

<< Method 2 >>
There is a method in which a manager or a prospective participant of the facility reservation system 100 sets a notification list in advance.
Notification list when A and B are scheduled to participate: A, B Notification list when A, B and C are scheduled to participate: A, B and C Notification list for Mr. A, Mr. B, Mr. C, and Mr. D: Whole group The meeting information notification unit 37 is a prospective participant set in the notification list among the prospective participants account and the reservation account included in the reservation information. Decide to notify.

<< Method 3 >>
In consideration of the group on the chat system side, only the prospective participant is notified from among the groups having the closest members to the reservation information account and the prospective participant account of the reservation information.
・ Case 1
In the case of a group on the chat system side: Mr. A and Mr. B who are scheduled to participate in the reservation information: Mr. A and Mr. B, the conference information notification unit 37 notifies Mr. A and Mr. B.
・ Case 2
Chat system group 1: A, B,
In the case of group 2 on the chat system side: A, C, and D who are scheduled to participate in the reservation information: A and B, the group 1 is closer, so the meeting information notification section 37 will contact A and B Notice. In this case, the notification robot needs to be added to each of the groups 1 and 2, and the conference management server 30 includes each group, the account of the chat server 10 belonging to the group, the account of the reservation management server 20, Must be stored in association with each other.

<Initial setting of conference room terminal>
The conference room terminal 90 is preferably set with a conference room ID, a conference room name, a URL of the conference management server 30, and the like. For this reason, the administrator of the facility reservation system 100 performs initial setting on the conference room terminal 90.

  FIG. 24 is an example of a sequence diagram relating to the initial setting of the conference room terminal 90.

  S1: The administrator of the equipment reservation system 100 operates the registration terminal 50 and logs in to the conference management server 30. The initial setting unit 39 of the conference management server transmits a menu screen to the registration terminal 50.

  S2: The administrator of the facility reservation system 100 presses the conference room list from the menu screen, and the display control unit 53 of the registration terminal 50 displays the conference room list screen.

  S3: The manager of the facility reservation system 100 presses the conference room in which he / she is (initially set) on the conference room list screen. The communication unit 51 of the registration terminal 50 transmits information specifying the conference room to the initial setting unit 39 of the conference management server. The initial setting unit 39 of the conference management server 30 generates a two-dimensional code. The two-dimensional code includes the conference room ID, the conference room name, and the URL of the conference management server 30. Thereby, the conference room ID and the conference room name managed by the conference management server 30 can be registered in the conference room terminal 90. Further, communication from the conference room terminal 90 to the conference management server 30 is enabled by the URL of the conference management server 30.

  S4: The administrator of the equipment reservation system 100 operates the conference room terminal 90 to activate the terminal application.

  S5: Next, the setting menu displayed by the terminal application 90a is pressed. The operation reception unit 93 of the conference room terminal 90 receives the press, and the display control unit 94 displays a screen corresponding to the operation.

  S6: The administrator of the equipment reservation system 100 presses the conference room registration menu. The operation reception unit 93 receives an operation, and the terminal device communication unit 92 of the conference room terminal 90 starts reading the two-dimensional code.

  S7: Since the display control unit 53 of the registration terminal 50 displays the two-dimensional code in step S3, the terminal device communication unit 92 of the conference room terminal 90 reads the two-dimensional code.

  S7.1: The server communication unit 91 of the conference room terminal 90 communicates with the conference management server 30 using the URL of the conference management server 30, and verifies whether or not it can be connected. For example, confirm that Ack is rejecting.

  S7.1.1: The server communication unit 91 of the conference room terminal 90 acquires the latest event (conference room reservation information, check-in state, control information, etc. in the current time zone) from the conference management server 30. When the check-in is not performed, the conference room terminal 90 displays a screen for waiting for entry.

  S8: If not checked in, the conference room terminal 90 starts advertising Bluetooth (registered trademark) Low Energy. As a result, the terminal device 60 can communicate with the conference room terminal 90.

  FIG. 25 is an example of a sequence diagram when a general user confirms the reservation status. A general user is a general user such as a person who intends to reserve a conference room.

  S1: The general user operates the conference room terminal 90 to display a menu for confirming the reservation status.

  S1.1: The server communication unit 91 of the conference room terminal 90 inquires of the conference management server 30 about the reservation status using the conference room ID that is initially set and the URL of the conference management server 30. The conference management server 30 transmits the reservation information specified by the conference room ID among the reservation information in the reservation information DB to the conference room terminal 90. The reservation information to be transmitted may be only for the current day, or can be set by a general user such as one week ahead or one month ahead. Thereby, the general user can confirm the reservation status of the conference room in which he / she is.

<Check-in>
The following describes the procedure for checking in using several methods.

<< Check-in using 2D code >>
FIG. 26 is an example of a sequence diagram illustrating a check-in procedure using a two-dimensional code.

  S1: As described above, the conference information notification unit 37 of the conference management server 30 generates the conference identification information by the start time of the conference.

  S2: As shown in FIG. 22 (c), the conference information notification unit 37 of the conference management server 30 transmits the conference identification information to the chat server 10 (terminal device 60) together with the information related to the conference room reservation. The terminal device 60 holds conference identification information.

  S3: The prospective participant presses the URL of the conference management server 30 included in the information related to the conference room reservation. The operation accepting unit 61b of the terminal device 60 accepts pressing of a URL. In the terminal device 60, a browser included in the chat application 60a is activated.

  S3.1: The communication unit 61a of the terminal device 60 requests a two-dimensional code together with the conference identification information from the conference management server 30 specified by the URL. The check-in management unit 38 of the conference management server 30 generates a two-dimensional code obtained by encoding the conference identification information, and the communication unit 31 transmits the two-dimensional code to the terminal device 60. The display control unit 66 (browser) of the terminal device 60 displays a two-dimensional code. This two-dimensional code includes conference identification information.

  S3.2: The server communication unit 65 of the terminal device 60 specifies the conference identification information and requests the conference management server 30 for a two-dimensional code.

  S4: The prospective participant selects a menu for accepting check-in with a two-dimensional code displayed on the conference room terminal 90.

  S4.1: The conference room terminal 90 activates the camera.

  S5: The prospective participant brings the two-dimensional code displayed by the terminal device 60 closer to the camera of the conference room terminal 90.

  S5.1: The terminal device communication unit 92 of the conference room terminal 90 detects the two-dimensional code and decodes it to acquire the conference identification information.

  S5.1.1: The server communication unit 91 of the conference room terminal 90 transmits the conference room ID and the conference identification information included in the two-dimensional code to the conference management server 30. The check-in management unit 38 of the conference management server 30 determines whether or not the received conference identification information matches the conference identification information of the most recently scheduled conference. That is, the conference identification information is registered in the conference identification information DB 494 in association with the conference room ID. However, since it is not appropriate to allow check-in long before the start time, the start time is specified by referring to the conference management information DB 493 with the reservation ID of the conference identification information DB 494. For example, if the current time is about 5 to 10 minutes before the start time of the conference (predetermined time), check-in is permitted. If they match, the check-in management unit 38 of the conference management server 30 responds to the conference room terminal 90 that the check-in is possible or not along with the conference time. In addition, 5 to 10 minutes is an example, and if there is no reservation in the same conference room, check-in may be permitted even before 5 to 10 minutes. Note that the communication unit 31 of the conference management server 30 returns the start time.

If the check-in is possible, step S6 is executed.
S6: The display control unit 94 of the conference room terminal 90 displays that the conference room is in use (in-use screen).

If check-in is not possible, step S7 is executed.
S7: The display control unit 94 of the conference room terminal 90 displays an error message. For example, “Reservation time is still ahead” is displayed.
S7.1: The display control unit 94 of the conference room terminal 90 displays waiting for entry (waiting for check-in).

<< Check-in where attendees manually input meeting identification information >>
FIG. 27 is an example of a sequence diagram illustrating a check-in procedure when a prospective participant forgets to carry the terminal device 60. The prospective participant logs in using the meeting identification information that is remembered or recorded.

  S1: As described above, the conference information notification unit 37 of the conference management server 30 generates the conference identification information by the start time of the conference.

  S2: As shown in FIG. 22 (c), the conference information notification unit 37 of the conference management server 30 transmits the conference identification information to the chat server 10 (terminal device 60) together with the information related to the conference room reservation. The terminal device 60 holds conference identification information. However, the prospective participant does not hold the terminal device 60.

  S3: The prospective participant presses the “Check in with conference identification information” menu displayed on the conference room terminal 90. The operation accepting unit 93 of the conference room terminal 90 accepts the operation, and the display control unit 94 displays an input field for conference identification information.

  S4: The prospective participant inputs conference identification information. The operation reception unit 93 of the conference room terminal 90 receives the conference identification information.

  S5: The prospective participant presses the OK button (confirmation button). The operation accepting unit 93 of the conference room terminal 90 accepts pressing of the OK button.

  The subsequent processing is the same as in FIG. In this way, even if there is no terminal device 60, if the conference identification information is remembered, the prospective participant can check in.

<< Check-in by near field communication >>
FIG. 28 is an example of a sequence diagram in which a prospective participant checks in by short-range wireless communication.

  S1: As described above, the conference information notification unit 37 of the conference management server 30 generates the conference identification information by the start time of the conference.

  S2: As shown in FIG. 22 (c), the conference information notification unit 37 of the conference management server 30 transmits the conference identification information to the chat server 10 (terminal device 60) together with the information related to the conference room reservation. The terminal device 60 holds conference identification information.

  S3: The prospective participant operates the chat application 60a of the terminal device 60 to cause the application communication unit 64 to activate the conference application 60b.

  S3.1: As a result, the conference application 60b is activated and information on the conference room reservation is held.

  S4: The prospective participant brings the terminal device 60 closer to the conference room terminal 90.

  S5: The terminal communication unit 68 of the terminal device 60 detects the conference room terminal 90. For example, in Bluetooth Low Energy (registered trademark), the conference room terminal 90 is a peripheral, and the terminal device 60 is a central.

  S5.1: The terminal communication unit 68 of the terminal device 60 is connected to the conference room terminal 90 via Bluetooth Low Energy (registered trademark).

  S5.2: The terminal communication unit 68 of the terminal device 60 writes the conference identification information in the characteristic for writing the conference identification information and transmits it to the conference room terminal 90.

  S6: The terminal device communication unit 92 of the conference room terminal 90 detects the conference identification information.

  S6.1: The server communication unit 91 of the conference room terminal 90 transmits the conference room ID and the conference identification information to the conference management server 30. The check-in management unit 38 of the conference management server 30 determines whether or not the received conference identification information matches the conference identification information of the most recently scheduled conference.

  S6.1-2: The check-in management unit 38 transmits the check-in result to the conference room terminal 90. At this time, it is preferable that the connection ID included in the reservation information is also transmitted to the conference room terminal 90. The conference room terminal 90 transmits the connection ID to the electronic device 70. As a result, the electronic device 70 can automatically connect to the electronic device 70 at the other site by specifying the electronic device 70 at the other site by the connection ID.

  S6.2: The server communication unit 91 of the conference room terminal 90 receives the check-in result, and the terminal device communication unit 92 writes the check-in result in the characteristic for reading the check-in result and transmits it to the terminal device 60. To do.

  S5.3 S5.4: The terminal communication unit 68 of the terminal device 60 acquires the check-in result by appropriately acquiring the characteristic for reading the check-in result from the conference room terminal 90.

  S5.5: The terminal communication unit 68 of the terminal device 60 disconnects Bluetooth Low Energy (registered trademark).

If check-in is possible, then:
S6.3: The terminal device communication unit 92 of the conference room terminal 90 ends the advertisement of Bluetooth Low Energy (registered trademark).
S6.4: The server communication unit 91 of the conference room terminal 90 communicates with the conference management server 30 and acquires the latest event.
S6.5: The display control unit 94 of the conference room terminal 90 displays that the conference room is in use (in-use screen).
S6.6: Thereafter, the meeting end time elapses. A prospective participant checks out. The display control unit 94 of the conference room terminal 90 displays waiting for entry (waiting for check-in). The check-out process will be described with reference to FIG.
S6.7: The terminal device communication unit 92 of the conference room terminal 90 resumes the Bluetooth Low Energy (registered trademark) advertisement.

If check-in is not possible:
S6.8: The display control unit 94 of the conference room terminal 90 displays an error message. For example, “Reservation time is still ahead” is displayed.
S6.8.1: The display control unit 94 of the conference room terminal 90 displays waiting for entry (waiting for check-in).

<Checkout procedure>
FIG. 29 is an example of a sequence diagram in which a prospective participant checks out.

  S1: The prospective participant presses the checkout button displayed on the conference room terminal 90.

  S1.1: The operation accepting unit 93 of the conference room terminal 90 accepts pressing of the checkout button, and the server communication unit 91 sends the conference room ID, conference identification information, and a signal indicating that the checkout has been performed to the conference management server 30. Send.

  S1.1.1: The check-in management unit 38 of the conference management server 30 performs a check-out process. Specifically, the checkout is recorded in the status of the conference management information DB 493. Since the server communication unit 91 of the conference room terminal 90 acquires the checkout state from the conference management server 30 as the latest event, the display control unit 94 of the conference room terminal 90 displays the waiting for entry (check-in) wait.

<Procedure for starting conference room terminal 90>
FIG. 30 is an example of a sequence diagram illustrating a process when the conference room terminal 90 is activated.

  S1: The administrator of the equipment reservation system 100 turns on the power to the conference room terminal 90.

  S1.1: The conference room terminal 90 is activated to automatically activate the terminal application.

  S1.2: The conference room terminal 90 reads the setting. This setting is the URL, conference room name, conference room ID, etc. of the conference management server 30 that are initially set.

The following processing is executed when the initial setting is completed.
S1.2.1: The server communication unit 91 of the conference room terminal 90 communicates with the conference management server 30 to acquire the latest event. For example, reservation information for the current time zone, whether check-in has been completed, and the like are transmitted.

  S1.2.2: When the check-in has been completed, the display control unit 94 of the conference room terminal 90 displays that the conference room is being used (in-use screen).

  S1.2.3: When not checked in, the display control unit 94 of the conference room terminal 90 displays a waiting for entry (check-in) wait.

  S1.2.4: The terminal device communication unit 92 of the conference room terminal 90 resumes the advertisement of Bluetooth Low Energy (registered trademark).

  If the initial setting has not been completed, the initial setting shown in FIG. 24 is executed.

<Processing procedure of conference management server>
FIG. 31A is an example of a flowchart regarding the process in which the conference management server 30 automatically cancels the reservation.

  First, as described above, when the prospective participant presses the “use” button, use confirmation is registered in the status of the conference management information DB 493.

  First, the status is determined to be used (S10). Then, the check-in management unit 38 of the conference management server 30 determines whether or not the current time has passed 10 minutes after the start time has passed (S20).

  Then, when 10 minutes have elapsed after the start time has elapsed, the check-in management unit 38 determines whether or not the check-in has been performed with reference to the status (S30).

  If the check-in is not performed even after 10 minutes have elapsed (No in S30), the check-in management unit 38 cancels the reservation (S40). If canceled, the check-in management unit 38 will not accept the check-in even if the conference identification information and the conference room ID are transmitted thereafter. The conference management server 30 specifies the reservation ID and notifies the reservation management server 20 that the reservation has been canceled. Thereby, empty reservations can be reduced.

  FIG. 31B is an example of a flowchart regarding check-in and check-out processing of the conference management server 30. For example, the process of FIG. 31 starts when the status of the conference management information DB 493 is confirmed to be used.

  The check-in management unit 38 of the conference management server 30 receives the conference room ID and the conference identification information from the conference room terminal 90 (S10).

  The check-in management unit 38 searches the conference identification information DB 494 using the conference room ID and the conference identification information, and specifies the reservation ID (S20).

  Next, the check-in management unit 38 specifies the reservation information with the reservation ID and acquires the start time (S30).

  The check-in management unit 38 determines whether the start time is within a predetermined time from the current time (S40).

  If the determination in step S40 is No, the check-in management unit 38 does not permit check-in and transmits a message to that effect to the conference room terminal 90 (S50).

  If the determination in step S40 is Yes, the check-in management unit 38 permits check-in and transmits a message to that effect to the conference room terminal 90 (S60). Note that “checked in” is set in the status of the conference management information DB 493. The conference room terminal 90 can display that it is being used.

  The conference information notifying unit 37 notifies the prospective participant via the notification robot that the check-in has been performed (S65). Since the reservation ID can be specified by the conference identification information DB 494, the group may be specified and notified from the reservation information account of the reservation information.

  Next, the check-in management unit 38 determines whether or not a check-out signal has been received (S70). The check-in manager 38 waits until a check-out signal is received.

  When the check-out signal is received, the check-in management unit 38 performs a check-out process (S80). That is, checkout is set in the status of the conference management information DB 493. As a result, processing relating to the reservation information is not performed.

  The check-in management unit 38 transmits a check-out OK to the conference room terminal 90 (S90). Thereby, the conference room terminal 90 can display waiting for entry.

<Screen example of conference room terminal>
FIG. 32 is an example of a screen example of the conference room terminal 90. FIG. 32A shows an example of a waiting for entry (waiting for check-in) screen, FIG. 32B shows an example of a busy screen, and FIG. 32C shows an example of an error screen. When checking in with a two-dimensional code, the prospective participant presses down menu 1 in FIG. 32A, and when checking in with conference identification information, the prospective participant presses down menu 2 in FIG. In the case of short-range wireless communication, there is no menu because the terminal device 60 and the conference room terminal 90 automatically communicate with each other. If the check-in is successful, the in-use screen of FIG. 32B is displayed until the check-out. When checking out, the waiting for entry (waiting for check-in) screen of FIG. 32A is displayed. If the check-in fails, the error screen of FIG. 32C is displayed, and then the screen automatically returns to the waiting for entry (waiting for check-in) screen of FIG.

<Summary>
As described above, the facility reservation system 100 according to the present embodiment can notify a prospective participant of information related to a conference room reservation using a chat system without using an e-mail. Since the prospective participant confirms the information regarding the reservation of the conference room, the empty reservation of the conference room can be reduced.

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

  For example, the notified message does not need to be text, and may be a file such as a sound, a still image, a moving image, a program, or an application.

  Further, in the present embodiment, the conference management server 30 also identifies the prospective participant with the account of the reservation management server 20. However, if the account of the reservation management server 20 and the unique account of the conference management server 30 are associated with each other. The conference management server 30 may identify a prospective participant with a unique account.

  The two-dimensional code may be a one-dimensional code such as a barcode. A two-dimensional code and a barcode are examples of an image code. Further, the terminal device 60 and the conference room terminal 90 may communicate with each other by NFC, infrared communication, or the like.

  The account may be information that can identify or identify a prospective participant in addition to an email address. For example, a telephone number, an IP address, a MAC address, an arbitrary ID, or the like may be used.

  A plurality of conference management servers 30 may exist, and the functions of the conference management server 30 may be distributed among a plurality of servers.

  8 and 9 shown in the above embodiments are divided according to main functions in order to facilitate understanding of the processing of the facility reservation system 100. However, the present invention is not limited by the way of dividing or the name of each processing unit. The facility reservation system 100 can also be divided into more processing units according to the processing contents. Moreover, it can also divide | segment so that one process unit may contain many processes.

  In the present embodiment, a facility reservation system 100 capable of controlling the electronic device 70 disposed in the conference room will be described. In particular, a device control method performed by the conference management server and the conference room terminal 90 will be described.

<Control of electronic equipment>
FIG. 33 and FIG. 34 are examples of diagrams illustrating an outline of control by the facility reservation system 100 of the electronic device 70 arranged in the conference room. In the present embodiment, the electronic device 70 is described as being turned on, but the conference room terminal 90 is turned on in conjunction with the check-in case 1 (FIG. 33) and the power is turned on a predetermined time before the start time. There is Case 2 to be performed (FIG. 34). Regarding the case 1, since the start time is taken into consideration whether or not the check-in is permitted as described in the first embodiment, the use of the electronic device 70 arranged in the conference room 6 is started based on the reservation information. The electronic device 70 is powered on by detecting the timing. Since the start time is used in case 2, the electronic device 70 is powered on upon detecting the start of use of the electronic device 70 arranged in the conference room 6 based on the reservation information.

<< Power on in conjunction with check-in >>
(1) As described in the first embodiment, the prospective participant checks in the conference room terminal 90 using the terminal device 60.
(2) When the conference room terminal 90 obtains a check-in response from the conference management server 30, the conference room terminal 90 requests control information from the conference management server 30. The request from the conference room terminal 90 is because the conference room terminal 90 is in the in-house network. Alternatively, the communication load can be reduced by acquiring the control information together with the check-in response.

  There are a plurality of methods for how much information is included in the control information.

  Method 1: Information on the electronic device 70 installed in the conference room (connection destination information such as IP and address of each electronic device, authentication information, ON / OFF interface (eg, ON / OFF command via network) API)) is set in the conference room terminal 90, and only the power ON / OFF time, whether to use the video conference system, only the connection destination information (connection destination ID, etc.) of the video conference system Send as control information. In this method, it is not necessary to register information on each conference room in the conference management server 30.

Method 2: Power ON / OFF time (that is, meeting start time and end time), information on devices installed in the conference room (connection destination information such as IP and address of each device, authentication information, power supply) ON / OFF interface (API)), whether or not to use the video conference system, and connection destination information (connection destination ID, etc.) of the video conference terminal are all sent as control information. In this method, information may be managed by the conference management server 30. For example, when the conference room terminal 90 does not store an interface for power ON / OFF in advance, the setting for each conference room terminal 90 is performed. Is less.
(3) The conference room terminal 90 controls the electronic device 70 by transmitting the acquired control information to the electronic device 70. When this control information is ON, the electronic device 70 is activated, so that a prospective participant can use the electronic device 70 immediately after checking in. Since the electronic device 70 does not start unless the power is turned on by the conference management server 30, it is possible to suppress use of the electronic device 70 by a person other than the prospective participant who does not have the right to check in the conference room. Therefore, the facility reservation system 100 can be managed without entrusting the use of the electronic device 70 to a prospective participant.

<< Turn on the power before the start time >>
(1) As described in the first embodiment, the prospective participant responds “use” to the information related to the conference room reservation, thereby registering the use confirmation in the status of the conference management information DB 493.
(2) The conference room terminal 90 generates control information for turning on the electronic device 70 when a predetermined time before the start time (for example, 5 to 10 minutes before).
(3) Since the conference room terminal 90 periodically inquires of the conference management server 30 about the presence or absence of control information, for example, when the control information is generated, the control information can be acquired. Control information may be generated in response to the inquiry.
(4) The conference room terminal 90 controls the electronic device 70 by transmitting the acquired control information to the electronic device 70. When this control information is ON, the electronic device 70 is activated, so the electronic device 70 is activated before the prospective participant checks in, and the prospective participant uses the electronic device 70 immediately after check-in. it can. Since the electronic device 70 does not start unless the power is turned on by the conference management server 30, it is possible to suppress use of the electronic device 70 by a person other than the prospective participant who does not have the right to check in the conference room. Therefore, the facility reservation system 100 can be managed without entrusting the use of the electronic device 70 to a prospective participant.

<Terminology>
The fact that the equipment terminal has communicated with the terminal device of the equipment user means that the user has arrived at the equipment or indicated an intention to use the equipment. In this embodiment, the term “check-in” is used.

  The termination of the use of the facility means that the user has left the facility or has indicated the intention of the user. In this embodiment, the term “checkout” is used.

<About system configuration>
The system configuration, hardware configuration, and functional blocks of the present embodiment are the same as those of the first embodiment, or even if they are different, there is no problem in the description of the present embodiment. In the present specification, components having the same reference numerals perform the same functions, and therefore, description of components once described may be omitted or only differences may be described.

<Operation procedure>
FIG. 35 is an example of a sequence diagram illustrating a procedure in which the conference management server 30 controls the power of the electronic device 70 to be turned on in conjunction with check-in.

  S1: As described in the first embodiment, a check-in result (check-in is possible or not) is transmitted from the conference management server 30. In FIG. 35, control information is transmitted together with check-in possible. Since the conference management server 30 communicates beyond the firewall, this process accepts a check-in request and performs it as a response.

  S1.1: The server communication unit 91 of the conference room terminal 90 receives check-in and control information. If the check-in is successful, the electronic device communication unit 95 of the conference room terminal 90 transmits control information to the electronic device 70.

  S1.2: The electronic device communication unit 95 of the conference room terminal 90 acquires a passcode necessary for using the electronic device 70 from the electronic device 70. The pass code becomes authentication information for the terminal device 60 to transmit video to the electronic device 70. Since the passcode is generated at each activation, it is possible to suppress, for example, a person who is scheduled to participate in another conference room and the like from wirelessly transmitting video.

  S1.3: The terminal device communication unit 92 of the conference room terminal 90 notifies the terminal device 60 of the passcode. There can be various notification methods. For example, it may be transmitted by Bluetooth Low Energy (registered trademark), or may be transmitted by infrared communication, NFC, or the like. Alternatively, the passcode may be displayed on the display 616 of the conference room terminal 90. When the terminal device 60 acquires the passcode, the terminal device 60 can transmit the video to the electronic device 70 and share it among the prospective participants.

  In this way, the prospective participant can check-in the conference room to turn on the electronic device 70, and the terminal device 60 can transmit video to the electronic device 70.

  Note that when the electronic device 70 is already turned on, the electronic device 70 remains turned on.

  FIG. 36 is an example of a sequence diagram illustrating a procedure in which the conference management server 30 controls the power of the electronic device 70 to be turned on a predetermined time before the start time.

  S1: The server communication unit 91 of the conference room terminal 90 acquires the presence / absence of control information from the conference management server 30 together with the conference room ID. Since it is difficult for the firewall to communicate from the external network to the internal network, the server communication unit 91 of the conference room terminal 90 polls the conference management server 30 (inquires periodically). Communication technology such as WebSocket may be used.

  S1.1: The communication unit 31 of the conference management server 30 acquires reservation information from the reservation management server using the conference room ID as a key. If the latest reservation information has already been acquired, this step can be omitted. That is, the reservation information need not be acquired at the polling timing of the conference room terminal 90. The control information generation unit 35 of the conference management server 30 determines whether to generate control information, and generates control information if necessary. That is, it is determined whether it is a predetermined time before the start time. When the reservation information is acquired in advance, the control information is generated in advance without generating the control information at the polling timing. Although the conference identification information is not taken into consideration, the conference identification information is taken into account at the time of check-in. If the check-in is not performed, the electronic device 70 is turned off, so that there is little trouble.

  S1.1.1: The conference management server 30 transmits the presence / absence of control information and, if there is control information, the control information to the conference room terminal 90. At this time, the communication unit 31 of the conference management server 30 can transmit the connection ID. When the connection ID of the electronic device 70 at another base is set in the reservation information, the connection ID is transmitted to the electronic device 70 after check-in by the participant by transmitting the connection ID together with the reservation information. The electronic device 70 can automatically connect to the electronic device 70 at another site using the connection ID and start a remote conference. Therefore, there is a case where the connection ID does not need to be transmitted at the time of check-in of the participant described in FIG.

  The procedure of steps S2 to S4 may be the same as in FIG. Therefore, the prospective participant can use the electronic device 70 immediately after check-in.

  S5: However, if the prospective participant does not check in, the electronic device 70 remains powered on. For this reason, the electronic device communication unit 95 of the conference room terminal 90 turns off the power of the electronic device 70 when the check-in permission is not received from the conference management server 30 within a predetermined time after the power is turned on. In this way, power consumption can be reduced.

<Power OFF control>
FIG. 37 is an example of a sequence diagram illustrating a procedure for controlling the electronic device 70 to be turned off after the conference room terminal 90 is checked out.

  S1: As described in the first embodiment, the server communication unit 91 of the conference room terminal 90 acquires a checkout notification and control information from the conference management server 30. This acquisition is obtained as a response to a checkout request from the conference room terminal 90.

  S1.1: The electronic device communication unit 95 of the conference room terminal 90 transmits the power-off control information to the electronic device 70. By doing so, the power of the electronic device 70 is turned off even if the prospective participant does not turn off the power, so that the power consumption can be reduced. The conference room terminal 90 that has received the checkout notification may request control information from the conference management server 30 again. Note that the check-out notification may also serve as power-off control information, but the check-out notification and control information are sent separately, so that the power-off at check-out is omitted when the next meeting starts immediately. it can. Details will be described later.

<Processing of the conference management server and conference room terminal when the electronic device is turned on in conjunction with check-in>
FIG. 38 is an example of a diagram illustrating processing of the conference management server 30 and the conference room terminal 90 when the electronic device 70 is controlled to be turned on in conjunction with check-in.

  FIG. 38A is an example of a flowchart illustrating a procedure in which the conference management server 30 transmits control information in conjunction with check-in.

  First, the check-in management unit 38 of the conference management server 30 permits check-in (S10).

  The check-in management unit 38 transmits check-in permission to the conference room terminal 90, and the control information response unit 36 transmits control information to the conference room terminal 90 (S20). Note that the check-in and control information need not be transmitted simultaneously. Further, check-in permission may also serve as control information.

  When a video conference terminal is included in the electronic device installed in the conference room, this control information may include a connection destination ID of the video conference terminal. Specifically, when the reservation management server 20 accepts a conference room reservation as shown in FIG. 10, the connection destination ID is also accepted at the same time, and when the connection destination ID can be specified from the reservation information, the connection destination information is Send it in the control information.

  Next, the check-in management unit 38 determines whether or not the check-out has been accepted (S30). If the check-in management unit 38 does not accept the check-out, the check-in management unit 38 waits. . This is because a prospective participant may leave the room without checking out.

  When the determination in step S30 is Yes, the check-in management unit 38 transmits a check-out notification to the conference room terminal 90 (S40).

  Next, the control information generation unit 35 determines whether or not the next meeting start time comes before the predetermined time elapses (S50). As a result, it is possible to prevent the power from being turned off and turned on in a short time.

  When the determination in step S50 is No, the control information generation unit 35 generates control information for power OFF, and the control information response unit 36 transmits the control information for power OFF to the conference management server 30 (S60).

  When the determination in step S50 is Yes, the control information generation unit 35 does not generate control information for turning off the power.

  FIG. 38B is an example of a flowchart illustrating a procedure in which the conference room terminal 90 controls the power of the electronic device 70 to be turned on in conjunction with check-in.

  First, the server communication unit 91 of the conference room terminal 90 acquires a check-in permission (S10). Only check-in is possible or control information may be received. Since these are acquired as a response to the check-in request, polling is unnecessary.

  When the check-in is permitted or the control information is received, the electronic device communication unit 95 of the conference room terminal 90 controls the power of the electronic device 70 to be ON (S20).

  When the connection destination ID of the video conference terminal is included in the control information, a request to connect to the connection destination ID may be made after a power-on command is issued. In addition, in order to control the power ON, control is performed via a network using connection information such as an IP address indicating a specific interface and the electronic device 70.

  FIG. 38C is an example of a flowchart illustrating a procedure in which the conference room terminal 90 controls the power of the electronic device 70 to be turned off in conjunction with the checkout.

  First, the server communication unit 91 of the conference room terminal 90 acquires a checkout notification (S10). Since a check-out notification is acquired as a response to the check-out request, polling is unnecessary.

  Next, the server communication unit 91 of the conference room terminal 90 acquires control information (S20). Control information is not transmitted when the start time of the next meeting arrives before the predetermined time elapses. Since control information is acquired as a response to the checkout request, polling is unnecessary.

  When the control information is received, the electronic device communication unit 95 of the conference room terminal 90 controls the power of the electronic device 70 to be turned off (S30).

  As in the case of power-on, in order to control power-off, control is performed via a network using connection information such as an IP address indicating a specific interface and the electronic device 70.

<Processing of Conference Management Server and Conference Room Terminal when Controlling Power of Electronic Device to Predetermined Time Before Start Time>
FIG. 39 is an example of a flowchart illustrating a procedure in which the conference management server 30 transmits control information a predetermined time before the start time.

  The conference information notification unit 37 of the conference management server 30 acquires a response that the conference room is used from the terminal device 60 (S10). As a result, usage confirmation is registered in the status of the conference management information DB 493.

  The control information generation unit 35 of the conference management server 30 determines whether or not a predetermined time before the start time set in the reservation information (S20).

  When the determination in step S20 is Yes, the control information generation unit 35 of the conference management server 30 generates control information and registers it in the control information DB 497 (S30).

  Thereafter, the control information response unit 36 of the conference management server 30 determines whether an inquiry about the presence or absence of control information has been received from the conference room terminal 90 (S40). Since this inquiry includes the conference room ID, the control information response unit 36 determines that there is control information that responds to the inquiry when the control information DB 497 has control information associated with the conference room ID. .

  When the determination in step S40 is Yes, the control information response unit 36 transmits the power ON control information to the conference room terminal 90 (S50).

  Thereafter, the control information generation unit 35 of the conference management server 30 determines whether or not the conference room terminal 90 is allowed to check in (S60). That is, if the prospective participant does not check in, the power remains on. When the check-in is not permitted within a predetermined time (for example, 10 minutes) after the start time has elapsed, the control information generation unit 35 of the conference management server 30 transmits control information for power OFF. This predetermined time may be equal to the time when the reservation is automatically canceled when the prospective participant does not check in.

  When the determination in step S60 is No, the conference information generation unit of the conference management server 30 generates power-off control information, and the conference information response unit transmits the power-off control information to the conference room terminal 90 (S90).

  If the determination in step S60 is Yes, the control information generation unit 35 of the conference management server 30 determines whether or not a checkout has been received (S70).

  Then, when accepting the checkout, the control information generating unit 35 determines whether or not the next meeting start time comes before the predetermined time elapses (S80). As a result, it is possible to prevent the power from being turned off and turned on in a short time.

  When the determination in step S80 is No, the control information generation unit 35 generates power-off control information, and the control information response unit 36 transmits the power-off control information to the conference room terminal 90 (S90).

  FIG. 40 is an example of a flowchart illustrating a procedure in which the conference room terminal 90 controls the power supply of the electronic device 70 to be turned on a predetermined time before the start time.

  First, the server communication unit 91 of the conference room terminal 90 inquires of the conference management server 30 about the presence or absence of control information together with the conference room ID (S10).

  The electronic device communication unit 95 of the conference room terminal 90 determines whether control information has been received (S20). If not received, the processing of FIG. 40 is reduced.

  When the control information is received (Yes in S20), the electronic device communication unit 95 controls the power supply of the electronic device 70 to be ON (S30).

  Next, the electronic device communication unit 95 determines whether or not the prospective participant has checked in and obtained check-in permission from the conference management server 30 (S40).

  When the server communication unit 91 of the conference room terminal 90 acquires the check-in permission (Yes in S40), the electronic device communication unit 95 determines whether or not the check-out notification is acquired from the conference management server 30 (S70). When the checkout notification is not received (No in S70), the conference room terminal 90 stands by.

  When the check-out notification is received (Yes in S70), the electronic device communication unit 95 controls the power of the electronic device 70 to be turned off by receiving control information indicating that the power is turned off (S80).

  When the server communication unit 91 of the conference room terminal 90 does not acquire the check-in permission (No in S40), the electronic device communication unit 95 determines whether or not a predetermined time has elapsed since the power was turned on (S50). If the determination in step S50 is No, the determination in step S40 is repeated.

If the determination in step S50 is Yes, the prospective participant does not check in, so the electronic device communication unit 95 controls the power of the electronic device 70 to be turned off (S60).
<Summary>
Through the processing as described above, the facility reservation system 100 can turn on and off the power of the electronic device 70 and can manage the use of the electronic device 70 in the conference room. The prospective participant can use the electronic device 70 immediately after check-in. Since the electronic device 70 does not start unless the power is turned on by the conference management server 30, it is possible to suppress use of the electronic device 70 by a person other than the prospective participant who does not have the right to check in the conference room. In addition, since the power is automatically turned off upon checkout, power consumption can be reduced.

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

  For example, the control information for power ON and power OFF has been described. For example, the conference management server 30 may transmit control information for displaying various information on the electronic device 70. For example, “the end time is reached in the remaining 10 minutes”, “countdown to the end time of the conference”, and the like can be displayed. You may display a meeting name, a prospective participant name (account), etc.

  In the second embodiment, the power supply of the electronic device 70 is controlled to be turned off in conjunction with the checkout. However, the conference management server 30 is turned off at the end time, slightly before the end time, or at the end time + α. You may control. In this case, the power is turned off even if there is no predetermined time until the start of the next meeting. This makes it easy to suppress the end time from elapses.

  The control information generation unit 35 is an example of a control information generation unit, the control information response unit 36 is an example of a control information transmission unit, and the check-in management unit 38 is an example of a facility management unit. The information is an example of first control information, the power-off control information is an example of second control information, and part of the facility reservation system 100 (for example, the conference management server and the conference room terminal 90) is device controlled. The server communication unit 91 is an example of a receiving unit, the electronic device communication unit 95 is an example of an electronic device communication unit, and the terminal device communication unit 92 is an example of a terminal communication unit.

DESCRIPTION OF SYMBOLS 10 Chat server 20 Reservation management server 30 Conference management server 50 Registration terminal 60 Terminal device 70 Electronic device 90 Conference room terminal 100 Equipment reservation system

JP2016-045634

Claims (11)

An information processing device connected via a network to a reservation management device that manages facility reservations,
Control information for detecting the timing when the use of the electronic device arranged in the facility is started based on the reservation information of the facility acquired from the reservation management device and generating first control information of the electronic device Generating means;
Control information transmitting means for transmitting the first control information to a facility terminal arranged in the facility;
An information processing apparatus comprising: The control information generating means generates the first control information when a predetermined time before the reservation start time of the facility included in the reservation information,
The information processing apparatus according to claim 1, wherein the control information transmitting unit transmits the first control information to the facility terminal in response to an inquiry from the facility terminal. The first control information is for controlling the power of the electronic device to be ON,
After transmitting the first control information to the facility terminal, the fact that the facility terminal communicated with the terminal device of the user of the facility is not acquired within a predetermined time from the start time,
The control information generation means generates second control information for controlling the power of the electronic device to be turned off,
The information processing apparatus according to claim 2, wherein the control information transmitting unit transmits the second control information to the facility terminal. After transmitting the first control information to the facility terminal, the fact that the facility terminal has communicated with the terminal device of the user of the facility is acquired within a predetermined time from the start time,
When the end of use of the equipment is received from the equipment terminal from the equipment terminal, the control information generating means generates second control information for controlling the power of the electronic device to be OFF, and the control information transmitting means is The information processing apparatus according to claim 3, wherein the second control information is transmitted to the facility terminal. After transmitting the first control information to the facility terminal, the fact that the facility terminal has communicated with the terminal device of the user of the facility is acquired within a predetermined time from the start time,
Even when the end of use of the equipment is received from the equipment terminal from the equipment terminal,
The information processing apparatus according to claim 4, wherein the control information generation unit does not generate the second control information when the start time of the next conference arrives before a predetermined time elapses. The control information generation unit generates the first control information when the facility terminal acquires that the facility terminal has communicated with the terminal device of the user of the facility,
The information processing apparatus according to claim 1, wherein the control information transmission unit transmits the first control information to the facility terminal. The fact that the equipment terminal has communicated with the terminal device of the user of the equipment means that the user checks in the equipment,
Meeting information indicating that the user has the right to use the equipment in the time zone reserved for the equipment, which is held by the terminal device and input to the equipment terminal, corresponds to the time zone for the information processing apparatus. If it matches the meeting identification information to be attached, has equipment management means that permits the use of the equipment,
When the use of the facility is permitted, the control information generating unit generates the first control information in response to an inquiry from the facility terminal,
The information processing apparatus according to claim 1, wherein the control information transmission unit transmits the first control information to the facility terminal. The reservation information includes a reservation start time of the facility,
When the end of use of the equipment is received from the equipment terminal from the equipment terminal,
If the start time of the next meeting does not arrive before the predetermined time elapses, the control information generating means generates second control information for controlling the power supply of the electronic device to be OFF,
The information processing apparatus according to claim 7, wherein the control information transmitting unit transmits the second control information to the facility terminal. An equipment control system having a reservation management device for managing a reservation of equipment, an information processing device connected via a network, and a equipment terminal arranged in the equipment,
The information processing apparatus includes:
Control information for detecting the timing when the use of the electronic device arranged in the facility is started based on the reservation information of the facility acquired from the reservation management device and generating first control information of the electronic device Generating means;
Control information transmitting means for transmitting the first control information to the equipment terminal arranged in the equipment,
The equipment terminal is
Receiving means for receiving the first control information received from the information processing apparatus;
Electronic device communication means for transmitting the first control information received by the receiving means to the electronic device;
A device control system comprising: After the electronic device communication means of the facility terminal transmits the first control information to the electronic device, a pass code for a terminal device used by a user of the facility to communicate with the electronic device is sent to the electronic device. Get from
The apparatus control system according to claim 9, wherein the facility terminal includes a terminal communication unit that transmits the passcode to the terminal device. An apparatus control method performed by an information processing apparatus connected via a network with a reservation management apparatus that manages the reservation of equipment,
The control information generation means detects the timing when the use of the electronic device arranged in the facility is started based on the reservation information of the facility acquired from the reservation management device, and performs first control of the electronic device. Generating information;
And a step of transmitting the first control information to a facility terminal arranged in the facility.

Images