Server device, system, server device control method and program

Abstract

Provided is a server device for realizing a cancellation standby reservation of a guest room of a hotel. This server device comprises an inventory management means and a control means. The inventory management means manages an inventory of guest rooms in a host hotel. The control means receives a cancellation standby reservation of a guest room when the inventory of guest rooms is depleted.

Description

Server device, system, server device control method and storage medium

[0001] The present invention relates to a server device, a system, a method for controlling a server device, and a storage medium.

[0002] There are technologies for booking hotels and other facilities.

[0003] For example, Patent Document 1 states that a reservation system and a reservation method are provided that increase user satisfaction by offering fees that appropriately correspond to the added value of services, and stabilize revenues by securing a stable number of users.

[0004] International Publication No. 2021 / 014510

[0005] There are several ways for users to reserve hotel rooms, including through the hotel's own website, through a travel agency, or through an OTA (Online Travel Agent) website. However, these methods do not allow for reservation on a waiting list for hotel rooms. For example, if an OTA website accepts a reservation on a waiting list, it is difficult to handle the situation if the reservation is not fulfilled, so cancellation waiting reservations are not made. On the other hand, hotels have a need to allow reservation on a waiting list for rooms in case a reserved room is canceled.

[0006] A primary object of the present invention is to provide a server device, a system, a method for controlling a server device, and a storage medium that contribute to realizing waiting list reservations for hotel rooms.

[0007] According to a first aspect of the present invention, there is provided a server device comprising an inventory management means for managing the inventory of guest rooms in its own hotel, and a control means for accepting standby reservations for the guest rooms when the inventory of the guest rooms runs out.

[0008] According to a second aspect of the present invention, there is provided a system including a hotel server that manages the inventory of hotel rooms and accepts reservations for the rooms, and a reservation management server that manages the reservation status of rooms by a plurality of reservation servers including the hotel server, wherein when the hotel runs out of room inventory, the reservation management server notifies the plurality of reservation servers including the hotel server that the hotel rooms are out of inventory, the plurality of reservation servers stop selling the rooms that are out of inventory, and the hotel server accepts waiting reservations for the rooms that are out of inventory.

[0009] According to a third aspect of the present invention, there is provided a method for controlling a server device, the method including an inventory management process for managing the inventory of guest rooms in the server device, and a control process for accepting standby reservations for the guest rooms when the inventory of the guest rooms runs out.

[0010] According to a fourth aspect of the present invention, there is provided a computer-readable storage medium that stores a program for causing a computer mounted on a server device to execute an inventory management process for managing the inventory of guest rooms in the hotel, and a control process for accepting standby reservations for the guest rooms when the inventory of the guest rooms runs out.

[0011] According to each aspect of the present invention, a server device, a system, a control method for a server device, and a storage medium are provided that contribute to realizing waiting list reservations for hotel rooms. Note that the effects of the present invention are not limited to those described above. The present invention may achieve other effects instead of or in addition to the effects described above.

[0012] FIG. 1 is a diagram illustrating an overview of an embodiment. FIG. 2 is a flowchart illustrating an overview of an operation of an embodiment. FIG. 3 is a diagram illustrating an example of a schematic configuration of an information processing system according to a first embodiment. FIG. 4 is a diagram illustrating the operation of the information processing system according to the first embodiment. FIG. 5 is a diagram illustrating the operation of the information processing system according to the first embodiment. FIG. 6 is a diagram illustrating the operation of the information processing system according to the first embodiment. FIG. 7 is a diagram illustrating the operation of the information processing system according to the first embodiment. FIG. 8 is a diagram illustrating an example of a processing configuration of a reservation management server according to the first embodiment. FIG. 9 is a diagram illustrating an example of a reservation status management database according to the first embodiment. FIG. 10 is a diagram illustrating an example of reservation status information according to the first embodiment. FIG. 11 is a diagram illustrating an example of a first cancellation waiting management database according to the first embodiment. FIG. 12 is a flowchart illustrating an example of an operation of a reservation management server according to the first embodiment. FIG. 13 is a diagram illustrating an example of a processing configuration of a hotel server according to the first embodiment. FIG. 14 is a diagram illustrating an example of an inventory management database according to the first embodiment. FIG. 15 is a diagram illustrating an example of a display on a terminal according to the first embodiment. FIG. 16 is a diagram illustrating an example of a processing configuration of a control server according to the first embodiment. Fig. 17 is a diagram showing an example of a second waiting list management database according to the first embodiment. Fig. 18 is a sequence diagram showing an example of the operation of the information processing system according to the first embodiment. Fig. 19 is a diagram showing an example of a display on a terminal according to the first embodiment. Fig. 20 is a diagram showing an example of a schematic configuration of an information processing system according to a modified example of the first embodiment. Fig. 21 is a diagram showing an example of a display on a terminal according to a modified example of the first embodiment. Fig. 22 is a diagram showing an example of a display on a terminal according to a modified example of the first embodiment. Fig. 23 is a diagram showing an example of the hardware configuration of a hotel server according to the present disclosure.

[0013] First, an overview of one embodiment will be described. Note that the reference numerals in the drawings are added to each element for convenience as an example to facilitate understanding, and the description of this overview is not intended to be limiting in any way. Furthermore, unless otherwise specified, the blocks shown in each drawing represent functional units, not hardware units. Connection lines between blocks in each drawing include both bidirectional and unidirectional lines. Unidirectional arrows are used to schematically indicate the flow of the main signal (data) and do not exclude bidirectionality. Note that in this specification and drawings, elements that can be similarly described may be assigned the same reference numerals to avoid redundant explanation.

[0014] The server device 100 according to one embodiment includes an inventory management unit 101 and a control unit 102 (see FIG. 1). The inventory management unit 101 manages the inventory of guest rooms in the hotel (step S1 in FIG. 2). The control unit 102 accepts a waiting list reservation for a guest room when the hotel runs out of room inventory (step S2).

[0015] The server device 100 provides a hotel reservation site that handles rooms in its own hotel and accepts reservations for rooms on a waiting list when the room is out of stock. Because the server device 100 is operated by the hotel itself, even if the room originally requested by the applicant for the waiting list reservation cannot be secured, the hotel can flexibly respond by allocating a room of a higher grade than the requested room. In other words, even if no cancellation occurs for the room for which a waiting list reservation has been made, the server device 100 can fulfill the waiting list reservation. As a result, the hotel can realize (implement) waiting list reservations for hotel rooms with peace of mind.

[0016] Specific embodiments will be described in more detail below with reference to the drawings.

[0017] First Embodiment The first embodiment will be described in more detail with reference to the drawings.

[0018] [System Configuration] Fig. 3 is a diagram showing an example of a schematic configuration of an information processing system (hotel reservation system) according to Embodiment 1. As shown in Fig. 3, the information processing system includes a hotel server 10, a travel agency server 11, multiple OTA (Online Travel Agent) servers 20-1 to 20-3, a reservation management server 30, and a control server 40.

[0019] In the following description, unless there is a particular reason to distinguish between the OTA servers 20-1 to 20-3, they will simply be referred to as the "OTA server 20." Similarly, for other elements, the symbol to the left of the hyphen will represent that element.

[0020] The information processing system includes a server that handles hotel reservations, etc. A hotel server 10, a travel agency server 11, and an OTA server 20 accept reservations for rooms from users. In the following description, the hotel server 10, the travel agency server 11, and the OTA server 20 that accept hotel room reservations will be collectively referred to as the "reservation server."

[0021] The information processing system includes a plurality of reservation servers, including a plurality of OTA (Online Travel Agent) servers 20 operated by a plurality of OTA operators.

[0022] The hotel server 10 is a server that allows hotels to directly sell rooms to customers. The hotel server 10 manages the inventory of rooms in the hotel and accepts reservations for rooms. The hotel server 10 implements an accommodation reservation site that handles rooms in the hotel.

[0023] The travel agency server 11 is a server device managed and operated by a travel agency operating in a brick-and-mortar store or the like.

[0024] The OTA server 20 is managed and operated by an OTA operator that sells rooms online. The OTA server 20 implements a hotel reservation site for selling rooms to customers. The OTA operator sells rooms at multiple hotels. In the example of FIG. 3 , the OTA server 20 sells (accepts reservations for) rooms at multiple hotels, including hotels managed and operated by the hotel server 10.

[0025] The reservation servers (hotel server 10, travel agency server 11, OTA server 20) are connected to the reservation management server 30 and the like via a network.

[0026] The reservation management server 30 is also called a site controller. The reservation management server 30 collectively manages the reservation status from each reservation server. Specifically, the reservation management server 30 manages the room availability (room inventory) of each hotel. The reservation management server 30 manages the reservation status of rooms in each of multiple hotels by multiple reservation servers, including the hotel server 10.

[0027] The control server 40 is a server managed and operated by the hotel. The control server 40 performs the main business of the hotel. Specifically, the control server 40 stores reservation information of guests (e.g., name, gender, address, email address, accommodation dates (length of stay; check-in date, check-out date), room type, etc.). The control server 40 uses the reservation information to perform check-in procedures, check-out procedures, etc. for guests.

[0028] A user, a hotel employee, or the like possesses a terminal 50. For example, a user makes a hotel reservation or the like using the terminal 50. Examples of the terminal 50 include a mobile terminal such as a smartphone or a tablet.

[0029] The configuration of the information processing system shown in Figure 3 is an example and is not intended to be limiting. For example, one hotel may include multiple hotel servers 10. Alternatively, the information processing system may include multiple travel agency servers 11.

[0030] Although FIG. 3 illustrates the hotel server 10 and control server 40 corresponding to one hotel, in reality the information processing system includes hotel servers 10 and control servers 40 corresponding to multiple hotels.

[0031] [Overall Operation] Next, an overall operation of the information processing system according to the first embodiment will be described.

[0032] <Room Reservation> Here, a case where a user makes a hotel reservation using the OTA server 20 will be described.

[0033] The reservation management server 30 manages the status (reservation status) of hotel rooms. The reservation management server 30 stores the total number of rooms available for sale and the number of rooms for which sales have been completed (reservations have been made) for each hotel. The reservation status is also shared with the reservation servers (hotel server 10, travel agency server 11, OTA server 20).

[0034] The user operates the terminal 50 to access the accommodation reservation site provided by the reservation server (here, as described above, the OTA server 20). In response to the user's access, the OTA server 20 presents the user with rooms available for sale (reservable by the user) based on the reservation status notified by the reservation management server 30.

[0035] When a user operates the terminal 50 to apply for a reservation, the OTA server 20 notifies the reservation management server 30 of the reservation information of the room reservation person (e.g., the name, gender, address, email address, accommodation date (length of stay), room type, etc.) of the room reservation person. Specifically, the OTA server 20 transmits a "room reservation notification" including the reservation information and the hotel ID to the reservation management server 30 (step S01 in FIG. 4).

[0036] The hotel ID is an ID for identifying each hotel. Examples of the hotel ID include the name of the hotel and a predetermined code. The hotel ID is shared by any method among the entities participating in the system. For example, the system administrator determines the hotel ID and sets the determined hotel ID in the reservation management server 30. The system administrator also notifies the OTA operator of the determined hotel ID. Each OTA operator sets the notified hotel ID in its own OTA server 20.

[0037] In response to receiving the room reservation notification, the reservation management server 30 updates the hotel reservation status. After updating the reservation status, the reservation management server 30 notifies the reservation servers of the updated reservation status. Specifically, the reservation management server 30 generates reservation status information based on the latest reservation status. The reservation management server 30 sends a "reservation status notification" including the generated reservation status information to each reservation server (step S02).

[0038] Upon receiving the reservation status notification, each reservation server updates the hotel reservation status (room availability, inventory status) held by the server itself.

[0039] When there are no more rooms available for sale, the reservation management server 30 generates reservation status information indicating that there are no more rooms in stock. The reservation management server 30 then sends a reservation status notification including the generated reservation status information to each reservation server. Upon receiving the notification, each reservation server becomes aware that there are no more rooms in stock. Each reservation server then stops selling the rooms that are out of stock.

[0040] In this way, when a room currently on sale becomes fully booked, the reservation management server 30 notifies each reservation server (hotel server 10, travel agency server 11, OTA server 20) that the room is out of stock. In response to this notification, the OTA server 20 etc. stops accepting new reservations. When the room is out of stock, the reservation servers (hotel server 10, travel agency server 11, OTA server 20) will not accept room reservations (normal room reservations) from users.

[0041] That is, when a hotel runs out of rooms, the reservation management server 30 notifies multiple reservation servers, including the hotel server 10 corresponding to that hotel, that the hotel rooms are out of stock. The multiple reservation servers stop selling the rooms that are out of stock.

[0042] Furthermore, upon receiving the room reservation notification, the reservation management server 30 transfers the received room reservation notification to the control server 40 (step S03).

[0043] The control server 40 stores the reservation information included in the room reservation notice. As described above, the reservation information is used for the check-in procedure of the guest.

[0044] <Cancellation of Room> A user who has made a room reservation can cancel the reservation. To cancel a room reservation, the user notifies the business that sold the room. For example, a user who has made a room reservation through an OTA business (OTA server 20) logs in to their account on the OTA server 20 and performs the procedure to cancel the room reservation.

[0045] When a cancellation is accepted, the reservation server (hotel server 10, travel agency server 11, OTA server 20) notifies the reservation management server 30. The reservation server sends a "cancellation notice" to the reservation management server 30, which includes information about the canceled reservation (cancellation information; for example, the name, gender, address, email address, accommodation dates, room type, etc. of the person canceling the reservation) and the hotel ID (step S11 in FIG. 5).

[0046] In response to receiving the cancellation notice, the reservation management server 30 updates the hotel reservation status. Specifically, the reservation management server 30 updates the hotel reservation status in the same way as when it receives a room reservation notice. The reservation management server 30 notifies the reservation server of the updated reservation status using the cancellation information included in the cancellation notice (step S12). The reservation management server 30 also forwards the cancellation notice to the control server 40 (step S13).

[0047] Upon receiving the reservation status notification, each reservation server updates the hotel reservation status (room availability, inventory status) held by the server itself. The reservation server recognizes that the cancellation of a room has increased the number of rooms available for sale. Furthermore, upon receiving the cancellation notification, the control server 40 recognizes that a cancellation has occurred for a room at its own hotel.

[0048] <Waiting for Room Cancellations> Among the multiple reservation sites, the hotel's own website accepts reservations for rooms that have sold out. The hotel server 10 accepts reservations for rooms that are out of stock. The travel agency server 11 and the OTA server 20 do not accept reservations for rooms that have been cancelled.

[0049] Specifically, when the hotel server 10 runs out of rooms, it accepts a request for a reservation for a room on a waiting list while clearly informing the customer (user) that the room is on a waiting list (see FIG. 6).

[0050] When the hotel server 10 accepts a reservation on the waiting list from a customer, it notifies the reservation management server 30 of information about the reservation on the waiting list. The hotel server 10 notifies the reservation management server 30 of information about the applicant who has applied for the reservation on the waiting list and information about the target room.

[0051] Specifically, the hotel server 10 sends a "cancellation waiting notice" including cancellation waiting information (e.g., the applicant's name, gender, address, email address, accommodation date (length of stay), room type, etc.) and the hotel ID to the reservation management server 30 (step S21 in Figure 6).

[0052] The reservation management server 30 stores information about the reservation on the waiting list notified by the hotel server 10, and notifies the control server 40 of the information about the reservation on the waiting list. Specifically, upon receiving a notification of the reservation on the waiting list, the reservation management server 30 stores the information included in the notification (hotel ID and cancellation waiting information) in a first cancellation waiting management database. Details of the first cancellation waiting management database will be described later.

[0053] Furthermore, the reservation management server 30 transfers the received cancellation waiting notice to the control server 40 (step S22).

[0054] The control server 40 stores information about the cancellation standby reservations notified by the reservation management server 30. Specifically, the control server 40 stores the information included in the received cancellation standby notification in a second cancellation standby management database. Details of the second cancellation standby management database will be described later.

[0055] <Notification of Cancellation Waiting Result> When the reservation management server 30 receives a "cancellation notification" from the reservation server (step S31 in FIG. 7), it determines whether a cancellation waiting reservation has been set for the canceled room.

[0056] If the canceled room is not set as a waiting room, the reservation management server 30 executes the same process as for a normal reservation cancellation.

[0057] If a cancellation standby reservation has been set for the canceled room, the reservation management server 30 changes the cancellation standby reservation to a formal reservation. In this case, the reservation management server 30 notifies the control server 40 of information about the cancellation standby reservation that has been changed to a formal reservation (confirmed cancellation standby information).

[0058] The reservation management server 30 sends a "cancellation waiting status confirmation notice" to the control server 40, which includes confirmed cancellation waiting status information (e.g., the applicant's name, gender, address, email address, accommodation date (length of stay), room type) (step S32 in Figure 7).

[0059] The control server 40 notifies the applicant of the cancellation waiting reservation that the reservation has been officially made (that the cancellation waiting reservation has become an official reservation). The control server 40 sends a "formal reservation notification" including information about the reservation that has been made official to the terminal 50 of the cancellation waiting applicant (cancellation waiting reservation applicant) (step S33).

[0060] In this way, the reservation management server 30 receives a cancellation notice for a reserved room from one of the multiple reservation servers. If a cancellation standby reservation has been set for the canceled room, the reservation management server 30 establishes the cancellation standby reservation. The reservation management server 30 sends a cancellation standby establishment notice including information about the established cancellation standby reservation to the control server 40. The control server 40 notifies the applicant of the established cancellation standby reservation that the cancellation standby reservation has been established.

[0061] If no cancellation occurs for the room for which the waiting list has been set at a predetermined time, the control server 40 performs a predetermined process for the waiting list reservation. For example, if there is a room available that is of a higher grade than the room for which the waiting list reservation has been made, the control server 40 assigns the higher grade room to the waiting list reservation. In this way, if the control server 40 does not receive a notice of the waiting list establishment by a predetermined date, the control server 40 may assign a room of a higher grade than the room for which the waiting list reservation has been accepted, and establish the waiting list reservation.

[0062] In this case, the control server 40 also sends a "formal reservation notification" to the terminal 50 of the person on the waiting list. Furthermore, if the waiting list is changed to a formal reservation by upgrading the room grade, the control server 40 notifies the reservation management server 30 of this.

[0063] Specifically, the control server 40 sends a "standby cancellation notice" including information (applicant's name, hotel ID, accommodation date, room type, etc.) that identifies the standby reservation that has been changed to an official reservation (standby reservation) to the reservation management server 30. Upon receiving this notice, the reservation management server 30 deletes the corresponding standby reservation from the first standby management database.

[0064] In this way, if no cancellation of the room reservation occurs, the control server 40 will, at a predetermined timing (for example, a few days before the accommodation date of the waiting-for-cancellation reservation), make the waiting-for-cancellation reservation an official reservation by upgrading the room grade from that of the canceled room. The control server 40 notifies the guest that the room grade has been upgraded from that at the time of the waiting-for-cancellation reservation application and that the reservation has become official by sending an official reservation notification to the terminal 50.

[0065] Alternatively, if there are no available rooms of a higher grade than the room for which the waiting reservation has been made, the control server 40 notifies the waiting reservation applicant that the waiting reservation cannot be made into an official reservation. Specifically, the control server 40 sends a "waiting reservation non-establishment notice" to the waiting reservation applicant's terminal 50. Furthermore, the control server 40 sends a "waiting reservation cancellation notice" to the reservation management server 30 that includes information identifying the waiting reservation to be canceled (waiting reservation).

[0066] The waiting list applicant displays a message based on the notification (formal reservation notification, cancellation waiting not accepted notification) received from the control server 40.

[0067] Next, details of each device included in the information processing system according to the first embodiment will be described.

[0068] [Reservation Management Server] Fig. 8 is a diagram showing an example of the processing configuration (processing modules) of the reservation management server 30 according to the first embodiment. Referring to Fig. 8, the reservation management server 30 includes a communication control unit 201, a reservation status control unit 202, a cancellation waiting control unit 203, and a storage unit 204.

[0069] The communication control unit 201 is a means for controlling communication with other devices. For example, the communication control unit 201 receives data (packets) from the OTA server 20. The communication control unit 201 also transmits data to the OTA server 20. The communication control unit 201 passes data received from other devices to other processing modules. The communication control unit 201 transmits data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data to and from other devices via the communication control unit 201. The communication control unit 201 has a function as a receiving unit that receives data from other devices and a function as a transmitting unit that transmits data to other devices.

[0070] The reservation status control unit 202 is a means for controlling the reservation status (vacant room status) of each hotel.

[0071] The reservation status control unit 202 obtains the total number of rooms available for sale at each hotel using any means. For example, the reservation status control unit 202 provides an interface that enables employees of each hotel to register the total number of rooms (total number of rooms for each room type) in the reservation management server 30. Alternatively, the reservation status control unit 202 obtains the total number of rooms from the control server 40.

[0072] The reservation status control unit 202 manages the reservation status of each hotel using a reservation status management database (see FIG. 9). As shown in FIG. 9, the reservation status management database stores the total number of rooms and the number of reservations for each hotel's business day and room type. Note that the reservation status management database shown in FIG. 9 is an example and is not intended to limit the items stored therein.

[0073] The reservation status control unit 202 receives room reservation notifications and cancellation notifications from the reservation server. In response to receiving the room reservation notifications and cancellation notifications, the reservation status control unit 202 updates the reservation status management database.

[0074] Specifically, the reservation status control unit 202 identifies an entry (entry in the reservation status management database) corresponding to the user's reservation using the hotel ID, accommodation date (stay period), and room type included in the room reservation notification. The reservation status control unit 202 increments the setting value in the reservation quantity field of the identified entry to update the reservation status management database.

[0075] When the reservation status management database is updated, the reservation status control unit 202 notifies each reservation server of the updated reservation status. Specifically, the reservation status control unit 202 generates reservation status information based on the information stored in the reservation status management database. The reservation status information is information about rooms available for sale by each reservation server (room inventory status).

[0076] The reservation status control unit 202 generates reservation status information for a hotel where there has been a change in inventory (a hotel corresponding to the hotel ID included in the room reservation notification). For example, as shown in Fig. 10, the reservation status control unit 202 generates reservation status information including the hotel ID of the hotel where there has been a change in inventory, the business day on which the change in inventory occurred, and the number of rooms available for sale for the room type.

[0077] The reservation status control unit 202 transmits a "reservation status notification" including the generated reservation status information to each reservation server.

[0078] When hotel rooms are sold out (when all reservations are filled), the reservation status control unit 202 sets the inventory in the reservation status information shown in Fig. 10 to "0." The reservation status control unit 202 notifies each reservation server that the room reservations have been completed by sending a reservation status notification to the reservation server, the reservation status information including the inventory set to "0."

[0079] When the reservation status control unit 202 receives a cancellation notice, it determines whether or not the room for which the reservation has been canceled is in stock. If a room that is in stock is canceled, the reservation status control unit 202 updates the reservation status management database in the same way as when a room reservation notice is received.

[0080] Specifically, the reservation status control unit 202 identifies the entry corresponding to the canceled reservation using the hotel ID, accommodation date (stay period), and room type included in the cancellation notice. The reservation status control unit 202 decrements the setting value in the reservation quantity field of the identified entry and updates the reservation status management database.

[0081] The reservation status control unit 202 then notifies each reservation server of the updated reservation status. The reservation status control unit 202 transmits a reservation status notification to each reservation server, including reservation status information for hotels whose inventory has changed.

[0082] In addition, when a reservation status notification is sent to each reservation server in response to receiving a room reservation notification or a cancellation notification, the reservation status control unit 202 transfers the received room reservation notification or cancellation notification to the control server 40.

[0083] Furthermore, when a room that is out of stock is canceled, the reservation status control unit 202 passes the cancellation notice received from the reservation server to the cancellation waiting control unit 203 .

[0084] The cancellation waiting control unit 203 is a means for executing control related to cancellation waiting reservations. The cancellation waiting control unit 203 processes cancellation notifications acquired from the reservation status control unit 202 when there is no inventory and cancellation waiting notifications received from the hotel server 10.

[0085] First, the operation of the cancellation waiting control unit 203 when a cancellation waiting notice is received will be described.

[0086] The cancellation standby control unit 203 stores the information contained in the received cancellation standby notice in a first cancellation standby management database (see FIG. 11 ). As shown in FIG. 11 , the first cancellation standby management database stores the hotel ID, the cancellation standby application date (the date the cancellation standby notice was received), the name of the person making the cancellation standby reservation, and the room for which the cancellation standby reservation is made (date of stay, room type). Note that the first cancellation standby management database shown in FIG. 11 is an example and is not intended to limit the items to be stored.

[0087] The cancellation waiting control unit 203 transfers the received cancellation waiting notice to the control server 40 .

[0088] Next, the operation of the cancellation waiting control unit 203 when a cancellation notice is received from the reservation status control unit 202 will be described.

[0089] When the cancellation notice is received from the reservation status control unit 202, the cancellation waiting control unit 203 determines whether or not a cancellation waiting reservation has been set for the canceled room.

[0090] Specifically, the cancellation standby control unit 203 searches the first cancellation standby management database using information identifying the reservation to be canceled (hotel ID, accommodation date, room type, etc.) included in the cancellation notice as a key.

[0091] If a corresponding entry is not stored in the first cancellation standby management database, the cancellation standby control unit 203 sends a reservation status notification including reservation status information reflecting the cancellation of the reservation to the reservation server, similar to the reservation status control unit 202. By sending this notification, the cancellation standby control unit 203 notifies each reservation server that the canceled room is now available for sale.

[0092] If a corresponding entry is stored in the first cancellation waiting management database, the cancellation waiting control unit 203 executes processing to change the cancellation waiting reservation into a formal reservation.

[0093] Specifically, the cancellation standby control unit 203 identifies the earliest cancellation standby reservation (entry in the first cancellation standby management database) for which a cancellation standby reservation has been applied. The cancellation standby control unit 203 generates confirmed cancellation standby information using the information from the identified entry. The confirmed cancellation standby information includes the name, gender, address, email address, accommodation date (length of stay), room type, etc. of the cancellation standby applicant.

[0094] The cancellation waiting control unit 203 sends a "cancellation waiting completion notification" including information identifying the canceled reservation and the generated completed cancellation waiting information to the control server 40 of the hotel that has the room for which the cancellation waiting reservation has been completed.

[0095] Furthermore, the cancellation standby control unit 203 processes the "cancellation standby cancellation notice" received from the control server 40. The cancellation standby control unit 203 searches the first cancellation standby management database using information identifying the cancellation standby reservation to be canceled (applicant name, hotel ID, accommodation date, room type) as a key. The cancellation standby control unit 203 deletes the entry identified by the search from the first cancellation standby management database.

[0096] The storage unit 204 is a means for storing information necessary for the operation of the reservation management server 30 .

[0097] The operation of the reservation management server 30 regarding the control of reservations on the cancellation waiting list (the operation when a cancellation notice is received) can be summarized as shown in the flowchart in FIG.

[0098] The reservation management server 30 determines whether the room corresponding to the cancellation notice is in stock (step S101).

[0099] If there is room availability (step S102, Yes branch), the reservation management server 30 updates the reservation status of the corresponding hotel (step S103), and notifies each reservation server of the updated reservation status.

[0100] If there is no room in stock (step S102, No branch), the reservation management server 30 determines whether or not a cancellation waiting list has been set for the canceled room (step S104).

[0101] If the canceled room is not on a waiting list (step S105, No branch), the reservation management server 30 updates the reservation status of the corresponding hotel (step S103). The reservation management server 30 notifies each reservation server of the updated reservation status.

[0102] If a cancellation standby reservation has been set for the canceled room (step S105, Yes branch), the reservation management server 30 changes the cancellation standby reservation to a formal reservation. The reservation management server 30 then sends a cancellation standby establishment notification to the control server 40 (step S106).

[0103] [Hotel Server] Fig. 13 is a diagram showing an example of the processing configuration (processing modules) of the hotel server 10 according to the first embodiment. Referring to Fig. 13, the hotel server 10 includes a communication control unit 301, a reservation control unit 302, an inventory management unit 303, and a storage unit 304.

[0104] The communication control unit 301 is a means for controlling communication with other devices. For example, the communication control unit 301 receives data (packets) from the reservation management server 30. The communication control unit 301 also transmits data to the reservation management server 30. The communication control unit 301 passes data received from other devices to other processing modules. The communication control unit 301 transmits data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data to and from other devices via the communication control unit 301. The communication control unit 301 has a function as a receiving unit that receives data from other devices and a function as a transmitting unit that transmits data to other devices.

[0105] The reservation control unit 302 is a means for controlling hotel (guest room) reservations made by users. The reservation control unit 302 realizes the functions of an accommodation reservation site, etc. The reservation control unit 302 accepts regular reservations for guest rooms, cancellations of reserved rooms, and waiting lists for reserved rooms. In particular, the reservation control unit 302 accepts waiting lists for cancellations of rooms when the hotel runs out of room inventory.

[0106] The reservation control unit 302 uses the reservation status of the hotel to generate information about rooms to be presented to users on the accommodation reservation site.

[0107] The reservation control unit 302 refers to the inventory management database and acquires information on rooms available for sale to users (see FIG. 14). The inventory management database shown in FIG. 14 is an example and is not intended to limit the items stored therein.

[0108] The reservation control unit 302 accepts regular reservations for rooms that are in stock, and accepts waiting reservations for rooms that are out of stock.

[0109] When a user performs a predetermined operation on the accommodation reservation site, the reservation control unit 302 displays a GUI (Graphical User Interface) such as that shown in Fig. 15 on the user's terminal 50. The reservation control unit 302 accepts regular room reservations and reservation on a waiting list. In this case, the reservation control unit 302 clearly indicates the existence of a risk that the reservation will not be finalized for a reservation on a waiting list, and accepts the reservation on a waiting list.

[0110] When the user completes the selection of a regular reservation or a waiting list reservation (presses the “Next” button shown in FIG. 15), the reservation control unit 302 acquires the name, gender, address, email address, etc. of the person making the reservation or the person applying for the waiting list.

[0111] When a regular reservation is accepted, the reservation control unit 302 sends a room reservation notification to the reservation management server 30, which includes the hotel ID and reservation information (reservation person's name, gender, address, email address, stay date, room type, etc.).

[0112] When a reservation for a waiting list is accepted, the reservation control unit 302 sends a waiting list notification to the reservation management server 30, which includes the hotel ID and waiting list information (the name, gender, address, email address, accommodation date, room type, etc. of the waiting list applicant).

[0113] As described above, the reservation control unit 302 accepts cancellation of a room reserved by a user. When a cancellation of a reservation is accepted, the reservation control unit 302 sends a cancellation notice to the reservation management server 30, which includes the hotel ID and cancellation information (such as the name, gender, address, email address, accommodation date, and room type of the person canceling the reservation).

[0114] The inventory management unit 303 is a means for controlling and managing the inventory of guest rooms available for sale by the hotel server 10. The inventory management unit 303 manages the inventory of guest rooms in its own hotel.

[0115] The inventory management unit 303 receives reservation status notifications from the reservation management server 30. The inventory management unit 303 processes the reservation status notification for its own hotel based on the hotel ID included in the reservation status notification. The inventory management unit 303 reflects the inventory quantity for each business day and room type included in the notification in the corresponding entry of the inventory management database (overwriting the set value in the inventory quantity field).

[0116] The storage unit 304 is a means for storing information necessary for the operation of the hotel server 10 .

[0117] 16 is a diagram showing an example of the processing configuration (processing modules) of the control server 40 according to the first embodiment. Referring to Fig. 16, the control server 40 includes a communication control unit 401, a reservation information control unit 402, a cancellation waiting control unit 403, and a storage unit 404.

[0118] The communication control unit 401 is a means for controlling communication with other devices. For example, the communication control unit 401 receives data (packets) from the reservation management server 30. The communication control unit 401 also transmits data to the reservation management server 30. The communication control unit 401 passes data received from other devices to other processing modules. The communication control unit 401 transmits data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data to and from other devices via the communication control unit 401. The communication control unit 401 has a function as a receiving unit that receives data from other devices and a function as a transmitting unit that transmits data to other devices.

[0119] The reservation information control unit 402 is a means for controlling room reservations at the hotel itself, and processes room reservation notifications and cancellation notifications received from the reservation management server 30.

[0120] The reservation information control unit 402 stores reservation information (for example, the name, gender, address, date of birth, etc. of the person making the reservation) included in the room reservation notification. The reservation information is used for the check-in procedure of the guest.

[0121] In addition, the reservation information control unit 402 manages the hotel's inventory in response to receiving a room reservation notification. The reservation information control unit 402 reduces the room inventory for the reserved stay date (scheduled stay date) and room type.

[0122] The reservation information control unit 402 identifies the canceled reservation based on the cancellation information included in the cancellation notice (e.g., the name of the person canceling the reservation, the date of stay, the room type, etc.), and deletes the reservation information corresponding to the identified reservation.

[0123] In addition, the reservation information control unit 402 updates the hotel's inventory in response to receiving the cancellation notice. The reservation information control unit 402 increases the room inventory for the cancelled stay date (scheduled stay date) and room type.

[0124] The cancellation waiting control unit 403 is a means for controlling cancellation waiting reservations.

[0125] The cancellation standby control unit 403 receives a cancellation standby notification from the reservation management server 30. The cancellation standby control unit 403 stores the cancellation standby information included in the notification (such as the name, gender, address, email address, accommodation dates, and room type of the cancellation standby reservation applicant) in a second cancellation standby management database (see FIG. 17 ).

[0126] The cancellation waiting control unit 403 receives a cancellation waiting establishment notification from the reservation management server 30. The cancellation waiting control unit 403 deletes the reservation information corresponding to the canceled reservation based on the information included in the notification that identifies the canceled reservation (such as the name of the person who canceled, the date of stay, and the room type).

[0127] Furthermore, the cancellation waiting control unit 403 deletes the entry in the second cancellation waiting management database that corresponds to the cancellation waiting establishment notification.

[0128] Furthermore, the cancellation waiting control unit 403 generates reservation information based on the established cancellation waiting information included in the cancellation waiting establishment notice, and stores the generated reservation information. Specifically, the cancellation waiting control unit 403 stores the name, gender, address, email address, accommodation date (accommodation period), room type, etc. of the cancellation waiting applicant as reservation information.

[0129] Upon receiving the cancellation standby establishment notice, the cancellation standby control unit 403 notifies the cancellation standby reservation applicant that the cancellation standby has been established. The cancellation standby control unit 403 then sends a "formal reservation notice" including information about the officially reserved room (such as the accommodation date and room type) to the applicant's terminal 50.

[0130] The cancellation standby control unit 403 accesses the second cancellation standby management database periodically or at a predetermined timing. The cancellation standby control unit 403 extracts, from the entries in the database, entries for which the number of days until the accommodation date (scheduled accommodation date) is a predetermined number of days or less. Specifically, the cancellation standby control unit 403 extracts cancellation standby reservations for which the cancellation standby is not established and for which the number of days until the scheduled accommodation date is less than a predetermined number.

[0131] The cancellation waiting control unit 403 performs a predetermined process on the extracted cancellation waiting reservation. Specifically, if there is a room available that is of a higher grade than the room for which the cancellation waiting reservation has been made, the cancellation waiting control unit 403 assigns the higher grade room to the room for the cancellation waiting reservation.

[0132] In this case, the cancellation waiting control unit 403 sends a "formal reservation notification" to the terminal 50 of the cancellation waiting applicant, which includes information about the room assigned to the cancellation waiting applicant as a formal reservation (date of stay, room type after upgrade, etc.).

[0133] Furthermore, when a reservation on the waiting list is changed to a formal reservation by upgrading the room grade, the waiting list control unit 403 notifies the reservation management server 30 that the reservation on the waiting list (reservation on the waiting list) has been canceled. The waiting list control unit 403 sends a "notice of cancellation of cancellation" to the reservation management server 30, which includes information identifying the reservation on the waiting list that has been changed to a formal reservation (such as the applicant's name, hotel ID, accommodation date, and room type).

[0134] If there are no available rooms of a higher grade than the room for which the standby reservation was made, the standby control unit 403 notifies the standby reservation applicant that the standby reservation cannot be made into an official reservation. The standby control unit 403 sends a "standby reservation failure notice" to the standby applicant's terminal 50, which includes information about the failed standby reservation, to the standby applicant's terminal 50. In this case as well, the standby control unit 403 sends a standby cancellation notice to the reservation management server 30.

[0135] Note that the room of a higher grade than the room for which the above-mentioned standby reservation has been made may be a room available for sale by the OTA server 20, etc., or may be a room that is not available for sale by the OTA server 20, etc. For example, a room that the hotel has reserved for its own business activities may be allocated as a room for a standby reservation. Furthermore, when a room available for sale by the OTA server 20, etc. is allocated as a room for a standby reservation, the control server 40 transmits a room reservation notification for the allocated room (higher grade room) to the reservation management server 30.

[0136] The storage unit 404 is a means for storing information necessary for the operation of the control server 40 .

[0137] [Travel Agency Server] Detailed description of the configuration and operation of the travel agency server 11 will be omitted, as the operation of the travel agency server 11 is obvious to those skilled in the art.

[0138] [OTA Server] A detailed description of the configuration and operation of the OTA server 20 will be omitted because the operation of the OTA server 20 is clear to those skilled in the art.

[0139] [Terminal] Examples of the terminal 50 include a smartphone, a mobile phone, a game console, a mobile terminal device such as a tablet, a computer (personal computer, laptop computer), etc. The terminal 50 can be any equipment or device that can accept user operations and communicate with the hotel server 10, etc. Furthermore, the configuration of the terminal 50 is clear to those skilled in the art, so a detailed description will be omitted.

[0140] [System Operation] Next, the operation of the information processing system according to the first embodiment will be described.

[0141] The operation of the information processing system according to the first embodiment will be described with reference to FIG.

[0142] The reservation management server 30 receives the cancellation notice from the reservation server (step S41).

[0143] If a cancellation standby reservation is set for the canceled reservation, the reservation management server 30 establishes the cancellation standby reservation. The reservation management server 30 transmits a cancellation standby establishment notification to the control server 40 (step S42).

[0144] The control server 40 notifies the user (waiting list applicant) that the cancellation waiting has been established. The control server 40 transmits a formal reservation notification to the terminal 50 of the waiting list applicant (step S43).

[0145] The terminal 50 outputs a message or the like according to the information contained in the received official reservation notice (step S44). For example, the terminal 50 displays a message as shown in FIG.

[0146] Next, a modification of the first embodiment will be described.

[0147] <Variation 1> In the above embodiment, the case where the site controller (reservation management server 30) is included in the information processing system has been described. The information processing system does not have to include the reservation management server 30. Specifically, as shown in Fig. 20, the functions of the reservation management server 30 described above may be implemented in a control server 40 that handles hotel operations.

[0148] That is, the control server 40 may have a control function related to the reservation management server 30's waiting list reservations in addition to guest check-in procedures.

[0149] Alternatively, the control server 40 may have the functions of the hotel server 10. In this case, the control server 40 only needs to have the function of selling rooms in its own hotel (the function of realizing an accommodation reservation site).

[0150] <Variation 2> When accepting a reservation on a waiting list, the hotel server 10 may inform the user of the hotel's response in the event that the reservation on a waiting list is not fulfilled (the possibility of staying in a higher-grade room without changing the accommodation fee). By responding in this way, the hotel server 10 may create a situation in which more reservations on a waiting list are received.

[0151] Specifically, if the waiting reservation is not fulfilled, the reservation control unit 302 may present to the applicant making the waiting reservation the possibility of staying in a room of a higher grade than the grade of the room for which the waiting reservation has been accepted. For example, the reservation control unit 302 may display a GUI such as that shown in FIG. 21 on the terminal 50.

[0152] <Variation 3> In consideration of user convenience, the hotel server 10 may present to the user the probability that a waiting reservation will be established. The reservation control unit 302 may present to the applicant who requests a waiting reservation the probability that the waiting reservation will be converted into a formal reservation. For example, the reservation control unit 302 may display a GUI such as that shown in FIG. 22 on the terminal 50.

[0153] In this case, the reservation control unit 302 of the hotel server 10 sends a "waiting list success probability calculation request" to the control server 40, which includes information about the room for which the waiting list reservation is made (date of stay, room type).

[0154] Upon receiving this request, the cancellation standby control unit 403 of the control server 40 calculates the probability that the cancellation standby reservation for the specified room will be successful. For example, the cancellation standby control unit 403 calculates this probability based on the hotel's room inventory (the inventory of rooms sold via the reservation server and the inventory of rooms not sold via the reservation server). For example, if the hotel has reserved rooms for commercial use, allocating these commercial rooms to the cancellation standby reservation will result in a high probability of the cancellation standby reservation being successful. In this case, the cancellation standby control unit 403 calculates a high probability close to 100% and notifies the hotel server 10.

[0155] Alternatively, the cancellation waiting control unit 403 may calculate the probability according to the number of days between the application date of the cancellation waiting reservation and the planned accommodation date of the cancellation waiting reservation. For example, the cancellation waiting control unit 403 calculates the probability that the cancellation waiting reservation will be established as the number of days is longer.

[0156] Alternatively, the waitlist control unit 403 may calculate the above probability using a learning model obtained by machine learning. For example, the learning model is obtained by machine learning using a large amount of training data in which labels (whether the waitlist reservation was successful or not) are assigned to past data (the application date for the waitlist reservation, the number of days from the application date to the date of stay, and the grade of the target room). Any algorithm such as a support vector machine, boosting, or neural network can be used to generate the learning model. Note that known technologies can be used for the algorithms such as the support vector machine, and therefore a description thereof will be omitted.

[0157] In this way, the hotel server 10 may provide applicants with the possibility (probability) of being able to stay through a waiting list reservation, creating an environment in which users can apply for a waiting list reservation with peace of mind.

[0158] As described above, in the information processing system according to the first embodiment, the hotel server 10, among the multiple reservation servers, accepts reservations for standby reservations. More specifically, the hotel server 10 accepts reservations for standby reservations for rooms when the hotel runs out of room inventory. Because the hotel server 10 and the control server 40 are operated by the hotel itself, even if the room originally requested by the applicant for the standby reservation cannot be secured, the control server 40 can assign a room of a higher grade than the requested room. In other words, even if no cancellations occur for the room for which a standby reservation has been made, the control server 40 can still fulfill the standby reservation.

[0159] There are multiple ways for users to reserve hotel rooms, including the hotel's own website and accommodation reservation sites provided by OTA operators. While OTA operators are important business partners for hotels, it is difficult for OTA operators to accept reservations for rooms on standby due to complex procedures such as refunds in the event of a failed reservation. On the other hand, hotels may have rooms reserved for their own business use without the involvement of OTA operators, and there is a need to realize reservations for rooms on standby from the perspective of ensuring profits. Therefore, in the information processing system according to the first embodiment, hotels themselves, which are capable of flexibly responding to reservations on standby, accept reservations on standby, thereby maximizing profits.

[0160] Next, the hardware of each device constituting the information processing system will be described. Fig. 23 is a diagram showing an example of the hardware configuration of the hotel server 10.

[0161] The hotel server 10 can be configured using an information processing device (a so-called computer), and has the configuration shown in Fig. 23. For example, the hotel server 10 includes a processor 311, a memory 312, an input / output interface 313, and a communication interface 314. The components such as the processor 311 are connected by an internal bus or the like, and are configured to be able to communicate with each other.

[0162] However, the configuration shown in Fig. 23 is not intended to limit the hardware configuration of the hotel server 10. The hotel server 10 may include hardware not shown, and may not include the input / output interface 313 as necessary. Furthermore, the number of processors 311 and the like included in the hotel server 10 is not intended to be limited to the example shown in Fig. 23; for example, the hotel server 10 may include multiple processors 311.

[0163] The processor 311 is a programmable device such as a central processing unit (CPU), a micro processing unit (MPU), or a digital signal processor (DSP). Alternatively, the processor 311 may be a device such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). The processor 311 executes various programs including an operating system (OS).

[0164] The memory 312 is a random access memory (RAM), a read only memory (ROM), a hard disk drive (HDD), a solid state drive (SSD), etc. The memory 312 stores an OS program, application programs, and various data.

[0165] The input / output interface 313 is an interface for a display device and an input device (not shown). The display device is, for example, a liquid crystal display. The input device is, for example, a keyboard, a mouse, a touch panel, or the like that accepts user operations.

[0166] The communication interface 314 is a circuit, module, etc. that communicates with other devices. For example, the communication interface 314 includes a network interface card (NIC).

[0167] The functions of the hotel server 10 are realized by various processing modules. The processing modules are realized, for example, by the processor 311 executing a program stored in the memory 312. The program can be recorded on a computer-readable storage medium. The storage medium can be a non-transitory medium such as a semiconductor memory, a hard disk, a magnetic recording medium, or an optical recording medium. That is, the present invention can also be embodied as a computer program product. The program can be downloaded via a network or updated using a storage medium storing the program. Furthermore, the processing modules can be realized by semiconductor chips.

[0168] The reservation management server 30, control server 40, etc. can also be configured using information processing devices, just like the hotel server 10, and their basic hardware configurations are no different from those of the hotel server 10, so a description thereof will be omitted.

[0169] The hotel server 10 is equipped with a computer, and the functions of the hotel server 10 can be realized by causing the computer to execute a program. The hotel server 10 also executes a control method for the hotel server 10 by means of the program.

[0170] [Modification] The configuration, operation, etc. of the information processing system described in the above embodiment are merely examples, and are not intended to limit the configuration, etc. of the system.

[0171] In the above embodiment, no limit is placed on the users who can make a reservation on a waiting list for a sold room, but a limit may be placed on the users who can make a reservation on a waiting list for a sold room. For example, the hotel server 10 may limit the number of users who can make a reservation on a waiting list for a room that has already been sold. The hotel server 10 may also limit the number of users who can make a reservation on a waiting list for a single room (business day and room type).

[0172] The control server 40 may instruct the hotel server 10 to stop (prohibit) waiting reservations for rooms for which sales have ended. For example, the control server 40 may instruct the hotel server 10 to stop accepting waiting reservations for rooms for which there is a low possibility (probability) that a waiting reservation will be made. In this case, the control server 40 may transmit information (business days, room type) about the rooms for which waiting reservations will no longer be accepted to the hotel server 10.

[0173] In the above embodiment, the case where the OTA server 20 is included in the information processing system has been described. However, the information processing system does not have to include the OTA server 20. Hotel rooms may be sold by the hotel's own accommodation reservation site and a travel agency. In this case, the information processing system realizes a reservation system for rooms in a single hotel. Alternatively, the travel agency server 11 does not have to be included in the information processing system.

[0174] In the above embodiment, the reservation status management database is configured inside the reservation management server 30, but the database may also be configured on an external database server, etc. In other words, some of the functions of the reservation management server 30 may be implemented in another device. More specifically, the above-described "reservation status control unit (reservation status control means)" and the like may be implemented in any of the devices included in the system.

[0175] There are no particular restrictions on the format of data transmission between each device (reservation server, reservation management server 30), but data transmitted between these devices may be encrypted. User names and other information are transmitted between these devices, and in order to properly protect this information, it is desirable to transmit and receive encrypted data.

[0176] In the flow charts (flowcharts, sequence diagrams) used in the above explanation, multiple steps (processes) are described in order, but the order of execution of the steps executed in the embodiments is not limited to the order described. In the embodiments, the order of the steps shown in the drawings can be changed to the extent that the content is not affected, such as by executing each process in parallel.

[0177] The above-described embodiments have been described in detail to facilitate understanding of the present disclosure, and it is not intended that all of the above-described configurations are required. Furthermore, when multiple embodiments are described, each embodiment may be used alone or in combination. For example, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, it is possible to add, delete, or replace part of the configuration of one embodiment with another configuration.

[0178] From the above explanation, it is clear that the present invention has industrial applicability, and the present invention is suitably applicable to information processing systems for hotel reservations, etc.

[0179] Some or all of the above embodiments may be described as, but are not limited to, the following supplementary notes. [Supplementary Note 1] A server device comprising: inventory management means for managing inventory of guest rooms in its own hotel; and control means for accepting a standby reservation for the room when the inventory of the room runs out. [Supplementary Note 2] The server device described in Supplementary Note 1, wherein, if the standby reservation is not fulfilled, the control means presents to the applicant who makes the standby reservation the possibility of staying in a room of a higher grade than the grade of the room for which the standby reservation was accepted. [Supplementary Note 3] The server device described in Supplementary Note 1 or 2, wherein the control means presents to the applicant who makes the standby reservation the probability that the standby reservation will be changed to a formal reservation. [Supplementary Note 4] A system comprising: a hotel server that manages an inventory of hotel rooms and accepts reservations for the rooms; and a reservation management server that manages the reservation status of rooms by multiple reservation servers including the hotel server, wherein when the hotel room inventory is depleted, the reservation management server notifies the multiple reservation servers including the hotel server that the hotel room inventory is depleted, the multiple reservation servers stop selling the depleted rooms, and the hotel server accepts standby reservations for the depleted rooms. [Supplementary Note 5] The system according to Supplementary Note 4 further comprises a control server operated by the hotel, wherein when the hotel server accepts the standby reservation, the hotel server notifies the reservation management server of information related to the standby reservation, the reservation management server stores information related to the notified standby reservation and notifies the control server of information related to the standby reservation, and the control server stores information related to the notified standby reservation. [Appendix 6] The system described in Appendix 5, wherein the reservation management server receives a cancellation notification of a reserved room from one of the plurality of reservation servers, and if the cancellation standby reservation has been set for the canceled room, establishes the cancellation standby reservation and sends a cancellation standby establishment notification to the control server including information about the established cancellation standby reservation.[Supplementary Note 7] The system described in Supplementary Note 6, wherein the control server notifies the applicant of the confirmed standby reservation that the standby reservation has been confirmed. [Supplementary Note 8] The system described in Supplementary Note 7, wherein, if the control server does not receive the notification that the standby reservation has been confirmed by a specified date, the control server confirms the standby reservation by allocating a room of a higher grade than the room for which the standby reservation was accepted. [Supplementary Note 9] A control method for a server device, comprising, in the server device: an inventory management step of managing inventory of rooms in the hotel itself; and a control step of accepting a standby reservation for the room when the inventory of the room runs out. [Supplementary Note 10] The control method for a server device described in Supplementary Note 9, wherein, if the standby reservation is not confirmed, the control step presents the applicant who applies for the standby reservation with the possibility of staying in a room of a higher grade than the room for which the standby reservation was accepted. [Supplementary Note 11] The control method for a server device according to Supplementary Note 9 or 10, wherein the control step presents to an applicant who makes the waitlist reservation a probability that the waitlist reservation will be changed to a formal reservation. [Supplementary Note 12] A computer-readable storage medium storing a program for causing a computer installed in a server device to execute: an inventory management process for managing inventory of guest rooms at the hotel; and a control process for accepting a waitlist reservation for the room when the inventory of the room is depleted. [Supplementary Note 13] The storage medium according to Supplementary Note 12, wherein the control process presents to an applicant who makes the waitlist reservation a possibility of staying in a room of a higher grade than the grade of the room for which the waitlist reservation was accepted, if the waitlist reservation is not fulfilled. [Supplementary Note 14] The storage medium according to Supplementary Note 12 or 13, wherein the control process presents to an applicant who makes the waitlist reservation a probability that the waitlist reservation will be changed to a formal reservation.

[0180] The disclosures of the above-cited prior art documents are incorporated herein by reference. Although the embodiments of the present invention have been described above, the present invention is not limited to these embodiments. Those skilled in the art will understand that these embodiments are merely illustrative and that various modifications are possible without departing from the scope and spirit of the present invention. In other words, the present invention naturally includes various modifications and alterations that may be made by those skilled in the art in accordance with the entire disclosure, including the claims, and the technical concepts thereof.

[0181] 10 Hotel server 11 Travel agency server 20 OTA server 20-1 OTA server 20-2 OTA server 20-3 OTA server 30 Reservation management server 40 Control server 50 Terminal 100 Server device 101 Inventory management means 102 Control means 201 Communication control unit 202 Reservation status control unit 203 Cancellation waiting control unit 204 Storage unit 301 Communication control unit 302 Reservation control unit 303 Inventory management unit 304 Storage unit 311 Processor 312 Memory 313 Input / output interface 314 Communication interface 401 Communication control unit 402 Reservation information control unit 403 Cancellation waiting control unit 404 Storage unit

Claims

1. An inventory management tool for managing the inventory of guest rooms in the hotel; a control means for accepting standby reservations for the rooms when the rooms are out of stock; A server device comprising:

2. The server device according to claim 1, wherein the control means, if the reservation on the waiting list is not fulfilled, presents to the applicant making the reservation on the waiting list the possibility of staying in a room of a higher grade than the grade of the room for which the reservation on the waiting list has been accepted.

3. 3. The server device according to claim 1, wherein the control means presents to an applicant who applies for the reservation on the waiting list a probability that the reservation on the waiting list will be changed to a formal reservation.

4. a hotel server that manages an inventory of hotel rooms and accepts reservations for the rooms; a reservation management server that manages the reservation status of rooms by a plurality of reservation servers including the hotel server; Including, When the hotel runs out of rooms, the reservation management server notifies the plurality of reservation servers including the hotel server that the hotel runs out of rooms; The plurality of reservation servers stop selling the rooms that have run out of stock, The hotel server accepts reservations for the out-of-stock rooms on a waiting list.

5. a control server operated by the hotel; When the hotel server accepts the reservation on the waiting list, it notifies the reservation management server of information regarding the reservation on the waiting list; the reservation management server stores information about the notified waiting list reservation and notifies the control server of the information about the waiting list reservation; The system of claim 4 , wherein the control server stores information about the notified waitlist reservation.

6. The reservation management server receiving a cancellation notice for a reserved room from one of the plurality of reservation servers; The system described in claim 5, wherein if the cancellation waiting reservation is set for the canceled room, the cancellation waiting reservation is confirmed and a cancellation waiting confirmation notification including information about the confirmed cancellation waiting reservation is sent to the control server.

7. The system according to claim 6 , wherein the control server notifies the applicant of the confirmed reservation on the waiting list that the reservation on the waiting list has been confirmed.

8. The system described in claim 7, wherein if the control server does not receive the notification of cancellation waiting status by a specified date, the control server assigns a room of a higher grade than the room for which the cancellation waiting reservation was accepted, thereby completing the cancellation waiting reservation.

9. In the server device, Inventory management process to manage the inventory of hotel rooms, a control step for accepting standby reservations for the room when the room is out of stock; A method for controlling a server device, comprising:

10. The computer installed in the server device Inventory management process to manage the inventory of hotel rooms, a control process that accepts standby reservations for the rooms when the rooms are depleted; A program to execute.