Information processing device, control method, program

Abstract

This invention provides an information processing device, control method, and program that facilitate online check-in. [Solution] In a check-in management system, a facility terminal that can communicate with a reservation management server that manages customer information of the accommodation facility comprises: a request receiving means for receiving online check-in requests for accommodation reservations from users; an acquisition means for obtaining customer information relating to the user from the reservation management server; and a display control means for controlling the display of a screen for performing online check-in for accommodation reservations using the acquired customer information.

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, a control method, and a program.

Background Art

[0002] Conventionally, check-in reception at a lodging facility has been performed by a staff member registering at the front desk from a staff terminal or by the guest himself / herself registering from a check-in terminal installed at the entrance or the like. In that case, during the time when guests' arrivals are concentrated, there has been a waiting time for check-in registration, resulting in inefficiency.

[0003] Therefore, in Patent Document 1, a method is described in which a customer-side terminal device and a management server on the lodging facility side are connected via the Internet, and the management server accepts check-in via the Internet by the customer operating the terminal device before arriving at the lodging facility.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Disclosure of the Invention

Problems to be Solved by the Invention

[0005] However, in the method described in Patent Document 1, since it is premised on directly connecting the customer's terminal device and the management server on the lodging facility side, the management server only needs to use the information of the customers of its own lodging facility. However, in the case of a service that provides a check-in function for a plurality of lodging facilities, requests are received from customers of a plurality of lodging facilities, and it is necessary to appropriately use the information of the customers of a plurality of lodging facilities.

[0006] Therefore, an object of the present invention is to provide a mechanism for easily performing online check-in.

Means for Solving the Problems

[0007] An information processing device capable of communicating with a management device for managing customer information of an accommodation facility, comprising: a request receiving means for receiving a request from a user for online check-in for a reservation at the accommodation facility; an acquisition means for acquiring customer information relating to the user from the management device; and a display control means for controlling the display of a screen for performing online check-in for the reservation using the acquired customer information. [Effects of the Invention]

[0008] According to the present invention, it is possible to provide a mechanism for easily performing online check-in. [Brief explanation of the drawing]

[0009] [Figure 1] System configuration diagram showing an example of a check-in management system configuration. [Figure 2] Block diagram showing the hardware configuration of information processing devices applicable to the check-in server 101, facility management server 102, reservation management server 103, guest terminal 105, facility terminal 106, staff terminal 107, and administrator terminal 109. [Figure 3] A flowchart illustrating an example of the reservation registration process. [Figure 4] A flowchart illustrating an example of the member registration process. [Figure 5] Flowchart showing an example of the reservation information import process and the check-in information import process. [Figure 6] A flowchart showing an example of the message sending process. [Figure 7] A flowchart illustrating an example of the online check-in process. [Figure 8] A flowchart illustrating an example of the online check-in process. [Figure 9] A flowchart illustrating an example of the facility check-in process. [Figure 10] A flowchart illustrating an example of the facility check-in process. [Figure 11] Figure showing an example of data to be used [Figure 12] Figure showing an example of a message [Figure 13] Figure showing an example of a screen to be displayed on the guest terminal 106 [Figure 14] Figure showing an example of a screen to be displayed on the guest terminal 106 [Figure 15] Figure showing an example of a screen to be displayed on the facility terminal 107 [Figure 16] Figure showing an example of a screen to be displayed on the facility terminal 107 [Figure 17] Figure showing an example of a facility setting information setting screen

Mode for Carrying Out the Invention

[0010] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[0011] FIG. 1 is a diagram showing an example of the system configuration of the check-in management system 100 of the present invention.

[0012] The check-in management system 100 is configured such that a check-in server (101), a facility management server (102), a reservation management server (103), a guest terminal (105), a facility terminal (106), an attendant terminal (107), and an administrator terminal (109) are connected via a network (104).

[0013] The check-in server 101 controls the execution of online check-in and facility check-in, which will be described later.

[0014] The facility management server 102 is managed for each accommodation facility and manages customer (member) user information (login information, personal information, etc.), accepts accommodation reservations from customers, and manages reservation information. In the following explanation, facility management server 102 refers to the facility management server managed by the accommodation facility that is the subject of reservations and check-ins. Furthermore, if multiple accommodation facilities are managed by dividing a single server into sections, facility management server 102 refers to the section within the server assigned to the accommodation facility that is the subject of reservations and check-ins.

[0015] The reservation management server 103 collects reservation information from the facility management server 102 and external reservation sites and manages it centrally.

[0016] The guest terminal 105 is a smartphone or other device owned by the guest, which displays received messages, shows a screen for online check-in and accepts user input. It also displays a QR code for facility check-in.

[0017] The facility terminal 106 is a tablet or similar device installed in the entrance or at the front desk of each accommodation facility, and it accepts facility check-in operations from guests. The facility terminal 106 is also equipped with an IC card writer 108, which writes card key information to an unwritten IC card and issues a card key. Alternatively, the facility terminal 106 and IC card writer 108 may be integrated into a single dedicated terminal.

[0018] Terminal 107 is a terminal operated by staff at the front desk of accommodation facilities and is used for traditional face-to-face check-in processing. It is also used to update the settings information for each accommodation facility.

[0019] Administrator terminal 109 is a terminal operated by the administrator who manages this check-in management system, and is used when updating the configuration information of multiple accommodation facilities with administrator privileges.

[0020] In this embodiment, the check-in server 101 and the reservation management server 103 are separate, but they could also be implemented on a single server. Furthermore, while a facility management server 102 is provided for each accommodation facility, multiple accommodation facilities could be managed by dividing a single server into sections.

[0021] Figure 2 is a block diagram showing an example of the hardware configuration of an information processing device applicable to the check-in server 101, facility management server 102, reservation management server 103, guest terminal 105, facility terminal 106, staff terminal 107, and administrator terminal 109 in an embodiment of the present invention. Since each device has a similar configuration, the same reference numerals are used for explanation.

[0022] As shown in Figure 2, the information processing device is connected via a system bus 220 to a CPU (Central Processing Unit) 201, ROM (Read Only Memory) 202, RAM (Random Access Memory) 203, storage device 204, input controller 205, audio input controller 206, video controller 207, memory controller 208, and communication I / F controller 209.

[0023] CPU201 provides comprehensive control over all devices and controllers connected to the system bus 220.

[0024] The ROM 202 or storage device 204 holds the BIOS (Basic Input / Output System) and OS (Operating System), which are control programs executed by the CPU 201, as well as computer-readable and executable programs and various necessary data (including data tables) for realizing this information processing method.

[0025] RAM203 functions as the main memory, work area, etc., of the CPU201. The CPU201 loads the necessary programs, etc., from ROM202 or storage device204 into RAM203 and executes the loaded programs to perform various operations.

[0026] The input controller 205 controls the input from the input device 210. Examples of input devices 210 include keyboards, touch panels, pointing devices such as mice, and imaging devices such as cameras.

[0027] Cameras and other imaging devices are used, for example, in the guest terminal 105 to take a picture of a passport, or in the facility terminal 106 to read a two-dimensional code presented by a guest.

[0028] Furthermore, if the input device 210 is a touch panel, the user can give various instructions by pressing (touching with a finger, etc.) the icons, cursors, or buttons displayed on the touch panel.

[0029] Furthermore, the touch panel may be a multi-touch screen or other touch panel capable of detecting the positions of multiple fingers touching it.

[0030] The audio input controller 206 controls the audio input from the microphone / speaker 211 when the microphone / speaker 211 is operating as a microphone, and is capable of recognizing the audio input from the microphone / speaker 211. Furthermore, when the microphone / speaker 211 is operating as a speaker, the audio input controller 206 controls the audio output to the microphone / speaker 211, and is capable of outputting audio to the microphone / speaker 211.

[0031] The video controller 207 controls the display to an external output device such as the display 212. The display may include the display of a notebook computer integrated with the main unit. The external output device is not limited to a display; for example, it may be a projector. Furthermore, for devices that can be operated by touch as described above, an input device 210 is provided.

[0032] The video controller 207 can control the video memory (VRAM) used for display control. It can utilize a portion of the RAM 203 as the video memory area, or it can provide a separate, dedicated video memory.

[0033] The memory controller 208 controls access to the external memory 213. The external memory can include an external storage device (hard disk), a flexible disk (FD), or a CompactFlash® memory connected to a PCMCIA card slot via an adapter, which stores boot programs, various applications, font data, user files, editing files, and other data.

[0034] The communication interface controller 209 connects to and communicates with external devices via the network 214 (104, 110, 120) and performs communication control processing on the network. For example, it can handle communication using TCP / IP, telephone lines such as ISDN, and 3G mobile phone lines.

[0035] The storage device 204 is a medium for permanently storing information, and its form is not limited to storage devices such as hard disks. For example, it may be a medium such as an SSD (Solid State Drive).

[0036] Furthermore, it can also be used as a temporary memory area during various processes performed by the communication terminal in this embodiment.

[0037] Furthermore, the CPU 201 enables display on the display 212 by, for example, performing the process of expanding (rasterizing) outline fonts into the display information area in RAM 203. The CPU 201 also enables user input via a mouse cursor (not shown) on the display 212.

[0038] Figure 3 is a flowchart showing an example of the reservation registration process.

[0039] This section shows the process of registering a reservation with the facility management server 102. While there are other external reservation sites that can be used to register reservations, their explanation is omitted here.

[0040] In step S301, the guest terminal 105 receives an operation from the user and sends a request to the facility management server 102 to access the reservation registration page.

[0041] In step S302, the facility management server 102 receives an access request and in step S303 sends the reservation registration screen to the guest terminal 105.

[0042] Here, there are three ways to register a reservation: a user who is already a member can log in and register; a user who is not yet a member can register and then log in and register; and a user can register without logging in.

[0043] In step S304, the guest terminal 105 displays the reservation registration screen.

[0044] In step S305, the guest terminal 105 receives a decision from the user regarding whether to register as a member. If the user registers, the terminal proceeds to step S306. If the user is already registered or does not wish to register, the terminal proceeds to step S307.

[0045] The member registration process in step S306 is explained in Figure 4.

[0046] In step S307, the guest terminal 105 receives a request from the user to decide whether to log in. If the user logs in, the terminal proceeds to step S308; otherwise, it proceeds to step S310.

[0047] In step S308, the guest terminal 105 receives login information from the user, namely the user ID and password, and requests login from the facility management server 102.

[0048] In step S309, the facility management server 102 executes the login process and puts the user into a logged-in state.

[0049] In step S310, the guest terminal 105, in cooperation with the facility management server 102, accepts searches for accommodation plans and availability, and finally accepts confirmed reservation information and sends it to the facility management server 102.

[0050] In step S311, the facility management server 102 receives the reservation information and registers it in the database in step S312.

[0051] This concludes the explanation of the reservation registration process.

[0052] Figure 4 is a flowchart showing an example of the member registration process for the facility management server 102.

[0053] This process is executed during reservation registration (Figure 3) and online check-in (Figure 7).

[0054] In step S401, the guest terminal 105 receives a membership registration request from the user via the reservation registration or online check-in login screen and sends it to the facility management server 102. Specifically, it accepts a press of the new member registration button 1314 from the login screen 1310 as shown in Figure 13(b).

[0055] In step S402, the facility management server 102 receives a member registration request, and in step S403, it sends the member registration screen.

[0056] In step S404, the guest terminal 105 displays the member registration screen.

[0057] An example of a member registration screen is shown in Figure 13(d). The member registration screen 1330 accepts input and selection of information (1331) required for member registration, confirms the information by accepting the press of the registration button 1332, and sends the confirmed information to the facility management server 102.

[0058] In step S405, the guest terminal 105 sends the received information to the facility management server 102, which receives it in step S406.

[0059] In step S407, if the facility management server 102 finds no problems with the received information, it registers it as member information and sends a reply to the guest terminal 105 indicating that member registration is complete (explanation of the reply is omitted).

[0060] An example of member information is shown in Figure 11(d). Member information 1150 includes user ID 1151 as login information, password 1152, and information about the individual member (1153~).

[0061] This concludes the explanation regarding the member registration process.

[0062] Figure 5 is a flowchart showing an example of the process for importing reservation information into the reservation management server 103 and the process for importing check-in information into the check-in server 101.

[0063] First, let's explain the reservation information import process.

[0064] This process is executed periodically (at regular intervals, fixed times, etc.) or as needed (each time a reservation is registered). The execution timing may also be changed depending on the source of the data (facility management server 102 or external reservation site). If a site controller is used, the site controller collects the reservation information from the source, so the facility management server 102 only needs to receive and register the reservation information (only steps S504 and S505 are executed). The reservation information to be imported includes all reservation information for the accommodation facilities being handled.

[0065] In step S501, the reservation management server 103 sends a request to the source (facility management server 102 or external reservation site) to import reservation information.

[0066] In step S502, the import source receives the import request and in step S503 sends the target reservation information to the reservation management server 103.

[0067] In step S504, the reservation management server 103 receives the relevant reservation information and registers it in the database in step S505.

[0068] An example of reservation information is shown in Figure 11(a). Note that this mainly shows the data that will be used for check-in information. Reservation information 1100 includes a reservation ID 1101 that uniquely identifies the reservation information, a facility ID 1102, an external reservation ID 1103, data related to the accommodation details (1104~1106), an email address 1109, a status 1110, and items related to the registration card (1111~) which will be described later.

[0069] This concludes the explanation of the reservation information import process.

[0070] Next, we will explain the process of importing check-in information.

[0071] This process is generally executed at a fixed time every day, and is performed as needed for target data that has been recently registered as reservation information. The check-in information to be imported may include all reservation information for the accommodation facilities handled, or it may be limited to only the information that will be used for message transmission as described later.

[0072] In step S511, the check-in server 101 sends a request to the reservation management server 103 to retrieve check-in information.

[0073] In step S512, the reservation management server 103 receives an import request.

[0074] In step S513, the reservation management server 103 searches for the reservation information to be checked in from the reservation information, extracts the necessary items, and generates check-in information for transmission.

[0075] In step S514, the reservation management server 103 sends the generated check-in information to the check-in server 101.

[0076] In step S515, the check-in server 101 receives the check-in information and stores it in the database in step S516.

[0077] An example of check-in information is shown in Figure 11(b). Basically, it is extracted from reservation information 1100. Check-in information 1120 includes a unique check-in ID 1121, reservation ID 1122, facility ID 1123, external reservation ID 1124, data related to accommodation details (1125~1129), email address 1130, status 1131, and items related to the registration card (1132~) described later.

[0078] This concludes the explanation of the check-in information import process.

[0079] Figure 6 is a flowchart showing an example of the message sending process.

[0080] This process sends different types of messages depending on the check-in type set for each accommodation facility. Furthermore, this process is repeated for each accommodation facility.

[0081] In step S601, the check-in server 101 searches for check-in information to send a message to from the check-in information 1120 stored in the database. For example, it searches for check-in information within N days from today until the arrival date 1127.

[0082] In step S602, the check-in server 101 determines whether the accommodation facility in the check-in information is an online check-in eligible facility. Specifically, this determination is made based on the check-in type 1142 in the facility setting information 1140 in Figure 11(c). If it is an online check-in eligible facility, the process proceeds to step S603; otherwise, the process proceeds to step S604.

[0083] Here, we will explain the facility settings information 1140. Facility settings information 1140 is information that is set in advance for each accommodation facility, and includes the check-in type 1142, message templates (1143, 1144, multiple templates for each message type), register card items 1145, confirmation items 1146 that guests are asked to confirm, etc. The person in charge of the accommodation facility may set the information for their own facility using the person in charge terminal 107, or the system administrator may set the information for all accommodation facilities at once using the administrator terminal 109. In addition, the settings may be made using the facility information setting screen shown in Figure 17, or the data table may be updated directly.

[0084] Figure 17 is an image showing an example of the facility settings information setting screen. This screen is accessed by the accommodation facility staff by entering the facility ID and password. The facility settings information setting screen 1700 includes the facility ID and facility name (1701), check-in type 1702, transmission settings 1703, message templates (1704, 1705, multiple templates for each message type), and register card items 1706. The settings made on this screen are reflected in the facility settings information 1140.

[0085] In step S603, the check-in server 101 creates an online check-in message using a message template (such as 1143).

[0086] Figure 12(a) shows an example of an online check-in message. The online check-in message 1200 is created by embedding the necessary data items from the check-in information into a message template (such as 1143). The online check-in message 1200 includes the reservation details 1201 and a link to the online check-in page 1202. The link 1202 has one or more of the following embedded: check-in ID 1121, reservation ID 1122, or external reservation ID 1124, so that it can be associated with the check-in information. In this embodiment, the external reservation ID 1124 is embedded.

[0087] In step S604, the check-in server 101 creates a message specifically for facility check-ins using a message template (such as 1143).

[0088] Figure 12(b) shows an example of a facility check-in message. The facility check-in message 1210 is created by embedding the necessary data items from the check-in information into a message template (such as 1143). The facility check-in message 1210 includes the reservation details 1211 and a two-dimensional code 1212. The two-dimensional code 1212 encodes the check-in ID 1121, reservation ID 1122, external reservation ID 1124, etc., and enables association with the check-in information. In this embodiment, the external reservation ID 1124 is encoded.

[0089] In step S605, the check-in server 101 sends the created message to the guest terminal 105. In this embodiment, it is sent by email, but any method that allows the guest terminal 105 to view the message, such as short message, SNS, or app, is acceptable. Alternatively, the message may be sent via another server or other intermediary instead of directly from the check-in server 101.

[0090] In step S606, the guest terminal 105 receives the sent message in a manner corresponding to the sending method.

[0091] This concludes the explanation of the message sending process.

[0092] Figures 7 and 8 are flowcharts illustrating an example of the online check-in process.

[0093] This process involves guests checking in in advance by operating their own devices before arriving at the accommodation.

[0094] In step S701, the guest terminal 105 displays the received message. If the message is for online check-in, it proceeds to step S702. Otherwise, if it is a message specifically for facility check-in, it proceeds to facility check-in, which will be described later in Figure 9.

[0095] In step S702, the guest terminal 105 receives the link 1202 of the online check-in message 1200 and sends a request to the check-in server 101 to access the check-in page.

[0096] In step S703, the check-in server 101 receives the access request, and in step S704, it sends the initial screen for check-in.

[0097] In step S705, the guest terminal 105 displays the initial check-in screen.

[0098] Figure 13(a) is a screen image showing an example of an initial screen for check-in. The initial screen 1300 has an online check-in button 1301 and a facility check-in button 1302. When the online check-in button 1301 is pressed, an online check-in request is sent to the check-in server 101. When the facility check-in button 1302 is pressed, a facility check-in request is sent to the check-in server 101.

[0099] In step S70A, the guest terminal 105, upon receiving a press of the online check-in button 1301 on the initial screen 1300, sends an online check-in request to the check-in server 101.

[0100] In step S70B, the check-in server 101 receives an online check-in request, and in step S70C, it sends a login screen to the guest terminal 105.

[0101] In step S70D, the guest terminal 105 displays the login screen.

[0102] Figure 13(b) is a screen image showing an example of a login screen. The login screen 1310 includes a user ID input field 1311, a password input field 1312, a login button 1313, and a new member registration button 1314. If the user has already registered with the facility management server 102, they enter their user ID and password in 1311 and 1312 and press the login button 1313 to perform the login process. If the user is not yet registered, they press the new member registration button 1314, which executes the member registration process described in Figure 4.

[0103] In step S706, the guest terminal 105 decides whether to register as a member with the facility management server 102. If it registers as a member, it proceeds to step S707; if it does not register as a member, it proceeds to step S708. Note that this assumes that online check-in processing is performed, but if online check-in is not performed and check-in is performed at the accommodation facility, the process proceeds to the facility check-in processing explained in Figure 9.

[0104] In step S707, the member registration process described in Figure 4 is executed. In this embodiment, the member registration process is executed by pressing the new member registration button 1314 on the login screen 1310, but the same button may also be placed on the initial screen 1300 to execute the process.

[0105] In step S708, the guest terminal 105 accepts login information (user ID, password) input from the user on the login screen 1310 and the press of the login button 1313, and sends the entered login information to the check-in server 101 in order to perform login authentication. Note that the information used for authentication does not have to be login information; any information that can identify the target user and can be authenticated by the facility management server 102 is acceptable, such as biometric authentication information or an email address.

[0106] In step S709, the check-in server 101 receives the login information, and in step S710, in order to confirm that the target user is a member of the facility management server 102, it sends a login authentication request to the facility management server 102 based on the login information.

[0107] In step S711, the facility management server 102 receives a login authentication request, and in step S712, it determines whether authentication is successful. If authentication is successful using the received login information, the process proceeds to step S717; otherwise, the process proceeds to step S713.

[0108] In step S713, the facility management server 102 sends authentication error information to the check-in server 101 indicating that authentication failed.

[0109] In step S714, the check-in server 101 receives authentication error information, and in step S715, it sends a request to the guest terminal 105 to re-enter login information along with the authentication error information.

[0110] In step S716, the guest terminal 105 receives the login information re-entry information, informs the user that the login failed, requests the user to re-enter the login information, and returns to step S708.

[0111] Figure 13(c) is an image showing an example of a login failure screen when a login attempt fails. The login failure screen 1320 displays in 1321 that either the user ID or password is incorrect, and allows the user to re-enter (correct) their user ID and password before attempting to log in again.

[0112] In step S717, the facility management server 102, having successfully authenticated the user as a legitimate member, extracts the member information necessary for the user's online check-in from the member information 1150 and sends it to the check-in server 101. The member information sent here includes name, address, telephone number, date of birth, etc. In this embodiment, member information is sent immediately after successful login authentication, but it may also be possible to send member information after receiving a request for member information retrieval from the check-in server 101 following login authentication.

[0113] In step S718, the transmitted member information is received and stored in the memory area. In this embodiment, it is stored in temporary memory, but it may also be stored on a hard disk or the like and deleted after processing is complete.

[0114] In step S719, the check-in server 101 searches for the target check-in information from the check-in information 1120. In this embodiment, the check-in information is identified by the external reservation ID 1124 embedded in the link 1202 when an access request is received from the guest terminal 105. Furthermore, it checks whether there are any inconsistencies between the identified check-in information and the member information obtained from the facility management server 102. Specifically, it checks whether there are any inconsistencies between the guest name in the check-in information and the name in the member information, etc. If there are inconsistencies, the guest terminal 105 is notified that online check-in is not possible (not shown).

[0115] In step S720, the check-in server 101 sends the registration card input screen to the guest terminal 105.

[0116] In step S721, the guest terminal 105 displays the register card input screen. Since the items to be entered from the register card input screen differ for each accommodation facility, the register card input screen is configured based on the contents set in the register card item 1145 of the facility setting information 1140.

[0117] In step S722, the guest terminal 105 receives input and modification of registration card information from the user and sends the received registration card information to the check-in server 101. The input content may be checked before transmission. In addition to registration card input, confirmation of other matters may also be accepted.

[0118] Figure 14(a) is a screen image showing an example of a register card input screen. The register card input screen 1400 includes multiple input fields 1401, a co-guest information input button 1402, and a confirmation button 1403. If there are data items corresponding to the member information obtained from the facility management server 102, the multiple input fields 1401 are displayed as initial values, and the user is allowed to modify them if necessary. Pressing the co-guest information input button 1402 displays a screen for entering information about co-guests (not shown). After inputting and modifying the information, pressing the confirmation button 1403 displays a confirmation screen 1410, an example of which is shown in Figure 14(b). Pressing the registration button 1412 from the confirmation screen 1410 sends the received register card information to the check-in server 101.

[0119] In step S723, the check-in server 101 receives the register card information.

[0120] In step S724, the check-in server 101 updates the check-in information based on the received register card information. Specifically, it updates the items related to the register card (1132~) for the corresponding record of check-in information 1120 in Figure 11(b). It also sets the status 1131 to "Online Check-in Completed".

[0121] In step S725, the check-in server 101 sends the updated check-in information to the reservation management server 103.

[0122] In step S726, the reservation management server 103 receives the check-in information.

[0123] In step S727, the reservation management server 103 updates the reservation information based on the received check-in information. Specifically, it updates the items related to the register card (1111~) for the corresponding record of reservation information 1100 in Figure 11(a). It also sets the status 1110 to "Online Check-in Completed".

[0124] In step S728, the check-in server 101 sends an online check-in completion message to the guest terminal 105 indicating that online check-in has been completed. The online check-in completion message 1420 is created using a template (such as 1144) set for each facility.

[0125] In step S729, the guest terminal 105 receives and displays an online check-in completion message.

[0126] Figure 14(c) shows an example of an online check-in completion message. The online check-in completion message 1420 includes a notification statement indicating completion and a link 1421 for accessing the check-in server 101 during facility check-in. In this embodiment, link 1421 is the same as link 1202 of the online check-in message, but it may be different.

[0127] Alternatively, online check-in processing may be performed by registering the register card information using the member information obtained from the facility management server 102, or the member information from the facility management server 102 may be obtained as needed.

[0128] This concludes the explanation of the online check-in process.

[0129] Figures 9 and 10 are flowcharts showing an example of the facility check-in process.

[0130] This process is performed when the guest arrives at the accommodation, and the procedure differs depending on whether or not online check-in has already been completed.

[0131] In step S901, the facility terminal 106 displays the initial screen. This screen is normally displayed on the facility terminal 106 when no user operations are being performed.

[0132] Figure 15(a) is a screen image showing an example of the initial screen of the facility terminal 106. The initial screen 1500 includes a reservation search button 1501 and a QR code reading button 1502. If the QR code cannot be displayed on the guest terminal 105, the reservation search button 1501 is pressed to search for reservations by name, etc. If the QR code can be displayed, the QR code reading button 1502 is pressed to display the QR code reading screen. In this embodiment, only the case where the QR code can be displayed is described, and the case where it cannot be displayed is omitted.

[0133] In step S902, the facility terminal 106 displays the QR code reading screen when the QR code reading button 1502 is pressed.

[0134] Figure 15(b) is a screen image showing an example of a two-dimensional code reading screen. The two-dimensional code reading screen 1510 displays a message prompting the user to read the two-dimensional code, and in practice, the two-dimensional code is read by the camera 1511 that is standard equipment on the facility terminal 106, or by an external camera or scanner.

[0135] Steps S903 to S912 below are processes to display a facility check-in screen including a QR code on the guest terminal 105 if the target accommodation facility is eligible for online check-in. However, if the target accommodation facility is eligible for facility check-in, this process is unnecessary because the QR code 1212 is displayed in the facility check-in message 1210.

[0136] In step S903, the guest terminal 105 displays either an online check-in message 1200 or an online check-in completion message 1420 in response to the user's request for display.

[0137] In step S904, the guest terminal 105 receives the designation of either the link 1202 in the online check-in message 1200 or the link 1421 in the online check-in completion message 1420, and sends a request to the check-in server 101 to access the check-in page.

[0138] In step S905, the check-in server 101 receives the access request, and in step S906, it sends the initial screen for check-in.

[0139] In step S907, the guest terminal 105 displays the initial check-in screen. If online check-in has been completed, the initial screen 1300 in Figure 13(a) is controlled so that the online check-in button 1301 cannot be pressed.

[0140] In step S90A, the guest terminal 105, upon receiving a press of the facility check-in button 1302 on the initial screen 1300, sends a facility check-in request to the check-in server 101.

[0141] In step S90B, the check-in server 101 receives a facility check-in request, and in step S90C, it sends a login screen to the guest terminal 105.

[0142] In step S90D, the guest terminal 105 displays the login screen. The login screen is the same as the online check-in process, as shown in Figure 13(b).

[0143] In step S908, the guest terminal 105 receives login information (user ID, password) from the user on the login screen 1310 and the login button 1313 is pressed, and sends the entered login information to the check-in server 101 in order to perform the login process.

[0144] In step S909, the check-in server 101 receives the login information, and in step S910, it performs login authentication in the same way as in steps S710 to S715. Here, we will only explain the case where authentication is successful, and we will omit the explanation for the case where authentication fails.

[0145] In step S911, the check-in server 101 sends the facility check-in screen to the guest terminal 105.

[0146] In step S912, the guest terminal 105 displays the facility check-in screen.

[0147] Figure 14(d) is a screen image showing an example of a facility check-in screen. The facility check-in screen 1430 includes reservation details and a two-dimensional code 1431. The two-dimensional code 1431 encodes the check-in ID 1121, reservation ID 1122, external reservation ID 1124, etc., and allows for association with check-in information. In this embodiment, the external reservation ID 1124 is encoded.

[0148] In step S913, the two-dimensional code 1431 of the facility check-in screen 1430 displayed on the guest terminal 105 is presented to the two-dimensional code reading screen of the facility terminal 106. Specifically, the screen of the facility terminal 106 is pointed towards the camera or other device so that it can be read by the camera or other device of the facility terminal 106. If the target accommodation facility is not eligible for online check-in, i.e., is eligible for facility check-in, the two-dimensional code 1212 of the facility check-in message 1210 is presented.

[0149] In step S914, the facility terminal 106 reads the presented two-dimensional code, with the two-dimensional code reading screen 1510 displayed in step S902.

[0150] In step S915, the facility terminal 106 converts the scanned QR code back into an external reservation ID and sends the converted external reservation ID to the check-in server 101.

[0151] In step S916, the check-in server 101 receives the external reservation ID, and in step S917, it searches for the check-in information corresponding to the received external reservation ID from the check-in information 1120.

[0152] In step S918, the check-in server 101 determines whether the status 1131 of the retrieved check-in information is "online checked in". If it is online checked in, it proceeds to step S927; otherwise, it proceeds to step S91A.

[0153] In step S91A, the check-in server 101 sends a confirmation screen to the facility terminal 106, prompting the user to confirm the reservation details.

[0154] In step S91B, the facility terminal 106 displays a screen to confirm the reservation details.

[0155] Figure 16(a) is a screen image showing an example of a confirmation screen when online check-in has not been performed. The confirmation screen 1600 displays the reservation details and includes a register card input button 1601. When the register card input button 1601 is pressed, a register card input request is sent to the check-in server 101.

[0156] In step S91C, the facility terminal 106 receives a press of the register card input button 1601 on the confirmation screen 1600 and sends a register card input request to the check-in server 101.

[0157] In step S91D, the check-in server 101 receives a registration card input request, and in step S919, it sends the registration card input screen to the facility terminal 106.

[0158] In step S920, the facility terminal 106 displays the register card input screen.

[0159] In step S921, the facility terminal 106 receives registration card information from the user and transmits the received registration card information to the check-in server 101.

[0160] Figure 16(b) is a screen image showing an example of the registration card input screen of the facility terminal 106. The registration card input screen 1610 of the facility terminal 106 includes multiple input fields, a co-guest information input button 1611, and a confirmation button 1612, similar to the registration card input screen 1400 for online check-in. Pressing the co-guest information input button 1611 displays a screen for inputting information about co-guests (not shown). After inputting the information, pressing the confirmation button 1612 displays the registration card information confirmation screen 1620, an example of which is shown in Figure 16(c). Pressing the registration button 1621 from the registration card information confirmation screen 1620 sends the received registration card information to the check-in server 101.

[0161] In step S922, the check-in server 101 receives the register card information.

[0162] In step S923, the check-in server 101 updates the check-in information based on the received register card information. Specifically, it updates the register card-related items (1132~) for the corresponding record of check-in information 1120 in Figure 11(b). It also sets the status 1131 to "Checked in".

[0163] In step S924, the check-in server 101 sends the updated check-in information to the reservation management server 103.

[0164] In step S925, the reservation management server 103 receives the check-in information.

[0165] In step S926, the reservation management server 103 updates the reservation information based on the received check-in information. Specifically, it updates the items related to the register card (1111~) for the corresponding record of reservation information 1100 in Figure 11(a). It also sets the status 1110 to "Checked in".

[0166] In step S927, the check-in server 101 sends a confirmation screen to the facility terminal 106 if the register card has already been registered.

[0167] In step S928, the facility terminal 106 displays a confirmation screen if the register card has already been registered.

[0168] Figure 15(c) is a screen image showing an example of a confirmation screen when a register card has been registered. The confirmation screen 1520 displays the reservation details and includes a key issuance screen display button 1521. When the key issuance screen display button 1521 is pressed, a key issuance screen, as shown in Figure 15(d) as an example, is displayed, and when the key issuance button 1531 is pressed, a key issuance request is sent to the check-in server 101.

[0169] In step S929, the facility terminal 106 receives a key issuance request from the check-in server 101 upon receiving a key issuance button 1531.

[0170] In step S930, the check-in server 101 receives a key issuance request.

[0171] In step S931, the check-in server 101 sends a key issuance command to the IC card writer 108 along with the information necessary for key issuance.

[0172] In step S932, the IC card writer 108 writes the necessary information to the unwritten IC card and issues a key.

[0173] This concludes the explanation regarding the facility check-in process.

[0174] In summary, the present invention makes it possible to provide a mechanism for easily performing online check-in.

[0175] In this embodiment, the reservation management server 103 is configured to manage reservation information and the check-in server 101 is configured to manage check-in information. However, it is also possible to manage them with a single server, and in that case, the reservation information may be treated as check-in information without distinguishing between reservation information and check-in information.

[0176] The present invention can take the form of, for example, a system, apparatus, method, program, or recording medium. Specifically, it may be applied to a system consisting of multiple devices, or to an apparatus consisting of a single device.

[0177] Furthermore, the program in this invention is a program that allows a computer to execute the processing methods of each flowchart, and the storage medium of this invention stores the program that allows a computer to execute the processing methods of each flowchart. Note that the program in this invention may also be a program for each processing method of each device in each flowchart.

[0178] As described above, it goes without saying that the object of the present invention can also be achieved by supplying a recording medium containing a program that realizes the functions of the embodiments described above to a system or device, and by having the computer (or CPU or MPU) of that system or device read and execute the program stored on the recording medium.

[0179] In this case, the program read from the recording medium itself realizes the novel function of the present invention, and the recording medium on which that program is recorded constitutes the present invention.

[0180] For recording media used to supply programs, examples include flexible disks, hard disks, optical disks, magneto-optical disks, CD-ROMs, CD-Rs, DVD-ROMs, magnetic tapes, non-volatile memory cards, ROMs, EPROMs, silicon disks, and the like.

[0181] Furthermore, it goes without saying that the functions of the aforementioned embodiments are realized not only by the computer executing the program it has read, but also by the operating system (OS) running on the computer performing some or all of the actual processing based on the instructions of that program, thereby realizing the functions of the aforementioned embodiments.

[0182] Furthermore, it goes without saying that this also includes cases where, after a program read from a recording medium is written to the memory of a function expansion board inserted into a computer or a function expansion unit connected to a computer, the CPU or other components of the function expansion board or function expansion unit perform some or all of the actual processing based on the instructions of the program code, and the functions of the aforementioned embodiments are realized through that processing.

[0183] Furthermore, the present invention may be applied to a system consisting of multiple devices or to a device consisting of a single device. It goes without saying that the present invention can also be applied when the results are achieved by supplying a program to a system or device. In this case, by reading a recording medium containing a program for achieving the present invention into the system or device, the system or device can enjoy the effects of the present invention.

[0184] Furthermore, by downloading and reading the program for achieving the present invention from a server, database, etc. on a network using a communication program, the system or device can enjoy the effects of the present invention. It should be noted that configurations combining the above-described embodiments and their variations are all included in the present invention. [Explanation of Symbols]

[0185] 100 Check-in Management Systems 101 Check-in Server 102 Facility Management Server 103 Reservation Management Server 104 Network 105 Guest terminal 106 Facility Terminals 107 Staff Terminal 108 IC card writer 109 Administrator terminal

Claims

1. An information processing device that can communicate with a management device for managing customer information of accommodation facilities, A request receiving means for receiving online check-in requests from users for accommodation reservations at the aforementioned accommodation facility, An acquisition means for acquiring customer information relating to the user from the management device, A display control means that controls the display of a screen for performing online check-in for the accommodation reservation using the acquired customer information, An information processing device characterized by comprising:

2. The information processing apparatus according to claim 1, wherein the acquisition means acquires customer information relating to the user when the user is authenticated by the management device.

3. The information processing device according to claim 1, further comprising determination means for determining whether the accommodation reservation was made by a customer of the accommodation facility based on the acquired customer information.

4. The information processing device according to claim 1, characterized in that the aforementioned screen is a screen for receiving input information relating to a guest.

5. A control method for an information processing device that can communicate with a management device for managing customer information of an accommodation facility, The request receiving means includes a request receiving step in which a user requests online check-in for a hotel reservation, The acquisition means includes an acquisition step of acquiring customer information relating to the user from the management device, A display control step in which the display control means controls the display to display a screen for performing online check-in for the accommodation reservation using the acquired customer information, A control method for an information processing device, characterized by comprising the following:

6. A program for causing at least one computer to function as one of the means of an information processing apparatus described in any one of claims 1 to 4.

Images