JP7131001B2 - Equipment control system, equipment terminal, control method - Google Patents

Description

The present invention relates to equipment control systems, equipment terminals, and control methods.

Equipment reservation systems for conference rooms and the like are known. A prospective participant of the conference can make a terminal device communicate with the reservation management server and reserve a conference room with a browser that operates on the terminal device. A prospective participant of the conference can confirm the schedule, place, etc. of the conference by operating the terminal device to communicate with the reservation management server.

In such a facility reservation system, an empty reservation may occur in which a conference room that is not actually used remains reserved. In order to reduce vacant reservations, there has been known a technique of notifying prospective participants of conference schedules by e-mail (see, for example, Patent Document 1). Japanese Patent Laid-Open No. 2002-200000 discloses a system that notifies the participants of each conference in advance by e-mail when the date and time of the conference is approaching.

However, in the conventional technology, there is a problem that whether or not to use the electronic devices placed in the conference room is left to the participants of the conference. Electronic devices such as an electronic blackboard, a multi-function device, and a projector are arranged in the conference room, and the participants can hold a conference using these devices. However, participants who use these devices must turn on the power of the electronic devices in order to use them, and it takes time for some participants to start up the electronic devices. On the other hand, if the electronic device can be turned on and off at will until the conference starts, even those who have not reserved the conference room can use the electronic device. In either case, power consumption increases if the participant forgets to turn off the power.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a device control system capable of managing the use of electronic devices.

The present invention is a device control system having a reservation management device that manages reservations for a facility, an information processing device that is connected via a network, and a facility terminal that is arranged in the facility, wherein the information processing device comprises: Control information for generating first control information for the electronic device by detecting timing at which use of the electronic device arranged in the facility is started based on the reservation information for the facility acquired from the reservation management device. generating means, and control information transmitting means for transmitting the first control information to an equipment terminal arranged in the equipment ;
The facility terminal includes receiving means for receiving the first control information received from the information processing device, and transmitting the first control information received by the receiving means to the electronic device, and performing the first control electronic device communication means for acquiring from the electronic device a pass code for a terminal device used by a user of the facility to communicate with the electronic device after the information is transmitted to the electronic device; and transmitting the pass code to the terminal. and terminal communication means for transmitting to the device .

A device control system can be provided that can manage the use of electronic devices.

It is an example of the figure explaining the prior registration work regarding a facility reservation system. FIG. 10 is a diagram illustrating an example of a procedure for a conference management server to notify prospective participants of information on reservation of a conference room; 1 is an example of a system configuration diagram of a facility reservation system; FIG. 1 is an example of a system configuration diagram of a facility reservation system; FIG. 4 is an example of a hardware configuration diagram of a conference management server; FIG. 3 is a hardware configuration diagram of an example of a conference room terminal; FIG. 1 is an example of a hardware configuration diagram of an electronic blackboard as an example of an electronic device; FIG. It is an example of the functional block diagram which shows the function of a reservation management server, a chat server, a conference management server, and a terminal device in block form. It is an example of a functional block diagram showing functions of a terminal device, a conference room terminal, and an electronic device in block form. It is an example of a conference room reservation screen provided by the reservation management server and displayed on the terminal device. It is an example of a registration work initial screen displayed on a registration terminal or a terminal device. It is an example of a notification robot registration screen displayed on the registration terminal. It is an example of a domain management screen displayed on a registration terminal. It is an example of an account correspondence screen displayed on the terminal device. FIG. 10 is an example of a sequence diagram showing a procedure for registering a notification robot; FIG. 10 is an example of a sequence diagram showing a procedure for registering a customer's reservation management server account; FIG. 10 is an example of a sequence diagram showing a procedure for associating a group of the chat system with an account of the reservation management server; FIG. 10 is an example of a diagram illustrating the timing of notification of information related to reservation of a conference room; FIG. 10 is an example of a sequence diagram showing a procedure for a conference management server to notify information about reservation of a conference room; FIG. 10 is an example of a flowchart of a procedure for a notification determination unit to determine whether or not to notify information related to reservation of a conference room; FIG. 10 is an example of a sequence diagram in which the conference management server notifies prospective participants of information on reservation of a conference room; FIG. 5 is a diagram showing an example of information related to reservation of a conference room displayed on the terminal device; FIG. 10 is an example of a flow chart showing a procedure for notifying a conference management server of information relating to reservation of a conference room; FIG. 10 is an example of a sequence diagram regarding initial settings of conference room terminals; FIG. 10 is an example of a sequence diagram when a general user confirms the reservation status; FIG. 10 is an example of a sequence diagram showing a check-in procedure using a two-dimensional code; FIG. 10 is an example of a sequence diagram showing a check-in procedure when a prospective participant forgets to carry a terminal device; FIG. 10 is an example of a sequence diagram of check-in by a prospective participant through short-range wireless communication; It is an example of a sequence diagram for a prospective participant to check out. FIG. 10 is an example of a sequence diagram illustrating processing when a conference room terminal is activated; FIG. 10 is an example of a flow chart of processing for automatically canceling a reservation by a conference management server, and check-in and check-out processing of the conference management server. It is a figure which shows an example of the screen example of a conference room terminal. FIG. 10 is an example of a diagram illustrating an outline of control by the facility reservation system for electronic devices arranged in a conference room; FIG. 10 is an example of a diagram illustrating an outline of control by the facility reservation system for electronic devices arranged in a conference room; FIG. 10 is an example of a sequence diagram showing a procedure for the conference management server to turn on the electronic device in conjunction with check-in; FIG. 10 is an example of a sequence diagram showing a procedure for the conference management server to turn on the power of the electronic device a predetermined time before the start time; FIG. 10 is an example of a sequence diagram showing a procedure for turning off the power of an electronic device by a conference room terminal after checkout; FIG. 10 is an example of a diagram illustrating processing of the conference management server and the conference room terminal when powering on the electronic device is controlled in conjunction with check-in; FIG. 10 is an example of a flowchart showing a procedure for the conference management server to transmit control information a predetermined time before the start time; FIG. 10 is an example of a flow chart showing a procedure in which the conference room terminal turns on the power of the electronic device a predetermined time before the start time.

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

<Pre-registration work>
First, the pre-registration work for operating the facility reservation system capable of reducing vacant reservations will be described.

FIG. 1 is an example of a diagram for explaining the preliminary registration work for the equipment reservation system 100 of this 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 management of meetings held in the conference rooms. A conference management server 30 is connected so as to be able to communicate as necessary.

A chat system is a system for sending and receiving information such as text in real time, either one-to-one or in a group. In FIG. 1, the accounts of Mr. A, Mr. B, Mr. C, and Mr. D are associated with Group 1, and Mr. A, Mr. B, Mr. C, and Mr. D form Group 1. In FIG. The text input by Mr. A is displayed on Mr. A's terminal device 60 and is transmitted to the terminal devices 60 of Mr. B, Mr. C, and Mr. D, respectively. The same applies to the texts input by Mr. B, Mr. C, and Mr. D. In this embodiment, using such a chat system, the conference management server 30 notifies the prospective participants (Mr. A, Mr. B, Mr. C, Mr. D) of the information regarding the reservation of the conference room. are one.

The reservation management server 20 is a server (information processing device) that provides a web service that manages the overall schedule. The reservation management server 20 accepts the reservation of the conference room, and the prospective participants of the conference can confirm the conference schedule at any timing. The facility reservation system 100 uses the account of the reservation management server 20 to associate the group of the chat system with the prospective participants of the conference (the prospective participants of the conference who have reserved the conference with the reservation management server 20). This is one of the features of the embodiment. The outline of the pre-registration work will be described below.

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

(2) Further, the administrator of the equipment 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 the account issued to the prospective participant by the reservation management server 20 (if the account is an email address, the domain part of the email address). For example, a domain is issued for each company. In principle, this domain can be used to retrieve meeting room reservation information. In addition, not only the domain is used to acquire reservation information, but also the account information (address and password) of the administrator with administrator authority. Acquire reservation information within the scope of authority of this administrator (for example, the entire domain if the administrator has authority over the entire domain).

(3) Next, one of the prospective participants associates group 1 with Mr. A, Mr. B, Mr. C, and Mr. D, respectively. Specifically, the terminal device 60 is operated to communicate with the conference management server 30, and the account of the user (prospective participant) of the facility reservation system 100 issued by the reservation management server 20 and the group name of group 1 (specifically, is information that specifies the notification destination of a message in a chat system, such as a group name.For example, slack (registered trademark) requires a channel name and a team name.) is associated and registered.

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

<Overview of notification>
FIG. 2 is an example of a diagram illustrating a procedure for the conference management server 30 to notify the prospective participants of information regarding the reservation of the conference room.

(4) At least one of the prospective participants uses the terminal device 60 to communicate with the reservation management server 20 to reserve a conference room. Reservation information regarding the reservation of the conference room is recorded in the reservation management server 20 . The reservation information records at least the account of the prospective participant who made the reservation (reserver account).

(5) The conference management server 30 determines an arbitrary domain. This is to notify prospective participants who have accounts containing this domain. The conference management server 30 periodically communicates with the reservation management server 20 to acquire reservation information from the reservation management server 20 .

(6) Here, for example, it is assumed that Mr. A's reservation information is found. As a result, the conference management server 30 can specify the message 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 and functions as a notification robot registered in the group 1 to notify the prospective participants of the group 1 of information regarding the reservation of the conference room. That is, have the other prospective participants send the appropriate text.

(8) The chat system sends the text entered by the notification robot to all members in the group. In this way, all prospective participants can be notified of the information regarding the reservation of the conference room.

Therefore, the equipment reservation system 100 of the present embodiment can notify prospective participants of information regarding conference room reservations using a chat system without using e-mail. Statistics show that chat system texts have a much higher reading rate than e-mails, which can reduce the chances of prospective participants overlooking texts. Also, in the chat system, it is easy to create a group, and the manager of the equipment reservation system 100 or the prospective participants can easily create a group of prospective participants.

<Terms>
A prospective participant becomes a participant upon check-in, but is referred to as a prospective participant without particular distinction.

The information related to the reservation of facilities may be any information that accompanies the reservation of facilities. For example, it may contain only the fact that a reservation has been made, or may include information such as the subject of the reservation and the start time of use of the facility. Sending information regarding the reservation of equipment may be referred to as a reminder.

A customer is a company that uses the equipment reservation system 100, and prospective participants are assumed to be employees of this customer. However, a customer can also be an individual.

A facility is a thing equipped with what is necessary for a certain purpose. In this embodiment, the term conference room will be used.

A group is a collection of people. A target person who belongs to a group means a person who belongs to an arbitrary group in the chat server 10 . Alternatively, it is a member of a group to which notification information is notified. Groups specify which members of the chat system, commonly referred to as rooms, rooms, etc., are to be notified. In slack (registered trademark), which is an example of a chat system, a "group" is called a channel. Also, in other chat systems, 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 is information shared by the group.

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

<System configuration example>
FIG. 3 is an example of a system configuration diagram of the facility reservation system 100. As shown in FIG. The equipment reservation system 100 can be mainly divided into an external network N2 and an internal network N1. Here, the in-house network N1 is a network inside the firewall, and the outside 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 with each other as necessary. A registration terminal 50 operated by an administrator of the facility reservation system 100 and a terminal device 60 operated by a prospective participant of the conference are connected to the external network N2 as necessary. Note that the registered terminal 50 and the terminal device 60 can also be connected to an external network from the in-house network N1.

The reservation management server 20 can be implemented by one or more information processing devices (computer systems) on which a general server OS or the like is installed. A system relating to facility reservations provided by the reservation management server 20 is called a reservation management system. The reservation management server 20 has a calendar system and provides a web application for managing various schedules. Specifically, it has the following functions, for example.
・Receiving schedule registration and confirming who has made the reservation anytime, anywhere ・Notification by e-mail at a set date and time, such as 30 minutes before the schedule ・One person can manage multiple calendars (for work, home, etc.) Yes/Share a calendar with people in the same group The reservation management server 20 manages users by accounts. An account is a user's right to use a service. In many systems, users log into the system using accounts. Therefore, the account has a function (identification information function) for the system to uniquely identify the user. In this embodiment, the conference management server 30 can acquire the reservation information of the conference room by using the account of the reservation management server 20 . The account may be e-mail, ID, telephone number, or the like. The conference management server 30 logs into the reservation management server 20 using, for example, an account and password.

In this embodiment, holding of a conference is managed as a schedule, but the reservation management server 20 can manage various kinds of schedules other than holding of a conference. In addition to meeting rooms, it can be used to reserve various facilities such as rental of various electronic devices and reservations for parking lots. G Suite (registered trademark), Office 365 (registered trademark), etc. are known as reservation management systems, but any reservation management server having the functions described in this embodiment may be used.

Further, in the present embodiment, information regarding the conference room 6 of the in-house network N1 is registered in the reservation management server 20 in advance. That is, the Web application of the reservation management server 20 is customized according to the name of each conference room 6 in the internal network of the company using the facility reservation system 100, the conference room ID, the available reservation time, the reservation unit, and the like. ing. Therefore, the conference room 6 of the company using the facility reservation system 100 is associated with the reservation information.

The chat server 10 can be realized by one or more information processing devices (computer systems) on which a general server OS or the like is installed. A real-time sharing system of information such as text among 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 regarding the reservation of the conference room.

Information to be shared includes images, voices, and the like, and is not limited to text. However, for the sake of convenience of explanation, it is assumed that text is mainly used for notification in the present embodiment. For example, a chat system may provide group-to-group voice calling capabilities. Voice calls may be one-to-one or one-to-N (≧2). Therefore, in this embodiment, when the chat system notifies the information regarding the reservation of the conference room, it may output a voice message in addition to the text display. Although LINE (registered trademark), Slack (registered trademark), and the like are known as chat systems, any chat system may be used as long as the notification robot can notify one or more users.

The chat server 10 similarly manages users with accounts (different from the accounts of the reservation management server), but the conference management server 30 need not be aware of the accounts of the chat server 10 .

The conference management server 30 can be implemented by one or more information processing devices (computer systems) on which a general server OS or the like is installed. As processing related to the external network N2, the conference management server 30 acquires the reservation information of the conference room from the reservation management server 20, detects prospective participants in the reservation information, and associates them with the prospective participants at the set timing. A notification is sent to the group of chat servers 10 that have been selected. In addition, as processing related to the internal network N1, it manages check-in and check-out to the conference room, and controls the power supply of the electronic device 70 based on the reservation information of the conference room acquired from the reservation management server 20.

The terminal device 60 and the registration terminal 50 can be implemented by one or more information processing devices (computer systems) on which a general OS or the like is installed. Although it has been described that the registration terminal 50 is a terminal operated by the administrator of the facility reservation system 100 and the terminal device 60 is a device operated by the prospective participants, the two need not be clearly distinguished. The terminal device 60 is, for example, a smart phone, a tablet terminal, a PC (Personal Computer), a PDA (Personal Digital Assistant), a wearable PC (sunglass type, wristwatch type, etc.). However, browser software having a communication function, or application software dedicated to the chat server 10 or reservation management server 20 may operate. For example, the terminal device 60 can be a car navigation system, a game machine, a television receiver, or the like.
In the terminal device 60, application software dedicated to the chat server 10 (hereinafter referred to as chat application) operates, and further application software dedicated to the equipment reservation system 100 (hereinafter referred to as conference application) operates. However, they 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 via the AP 80 as necessary. . The in-house network N1 is, for example, a LAN (Local Area Network). A prospective participant brings a terminal device 60 into the in-house network N1.

The AP 80 is a base station for communicating between the conference room terminal 90 and the electronic device 70 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 destination IP address of the communication, and switches the transfer destination of the communication. Since the internal network N1 is behind 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 device (equipment terminal) operated by prospective participants who use the conference room. The conference room terminal 90 is arranged on the desk of the conference room 6 or 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 implemented by one or more information processing devices (computer systems) on which a general OS or the like is installed. The conference room terminal 90 displays a menu for check-in, check-out, etc., and communicates with the conference management server 30 to notify the conference management server 30 of check-in or check-out. Further, for example, the conference room ID is transmitted to the conference management server 30, and the reservation information of the conference room currently being held in the conference room is displayed. Also, 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 powers on and off the electronic device 70 .

A conference application running on the terminal device 60 communicates with the conference room terminal 90 by short-range wireless communication, for example. As will be described later, the information regarding the reservation of the conference room acquired by the terminal device 60 includes the conference identification information. The conference room terminal 90 acquires the conference identification information by short-range wireless communication, manual input, two-dimensional code, or the like, and transmits it to the conference management server 30 . Accordingly, the conference room terminal 90 can determine whether or not the prospective participants who have reserved the conference room in the latest time zone from the current time have 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 the prospective participant. You can make sure that prospective attendees who join the meeting together use the reserved meeting room.

Electronic equipment 70 is any type of office equipment that may be used in a conference room. For example, they are an electronic blackboard, a multi-function device, a projector, a digital signage, a digital camera, and the like. An electronic blackboard has a large display with a touch panel, detects coordinates of a board indicated by a user, connects the coordinates, and displays strokes. In addition, it is possible to display images of the connected PC, communicate with electronic blackboards at other sites, and synchronize strokes. The electronic blackboard is sometimes called an electronic information board or an electronic whiteboard.

A multi-function device has functions such as a copier, scanner, printer, and facsimile transmission/reception, and is used for printing materials during a meeting, copying materials, digitizing materials, and transmitting materials. A projector is a device that projects an image. For example, by projecting the image displayed on the display by the terminal device 60 onto a screen or the like, it is possible to share the image among prospective participants. Digital signage is a large display used to display any still or moving image. A digital camera is used by each prospective participant to capture and save paper materials or materials displayed on an electronic blackboard.

As shown in FIG. 3, the conference room terminal 90 includes a type without UI (User Interface) and a type with UI (FIG. 4). UI means display. The function of the conference room terminal 90 is slightly different between without UI and with UI. For example, since it is not possible to accept direct user operations without a UI, there are restrictions on the check-in method. In this embodiment, for convenience of explanation, the conference room terminal 90 with the UI shown in FIG. 4 will be 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. As shown in FIG. 3 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 . CPU 201 and memory 202 are connected via system bus 203 to other devices or drivers of conference management server 30 , such as graphics driver 204 and network driver (NIC) 205 .

A graphics driver 204 is connected to an LCD (display device) 206 via a bus to monitor the results of processing by the CPU 201 . The network driver 205 also connects the conference management server 30 to the external network N2 at the transport layer level and the physical layer level to establish sessions with other devices.

Also connected to system bus 203 is I/O bus bridge 207 . On the downstream side of the I/O bus bridge 207, via an I/O bus 208 such as PCI, a storage device such as an HDD (hard disk drive) 209 is connected via IDE, ATA, ATAP80I, serial ATA, SCSI, USB, etc. is connected. The HDD 209 stores a program 209p that controls the conference management server 30 as a whole. The HDD 209 may be an SSD (Solid State Drive). The program 209p may be distributed while being 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 (called a pointing device) is connected to the I/O bus 208 via a bus such as USB, and receives inputs and commands from an operator such as a system administrator. there is

The illustrated hardware configuration of the conference management server 30 indicates hardware elements that the conference management server 30 preferably has.

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 the conference management server 30, or even if it is different, the equipment reservation system 100 of the present embodiment will be explained. There shall be no obstacles on the In addition, since the conference management server 30, reservation management server 20, and chat server 10 are compatible with cloud computing, the hardware configuration of these hardware resources can be dynamically connected/disconnected according to the load. may consist of Note that cloud computing is a form of usage in which resources on a network are used without being conscious of specific hardware resources.

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

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

A media drive 608 controls reading or writing (storage) of data to a medium 607 such as a flash memory. The media drive 608 has a configuration in which a medium 607 from which previously recorded data is read or new data is written and stored is detachable.

Note that the EEPROM 604 stores a program 604p executed by the CPU 601 . The program 604p is application software, OS, etc. for executing various processes in the embodiment. The program 604p may be distributed while being stored in the media 607 or the like, or may be distributed from a server for program distribution.

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

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

The vibration actuator 624 is a motor that vibrates the conference room terminal 90 . For example, when the end time of the conference is approaching, the conference room terminal 90 vibrates to inform prospective participants of the fact.

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 .

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

The short-range wireless communication unit 615 is a communication device that uses a short-range wireless communication antenna 614 and complies with, for example, Bluetooth (registered trademark) or Bluetooth Low Energy (registered trademark) communication standards.

A display 616 is a liquid crystal, organic EL, or the like that displays an image of a subject, various icons, and the like. A 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 units.

The conference room terminal 90 also has its own battery 618 and can be powered by either battery 618 or mains power. Note that the voice input unit 609 includes a microphone for inputting voice. Audio output unit 610 includes a speaker for outputting 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. As shown in FIG. 7, the electronic blackboard includes a CPU 101 that controls the overall operation of the electronic blackboard, a ROM 102 that stores programs used to drive the CPU such as IPL, a RAM 103 that is used as a work area for the CPU 101, a program 104p, a network controller 105 that controls communication with the company network, and an external storage controller 106 that controls communication with the USB memory 5. FIG.

The electronic blackboard also has an external video interface 111 for taking in still images or moving images displayed by the PC 6 on the display of the PC 6 . Also, a GPU 112 that specializes in graphics (image processing of the 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 teleconference terminal 7. It has

Further, the electronic blackboard includes a sensor controller 114 that controls processing of the touch panel, and a touch panel 115 that detects that the indicator 4 and the hand H touch the display 3 . The electronic blackboard also has an electronic pen controller 116 . The electronic pen controller 116 communicates with the pointer 4 to determine whether or not the display 3 is touched by the tip of the pointer 4 or the bottom of the pen. It should be noted that the electronic pen controller 116 may determine the presence or absence of touch and pressure on the portion of the pointer 4 that the user grips and other portions of the pointer 4 in addition to the pen tip and pen butt.

Further, the electronic whiteboard electrically connects 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 and a data bus for connection is provided.

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

<<Reservation management server 20>>
The reservation management server 20 has a communication section 21 and a reservation information management section 22 . Each of these functional units of reservation management server 20 is realized by any one of the components shown in FIG. function or means to

The communication unit 21 transmits and receives various information to and from the conference management server 30 . In this 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, for example.

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 by 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 . FIG. 10 shows an example of a screen displayed on the terminal device 60 of the prospective participant by the Web application. The reservation information management unit 22 is implemented by the CPU 201 in FIG. 5 executing the program 209p.

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

表１は予約情報ＤＢ２９１に記憶されている予約情報の一例を示す。予約情報は会議室の予約状況を管理するための情報である。予約情報には、予約ＩＤに対応付けて予約者アカウント、会議名、会議室ＩＤ、開始時刻、終了時刻、及び、参加予定者アカウントの各項目が登録されている。予約ＩＤは予約情報の１レコードを識別する識別情報（予約識別情報）である。ＩＤは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, each item of a reserver account, a conference name, a conference room ID, a start time, an end time, and a prospective participant account is registered in association with the reservation ID. The reservation ID is identification information (reservation identification information) that identifies one record of reservation information. ID is an abbreviation for Identification and means an identifier or identification information. An ID is 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 object from a plurality of objects. The same applies to IDs other than the reservation ID. A reserver account is an account of a prospective participant who has reserved a conference room. The conference name is the name of the conference arbitrarily given by the prospective participants. The conference room ID is identification information for identifying a conference room in the company network and is assigned by the conference management server 30 . The start time is the beginning of the time period in which the conference room is reserved (the time when the conference starts), and the end time is the period of the time period in which the conference room is reserved (the time when the conference ends). A prospective participant account is an account of a prospective participant who plans to participate in the conference. Note that the accounts in Table 1 are all accounts issued by the reservation management server 20 .

<<Chat Server 10>>
The chat server 10 has a communication section 11 and a text processing section 12 . Each of these functional units of chat server 10 is implemented by any one of the components shown in FIG. It is a function or a means.

The communication unit 11 transmits and receives various information to and from the conference management server 30 . In this embodiment, the conference management server 30 receives from the conference management server 30 information about the reservation of the conference room, information identifying the notification robot, and information identifying the group to be notified (this information identifying the notification robot is is notified in advance from the chat server 10 as the identification information of the notification robot). The prospective participant sends to the conference management server 30 a response indicating that the prospective participant has already read the information about the reservation of the conference room, or a response of the prospective participant to the displayed information about the reservation of the conference room. The communication unit 11 is implemented by the CPU 201 shown in FIG. 5 executing the program 209p and controlling the network driver 205, for example.

The text processing unit 12 identifies the group to be notified from the group information DB 191 of Table 2 based on the information identifying the notification robot and the information identifying the group of the notification destination notified from the conference management server 30, and assigns the notification robot to the group as the notification robot. Send information about room reservations to prospective attendees you belong to. Therefore, in principle, notifications are made for the number of prospective participants. The text processing unit 12 can perform so-called push notifications. For example, the mechanism is as follows. The chat application 60a receives a push notification ID (token) from a server operated by an OS (Operating System) manufacturer. This server associates the token with the device (terminal device 60). The chat application 60a registers the token and the account of the chat application 60a in the chat server 10 in advance. When the chat server 10 performs the push notification, it identifies the account of the chat application 60a, so it is possible to identify the associated token. The chat system designates the token and transmits the notification contents to the 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 implemented by the memory 202, the HDD 209, and the like in FIG. A group information DB 191 is stored in the storage unit 19 .

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

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, group names, member accounts 1 to n (n=4 in Table 2), and notification robot accounts are registered in association with team IDs.

A 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 further has a plurality of groups according to purposes (for example, a group for product A, a group for product B, etc.). etc.), one of the members belonging to the team belongs to the group (the number of members belonging to the group is from 1 to all members). That is, the notification destination is specified by the team ID and group name. However, since the method of identifying the notification destination differs depending on the chat system, if there is identification information that can uniquely identify the group, that information alone or three or more pieces of information may be used for identification.

The group name is the name of the group with which the chat system shares text, and uniqueness is guaranteed. Member accounts 1 to n are group member accounts, and these accounts are issued by the chat server 10 . In this embodiment, a notification robot is registered as a member for notifying information about reservation of a conference room. The notification robot can be said to be an agent or fictitious member of the conference management server 30, so to speak. The statement (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 . These functional units of the conference management server 30 are implemented by any one of the constituent elements shown in FIG. function or means to This program 209p is distributed from a program distribution server or stored in a storage medium.

The communication unit 31 transmits and receives various information to and from the reservation management server 20 , the chat server 10 , the registration terminal 50 and the terminal device 60 . In the present embodiment, reservation information is received from the reservation management server 20, information on conference room reservations is transmitted to the chat server 10, a group in which the notification robot is registered is received from the registration terminal 50, and a chat system is registered from the terminal device 60. Accepts group-to-account mappings. In addition, it also communicates with the conference room terminal 90 . The communication unit 31 is implemented by the CPU 201 in FIG. 5 executing the program 209p and controlling the network driver 205, for example.

The information association unit 32 mainly performs processing related to pre-registration work. That is, domain registration is received 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 is associated with the account of the reservation management server 20 and registered in the associated information DB 491 . Details will be described later. The information association unit 32 is implemented by the CPU 201 in FIG. 5 executing the program 209p.

The reservation information acquisition unit 33 designates 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. Among the reservation information held by the reservation management server 20, reservation information for a predetermined period future from the present is acquired. The predetermined period is determined by how far in advance the conference room reservation information is to be notified. The reservation information acquisition unit 33 is implemented by the CPU 201 in FIG. 5 executing the program 209p.

The notification determination unit 34 determines whether or not there is a reservation with a start time that satisfies the conditions for notification in the reservation information. For example, the notification setting DB 496 is referred to, and it is determined that notification will be made when the date and time set by counting backward from the start time of the reservation is reached. Note that if the notification robots are divided according to their roles, such as a notification robot for reminders and a notification robot for accepting reservations, the notification robot is specified according to the process. The notification determination unit 34 is implemented by the CPU 201 in FIG. 5 executing the program 209p.

When the notification determination unit 34 determines that notification is to be made, the conference information notification unit 37 designates the information identifying the notification robot and the information identifying the notification destination group, and notifies the chat server 10 of the information regarding the reservation of the conference room. request to The notification is made several times, but at least one of the notifications includes the meeting identification information. The conference identification information is information for the conference management server 30 to confirm that the prospective participants have the right to use the reserved conference room during the reserved time slot. The conference information notification unit 37 generates conference identification information at least before final notification. Note that the conference identification information is registered in the conference identification information DB 494 . The meeting information notification unit 37 is implemented by the CPU 201 in FIG. 5 executing the program 209p.

The control information generation unit 35 generates control information for the electronic device 70 with reference to the reservation information, and registers the control information in the control information DB 497 . For example, control information for powering on the electronic device 70 is generated several minutes before the meeting start time, and control information for powering off the electronic device 70 is generated when checkout is detected. Control information is stored in the control information DB 497 . The control information generator 35 is implemented 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 implemented 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 check-in is permitted or not, and registers the conference status in the conference management information DB 493 . A set of conference room ID and conference identification information is registered in the conference identification information DB 494, and check-in is recognized 5 to 10 minutes before the start time of the conference specified by the reservation ID. The check-in manager 38 is implemented by the CPU 201 in FIG. 5 executing the program 209p.

The initial setting unit 39 performs processing related to initial setting of the conference room terminal 90 . For example, a list of conference rooms is provided to the registration terminal 50 of the manager of the equipment reservation system 100, the conference room ID and the name of the conference room selected by the manager of the equipment reservation system 100 are specified, and furthermore, 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 manager 38 is implemented 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, the HDD 209, etc. in FIG. The storage unit 49 stores a correspondence information DB 491, a meeting management information DB 493, a meeting 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 correspondence information stored in the correspondence information DB 491 . The correspondence information is information that associates the account of the reservation management system with the group name of the chat system. The correspondence information has 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. Accounts of prospective participants issued by the reservation management server 20 are registered in the member accounts 1 to n. Also, as shown in Table 3, chat system accounts may be registered. In order to notify the group, information for specifying the account of the user who reserved the conference to the reservation management server and the group and channel of the notification destination (in this embodiment, the team ID and the group ( Channel) name) is sufficient, and accounts of all members belonging to the group do not necessarily have to be registered. However, when notifying an individual user, the account information of each chat system is required, so it may be registered 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 an item of status. Status means the status of reservation. For example, a status such as notification of information regarding the reservation of the conference room, usage confirmation, check-in completion, check-out, or cancellation (cancellation) is registered.

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

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

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

Table 6 shows an example of customer domain information stored in the customer domain DB 495. The customer domain information is information for managing customer domains and customer administrator accounts. In the customer domain information, the customer's domain name and the customer's administrator account are associated and registered. The customer domain in Table 6 is the domain of the account (mail address) issued by the reservation management server 20 . Also, the administrator account is the account of the administrator (representative) of the customer. Note that 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 settings regarding notification for each customer. Customer domain names and notification settings are associated and registered in the notification setting information. In the notification setting, the timing of how long before the start time of the conference is set to notify the information regarding the reservation of the conference room. Alternatively, a fixed date and time may be set. Also, the timing does not need to be one, and multiple notification settings may be registered for one customer.

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

Table 8 shows an example of control information stored in the control information DB 497. The control information is information for controlling the electronic equipment 70 in the conference room. The control information includes each item of conference 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 . The reason why the time to be controlled is not registered is that it is difficult to transmit from the conference management server 30 of the external network to the conference room terminal 90. is generated, the control content is transmitted.

<<Registered terminal 50>>
The registration terminal 50 has a communication section 51 , an operation reception section 52 and a display control section 53 . Each of these functional units of registration terminal 50 is realized by any one of the components shown in FIG. It is a function or a means. This program 209p is distributed from a program distribution server or 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 will be described in detail together with the terminal device 60. FIG.

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

The terminal device 60 includes a communication section 61a, an operation reception section 61b, a chat communication section 62, a text display section 63, an application communication section 67, a server communication section 65, a display control section 66, an application communication section 67, and a terminal communication section 68. have Each of these functional units of the terminal device 60 is realized by operating one of the components shown in FIG. It is a function or a means. This program 209p is distributed from a program distribution server or stored in a storage medium. Since the chat application 60a and the conference application 60b are running on the terminal device 60, the program 209p includes the chat application 60a and the conference application 60b.

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

The operation reception unit 61b receives various operations of prospective participants on the terminal device 60 . The operation reception unit is implemented by the CPU 201 in FIG. 5 executing the program 209p and controlling the input device 210, for example.

The chat communication unit 62 of the chat application 60a transmits and receives various information to and from the chat server 10 . In this embodiment, the information about the reservation of the conference room is received from the chat server 10, and the chat server 10 is notified whether the conference room will be used or cancelled. The chat communication unit 62 is implemented by the CPU 201 in FIG. 5 executing the program 209p and controlling the network driver 205, for example.

The text display unit 63 of the chat application 60a displays the text (information regarding the reservation of the conference room) transmitted from the chat server 10. FIG. For example, the speaker is a notification robot and the text is displayed as if the notification robot had typed it. The text display unit 63 is implemented by the CPU 201 of 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 regarding the reservation of the conference room, the chat application 60a designates the conference application 60b to the OS and transmits the conference identification information. request notification of The OS can start the conference application 60b. Application communication unit 64 is implemented by CPU 201 in FIG. 5 executing chat application 60a.

A server communication unit 65 of the conference application 60 b communicates with the conference management server 30 . In this embodiment, a two-dimensional code including conference identification information is acquired from the conference management server 30 . The server communication unit 65 is implemented 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 two-dimensional code and the like notified from the conference management server 30 on the LCD 206 . The display control unit 66 is implemented 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 kinds of information (such as conference identification information included in the information regarding the reservation of the conference room) from the chat application 60a via the OS. The application communication unit 67 is implemented 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 existence of the conference room terminal 90 by short-range wireless communication such as Bluetooth (registered trademark), and transmits the conference identification information when the conference room terminal 90 is detected. It also provides the conference room terminal 90 with a function of displaying a two-dimensional code. The terminal communication unit 68 is implemented by the CPU 201 in FIG. 5 executing the conference application 60b.

<<Meeting room terminal 90>>
The conference room terminal 90 has a server communication section 91 , a terminal device communication section 92 , an operation reception section 93 , a display control section 94 and an electronic equipment communication section 95 . Each of these functional units of the conference room terminal 90 is realized by any one of the constituent elements shown in FIG. It is a function or a means. This program 604p is distributed from a program distribution server or stored in a storage medium.

The server communication section 91 communicates with the conference management server 30 . Since the conference room terminal 90 exists in the company network, it is difficult for the conference management server 30 to communicate with the conference room terminal 90 . Therefore, the server communication unit 91 communicates with the conference management server 30 using communication techniques such as polling (periodic communication with the conference management server 30) and WebSocket. The server communication section 91 of this embodiment transmits the conference identification information and the conference room ID that the terminal device communication section 92 has received 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 the reservation information of the conference room for the day. Also, the server communication unit 91 receives control information from the conference management server 30 . The server communication unit 91 is implemented by the CPU 601 in FIG. 6 executing the program 604p and controlling the wireless LAN communication unit 613, for example.

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

The electronic device communication section 95 communicates with the electronic device 70 . In this 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 implemented by the CPU 601 in FIG. 6 executing the program 604p and controlling the wireless LAN communication unit 613, for example.

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 implemented by the CPU 601 in FIG. 6 executing the program 604p to control the display 616 and the like.

An operation reception unit 93 receives various operations for the conference room terminal 90 . The operation reception unit 93 is implemented by the CPU 601 in FIG. 6 executing the program 604p and controlling the touch panel 617, for example.

The conference room terminal 90 also has a storage unit 99 . The storage unit 99 is implemented by the ROM 602 and EEPROM 604 shown 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 has a basic function section 71 , a control section 72 and a communication section 73 . Each of these functional units of the electronic device 70 is a function realized by any one of the components shown in FIG. or means. This program 104p is distributed from a program distribution server or 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 implemented by the CPU 101 shown in FIG. 7 executing the program 104p and controlling the network controller 105, for example.

The control unit 72 controls the electronic device 70 as a whole. In this embodiment, the power of the electronic device 70 is controlled to be ON or OFF according to the control information. The control unit 72 is implemented 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 strokes are displayed, and an image of the PC is displayed on the display 3 . The basic function unit 71 is implemented by the CPU 101 shown in FIG. 7 executing the program 104p and controlling the hardware elements shown in FIG.

<Reservation of meeting room>
Reservation of a conference room will be described with reference to FIG. FIG. 10 shows 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 has 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 . A prospective participant logs in to the reservation management server 20 with an account of the reservation management server 20 and inputs necessary items on the reservation screen 401 . Since the conference room input field 405 displays selectable conference room names and conference room IDs in a pulldown, the user can select a conference room by selecting the conference room name.

Also, in the conference room input field 405, “connection ID: XXX . . . X” is set. The connection ID is connection destination information for connecting the electronic device 70 at one site to the other site. In the case of a telephone, it corresponds to a telephone number. In other words, it is information for connecting the electronic device 70 at one base and the electronic device 70 at the other base. The connection destination information is information for identifying the remote conference device of the connection destination, and the remote conference devices are connected using the connection destination information. The connection destination information may be information that can identify the connection destination, and may be identification information of the teleconference device itself, identification information on the network of the teleconference device itself such as an IP address, or user ID or the like. It may be identification information associated with a user who uses the device.

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 either one of the electronic devices 70 can be connected to the connection destination, it is unnecessary to set the connection ID of the electronic device 70 installed in one of the conference rooms on the reservation screen 401 of the other conference room. However, the connection ID may be set on the reservation screens 401 of both conference rooms where remote conferences are held.

A calendar selection field 406 is also displayed on the reservation screen 401 . A calendar selection field 406 is a field for the user to select a calendar to be shared by the group. Therefore, the user can use different calendars.

<Example of pre-registration screen>
An example of a screen input by the administrator of the facility reservation system 100 or the prospective participant in the preliminary 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. As shown in FIG. The registration work initial screen 411 is a web page provided by the conference management server 30, for example. The registration operation initial screen 411 has an add notification robot button 412 , an administrator login button 413 , and a reservation management server login button 414 . When the add notification robot button 412 is pressed, the notification robot registration screen 421 shown in FIG. 12 is displayed. When the administrator login button 413 is pressed, the domain management screen 431 shown in FIG. is pressed, the screen transitions to the account correspondence screen 441 of FIG.

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

The notification robot registration screen 421-2 of FIG. 12(b) has an account input field 424 and a password input field 425. The administrator of the equipment reservation system 100 inputs the accounts and passwords of the members belonging to the team ID entered in FIG. 12(a). That is, the authority to add notification robots to the team is authenticated.

The notification robot registration screen 421-3 of FIG. 12(c) has a notification destination account display field 426 and an authentication button 427 to be notified by the notification robot. A specific account may be selected in the notification destination account display field 426, or a group may be selected. By pressing pull-down key 426a, the 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. The message input field 428 is a field in which the manager of the facility reservation system 100 inputs text to be spoken by the notification robot on a trial basis. As a result, the administrator (and each member) of the equipment 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. As shown in FIG. A domain management screen 431 is provided by the conference management server 30 . The domain management screen 431 is a screen for the manager of the equipment reservation system 100 to set the domain of the customer who can use the equipment reservation system 100 . The facility reservation system 100 is used by customers who have accounts that include a registered domain as part. The domain management screen 431-1 of FIG. 13(a) has an administrator account input field 432 and a password input field 433. FIG. An administrator of the equipment reservation system 100 logs into the conference management server 30 with the administrator account and password of the equipment reservation system 100 .

13(b) and 13(c) are the domain management screen 431-2, and FIG. 13(c) is an enlarged view of FIG. 13(b). The domain management screen 431 - 2 has a domain name entry field 435 , an account entry field 436 and a registration button 437 . In the domain name entry field 435, the domain of the customer who uses the reservation management server 20 is entered. In the account input field 436, the account of the manager of the customer who uses the reservation management server 20 is input.

That is, the domain and account of the reservation management server 20 of the customer are registered in the conference management server 30 . The customer uses this account (issued by the reservation management server 20) to log in to the conference management server 30, and the conference management server 30 logs in to the reservation management server 20 with the registered account to acquire the reservation information, and the registered Target subscriber accounts containing domains for notification.

Note that the domain has already been registered as indicated by the check marks in FIGS. 13(b) and 13(c). As a result, the administrator of the equipment reservation system 100 can register the domain only by checking the check mark, and can avoid the occurrence of input errors in spelling of the domain.

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

The account correspondence screen 441-2 in FIG. 14B includes an account 443 of the administrator of the logged-in customer (account of the reservation management server 20), a chat system selection field 444, a chat system account input field 445, a 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 chat system account in the chat system account entry field 445 . The team ID of the chat system to which the notification robot is added is entered in the chat system team ID entry field 446, and the group name is entered in the group name selection field 446-2.

An account correspondence screen 441-3 in FIG. 14(c) shows a group name input screen of the chat system, and an account correspondence screen 441-4 in FIG. 14(d) shows a login screen to the chat system. As in FIG. 12, prospective participants specify a group name in the group name field 447, enter an account for the chat system in the account entry field 448, enter a password in the password entry field 449, and log in to the chat system. , it is confirmed that the input contents of FIG. 14(b) are appropriate. If confirmed, the conference management server 30 associates the group name with the account of the customer's manager and registers them.

<Sequence of pre-registration work>
First, the token of the notification robot will be explained. Only one notification robot needs to exist on the conference management server. The conference management server 30 performs a process of acquiring a notification robot token before the conference management server 30 starts operating.

For example, in response to a notification robot addition request from the conference management server 30, the chat server 10 generates a notification robot and assigns a unique token to this notification robot. The communication unit 11 of the chat server 10 transmits the notification robot token to the conference management server 30 . The information association unit 32 of the conference management server 30 manages the notification robot token. As a result, the conference management server 30 can send notifications as a notification robot.

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

FIG. 15 is an example of a sequence diagram showing a procedure for registering a 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 request for addition is sent by selecting the add button 412 on the registration operation initial screen 411 of FIG. 11 displayed by the conference management server 30 .

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

S3: As a result, the chat server 10 causes the registration terminal 50 to display the notification robot registration screen 421-1.

S4: The administrator of the equipment reservation system 100 enters the group name in the notification robot registration screen 421-1. The operation reception unit 52 of the registration terminal 50 receives 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 the notification robot registration screen 421-2 to the registration terminal 50. FIG.

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 equipment reservation system 100 enters the chat system account name and password (one of the members of the group). The operation reception unit 52 of the registration terminal 50 receives the input of the account name and password of the chat system, and the communication unit 51 transmits them to the chat server 10 .

S7: The chat server 10 authenticates upon receipt of the account name and password of the chat system, and transmits the 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 . Operation accepting unit 52 of registration terminal 50 accepts pressing of authentication button 427 and transmits authentication OK to 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 associates the team ID with the notification robot token and manages them.

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

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

S2: The administrator of the equipment reservation system 100 inputs the account name and password of the administrator of the equipment 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 them to the conference management server 30 .

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

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 equipment reservation system 100 inputs the customer's domain and the account of the customer's administrator in the reservation management server 20 . The operation reception unit 52 of the registration terminal 50 receives the domain and account of the customer of the reservation management server 20 , and the communication unit 51 transmits them to the conference management server 30 .

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

FIG. 17 is an example of a sequence diagram showing a procedure for associating groups in the chat system with accounts in the reservation management server 20. As shown in FIG.

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

S2: The prospective participant selects the account name registered in FIG. 16 and logs in. Therefore, the account of the customer's manager in the reservation management server 20 is specified in the conference management server 30 .

S3: When the conference management server 30 permits login, it transmits an account correspondence screen 441-2 to the terminal device 60. FIG.

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

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 to verify the account name and group name. As a result, the terminal device 60 displays the account correspondence screen 441-3. This account correspondence screen 441 includes a team ID.

S6: The operation reception unit 61b of the terminal device 60 receives the operation by the prospective participant's operation, and the communication unit 61a transmits the team ID to the chat server 10. FIG.

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: Prospective participants enter the account name and password of the chat system. The operation reception unit 61 b of the terminal device 60 receives the input, and the communication unit 61 a 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 sends a confirmation to the conference management server 30 when the authentication is established. Redirect processing in this case is omitted in the figure.

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

When a customer reserves a conference room with the reservation management server 20 through the above processing, the reservation management server 20 can notify the terminal devices 60 of prospective participants via the chat server 10 of information regarding the reservation of the conference room.

<Timing of notification of information regarding conference room reservations>
FIG. 18 is an example of a diagram for explaining the timing of notification of information regarding conference room reservations.
• Timing 1: At the timing of the notification registered in the notification setting DB 496, first, the conference information notification unit 37 of the conference management server 30 notifies the terminal device 60 of information regarding the reservation of the conference room.
• Timing 2: If there is no response from prospective participants for 10 minutes, the conference information notifier 37 automatically cancels the reservation management server 20 .
• Timing 3: When there is a response to use the conference room, the conference information notification unit 37 of the conference management server 30 again notifies the information regarding the reservation of the conference room 10 minutes before the start time of the conference. In this embodiment, conference identification information is transmitted as an example.
- Timing 4: Start time of the conference - Timing 5: If the conference management server 30 does not receive a check-in notification from the conference room terminal 90 even after 10 minutes have passed since the start time, the check-in management unit of the conference management server 30 38 automatically cancels the reservation management server 20 .

It should be noted that the reservation will not be canceled if even one of the prospective participants of the conference responds to the information regarding the reservation of the conference room. However, responses from all prospective participants may be required, or responses from half or more of the prospective participants may be required.

<Processing notification of information related to conference room reservation>
FIG. 19 is an example of a sequence diagram showing a procedure for the conference management server 30 to notify the information regarding the reservation of the conference room.

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

S2: Next, the reservation information acquisition unit 33 reads out the customer's notification settings from the notification setting DB 496 .

S3: The reservation information acquisition unit 33 logs in with the account of the customer domain DB 495 entered in FIG. 13 and acquires reservation information from the reservation management server 20 . The period to be acquired is the period set as the notification timing in the notification setting. For example, when notifying information about reservation of a conference room one month in advance, reservation information up to one month in advance 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 and determines whether or not it is time to notify (remind) the information regarding the reservation of the conference room. Details will be described with reference to the flow chart of FIG.

FIG. 20 is an example of a flow chart of a procedure for the notification determination unit 34 to determine whether or not to notify the information regarding the reservation of the conference room.

The notification determination unit 34 searches the customer's domain name in the customer domain DB 495 from the reservation information (S10). Since reservation information is obtained by designating the customer's domain, all the accounts of the reserving party or prospective participants in 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 for the domain of the customer. Here, it is assumed that the reservation information includes a reservation person's account or prospective participant's account including the customer's domain name in the customer domain DB 495 .

Next, the notification determination unit 34 determines whether or not there is reservation information for the notification timing (S20). That is, 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), it is determined to notify. If the determination in step S20 is No, the processing of FIG. 20 ends because no notification is made.

If the determination in step S20 is YES, the notification determination unit 34 searches the correspondence information DB 491 for the subscriber account acquired from the reservation information, and specifies group identification information including the team ID and group name (S30). The conference management server 30 can notify the group by designating the team ID, the group name (information specifying the group), and the token of the notification robot.

The meeting information notifying unit 37 serves as a notification robot and notifies the prospective participants of information regarding the reservation of the conference room by using information for identifying the group including the specified team ID and group name (S40).

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

S1: The conference information notification unit 37 specifies the specified team ID and group name together with a token indicating that the conference management server 30 is a notification robot, and transmits a message (information on reservation of the conference room) to the chat server 10. . Since the conference identification information may be created before the notification of the information regarding the reservation of the conference room, it may be transmitted at this timing (timing 1 in FIG. 18). In addition, a reservation ID is included 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 to "notified".

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

S3: The chat communication section 62 of the terminal device 60 receives the message, and the text display section 63 displays the message. This message includes a button used as a display component and a cancel button, as shown in FIG. 22, which will be described later. When the prospective participant presses the button used for the message or the cancel button, the operation accepting unit 61b of the terminal device 60 accepts the press.

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

S5: The communication unit 21 of the chat server 10 transmits the fact that the button to be used has been pressed or the fact that the cancel button has been pressed and the reservation ID to the notification robot of the conference management server 30 . The communication unit 31 of the conference management server 30 receives the fact 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 participants. The conference information notifier 37 sets the status of the conference management information DB 493 to confirmed. Also, when the cancel button is pressed, the conference information notifier 37 sets the status of the conference management information DB 493 to cancel.

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

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

<Text display screen>
FIG. 22 shows an example of information related to conference room reservations displayed on the terminal device 60 . FIG. 22( a ) is an example of information relating to conference room reservation notified at the timing of the notification setting DB 496 . Such a message is displayed at timing 1 in FIG. 18, for example.
"2017-05-18 20:47:00 A meeting (regular) has been reserved in Conference Room A. Select "Use" if you want to use it as reserved, or "Cancel" if you do not want to use it. If you do not respond within 10 minutes, your reservation will be automatically canceled."
The prospective participant can take appropriate measures such as pressing a button 451 to be used or a cancel button 452 after viewing the message. Further, when 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, thereby reducing vacant reservations.

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

Further, when the prospective participant presses a button 451 to be used, the conference information notification unit 37 transmits a confirmation 453 via the chat server 10 to the chat application 60 a of the terminal device 60 . When the prospective participant presses the cancel button 452 , the conference information notification unit 37 transmits a cancellation 454 to the chat application 60 a of the terminal device 60 via the chat server 10 .

FIG. 22(b) shows a message indicating that the reservation has been canceled without pressing the cancel button.
"The reserved meeting room 'Meeting (Regular) 2017-05-18 20:47:00 Meeting room A' has been cancelled. ”
The prospective participants can see the message and understand that the conference room has been cancelled.

FIG. 22(c) shows information related to the reservation of the conference room further displayed on the terminal device 60 after the use button 451 is pressed and the use is confirmed.
The use of "Meeting (Regular) 2017-05-18 20:47:00 Conference Room A" has been confirmed.
Please check in from the URL below.
XXXX://XXX.tk?receptID=NNN...N"
N is any number or alphabet. Such a message is displayed at timing 3 in FIG. 18, for example. If the use has already been confirmed, the message includes the conference identification information "NNN...N" in this embodiment. The prospective participant inputs this conference identification information to 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 reservation of the conference room in FIG. 22(a). Also, the same conference identification information may be notified multiple times.

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

“XXXX://XXX.tk” in FIG. 22(c) is the URL of the conference management server 30 . Since "NNN...N" is specified in the parameter, the terminal device 60 can access the conference management server 30 together with the conference identification information. As a result, the check-in management unit 38 of the conference management server 30 can generate 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. 22(d) shows a message indicating that check-in has been accepted. Details of check-in will be described later.
"Reserved meeting room "Regular meeting 2017-05-18 20:47:00 Meeting room A"
has been accepted for check-in. ”
The prospective participants can see the message and know that one or more of the prospective participants has checked in. In addition, you may display who checked in.

<Operating procedure of the conference management server>
FIG. 23 is an example of a flow chart diagram showing a procedure for the conference management server 30 to notify the information regarding the reservation of the conference room.

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

The meeting information notification unit 37 determines whether or not it has received a response of "use" or "cancel" (S20).

When receiving a response to the effect of canceling, the meeting information notification unit 37 again notifies the effect of cancellation from the notification robot (S30). Note that the reservation ID included in the response can identify the reservation person account, and the group can be identified from the reservation person account. Cancellation is registered in the status of the conference management information DB 493 .

When receiving a response indicating use, the meeting information notification unit 37 notifies the use confirmation from the notification robot again (S40). Confirmation of use is registered in the status of the conference management information DB 493 .

Next, the meeting information notification unit 37 determines whether or not a predetermined time has passed since the start time (S50). Standby until a predetermined time is reached.

Before a predetermined time, 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 meeting information notification unit 37 generates meeting identification information and registers it in the meeting identification information DB 494 in association with the reservation ID and the conference room ID. By doing so, it becomes easier to suppress vacant reservations, and the user can 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 meeting information notification unit 37 determines whether or not a predetermined time has passed since the notification based on the notification setting DB 496 (S70). . The determinations in steps S20 and S70 are repeated until a predetermined time elapses.

Then, if the response of "use" or "cancel" is not received even after the predetermined time has passed (Yes in S70), the meeting information notification unit 37 notifies the notification robot of the cancellation (S80). Cancellation is registered in the status of the conference management information DB 493 .

<Notification to individual prospective participants>
The notification robot of the chat server 10 can send messages to all members of the same group in real time. However, the equipment reservation system 100 of this embodiment can also limit the destination of the message to some members in the group. In this case, it is necessary to specify the accounts of the reservation management server 20 of all prospective participants to whom notification is to be given on the reservation screen 401 of FIG.

<<Method 1>>
For example, there is a case where a notification destination of information regarding reservation of a conference room is determined in advance. In this case, the conference information notification unit 37 only needs to notify the predetermined prospective participants of the information regarding the reservation of the conference room. For example, it is possible to notify prospective participants of a subscriber account. In the chat server 10, the notification robot generally sends a message to all the members of the group. request to do so. In this case, the conference management server 30 needs to associate and store the chat server 10 accounts and reservation management server 20 accounts of all prospective participants to whom notification is to be sent.

<<Method 2>>
There is a method in which the administrator of the equipment reservation system 100 or prospective participants sets a notification list in advance.
Notification list when prospective participants are Mr. A and Mr. B: Mr. A and Mr. B Notification list when prospective participants are Mr. A, Mr. B and Mr. C: Mr. A, Mr. B and Mr. C Notification list for Mr. A, Mr. B, Mr. C, and Mr. D: Entire group decide to notify

<<Method 3>>
Considering the group on the chat system side, only the prospective participants are notified among the groups having members closest to the reservation person account and the prospective participant account of the reservation information.
・Case 1
Group on the chat system side: Mr. A, Mr. B. Participants in the reservation information: Mr. A, Mr. B. In this case, the conference information notification unit 37 notifies Mr. A and Mr. B.
・Case 2
Group 1 on the chat system side: Mr. A, Mr. B,
Group 2 on the chat system side: Mr. A, Mr. C, Mr. D Participants in the reservation information: Mr. A and Mr. B In the case of Mr. A and Mr. B, group 1 is closer, so the meeting information notification unit 37 sends Mr. A and Mr. B. Notice. In this case, the notification robot must be added to each of the above groups 1 and 2, and the conference management server 30 can store each group, the account of the chat server 10 belonging to the group, and the account of the reservation management server 20. must be associated and stored.

<Initial settings for meeting room terminals>
A conference room ID, a conference room name, a URL of the conference management server 30, and the like are preferably set in the conference room terminal 90 . For this reason, the administrator of the equipment reservation system 100 makes initial settings for the conference room terminal 90 .

FIG. 24 is an example of a sequence diagram for initial setting of the conference room terminal 90. As shown in FIG.

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

S2: The administrator of the equipment 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 administrator of the facility reservation system 100 presses the conference room in which he/she is (to be 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 section 39 of the conference management server 30 generates a two-dimensional code. The two-dimensional code includes the conference room ID, conference room name, and URL of the conference management server 30 . As a result, 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 . Also, the URL of the conference management server 30 enables communication from the conference room terminal 90 to the conference management server 30 .

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

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

S6: The administrator of the equipment reservation system 100 presses the conference room registration menu. The operation reception unit 93 receives the 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 section 53 of the registration terminal 50 displays the two-dimensional code of step S3, the terminal device communication section 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 connection is possible. For example, confirm that Ack is returned.

S7.1.1: The server communication unit 91 of the conference room terminal 90 acquires the latest event (reservation information of the conference room in the current time zone, check-in status, control information, etc.) from the conference management server 30 . If it has not been checked in, the conference room terminal 90 displays an entrance waiting screen.

S8: If not checked in, the conference room terminal 90 starts advertising Bluetooth (registered trademark) Low Energy. This enables the terminal device 60 to 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 reserves a conference room.

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

S1.1: The server communication unit 91 of the conference room terminal 90 inquires the reservation status of the conference management server 30 using the initially set conference room ID 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 for the current day only, or can be set by the general user, such as one week ahead or one month ahead. This allows general users to check the reservation status of the conference room they are in.

<Check-in>
Below are instructions for checking in in several ways.

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

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

S2: As shown in FIG. 22(c), the conference information notification unit 37 of the conference management server 30 transmits conference identification information to the chat server 10 (terminal device 60) together with information regarding the reservation of the conference room. 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 regarding the reservation of the conference room. The operation accepting unit 61b of the terminal device 60 accepts pressing of the URL. In the terminal device 60, the browser of the chat application 60a is activated.

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

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

S4: The prospective participant selects a check-in menu using the two-dimensional code displayed by 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 close 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 obtain 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 from a long time before the start time, the start time is specified by referring to the conference management information DB 493 using the reservation ID of the conference identification information DB 494 . Then, for example, if the current time is about 5 to 10 minutes before the start time of the conference (before a 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 with the conference time and whether or not check-in is possible. Note that 5 to 10 minutes is just an example, and if the same conference room is not reserved, check-in may be permitted even 5 to 10 minutes earlier. Note that the communication unit 31 of the conference management server 30 returns the start time.

If check-in is permitted, 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, a message such as "the 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 prospective participants manually enter conference identification information>>
FIG. 27 is an example of a sequence diagram showing a check-in procedure when a prospective participant forgets to bring the terminal device 60 with them. Prospective participants log in using their remembered or recorded meeting identification information.

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

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

S3: The prospective participant presses the menu “check in with meeting identification information” displayed by the meeting room terminal 90 . The operation reception unit 93 of the conference room terminal 90 receives the operation, and the display control unit 94 displays the input field for the conference identification information.

S4: Prospective participants enter 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.

Subsequent processing is the same as in FIG. In this way, prospective participants can check-in without the terminal device 60 if they remember the conference identification information.

<<Check-in by Near Field Communication>>
FIG. 28 is an example of a sequence diagram of check-in by a prospective participant through short-range wireless communication.

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

S2: As shown in FIG. 22(c), the conference information notification unit 37 of the conference management server 30 transmits conference identification information to the chat server 10 (terminal device 60) together with information regarding the reservation of the conference room. 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 section 64 to start the conference application 60b.

S3.1: As a result, the conference application 60b is activated and holds the information regarding the reservation of the conference room.

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 the peripheral and the terminal device 60 is the central.

S5.1: The terminal communication unit 68 of the terminal device 60 connects with the conference room terminal 90 by Bluetooth Low Energy (registered trademark).

S5.2: The terminal communication unit 68 of the terminal device 60 writes the conference identification information into 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 manager 38 sends the check-in result to the conference room terminal 90. At this time, it is preferable to transmit the connection ID included in the reservation information to the conference room terminal 90 as well. 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 a characteristic for reading the check-in result and transmits it to the terminal device 60. do.

S5.3 S5.4: The terminal communication unit 68 of the terminal device 60 obtains the check-in result by appropriately obtaining 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 allowed, the following is done.
S6.3: The terminal device communication unit 92 of the conference room terminal 90 finishes advertising 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: Then the end time of the meeting elapses. Prospective attendees check out. The display control unit 94 of the conference room terminal 90 displays waiting for entry (waiting for check-in). The checkout process is illustrated in FIG.
S6.7: The terminal device communication unit 92 of the conference room terminal 90 resumes advertising Bluetooth Low Energy (registered trademark).

If check-in is not possible, the following will be executed.
S6.8: The display control unit 94 of the conference room terminal 90 displays an error message. For example, a message such as "the 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).

<Check-out procedure>
FIG. 29 is an example of a sequence diagram for a prospective participant to check out.

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

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

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

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

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

S1.1: The conference room terminal 90 starts and automatically starts the terminal application.

S1.2: The conference room terminal 90 reads the settings. This setting includes the initially set URL of the conference management server 30, the name of the conference room, the ID of the conference room, and the like.

The following processing is executed when the initial settings have been 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 slot, whether or not check-in has been completed, etc. are sent.

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

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

S1.2.4: The terminal device communication unit 92 of the conference room terminal 90 restarts advertising 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 the conference management server>
FIG. 31(a) is an example of a flow chart of processing for automatically canceling a reservation by the conference management server 30. FIG.

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

First, the status becomes use confirmed (S10). Then, the check-in management unit 38 of the conference management server 30 determines whether or not 10 minutes have passed since the start time (S20).

Then, when 10 minutes have passed since the current time passed the start time, the check-in management unit 38 refers to the status and determines whether or not the check-in has been completed (S30).

If the check-in is not completed within 10 minutes (No in S30), the check-in management unit 38 cancels the reservation (S40). If canceled, the check-in management unit 38 will not accept check-in even if the conference identification information and the conference room ID are sent. The conference management server 30 designates the reservation ID and notifies the reservation management server 20 that the reservation has been canceled. This makes it possible to reduce vacant reservations.

FIG. 31(b) is an example of a flowchart for check-in and check-out processing of the conference management server 30. FIG. Note that, for example, the processing of FIG. 31 starts when the status of the conference management information DB 493 becomes use confirmation.

The check-in manager 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 to identify the reservation ID (S20).

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

The check-in management unit 38 determines whether or not 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 notifies the conference room terminal 90 (S50).

If the determination in step S40 is YES, the check-in management unit 38 permits check-in and sends a notification to that effect to the conference room terminal 90 (S60). In addition, the status of the conference management information DB 493 is set to "checked in". The conference room terminal 90 can display that it is being used.

The meeting information notification unit 37 notifies the prospective participants of the check-in via the notification robot (S65). Since the reservation ID can be identified by the conference identification information DB 494, the group may be identified from the reservation person account of the reservation information and notified.

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 it receives a check-out signal.

Upon receiving the check-out signal, the check-in management unit 38 performs check-out processing (S80). That is, the status of the conference management information DB 493 is set to checkout. As a result, processing related to this reservation information is no longer performed.

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

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

<Summary>
As described above, the facility reservation system 100 of the present embodiment can notify prospective participants of information regarding conference room reservations using a chat system without using e-mail. Since the prospective participants check the information regarding the reservation of the conference room, it is possible to reduce the number of vacant conference room reservations.

<Other application examples>
Although the best mode for carrying out the present invention has been described above using examples, the present invention is by no means limited to such examples, and various modifications can be made without departing from the scope of the present invention. and substitutions can be added.

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

Further, in the present embodiment, the conference management server 30 also identifies prospective participants by the account of the reservation management server 20, but if the account of the reservation management server 20 and the unique account of the conference management server 30 are associated, , the conference management server 30 may identify prospective participants with their own account.

The two-dimensional code may be a one-dimensional code such as a bar code. Also, the two-dimensional code and bar code are examples of the image code. Also, the terminal device 60 and the conference room terminal 90 may communicate by NFC, infrared communication, or the like.

An account may be any information other than an e-mail address as long as it can specify or identify prospective participants. For example, it may be a telephone number, IP address, MAC address, arbitrary ID, or the like.

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.

In addition, the configuration examples shown in FIGS. 8 and 9 shown in the above embodiment are divided according to main functions in order to facilitate understanding of the processing of the equipment reservation system 100. FIG. However, the method of dividing each processing unit and the names thereof do not limit the present invention. The equipment reservation system 100 can also be divided into more processing units according to the content of processing. Also, one processing unit can be divided to include more processing.

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

<Control of electronic devices>
FIG. 33 and FIG. 34 are examples of diagrams explaining an outline of the control by the equipment reservation system 100 of the electronic equipment 70 arranged in the conference room. In this embodiment, an example of turning on the power of the electronic device 70 will be described. There is case 2 (FIG. 34). Regarding case 1, as explained in the first embodiment, whether or not check-in is permitted depends on the start time, so 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 to be set. Since the start time is used in case 2, the electronic device 70 placed in the conference room 6 is powered on by detecting the timing when the use of the electronic device 70 is started based on the reservation information.

<<Power ON at check-in>>
(1) As described in the first embodiment, prospective participants use the terminal device 60 to check in to the conference room terminal 90 .
(2) When the conference room terminal 90 obtains a check-in OK response from the conference management server 30, it requests the conference management server 30 for control information. The reason why the request is made from the conference room terminal 90 is that the conference room terminal 90 is in the company network. Alternatively, the communication load can be reduced by acquiring the control information together with the check-in OK response.

Note that there are a plurality of methods for how much information is included in the control information.

Method 1: Information on the electronic devices 70 installed in the conference room (connection destination information such as IP and address of each electronic device, authentication information, interface for ON/OFF (for example, ON/OFF command via network The API)) for outputting is set in the conference room terminal 90, and only the power ON/OFF time, whether or not the video conference system is used, and the connection destination information of the video conference system (connection destination ID, etc.) Send as control information. With 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 An interface (API) for turning ON and OFF), whether or not a video conference system is used, 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, setting for each conference room terminal 90 is performed. less.
(3) The conference room terminal 90 controls the electronic device 70 by transmitting the acquired control information to the electronic device 70 . If the control information indicates that the power is ON, the electronic device 70 is activated, so that the prospective participant can use the electronic device 70 immediately after checking in. Since the electronic device 70 does not start until the power is turned on by the conference management server 30, it is possible to suppress the use of the electronic device 70 by persons other than prospective participants who do not have the right to check in to the conference room. Therefore, the equipment reservation system 100 can be managed without entrusting the use of the electronic equipment 70 to prospective participants.

<<Turn on the power before the specified time before the start time>>
(1) As described in the first embodiment, when the prospective participant responds to the information regarding the reservation of the conference room with "use", use confirmation is registered in the status of the conference management information DB 493. FIG.
(2) The conference room terminal 90 generates control information for powering on the electronic device 70 at a predetermined time (for example, 5 to 10 minutes) before the start time.
(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, the control information can be obtained by inquiring after the control information is generated. Control information may be generated for the query.
(4) The conference room terminal 90 controls the electronic device 70 by transmitting the acquired control information to the electronic device 70 . If the control information indicates that the power 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. can. Since the electronic device 70 does not start until the power is turned on by the conference management server 30, it is possible to suppress the use of the electronic device 70 by persons other than prospective participants who do not have the right to check in to the conference room. Therefore, the equipment reservation system 100 can be managed without entrusting the use of the electronic equipment 70 to prospective participants.

<Terms>
The fact that the facility terminal has communicated with the terminal device of the user of the facility means that the user has arrived at the facility or has indicated the intention to use the facility. In this embodiment, the term "check-in" will be used.

Termination of the use of the facility means that the user has indicated his/her intention to leave the facility. In this embodiment, the term "checkout" will be used.

<About system configuration, etc.>
The system configuration, hardware configuration, and functional blocks of this embodiment are the same as those of the first embodiment, or even if they are different, it will not hinder the explanation of this embodiment. In this specification, the components denoted by the same reference numerals perform the same functions, so the description of the components that have already been described may be omitted or only the differences may be described.

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

S1: As described in the first embodiment, the conference management server 30 sends a check-in result (check-in permitted or not). In FIG. 35, control information is transmitted together with check-in enabled. Since the conference management server 30 communicates through the firewall, this processing is performed as a response to a check-in request received.

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

S1.2: The electronic device communication section 95 of the conference room terminal 90 obtains from the electronic device 70 a passcode necessary for using the electronic device 70 . The passcode serves as authentication information for the terminal device 60 to transmit video to the electronic device 70 . Since a passcode is generated each time the system is activated, it is possible to prevent, for example, prospective participants in another conference room from transmitting video wirelessly.

S1.3: The terminal device communication unit 92 of the conference room terminal 90 notifies the terminal device 60 of the passcode. Various methods of notification are possible. For example, it may be transmitted by Bluetooth Low Energy (registered trademark), 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 the video with prospective participants.

In this manner, the prospective participant can turn on the electronic device 70 by checking in to the conference room, and the terminal device 60 can transmit video to the electronic device 70 .

If the electronic device 70 is already powered on, the electronic device 70 remains powered on.

FIG. 36 is an example of a sequence diagram showing a procedure in which the conference management server 30 turns on the power of the electronic device 70 a predetermined time before the start time.

S1: The server communication unit 91 of the conference room terminal 90 acquires the presence or absence of control information from the conference management server 30 together with the conference room ID. Since communication from the external network to the internal network is difficult due to the firewall, the server communication section 91 of the conference room terminal 90 polls the conference management server 30 (regularly inquires). Communication technologies such as WebSockets may also 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 obtained, this step can be omitted. That is, it is not necessary to acquire the reservation information at the polling timing of the conference room terminal 90 . The control information generator 35 of the conference management server 30 determines whether or not to generate control information, and generates control information if necessary. That is, it is determined whether or not it is a predetermined time before the start time. If the reservation information is acquired in advance, the control information is generated in advance without generating the control information at polling timing. Although the conference identification information is not taken into consideration, the conference identification information is taken into consideration at the time of check-in, and if the check-in is not made, the power of the electronic device 70 is turned off, so there is little trouble.

S1.1.1: The conference management server 30 transmits to the conference room terminal 90 the presence or absence of control information and, if there is control information, the control information. 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 equipment 70 of the other site is set in the reservation information, the connection ID is transmitted together with the reservation information, so that the connection ID is transmitted to the electronic equipment 70 after the check-in of the participant. Using the connection ID, the electronic device 70 can automatically connect to the electronic device 70 at the other site and start a remote conference. Therefore, it may not be necessary to transmit the connection ID at the check-in of the participant described in FIG.

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

S5: However, if the prospective participant does not check in, the electronic device 70 will remain powered on. Therefore, if the electronic device communication unit 95 of the conference room terminal 90 does not receive a check-in permission from the conference management server 30 within a predetermined time after the power is turned on, the electronic device 70 is powered off. By doing so, power consumption can be reduced.

<Power OFF control>
FIG. 37 is an example of a sequence diagram showing a procedure for the conference room terminal 90 to turn off the power of the electronic device 70 after checkout.

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

S1.1: The electronic device communication unit 95 of the conference room terminal 90 transmits power OFF control information to the electronic device 70 . By doing so, the power consumption of the electronic device 70 can be reduced even if the prospective participants do not turn off the power. The conference room terminal 90 that has received the check-out notification may again request the conference management server 30 for the control information. Note that the check-out notification may serve as power-off control information, but by sending the check-out notification and the control information separately, if the next meeting starts immediately, turning off the power during check-out can be omitted. can. Details will be described later.

<Processing of conference management server and conference room terminal when powering on electronic device 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 controlling the power supply of the electronic device 70 to be ON in conjunction with check-in.

FIG. 38(a) is an example of a flowchart showing a procedure for the conference management server 30 to transmit control information in conjunction with check-in.

First, the check-in manager 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 check-in permission and control information need not be transmitted at the same time. Also, check-in permission may serve as control information.

If the electronic equipment installed in the conference room includes a teleconference terminal, the control information may include the connection destination ID of the teleconference terminal. Specifically, as shown in FIG. 10, when the reservation management server 20 accepts the reservation of the conference room, it also accepts the input of the connection destination ID at the same time. It is included in the control information and transmitted.

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

If the determination in step S30 is Yes, the check-in manager 38 sends a check-out notification to the conference room terminal 90 (S40).

Next, the control information generation unit 35 determines whether or not the start time of the next conference arrives before a predetermined period of time has elapsed (S50). As a result, it is possible to prevent the power from being turned off in a short period of time and then turned on again.

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

If the determination in step S50 is Yes, the control information generator 35 does not generate power OFF control information.

FIG. 38(b) is an example of a flow chart showing a procedure for the meeting room terminal 90 to turn on the power of the electronic device 70 in conjunction with check-in.

First, the server communication unit 91 of the conference room terminal 90 acquires check-in permission (S10). Only check-in may be permitted, or control information may be received. No polling is required as we get these as a response to the check-in request.

When the check-in is permitted or the control information is received, the electronic device communication section 95 of the conference room terminal 90 turns on the power of the electronic device 70 (S20).

If the control information includes the connection destination ID of the teleconference terminal, a connection request may be made to the connection destination ID after the power-on command is issued. In addition, in order to control this power ON, connection destination information such as an IP address indicating a specific interface and the electronic device 70 is used to perform control via a network.

FIG. 38(c) is an example of a flowchart showing a procedure for the conference room terminal 90 to turn off the power of the electronic device 70 in conjunction with checkout.

First, the server communication unit 91 of the conference room terminal 90 acquires a checkout notification (S10). No polling is required as you get checkout notifications in response to checkout requests.

Next, the server communication unit 91 of the conference room terminal 90 acquires control information (S20). If the start time of the next conference arrives before the predetermined time elapses, control information is not transmitted. Polling is not necessary because the control information is acquired as a response to the checkout request.

Upon receiving the control information, the electronic device communication unit 95 of the conference room terminal 90 turns off the electronic device 70 (S30).

As in the case of turning on the power, in order to turn off the power, control is performed via a network using connection destination 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 powering on electronic device at predetermined time before start time>
FIG. 39 is an example of a flowchart showing a procedure for the conference management server 30 to transmit control information a predetermined time before the start time.

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

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

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

After that, the control information response unit 36 of the conference management server 30 determines whether or not 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 to respond to the inquiry when control information associated with the conference room ID exists in the control information DB 497. .

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

After that, the control information generator 35 of the conference management server 30 determines whether or not the conference room terminal 90 is permitted to check in (S60). In other words, if the prospective participants do not check in, the power will remain ON. If check-in is not permitted within a predetermined time (for example, 10 minutes) after the start time has elapsed, the control information generator 35 of the conference management server 30 transmits control information for turning off the power. This predetermined time may be equivalent to the time at which the reservation is automatically canceled if the prospective participant does not check in.

If the determination in step S60 is No, the conference information generator 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 generator 35 of the conference management server 30 determines whether checkout has been received (S70).

Then, when the checkout is received, the control information generator 35 determines whether or not the start time of the next conference arrives before the predetermined time has passed (S80). As a result, it is possible to prevent the power from being turned off in a short period of time and then turned on again.

If the determination in step S80 is No, the control information generating unit 35 generates power OFF control information, and the control information responding unit 36 transmits the power OFF control information to the conference room terminal 90 (S90).

FIG. 40 is an example of a flowchart showing a procedure for the conference room terminal 90 to turn on the power of the electronic device 70 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 or not the control information has been received (S20). If not, the processing of FIG. 40 is reduced.

When the control information is received (Yes in S20), the electronic device communication section 95 turns on the power of the electronic device 70 (S30).

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

When the server communication unit 91 of the conference room terminal 90 has obtained check-in permission (Yes in S40), the electronic device communication unit 95 determines whether or not a check-out notification has been obtained from the conference management server 30 (S70). If the check-out notification is not received (No in S70), the conference room terminal 90 waits.

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

If the server communication unit 91 of the conference room terminal 90 does not acquire check-in permission (No in S40), the electronic device communication unit 95 determines whether a predetermined time has passed 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 section 95 turns off the electronic device 70 (S60).
<Summary>
With the above processing, the equipment reservation system 100 can turn on and off the power of the electronic equipment 70 and manage the use of the electronic equipment 70 in the conference room. Prospective participants can use the electronic device 70 immediately after check-in. Since the electronic device 70 does not start until the power is turned on by the conference management server 30, it is possible to suppress the use of the electronic device 70 by persons other than prospective participants who do not have the right to check in to the conference room. In addition, since the power is automatically turned off upon checkout, power consumption can be reduced.

<Other application examples>
Although the best mode for carrying out the present invention has been described above using examples, the present invention is by no means limited to such examples, and various modifications can be made without departing from the scope of the present invention. and substitutions can be added.

For example, control information for power ON and power OFF has been described, but the conference management server 30 may transmit control information for displaying various information on the electronic device 70, for example. For example, it is possible to display a message such as ``it will be the end time in 10 minutes left'', ``countdown to the end time of the meeting'', and the like. The name of the conference, names of prospective participants (accounts), etc. may be displayed.

In the second embodiment, the power of the electronic device 70 is controlled to be turned off in conjunction with checkout. may be controlled. In this case, the power is turned off even if the predetermined time does not elapse before the start of the next conference. This makes it easier to prevent the end time from passing.

Note that the control information generation unit 35 is an example of control information generation means, the control information response unit 36 is an example of control information transmission means, the check-in management unit 38 is an example of facility management means, and controls power ON. The information is an example of first control information, and the control information for power OFF is an example of second control information. It is an example of the system, the server communication section 91 is an example of receiving means, the electronic device communication section 95 is an example of electronic device communication means, and the terminal device communication section 92 is an example of terminal communication means.

REFERENCE SIGNS LIST 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

JP 2016-045634 A

Claims (10)

A device control system comprising a reservation management device that manages reservations for a facility, an information processing device connected via a network, and a facility terminal arranged in the facility,
The information processing device is
Control information for generating first control information for the electronic device by detecting timing at which use of the electronic device arranged in the facility is started based on the reservation information for the facility acquired from the reservation management device. a generating means;
a control information transmitting means for transmitting the first control information to a facility terminal arranged in the facility;
The equipment terminal is
receiving means for receiving the first control information received from the information processing device;
The first control information received by the receiving means is transmitted to the electronic device, and after transmitting the first control information to the electronic device, the terminal device used by the user of the facility is connected to the electronic device. Electronic device communication means for acquiring a passcode for communication from the electronic device;
terminal communication means for transmitting the passcode to the terminal device;
A device control system comprising: The control information generating means generates the first control information at a predetermined time before the reservation start time of the equipment included in the reservation information,
2. The equipment control system according to claim 1, wherein said control information transmitting means transmits said first control information to said equipment terminal in response to an inquiry from said equipment terminal. The first control information controls the power supply of the electronic device to ON,
After transmitting the first control information to the equipment terminal, if the equipment terminal does not acquire communication with the terminal device of the user of the equipment within a predetermined time from the start time,
The control information generating means generates second control information for controlling the power supply of the electronic device to be OFF,
3. The equipment control system according to claim 2, wherein the control information transmitting means transmits the second control information to the equipment terminal. After transmitting the first control information to the equipment terminal, it is obtained within a predetermined time from the start time that the equipment terminal communicated with the terminal device of the user of the equipment,
When the end of use of the equipment is received from the equipment terminal, the control information generating means generates second control information for controlling the power supply of the electronic equipment to be turned off, and the control information transmitting means 4. The equipment control system according to claim 3, wherein said second control information is transmitted to said equipment terminal. After transmitting the first control information to the equipment terminal, it is obtained within a predetermined time from the start time that the equipment terminal communicated with the terminal device of the user of the equipment,
Even if the end of use of the equipment is received from the equipment terminal,
5. The equipment control system according to claim 4, wherein said control information generating means does not generate said second control information when said start time of the next conference arrives before a predetermined time elapses. The control information generating means generates the first control information when the equipment terminal acquires communication with a terminal device of a user of the equipment,
2. The equipment control system according to claim 1, wherein said control information transmitting means transmits said first control information to said equipment terminal. The fact that the facility terminal communicates with the terminal device of the user of the facility means that the user checks in to the facility,
The conference identification information held by the terminal device and input to the equipment terminal, which indicates that the user has the right to use the equipment during the reserved time period for the equipment, corresponds to the time period when the information processing device corresponds to the time period. having facility management means for permitting the use of the facility when it matches the conference identification information stored with the
The control information generating means generates the first control information in response to an inquiry from the equipment terminal when use of the equipment is permitted,
7. The equipment control system according to claim 6 , wherein said control information transmitting means transmits said first control information to said equipment terminal. The reservation information includes a start time for the reservation of the equipment,
When receiving from the equipment terminal the end of use of the equipment from the equipment terminal,
If the start time of the next meeting does not arrive before a predetermined time elapses, the control information generating means generates second control information for controlling the power supply of the electronic device to be turned off,
8. The equipment control system according to claim 7, wherein the control information transmitting means transmits the second control information to the equipment terminal. Based on the reservation information of the facility acquired from the reservation management device for managing the reservation of the facility, the timing of starting to use the electronic device arranged in the facility is detected, and the first control information of the electronic device is obtained. a control information generating means for generating
A facility terminal located in the facility, which communicates with an information processing device having control information transmission means for transmitting the first control information to the facility terminal located in the facility,
receiving means for receiving the first control information received from the information processing device;
The first control information received by the receiving means is transmitted to the electronic device, and after transmitting the first control information to the electronic device, the terminal device used by the user of the facility is connected to the electronic device. Electronic device communication means for acquiring a passcode for communication from the electronic device;
terminal communication means for transmitting the passcode to the terminal device;
A facility terminal characterized by having: Based on the reservation information of the facility acquired from the reservation management device for managing the reservation of the facility, the timing of starting to use the electronic device arranged in the facility is detected, and the first control information of the electronic device is obtained. a control information generating means for generating
Control information transmitting means for transmitting the first control information to the equipment terminal arranged in the equipment, and a control method performed by the equipment terminal arranged in the equipment, which communicates with an information processing device having,
receiving means for receiving the first control information received from the information processing device;
The first control information received by the receiving means is transmitted to the electronic device, and after transmitting the first control information to the electronic device, the electronic device communication means is a terminal used by the user of the equipment. obtaining a passcode from the electronic device for the device to communicate with the electronic device;
a terminal communication means transmitting the passcode to the terminal device;
A control method characterized by having

Images