JP2021196652A - Information processor, reservation system and reservation processing method - Google Patents

Abstract

To provide a reservation system capable of preferentially accepting either of a utilization start of a reservation-based resource or a registration of a new reservation.SOLUTION: An information processor 30, for managing the use of a resource under reservation, has a utilization managing section 38 that accepts a utilization start of the resource and a reservation control section 41 that if the utilization managing section does not accept a utilization start of the resource and a first time has elapsed from a utilization-start time of the resource, changes the reservation of the resource to a first status. Before elapsing a second time from a lapse of the first time, processing is preferentially performed on an earlier one of an acceptance of a utilization start of reserving the first status and a registration of a new reservation in an overlapping time zone with the reservation of the first status.SELECTED DRAWING: Figure 2

Description

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

A reservation system for managing reservations for resources such as conference rooms is known. A reservation person such as a person who is planning to participate in a conference can communicate a terminal device with an information processing device such as a reservation management server and reserve resources such as a conference room with a browser operated by the terminal device. An information processing terminal such as a conference room terminal that accepts check-in is installed in the conference room, and when the user starts using the conference room, he / she inputs the start of use to the information processing terminal and ends the use when he / she ends the use. It becomes possible to use it like inputting.

From the user's point of view, it is easier to reserve a conference room, but if the schedule changes and you forget to cancel the unused conference room, the reservation will be empty. Conventionally, a technique for suppressing empty reservation has been devised (see, for example, Patent Document 1). Patent Document 1 discloses a method of preventing an empty reservation by readjusting the reserved meeting schedule from the relationship between the work set as the pre-meeting work and the meeting date.

However, the conventional technique has a problem that it can only accept either the start of use of the resource based on the reservation or the registration of a new reservation. In other words, even if the reservation person does not enter the operation to start using by the start time, deleting the reservation will deprive the reservation person of the right, so a grace period until deletion (for example, check within 10 minutes after the start time). If there is no check-in, automatic cancellation) is often provided. On the other hand, the longer the grace period until the reservation is deleted (10 minutes in the above case), the more difficult it is to reuse the conference room, and as a result, it becomes difficult to reuse it. In this case, only the start of use of the resource can be accepted until 10 minutes have passed from the start time, and after 10 minutes, only the registration of a new reservation can be accepted, and the time that cannot be reused tends to be long.

In view of the above problems, it is an object of the present invention to provide a reservation system capable of preferentially accepting either the start of use of resources based on reservations or the registration of new reservations.

In view of the above problems, the present invention is an information processing device that manages the use of reserved resources, and the usage management unit that accepts the start of use of the resource and the usage management unit accept the start of use of the resource. When the first time elapses from the usage start time of the resource, the reservation control unit for changing the reservation of the resource to the first status is provided, and after the first time elapses. Until the second time elapses, priority is given to the earlier of the acceptance of the start of use of the reservation of the first status and the registration of the new reservation in the time zone overlapping with the reservation of the first status. It is characterized by processing.

It is possible to provide a reservation system that can preferentially accept either the start of use of resources based on reservations or the registration of new reservations.

It is an example of the figure explaining the outline of the overall operation of the reservation system. It is a figure explaining the outline of the operation of the reservation management server and the conference management server when the reservation start time has passed. This is an example of a system configuration diagram of a reservation system. This is an example of the hardware configuration diagram of the conference management server. This is an example of the hardware configuration diagram of the conference room terminal. This is an example of a functional block diagram showing the functions of the reservation management server, the chat server, and the conference management server in a block shape. This is an example of a functional block diagram showing the functions of a terminal device and a conference room terminal in a block shape. It is a figure which shows an example of the cancellation policy setting screen. This is an example of a sequence diagram showing a procedure for the conference room terminal to acquire reservation information. This is an example of a sequence diagram for explaining the temporary deletion and automatic cancellation processing of the reservation information in the conference management server. It is a figure which shows an example of the standby screen when the reservation information of waiting to enter a room is not temporarily deleted. It is a figure which shows an example of the standby screen when the reservation information of waiting to enter a room is temporarily deleted.

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

<Outline of reservation system>
First, the outline of the reservation system will be described with reference to FIG. FIG. 1 is an example of a diagram illustrating an outline of the overall operation of the reservation system 100.

A. The reservation person operates his / her 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 are registered trademarks), etc.), but a conference room owned by an organization such as a company to which the reservation person belongs is registered.

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

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

D. The conference management server 30 reminds the reservation person to hold the conference before the fixed time of the conference start time in the reservation information. As a result, the empty reservation of the conference room is suppressed. Further, the conference management server 30 notifies the user of the invitation code as needed. The person who booked the conference stores the information (meeting identification information) for checking in to the conference room by receiving the reminder 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 to be performed in this conference room. The conference room terminal 90 can display the schedule of the current day or the latest conference and have the participants confirm the schedule. Shortly before the start time of the conference, the person who reserved the conference room goes to the conference room 6 to check in. For example, the conference identification information is input to the conference room terminal 90, or the terminal device 60 is held over the conference identification information (the conference identification information is read, communicated, 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 sends a check-in request (use start notification) to the conference management server 30, if authentication can be performed with the conference identification information, a response to the effect that the check-in has been completed is received from the conference management server 30. The conference room terminal 90 displays that the conference room is being conferenced (in use). If check-in cannot be confirmed by a fixed time with respect to the start time of the conference, the conference management server 30 cancels the reservation of the conference room 6 and transmits the status to that effect to the conference room terminal 90 as the status included in the reservation information. .. 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 in response to a request from the conference management server 30. For example, the power is turned on at the start time and the power is turned off at the end time of the conference. By doing so, it is possible to improve the convenience when the participants of the conference operate the electronic device 70.

H. When the electronic device 70 has, for example, a video conference function, it can communicate with an electronic device (video conference terminal 70x or the like) of another base 4 to hold a conference with another base. The PC 70y on which the application operates can also communicate with the electronic device 70. The reservation information includes destination information (destination communication ID) indicating another base in advance, and the electronic device 70 can automatically communicate with the video conference terminal 70x and the PC 70y.

I. When the reservation person ends the conference, he / she presses the button of the conference room terminal 90 to check out, so that the conference room terminal 90 displays the next reservation status. As a result, any user can grasp the reservation status of the conference room.

<Outline of operation of source reservation system when the start time has passed>
FIG. 2 is a diagram illustrating an outline of the operation of the reservation management server 20 and the conference management server 30 when the reservation start time has passed. The time zone from the start time to the end time in FIG. 2 is the time zone in which the conference room is reserved.

(1) The conference management server 30 temporarily deletes the reservation (A) when the temporary deletion time T1 (an example of the first time) elapses from the start time without checking in. Even if the conference management server 30 is temporarily deleted, check-in to the reservation (A) is accepted during the automatic cancellation time T2 (an example of the second time).

(2) The conference management server 30 requests the reservation management server 20 to delete the reservation (A). The reservation management server 20 deletes the schedule (A) (or puts it in the cancel status) by the deletion request.

(3) By deleting the schedule (A), the reservation management server 20 can accept the reservation (B) at a time zone overlapping with the reservation (A).

(4) When the reservation (B) is added in the time zone overlapping with the reservation (A), the conference management server 30 cancels the reservation (A) at that time.

(5) If the reservation person checks in to the reservation (A) by the automatic cancellation time T2 without adding a new reservation, the conference management server 30 permits the check-in. In this way, after the provisional deletion time T1 elapses and until the automatic cancellation time T2 elapses, the earlier of check-in and registration of a new reservation is prioritized.

(6) When the reservation person checks in, the conference management server 30 requests the reservation management server 20 to restore the reservation (A) (depending on the specifications of the reservation management server 20, there are many cases where a new reservation is made).

This (5) and (6) overlap with the acceptance of the start of use of the reservation of the temporary deletion status and the reservation of the temporary deletion status from the lapse of the temporary deletion time T1 to the lapse of the automatic cancellation time T2. It means that the earliest one of the registrations of new reservations in the time zone will be processed first.

In this way, the provisional deletion of the reservation enables another user to reserve the conference room at a time zone overlapping with the reservation (A) while retaining the right to check in the reservation person of the schedule (A). Therefore, the reservation person is allowed the conventional grace, and the user who wants to use the conference room can start using the conference room earlier than the conventional (automatic cancellation).

<Terminology>
A resource is a resource. The conference room and the equipment, equipment, people (reception), mechanism, etc. that can be used in the conference room can be resources. Equipment that is difficult to move, such as a conference room, may be called equipment. In this embodiment, the term conference room is used as an example of a resource.

Participants are participants in the conference. The reservation person means the person who reserved the conference room. Generally, the reservation person is one of the participants, so it is not necessary to strictly distinguish between the two. In the present embodiment, the work performed by the reservation person may be performed by the participant. Collectively, those who use the conference room are simply called users.

Temporary deletion is a method of deleting a reservation that allows another user to reserve a conference room at a time that overlaps with the provisionally deleted reservation while retaining the right of the reservation person to start using the reserved resource. It may be called a provisional cancellation. On the other hand, cancellation means that the right to reserve a resource is waived.

<System configuration example>
FIG. 3 is an example of a system configuration diagram of the reservation system 100. The reservation system 100 can be mainly divided into an external network N2 and an internal network N1. The internal network N1 refers to the 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 as needed. The terminal device 60 operated by the participants of the conference may be connected to the external network N2 as needed.

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 reservation provided by the reservation management server 20 is called a reservation management system. The reservation management server 20 has a calendar system and provides a Web application for managing various schedules. Specifically, it has the following functions, for example.
・ Reservation can be confirmed anytime and anywhere by accepting schedule registration ・ Notify by e-mail at the set date and time, such as 30 minutes before the schedule ・ One person manages the schedule with multiple calendars (work, home, etc.) Yes-The reservation management server 20 that shares the calendar with people in the same group manages users by account. An account is a user's right to use a service. On many systems, users use an account to log in to the system. Therefore, the account has a function (identification information function) in which the system uniquely identifies the user. In the present embodiment, the reservation management server 20 transmits the reservation information of the account (domain) registered in advance to the conference management server 30. Alternatively, by designating an account of the reservation management server 20 and requesting the reservation information by the conference management server 30, the conference management server 30 can acquire the reservation information of the conference room 6 from the reservation management server 20. The account may be any information that can uniquely identify the user, such as e-mail, ID, and telephone number.

In the present embodiment, the reservation of the conference room 6 is managed as a schedule, but the reservation management server 20 is not limited to the conference room 6 and can manage various schedules. In addition to the conference room 6, various resources such as rental offices, rental studios, rental cycles, rental cars, accommodation facilities such as hotels, rental spaces such as entertainment venues and lockers, rental of various electronic devices, reservation of parking lots, etc. Can be used for reservations.

As the reservation management system, G Suite (registered trademark), Office365 (registered trademark) and the like are known, but any reservation management system having the functions described in the present embodiment may be used.

Further, in the present embodiment, information about the conference room 6 of the in-house network N1 is registered in advance in the reservation management server 20. That is, the reservation management server 20 according to 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 company's internal network using the reservation system 100. Web application is customized. Therefore, the reservation information is linked to the conference room 6 of the company that uses the reservation system 100.

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 of information such as text, voice, and video among a plurality of users provided by the chat server 10 is called a chat system. The chat server 10 notifies the terminal device 60 of information regarding the reservation of the conference room 6. In this embodiment, a plurality of chat servers 10 having different operating entities may be included.

The information to be shared includes images, sounds, and the like and is not limited to text, but in the present embodiment, for convenience of explanation, it is described that text is mainly used for notification. For example, a chat system may provide voice call functionality between groups. The voice call may be one-to-one or one-to-N (≧ 2). Therefore, when the chat system notifies the information regarding the reservation of the conference room 6 in the present embodiment, it may output a voice message in addition to displaying the text. As chat systems, LINE (registered trademark, hereinafter omitted), slack, Microsoft Teams (registered trademark, hereinafter omitted), etc. are known, but bots (predetermined processing) are performed. Any chat system that can notify one or more users from the program to be executed) may be used.

The chat server 10 also manages users with an account (different from the account of the reservation management server 20), but in principle, the conference management server 30 does not need to be aware of the account of 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 devices within the scope of claims). The conference management server 30 acquires the reservation information of the conference room 6 from the reservation management server 20 as a process related to the external network N2, acquires the prospective participants set in the reservation information, and the prospective participants at the set timing. A notification is sent to a group of chat servers 10 (or individual persons such as reservation persons) associated with. Further, as a process related to the in-house network N1, check-in and check-out to the conference room 6 are managed, and the power supply of the electronic device 70 is controlled based on the reservation information of the conference room 6 acquired from the reservation management server 20. do.

The in-house network N1 includes a conference room 6, a work place 101 for prospective participants, a work place 102 for managers, and the like, and prospective participants can access the external network N2 from various places via the in-house 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 LANs in 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 with each other by a small-scale 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 either wirelessly or by wire. Since the internal network N1 is inside the firewall 73, it is difficult to directly communicate from the external network N2 to the internal network N1.

The conference room terminal 90 is an information processing device (equipment terminal) operated by a conference participant such as a reservation person who uses the conference room 6. The conference room terminal 90 is arranged on the desk of the conference room 6 or is arranged at the entrance of the conference room 6. A plurality of conference room terminals 90 may be arranged in one conference room 6. The conference room terminal 90 can be realized by one or more information processing 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 the reservation information of the conference room 6 on the day. Further, control information such as power ON / OFF of the electronic device 70 is acquired from the conference management server 30. As a result, the conference room terminal 90 turns 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 from the reservation person and the conference room ID held in advance to the conference management server 30, so that the conference management server 30 uses the conference identification information and the conference room ID. It can be confirmed that the person who made the reservation for the conference room 6 uses the reserved conference room 6.

The electronic device 70 is various office devices 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, an electronic blackboard, a multifunction device, a projector, a digital signage, a digital camera, and the like. The electronic blackboard has a large display with a touch panel, detects the coordinates of the board surface instructed by the user, connects the coordinates, and displays the stroke. In addition, it is possible to display the image of the connected PC and synchronize the stroke by communicating with the electronic blackboard of another base. The electronic blackboard may be called an electronic information board or an electronic whiteboard.

The multifunction device has functions such as a copier, a scanner, a printer, and fax transmission / reception, and is used for printing materials during a meeting, copying materials, digitizing materials, and transmitting materials. A projector is a device that projects an image. For example, the image displayed on the display by the terminal device 60 can be shared among the participants by projecting it on a screen or the like. Digital signage is a large display used to display any still image or moving image. Digital cameras are used by each participant to capture and store paper materials and materials displayed on electronic blackboards.

A terminal device 60 that can be connected to the in-house 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 a prospective participant (including a reservation person) reserves a conference room, but it is also assumed that the terminal device 60 will be brought into the conference room. It 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 (sunglass type, wristwatch type, etc.) and the like. However, it suffices if the browser software has a communication function or the dedicated application software operates on the chat server 10 or the reservation management server 20. For example, a car navigation system, a game machine, a television receiver, and the like can also be the terminal device 60.

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

The terminal device 60 can have the same function as the conference room terminal 90. That is, the standby screen described later is displayed, and check-in and check-out are accepted. Since it is not necessary to arrange the conference room terminal 90 in the conference room, the cost can be reduced.

A registration terminal 50 capable of connecting to the in-house network N1 is arranged in the work place 102 of the administrator. The registration terminal 50 may communicate by wire or wirelessly. The registration terminal 50 is an information processing device for the administrator to initially set in 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 by the administrator to set the conference management server 30, there is no need for a chat application or a conference application. The registration terminal 50 communicates with the conference management server 30 mainly by browser software.

<Hardware configuration>
<< Hardware configuration of conference management server >>
FIG. 4 is an example of a hardware configuration diagram of the conference management server 30. The conference management server 30 is constructed by a computer, and has a CPU 501, ROM 502, RAM 503, HD 504, HDD (Hard Disk Drive) controller 505, display 506, external device connection I / F (Interface) 508, network I / F 509, and bus. It is equipped with a line 510, a keyboard 511, a pointing device 512, a DVD-RW (Digital Versatile Disk Rewritable) drive 514, and a media I / F 516.

Of these, the CPU 501 controls the operation of the entire conference management server. The ROM 502 stores a program used to drive the CPU 501 such as an IPL. The RAM 503 is used as a work area of the CPU 501. The HD504 stores various data such as programs. The HDD controller 505 controls reading or writing of various data to the HD 504 according to the control of the CPU 501. The display 506 displays various information such as cursors, menus, windows, characters, or images. The 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 performing data communication using a communication network. The bus line 510 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 501 shown in FIG.

Further, the keyboard 511 is a kind of input means including a plurality of keys for inputting characters, numerical values, various instructions and the like. The pointing device 512 is a kind 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 or writing of various data to the DVD-RW 513 as an example of a detachable recording medium. In addition, it is not limited to DVD-RW, and 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.

The hardware configuration of the conference management server 30 shown in the figure shows a hardware element that is preferably provided in the conference management server 30.

The hardware configuration diagram of the reservation management server 20, the chat server 10, the registration terminal 50, and the terminal device 60 is the same as or different from the conference management server 30, but the description of the reservation system 100 of the present embodiment. It is assumed that there is no problem in the above. Further, since the conference management server 30, the reservation management server 20, and the chat server 10 support cloud computing, hardware resources are dynamically connected / disconnected according to the load in these hardware configurations. May consist of. Note that cloud computing refers to a usage mode in which resources on a network are used without being aware of specific hardware resources.

<< Meeting room terminal >>
FIG. 5 is a hardware configuration diagram of an example of the conference room terminal 90. FIG. 5 shows two hardware configuration examples of the conference room terminal 90. The conference room terminal 90 in FIG. 5 is assumed to be a tablet device. The conference room terminal 90 includes a CPU 701, a ROM 702, a RAM 703, an EEPROM 704, a CMOS sensor 705, an image sensor I / F706, an acceleration / direction sensor 707, a media I / F709, and a GPS receiving unit 711.

Of these, the CPU 701 controls the operation of the entire conference room terminal 90. The ROM 702 stores a program used to drive the CPU 701 such as the CPU 701 and the IPL. The RAM 703 is used as a work area for the CPU 701. The EEPROM 704 reads or writes various data such as an application according to the control of the CPU 701. The CMOS (Complementary Metal Oxide Semiconductor) sensor 705 is a kind of built-in image pickup means that captures a subject (mainly a self-portrait) and obtains image data under the control of the CPU 701. In addition, instead of a CMOS sensor, an image pickup means such as a CCD (Charge Coupled Device) sensor may be used. The image sensor I / F706 is a circuit that controls the drive of the CMOS sensor 705. The acceleration / orientation sensor 707 is a variety of sensors such as an electronic magnetic compass, a gyro compass, and an acceleration sensor that detect the geomagnetism. The media I / F 709 controls reading or writing (storage) of data to a recording medium 708 such as a flash memory. The GPS receiving unit 711 receives a GPS signal from a GPS satellite.

Further, the conference room terminal 90 includes a long-distance communication circuit 712, a CMOS sensor 713, an image sensor I / F714, a microphone 715, a speaker 716, a sound input / output I / F717, a display 718, and an external device connection I / F (Interface) 719. The short-range communication circuit 720, the antenna 720a of the short-range communication circuit 720, and the touch panel 721 are provided.

Of these, the telecommunications circuit 712 is a circuit that communicates with other devices via a communication network. The CMOS sensor 713 is a kind of built-in imaging means for capturing an image of a subject and obtaining image data under the control of the CPU 701. The image sensor I / F 714 is a circuit that controls the drive of the CMOS sensor 713. The microphone 715 is a built-in circuit that converts sound into an electrical signal. The speaker 716 is a built-in circuit that converts an electric signal into physical vibration to produce sounds such as music and voice. The sound input / output I / F 717 is a circuit that processes sound signal input / output between the microphone 715 and the speaker 716 under the control of the CPU 701. The display 718 is a kind of display means such as a liquid crystal display or an organic EL (Electro Luminescence) for displaying an image of a subject, various icons, and the like. The external device connection I / F719 is an interface for connecting various external devices. The short-range communication circuit 720 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The touch panel 721 is a kind of input means for operating the conference room terminal 90 by the user pressing the display 718.

Further, the conference room terminal 90 is provided with a bus line 710. The bus line 710 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 701 shown in FIG.

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

<< Reservation Management Server >>
The reservation management server 20 has a communication unit 21 and a reservation information management unit 22. Each of these functional units included in the reservation management server 20 is a function realized by operating any of the components shown in FIG. 4 by an instruction from the CPU 501 according to a program developed from the HD 504 to the RAM 503. Or it is a 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 the screen information of the reservation setting screen to the terminal device 60, and receives the reservation setting from the terminal device 60. In addition, the reservation information is transmitted to the conference management server 30. The communication unit 21 is realized by the CPU 501 of FIG. 4 executing a program and controlling the network I / F 509.

The reservation information management unit 22 manages the reservation information registered by the user. The reservation information management unit 22 reads the reservation information of the conference room 6 requested from the conference management server 30 from the reservation information DB 291 and transmits it to the conference management server 30 via the communication unit 21. Alternatively, when the reservation information is registered (or changed), the reservation information is transmitted to the conference management server 30 even if there is no request. It is assumed that a general Web application is used as a method for a prospective participant to reserve the conference room 6 in the reservation management server 20. The reservation information management unit 22 is realized by the CPU 501 of FIG. 4 executing a program or the like.

The reservation management server 20 has a storage unit 29. The storage unit 29 is realized by the RAM 503, HD 504, etc. of FIG. The storage unit 29 stores the reservation information DB 291 (Data Base), the constraint condition DB 292, and the requirement condition DB 293.

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

Table 1 shows an example of the reservation information stored in the reservation information DB 291. The reservation information is information for managing the reservation status of the conference room 6. In the reservation information, each item of the reservation person account, the conference name, the conference room ID, the start time, the end time, and the prospective participant account is registered in association with the reservation ID. The reservation ID is identification information that identifies one record of the reservation information. ID is an abbreviation for Identification and means an identifier or identification information. An ID refers to a name, a code, a character string, a numerical value, or a combination thereof used to uniquely distinguish a specific object from a plurality of objects. The same applies to IDs other than the reserved ID. The reservation person account is an account of a prospective participant who has reserved the conference room 6. The meeting name is the name of the meeting arbitrarily given by the prospective participants. The conference room ID is identification information that identifies the conference room 6 in the company network. The start time (use start time) is the beginning of the time zone in which the conference room 6 is reserved (the time when the conference is started), and the end time (use end time) is the end of the time zone in which the conference room 6 is reserved (use end time). The time when the meeting ends). The prospective attendee account is the account of the prospective attendee who will attend the conference. The accounts in Table 1 are all accounts issued by the reservation management server 20.

<< Chat Server >>
The chat server 10 has a communication unit 11 and a text processing unit 12. Each of these functional units included in the chat server 10 is a function realized by operating any of the configuration categories shown in FIG. 4 by an instruction from the CPU 501 according to a program developed from the HD 504 to the RAM 503. It is a means.

The communication unit 11 transmits and receives various information to and from the conference management server 30. In the present embodiment, the conference management server 30 receives information regarding the reservation of the conference room, information for identifying the bot (such as a token described later), and information for specifying the group of the notification destination. The information that identifies this bot is notified in advance from the chat server 10 as bot identification information when the bot of the conference management server 30 is created. Furthermore, an individual account such as a reservation person may be specified. Further, the communication unit 11 transmits to the conference management server 30 that the prospective participant has read the information regarding the reservation of the conference room, or the response of the prospective participant to the displayed information regarding the reservation of the conference room. The communication unit 11 is realized by the CPU 501 of FIG. 4 executing a program and controlling the network I / F 509.

The text processing unit 12 reserves the conference room 6 for prospective participants belonging to the group as information spoken by the bot based on the information for identifying the bot notified from the conference management server 30 and the information for specifying the group to be notified. Send information about. When the account to be notified is further specified by the conference management server 30, information regarding the reservation of the conference room 6 is transmitted to one of the prospective participants belonging to the group. Therefore, the notification may be given as many as the number of prospective participants, or may be given only to any user such as a reservation person.

The text processing unit 12 can perform so-called push notification. As a mechanism, for example, there are the following. The chat application 60a receives an ID (token) for push notification from a server operated by an OS (Operating System) maker. In this server, the token and the device (terminal device 60) are associated with each other. The chat application 60a registers the token and the account of the chat application 60a in the chat server 10. When the chat server 10 performs push notification, the account of the chat application 60a is specified, so that the associated token can be specified. The chat system specifies a token and sends the notification content to the server operated by the OS maker. This server gives a push notification to the device (terminal device 60) associated with the token.

Further, the chat server 10 has a storage unit 19. The storage unit 19 is realized by the RAM 503, HD 504, etc. of FIG. The group information DB 191 is stored in the storage unit 19.

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

Table 2 shows an example of the group information stored in the group information DB 191. Group information is information in which the 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 the workspace and the channel.

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 the workspace (for example, company A). The workspace is, for example, a URL, but it may be unique. Further, the workspace has a plurality of channels according to the purpose of chat and the like. A channel is a group of members with which common information is exchanged, such as a group for product A and a group for product B. One of the members belonging to the workspace belongs to the channel. That is, the notification destination is specified by the workspace and the channel. However, since the method of specifying the notification destination differs depending on the chat system, if there is identification information that can uniquely identify the group, only that information may be used, or the notification destination may be specified by three or more pieces of information.

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

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

<< Meeting Management Server >>
The conference management server 30 includes a communication unit 31, an information support unit 32, a reservation information acquisition unit 33, a notification determination unit 34, a control information generation unit 35, a control information response unit 36, a conference information notification unit 37, and a usage management unit 38. It has a reservation information transmission unit 39, a task execution unit 40, a reservation control unit 41, and a reservation unit 42. Each of these functional units possessed by the conference management server 30 is a function realized by operating any of the configuration categories shown in FIG. 4 by an instruction from the CPU 501 according to a program developed from the HD 504 to the RAM 503. Or it is a means. This program is distributed from a server for program distribution 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 unit 31 has a transmission unit 31a and a reception unit 31b. The receiving unit 31b receives the reservation information from the reservation management server 20, and receives the request for the reservation information from the conference room terminal 90. Further, the receiving unit 31b receives a check-in request / check-out request from the conference room terminal 90. Further, the receiving unit 31b receives the correspondence between the group of the chat system and the account from the registration terminal 50 operated by the administrator. The transmission unit 31a transmits information regarding the reservation of the conference room to the chat server 10, and transmits the reservation information to the conference room terminal 90. The communication unit 31 is realized by the CPU 501 of FIG. 4 executing a program and controlling the network I / F 509.

The information handling unit 32 mainly performs processing related to prior registration work. That is, the domain registration is received from the registration terminal 50 or the like, the domain is registered in the customer domain DB 495, and the chat system workspace and channel transmitted from the registration terminal 50 or the like are associated with the account of the reservation management server 20 in the corresponding information DB 491. sign up. The information correspondence unit 32 is realized by the CPU 501 of FIG. 4 executing a program or the like.

The reservation information acquisition unit 33 specifies the account of the customer who uses the reservation system 100 (since the conference management server 30 has been authenticated by the reservation management server 20 in advance, an authentication ticket or the like is also attached), the reservation management server The reservation information is acquired from 20 and registered in the conference management information DB 493 as the conference management information. Alternatively, the changed reservation information is automatically received. Therefore, at least a 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 the reservation information from the present to the future for a predetermined period among the reservation information held by the reservation management server 20. The predetermined period is determined by how long the meeting ahead will be notified of the information regarding the reservation of the conference room 6.

When the reservation information is acquired, the reservation information acquisition unit 33 generates a temporary deletion and automatic cancellation task and registers it in the task queue 499. The task queue 499 is a FIFO (First In First Out) queue, and is executed when the execution time arrives. The reservation information acquisition unit 33 is realized by the CPU 501 of FIG. 4 executing a program or the like.

The notification determination unit 34 determines whether or not there is a reservation for a start time satisfying the condition to be notified in the conference management information. For example, the notification setting DB 496 is referred to, and it is determined that the notification is made when the set date and time is reached by calculating back from the reservation start time. When bots are divided according to roles, such as bots for reminders and bots for accepting reservations, the bots are specified according to the processing. The notification determination unit 34 is realized by the CPU 501 of FIG. 4 executing a program or the like.

When the conference information notification unit 37 determines that the notification determination unit 34 notifies, the conference information notification unit 37 specifies information for identifying the bot (for example, a token in slack) and information for identifying the notification destination group, and notifies the information regarding the reservation of the conference room 6. Request the chat server 10 to do so. The notification is divided into several times, and 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 participants have the right to use the reserved conference room 6 in the reserved time zone. The conference information notification unit 37 generates conference identification information at least before the final notification. The conference identification information is registered in the conference identification information DB 494. The conference information notification unit 37 is realized by the CPU 501 of FIG. 4 executing a program or the like.

The control information generation unit 35 generates control information of 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, a few minutes before the start time of the conference, control information for turning on the power of the electronic device 70 is generated, and when a checkout is detected, control information for turning off the power of the electronic device 70 is generated. The control information is stored in the control information DB 497. The control information generation unit 35 is realized by the CPU 501 of FIG. 4 executing a program or the like.

The control information response unit 36 receives an inquiry as to whether or not there is control information from the conference room terminal 90 of the conference room 6, refers to the control information DB 497, and transmits control information corresponding to the conference room 6 to the conference room terminal 90. .. The control information response unit 36 is realized by the CPU 501 of FIG. 4 executing a program or the like.

The usage management unit 38 manages check-in / check-out to the conference room. In addition, the status of the conference mainly associated with check-in / check-out is registered in the conference management information DB 493. Check-in is permitted, for example, 5-10 minutes before the start time of the meeting specified by the booking ID. For example, the time 5 to 10 minutes before the start time of the conference is called the check-in possible time (the time when the use start operation is possible). Then, when the set of the conference room ID and the conference identification information transmitted by the conference room terminal 90 is registered in the conference identification information DB 494, check-in is permitted. When the check-in is permitted, the usage management unit 38 deletes the temporary deletion and automatic cancellation tasks (in some cases, only automatic cancellation can be deleted). The usage management unit 38 is realized by the CPU 501 of FIG. 4 executing a program or the like.

The task execution unit 40 periodically checks the tasks stored in the task queue 499 and executes the task whose execution time has arrived. If the check-in request is not sent by the time the temporary deletion time T1 elapses, the task execution unit 40 executes the temporary deletion task (when the temporary deletion time T1 elapses) because the task has not been deleted. Temporarily delete the reservation information. Specifically, the usage management unit 38 changes the status of the reservation information to "temporary deletion". If the check-in request is not sent from the conference room terminal 90 by the automatic cancellation time T2, the task execution unit 40 cancels the reservation of the conference room because the task has not been deleted (automatic cancellation). ). Specifically, the usage management unit 38 changes the status of the reservation information to "cancelled".

The reservation person can check in from the start time until the automatic cancellation time T2 elapses. The reservation information that overlaps with the reservation information of the temporary deletion status, which is reserved between the time when the temporary deletion time T1 elapses and the time when the automatic cancellation time T2 elapses, becomes the formal reservation information.

Although the task described in this embodiment is a temporary deletion or automatic cancellation task, various tasks executed at the time may be executed.

The reservation control unit 41 requests the reservation management server 20 to delete or restore the reservation according to the execution of the temporary deletion and the check-in after the temporary deletion.

When the reservation button is pressed immediately on the conference room terminal 90, the reservation unit 42 requests the reservation management server 20 to reserve the conference room with the authority of the conference management server 30.

Further, the conference management server 30 has a storage unit 49. The storage unit 49 is realized by the RAM 503, HD 504, etc. of FIG. Corresponding information DB 491, conference management information DB 493, conference identification information DB 494, customer domain DB 495, notification setting DB 494, control information DB 497, conference room setting information DB 498, and task queue 499 are stored in the storage unit 49.

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

Table 3 shows an example of the correspondence information stored in the correspondence information DB 491. Correspondence information is information that associates an account of a reservation management system with a group of a chat system. Corresponding information has each item of workspace, channel and member accounts 1 to n (n = 4 in the figure). The workspaces and channels are as described above. The account of each participant issued by the reservation management server 20 is registered in the member accounts 1 to n. Further, as shown in Table 3, a chat system account may be registered. In order to notify the group, the account of the user who reserved the conference to the reservation management server 20 and the information for specifying the group and channel of the notification destination (in the present embodiment, the workspace and the information). It is only necessary to have the channel name), and it is not always necessary that the accounts of all the members belonging to the group are registered. However, when notifying an individual user, the account information of each chat system is required, so that the information may be registered as shown in Table 3.

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

Table 4 shows an example of the conference management information stored in the conference management information DB 493 of the conference management server 30. Since the reservation information is stored in the conference management information DB 493, the difference from the reservation information DB 291 in Table 1 will be described in Table 4. The meeting management information in Table 4 has a status item. Status means the status of the reservation. For example, the status such as notification of information regarding the reservation of the conference room 6, confirmation of use, waiting for check-in, checked-in completed, check-out, temporary deletion, or cancellation (cancellation) is registered.

表５は会議識別情報ＤＢ４９４に記憶されている会議識別情報管理情報の一例を示す。会議識別情報管理情報は会議室６の予約ごとに会議識別情報を管理する情報である。会議識別情報管理情報は、予約ＩＤ、会議室ＩＤ、及び、会議識別情報の各項目を有する。これらについてはステータスを除き予約情報と同じであり（予約管理サーバ２０から受信した予約情報）、既出であるため説明は省略する。なお、予約ＩＤが登録されているのは、同じ会議室６の予約を識別するためである。ステータスは、予約の状況を意味する。例えば、会議室の予約に関する情報の通知済み、利用確定、チェックイン済み、チェックアウト、又は、キャンセル（取り消し）等の状況が登録される。

Table 5 shows an example of the conference identification information management information stored in the conference identification information DB 494. The conference identification information management information is information for managing the conference identification information for each reservation of the conference room 6. The conference identification information management information has each item of the reservation ID, the conference room ID, and the 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 published, the description thereof will be omitted. The reservation ID is registered in order to identify the reservation of the same conference room 6. Status means the status of the reservation. For example, the status such as notification of information regarding the reservation of the conference room, confirmation of use, check-in, check-out, or cancellation (cancellation) is registered.

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

Table 6 shows an example of the customer domain information stored in the customer domain DB 495. Customer domain information is information that manages the customer's domain and the account of the customer's administrator. 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. The administrator account is an account of the customer's administrator (representative). The account in Table 6 is issued by the reservation management server 20.

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

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

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

Table 8 shows an example of the control information stored in the control information DB 497. The control information is information for controlling the electronic device 70 of the conference room 6. The control information includes the conference room ID and each item of the 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. Further, it is difficult to transmit the time to be controlled from the conference management server 30 of the external network to the conference room terminal 90 because the time to be controlled is not registered, and the conference room terminal 90 accesses the conference management server 30 at this time. This is because the control content is transmitted if is generated.

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

Table 9 shows an example of the conference room setting information stored in the conference room setting information DB 498. The conference room setting information is information related to the setting for each conference room. The conference room setting information includes each item of the conference room name, the conference room ID, the status of the conference room terminal, the authentication key, the management start flag, and the access time.
-The conference room name is a general name of the conference room recognized by the participants of the conference, for example, the one presented at the entrance of the conference room.
-The conference room ID is identification information that uniquely identifies the conference room as described above. Simply, the conference room ID can be shared with the reservation management server 20. Further, by providing the conversion table, the administrator can set it separately from the reservation management server 20.
-The state of the conference room terminal indicates whether the initial setting of the conference room terminal 90 is completed, communication is possible, and the like.
Connecting: For example, communication can be confirmed by polling Before setup: Before initial setting Connection disconnection: No communication for a certain period (M minutes in this embodiment) -The authentication key is the conference management server 30 in the conference room. It becomes the authentication information for authenticating the terminal 90. The authentication key is transmitted to the conference room terminal 90 by the initial setting. The authentication key is a combination of numbers, alphabets, symbols, etc. with long digits that cannot be specified by the 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 (True: start False: not start) indicating whether or not the conference management server 30 starts the management of the conference room after the initial setting of the conference room terminal 90 is completed. By having the management start flag, it is possible to suppress the inconvenience caused by the time lag from the completion of the initial setting to the arrangement of the conference room terminal 90.
The access time is a time when the reservation information periodically requested by the conference room terminal 90 is recorded every N minutes. Not limited to the request for reservation information, the time of communication with the conference room terminal 90 may be recorded. There are the following relationships between N minutes, M minutes, and polling intervals.
Polling interval <N minutes <M minutes The access time may be recorded for each polling. However, if the polling interval is short, the load on the conference room setting information DB 498 of the conference management server 30 becomes large. Therefore, the load is reduced by recording the access time every N minutes, which is larger than the polling interval.

Among the conference room setting information stored in the conference room setting information DB 498, the conference room name and the conference room ID are predetermined or can be set by the administrator. The one transmitted from the reservation management server 20 may be used. The initial state of the conference room terminal 90 (immediately after the setting of the provider) is before the setup, but it changes depending on the communication status as described in the present embodiment. The authentication key is assigned 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 the 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 items of a task ID, an execution time, a task content, and a reservation ID. The task ID is identification information for identifying the task. The execution time is the time when this task is executed. The task content is the specific content of the task. The reservation ID is set to specify the reservation information of the conference management information DB 493. For example, set to delete a checked-in booking task. In Table 10, it can be seen that it takes 5 minutes from temporary deletion to automatic cancellation, but this is just an example.

When a check-in request is sent from the conference room terminal 90, the usage management unit 38 updates the status of the conference management information DB 493 to "check-in completed", but the usage management unit 38 is in the task queue 499 when the check-in is detected. Delete the task. That is, the usage management unit 38 identifies the task in the task queue 499 by the reservation ID of the conference management information whose status is updated to "checked in", and deletes the "temporary deletion" and automatic cancellation tasks. This will prevent you from being canceled even though you are checking in. In some cases, the task of "temporary deletion" or automatic cancellation has already been executed.

<< Terminal device >>
FIG. 7 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 shape. The functions of the registration terminal 50 and the electronic device 70 will be described as necessary.

The terminal device 60 includes a communication unit 61a, an operation reception unit 61b, a display control unit 61c, a chat communication unit 62, a text display unit 63, an application communication unit 64, a server communication unit 65, a display control unit 66, an application communication unit 67, and the like. , Has a terminal communication unit 68. Each of these functional units included in the terminal device 60 has a function realized by operating any of the configuration categories shown in FIG. 4 by an instruction from the CPU 501 according to a program developed from the HD 504 to the RAM 503. It is a means. This program is distributed from a server for program distribution or stored in a storage medium. Since the chat application 60a and the conference application 60b are operating on the terminal device 60, the program includes the chat application 60a and the conference application 60b.

The communication unit 61a transmits and receives various information to and from the conference management server 30 and the reservation management server 20. The communication unit 61a is realized by the CPU 501 of FIG. 4 executing a program and controlling the network I / F 509.

The operation reception unit 61b receives various operations of the participants with respect to the terminal device 60. The operation receiving unit 61b is realized by the CPU 501 of FIG. 4 executing a program and controlling the keyboard 511, the pointing device 512, and the like.

The display control unit 61c interprets the screen information of various screens and displays it on the display 506. 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 the 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 the present embodiment, information regarding the reservation of the conference room 6 is received from the chat server 10, and the chat server 10 is notified that the information has been read, whether the conference room 6 is used or canceled, and the like. The chat communication unit 62 is realized by the CPU 501 of FIG. 4 executing a program and controlling the network I / F 509.

The text display unit 63 of the chat application 60a displays the text (information regarding the reservation of the conference room 6) transmitted from the chat server 10. For example, the source is a bot and the text is displayed as if the bot had typed it. The text display unit 63 is realized by the CPU 501 of FIG. 4 executing the chat application 60a or the like.

The application communication unit 64 of the chat application 60a calls the conference application 60b and transmits the conference identification information to the conference application 60b. Since the chat server 10 transmits information for identifying the conference application 60b to the terminal device 60 when notifying the information regarding the reservation of the conference room 6, the chat application 60a designates the conference application 60b to the OS and identifies the conference. Request notification of information. The OS can start the conference application 60b. The application communication unit 64 is realized by the CPU 501 of FIG. 4 executing the chat application 60a or the like.

The server communication unit 65 of the conference application 60b communicates with the conference management server 30. The two-dimensional code including the conference identification information is acquired from the conference management server 30 and the like. The server communication unit 65 is realized by the CPU 501 of FIG. 4 executing the conference application 60b or the like. The two-dimensional code is used for authentication at check-in. It may be a few digits for authentication.

The display control unit 66 of the conference application 60b displays a two-dimensional code or the like including the conference identification information on the display 506. The display control unit 66 is realized by the CPU 501 of FIG. 4 executing the conference application 60b and controlling the graphics driver.

The application communication unit 67 of the conference application 60b acquires various information (conference identification information and the like included in the information regarding the reservation of the conference room 6) from the chat application 60a via the OS. The application communication unit 67 is realized by the CPU 501 of FIG. 4 executing the conference application 60b or the like.

The terminal communication unit 68 communicates with the conference room terminal 90 and transmits conference identification information and the like. The terminal communication unit 68 detects the presence of the conference room terminal 90 by short-range wireless communication such as Bluetooth (registered trademark), and transmits the conference identification information when the conference room terminal 90 is detected. It also provides a function to display a two-dimensional code to the conference room terminal 90. The terminal communication unit 68 is realized by the CPU 501 of FIG. 4 executing the conference application 60b or the like.

<< Meeting room terminal >>
The conference room terminal 90 has a server communication unit 91, a terminal device communication unit 92, an operation reception unit 93, a display control unit 94, an electronic device communication unit 95, and a reservation information request unit 96. Each of these functional units included in the conference room terminal 90 is a function realized by operating any of the configuration categories shown in FIG. 5 by a command from the CPU 701 according to a program developed from the EEPROM 704 to the RAM 503. Or it is a means. This program is distributed from a server for program distribution or stored in a storage medium.

The server communication unit 91 communicates with the conference management server 30 with the server URL 993 as the destination. Since the conference room terminal 90 exists in the company network, it is difficult to communicate with the conference room terminal 90 from the conference management server 30. Therefore, the server communication unit 91 communicates with the conference management server 30 by communication technology such as polling (communicate with the conference management server 30 periodically) and WebSocket. If there is no communication from the server communication unit 91, the connection 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.

At the time of check-in, the server communication unit 91 of the present embodiment transmits the conference identification information received from the terminal device 60 by the terminal device communication unit 92 or the conference identification information manually input to the conference management server 30. Further, the server communication unit 91 receives control information from the conference management server 30. The server communication unit 91 is realized by the CPU 701 of FIG. 5 executing a program and controlling the wireless LAN communication unit 613.

The terminal device communication unit 92 communicates with the terminal device 60. In this embodiment, conference identification information and the like are received. The terminal device communication unit 92 is realized by the CPU 701 of FIG. 5 executing a program and controlling the short-range communication circuit 720.

The electronic device communication unit 95 communicates with the electronic device 70. In the present embodiment, the control information received by the server communication unit 91 is transmitted to the electronic device 70. The electronic device communication unit 95 is realized by the CPU 701 of FIG. 5 executing a program and controlling the long-distance communication circuit 712.

The display control unit 94 displays the screen generated by the terminal application 90a on the display 718. This screen is a standby screen where you can check in and check out. The display control unit 94 is realized by the CPU 701 of FIG. 5 executing a program and controlling the display 718.

The operation reception unit 93 receives various operations for the conference room terminal 90. The operation reception unit 93 is realized by the CPU 701 of FIG. 5 executing a program and controlling the touch panel 721.

The reservation information request unit 96 repeatedly transmits the conference room ID and the authentication key to the conference management server 30 via the server communication unit 91 at a periodic timing for acquiring the reservation information. In response to this, the reservation information request unit 96 acquires reservation information via the server communication unit 91. Reservation information only needs to be obtained if there is a change. The timing is a cycle of several seconds to several minutes. The shorter the cycle, the earlier the reservation information can be updated, but the communication load also increases, so the decision is made by considering both. In this embodiment, it is set to, for example, 30 seconds. Further, at least the conference management information (reservation information) of the conference room 6 on the day can be received via the server communication unit 91.

In a situation where the reservation information requesting unit 96 cannot request the reservation information from the conference management server 30, the communication environment may deteriorate. For example, there is a case where radio waves interfere with each other, a wireless LAN access point breaks down, or the power is turned off. It is thought that the communication environment will deteriorate even if a power outage occurs. Further, even if the conference room terminal 90 fails in terms of hardware, communication may become difficult. Further, when the terminal application is not running or is operating in the background, the reservation information request unit 96 does not request the reservation information. In either case, the conference management server 30 detects a communication undetected state in which the state of the conference room terminal 90 is set to "disconnected".

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

<Example of setting temporary deletion time and automatic cancellation time>
The temporary deletion time T1 and the automatic cancellation time T2 can be set by the administrator in the cancellation policy setting of the conference room.

FIG. 8 is an example of the cancellation policy setting screen 300. The administrator operates the registration terminal 50 to connect to the conference management server 30, and causes the registration terminal 50 to display the cancellation policy setting screen 300. The conference management server 30 provides the cancellation policy setting screen 300 to the registration terminal 50 as, for example, a Web page (including a Web application).

The cancellation policy setting screen 300 has a rule name column 301, a room entry method column 302, a temporary deletion time column 303, an automatic cancellation time column 304, and a reminder column 305.
-Rule name field 301: A name for the administrator to determine the operation rule of the conference room set on the cancellation policy setting screen 300.
-Room entry method column 302: A method for a reservation person or the like to check in (a method for inputting conference identification information to the conference room terminal 90). Input of conference identification information, reading of image code, short-range communication, etc.
-Temporary deletion time column 303 ... This is a column for setting the temporary deletion time T1. If the relationship is not "temporary deletion time T1 in the temporary deletion time column 303 ≥ automatic cancellation time T2 in the automatic cancellation time column 304", the registration terminal 50 may not accept the input. In this case, the registration terminal 50 may display a message such as "Please input so that the temporary deletion time T1 <automatic cancellation time T2".
-Automatic cancellation time column 304 ... This is a column for setting the automatic cancellation time T2. If the relationship is not "temporary deletion time T1 in the temporary deletion time column 303 ≥ automatic cancellation time T2 in the automatic cancellation time column 304", the registration terminal 50 may not accept the input. In this case, the registration terminal 50 may display a message such as "Please input so that the temporary deletion time T1 <automatic cancellation time T2". Further, the automatic cancellation time T2 may have an upper limit value that can be input.
-Reminder column 305 ... This is a setting column for the timing at which the conference management server 30 reminds that the conference room is reserved.

The information set on the cancellation policy setting screen 300 is transmitted to the conference management server 30. When the reservation information acquisition unit 33 acquires the reservation information from the reservation management server 20, the reservation information acquisition unit 33 registers the task in the task queue 499 based on the reservation start time, the temporary deletion time T1 and the automatic cancellation time T2.

<Operation procedure for the conference room terminal to acquire reservation information>
FIG. 9 is an example of a sequence diagram showing a procedure for the conference room terminal 90 to acquire reservation information. The process of FIG. 9 starts from the state where the initial setting is completed.

S1: The reservation person operates the terminal device 60 to set the reservation of the conference room in the reservation management server 20.

S2: The reservation information management unit 22 of the reservation management server 20 stores the reservation information in the reservation information DB 291.

S3: The communication unit 21 of the reservation management server 20 transmits the change of the reservation information to the conference management server 30. As a result, the reservation information acquisition unit 33 of the conference management server 30 requests the reservation information in order to synchronize the reservation information. Reservation information may be attached to the change notification.

S4: The reservation information acquisition unit 33 generates a temporary deletion and automatic cancellation task based on the reservation information, and registers the task in the task queue 499.

The following processing is executed every polling interval (for example, 30 seconds).

S5: Since the polling interval is based on the update of the standby screen described later, the display control unit 94 of the conference room terminal 90 starts the screen update.

S6: The reservation information request unit 96 of the conference room terminal 90 designates the conference management server 30 by the server URL, transmits the conference room ID and the authentication key via the server communication unit 91, and requests the reservation information. The communication unit 31 of the conference management server 30 receives the request for reservation information, and the reservation information transmission unit 39 authenticates with the authentication key. In this embodiment, it is assumed that the authentication is successful.

S7: The reservation information transmission unit 39 of the conference management server 30 transmits the reservation information specified by the conference room ID to the conference room terminal 90. The reservation information request unit 96 of the conference room terminal 90 receives the reservation information via the server communication unit 91. The display control unit 94 updates the standby screen based on the reservation information. 11 and 12 show an example of the standby screen.

<Sequence from temporary deletion of meeting reservation to automatic cancellation>
FIG. 10 is an example of a sequence diagram illustrating a process of provisional deletion and automatic cancellation of reservation information in the conference management server 30.

S11: When the execution time of the temporary deletion registered in the task queue 499 comes, the task execution unit 40 of the conference management server 30 requests the reservation control unit 41 to temporarily delete the reservation based on the task.

S12: The reservation control unit 41 specifies a reservation ID and requests the reservation management server 20 to delete the reservation information.

S13: The reservation information management unit of the reservation management server 20 deletes the reservation information specified by the reservation ID. That is, since the reservation management server 20 does not have the status of temporary deletion, the reservation is deleted (or becomes the cancellation status), and another reservation can be accepted in the overlapping time zone. If the reservation management server 20 has a status of temporary deletion, the temporary deletion may be requested.

S14: Further, the task execution unit 40 requests the usage management unit 38 to change the status to temporary deletion. The usage management unit 38 changes the status of the conference management information DB 493 to "temporary deletion" (an example of the first status). In the "temporary deletion" state, the reservation person can check in.

Next, the case where the check-in operation is performed after the temporary deletion is executed will be described.

S15: The reservation person presses the entry button described later on the standby screen displayed by the conference room terminal 90. The operation reception unit 93 of the conference room terminal 90 accepts the press, and the server communication unit 91 sends a check-in request to the conference management server 30.

S16: The usage management unit 38 determines whether to allow check-in based on the conference identification information. When the check-in is permitted, the reservation control unit 41 is notified to that effect.

S17: The reservation control unit 41 determines whether or not the status of the checked-in reservation is provisional deletion. In the case of temporary deletion, the reservation control unit 41 makes a reservation restoration request to the reservation management server 20. A reservation restoration request is, in principle, a request for a new reservation. The reservation management server 20 is requested to register the reservation of the same conference room at the same time zone as the temporarily deleted reservation information. The time zone may be shifted backward by the amount elapsed from the start time. Exceptionally, if the reservation management server 20 has a status of temporary deletion, the temporarily deleted reservation is returned to the original state. In this case, the temporarily deleted reservation information will be restored in the same conference room at the same time.

S18: The reservation information management unit 22 of the reservation management server 20 restores the reservation newly registered or temporarily deleted to the original state.

S19: Also, since the usage management unit 38 has permitted check-in, the status of the conference management information DB 493 is changed to "check-in completed". Also, the task of automatic cancellation of task queue 499 is deleted.

Next, the case where the automatic cancellation time T2 has elapsed without being checked in will be described.

S20: When the execution time of the automatic cancellation registered in the task queue 499 comes, the task execution unit 40 of the conference management server 30 notifies the reservation control unit 41 of the execution of the automatic cancellation.

S21: The task execution unit 40 specifies the reservation ID and notifies the usage management unit 38 of the automatic cancellation of the reservation information. The usage management unit 38 changes the status of the reservation information specified by the reservation ID to "cancelled" (an example of the second status).

S22: The reservation control unit 41 notifies the user that the reservation has been canceled via the conference information notification unit 37. For example, the chat server 10 uses a bot to notify the user that the reservation has been canceled or send an e-mail.

Next, a case where another reservation is registered without being checked in by the automatic cancellation time T2 will be described.

S23: On the standby screen displayed by the conference room terminal 90, the user presses the "immediate use button" described later. The operation reception unit 93 of the conference room terminal 90 accepts the press, and the server communication unit 91 transmits a reservation request to the conference management server 30.

In step S23, the conference room is reserved from the conference room terminal 90, but the user can also connect the terminal device 60 to the reservation management server 20 to reserve the conference room.

S24: The reservation unit 42 of the conference management server 30 transmits a reservation request for a fixed time such as 30 minutes or 1 hour from the current time to the reservation management server 20 with the authority of the conference management server 30.

S25: The reservation management server 20 notifies the conference management server 30 that another reservation has been added. As a result, the reservation information acquisition unit 33 acquires the latest reservation information from the reservation management server 20. If you make a reservation by pressing the use button now, the task of temporary deletion or automatic cancellation will not be generated. This is because the user is already in the conference room. Since the reservation information reservation unit 33 has the authority of the conference management server 30, the reservation information acquisition unit 33 does not generate a task. Further, the usage management unit 38 permits check-in because the reservation person has the authority of the conference management server 30.

S26: The reservation information acquisition unit 33 notifies the reservation control unit 41 of the latest reservation information.

S27: The reservation control unit 41 determines whether or not the meeting time of the new reservation overlaps with the meeting time of the reservation information in the status of provisional deletion. If they overlap, the reservation control unit 41 requests the usage management unit 38 to change the status of the reservation information for temporary deletion to canceled. The canceled reservation information will no longer be valid reservation information (the reservation person cannot check in).

S28: The reservation control unit 41 notifies the user that the reservation has been canceled via the conference information notification unit 37. For example, the chat server 10 uses a bot to notify the user that the reservation has been canceled, or sends an e-mail.

In addition, it supplements the case where "new reservation" and "check-in after temporary deletion" occur almost at the same time and the processing conflicts. For both "new reservation" and "check-in after temporary deletion", the reservation is added (restoration or new registration) to the reservation management server 20. When such a processing conflict occurs, the solution is based on the processing result of the reservation management server 20. As an example, when a schedule is added at almost the same time, the reservation management server 20 executes the reservation processing in the order in which the processing is received. If there is already an appointment, an error will occur. That is, the reservation in the order of receiving the processing is prioritized.

<Example of standby screen>
The standby screen displayed by the conference room terminal 90 will be described with reference to FIGS. 11 and 12. 11 and 12 both show an example of the standby screen 550 displayed by the conference room terminal 90 when the conference room is currently vacant but within a predetermined time (for example, 10 minutes) until the start time of the next conference. ..

First, FIG. 11 is a standby screen when the reservation information is not temporarily deleted. On the standby screen 550, the current status column 561, the conference room name column 562, the conference name column 563, the start time column 564, the end time column 565, the entry button 568, the reservation column 567 after that, and the like are displayed. ing.

The current status column 561 indicates the current status of the conference room. Ten minutes before the start time, the status changes to "Check-in possible", etc., so the display control unit 94 displays "Waiting for entry" in the current status column 561 and displays the entry button 568 to check in. Allow. In other words, the reservation person can check in. Further, if the conference room terminal 90 does not send the check-in request before the automatic cancellation task is executed as described above, the task execution unit 40 automatically cancels. Therefore, the display control unit 94 counts down the time 569 until it is automatically canceled and displays it in the current status column 561.

The conference room name stored in the storage unit 99 is displayed in the conference room name column 562. The conference name included in the reservation information is displayed in the conference name column 563. The start time and end time included in the reservation information are displayed in the start time column 564 and the end time column 565, respectively. In the reservation column 567 after this, the start time and the end time of each conference reserved after the present are displayed according to the reservation information.

The entry button 568 is a button for the user to check in. When this button is pressed, the reservation person can input the conference identification information. The reservation person information is displayed in the reservation person name column 570. The 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.

When the entry button 568 is pressed, the conference identification information is transmitted to the conference management server 30, and the check-in is approved, the status of this conference room is changed to "checked in". The change in status is also reflected on the standby screen 550 when the conference room terminal 90 receives the reservation information (for example, the entry button becomes the exit button).

FIG. 12 is an example of a standby screen displayed when the reservation information waiting to enter the room is temporarily deleted. In the description of FIG. 12, since the components having the same reference numerals in FIG. 11 perform the same function, only the main components of FIG. 12 may be mainly described.

First, the reservation information whose status is temporarily deleted is transmitted to the conference room terminal 90. Since the reservation information is transmitted, the conference room terminal 90 can continuously display the reservation information.

However, since the status of the display control unit 94 of the conference room terminal 90 is "temporary deletion", the message 572 "This conference has passed the temporary cancellation time. It can be used by anyone other than the reserved person." Is displayed. That is, it displays that it can be used by anyone other than the person who made the reservation.

Further, since the status of the display control unit 94 is "temporary deletion", not only the entry button but also the immediate use button 571 is displayed. The immediate use button 571 is a button pressed by a user who wants to use the conference room other than the reserved person. When the status is "temporary deletion" in this way, the display control unit 94 uses the immediate use button 571 (an example of the second display component) that allows both the reservation person and other users to check in, and the entry button 568 (the first). Display at the same time as an example of one display component). Therefore, the user who wants to use the conference room can press the use button 571 immediately before the automatic cancellation to reserve the conference room and check in.

When the use button 571 is pressed on the standby screen of the reservation information whose status is temporarily deleted, the reservation management server 20 is determined to be 30 minutes or 1 hour from the current time from the conference room terminal 90 via the conference management server 30. A reservation request for the time is sent. Since the reservation has already been canceled on the reservation management server 20, the reservation management server 20 accepts a new reservation. Since the newly registered reservation information is transmitted to the conference management server 30, the conference management server 30 registers the reservation information in the conference management information DB 493 and permits check-in. Since the reservation by the use button 571 now is reserved with the authority of the conference management server 30, check-in can be performed without task generation or authentication by the conference identification information.

Since the reservation has been deleted from the reservation management server 20 at the time of temporary deletion, the user who wants to use the conference room may make a reservation directly to the reservation management server 20.

<Main effect>
According to the reservation system of the present embodiment, due to the provisional deletion of the reservation, the reservation person who is scheduled to be provisionally deleted retains the right to check in, and another user has a meeting at a time zone overlapping with the provisionally deleted reservation. You will be able to reserve a room. Therefore, the reservation person is allowed the conventional grace, and the user who wants to use the conference room can start using the conference room earlier than the conventional (automatic cancellation).

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

For example, in the present embodiment, the conference room terminal 90 displays the standby screen, but the terminal device 60 can also display the standby screen. In this case, the terminal device 60 displays the message 572.

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

The group of devices described in this embodiment is merely one of a plurality of computing environments for implementing the embodiments disclosed herein. In one embodiment, the conference management server 30 includes a plurality of computing devices such as server clusters. The plurality of computing devices are configured to communicate with each other over any type of communication link, including networks, shared memory, and the like, and perform the processes disclosed herein.

Further, the reservation system 100 of the present embodiment can also be referred to as a Web service. Web services are various services provided by applying Internet-related technologies. For example, a conference room rental service and various rental services can be mentioned. A system that uses Web services is called a usage system.

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

Each function of the embodiment described above can be realized by one or more processing circuits. Here, the "processing circuit" as used herein is a processor programmed to perform each function by software, such as a processor implemented by an electronic circuit, or a processor designed to execute each function described above. It shall include devices such as ASIC (Application Specific Integrated Circuit), DSP (digital signal processor), FPGA (field programmable gate array) and conventional circuit modules.

30 Conference management server 100 Reservation system

Japanese Unexamined Patent Publication No. 2010-102578

Claims (8)

An information processing device that manages the use of reserved resources.
The usage management unit that accepts the start of use of the resource,
The usage management unit has a reservation control unit that changes the reservation of the resource to the first status when the first time elapses from the usage start time of the resource without accepting the start of use of the resource. death,
From the lapse of the first time to the lapse of the second time, the acceptance of the start of use of the reservation of the first status and the new time zone overlapping with the reservation of the first status An information processing device characterized by giving priority to processing the earliest of the reservation registrations. If the acceptance of the start of use of the reservation of the first status is earlier than the registration of a new reservation in the time zone overlapping with the reservation of the first status, the usage management unit starts using the resource. Allow and
If the registration of a new reservation in a time zone overlapping with the reservation of the first status is earlier than the acceptance of the start of use of the reservation of the first status, the usage management unit will make the new reservation. The information processing apparatus according to claim 1, wherein the start of use of the resource is permitted based on the above. When a new reservation in a time zone that overlaps with the reservation of the first status is registered between the lapse of the first time and the lapse of the second time.
The information processing apparatus according to claim 1 or 2, wherein the reservation control unit changes the reservation status of the resource from the first status to the second status meaning the cancellation of the reservation. When the first time elapses from the usage start time of the resource without the usage management unit accepting the start of use of the resource.
The usage management unit requests the information processing apparatus that accepts the reservation of the resource to delete the reservation changed to the first status.
When the usage management unit accepts the start of use of the reservation of the first status between the lapse of the first time and the lapse of the second time, the usage management unit receives the information. The information processing apparatus according to any one of claims 1 to 3, wherein the processing apparatus is requested to register the same reservation as the reservation requested to be deleted. A reservation system including an information processing device that performs processing related to resource reservation and an information processing terminal that displays information related to the resource received from the information processing device.
The information processing device is
The usage management unit that accepts the start of use of the resource,
The usage management unit has a reservation control unit that changes the reservation of the resource to the first status when the first time elapses from the usage start time of the resource without accepting the start of use of the resource. death,
From the lapse of the first time to the lapse of the second time, the acceptance of the start of use of the reservation of the first status and the new time zone overlapping with the reservation of the first status Of the reservation registrations, the earlier one is given priority and processed.
The information processing terminal is
The communication unit that receives the information about the reservation changed to the first status,
A display control unit that displays that the resource can be used by anyone other than the reserved person according to the first status.
A reservation system characterized by having. The fifth aspect of the present invention is characterized in that the display control unit displays a first display component that accepts the start of use of the resource in the first status and a second display component that accepts the registration of a new reservation. Reservation system described. When the information processing terminal accepts the pressing of the first display component, the communication unit transmits to the information processing apparatus that the pressing of the first display component has been accepted.
The usage management unit of the information processing apparatus accepts the start of use of the reservation of the first status in response to the acceptance of the pressing of the first display component.
When the information processing terminal accepts the pressing of the second display component, the communication unit transmits to the information processing apparatus that the pressing of the second display component has been accepted.
The reservation system according to claim 6, wherein the information processing apparatus accepts registration of a new reservation in a time zone overlapping with the reservation of the first status. It is a reservation processing method by an information processing device that performs processing related to resource reservation.
The step in which the usage management department accepts the start of use of the resource,
When the first time elapses from the usage start time of the resource without the usage management unit accepting the start of use of the resource, the reservation control unit changes the reservation of the resource to the first status. ,
From the lapse of the first time to the lapse of the second time, the acceptance of the start of use of the reservation of the first status and the new time zone overlapping with the reservation of the first status Of the reservation registration, the step to process the earlier one with priority,
A reservation processing method characterized by having.

Images