JP7135667B2 - resource reservation system, notification method, conference management server - Google Patents

Description

The present invention relates to a resource reservation system, notification method, and conference management server .

A resource reservation system that manages reservation of resources such as conference rooms is known. A person who reserves a conference room can make a terminal device communicate with a reservation management server and reserve a conference room using a browser that operates on the terminal device. The reservation status of the conference registered in the reservation management server can be checked by each prospective participant of the conference by operating the terminal device and communicating with the reservation management server.

Such a resource reservation system allows the reserver to easily reserve resources, but on the other hand, if the conference is postponed or canceled, the reserver cancels or changes the reservation of the conference room registered in the reservation management server. sometimes neglect. Also, even if the conference is not postponed or canceled, prospective participants may forget that the conference is being held. The reservation of an unused conference room is called vacant reservation, and the vacant reservation not only deprives the person who wants to rent the conference room of the opportunity to use it, but also deprives the conference room provider of the opportunity to provide the conference room.

Therefore, there is known a technique of transmitting information related to resource reservation that a conference room has been reserved before the start time of the reserved conference (for example, see Patent Document 1). Sending information about resource reservation to call attention to resource reservation is called a reminder. Patent Literature 1 discloses a schedule reminder system that notifies, at a predetermined point in time, a message instructing the content of work required to execute a scheduled event.

However, in the conventional resource reservation system, there is a problem that the transmission method or destination of information on resource reservation is fixed. For example, when reminding using an SNS (Social Network Service) with a resource reservation system, the reminder could only be done through a predetermined SNS. In addition, it is difficult to set the destination of information on resource reservation, and the destination of information on resource reservation is limited to, for example, the person who made the reservation.

SUMMARY OF THE INVENTION An object of the present invention is to provide a resource reservation system capable of changing the transmission method or destination of information on resource reservation.

In view of the above problems, the present invention provides a resource reservation system in which a conference management server that manages resource reservation transmits a notification regarding resource reservation to terminal devices, and includes reservation information obtaining means for obtaining reservation information regarding resource reservation. a transmission method determining means for determining a transmission method of the notification regarding the reservation of the resource according to the reservation information acquired by the reservation information acquisition means , and further determining a destination with respect to the transmission method requiring a destination; transmission means for transmitting a notification regarding reservation of the resource using the transmission method determined by the transmission method determination means and, if the transmission method determination means determines a destination, to the destination in the transmission method; a keyword; a transmission method storage unit associated with the transmission method, wherein the transmission method determination unit transmits a notification regarding reservation of the resource by the transmission method associated with the keyword included in the reservation information. Then, it is characterized by determining .

It is possible to provide a resource reservation system capable of changing the transmission method or destination of information on resource reservation.

It is a figure explaining the outline of operation|movement of a facility reservation system. 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. 4 is an example of a hardware configuration diagram of a conference management server; FIG. 1 is an example of a hardware configuration diagram of a conference room terminal; FIG. It is an example of a functional block diagram showing functions of a reservation management server, a chat server, and a conference management server in block form. It is an example of a functional block diagram showing functions of a terminal device and a conference room terminal in block form. It is an example of the functional block diagram which shows the function of a meeting information notification part in block form. It is an example of a keyword setting screen for registering keywords and the like. It is a figure which shows an example of a destination setting screen. FIG. 12 is an example of a sequence diagram showing a procedure for an administrator to set keywords and the like on the screens of FIGS. 10 and 11; FIG. It is an example of a conference room reservation screen provided by the reservation management server and displayed on the terminal device. FIG. 10 is an example of a sequence diagram showing a procedure for a conference management server to remind a conference; It is an example of the flowchart figure explaining the detail of the procedure which a meeting information notification part reminds. FIG. 5 is a diagram showing an example of information related to reservation of a conference room displayed on the terminal device;

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

<Outline of operation of the equipment reservation system>
In the facility reservation system of this embodiment, when a preset keyword is included in the reservation information of the reserved conference room, the reminder is sent to the transmission method and destination set in association with the keyword.

FIG. 1 is a diagram for explaining the outline of the operation of the equipment reservation system 100 of this embodiment.
(1) A reservation person R reserves a conference room in the reservation management server 20 . Although the details will be described later, the name of the conference, prospective participants, etc. are set at the time of reservation.
(2) The conference management server 30 appropriately acquires reservation information from the reservation management server 20 and manages the timing of reminders based on the start time of the conference.
(3) The conference management server 30 has one or more chat servers 10 or destinations associated with keywords. When reminding, the conference management server 30 determines whether or not this keyword is included in the reservation information, and transmits the reminder to one or more of the chat servers 10 or destinations associated with the keyword.
(4) For example, if the reservation information contains the keyword "project X", the conference management server 30 determines the transmission method of the chat server 10A and transmits the reminder to the members belonging to the chat server 10A.
(5) For example, if the reservation information includes the keyword "sales department 2", the conference management server 30 determines the email transmission method and sends the email to "abc@sample.com" via the mail server 80. Send reminders to recipients.

In this way, the facility reservation system 100 of this embodiment can arbitrarily change at least one of the transmission method and the destination used for the reminder. You can also change only the destination using the same sending method. Conventionally, for example, a person who made a reservation could only remind himself/herself. For this reason, for example, when a general affair reserves a conference room, there is an inconvenience that a reminder is sent to the general affairs instead of the prospective participants.

<Terms>
A resource is a resource. A conference room and equipment, devices, people (receptionists), mechanisms, etc. that can be used in the conference room can be resources. Resources that are difficult to move are called facilities. In this embodiment, for convenience of explanation, the term conference room is used as an example of a resource.

Remind means reminding or making aware of some event. In this embodiment, the object is to remind the reservation of the conference room.

The notification regarding the reservation of the facility may be any information that can remind that the facility is reserved. For example, any information set in a reservation management server, which will be described later, can be notified.

The method of transmitting the notification regarding the reservation of the facility may be any method capable of notifying the information. It is not limited to email or chat systems.

A resource reservation system is a system that manages reservation of resources, and in this embodiment, the term facility management system will be used as an example.

<Pre-registration work>
Before describing the present embodiment, a pre-registration work for operating the equipment reservation system 100 capable of reducing vacant reservations will be described.

FIG. 2 is an example of a diagram for explaining the preliminary registration work for the facility reservation system 100 of this embodiment. The network N includes a chat server 10 (an example of an information notification device) that controls a chat system, a reservation management server 20 that manages reservations for facilities such as conference rooms, and a conference management server that manages conferences held in the conference rooms. A server 30 is communicatively connected as needed.

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. 2, 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 can notify prospective participants (Mr. A, Mr. B, Mr. C, and Mr. D) of information regarding the reservation of the conference room.

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. All prospective participants of the conference have an account of the reservation management server 20 in order to confirm the schedule of the conference. 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 conference participants (the prospective conference participants who have reserved the conference with the reservation management server 20). The outline of the pre-registration work will be described below.

(1) The administrator of the facility reservation system 100 operates the registration terminal 50 to communicate with the chat server 10 and obtains an account for a bot (a program that executes predetermined processes). The bot speaks to the group as a proxy of the conference management server 30 registered in the chat system. Although registered in group 1 in FIG. 2, the group in which the bot account 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 (in the chat system Information specifying the notification destination of the message (for example, slack (registered trademark; abbreviated hereinafter) requires a channel name and team name) is associated and registered. Note that the association may be made by an administrator.

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. 3 is an example of a diagram for explaining a procedure for the conference management server 30 to notify prospective participants of information on reservation of a conference room. The mechanism for reminding is also similar to this.

(4) A prospective participant or a simple reservation person 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 reservation account that made the reservation.

(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 or arbitrarily communicates with the reservation management server 20 to acquire reservation information from the reservation management server 20 . Alternatively, the reservation information reserved by the account containing the domain specified by the conference management server 30 is automatically sent to the conference management server 30 .

(6) Here, for example, it is assumed that Mr. A's reservation information specified in the reservation person's account is found. Accordingly, the conference management server 30 can identify the bot associated with Mr. A. Here, it is assumed that group 1 associated with Mr. A is specified. Conventionally, the reservation person is specified in this way, but in the present embodiment, the chat server 10 or destination of the notification can be arbitrarily changed.

(7) The conference management server 30 communicates with the chat server 10, designates a bot and a group, and notifies the reservation person of the group 1 of the information regarding the reservation of the conference room.

(8) The chat system sends information regarding the reservation of the conference room to the reservation person. Thereby, the reservation person can be notified of the information regarding the reservation of the conference room. In this embodiment, not only the person who made the reservation, but also any prospective participant (or a person who does not participate but who is in a position to remind the prospective participant) can be notified of information regarding the reservation of the conference room. For convenience of explanation, the user to whom the reminder is notified is referred to as the notification destination user.

In this way, the equipment reservation system 100 of the present embodiment can use the chat system to notify the prospective participants of information regarding the reservation of the conference room. Statistics show that texts in chat systems are viewed more frequently 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.

<System configuration example>
FIG. 4 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. The internal network N1 is a network inside the firewall 73, and the external network N2 is a network such as 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 terminal device 60 operated by a prospective participant of the conference may be connected to the external network N2 as necessary.

The reservation management server 20 is 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 reservation management server 20 transmits reservation information of an account (domain) registered in advance to the conference management server 30 . Alternatively, the conference management server 30 can acquire the reservation information of the conference room 6 from the reservation management server 20 by designating the account of the reservation management server 20 and requesting the reservation information from the conference management server 30 . Note that the account may be any information that can uniquely identify the user, such as e-mail, ID, and telephone number.

Although the reservation of the conference room 6 is managed as a schedule in this embodiment, the reservation management server 20 can manage not only the conference room 6 but also various other schedules. In addition to meeting room 6, various facilities such as rental of various electronic equipment, reservation of parking lot, rental office, rental studio, rental cycle, rental car, hotel and other accommodation facilities, event venue, locker rental space, etc. Available for reservation.

G Suite (registered trademark), Office 365 (registered trademark), etc. are known as reservation management systems, but any reservation management system 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 reservation management server according to the conference room name, conference room ID, reservable time, capacity of each conference room 6, reservation unit, etc. 20 web apps are customized. 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, voice, and video 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 6 . This embodiment may include a plurality of chat servers 10 operated by different entities.

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 6, it may output a voice message in addition to the text display. As chat systems, LINE (registered trademark; abbreviated hereinafter), slack, Microsoft Teams (registered trademark; abbreviated hereinafter), etc. are known. Any chat system may be used as long as it can notify one or more users from a program to be executed).

The chat server 10 similarly manages users with accounts (different from the accounts of the reservation management server 20), but in principle the conference management server 30 does not need to be aware of the chat server 10 accounts. However, the conference management server 30 can designate any account of the chat server 10 to notify.

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. The conference management server 30 acquires the reservation information of the conference room 6 from the reservation management server 20 as a process related to the external network N2, acquires the prospective participants set in the reservation information, and informs the prospective participants at the set timing. A notification is sent to the group of the chat server 10 associated with (or an individual person such as a reservation person). In addition, as processing related to the internal network N1, check-in and check-out to the conference room 6 are managed, and the power supply of the electronic device 70 is controlled based on the reservation information of the conference room 6 obtained from the reservation management server 20. do.

The company has a conference room 6, a prospective participant's current location 5, etc., and the prospective participant can access the external network N2 via the in-house network N1 from various locations. The in-house network N1 is, for example, a LAN (Local Area Network).

An access point 72 connected to the company network N1 is arranged in the conference room 6 . The conference room terminal 90 and the electronic device 70 are connected to the in-house network N1 via the access point 72 . The conference room terminal 90 and the electronic device 70 can communicate via the access point 72 as necessary. The conference room terminal 90 and the electronic device 70 may communicate by wire.

The access point 72 is a base station for wireless LAN communication between the conference room terminal 90 and the electronic device 70 . The access point 72 may have a router function, and the access point 72 determines whether the destination is the outside network N2 or the in-house 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 inside the firewall 73, direct communication from the external network N2 to the internal network N1 is difficult. Of course, you may communicate by wire.

The conference room terminal 90 is an information processing device (equipment terminal) operated by prospective participants who use the conference room 6 . 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 transmits the conference room ID to the conference management server 30 and displays the conference management information of the conference room 6 on the day. 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 .

Also, the conference room terminal 90 displays a standby screen 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. At the time of check-in, the conference room terminal 90 transmits the conference identification information input by the reservation person and the previously stored conference room ID to the conference management server 30. Therefore, the conference management server 30 uses the conference identification information and the conference room ID to It can be confirmed that the person who reserved the conference room 6 will use the reserved conference room 6 .

Electronic equipment 70 is various office equipment that can be used in conference room 6 . 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 an image displayed on the display by the terminal device 60 onto a screen or the like, the participants can share the image. Digital signage is a large display used to display any still or moving image. A digital camera is used by each participant to capture and save paper materials or materials displayed on an electronic blackboard.

There is an access point 71 at the current location 5 of the prospective participant, and the registration terminal 50 and the terminal device 60 are connected to the in-house network N1 via this access point 71 . The registration terminal 50 and the terminal device 60 may communicate by wire. Further, the registration terminal 50 does not need to be located at the current location 5 of the prospective participant as long as it can be connected to the conference management server.

The terminal device 60 can be implemented by one or more information processing devices (computer systems) on which a general OS or the like is installed. 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.

The registration terminal 50 may also be an information processing device similar to the terminal device 60 . However, since it is mainly used for setting by the administrator in the conference management server 30, the chat application and the conference application may be omitted. The registered terminal mainly communicates with the conference management server 30 using browser software.

<Hardware configuration>
<<Hardware configuration of the conference management server>>
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, an example of a display) 206 via a bus, and monitors 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 terminals>>
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 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 the participants of that 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 apparatus 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.

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

<<Reservation management server>>
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 one of the configuration categories shown in FIG. function or means to

The communication unit 21 transmits and receives various information to and from the conference management server 30 and the terminal device 60 . A reservation setting is received from the terminal device 60 . Also, it transmits reservation information 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 6 requested by the conference management server 30 from the reservation information DB 291 and transmits it to the conference management server 30 via the communication unit 21 . Alternatively, when the reservation information is registered (or changed), the reservation information is transmitted to the conference management server 30 even without a request. It is assumed that a general Web application is used as a method for a reservation person to reserve the conference room 6 in the reservation management server 20 . FIG. 13 shows an example of a screen that the Web application displays on the terminal device 60 of the person who made the reservation. 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 6 . In the reservation information, each item of a reserver account, a conference name (a title such as an agenda), 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 for identifying 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 reservation person account is an account of a prospective participant who has reserved the conference room 6 . The conference name is the name of the conference arbitrarily given by the prospective participants. The conference room ID is identification information for identifying the conference room 6 in the company network. The start time is the beginning of the reserved time slot in which the conference room 6 is reserved (the time when the conference starts), and the end time is the end of the reserved time slot in which the conference room 6 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 .

In addition to those shown in Table 1, the reservation person's name, conference room name, conference room reservation authority range, or reservation date may be registered. The reservation name is the name of the reservation person. The conference room name is the general name of the conference room. The conference room reservation authority range is the authority of the reserver required to reserve the conference room. For example, a conference room reserved exclusively for executives is assigned a predetermined reservation authority. The reservation date is the date on which the conference is held.

The reservation information, reservation person name, reservation person affiliation, conference room name, reservation authority range, reservation time zone, and reservation date shown in Table 1 are subject to keyword search.

<<chat server>>
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 realized by one of the configuration categories 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 the present embodiment, the information regarding the reservation of the conference room 6, the information identifying the bot, and the information identifying the group of the notification destination are received from the conference management server 30. FIG. If a specific notification destination is specified, the account of the subscriber or the notification destination user is received. Information for identifying this bot is previously notified from the chat server 10 to the conference management server 30 as bot identification information when a bot that speaks as the conference management server 30 is created. Information that identifies a bot is called a token and has an authentication function.

Further, the communication unit 11 notifies that the reservation person or the notification destination user has already read the information regarding the reservation of the conference room 6, or the response of the reservation person or the notification destination user to the displayed information regarding the reservation of the conference room 6. Send to the management server 30 . 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.

Based on the information identifying the bot notified from the conference management server 30 and the information identifying the group to which the notification is to be sent, the text processing unit 12 prepares the conference room 6 reservation information for prospective participants belonging to the group as information to be spoken by the bot. Send information about If the conference management server 30 further designates a notification destination account, the information regarding the reservation of the conference room 6 is transmitted to one of the prospective participants belonging to the group. Therefore, there are cases in which notifications are sent out for the number of prospective participants, and in other cases, notifications are sent only to arbitrary users such as those who have made reservations.

The text processing unit 12 can perform so-called push notifications. For example, the mechanism is as follows. The chat application 60a (to be described later) receives a push notification ID (token, which is different from a token for identifying a bot) 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, member accounts 1 to n (n=4 in Table 2) and bot accounts are registered in association with workspaces and channels. Since the group is specified at the time of notification, the bot account can be common to the group.

A workspace is identification information for identifying an organization such as a company or department. In this embodiment, multiple members belong to a workspace (for example, company A). A workspace is, for example, a URL, but it should be unique. Furthermore, the workspace has a plurality of channels according to the purpose of chat and the like. A channel is, for example, a group for product A, a group for product B, etc., and is a group of members exchanging common information. One of the members belonging to the workspace belongs to the channel. In other words, notification destinations are specified by workspaces and channels. 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.

Channels are guaranteed unique. Member accounts 1 to n are accounts of channel members, and these accounts are issued by the chat server 10 . In this embodiment, a bot is registered as a member for notifying information regarding the reservation of the conference room 6 . The bot can be said to be an agent or fictitious member of the conference management server 30, so to speak. The bot's statement (text) is transmitted to the terminal devices 60 of the member accounts 1 to n.

Workspaces and channels are managed by the conference management server 30 and serve as information for identifying groups to which participants belong.

<<Meeting Management Server>>
The conference management server 30 has a communication section 31 , a reservation information acquisition section 33 , a notification determination section 34 , a control information generation section 35 , a control information response section 36 , a conference information notification section 37 and a check-in management section 38 . Each of these function units of the conference management server 30 is realized by any one of the configuration categories 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 . The communication section 31 has a transmission section 31a and a reception section 31b. The receiving unit 31 b receives reservation information from the reservation management server 20 and receives a request for reservation information from the conference room terminal 90 . Also, the reception unit 31b receives a check-in request from the conference room terminal 90. FIG. Further, the receiving unit 31b receives correspondence between groups and accounts of the chat system from the registration terminal 50 operated by the administrator. The transmission unit 31 a transmits information regarding the reservation of the conference room to the chat server 10 and transmits the reservation information to 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 reservation information acquisition unit 33 designates an account of a customer who uses the equipment reservation system 100, acquires reservation information from the reservation management server 20, and registers it in the conference management information DB 493 as conference management information. Alternatively, it receives changed reservation information. Therefore, at least part of the reservation information of the reservation management server 20 is stored in the conference management information DB 493 . The reservation information acquisition unit 33 acquires reservation information for a predetermined period from the present to the future from among the reservation information held by the reservation management server 20 . The predetermined period is determined by how far ahead the conference the information regarding the reservation of the conference room 6 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 of a start time that satisfies the conditions for notification in the conference management 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. For example, when bots are classified according to their roles, such as a bot for reminders and a bot for reservation reception, the bots are specified according to the processing. 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 to notify, the meeting information notification unit 37 designates information identifying the bot (for example, a token in slack) and information identifying the group of the notification destination, and notifies information regarding the reservation of the conference room 6. request the chat server 10 to Notification may be made for the number of prospective participants, or may be made only for the reserving person or the notified user.

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 reserved person has the right to use the reserved conference room 6 during the reserved time period. 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 . At least one of the notifications made by the meeting information notification unit 37 corresponds to a reminder. The function of the meeting information notification unit 37 regarding reminder will be described in detail later. The meeting information notification unit 37 is implemented by the CPU 201 in FIG. 5 executing the program 209p.

The control information generator 35 refers to the conference management information to generate control information for the electronic device 70 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 from the conference room terminal 90 of the conference room 6 as to whether or not there is control information, refers to the control information DB 497, and transmits control information corresponding to the conference room 6 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 manages check-in/check-out to/from the conference room. In addition, the status of the conference mainly associated with check-in/check-out is registered in the conference management information DB 493 . Check-in is permitted 5-10 minutes prior to the start time of the meeting identified in the booking ID. Then, check-in is permitted when the combination of the conference room ID and the conference identification information transmitted by the conference room terminal 90 is registered in the conference identification information DB 494 . 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 transmission method 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 transmission method information stored in the transmission method information DB 491 . The destination information is information in which a keyword and a transmission method are associated with each account of the facility reservation system. Specifically, it is information that associates a reminder method to oneself, a keyword, an e-mail address, a chat server account, and a chat server group information (workspace and channel). Information registered in Table 3 is set in FIGS. 10 and 11, which will be described later. Although Table 3 shows the sending method for only one user, the user to be reminded has similar information.

The user is assumed to be a person who uses the facility reservation system and who makes reservations. A user is represented by an account in the facility reservation system. The keyword is Japanese, English, numbers, symbols, etc., or a combination thereof, which triggers the reminder to this user. It is sufficient if it can be represented by a code that can be input from a keyboard or the like. The e-mail address may be a general e-mail address. The chat server 10 account is the chat system account. The group information of the chat server is information that identifies the group in the chat system.

If a keyword is included in the reservation information, an e-mail or chat system is identified and the destination specified by each transmission method is reminded. Alternatively, in the chat system, the reminder may be given to the group specified by the group information of the chat server. In this case, all members of the group can be reminded.

In this manner, the transmission method information DB 491 associates the account of the reservation management server 20 with the account of the chat server 10 . A chat system may be designated as a reminder method to oneself.

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

Table 4 shows an example of conference management 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 conference management information in Table 4 has an item of status. Status means the status of reservation. For example, the status of information regarding the reservation of the conference room 6 has been notified, usage confirmation, check-in completed, 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 reservation of the conference room 6 . The conference identification information management information has items of reservation ID, conference room ID, and conference identification information. Except for the status, these are the same as the reservation information (reservation information received from the reservation management server 20), and since they have already been described, the description is omitted. The reason why the reservation ID is registered is to identify reservations for the same conference room 6 . 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 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 6 . 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 6 . 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>>
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 registration terminal 50 is a terminal used by a conference room reservation person or an administrator of the equipment reservation system 100 . In this embodiment, it is assumed that the reservation person uses this to set the keyword, transmission method, and destination. A terminal device 60 may be used. The functions of the communication unit 51, the operation reception unit 52, and the display control unit 53 of the registration terminal 50 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>>
FIG. 8 is an example of a functional block diagram showing functions of the terminal device 60 and the conference room terminal 90 in block form. Note that functions of the electronic device 70 will be described as necessary.

The terminal device 60 includes a communication unit 61a, an operation reception unit 61b, a display control unit 61c, a chat communication unit 62, a text display unit 63, an application communication unit 64, a server communication unit 65, a display control unit 66, an application communication unit 67, and , and a terminal communication unit 68 . 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 performed by the participant on the terminal device 60 . The operation reception unit 61b is implemented by the CPU 201 in FIG. 5 executing the program 209p and controlling the input device 210, for example.

The display control unit 61c interprets screen information written in HTML, CSS (Cascade Style Sheet), JavaScript (registered trademark), etc., and displays various screens on the LCD 206. FIG. A program written in JavaScript (registered trademark) is sometimes called a Web application.

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 bot and the text is displayed as if the bot 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 terminals>>
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 configuration categories 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 unit 91 of this embodiment periodically receives the reservation information if there is any change in the reservation information. Also, at the time of check-in, the terminal device communication unit 92 transmits the conference identification information received from the terminal device 60 or the manually input conference identification information to the conference management server 30 . Also, the server communication unit 91 receives control information from the conference management server 30 .

The timing for receiving the reservation information periodically is every several seconds to several minutes. The shorter the cycle, the earlier the reservation information can be updated, but the higher the communication load. The server communication unit 91 can receive at least the conference management information (reservation information) of the conference room 6 on the day. 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 . This screen is a standby screen or the like that enables check-in and check-out. 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, the IP address of the electronic device 70, and the like.

<About the functions of the meeting information notification section>
FIG. 9 is an example of a functional block diagram showing functions of the meeting information notification unit 37 in a block form. The meeting information notification unit 37 has a keyword setting reception unit 41 , a keyword matching confirmation unit 42 , a transmission method determination unit 43 , a destination determination unit 44 and a reminder transmission unit 45 .

The keyword setting reception unit 41 generates screen information for screens as shown in FIGS. 10 and 11, causes the terminal device to execute a web application based on this screen information, and receives operations related to keyword setting by the reservation person. Since the reservation person sets the keyword and the transmission method (in the case of a chat system, the destination does not have to be set), the keyword setting reception unit 41 stores the transmission method and the destination in the transmission method information DB 491 in association with the keyword. sign up.

The keyword match confirmation unit 42 detects conference management information including the keyword stored in the transmission method information DB 491 from the conference management information DB 493 . That is, the conference management information is searched by keyword. Reservation information is searched among conference management information, so it can be said that reservation information is searched. The information described in Table 1 or the name of the reservation person, the affiliation of the reservation person, the name of the conference room, the reservation authority range, the reservation time zone, and the reservation date that may be included in Table 1 are subject to keyword detection. If the reservation person's name can be retrieved, it is possible to control the transmission method or destination of the reservation information reserved by any reservation person. If the affiliation of the reservation person can be retrieved, it is possible to control the transmission method or destination of the reservation information reserved by the reservation person of the same affiliation (development team or sales department). If the conference room name can be retrieved, it is possible to control the transmission method or destination of reservation information for a conference held in a certain conference room. If the reservation authority range can be retrieved, it is possible to control the transmission method or destination of the reservation information reserved by a reservation person with a certain authority (eg, a secretary). If the reserved time period can be retrieved, it is possible to control the transmission method or destination of the reservation information of a meeting (a fixed meeting such as a regular meeting) in a certain time period. If the reservation date can be retrieved, it is possible to control the transmission method or destination of the reservation information of the meeting (fixed meeting such as regular meeting) on the specified date.

Furthermore, the affiliation of the reservation person may be a keyword detection target. A reservation person's affiliation refers to a department, title, occupation, etc., and is registered in a publicly known user information DB in which information about users is registered. Since the reservation person is specified by the reservation person account, the user information DB can be searched by the reservation person account, and the affiliation of the reservation person can be obtained.

When meeting management information including a keyword is found, the transmission method determination unit 43 acquires the transmission method associated with this keyword from the transmission method information DB 491 . Determining the transmission method may also include determining individual destinations.

When meeting management information containing a keyword is found, the destination determination unit 44 acquires the destination associated with the keyword (account of the user to be notified, e-mail address, or the like) from the transmission method information DB 491 .

The reminder transmission unit 45 transmits the reminder to the destination associated with the keyword by the transmission method associated with the keyword.

<Example of keyword registration>
FIG. 10 shows an example of a keyword setting screen 501 for registering keywords and the like. The keyword setting screen 501 is mainly used by the reservation person to set keywords. An administrator of the equipment reservation system 100 may set it. There are the following two modes when the reservation person sets.
(i) setting preferences for bookers to remind themselves;
(ii) Make settings for the reservation person to remind other prospective participants
As the mode (i), the reservation person sets the transmission method and the address to be notified when the reservation person reminds himself/herself. As a mode of (ii), when the general affairs or the secretary reserves the conference room and reminds the prospective participants, which transmission method and address should be used to notify the prospective participants, etc. are set.

The reservation person operates the registration terminal 50 to log in to the conference management server 30, and acquires screen information described in HTML, CSS (Cascade Style Sheet), JavaScript (registered trademark), etc. from the keyword setting reception unit 41. to display. A keyword setting screen 501 is one screen of a web application provided by the keyword setting reception unit 41 . In the explanation of FIG. 10, the reservation person operates the registration terminal 50 in order to explain the operation related to setting, but the terminal device 60 may also be operated.

The keyword setting screen 501 has a tab column 502 , a user account column 503 , a default setting column 504 and an option setting column 505 .

The tab field 502 has tabs for reminder notification destination setting 502a and user setting 502b. The keyword setting screen 501 of FIG. 10 is displayed when the tab of reminder notification destination setting 502a is selected. Reminder notification destination setting 502a is a tab for the subscriber to set a reminder transmission method. The user setting 502b is a tab for the reservation person to make user settings regarding the chat system.

A user account column 503 is a column in which the account of a person who has made a reservation logged in to the conference management server 30 is displayed. This account is an account issued by the facility reservation system (reservation management server 20).

A default setting column 504 displays a transmission method for notifying the reservation person. That is, the default setting column 504 is a column for setting the reminder transmission method when the reservation person reminds himself/herself. In FIG. 10, a mail address column 504a is displayed to show a state in which "Mail" 504c is selected in the transmission method list. In the e-mail address column 504a, any convenient e-mail address can be set for the reservation person to remind himself/herself.

A chat system 504b displayed in the default setting field 504 is a chat system that can cooperate with the conference management server 30 and is set in advance. Bookers can choose which chat system to use for reminders. When the chat system is selected, a user interface for specifying the user in the chat system is displayed in default setting field 504 . An example of this user interface is the same as in FIG.

The option setting field 505 displays a number 505a, a keyword 505b, a notification destination setting field 505c, an edit button 505d, a delete button 505e, and an add button 505f. An option setting field 505 is a field for setting a transmission method when a reservation person transmits a reminder to a person other than himself/herself. Therefore, the option setting column 505 may be left blank. In this embodiment, the option setting field 505 enables the reservation person to remind participants other than the reservation person.

The setting of the option setting column 505 is performed on the destination setting screen 511 of FIG. The edit button 505d is a button for the subscriber to edit the notification destination setting field 505c once set, the delete button 505e is a button for deleting the keyword and transmission method settings, and the add button 505f is a new button. This is a button for the administrator to add keywords and transmission methods to the

FIG. 11 shows an example of the destination setting screen 511. As shown in FIG. The destination setting screen 511 is displayed when the edit button 505d or the add button 505f is pressed in FIG. The destination setting screen 511 is a screen for the reservation person to set a keyword and a transmission method. The destination setting screen 511 has a transmission method selection tag 512 . When the administrator selects the chat system 512a or mail (Mail) 512b with the transmission method selection tag 512, a user interface corresponding to the chat system or mail is displayed. That is, the input fields necessary for setting the destination in the selected chat system are displayed. When the mail 512b is selected, a mail address column 504a is displayed as shown in FIG.

In FIG. 11, since the chat system slack is selected, a team name 513 (corresponding to workspace), an account 514, and a channel 515 can be selected. A group is specified by a team name 513 (corresponding to a workspace) and a channel 515, and a destination can be specified by an account 514. FIG. Therefore, when the reservation person selects the chat system, the destination can also be specified. The account 514 may not be set, in which case the conference management server 30 can notify all members of the group.

Further, the destination setting screen 511 has a keyword column 516 and a match judgment setting column 517 . The keyword described above is entered in the keyword column 516 . In the match determination setting column 517, determination methods such as partial match, complete match, prefix match, and suffix match are set.

When the reservation person presses the save button 518 after setting these, the keyword setting screen 501 in FIG. 10 is returned to, and the contents set in FIG. In FIG. 10, the e-mail address of the reminder transmission destination is displayed in the notification destination setting field 505c. Although the email address is displayed in FIG. 10, depending on the chat system, information for specifying the user in the chat system, such as workspace, channel, and account of the chat system, is displayed.

The keyword and transmission method set by the reservation person on the screens of FIGS.

<Keyword setting procedure>
FIG. 12 is an example of a sequence diagram showing a procedure for an administrator to set keywords and the like on the screens of FIGS. 10 and 11. In FIG. The reservation person operates the registration terminal 50 to communicate with the conference management server 30 and executes the Web application on the registration terminal 50 .

S1: The reservation person inputs a keyword into the keyword field 516 of the destination setting screen 511 shown in FIG. The operation reception unit 52 of the registration terminal 50 receives input from the reservation person.

S2: The reservation person selects the transmission method selection tag 512 on the destination setting screen 511 shown in FIG. 11, and sets the transmission method used for the reminder. The operation reception unit 52 of the registration terminal 50 receives selection of the transmission method.

S3: The administrator sets the destination on the destination setting screen 511 shown in FIG. That is, in the case of slack, the team name 513, account 514, and channel 515 are set. When the mail 512b is selected in the transmission method selection tag 512, enter the mail address. The operation reception unit 52 of the registration terminal 50 receives input from the administrator.

S4: The communication unit 51 of the registration terminal 50 transmits the keyword and transmission method set by the administrator to the conference management server 30 .

S5: The communication section 31 of the conference management server 30 receives these setting information, and the information correspondence section 32 registers (updates) them in the transmission method information DB 491 .

In this manner, keywords, transmission methods, and destinations are registered in the conference management server 30 for each user of the equipment reservation system 100 .

<Reservation of meeting room>
Reservation of a conference room will be described with reference to FIG. FIG. 13 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 . For the participation schedule, log in to the reservation management server 20 with the account of the reservation management server 20 and input necessary items on the reservation screen 401 . Since the conference room input field 405 displays selectable conference room names and communication IDs in a pulldown, the user can select a conference room by selecting the conference room name. The communication ID displayed in the conference room input field 405 is an ID for specifying a partner when the electronic device 70 in the conference room 6 communicates with the electronic device 70 at another site. As a result, the electronic device 70 can automatically start communication with the electronic device 70 at another site.

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.

The conference room reservation screen 401 is merely an example, and the design is changed according to the screen provided by the reservation management server 20 . When the reservation person inputs the necessary items from the reservation screen 401 , the reservation information shown in Table 1 is registered in the reservation management server 20 .

<Reminder sending process>
FIG. 14 is an example of a sequence diagram showing a procedure for the conference management server 30 to remind the conference.

S11: When the communication unit 21 of the reservation management server 20 receives the registration (including change) of the reservation information, it transmits a reservation notification indicating that the reservation has been made to the conference management server 30 .

S12: The communication section 31 of the conference management server 30 receives the reservation notification, and the reservation information acquisition section 33 acquires the reservation information from the reservation management server 20. FIG. For example, the notified reservation information may be acquired, or a domain may be designated and acquired.

S13: When the reservation information acquisition unit 33 acquires the reservation information, the keyword match confirmation unit 42 of the meeting information notification unit 37 searches for the reservation information using the keyword set in the transmission method information DB 491 . The search destination of the keyword may be any part of the reservation information, but for example, the conference name is searched. Details of the search will be described with reference to FIG. A case where reservation information containing a keyword is found will be described below.

S14: The transmission method determination unit 43 acquires the transmission method associated with the keyword from the transmission method information DB 491. FIG. For example, a chat system is identified.

S15: Next, the destination determination unit 44 acquires the destination associated with the keyword from the transmission method information DB 491. FIG. For example, an e-mail address is specified. Note that the determination of the transmission method and the determination of the destination may be performed in parallel.

S16: The reminder transmitter 45 sets a timer for reminder transmission. In other words, since the timing before the start of the meeting is set by the notification setting DB 496, a timer (the date and time to send the reminder) is set for each user so that the reminder can be made at the timing set in the notification setting DB 496. do.

S17: The reminder transmission unit 45 notifies the notification destination user of the reminder at the set date and time.

FIG. 15 is an example of a flow chart for explaining the details of the procedure of the reminder by the meeting information notifier 37. As shown in FIG.

First, as described with reference to FIGS. 10 and 11, the transmission method and destination to be used for reminder transmission are set (S100).

The keyword matching confirmation unit 42 confirms the reservation person account included in the reservation information, acquires the transmission method associated with this reservation person account from the transmission method information DB 491, and checks whether or not the keyword is set. It judges (S101).

If no keyword is set (No in S101), the meeting information notification unit 37 transmits a reminder using the transmission method and destination set in the default setting field 504 of the keyword setting screen 501 (S102). Therefore, the destination is the person who reserved the conference.

If a keyword is set (Yes in S101), the keyword matching confirmation unit 42 determines whether or not the keyword is included in the reservation information (S103).

If a keyword is included in the reservation information (Yes in S103), the destination determination unit 44 determines the transmission method and destination from the transmission method information DB 491 based on the keyword (S104).

Next, the transmission method determination unit 43 determines the transmission method and destination associated with the keyword (S105).

When the transmission method is slack, the transmission method determination unit 43 determines slack as the transmission method (S106). Determination of the transmission method also determines the destination.

When the transmission method is Microsoft Teams, the transmission method determination unit 43 determines the transmission method to be Microsoft Teams (S107). Determination of the transmission method also determines the destination.

When the transmission method is Mail (e-mail), the transmission method determination unit 43 determines the transmission method to be e-mail (S108). When the transmission method is determined to be e-mail, the destination is also determined. Note that LINE is omitted in FIG.

If there is no reservation information including a keyword (No in S103), the meeting information notifier 37 transmits a reminder using the transmission method and destination set in the default setting field 504 of the keyword setting screen 501 (S109). Therefore, the destination is the person who reserved the conference room.

Explain how the chat system sends reminders. The conference management server 30 transmits the reminder to the terminal device 60 via the chat server 10 . Here, for example, it is assumed that slack is selected.
a. The meeting information notifier 37 identifies the account of the person who made the reservation based on the reservation information.
b. Identify the transmission method associated with this subscriber's account in the transmission method information DB 491 . Thereby, the account, workspace and channel of the destination (other than the person who made the reservation) in the chat server 10 can be specified.
c. The meeting information notification unit 37 sends a message to the chat server 10 by designating pre-assigned bot identification information (for example, a token), the account of the destination (other than the person who made the reservation), workspace and channel in the chat server. do.
d. The text processing unit 12 of the chat server 10 notifies the destination (other than the subscriber) account of the group specified by the workspace and channel in the form of the bot specified by the token speaking.

<Example of reminder>
FIG. 16 shows an example of information about conference room reservations displayed on the terminal device 60 . FIG. 16( a ) is an example of information relating to conference room reservation notified at the timing of the notification setting DB 496 . Such a message may be sent, for example, the day before, several hours, or half an hour before the start time of the meeting.

In FIG. 16(a), it is displayed as follows.
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 person making the reservation or the user to whom the notification is to be notified can take an appropriate action 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 to be used and the cancel button 452 are pressed by designating the bot that is the speaker, and the chat server 10 is notified of this. When the chat server 10 sends a response to the bot, the bot corresponds to the conference management server 30, so the conference management server 30 can receive the reply of the person who made the reservation or the user to whom the notification is made. The meeting information notifying unit 37 transmits again the confirmation 453 via the chat server 10 to the chat application 60 a of the terminal device 60 . Similarly, when the prospective participant presses the cancel button 452, a message 454 to the effect that the event has been canceled is displayed.

FIG. 16(b) shows information relating 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. When the use is confirmed, the conference identification information "NNN...N" is included in the message at a predetermined timing. The prospective participant inputs this conference identification information to the conference room terminal 90 (the terminal device 60 may transmit it).

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. 16B is the URL of the conference application. When this URL is tapped, the conference application starts. Since "NNN...N", which is the conference identification information, is specified by the parameter, the terminal device 60 starts the conference application and notifies the conference identification information to the conference application 60b. As a result, the conference application 60b can communicate with the conference management server 30 using the previously held IP address of the conference management server 30 and request the two-dimensional code including the conference identification information. The check-in management unit 38 of the conference management server 30 generates a two-dimensional code in which “NNN . The terminal device 60 can hold a two-dimensional code. With this two-dimensional code, the reservation person or the notified user can check in without inputting the conference identification information.

<Summary>
As described above, the facility reservation system 100 of this embodiment can arbitrarily change at least one of the chat server 10 and the destination used for reminders. Any destination can be selected even when the chat server is selected.

<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, a plurality of conference management servers 30 may exist, and functions of the conference management server 30 may be distributed among a plurality of servers. Also, the reservation management server 20 and the conference management server 30 may be integrated.

In addition, the configuration examples shown in FIGS. 6 and 7 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.

Each function of the embodiments described above may be implemented by one or more processing circuits. Here, the "processing circuit" in this specification means a processor programmed by software to perform each function, such as a processor implemented by an electronic circuit, or a processor designed to perform each function described above. devices such as ASICs (Application Specific Integrated Circuits), DSPs (digital signal processors), FPGAs (field programmable gate arrays) and conventional circuit modules.

The reservation information acquisition section 33 is an example of reservation information acquisition means, the transmission method determination section 43 and the destination determination section 44 are examples of transmission method determination means, and the reminder transmission section 45 is an example of transmission means. The method information DB 491 is an example of a transmission method storage unit.

REFERENCE SIGNS LIST 10 chat server 20 reservation management server 30 conference management server 60 terminal device 70 electronic device 90 conference room terminal 100 equipment reservation system

Japanese Patent Application Laid-Open No. 2001-350884

Claims (9)

A resource reservation system in which a conference management server that manages resource reservation transmits a notification regarding resource reservation to a terminal device,
a reservation information obtaining means for obtaining reservation information relating to resource reservation;
transmission method determination means for determining a transmission method of a notification regarding the resource reservation according to the reservation information acquired by the reservation information acquisition means , and further determining a destination with respect to the transmission method requiring a destination ;
a transmission means for transmitting a notification regarding reservation of the resource to the destination in the transmission method using the transmission method determined by the transmission method determination means and, when the transmission method determination means determines the destination ;
a transmission method storage unit in which a keyword and the transmission method are associated with each other;
The resource reservation system , wherein the transmission method determination means determines to transmit the notification regarding the reservation of the resource by the transmission method associated with the keyword included in the reservation information . The conference management server communicates via a network with a plurality of information notification devices that notify information to the terminal device,
One of the transmission methods is the information notification device that transmits a notification regarding reservation of the resource,
2. The resource reservation system according to claim 1, wherein said transmission method determination means determines said information notification device for transmitting said resource reservation notification according to said reservation information. 3. A resource reservation system according to claim 2, wherein said information notification device is a chat server. one of the transmission methods is an email that transmits a notification regarding the reservation of the resource;
3. The resource reservation system according to claim 1, wherein said transmission method determining means determines an e-mail address of an e-mail to which a notification relating to reservation of said resource is to be sent, according to said reservation information. 2. The resource reservation system according to claim 1 , wherein said transmission method determination means determines whether or not said keyword is included in a conference name of said reservation information. 2. The resource reservation system according to claim 1 , wherein said transmission method determination means determines whether or not said keyword is included in a name of a person who reserved said reservation information. The transmission method determining means determines whether or not the keyword is included in the affiliation of the person who reserved the reservation information, the conference room name, the reservation authority range, the reservation time zone, or the reservation date. The resource reservation system according to claim 1 . A notification method performed by a resource reservation system in which a conference management server that manages resource reservation transmits a notification regarding resource reservation to a terminal device,
a step in which a reservation information obtaining means obtains reservation information relating to the reservation of the resource;
a step in which a transmission method determination means determines a transmission method of a notification regarding the resource reservation according to the reservation information acquired by the reservation information acquisition means, and further determines a destination with respect to the transmission method that requires a destination;
A step of transmitting, by means of the transmission means, the notification regarding the reservation of the resource , using the transmission method determined by the transmission method determination means, and further, when the transmission method determination means determines a destination, to the destination in the transmission method. and
Based on a transmission method storage unit in which a keyword and the transmission method are associated, the transmission method determination means transmits a notification regarding reservation of the resource by the transmission method associated with the keyword included in the reservation information. A notification method characterized by determining that the A conference management server that manages resource reservations,
a reservation information obtaining means for obtaining reservation information relating to resource reservation;
transmission method determination means for determining a transmission method of a notification regarding the resource reservation according to the reservation information acquired by the reservation information acquisition means , and further determining a destination with respect to the transmission method requiring a destination ;
a transmission means for transmitting a notification regarding reservation of the resource to the destination in the transmission method using the transmission method determined by the transmission method determination means and, when the transmission method determination means determines the destination ;
a transmission method storage unit in which a keyword and the transmission method are associated with each other;
The conference management server , wherein the transmission method determining means determines to transmit the notification regarding the reservation of the resource by the transmission method associated with the keyword included in the reservation information .

Images