JP7419760B2 - Resource reservation system, display method, information processing device - Google Patents

Description

The present invention relates to a resource reservation system, a display method, and an information processing device.

Resource reservation systems for reserving facilities such as conference rooms are known. In a typical resource reservation system, a user can reserve a conference room by operating a terminal device connected to a reservation management server via a network.

It is hoped that such a resource reservation system will suppress empty reservations and promote effective use of conference rooms, and will be able to notify those on the waiting list that their conference room reservations have been cancelled. A technique to do this has been devised (for example, see Patent Document 1). Patent Document 1 discloses a conference room reservation system that, when a conference room specified from cancellation waiting information is released, sends a message indicating that the conference room has been released to a user terminal that has received input of cancellation waiting information. is disclosed.

However, the conventional technology has a problem in that it does not provide a time period until automatic cancellation. For example, even if a conference room is only reserved and not in use, it is impossible to predict whether it will be canceled or used in the future until it is actually cancelled, so the user can choose another available time slot. You need to make a reservation.

SUMMARY OF THE INVENTION In view of the above problems, an object of the present invention is to provide a resource reservation system that provides a time period until automatic cancellation.

In view of the above-mentioned problems, the present invention provides a resource reservation system including an information processing device that holds information regarding resource reservation, and a terminal device, wherein the terminal device is configured based on information received from the information processing device. and a display control unit that displays the remaining time until the reservation of the resource is automatically canceled for each resource , and the display control unit displays a predetermined time from the start time of use for each of the plurality of resources. Displays either the fact that the room is waiting for room entry within the specified time, the fact that the resource is in use, or the fact that the room is vacant and not in use within a predetermined time from the start time of use, and the resource that is waiting for room entry is displayed. It is characterized by displaying the remaining time until automatic cancellation .

A resource reservation system can be provided that provides a time period before automatic cancellation.

1 is an example of a diagram illustrating an outline of the overall operation of the resource reservation system. It is a figure explaining the example of a display of a reservation status, and an example of the usage pattern of a user at that time. It is a figure which shows the example of a display of automatic cancellation time. 1 is an example of a system configuration diagram of a resource reservation system. 1 is an example of a hardware configuration diagram of a conference management server. It is an example of a hardware configuration diagram of a conference room terminal. It is an example of a functional block diagram showing the functions of a reservation management server, a chat server, a conference management server, and a registration terminal in a block form. It is an example of the functional block diagram which shows the function of a terminal device and a conference room terminal in block form. It is an example of a sequence diagram illustrating the process from reserving a conference room to displaying a standby screen. FIG. 2 is a diagram showing an example of a standby screen I displayed by a conference room terminal when the conference room is currently vacant. 12 is a diagram illustrating an example of a standby screen II displayed by a conference room terminal when the conference room is currently vacant but the next conference start time is within a predetermined time. FIG. This is an example of a standby screen III displayed by the conference room terminal when the conference room is currently in use. FIG. 3 is a diagram illustrating a process or operation in which a terminal device acquires a conference room ID from a transmitter installed in a conference room. FIG. 3 is a diagram illustrating an operation when the conference management server proposes a conference room suitable for the reservation person's current location. It is an example of the sequence diagram explaining the process or operation|movement by which a terminal device displays a reservation status screen. FIG. 7 is an example of a sequence diagram illustrating a procedure in which a reservation application on a terminal device reserves a conference room on a reservation management server. FIG. It is a figure which shows an example of a reservation status screen (Example 2). FIG. 2 is an example of a sequence diagram illustrating a procedure in which a conference application on a terminal device reserves a conference room in a conference management server. FIG. It is a figure which shows an example of a reservation status screen (Example 3). It is an example of a diagram illustrating the transition between a waitlist reservation button and a button to be used at the next time. It is a figure which shows an example of the detailed reservation screen displayed after pressing the link of detailed reservation. FIG. 7 is an example of a sequence diagram illustrating a procedure in which a conference application on a terminal device reserves a conference room in a conference management server when a waitlist reservation button is pressed. FIG. It is a figure showing an example of a reservation status screen displayed by a centralized terminal.

DESCRIPTION OF THE PREFERRED EMBODIMENTS A resource reservation system and a display method performed by the resource reservation system will be described below with reference to the drawings as an example of a mode for carrying out the present invention.

<Outline of resource reservation system>
First, the outline of the resource reservation system will be explained using FIG. FIG. 1 is an example of a diagram illustrating an overview of the overall operation of the resource reservation system 100.

A. The person making the reservation operates his or her own terminal device to communicate with the reservation management server 20 and reserve a conference room. The reservation management server 20 is a general-purpose cloud service (Office365, G Suite (both registered trademarks), etc.), and conference rooms owned by organizations such as companies to which the reservation person belongs are registered.

B. The conference management server 30 is a server that controls the entire resource reservation system 100 based on the reservation status of conference rooms. Since the conference management server 30 appropriately communicates with the reservation management server 20 to obtain reservation information, the reservation information is synchronized with the reservation management server 20.

C. The administrator of the resource reservation system 100 or the organization side can register users and perform various settings on the conference management server 30. User registration refers to registering a user to whom various notifications will be sent using the chat server 10 (slack, Line, Microsoft Teams (all registered trademarks), etc.). Further, since the notification is performed via a bot that sends a message as the conference management server 30, a bot provided by the chat server is also registered. Various settings include registration of the conference room terminal 90, reminder timing settings, and the like.

D. The conference management server 30 reminds the person making the reservation to hold the conference at a predetermined time before the conference start time in the reservation information. This suppresses empty reservations of conference rooms. Further, the conference management server 30 notifies the user of the invitation code as necessary. Upon receiving the reminder, the person who reserved the conference stores information (conference identification information) for checking into the conference room in the terminal device 60.

E. A conference room terminal 90 (an example of an information processing terminal) is arranged in each conference room 6, and the conference room terminal 90 periodically downloads reservation information for this conference room. The conference room terminal 90 can display the current day's schedule, the latest conference schedule, etc., and allow participants to confirm the schedule. Shortly before the start time of the conference, the person who reserved the conference room goes to conference room 6 and checks in. For example, the conference identification information is input into the conference room terminal 90, or the terminal device 60 is held over the conference identification information (to read the conference identification information, to communicate, etc.). Such an operation is called a check-in operation, and the check-in operation is an operation to start using the conference room.

F. Since the conference room terminal 90 transmits a check-in request (notification of start of use) to the conference management server 30, if the conference identification information can be authenticated, the conference room terminal 90 receives a response from the conference management server 30 indicating that the check-in was successful. The conference room terminal 90 displays that the conference room is in session (in use). If check-in cannot be confirmed by the predetermined time relative to the start time of the conference, the conference management server 30 cancels the reservation for the conference room 6 (automatic cancellation) and displays this fact on the conference room terminal as a status included in the reservation information. Send to 90. In this case, since the conference room terminal 90 displays that the room is vacant, any user can use the conference room 6.

G. The conference room terminal 90 controls the electronic device 70 based on a request from the conference management server 30. For example, the power is turned on at the start time and turned off at the end time of the conference. By doing so, it is possible to improve the convenience when conference participants operate the electronic device 70.

H. For example, when the electronic device 70 has a video conference function, it can communicate with the electronic device (such as the video conference terminal 70x) of another base 4 and hold a conference with the other base. Note that the PC 70y on which the application operates can also communicate with the electronic device 70. The reservation information includes in advance destination information (communication ID of the destination) indicating another base, and the electronic device 70 can automatically communicate with the video conference terminal 70x and the PC 70y.

I. When the person making the reservation ends the meeting, he or she presses a button on the conference room terminal 90 to check out, so the conference room terminal 90 displays the next reservation status. This allows any user to grasp the reservation status of a conference room.

<Display example of conference room reservation status>
Next, an example of a display of the reservation status of a conference room and an example of the user's usage pattern at that time will be explained using FIG. 2. FIG. 2A is an example of a reservation list screen 310 provided by the conference management server 30. FIG. 2(b) is a diagram showing an example of the positions of the user's own seat and the conference room.

First, the premise is as follows.
-Current time is "10:10".
- The user wants to use the conference room for "one hour now."
- The conference room is reserved on the reservation management server as shown in Figure 2.
- Conference room A is currently reserved on the reservation management server, but no user has checked in.
- The automatic cancellation time registered in the conference management server 30 is when 15 minutes have elapsed from the start time.

In such a system, when the user checked the reservation status on the reservation list screen 310 in FIG. 2(a), it was found that there were no conference rooms available for immediate use. When I visually checked from my seat, it appeared that "Meeting Room A" was not in use, but it was determined that it could not be used because it was reserved on the reservation management server. Conference room E is empty, but there is only less than an hour until the next meeting. In this way, since the user cannot use the room for "an hour right now," he reserved "conference room F" for "11:30 to 12:30," where he could secure an hour the earliest.

In this case, even if conference room A is vacant and is canceled, the user cannot know the possibility of being able to use conference room A until it is cancelled.

<Display of remaining time until automatic cancellation of conference room>
Therefore, in the present embodiment, the terminal device 60 uses a web browser or an application to display the remaining time until the conference room is automatically canceled, so that the user can view the conference room that has a high possibility of being automatically canceled. clearly indicate.

FIG. 3 is a diagram showing a display example (reservation status screen 300) of automatic cancellation time. As shown in FIG. 3, the terminal device 60 can display the remaining time until automatic cancellation for each resource (conference room) based on the information received from the conference management server 30.

This allows the user to know that there is a possibility that conference room A will be available even before conference room A is cancelled, so they can reserve conference room A by waiting just 5 minutes. Become. Therefore, it becomes easier to use the resource of conference room A effectively. Furthermore, it is possible to eliminate the task of visually checking the usage status of resources (conference rooms), thereby improving usability for the user.

Furthermore, as shown in FIG. 3, the start time of the next reservation is also displayed, making it possible to assist in determining whether to wait for automatic cancellation and use the resource (conference room).

<About terms>
Resource means resource. A conference room and equipment, equipment, people, 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.

The reservation person is a person who has reserved a conference room, and the participant is a person who participates in the conference. The person who made the reservation is often included in the participants, but does not have to be included. In this embodiment, the work performed by the reservation holder may be performed by the participant. Collectively, those who use the conference room are simply referred to as users.

Permitting the use of a resource means that the conference management server detects that the use of the resource has been started by a legitimate reservation holder or participant. The fact that resource use is permitted is reflected on the conference room terminal. From the user's point of view, this means that the use of the resource is permitted (this means that the user was able to check in).

Automatic cancellation means that a resource reserved by a user is canceled without the user performing a cancellation operation. For example, if the user does not perform an operation to start using the resource by a predetermined time, it will be automatically canceled.

The remaining time until automatic cancellation refers to how much time remains until automatic cancellation. It may also be called a countdown. In addition to the time itself, it may be displayed as an image such as a bar display or an hourglass display.

<System configuration example>
FIG. 4 is an example of a system configuration diagram of the resource reservation system 100. The resource reservation system 100 can be mainly divided into an external network N2 and an internal network N1. The internal network N1 refers to 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 one or more chat servers 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 conference participant may be connected to the external network N2 as necessary.

The reservation management server 20 is realized by one or more information processing devices (computer systems) equipped with a general server OS or the like. A system related to resource reservations provided by the reservation management server 20 is referred to as a reservation management system. The reservation management server 20 has a calendar system and provides a web application for managing various schedules. Specifically, it has the following functions, for example.
- Accepts appointment registrations and allows reservation holders to check anytime and anywhere - Notifies you via email at a set date and time, such as 30 minutes before the appointment - One person can manage appointments on multiple calendars (work, home, etc.) Possible - Share a calendar with people in the same group The reservation management server 20 manages users by account. 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 for the system to uniquely identify the user (a function of identification information). 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 specifying the account of the reservation management server 20 and requesting the reservation information. Note that the account may be any information that can uniquely identify the user, such as e-mail, ID, or telephone number.

In this embodiment, what is managed as a schedule is the reservation for the conference room 6, but the reservation management server 20 is not limited to the conference room 6 and can manage various schedules. In addition to conference room 6, we offer a variety of other resources such as rental of various electronic devices, parking reservations, rental offices, rental studios, rental bicycles, rental cars, accommodation facilities such as hotels, and rental spaces such as event halls and lockers. Available for reservations.

Note that G Suite (registered trademark), Office365 (registered trademark), and the like are known as reservation management systems, but any reservation management system that has the functions described in this embodiment may be used.

Further, in this 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 uses the conference room name, conference room ID, reservation available time, capacity of each conference room 6, reservation unit, etc. of each conference room 6 in the internal network of the company using the resource reservation system 100. 20 web apps are customized. Therefore, the conference room 6 of the company using the resource reservation system 100 and the reservation information are linked.

The chat server 10 can be realized by one or more information processing devices (computer systems) equipped with a general server OS or the like. A real-time sharing system for information such as text, audio, and video among multiple users provided by the chat server 10 is referred to as a chat system. The chat server 10 notifies the terminal device 60 of information regarding the reservation of the conference room 6. In this embodiment, a plurality of chat servers 10 operated by different operators may be included.

The information to be shared includes images, audio, etc., and is not limited to text; however, for convenience of explanation, in this embodiment, text is mainly used for notifications. For example, a chat system may provide voice calling functionality between groups. The voice call may be one-to-one or one-to-N (≧2). Therefore, in this embodiment, when the chat system notifies information regarding the reservation of the conference room 6, it may output a voice message in addition to displaying text. Note that chat systems such as LINE (registered trademark, hereinafter omitted), slack, and Microsoft Teams (registered trademark, hereinafter omitted) are known, but bots (which perform predetermined processing) Any chat system may be used as long as it is possible to notify one or more users from an executed program.

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

The conference management server 30 can be realized by one or more information processing devices (computer systems) equipped with a general server OS or the like (corresponding to the information processing device in the claims). As a process related to the external network N2, the conference management server 30 acquires the reservation information of the conference room 6 from the reservation management server 20, acquires the scheduled participants set in the reservation information, and selects the scheduled participants at the set timing. A notification is sent to the group (or individual person such as the reservation holder) of the chat server 10 associated with the . Further, as processing related to the in-house network N1, check-in and check-out to the conference room 6 is 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 internal network N1 includes a conference room 6, a work place 101 for prospective participants, a work place 102 for an administrator, etc., and prospective participants can access the external network N2 from various locations via the internal network N1. The in-house network N1 is, for example, a LAN (Local Area Network). The conference room 6, the work place 101 of the prospective participant, and the work place 102 of the administrator are not necessarily on a LAN within the same company.

A conference room terminal 90 and an electronic device 70 are arranged in the conference room 6. The conference room terminal 90 and the electronic device 70 can communicate via a small LAN or a dedicated line. The electronic device can be connected to the internal network N1 and the external network N2 without going through the conference room terminal 90. The conference room terminal 90 and the electronic device 70 may communicate wirelessly or by wire. Note that since the internal network N1 is located inside the firewall 73, direct communication from the external network N2 to the internal network N1 is difficult.

The conference room terminal 90 is an information processing device (information processing terminal) operated by a participant in the conference, such as a person making a reservation, who uses the conference room 6 . The conference room terminal 90 is placed on a desk in the conference room 6 or at the entrance of the conference room 6. A plurality of conference room terminals 90 may be arranged in one conference room 6. The conference room terminal 90 can be realized by one or more information processing devices (computer systems) equipped with a general OS or the like.

The conference room terminal 90 transmits the conference room ID to the conference management server 30, and displays reservation information for the conference room 6 for the current day. Further, control information such as power ON/OFF of the electronic device 70 is acquired from the conference management server 30 . Thereby, the conference room terminal 90 turns on and off the power of the electronic device 70.

Further, 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 pre-held conference room ID to the conference management server 30, so the conference management server 30 uses the conference identification information and the conference room ID. It can be confirmed that the person who reserved the conference room 6 will use the reserved conference room 6.

The electronic equipment 70 is various office equipment that can be used in the conference room 6. The electronic device 70 is a resource to be reserved together with the conference room 6. For example, electronic whiteboards, multifunction peripherals, projectors, digital signage, digital cameras, etc. An electronic blackboard has a large display with a touch panel, detects the coordinates of the board specified by the user, connects the coordinates, and displays strokes. In addition, it is possible to display images from a connected PC, and to synchronize strokes by communicating with electronic whiteboards at other locations. Note that the electronic blackboard is sometimes called an electronic information board or an electronic whiteboard.

Multifunction peripherals have functions such as copiers, scanners, printers, and fax transmission/reception, and are used to print materials during meetings, copy materials, digitize materials, and send materials. A projector is a device that projects an image. For example, images displayed on a display by the terminal device 60 may be projected onto a screen or the like, thereby allowing them to be shared among participants. Digital signage is a large display used to display any still or moving image. Digital cameras will be used by each participant to capture and save images of paper materials and materials displayed on the electronic blackboard.

A terminal device 60 that can be connected to the company network N1 is arranged at the work place 101 of the prospective participant. The terminal device 60 may communicate by wire or wirelessly. The terminal device 60 is an information processing device used when prospective participants (including those making reservations) reserve a conference room, but it is also assumed that the terminal device 60 is brought into the conference room. This is an information processing device carried by participants.

The terminal device 60 can be realized by one or more information processing devices (computer systems) equipped with a general OS or the like. The terminal device 60 is, for example, a smartphone, a tablet terminal, a PC (Personal Computer), a PDA (Personal Digital Assistant), a wearable PC (sunglasses type, wristwatch type, etc.). However, it is only necessary to have a communication function and operate browser software or application software dedicated to the chat server 10 or the reservation management server 20. For example, a car navigation system, a game machine, a television receiver, etc. can also serve as the terminal device 60.

In the terminal device 60, application software (hereinafter referred to as a chat application) dedicated to the chat server 10 runs, and further, application software dedicated to the resource reservation system 100 (hereinafter referred to as a conference application) runs. However, these may be replaced by browser software.

A registration terminal 50 that can be connected to the in-house network N1 is arranged at the administrator's work place 102. The registration terminal 50 may communicate by wire or wirelessly. The registration terminal 50 is an information processing device used by the administrator to perform initial settings on the conference room terminal 90.

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

<Hardware configuration>
<<Hardware configuration of conference management server>>
FIG. 5 is an example of a hardware configuration diagram of the conference management server 30. 3 is an example of a schematic hardware configuration diagram of the conference management server 30. FIG. The conference management server 30 is constructed by a computer, and as shown in FIG. interface), network I/F 509, bus line 510, keyboard 511, pointing device 512, DVD-RW drive 514 (Digital Versatile Disk Rewritable), and media I/F 516.

Among these, the CPU 501 controls the entire operation of the conference management server 30. The ROM 502 stores programs used to drive the CPU 501 such as IPL. RAM 503 is used as a work area for CPU 501. The HD 504 stores various data such as programs. The HDD controller 505 controls reading and writing of various data to the HD 504 under the control of the CPU 501. The display 506 displays various information such as a cursor, menu, window, characters, or images. External device connection I/F 508 is an interface for connecting various external devices. The external device in this case is, for example, a USB (Universal Serial Bus) memory, a printer, or the like. The network I/F 509 is an interface for data communication using a communication network. The bus line 510 is an address bus, a data bus, etc. for electrically connecting each component such as the CPU 501 shown in FIG. 5.

Further, the keyboard 511 is a type of input means that includes a plurality of keys for inputting characters, numerical values, various instructions, and the like. The pointing device 512 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, and the like. The DVD-RW drive 514 controls reading and writing of various data on a DVD-RW 513, which is an example of a removable recording medium. Note that it is not limited to DVD-RW, but may be DVD-R or the like. The media I/F 516 controls reading or writing (storage) of data to a recording medium 515 such as a flash memory.

＜＜Conference room terminal＞＞
FIG. 6 is a hardware configuration diagram of an example of the conference room terminal 90. Note that the conference room terminal 90 in FIG. 6 is assumed to be a tablet device. As shown in FIG. 6, the conference room terminal 90 includes a CPU 701, ROM 702, RAM 703, EEPROM 704, CMOS sensor 705, image sensor I/F 706, acceleration/direction sensor 707, media I/F 709, and GPS receiving section 711. We are prepared.

Among these, the CPU 701 controls the operation of the conference room terminal 90 as a whole. The ROM 702 stores the CPU 701 and programs used to drive the CPU 701 such as IPL. RAM 703 is used as a work area for CPU 701. The EEPROM 704 reads or writes various data such as applications under the control of the CPU 701. A CMOS sensor 705 (Complementary Metal Oxide Semiconductor) is a type of built-in imaging means that images a subject (mainly a self-portrait) and obtains image data under the control of the CPU 701. Note that instead of a CMOS sensor, an imaging means such as a CCD (Charge Coupled Device) sensor may be used. The image sensor I/F 706 is a circuit that controls driving of the CMOS sensor 705. The acceleration/azimuth sensor 707 is a variety of sensors such as an electronic magnetic compass, a gyro compass, and an acceleration sensor that detect geomagnetism. A media I/F 709 controls reading or writing (storage) of data to a recording medium 708 such as a flash memory. GPS receiving section 711 receives GPS signals from GPS satellites.

The conference room terminal 90 also includes a long-distance communication circuit 712, a CMOS sensor 713, an image sensor I/F 714, a microphone 715, a speaker 716, a sound input/output I/F 717, a display 718, an external device connection I/F 719, and a short-range communication It includes a circuit 720, an antenna 720a of a short-range communication circuit 720, and a touch panel 721.

Among these, the long distance communication circuit 712 is a circuit that communicates with other devices via a communication network. The CMOS sensor 713 is a type of built-in imaging means that images a subject and obtains image data under the control of the CPU 701. The image sensor I/F 714 is a circuit that controls driving of the CMOS sensor 713. Microphone 715 is a built-in circuit that converts sound into electrical signals. The speaker 716 is a built-in circuit that converts electrical signals into physical vibrations to produce sounds such as music and voice. The sound input/output I/F 717 is a circuit that processes input/output of sound signals between the microphone 715 and the speaker 716 under the control of the CPU 701 . The display 718 is a type of display means such as a liquid crystal or organic EL (Electro Luminescence) that displays an image of a subject, various icons, and the like. The external device connection I/F 719 is an interface for connecting various external devices. The near field communication circuit 720 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The touch panel 721 is a type of input means by which the user operates the conference room terminal 90 by pressing the display 718.

The conference room terminal 90 also includes a bus line 710. The bus line 710 is an address bus, a data bus, etc. for electrically connecting each component such as the CPU 701 shown in FIG. 6.

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

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

The communication unit 21 transmits and receives various information to and from the conference management server 30 and the terminal device 60. The communication unit 21 transmits screen information of a reservation setting screen to the terminal device 60 and receives reservation settings from the terminal device 60. Further, reservation information is transmitted to the conference management server 30.

The reservation information management unit 22 manages reservation information registered by the user. The reservation information management section 22 reads the reservation information for 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 section 21 . Alternatively, once 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 prospective participant to reserve a conference room 6 on the reservation management server 20.

The reservation management server 20 has a storage section 29 . The storage unit 29 is realized by the RAM 503, HD 504, etc. shown in FIG. A reservation information DB 291 (Data Base) is constructed 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, the following items are registered in association with the reservation ID: reservation person account, conference name, conference room ID, start time, end time, and prospective participant account. The reservation ID is identification information that identifies one record of reservation information. ID is an abbreviation for Identification and means an identifier or identification information. ID refers to a name, code, character string, 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. The 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 assigned by the prospective participants. The conference room ID is identification information that identifies the conference room 6 in the company network. The start time (usage start time) is the beginning of the time slot in which the conference room 6 was reserved (the time at which the meeting starts), and the end time (use end time) is the end of the time slot in which the conference room 6 was reserved (the time at which the meeting starts). (time when the meeting ends). The prospective participant account is an account of a prospective participant who is scheduled to participate in the conference. Note that the accounts in Table 1 are all issued by the reservation management server 20.

<<Chat server>>
The chat server 10 includes a communication section 11 and a text processing section 12. Each of these functional units possessed by the chat server 10 is a function realized by operating one of the configuration categories shown in FIG. It is a means.

The communication unit 11 transmits and receives various information to and from the conference management server 30. In this embodiment, information regarding the reservation of a conference room, information identifying a bot (such as a token to be described later), and information identifying a group to be notified are received from the conference management server 30. Information identifying this bot is notified in advance as bot identification information from the chat server 10 when the bot for the conference management server 30 is created. Furthermore, an account of an individual such as the person making the reservation may be specified. The communication unit 11 also transmits to the conference management server 30 a notification that the prospective participant has already read the information regarding the conference room reservation, or a response from the prospective participant to the displayed information regarding the conference room reservation.

Based on the information that identifies the bot and the information that specifies the notification destination group notified from the conference management server 30, the text processing unit 12 reserves the conference room 6 for prospective participants belonging to the group as information to be spoken by the bot. Send information about. If a notification destination account is further designated by the conference management server 30, information regarding the reservation of the conference room 6 is sent to one of the prospective participants belonging to the group. Therefore, notifications may be given for the number of prospective participants, or may be given only to arbitrary users such as those who have made reservations.

The text processing unit 12 can perform so-called push notifications. Examples of mechanisms include the following. The chat application 60a receives an ID (token) for push notification 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 chat application 60a account in the chat server 10. When the chat server 10 sends a push notification, the account of the chat application 60a is specified, so the linked token can be specified. The chat system specifies the token and sends the notification contents to the server operated by the OS manufacturer. This server sends a push notification to the device (terminal device 60) linked to the token.

The chat server 10 also includes a storage section 19 . The storage unit 19 is realized by the RAM 503, HD 504, etc. shown in FIG. A group information DB 191 is constructed 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.

A workspace is identification information for identifying an organization such as a company or a department. In this embodiment, a plurality of members belong to a workspace (for example, company A). The workspace is, for example, a URL, but only needs to be unique. Furthermore, the workspace has multiple channels depending on the purpose of chatting. A channel is a collection of members, such as a group for product A and a group for product B, with which common information is exchanged. One of the members belonging to the workspace belongs to the channel. In other words, notification destinations are identified by workspace and channel. However, since the method of specifying the notification destination differs depending on the chat system, if there is identification information that can uniquely specify the group, the group may be specified using only that information, or may be specified using three or more pieces of information.

Channels are guaranteed to be unique. Member accounts 1 to n are accounts of members of the channel, 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 a proxy or a fictitious member of the conference management server 30. The bot's remarks (text) are transmitted to the terminal devices 60 of member accounts 1 to n.

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

<<Conference management server>>
The conference management server 30 includes a communication section 31 , an information association section 32 , a reservation information acquisition section 33 , a notification judgment 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 , a reservation information transmission section 39, a task execution section 40, an information provision section 41, a reservation section 42, and a resource determination section 43. Each of these functional units possessed by the conference management server 30 is realized by operating one of the configuration categories shown in FIG. or means. This program 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, and the terminal device 60. The communication section 31 has a transmitting section 31a and a receiving section 31b. The receiving unit 31b receives reservation information from the reservation management server 20 and receives a request for reservation information from the conference room terminal 90. Further, the receiving unit 31b receives a check-in request from the conference room terminal 90. Further, the receiving unit 31b receives correspondence between groups of the chat system and accounts from the registration terminal 50 operated by the administrator. The transmitter 31a transmits information regarding the reservation of a conference room to the chat server 10, and transmits reservation information to the conference room terminal 90.

The information association unit 32 mainly performs processing related to pre-registration work. That is, domain registration is received from the registration terminal 50, etc., and registered in the customer domain DB 495, and the workspace and channel of the chat system sent from the registration terminal 50, etc. are associated with the account of the reservation management server 20, and are stored in the correspondence information DB 491. register.

The reservation information acquisition unit 33 specifies the account of the customer who uses the resource 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. Or automatically receive 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 in the future from the present among the reservation information held by the reservation management server 20. The predetermined period is determined by how far into the future the conference room 6 reservation information is to be notified.

The reservation information acquisition unit 33 generates an automatically canceled task and registers it in the task queue 499 when the reservation information is acquired. The task queue 499 is a FIFO (First In First Out) queue, and is executed when the execution time arrives.

The notification determination unit 34 determines whether there is a reservation for a start time that satisfies notification conditions in the conference management information. For example, with reference to the notification setting DB 496, it is determined that the notification will be sent at the set date and time by counting backwards from the reservation start time. Note that if bots are divided by role, such as a bot for reminders and a bot for reservation reception, the bots are identified according to the processing.

When the notification determination unit 34 determines to notify, the conference information notification unit 37 specifies information that identifies the bot (for example, a token in Slack) and information that specifies the group to be notified, and notifies information regarding the reservation of the conference room 6. request the chat server 10 to do so. Note that although the notification is divided into several times, the conference identification information is included in at least one of the notifications. The conference identification information is information for the conference management server 30 to confirm that the participant has the right to use the reserved conference room 6 during the reserved time slot. The conference information notification unit 37 generates conference identification information at least before final notification. Note that the conference identification information is registered in the conference identification information DB 494.

The control information generation unit 35 generates control information for the electronic device 70 with reference to the conference management information DB 493 and registers the control information in the control information DB 497. For example, control information for turning on the electronic device 70 several minutes before the start time of a conference is generated, and control information for turning off the power for the electronic device 70 when a checkout is detected is generated. The control information is stored in the control information DB 497.

The control information response unit 36 receives an inquiry from the conference room terminal 90 of the conference room 6 as to whether 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 check-in management section 38 manages check-in and check-out to the conference room. Further, 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, for example, 5 to 10 minutes before the start time of the conference specified by the reservation ID. For example, a time 5 to 10 minutes before the start time of the conference is called a check-in possible time (a possible use start time). Then, check-in is permitted when the combination of the conference room ID and conference identification information transmitted by the conference room terminal 90 is registered in the conference identification information DB 494. When the check-in management unit 38 permits check-in, it deletes the automatic cancellation task. Unless the task is deleted, the task execution unit 40 cancels the conference room reservation at a time, for example, 10 to 15 minutes after the conference start time. In this case, the check-in management section 38 requests the reservation management server 20 to cancel the reservation. This suppresses empty reservations.

The reservation information transmitter 39 transmits reservation information (conference management information) stored in the conference management information DB 493 in response to a request from the conference room terminal 90. The reservation information transmitter 39 may transmit in JSON format, XML format, CVS (Comma-Separated Values) format, or the like. Since reservation information is repeatedly transmitted, a format with a small capacity is advantageous.

The task execution unit 40 periodically checks the tasks stored in the task queue 499 and executes the tasks whose execution time has arrived. Therefore, if the check-in request is not transmitted from the conference room terminal 90 by the predetermined timing based on the start time, the task execution unit 40 cancels the conference room reservation (automatic cancellation) since the task has not been deleted. Note that although the task described in this embodiment is an automatically canceled task, various tasks that are executed based on time may be executed.

The information providing unit 41 transmits information for displaying a reservation status screen to the terminal device 60. Screen information for displaying a web page or web application may also be transmitted. The information providing unit 41 can provide any information held by the conference management server 30, but for example, the information providing unit 41 may provide information such as the start time, end time, automatic cancellation time, and check-in status of a conference room in response to a request from the terminal device 60. and transmits it to the terminal device 60.

The reservation unit 42 reserves a conference room in the reservation management server 20 with the authority of the conference management server 30. As a result, if the conference room is vacant, the user can use it immediately without making a reservation with the reservation management server 20.

The resource determining unit 43 uses the conference room provision information DB 492 to determine a conference room from the MAC address of the access point transmitted from the terminal device 60 and provides the conference room to the terminal device 60.

The conference management server 30 also has a storage section 49 . The storage unit 49 is realized by the RAM 503, HD 504, etc. shown in FIG. The storage unit 49 includes a correspondence information DB 491, a conference room provision information DB 492, a conference management information DB 493, a conference identification information DB 494, a customer domain DB 495, a notification setting DB 496, a control information DB 497, a conference room setting information DB 498, and a task queue 499. is memorized.

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

Table 3 shows an example of the association information stored in the association information DB 491. The association information is information that associates an account in the reservation management system with a group in the chat system. The correspondence information includes items such as workspace, channel, and member accounts 1 to n (n=4 in the figure). Workspace and channels are as above. Each participant's account issued by the reservation management server 20 is registered in member accounts 1 to n. Additionally, a chat system account may be registered as shown in Table 3. In order to notify a group, information for specifying the reservation management server 20 account of the user who reserved the conference, the notification destination group and channel (in this embodiment, the workspace and (channel name) is sufficient, and it is not necessarily necessary that the accounts of all members belonging to the group are registered. However, when notifying individual users, account information for each chat system is required, so the information may be registered as shown in Table 3.

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

Table 4 shows an example of conference management information stored in the conference management information DB 493 of the conference management server 30. Since reservation information is stored in the conference management information DB 493, Table 4 will explain the differences from the reservation information DB 291 in Table 1. The conference management information in Table 4 has a status item. Status means the status of the reservation. For example, the status of information regarding the reservation of the conference room 6, such as notified, usage confirmed, checked in, checked out, or canceled, 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 includes the following items: reservation ID, conference room ID, and conference identification information. These are the same as the reservation information except for the status (reservation information received from the reservation management server 20), and since they have already been mentioned, their explanation will be omitted. Note that the reason why the reservation ID is registered is to identify reservations for the same conference room 6. Status means the status of the reservation. For example, the status of information regarding the reservation of a conference room, such as notified, confirmation of use, checked-in, checked-out, or cancellation (cancellation), is registered.

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

Table 6 shows an example of customer domain information stored in the customer domain DB 495. Customer domain information is information for managing the customer's domain and the customer's administrator account. In the customer domain information, the customer's domain name and the customer's administrator account are registered in association with each other. The customer domain in Table 6 is the domain of the account (email address) issued by the reservation management server 20. Further, the administrator account is an account of a customer's administrator (representative). Note that the accounts in Table 6 are those 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 notification-related settings for each customer. In the notification setting information, customer domain names and notification settings are registered in association with each other. In the notification settings, the timing of how far in advance of the start time of the conference the information regarding the reservation of the conference room 6 is to be notified is set. Alternatively, a fixed date and time may be set. Further, 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 for the electronic device 70. The conference management server 30 can set detailed control contents for each electronic device 70. Furthermore, the reason why the control time is not registered is that it is difficult to transmit the control information from the conference management server 30 of the external network to the conference room terminal 90, and when the conference room terminal 90 accesses the conference management server 30, This is because if the control information is generated, the control contents will be transmitted.

表９は、会議室設定情報ＤＢ４９８に記憶されている会議室設定情報の一例を示す。会議室設定情報は会議室ごとの設定に関する情報である。会議室設定情報は会議室名称、会議室ＩＤ、会議室端末の状態、認証キー、管理開始フラグ、及び、アクセス時刻の各項目を有する。
・会議室名称は会議の参加者が認識している会議室の一般的な名称であり、例えば会議室の入り口に提示されているものをいう。
・会議室ＩＤは上記のように会議室を一意に識別する識別情報である。簡易的には、会議室ＩＤは予約管理サーバ２０と共通とすることができる。また、変換テーブルを設けることで、予約管理サーバ２０と別に管理者が設定することもできる。
・会議室端末の状態は会議室端末９０の初期設定が終了したか、通信が可能か等を示す。
接続中 ：例えばポーリングにより通信が確認できている状態
セットアップ前：初期設定の前
接続断 ：一定期間（本実施形態ではＭ分）以上、通信がない状態
・認証キーは会議管理サーバ３０が会議室端末９０を認証するための認証情報となる。初期設定により認証キーが会議室端末９０に送信される。認証キーは総当たり方式で特定できない程度に長い桁数の数字、アルファベット、記号などの組み合わせである。認証キーは会議管理サーバ３０が決定しても管理者が決定してもよい。
・管理開始フラグは、会議室端末９０の初期設定が終わった後に、会議室の管理を会議管理サーバ３０が開始するか否かを示すフラグ（Ｔｒｕｅ：開始する Ｆａｌｓｅ：開始しない）である。管理開始フラグがあることで、初期設定が完了してから会議室端末９０の配置までのタイムラグで生じる不都合を抑制できる。
・アクセス時刻は、会議室端末９０が定期的に要求する予約情報をＮ分ごとに記録した時刻である。予約情報の要求に限らず、会議室端末９０と通信した時刻を記録してよい。Ｎ分、Ｍ分、ポーリングの間隔には以下の関係がある。
ポーリングの間隔＜Ｎ分＜Ｍ分
ポーリングごとにアクセス時刻を記録してもよい。しかし、ポーリング間隔が短い場合、会議管理サーバ３０の会議室設定情報ＤＢ４９８の負荷が大きくなってしまう。そこで、ポーリングの間隔よりも大きいＮ分ごとにアクセス時刻を記録することにして、負荷を低減する。

Table 9 shows an example of conference room setting information stored in the conference room setting information DB 498. The conference room setting information is information regarding settings for each conference room. The conference room setting information includes the following items: conference room name, conference room ID, conference room terminal status, authentication key, management start flag, and access time.
- The conference room name is the general name of the conference room that is recognized by the participants of the conference, for example, the name displayed at the entrance of the conference room.
- The conference room ID is identification information that uniquely identifies the conference room as described above. For simplicity, the conference room ID can be the same as that of the reservation management server 20. Further, by providing a conversion table, the administrator can set it separately from the reservation management server 20.
- The status of the conference room terminal indicates whether the initial settings of the conference room terminal 90 have been completed, whether communication is possible, etc.
Connected: For example, communication has been confirmed by polling. Before setup: Before initial settings. Connection disconnected: No communication for a certain period of time (M minutes in this embodiment). The authentication key is set by the conference management server 30 in the conference room. This is authentication information for authenticating the terminal 90. An authentication key is sent to the conference room terminal 90 by initial setting. The authentication key is a combination of numbers, alphabets, symbols, etc. with a long number of digits that cannot be determined using a brute force method. The authentication key may be determined by the conference management server 30 or by the administrator.
- The management start flag is a flag indicating whether or not the conference management server 30 starts managing the conference room after the initial settings of the conference room terminal 90 are completed (True: start, False: do not start). With the management start flag, it is possible to suppress inconveniences caused by a time lag between the completion of initial settings and the placement of conference room terminals 90.
- The access time is the time when the reservation information periodically requested by the conference room terminal 90 is recorded every N minutes. In addition to the request for reservation information, the time of communication with the conference room terminal 90 may be recorded. The following relationship exists between N minutes, M minutes, and polling intervals.
Polling interval <N minutes <M minutes The access time may be recorded for each poll. However, if the polling interval is short, the load on the conference room setting information DB 498 of the conference management server 30 will increase. Therefore, the load is reduced by recording access times every N minutes, which is longer than the polling interval.

Among the conference room setting information stored in the conference room setting information DB 498, the conference room name and conference room ID are predetermined or can be set by the administrator. The one sent from the reservation management server 20 may be used. The initial state of the conference room terminal 90 (immediately after provider settings) is before setup, but changes depending on the communication status as described in this embodiment. The authentication key is numbered and set by the conference management server 30 at the time of initial setting. The management start flag is set by the administrator. The access time is recorded by the conference management server 30 every N minutes.

表１０はタスクキュー４９９に記憶されているタスクの一例を示す。タスクキュー４９９には時系列に会議管理サーバ３０が実行すべきタスクが登録されている。タスクキュー４９９は、タスクＩＤ、実行時刻、タスク内容、及び、予約ＩＤの各項目を有する。タスクＩＤはタスクを識別するための識別情報である。実行時刻はこのタスクを実行する時刻である。タスク内容は、タスクの具体的な内容である。予約ＩＤは、会議管理情報ＤＢ４９３の予約情報を特定するために設定される。例えば、会議室の予約がキャンセルされた場合に、タスク実行部４０が会議管理情報ＤＢ４９３の予約情報を特定してステータスを「キャンセル済み」に変更するために設定される。

Table 10 shows an example of tasks stored in the task queue 499. Tasks to be executed by the conference management server 30 are registered in the task queue 499 in chronological order. The task queue 499 has the following items: task ID, execution time, task content, and reservation ID. The task ID is identification information for identifying a task. The execution time is the time at which this task is executed. The task content is the specific content of the task. The reservation ID is set to specify reservation information in the conference management information DB 493. For example, when a reservation for a conference room is canceled, the task execution unit 40 is configured to specify the reservation information in the conference management information DB 493 and change the status to "cancelled".

Further, when a check-in request is sent from the conference room terminal 90, the check-in management unit 38 updates the status of the conference management DB to “checked in”, but upon detection of check-in, the check-in management unit 38 updates the task Delete tasks in queue 499. That is, the check-in management unit 38 identifies the task in the task queue 499 using the reservation ID of the conference management information whose status has been updated to "checked in", and deletes the automatically canceled task. This prevents your check-in from being canceled even though you have already checked in.

表１１（ａ）は、会議室提供情報ＤＢ４９２に記憶されているアクセスポイントテーブルの一例を示す。アクセスポイントテーブルには後述するアクセスポイントが設置されている場所が登録されている。アクセスポイントテーブルは、ＭＡＣアドレス、棟、フロア及び方位の各項目を有している。アクセスポイントの場所を特定する棟、フロア又は方位をカテゴリという。

Table 11(a) shows an example of an access point table stored in the conference room provision information DB 492. The access point table registers locations where access points, which will be described later, are installed. The access point table has items such as MAC address, building, floor, and direction. A building, floor, or direction that specifies the location of an access point is called a category.

A MAC address is a physical address uniquely assigned to the hardware of a network device such as a LAN card, which is set to identify each node (each individual) on a network. In Table 11(a), the MAC address of the access point is registered. The ridge is the building where the access point is installed, the floor is the floor of the building where the access point is installed, and the direction is where the access point is located on the floor (for example, north, south, east, west, but the number indicating the division, Indicates whether it is installed near ○○ stairs, XX elevators, etc.). Therefore, if you know the MAC address, you can know where the access point is located.

Table 11(b) shows an example of a conference room location table stored in the conference room provision information DB 492. The location of the conference room 6 is registered in the conference room location table. The conference room location table has items such as conference room name, building, floor, and direction. The conference room name is the name of conference room 6. The ridge, floor, and direction are the same as in Table 11(a). Therefore, if a location is specified, conference rooms 6 near this location can be found.

<<Terminal device>>
FIG. 8 is an example of a functional block diagram showing the functions of the terminal device 60 and the conference room terminal 90 in a block form. The functions of the registration terminal 50 and the electronic device 70 will be explained as necessary.

The terminal device 60 includes a communication section 61a, an operation reception section 61b, a display control section 61c, a chat communication section 62, a text display section 63, an application communication section 64, a server communication section 65, a display control section 66, an application communication section 67, and a terminal. It includes a communication section 68, an information acquisition section 69, a communication section 81, a display control section 82, a reservation request section 83, and an application communication section 84. Each of these functional units included in the terminal device 60 is a function realized by operating one of the configuration categories shown in FIG. It is a means. This program is distributed from a program distribution server or stored in a storage medium. Since the chat application 60a, the conference application 60b, and the reservation application 60c are running on the terminal device 60, the program includes the chat application 60a, the conference application 60b, and the reservation application 60c.

The communication unit 61a transmits and receives various information to and from the conference management server 30 and the reservation management server 20. The operation accepting unit 61b accepts various operations performed by participants on the terminal device 60.

The display control unit 61c interprets screen information of various screens and displays it on the LCD 206. The operation reception unit 61b and the display control unit 61c have, for example, a browser function and can execute a web application. For example, the reservation setting screen received from the reservation management server 20 is displayed, and the operation reception unit 61b receives reservation information set by the reservation person.

The chat communication unit 62 of the chat application 60a sends and receives various information to and from the chat server 10. In this embodiment, the information regarding the reservation of the conference room 6 is received from the chat server 10, and the chat server 10 is notified of whether the reservation of the conference room 6 has been read, whether the conference room 6 will be used or canceled, etc.

The text display section 63 of the chat application 60a displays the text (information regarding the reservation of the conference room 6) sent from the chat server 10. For example, the source of the message is a bot, and the text is displayed as if it were input by the bot.

The application communication unit 64 of the chat application 60a calls the conference application 60b and transmits conference identification information to the conference application 60b. When the chat server 10 notifies information regarding the reservation of the conference room 6, it sends information identifying the conference application 60b to the terminal device 60, so the chat application 60a specifies the conference application 60b to the OS and performs conference identification. Request information notifications. The OS can launch the conference application 60b.

The server communication unit 65 of the conference application 60b communicates with the conference management server 30. A two-dimensional code including conference identification information is acquired from the conference management server 30. The two-dimensional code is used for authentication at check-in. It may also be a several-digit number for authentication.

The display control unit 66 of the conference application 60b displays a two-dimensional code and the like including conference identification information on the LCD 206.

The application communication unit 67 of the conference application 60b acquires various information (conference identification information included in information regarding reservation of the conference room 6, etc.) from the chat application 60a via the OS.

The terminal communication unit 68 communicates with the conference room terminal 90 and transmits conference identification information and the like. The terminal communication unit 68 detects the presence of the conference room terminal 90 using short-range wireless communication such as Bluetooth (registered trademark), and upon detecting the conference room terminal 90, transmits conference identification information. Furthermore, a function for displaying a two-dimensional code on the conference room terminal 90 (in the case of checking in using a two-dimensional code) is provided.

The information acquisition unit 69 acquires the start time, end time, automatic cancellation time, check-in status, etc. of each conference room from the conference management server 30 via the server communication unit 65. This is to display a reservation status screen 300 as shown in FIG.

A communication unit 81 of the reservation application 60c communicates with the reservation management server 20. This is to reserve vacant conference rooms, including automatically canceled conference rooms. The reservation request unit 83 uses the information acquired by the application communication unit 84 to reserve a conference room with the reservation management server 20.

The display control unit 82 of the reservation application 60c displays a screen for accepting input of the start time and conference room, a message indicating completion of the reservation, and the like. The application communication unit 84 communicates with the conference application 60b to acquire information necessary for reservation, such as the conference room ID and start time of the automatically canceled conference room.

<<Conference room terminal>>
The conference room terminal 90 includes a server communication section 91 , a terminal device communication section 92 , an operation reception section 93 , a display control section 94 , an electronic device communication section 95 , and a reservation information request section 96 . Each of these functional units included in the conference room terminal 90 is realized by operating one of the configuration categories shown in FIG. or means. This program is distributed from a program distribution server or stored in a storage medium.

The server communication unit 91 communicates with the conference management server 30 using the server URL 993 as the destination. Since the conference room terminal 90 exists in the in-house network, it is difficult for the conference management server 30 to communicate with the conference room terminal 90. For this reason, the server communication unit 91 communicates with the conference management server 30 using communication techniques such as polling (communicating with the conference management server 30 periodically) and WebSocket. If there is no communication from the server communication unit 91, disconnection is registered in the conference room setting information DB 498. The server communication unit 91 may communicate using a communication protocol such as HTTP, and the communication protocol is not particularly limited.

The server communication unit 91 of this embodiment transmits the conference identification information received by the terminal device communication unit 92 from the terminal device 60 or the manually inputted conference identification information to the conference management server 30 at the time of check-in. Additionally, the server communication unit 91 receives control information from the conference management server 30.

The terminal device communication unit 92 communicates with the terminal device 60 using short-range wireless communication such as Bluetooth (registered trademark) and NFC. In this embodiment, conference identification information and the like are received.

Electronic device communication section 95 communicates with electronic device 70 . In this embodiment, the control information received by the server communication unit 91 is transmitted to the electronic device 70.

The display control unit 94 displays a screen generated by the terminal application 90a on the display 718. This screen is a standby screen where check-in, check-out, etc. can be performed. The operation reception unit 93 accepts various operations on the conference room terminal 90.

The reservation information requesting section 96 repeatedly transmits the conference room ID and the authentication key to the conference management server 30 via the server communication section 91 at regular timings for acquiring reservation information. In response to this, the reservation information request section 96 obtains reservation information via the server communication section 91. Reservation information only needs to be acquired when there is a change. The timing is every few seconds to every few minutes. The shorter the cycle, the earlier the reservation information can be updated, but the communication load will also be higher, so it is determined by taking both into consideration. In this embodiment, it is set to 30 seconds, for example. Further, it is possible to receive at least conference management information (reservation information) for the conference room 6 on that day through the server communication unit 91 .

A situation in which the reservation information requesting unit 96 cannot request reservation information from the conference management server 30 may result in a deterioration of the communication environment. For example, there may be interference with radio waves, a wireless LAN access point may be out of order, or the power may be turned off. The communication environment is also likely to deteriorate in the event of a power outage. Furthermore, if the conference room terminal 90 has a hardware failure, communication may become difficult. Further, if the terminal application is not activated or is running in the background, the reservation information requesting unit 96 does not request reservation information. In either case, the conference management server 30 detects a communication undetected state that sets the state of the conference room terminal 90 to "disconnected."

Further, the conference room terminal 90 has a storage section 99. The storage unit 99 is realized by the ROM 702, EEPROM 704, etc. in FIG. The storage unit 99 stores a conference room ID 991, an authentication key 992, a server URL 993, a conference room name 994, and an IP address 995 of the electronic device 70. The conference room ID 991, authentication key 992, server URL 993, and conference room name 994 are stored by the initial settings of the conference room terminal 90. Using the conference room ID 991, authentication key 992, and server URL 993, the conference room terminal 90 can communicate with the conference management server 30 and acquire reservation information.

<Standby screen displayed by conference room terminal>
For comparison, a standby screen displayed by the conference room terminal 90 will be described. FIG. 9 is an example of a sequence diagram illustrating the process from reserving a conference room to displaying the standby screen.

S1: The reservation person operates the terminal device 60 to connect to the reservation management server 20, and receives authentication using the user information DB 292. If the authentication is successful, the start time, end time, conference room, conference name, etc. of the conference are set on a predetermined web page or a dedicated application, and the conference room is reserved. The communication unit 61a of the terminal device 60 transmits this reservation information to the reservation management server 20.

S1.1: The communication unit 21 of the reservation management server 20 receives the reservation information, and the reservation information management unit 22 registers the reservation information in the reservation information DB 291.

S1.2: When there is a change in the reservation information, the communication unit 21 of the reservation management server 20 notifies the conference management server 30 of the change along with the reservation person's domain and the like.

S1.3: The reservation information acquisition unit 33 of the conference management server 30 requests reservation information from the reservation management server 20 by specifying a domain that identifies the customer, either periodically or in response to a notification from the reservation management server 20 ( License information of the conference management server 30 is also included for authentication).

S1.4: The communication unit 21 of the reservation management server 20 receives the request and transmits the reservation information of the reservation person having the specified domain, which the reservation information management unit 22 has acquired from the reservation information DB 291, to the conference management server 30. do.

S1.5: The reservation information acquisition unit 33 of the conference management server 30 can acquire reservation information and register it in the conference management information DB 493. The reservation information acquisition unit 33 issues conference identification information for each acquired reservation information and registers it in the conference identification information DB 494.

S1.6: The conference information notification unit 37 of the conference management server 30 detects the reservation person or participant from the correspondence information DB 491, specifies information that specifies the group in the chat server 10, and sends the reservation to the chat server 10 to complete the reservation. (including meeting identification information). As a result, the text processing unit 12 of the chat server 10 broadcasts reservation information such as meeting identification information to the group (workspace channel) specified by the group specifying information. Note that the notification may be made by e-mail. When checking in to the conference room terminal 90, the reservation holder or participant inputs conference identification information as necessary.

S2: The reservation information requesting unit 96 of the conference room terminal 90 specifies the authentication key 992 and the conference room ID 991 and requests reservation information from the conference management server 30 using the server URL 993 as the destination, periodically or in response to an operation by a participant. do. The reception unit 31b of the conference management server 30 receives the request, and if the combination of authentication key and conference room ID is registered in the conference room setting information DB 498, reservation information (conference management information) specified by the conference room ID is received. is acquired from the conference management information DB 493 and transmitted to the conference room terminal 90.

S3: The server communication unit 91 of the conference room terminal 90 receives the reservation information, and the display control unit 94 displays the reservation information on the standby screen. Examples of standby screens are shown in FIGS. 10 to 12.

<Standby screen>
The reservation information displayed by the conference room terminal 90 will be explained using FIGS. 10 to 12.
FIG. 10 shows an example of a standby screen I displayed by the conference room terminal 90 when the conference room is currently vacant. The standby screen I in FIG. 10 includes a current status field 561, a conference room name field 562, a conference name field 563, a start time field 564, an end time field 565, a start use button 566, and a subsequent reservation field 567. etc. are displayed.

The current status column 561 indicates the current status of the conference room. The display control unit 94 of the conference room terminal 90 displays the status of reservation information in the current status column 561. If there is no reservation information reserved at the current time, the display control unit 94 displays the current status column 561 as either "vacant" (until check-in for the next reservation becomes possible) or "waiting for entry" (until the next reservation becomes available). (after the reservation is available for check-in).

In the conference room name column 562, conference room names stored in the storage section 99 are displayed. The conference name column 563 displays the conference name included in the reservation information. The display control unit 94 displays "No reservation" in the conference name column 563 until check-in for the next reservation becomes possible.

The start time column 564 and the end time column 565 display the start time and end time included in the reservation information, respectively. In FIG. 10, the standby screen is for a time slot when there is no reservation, so the end time of the last conference is displayed in the start time column 564, and the start time of the next conference is displayed in the end time column 565.

The subsequent reservation column 567 displays the start time and end time of each conference scheduled for later than the current one, according to the reservation information. The start use button 566 is displayed when the current status column 561 is "vacant". Even if the conference room has not been reserved, the user can start using the conference room by pressing the start use button 566. Pressing this button is transmitted to the reservation management server 20 via the conference management server 30, reservation information is generated, and the status of the conference room is changed. The change in status is also reflected on the standby screen when the conference room terminal 90 receives the reservation information.

FIG. 11 shows an example of a standby screen II displayed by the conference room terminal 90 when the conference room is currently vacant but the next conference start time is within a predetermined time. On the standby screen II of FIG. 11, "Waiting for room entry" is displayed in the current status column 561, and an entry button 568 is displayed. Waiting for entry corresponds to waiting for check-in. Further, the person making the reservation is displayed in the person making the reservation column 570. When the status of the reservation information changes to "waiting for check-in" or the like, the display control unit 94 displays "waiting for entry" and displays the entry button 568.

For example, 10 minutes before the start time, the status changes to "Waiting for check-in" or the like, so the display control unit 94 displays "Waiting for entry" and permits check-in. In other words, those who made reservations will be able to check-in. Further, if the conference room terminal 90 does not send a check-in request by a predetermined time, the task execution unit 40 of the conference management server 30 automatically cancels the request if no check-in is detected. Therefore, the display control unit 94 automatically counts down the time 569 until cancellation and displays it in the current status column 561. The automatic cancellation time is, for example, 10 minutes after the start time.

The room entry button 568 is a button for the user to check in. By pressing this button, the person making the reservation can enter conference identification information.

The reservation person information is displayed in the reservation person name field 570. This reservation person may be an account included in the reservation information, or the name or nickname of the reservation person may be transmitted from the conference management server 30. Further, a photo of the person making the reservation or a character representing the person making the reservation may be displayed.

FIG. 12 shows an example of a standby screen III displayed by the conference room terminal 90 when the conference room is currently in use. In the standby screen III of FIG. 12, "in use" is displayed in the current status column 561, and an exit button 571 is displayed. When the reservation person inputs the conference identification information or holds the terminal device 60 over the conference management server 30 and allows check-in, the status of the conference management information DB 493 becomes "checked in". When the conference room terminal 90 receives the reservation information, the display control unit 94 detects that the status has changed to checked-in. The display control unit 94 displays "in use" in the current status column 561 and displays the exit button 571 until the user checks out. Further, the display control unit 94 counts down the time until the end time and displays it in the current status column 561. The exit button 571 is a button for the reservation holder to check out. When this button is pressed, a check-out request is sent to the conference management server 30, and the check-in management unit 38 of the conference management server 30 updates the status of the conference management information DB 493 to "checked out". When the conference room terminal 90 receives the reservation information, the display control unit 94 displays "vacant room" or "waiting for entry" in the current status column 561.

<Dynamically obtain conference room ID from conference room transmitter>
Next, two methods for the user's terminal device 60 to search for a nearby conference room will be explained using FIGS. 13 and 14.

FIG. 13 is a diagram illustrating a process or operation in which the terminal device 60 acquires the conference room ID from the transmitters installed in the conference rooms A to F. In FIG. 13, six conference rooms A to F are provided on an office floor.

Inside or near the conference room A to conference room F (for example, at the entrance), facility information, including at least information for identifying the facility, is provided using BLE (Bluetooth (registered trademark) Low Energy), Wi-Fi, etc. Transmitters 1A to 1F are provided that perform broadcast transmission continuously or intermittently based on a short-range wireless communication protocol. The transmitters 1A to 1F may be the conference room terminal 90, or may be different terminals from the conference room terminal 90.

As the facility information, for example, a conference room ID, conference room name, reservation status, etc. can be used. Additionally, information that can identify the "name" of the facility can be used. Further, a number that allows the conference management server 30 to uniquely identify a facility such as a conference room, or a combination of a number that identifies a building and a unique conference room identification number within the building can be used.

Based on the conference application 60b installed in advance, the user's terminal device 60 receives facility information whose radio wave intensity is equal to or higher than a predetermined threshold among the radio waves from each of the transmitters 1A to 1F received at the current location. , a list is displayed on the display unit of the terminal device 60.

The conference management server 30 has a conference management information DB 493 in which reservation information for each conference room A to F is stored. When the conference management server 30 receives a request from the user's terminal device 60 to check the reservation status of a desired conference room, the conference management server 30 returns the requested conference room reservation information to the user's terminal device 60.

The user looks at the reservation status of the desired conference room returned from the conference management server 30 and selects an available time slot. The user operates the pre-installed reservation application 60c to select a desired conference room based on the facility information displayed in a list on the display section of the terminal device 60, for example, through WI-FI (registered trademark) communication, etc. Through network communication, the reservation status of the desired conference room is confirmed with a reservation management server 20 provided in a predetermined network such as a LAN (Local Area Network).

When the reservation management server 20 receives a reservation from a user, it accepts the reservation. This completes the reservation for use of the desired conference room in the desired time slot.

According to such a system, facility information transmitted from a location close to the user's current location is received through short-range wireless communication, so that facility information such as a conference room that is located near the user's current location is targeted. You can narrow down your search and make reservations for use.

<Identification of conference rooms using a table that associates access point MAC addresses with conference rooms>
FIG. 14 is a diagram illustrating an operation when the conference management server 30 proposes a conference room suitable for the reservation person's current location.
(1) First, the reservation person 201 exists on a certain floor of a certain building in a certain direction. The reservation person 201 operates the terminal device 60 to communicate with the conference management server 30 . There is a wireless LAN access point 71 near the reservation person 201, and the terminal device 60 communicates with the conference management server 30 via this access point 71.
(2) The terminal device 60 transmits the MAC address of the access point 71 to the conference management server 30.
(3) The resource determining unit 43 of the conference management server 30:
I. Estimate the current location 5 of the reservation person 201 by referring to the access point table of Table 11(a) in which the location (building, floor, direction) of the access point 71 is associated with the MAC address.
II. Next, referring to the conference room location table in Table 11(b) in which conference room locations are registered, a conference room 6 near the reservation person's current location is determined and transmitted to the terminal device 60.

Since this conference room 6 is a conference room 6 near the access point 71, it is also a nearby conference room 6 when viewed from the reservation person's current location. Therefore, the conference management server 30 of this embodiment can suggest a conference room 6 close to the current location 5 of the reservation person 201.

<Operating procedure>
Next, the process or operation in which the user displays the reservation status screen 300 will be described using FIG. 15. FIG. 15 is an example of a sequence diagram illustrating a process or operation in which the terminal device displays the reservation status screen 300.

S1: The reservation information acquisition unit 33 of the conference management server 30 requests reservation information from the reservation management server 20 by specifying a domain that identifies the customer, periodically or in response to a notification from the reservation management server 20 (authentication license information for the conference management server 30 is also included).

S2: The communication unit 21 of the reservation management server 20 receives the request and transmits to the conference management server 30 the reservation information of the reservation person having the specified domain, which the reservation information management unit 22 has acquired from the reservation information DB 291.

S3: The reservation information acquisition unit 33 of the conference management server 30 acquires reservation information and registers it in the conference management information DB 493. The reservation information acquisition unit 33 issues conference identification information for each acquired reservation information and registers it in the conference identification information DB 494.

S4: Meanwhile, the user operates the terminal device 60 to start the conference application 60b.

S5: The user causes the terminal device 60 to obtain information for identifying a nearby conference room, such as a conference room ID, using the method described in FIG. 13 or 14, and the terminal communication unit 68 of the terminal device 60 identifies the conference room. The communication unit 81 obtains information specifying the conference room from the conference management server 30. This embodiment will be described assuming that a conference room ID has been acquired. Note that in FIG. 15, for convenience of drawing, the terminal device 60 communicates with the conference room terminal 90, but it may be an access point or may communicate with a device other than the conference room terminal.

S6: The server communication unit 65 of the launched conference application connects to the conference management server 30 using the preset URL of the conference management server 30 as the destination.

S7: The information acquisition unit 69 sends information necessary for displaying the reservation status screen 300 (start time, end time, automatic cancellation time, check-in status, etc.) to the conference management server 30 via the server communication unit 65. request. At the time of the request, the information acquisition unit 69 can specify the conference room ID specified in step S5. However, information etc. on all conference rooms may be requested without narrowing down the conference rooms. The user may request the terminal device 60 for information on only the conference rooms registered by the user (the user selects a conference room from all conference rooms and saves the conference room ID in advance).

S8: Thereby, the communication unit 31 of the conference management server 30 receives the request, and the information providing unit 41 transmits the start time and end time to the terminal device 60 for each conference room.

S9: Similarly, the information providing unit 41 transmits the automatic cancellation time to the terminal device 60. Note that the automatic cancellation time may be common to all conference rooms, but if it differs for each conference room, it will be sent for each conference room. Further, the information providing unit 41 may transmit the remaining time until automatic cancellation calculated from the start time and the automatic cancellation time to the terminal device 60.

S10: The information providing unit 41 transmits the check-in status (status) for each conference room to the terminal device 60.

S11: The display control unit 66 of the conference application displays the reservation status screen 300 shown in FIG. 3 on the display 506. The display control unit 66 continues to display the remaining time until automatic cancellation while updating it using its own RTC (Real Time Clock) (for example, it is preferably in seconds, but may also be in minutes). Alternatively, the terminal device 60 may repeatedly acquire the remaining time until automatic cancellation from the conference management server 30. Note that the screen may be constructed by the terminal device 60, or by the conference management server 30 if the terminal device 60 uses a browser function.

S12: The user can check the reservation status by viewing the reservation status screen 300. Since the terminal device 60 repeats steps S8 to S10 regularly (or irregularly), it can obtain the latest check-in status. Further, based on the check-in status (status), the display control unit 66 does not display the remaining time until automatic cancellation in the conference room where the reservation person checked in or the conference room where the reservation person was automatically checked out. In these cases, the display control unit 66 displays information such as the end time of the meeting and the fact that the room is vacant, as shown in FIG.

<Reservation status screen>
With the above processing, the reservation status screen shown in FIG. 3 is displayed. The reservation status screen 300 in FIG. 3 will be explained. The reservation status screen 300 has the following items for each conference room (each resource): resource 301, usage status 302, remaining time until automatic cancellation 303, and next reservation start time 304.
- Resource 301...The name of the conference room is displayed.
- Usage status 302: The current usage status of the conference room is displayed based on the status. For example, a room waiting to enter (waiting for check-in), in use (checked in), or vacant is displayed.
- Remaining time until automatic cancellation 303...If you are waiting to enter the room, the number of minutes (seconds) until automatic cancellation is displayed. For example, it is "start time + automatic cancellation time (for example, 15 minutes) - current time". If it is in use, the end time will be displayed. If the room is vacant, "Vacant" will be displayed.
- Start time of next reservation 304...The start time of the next reservation is displayed relative to the current time.

For example, if the "remaining time until automatic cancellation" is less than 5 minutes (less than a certain amount of time), it is preferable that the display control unit 66 of the conference application 60b displays the remaining time with emphasis in red or the like. . It becomes possible to assist in determining whether to use a resource (conference room) after waiting for automatic cancellation. In addition to red letters, you may use large letters, blinking, etc. to cooperate.

Further, the conference room name in the resource item is a link button that starts the reservation application 60c. When a conference room name is pressed when the usage status is vacant, the OS starts the reservation application 60c and notifies the reservation application 60c of the conference room ID associated with the conference room name. . This allows the user to reserve a conference room after automatic cancellation without having to input the conference room name. The start time may be the current time, and the end time may be fixed, for example, from 30 minutes to 1 hour. However, it would be nice if the user could edit these. Note that if the conference room name is pressed when the usage status is not vacant, the conference application 60b may display an error message indicating that reservations cannot be made yet. Instead of using the conference room name as a link to the reservation application 60c, a start button for the reservation application 60c may be displayed.

In this way, by displaying the remaining time until automatic cancellation, the user can know which conference room can be used the earliest. For example, the conference room terminal 90 can also display the remaining time until automatic cancellation, but the user must visit each conference room one by one. In this embodiment, the remaining time until automatic cancellation of a plurality of (nearby or all) conference rooms can be displayed in a list, thereby improving convenience.

In addition, in FIG. 3, the conference room names are sorted, but the display may be sorted by the remaining time until automatic cancellation. In this case, the terminal device 60 displays the shorter remaining time until automatic cancellation at a higher rank. Further, the time until automatic cancellation may be displayed on the reservation list screen 310 in FIG. 2(a). For example, the remaining time until automatic cancellation is displayed over the reserved time slot. By doing this, you can visually see the length of the reserved time slot, so you can choose a reservation that has the shortest remaining time before automatic cancellation, from among the reservations that allow you to secure the meeting time you need.

<Reservation processing or operation>
The reservation processing or operation when the reservation application 60c is started will be described using FIG. 16. FIG. 16 is an example of a sequence diagram illustrating a procedure in which the reservation application 60c of the terminal device 60 reserves a conference room in the reservation management server 20.

S21: As described above, when the conference room name is pressed, the reservation application 60c is started. The reservation application 60c acquires at least the conference room ID from the conference application. Any information possessed by the conference application can be acquired. A browser that displays the Web application of the reservation management server 20 instead of the reservation application 60c may be started. In this case, the URL of the reservation management server 20 is notified from the conference application.

S22: When the user inputs authentication information such as a user ID and password and presses a login button, the operation reception unit 61b accepts the request, and the communication unit 81 transmits a login request together with the authentication information to the reservation management server 20. The communication unit 21 of the reservation management server 20 receives the authentication information and authenticates the user based on the authentication information. Here, it is assumed that the authentication was successful.

S23: If the authentication is successful, the display control unit 66 of the reservation application 60c displays the conference room name, start time (current time), and end time received from the conference application. The end time may be a default value (30 minutes to 1 hour, etc.), but it is displayed so that it does not exceed the start time of the next reservation. In addition, by displaying the start time of the next reservation, it becomes easier for the user to determine until what time the reservation can be made. The user edits the conference room name, start time, and end time as necessary, and performs the reservation execution operation. The operation reception unit 61b receives the operation, and the communication unit 81 transmits the conference room name (conference room ID), start time, and end time to the reservation management server 20.

This allows the user to reserve a conference room that has been automatically canceled. You can reserve any vacant conference room, not just automatically canceled conference rooms.

<Main effects>
As explained above, the resource reservation system 100 of this embodiment provides the remaining time until automatic cancellation, so the user has the possibility of being able to use each conference room even before the conference room is automatically canceled. This makes it possible to reserve a conference room by waiting for the remaining time until automatic cancellation. Therefore, it becomes easier to use resources effectively. Furthermore, it is possible to eliminate the task of visually checking the usage status of resources (conference rooms), thereby improving usability for the user.

In this embodiment, a resource reservation system 100 that allows a user to reserve a conference room from a conference application 60b on a reservation status screen 300 will be described.

This embodiment will be described with reference to the hardware configuration diagrams shown in FIGS. 5 to 6 and the functional block diagrams shown in FIGS. 7 and 8 described in the first embodiment.

<Reservation status screen>
FIG. 17 shows an example of a reservation status screen according to this embodiment. The reservation status screen 300 in FIG. 17 includes items such as a usage status 311, detailed information 312, a reservation person's name 313, a message 314, and a button field 315. The reservation status screen 300 in FIG. 17 has a different design from that in FIG. 3, mainly in that it includes a button column 315.
Usage status 311...Similar to usage status 302 in FIG. 3.
Detailed information 312...The conference room name, conference name, start time and end time are displayed. Both are included in the reservation information managed by the conference management server 30.
Reservation person name 313...The reservation person name is displayed. It is included in the reservation information managed by the conference management server 30.
Message 314: The remaining time until automatic cancellation and the start time of the next reservation are displayed.
Button column 315...A use now button 316 is displayed. The use now button 316 is a button for the user to reserve a conference room without using the reservation application 60c. In the waiting state, the use now button 316 is not displayed, but in response to automatic cancellation being executed, the room is updated to a vacant room and the use now button 316 is displayed. If it is in use, the use now button 316 is not displayed because the next reservation is made. For vacant rooms, a use now button 316 is displayed.

Therefore, the user can view the conference room name and the start time of the next reservation, press the use now button 316, and reserve the conference room. Since the start time of the reservation may be the current time and the end time is a predetermined time (for example, 30 minutes), the user can reserve the conference room simply by pressing the use now button 316. However, the conference application 60b may display a screen when the use now button 316 is pressed and accept input of the current time and end time.

<Reservation processing or operation>
The reservation processing or operation when the use now button is pressed will be described using FIG. 18. FIG. 18 is an example of a sequence diagram illustrating a procedure in which the conference application 60b of the terminal device 60 reserves a conference room in the conference management server 30.

S31: As described above, the user presses the use now button 316. The operation reception unit 61b of the terminal device 60 accepts the operation, and the server communication unit 65 of the conference application 60b transmits the conference room ID to the conference management server 30 along with a notification that the use now button 316 has been pressed.

S32: The communication unit 31 of the conference management server 30 receives the fact that the use now button 316 has been pressed and the conference room ID, and the reservation unit 42 makes the reservation together with the conference room ID, start time, and end time via the communication unit 31. Send the request to the reservation management server 20. Note that the start time may be the current time, the end time may be the start time + 30 minutes, etc. The conference management server 30 holds in advance license information (a token indicating that it is a conference management server) for making a reservation from the reservation management server 20, and is authorized to make a reservation. Therefore, in this embodiment, the reservation person is the conference management server.

S33: The reservation management server 20 reserves a conference room. The reservation information after the reservation is sent to the conference management server 30 and is also reflected on the reservation status screen 300 displayed by the terminal device 60.

<Main effects>
In this way, the resource reservation system 100 of this embodiment has the effects of the first embodiment and also provides the use now button, thereby allowing the user to make a reservation with fewer man-hours.

In this embodiment, a resource reservation system 100 that allows a user to make a waitlist reservation from a conference application on a reservation status screen 300 will be described.

The present embodiment will be described on the assumption that the hardware configuration diagrams shown in FIGS. 5 and 6 and the functional block diagrams shown in FIGS. 7 and 8 described in the above-described first embodiment can be used.

<Reservation status screen>
FIG. 19 shows an example of the reservation status screen 300 of this embodiment. Note that in the explanation of FIG. 19, differences from FIG. 17 will be mainly explained. The reservation status screen 300 in FIG. 19 displays not only a use now button 316 in a button column 315, but also a waitlist reservation button 318 and a next time use button 319, as well as an item for a detailed reservation button 317. have.
- The waiting-to-cancel reservation button 318 displays the usage status as waiting for entry. The waitlist reservation is a button that allows the user to reserve the use of a conference room in the event that the reservation is automatically cancelled, even before the automatic cancellation.
- The next time button 319 is displayed when there are no reservations for the time after the current meeting (14:00 to 16:00 in the example of conference room B). A user can make a reservation for a predetermined time (for example, 30 minutes; therefore, from 14:00 to 14:30) with the authority of the conference management server 30. By pressing this button, a detailed reservation button 317 screen (conference room name and next start time already entered) may be activated, which will be described below.
・Embedded in the detailed reservation button 317 is a link for opening a detailed reservation input screen for each conference room. The conference application 60b may use the conference room ID of the selected conference room to automatically display the selected conference room and the most recent time with no reservations. An example of the screen will be explained with reference to FIG. As for how to display the screen,
(i) Open the reservation management server's web application in a browser,
(ii) The reservation application 60c for making reservations on the reservation management server starts and displays a reservation screen;
and so on.

Note that if the user has been successfully authenticated to the reservation management server 20, the terminal device 60 directly opens the reservation screen, but if the authentication has not been successful, the authentication screen is opened. Further, the link may be a button embedded in the usage status, conference room name, or the like.

FIG. 20 is an example of a diagram illustrating the transition between the waitlist reservation button 318 and the next time use button 319. FIG. 20(a) shows an example of the transition of the wait-for-cancellation reservation button 318.
A. When the waitlist reservation button 318 is pressed, the terminal displays a reservation cancel button 318-2 that displays information such as "cancellation of waitlist reservation." When the reservation cancellation button 318-2 is pressed, the cancellation waiting list is canceled.
B. On other terminal devices 60, information "waiting for cancellation" is displayed. The waitlist reservation button 318 may not be displayed on other terminal devices 60.

Furthermore, after the reservation cancellation button 318-2 is displayed, the following occurs.
C. If the reservation is automatically canceled, the information "Reserved" will be displayed.
D. If the reservation is not automatically canceled and the previous user checks in, the information "Reservation could not be made" will be displayed.

The conference management server 30 displays a message such as C or D only on the terminal device 60 that has pressed the cancellation reservation button 318. In other terminal devices 60, the usage status changes to "in use" by updating the reservation status screen, so the button 319 switches to the button 319 for use at the next time.

The method for the conference management server 30 to identify the terminal device 60 that pressed the cancellation waiting reservation button 318 is to transfer the application ID, user ID, authentication ticket, etc. to the terminal device 60 when the cancellation waiting reservation button 318 was pressed. There is a way to exchange it. The information providing unit 41 of the conference management server 30 selects the reservation cancellation button 318-2 or "cancellation waiting list" depending on whether or not to send the screen information of the reservation status screen to the terminal device 60 that pressed the cancellation reservation reservation button 318. Control which of the following is displayed.
- The transition of A may be performed within the terminal device 60.
- In transition B, the information providing unit 41 of the conference management server 30 determines that the terminal device 60 is not the one that pressed the cancellation waiting reservation button 318, and displays "Cancellation waiting list". If another terminal device 60 is displaying the reservation status screen 300, push transmission from the conference management server 30 to the other terminal device 60 is preferable. Alternatively, "waiting for cancellation" may be displayed in response to a user operation or a request from a conference application. If the other terminal device 60 is not displaying the reservation status screen 300, when the other terminal device 60 communicates with the conference management server 30 to display the reservation status screen 300, the conference management server 30 sends the other terminal device 60 ``Waiting list for cancellation'' is displayed.
- In transitions C and D, the information providing unit 41 of the conference management server 30 determines that the terminal device 60 is the one that pressed the waitlist reservation button 318, and displays "Reserved" or "Reservation not possible". . When the terminal device 60 is displaying the reservation status screen 300, push transmission from the conference management server 30 to the terminal device 60 is preferable. Alternatively, "Reserved" or "Reservation not possible" may be displayed in response to a user operation or a request from a conference application. If the terminal device 60 is not displaying the reservation status screen 300, when the terminal device 60 communicates with the conference management server 30 to display the reservation status screen 300, the conference management server 30 sends messages to the terminal device 60 such as “Reserved” and “Reserved”. The message "Reservation could not be made" is displayed.

FIG. 20(b) shows an example of the transition of the button 319 to be used at the next time.
E. When the button 319 to be used for the next time is pressed, the own terminal displays a reservation cancellation button 319-2 on which information "cancellation of reservation for the next time" is displayed. The transition of E may be the same as that of A. When the reservation cancellation button 319-2 is pressed, the reservation is canceled.
F. When the button 319 to be used next time is pressed, the other terminal device 60 displays the information "Next reservation available". The transition of F may be the same as that of B.

Note that instead of the button transition as shown in FIG. 20, the terminal device 60 may display a list screen of conference room reservation information as shown in FIG. 2(a).

FIG. 21 shows an example of a detailed reservation screen 330 that is displayed after the link of the detailed reservation button 317 is pressed. The detailed reservation screen 330 is a reception screen that accepts the conference name, conference room name, and the start time and end time of resource usage. When the detailed reservation button 317 is pressed, a detailed reservation screen 330 in FIG. 21 is displayed. The detailed reservation screen 330 has a conference name field 331, a conference room name field 332, a start time field 333, and an end time field 334. The user can enter an arbitrary conference name in the conference name column 331. The conference room name column 332 displays the conference room name displayed on the reservation status screen 300. The end time of the current conference is automatically entered in the start time column 333. For example, the start time + 30 minutes is automatically entered in the end time column 334.

The user can make the reservation as is, or edit the start time and end time before making the reservation.

<Reservation processing or operation>
The reservation process or operation when the waitlist reservation button 318 is pressed will be described using FIG. 22. FIG. 22 is an example of a sequence diagram illustrating a procedure for the conference application of the terminal device 60 to reserve a conference room in the conference management server 30 when the waitlist reservation button 318 is pressed.

S41: The user presses the waiting list reservation button 318 for conference room A on the reservation status screen 300. The operation accepting unit 61b accepts the operation (transition A in FIG. 20). This specifies the conference room ID.

S42: The server communication unit 65 of the conference application specifies the conference room ID and transmits a cancellation waiting reservation request to the conference management server 30.

S43: The communication unit 31 of the conference management server 30 receives the waiting list reservation request, and the reservation unit 42 registers the waiting list reservation in association with the reservation ID. Therefore, the user can reserve a conference room even before automatic cancellation.

Next, a case will be described in which the status of the reservation information for a conference room that is on the waiting list changes to checked-in without being automatically canceled. In this case, the reservation unit 42 deletes the cancellation waiting reservation information.

S44: The conference room terminal 90 of conference room A accepts check-in by inputting the conference identification number. The server communication unit 91 of the conference room terminal 90 transmits an entry (check-in request) to the conference management server 30 along with the conference room ID and conference identification information.

S45: The check-in management unit 38 of the conference management server 30 permits check-in when the combination of conference identification information and conference room ID is registered in the conference identification information DB 494. Change the status of the conference management information DB 493 to "checked in".

S46: Since the reservation was not automatically canceled, the reservation unit 42 deletes the reservation waiting for cancellation in step S43 specified by the reservation ID in the conference management information DB 493.

S47: The communication unit 31 of the conference management server 30 displays the failure of the waiting list reservation on the terminal device 60 (transition D in FIG. 20).

S48: The conference management server 30 may further notify the cancellation waitlist failure using e-mail or the chat server 10. When using the chat server 10, the conference information notification unit 37 refers to the association information DB 491 and transmits a failure message to the chat server 10 along with information specifying the group to be notified. Alternatively, when requesting a waitlist reservation, an e-mail address or the like saved in the conference application may be sent to the information processing device together with the conference room ID.

Next, a case will be described in which a reservation for a conference room that has been placed on a waiting list is automatically canceled.

S49: The task execution unit 40 of the conference management server 30 executes the task and cancels the reservation when the automatic cancellation time comes (after a predetermined period of time has passed from the start time). The canceled reservation is identified by the reservation ID, and the check-in management unit 38 deletes the reservation information in the conference management information DB or sets the status to cancel.

S50: Furthermore, it is detected that there is a waiting list reservation associated with the reservation ID of the canceled reservation, and the reservation unit 42 executes the waiting list reservation. That is, the reservation unit 42 specifies the conference room ID, start time (end time of the canceled reservation), and end time (default value such as 30 minutes, for example) and transmits them to the reservation management server 20. Note that instead of executing the automatic cancellation task, the person making the reservation for the reservation to be canceled may be changed to the conference management server 30.

S51: The communication unit 21 of the reservation management server transmits reservation success to the conference management server 30. The communication unit 31 of the conference management server 30 receives the reservation success.

S52: The reservation unit 42 of the conference management server 30 notifies the terminal device 60 of the success of the waiting list reservation via the communication unit 31 (transition of C in FIG. 20). In this case as well, either or both of e-mail and chat server 10 may be used.

S53: The reservation information acquisition unit 33 of the conference management server 30 specifies the domain that identifies the customer from the reservation management server 20 and requests reservation information periodically or in response to a notification from the reservation management server 20 (for authentication). license information for the conference management server 30 is also included).

S54: The communication unit 21 of the reservation management server 20 receives the request and transmits the reservation information of the reservation person having the specified domain, which the reservation information management unit 22 has acquired from the reservation information DB 291, to the conference management server 30.

S55: The communication unit 31 of the conference management server 30 transmits the start time, end time, automatic cancellation time, check-in status, etc. to the terminal device 60. This is to update the reservation status screen 300. However, if the terminal device 60 is not displaying the reservation status screen 300, there is no need to transmit it.

S56: The server communication unit 65 of the terminal device 60 receives the start time, end time, automatic cancellation time, check-in status, etc., and the display control unit 66 reflects the information on the reservation status screen 300. The usage status item will be in use, and the button field 315 will be "use next time".

<Summary>
As described above, in addition to the effects of the first embodiment, the resource reservation system 100 of the present embodiment provides the waiting list reservation button 318, so that the user can reserve a conference room even before automatic cancellation.

<Example of reservation status screen on centralized terminal>
Although the reservation status screen 300 displayed by the individual terminal device 60 has been described in FIG. 3, FIG. 17, and FIG. 19, a central terminal may be provided in common for several conference rooms. The reservation status screen 300 displayed by the centralized terminal will be explained.

FIG. 23 shows an example of a reservation status screen 300 displayed by the centralized terminal. In the explanation of FIG. 23, differences from FIG. 17 will be mainly explained. The reservation status screen 300 in FIG. 23 is used not only by those who have not made a reservation, but also by those who have made a reservation and those who have checked in, so all buttons, including not only the entry button (check-in) but also the exit button (check-out), are used. indicate.
- If the usage status is Waiting to enter, an enter button 321 is displayed. This is because the person making the reservation also operates it.
- If the usage status is in use, an extension button 322 and an exit button 323 are displayed. This is because the reservation holder who has already checked in wants to extend the reservation or check out. If extension is not possible, the extension button will not be displayed.

The information providing unit 41 of the conference management server 30 determines whether the terminal device 60 is an individual terminal device or a centralized terminal according to the application ID and terminal identification information, and if it is a centralized terminal, displays all buttons and displays the button for the individual terminal device 60. If so, a reservation status screen 300 as shown in FIG. 17 is displayed on the terminal device 60.

<Main effects>
In this way, the resource reservation system 100 of the present embodiment has the effects of the first embodiment, and also allows the user to make a waitlist reservation from the conference application, so that the user can make a reservation with fewer man-hours.

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

For example, a plurality of conference management servers 30 may exist, or the functions of the conference management server 30 may be distributed among a plurality of servers. Further, the reservation management server 20 and the conference management server 30 may be integrated.

Additionally, the devices described in the Examples are merely illustrative of one of multiple computing environments for implementing the embodiments disclosed herein. In some embodiments, conference management server 30 includes multiple computing devices, such as a server cluster. The plurality of computing devices are configured to communicate with each other via any type of communication link, including a network, shared memory, etc., to perform the processes disclosed herein.

Furthermore, the conference management server 30 can be configured to share the disclosed processing steps, eg, FIGS. 9, 15, 16, 18, and 22, in various combinations. For example, a process executed by a predetermined unit may be executed by a plurality of information processing devices included in the conference management server 30. Further, the conference management server 30 may be integrated into one server device, or may be divided into multiple devices.

Further, the resource reservation system 100 of this embodiment can also be referred to as a web service. Web services are various services provided by applying Internet-related technology. Examples include conference room rental services and various rental services. A system that uses Web services is called a usage system.

Further, the configuration examples shown in FIGS. 7 and 8 in the above embodiments are divided according to main functions in order to facilitate understanding of the processing of the resource reservation system 100. However, the present invention is not limited by the division method or name of each processing unit. The resource reservation system 100 can also be divided into more processing units depending on the processing content. Furthermore, one processing unit can be divided to include more processing.

Each function of the embodiments described above can be realized by one or more processing circuits. Here, the term "processing circuit" as used herein refers to a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, or a processor designed to execute each function explained above. This includes devices such as ASICs (Application Specific Integrated Circuits), DSPs (digital signal processors), FPGAs (field programmable gate arrays), and conventional circuit modules.

10 chat server 20 reservation management server 30 conference management server 50 registration terminal 60 terminal device 70 electronic device 90 conference room terminal 100 resource reservation system

Japanese Patent Application Publication No. 2016-004511

Claims (13)

A resource reservation system comprising: an information processing device that holds information regarding resource reservation; and a terminal device;
The terminal device is
a display control unit that displays, for each resource, the remaining time until the reservation of the resource is automatically canceled based on information received from the information processing device ;
The display control unit displays, for each of the plurality of resources, a message indicating that the resource is waiting for entry within a predetermined time from the start time of use, that the resource is in use, or that the resource is not being used within a predetermined time from the start time of use. Display one of the vacant rooms,
A resource reservation system characterized by displaying the remaining time until automatic cancellation for the resource waiting for room entry . The information processing device holds information regarding resource reservation,
The display control unit displays the remaining time until automatic cancellation of the resource, using a start time when the use of the resource is started and a time when the resource is automatically canceled, which is transmitted from the information processing device. The resource reservation system according to claim 1, characterized in that: The terminal device is
a terminal communication unit that wirelessly communicates with a terminal installed at the resource or a terminal installed near the resource and acquires identification information of the resource;
an information acquisition unit that specifies the identification information of the resource acquired by the terminal communication unit and receives from the information processing device a start time when the use of the resource is started and a time when the resource is automatically canceled; 3. The resource reservation system according to claim 2, comprising: a communication unit that communicates with the information processing device via an access point, transmits a MAC address of the access point to the information processing device, and obtains identification information of the resource associated with the MAC address;
The method further comprises: an information acquisition unit that specifies identification information of the resource and receives from the information processing device a start time when use of the resource is started and a time when automatic cancellation of the resource is to be performed. The resource reservation system according to claim 2. According to any one of claims 1 to 4, the display control unit displays the remaining time in an emphasized manner when the remaining time until automatic cancellation of the resource becomes less than a certain time. resource reservation system. The resource reservation system according to any one of claims 1 to 5, further comprising an information processing terminal that displays the remaining time until automatic cancellation. The display control unit displays a button for accepting a reservation of the resource from a user for the resource in the vacant room;
The resource reservation according to claim 1 , wherein the terminal device includes a reservation requesting unit that requests the information processing device to reserve the resource together with identification information of the resource when the button is pressed. system. The display control unit displays a button for accepting a cancellation request from a user for the resource waiting to enter the room;
The terminal device includes a reservation requesting unit that requests the information processing device to wait for cancellation along with identification information of the resource when the button is pressed;
The information processing device includes:
If the use of the resource does not start by the automatic cancellation time, either cancel the reservation of the resource that is waiting to fill the room and make a new reservation for the resource, or cancel the reservation of the resource that is waiting to fill the room. The resource reservation system according to claim 1 , characterized in that the resource reservation system is changed to an information processing device. The display control unit displays, for the resource in use, a button that accepts a reservation for the resource at a time after the resource is used;
The terminal device further includes a reservation requesting unit that requests the information processing device to make a reservation for a time after the use of the resource together with identification information of the resource when the button is pressed. 1. The resource reservation system described in 1 . The display control unit displays a detailed reservation button for the resource in the vacant room, the resource waiting for room entry, or the resource in use,
When the detailed reservation button is pressed, displaying a reception screen for the start time and end time of the use of the resource to which the detailed reservation button is associated;
10. The resource reservation system according to claim 7, wherein the reservation requesting unit requests the information processing device to reserve the resource together with the information displayed on the reception screen. having a centralized terminal commonly provided to a plurality of the resources;
The centralized terminal displays, for each resource, either the waiting room, the in use, or the vacant room;
Displaying a button for accepting reservations for the resource from the user for the resource in the vacant room;
Displaying a button for accepting entry from a user for the resource waiting for entry;
11. The resource reservation system according to claim 1 or any one of claims 7 to 10, characterized in that a button is displayed for accepting exit from the resource for the resource in use. A display method performed by a resource reservation system including an information processing device that holds information regarding resource reservations and a terminal device, the method comprising:
The terminal device displays, for each resource, the remaining time until automatic cancellation of the reservation of the resource, based on the information received from the information processing device,
For each of the plurality of resources, the terminal device displays a message indicating that the resource is waiting for entry within a predetermined time from the start time of use, that the resource is in use, or that the resource is not in use within a predetermined time from the start time of use. Shows one that there is no vacancy,
A display method characterized by displaying the remaining time until automatic cancellation for the resource waiting for room entry . An information processing device that retains information regarding resource reservations, the information processing device comprising:
In response to a request from a terminal device, the terminal device transmits information for displaying the remaining time until the reservation of the resource is automatically canceled for each resource to the terminal device,
For each of the plurality of resources, the terminal device displays a message indicating that the resource is waiting for entry within a predetermined time from the start time of use, that the resource is in use, or that the resource is not in use within a predetermined time from the start time of use. Shows one that there is no vacancy,
An information processing device characterized in that the remaining time until automatic cancellation is displayed for the resource waiting to enter the room .

Images