HK1058077A1 - Remote airline check-in using a global computer network - Google Patents

Description

Remote airline check-in using global computer network

Technical Field

The present invention relates to the aircraft industry, and in particular to techniques for checking in passengers of departure flights.

Background

A ticket can book a seat for a passenger on a flight. While tickets may be used for reservations, seats on flights are often overbooked because "passengers who gave up booking seats" are expected. For this reason, seat assignments are generally not confirmed until after the passenger arrives at the airport and checks in for a "check-in" procedureAnd (4) identifying. Historically, the check-in of a "check-in" procedure required the passenger to be in contact with a ticket or boarding manager. More recently, however, airlines have installed automation devices that allow a passenger to check in by self after arriving at an airport. E-Ticket was offered by northwest airline of Minneapolis, Minnesota^SME-Service Center of passenger^SMA service is an example. After the check-in, the passenger's reservation is confirmed, the passenger is assigned a seat on the corresponding flight, and a boarding pass for confirming the seat is obtained. Generally, automatic boarding equipment requires that a check-in is completed within a certain period of time before the departure of an airliner, as with a corresponding boarding manager.

Disclosure of Invention

The invention provides a system and a method for checking in remote flights through a global computer network. The present invention may be configured to allow passengers to remotely access airline servers using a global computer network (e.g., the internet). This server (e.g., a web server) may receive a flight passenger check-in request over the internet. In response to the check-in request, the server assigns seats to the passengers on the designated flight. In particular, the airline server may record the confirmed seat assignments in a seat booking system database.

The passenger may be located at a remote location from the airport lounge associated with the departure of the designated flight. For example, the passenger may connect to the network through a desktop or portable computer located in the passenger's home, office, or car. Alternatively, the passenger may also rely on a PDA (personal digital assistant) or a mobile phone with internet access to the airline server. As another example, particularly for hotel guests, an airline server may be accessed by using an interactive television system (e.g., a system for hotel checkout).

In other cases, the passenger may be located in an airport lounge associated with the departure of a designated flight. For example, the passenger may carry a computer, PDA or mobile phone, or use a public computer or other network device provided in an airport lounge. In any event, the airline servers can be located anywhere, including in an airport lounge or in a remote location. Network communication between the passenger and the airline server can be accomplished using conventional network protocols (e.g., TCP/IP).

With remote boarding, passengers do not have to wait until arriving at an airport lounge to make seat assignment confirmation. In contrast, passengers may check-in on a self-service basis from virtually anywhere and reduce the required pre-boarding time in the airport lounge. Furthermore, passengers can have a very flexible choice of seat assignments before arriving at the airport. In particular, in some embodiments, the passenger may have finished checking in remotely a few hours before boarding the designated flight.

Once the seat allocation is confirmed, the server notifies the passenger of the seat allocation that was confirmed over the global computer network. The passenger may print out a boarding pass or record an electronic boarding pass for presentation to the airline boarding manager. The printed boarding pass may include information for verification of authenticity, which may be accomplished by visual inspection or optical scanning. An electronic boarding pass may be represented by information transmitted from a handheld device (e.g., PDA or mobile phone) carried by the passenger to a receiver operated by the airline boarding manager.

Alternatively, the passenger may carry a programmable smart card carrying information indicating confirmation of seat allocation. The smart card may be embedded in an electronic device, such as a phone or PDA. In other embodiments, the passenger may only present the proof against seat assignment confirmation information recorded by the airline server. The net result is that passengers have the ability to check-in remotely, but the confirmation of seat assignment can only be verified when arriving at the airport lounge.

Remote check-in can also provide benefits to airline personnel in terms of making check-in and check-in processes more orderly. In particular, remote check-in may support early confirmation of seat assignments for a significant number of passengers, reducing the number of passengers arriving at the airport check-in one hour prior to flight departure. In other words, the work and pressure intensity often associated with conventional check-in and boarding procedures immediately prior to flight departure is diminished due to the involvement of passengers in the remote boarding procedure. Airline personnel can better deal with passenger roster and oversubscription issues due to the receipt of many advanced seat assignment acknowledgements.

In some embodiments, the availability of a passenger to check-in remotely may be limited to a predetermined time window before flight departure. For example, this window may extend from about 6 hours before flight departure to 90 minutes before flight departure.

Disabling the check-in before a given time (e.g., 6 hours before flight departure) reduces the likelihood of excessive passengers abandoning reserved seats and helps airline personnel to manage the check-in and check-in process. Passengers who have checked in within 6 hours before the departure of the flight are more likely to take the flight than passengers who have checked in one day before the departure of the flight.

In particular, if the check-in is late, the passenger has more knowledge of his ability to arrive at the airport on time to take an airplane. As a further consideration, the later the check-in is made, the more certain will be the airline's knowledge of the situation of the flight that is taking this flight, and thus the seat assignment can be confirmed with greater reliability.

Stopping the check-in for a given time (90 minutes before the flight takes off) will avoid a conflict between a passenger checking in remotely and an airline worker using a traditional check-in approach. This feature may also assist airline personnel in managing check-in and check-in procedures.

For passengers who have never before given up a reservation history, the check-in window may be extended so that such passengers may check in remotely at an earlier time (e.g., one or more days before the flight takes off). In this manner, check-in applications for individual passengers may be processed on a selective and customized basis. Historical information may be collected from past air travel records and used as an indication that a passenger is a passenger with a lower risk of giving up a reserved seat. Tagged passengers may check in early, while passengers with little or no historical data and passengers with a history of frequently giving up booked seats may check in only during a normal time window.

The system and method for checking in remotely may also be configured to handle non-routine jobs ("IRROPS"). In particular, upon check-in, the airline server may access the airline reservation database to confirm whether the specified flight has been cancelled, late, or adjusted with respect to the original flight plan. The network server may receive one or more other booking schemes for selection by the passenger by communicating with a conventional booking system or booking agent.

In this way, the passenger is notified of both IRROPS and other options for travel. In some cases, the web server may generate a printable web page or other information to provide the passenger with a credential for service, such as a hotel stay, flight coupon, or the like, particularly if the flight is cancelled.

In one embodiment, the present invention provides a method for airline passenger check-in, the method comprising receiving a request for airline passenger check-in over a global computer network, and confirming a seat assignment for a passenger on a designated airline responsive to the request for check-in.

In another embodiment, the invention provides a system for airline passenger check-in, the system comprising a web user machine for transmitting a request for airline passenger check-in over a global computer network, and a web server for receiving the request for airline passenger check-in over the global computer network, the server confirming seat allocation for the passenger on a designated flight in response to the request for check-in.

In a further embodiment, the present invention provides a method for airline passenger check-in, the method comprising receiving a request for airline passenger check-in over a global computer network, confirming a seat assignment for a passenger on a designated airline flight in response to the request for check-in, and generating a ticket for the designated airline flight at a location remote from an airport terminal associated with the designated airline flight.

In an additional embodiment, the invention provides a system for airline passenger check-in, the system comprising a web-user machine for transmitting a request for airline passenger check-in over a global computer network, and a web-server for receiving the request for check-in over the global computer network, the server confirming seat assignment for the passenger on a designated airline flight in response to the request for check-in, and providing a device located remotely from an airport terminal associated with the designated airline flight capable of generating a ticket for the designated airline flight.

In another embodiment, the invention provides a method for airline passenger check-in, the method comprising receiving a request for airline passenger check-in over a global computer network, comparing a time at which the request for check-in was received to a maximum permitted time period, and if the time at which the request for check-in was received is within the maximum permitted time period, confirming a seat assignment for the passenger on the designated airline flight in response to the request for check-in.

In a further embodiment, the present invention provides a system for airline passenger check-in, the system including a web user machine for transmitting a request for airline passenger check-in over a global computer network, and a web server for receiving the request for check-in over the global computer network, the server comparing a time at which the request for check-in was received with a maximum permitted time period, and if the time at which the request for check-in was received is within the maximum permitted time period, the server confirming seat allocation for the passenger on the designated airline flight in response to the request for check-in.

In an additional embodiment, the present invention provides a method for airline passenger check-in, the method comprising receiving a request for airline passenger check-in over a global computer network, confirming whether a designated flight associated with the request for check-in is late or cancelled, and if so, confirming seat allocation on another flight in response to the request for check-in.

In another embodiment, the invention provides a system for airline passenger check-in, the system including a web user machine for transmitting a request for airline passenger check-in over a global computer network, and a web server for receiving the request for check-in over the global computer network, the server confirming whether a designated flight associated with the request for check-in is late or cancelled, and if so, confirming seat assignment on another flight in response to the request for check-in.

Drawings

FIG.1 is a block diagram of a system for remote check-in using a global computer network;

FIG.2 is a flow chart of a method for passenger check-in remotely;

FIG.3 is a flow chart illustrating the management of a boarding time window as part of a remote check-in;

FIG.4 is a flow chart illustrating the management of a selective boarding time window as part of a remote boarding pass;

FIG.5 is a flow chart illustrating the management of an irregular job session as part of a remote check-in;

FIG.6 illustrates an initial web browser window displaying the web page to the flight passenger upon entering personal identification information during a check-in process;

FIG.7 illustrates a web browser window that is displayed to the flight passenger when a reservation record is retrieved during a check-in process;

FIG.8 illustrates a web browser window displaying a designated passenger to the flight passenger upon selection of the passenger during a check-in process;

FIG.9 illustrates a web browser window displaying the web page to the airline passenger upon airline confirmation during the check-in of the remote check-in;

FIG.10 illustrates a web browser window displaying the web page to the airline passenger upon security confirmation during the check-in of the remote check-in;

FIG.11 illustrates a web browser window displaying the web page to the flight passenger when notifying a contact information request during a check-in process;

FIG.12 illustrates a web browser window displaying the web page to the flight passenger when notifying the ticket envelope to discard statement information during the check-in process;

FIG.13 illustrates a web browser window displaying the web page to the airline passenger when the ticket is notified to print instructions during the check-in process;

fig.14 illustrates a web browser window that displays the web page to the flight passenger after the check-in process is completed.

Like numbers refer to like elements throughout.

Detailed Description

Fig.1 is a block diagram illustrating a system 10 for check-in of remote flights using a global computer network, such as the world wide web 12. The system 10 may be used to perform a method for providing check-in for airline passengers. Using the system 10, airline passengers can check-in from virtually anywhere without contact with a boarding agent or an electronic service center located in an airport terminal room. In this way, passengers may receive confirmation of seat assignments prior to arriving at the airport lounge, if desired. Checking in remotely can at least reduce the time before a passenger boards in the airport terminal. In addition, for airline personnel and passengers, the check-in advance can make the check-in and check-in processes before flight take-off more orderly.

As shown in fig.1, the system 10 may include a number of passenger devices 14, 16, 18, 20, and 22 connected to the network 12. In the example of fig.1, the passenger device 14 takes the form of an internet-enabled mobile, i.e., wireless, telephone. The passenger device 16 takes the form of an interactive television system that mounts a set top box that has access to the network 12. The passenger device 18 is a desktop computer, such as a personal computer or a Macintosh computer having access to the network 12. The passenger device 20 takes the form of a portable computer, such as a laptop personal computer or a Macintosh computer. The passenger device 20 takes the form of a Personal Digital Assistant (PDA), for example based on a Palm, Windows CE or similar operating system for small portable devices. Other future internet devices may also be used by the system 10.

The passenger may also access the network 12 through an internet kiosk 24 and other public facilities. In addition, business users (e.g., travel agencies, hotels, land transportation companies, and the like) may access network 12 on behalf of passengers via device 26. The device 26 used by the commercial user may be the same as any of the passenger devices 14, 16, 18, 20, and 22 (i.e., computers, personal digital assistants, telephones, interactive televisions, and other similar devices). Check-in may be considered a value added service provided to passengers by commercial users. For a hotel guest to be checked out, the hotel operator may check in for the guest and provide a boarding pass for the guest. Check-in of internet boarding procedures by people other than passengers requires modification of existing security operations.

With further reference to fig.1, the system 10 also includes an airline server 28, such as a web server, which server 28 can communicate with the passenger devices 14, 16, 18, 20, 22, the internet kiosks 24, and the business user devices 26 via the world wide web 12. Although the number of passenger devices, internet kiosks, and business user devices shown in fig.1 is limited for ease of illustration, the actual number is virtually unlimited, as determined by the bandwidth limitations of the server 28 and the network 12. Passengers accessing the system 10 will typically make reservations using the airline network server 28 that operates the airliner. In some embodiments, however, the passenger may be allowed to check-in using flight information and other flights having a partnership that enables shared or coordinated use of the reservation database information.

The passenger's location may be remote from the airport lounge, such as at home, in the office, or during travel. The advent of personal digital assistants and web-enabled wireless telephones will allow check-in with a higher level of mobility. Thus, a passenger may even check in at an airport remotely but use his own mobile device. The logic performed by the airline network server 28 may be configured to limit check-in transactions to a particular time window.

For example, the window may extend from about 6 hours before flight departure to 90 minutes before flight departure. Thus, if a passenger attempts to check in before the time window begins, he will be notified to do so later. If the passenger tries to check in after the time window has ended, he will be informed to check in to the airport and can check in by contact with an electronic service center or an airline representative. For so-called "red-eye" flights, the time window may span several consecutive days.

The system 10 may also include a database server 30 and an airline reservation database 32, as well as a file server 34 and a file archive 36 containing data organized by the database 32. The database server 30 may communicate with a global subscription system 38, such as Worldspan operated by Worldspan of Atlanta, Ga^RComputer Reservation System (CRS). The database server 30 may also communicate with an electronic service center 40 located in an airport terminal room, such as the E-Ticket for airlines in northwest^SMPassenger providing E-Service Center^SMA service center used for the service.

Communication between the airline network server 28 and the passenger devices 14, 16, 18, 20, 22, the internet kiosk 24, and the business user device 26 can occur over the internet using conventional network protocols (e.g., TCP/IP). Communication between the airline network server 28, the database server 30, the airline reservation database 32, and the electronic service center 40 may also be performed using TCP/IP. In most embodiments, the database server 30, the airline reservation database 32, and the electronic service center 40 are connected to a private local area network or wide area network maintained by the airline. In some embodiments, however, the electronic service center 40 has the capability to access the database server 30 indirectly through the airline web server 28 and the network 12, as indicated by numeral 42 in the drawings.

It is preferable to provide a firewall as a security means. The firewall isolates the database server 30 and the file server 34 from the web server 28 to prevent unauthorized intrusion of information for use by the passenger. The security and privacy of the database server 30 and the document archive 36 is a very important issue, since it is a repository of information about individual accounts and travel plans in its nature. To enhance the security and privacy of the customer information, the web page generated by the web server 28 may be transmitted to the generator 14, 16, 18, 20 using public key encryption methods (e.g., SSL).

Business users (e.g., travel agencies) may communicate with the airline web server 28 through the network 12 and the device 46. The commercial user equipment 46 may access the global subscription system 38 through dial-up or private access, as indicated by numeral 44 in the figure. Similarly, the database server 30 may also communicate with the global subscription system 38 via dial-up or private access, as indicated by numeral 46 in the drawing. The global subscription system 38 may also provide access to the file server 34 through a dial-up or private connection, as indicated by numeral 48 in the drawing.

In operation, the web server 28 interacts with the database server 30 and the file server 34 to compile content for use by passengers connected to the passenger devices 14, 16, 18, 20, 22, the internet kiosk 24, and the commercial user device 26 organized by the airline reservation database 32 and stored in the file archive 36. The information may include relatively unchanging textual and graphical web page content, as well as passenger profile information stored for each passenger, and displayed on a special web page generated by the airline web server 28.

The web server 28 retrieves and provides the passenger record information to the passenger during the check-in procedure. In some embodiments, the web server 28 may interact with the database server 30 and the airline reservation database 32 to confirm that the designated flight is on time. In particular, the system 10 may be configured to handle non-routine jobs ("IRROPS"), such as flight cancellation, late hours, and the like. The web server 28 is connected to conventional booking services (e.g., automatic booking software and/or ticketing agents) provided within the airline.

Also, in some embodiments, interaction with the global reservation system 38 may be used to provide travel options including other airline flights. In this manner, the network server 28 receives one or more selective ticketing schemes for selection by the passenger and provides them on a remote basis. Thus, the passenger is both notified of the IRROPS event and is also given selective travel options. In some cases, web server 28 may generate a printable web page or other information to provide the passenger with a service credential, such as a hotel stay, flight coupon, or the like, particularly if the flight is cancelled.

Further, the devices used by passengers and business users may employ personal computers, Macintosh computers, PDAs, interactive televisions, mobile phones, and the like, as long as the devices have the telecommunication service function of accessing the network 12. These devices may connect to the world wide web 12 directly or through an internet service provider and communicate using a network protocol (e.g., TCP/IP). Each device preferably executes a graphical view application (e.g., a web browser) to use resources located on other computers connected to network 12. In particular, web browsers may allow passengers and business users to view HTML web pages generated by web server 26. Other user interface applications may also be used to access the airline server 28 if the information is provided in a user interactive format.

The web server 26 may take the form of a single web server or multiple web servers connected to the database server 30 and the file server 34, or multiple mirror servers. The web server 26 executes the server page script. Scripts may be written in Lotus Notes format, Active Server Pages (ASP), CGI scripts, java servlets, or other Server-side scripting language suitable for creating and maintaining database driven websites. If dynamic graphical content is desired, user-side scripts may be executed on the various devices 12, 16, 18, 20, 22, 24, and 26. Due to the variety and relative simplicity of some of the different client device 12, 16, 18, 20, 22, 24, and 26 platforms, however, it is desirable to use server-side scripts to provide most of the daily processing operations.

The web server 28 interacts with a database server 30 to allow passengers to use the information contained in the airline reservation database 30. The web server 26 compiles the content required for the web pages requested by the passenger devices 12, 16, 18, 20, 22, the internet kiosks 24 and the commercial user devices 26 and receives information from the devices for populating the database 32 with content. The database server 30 may be any type of server suitable for database-oriented applications, such as an OLEDB or ODBC driver.

In response to a query from the web server 28, the database server 30 looks up the appropriate record in the airline reservation database 32. The web server 28 then retrieves the information associated with the records from the document archive 36 via the document server 34 and processes the information to generate the content of the web pages for use by the devices 12, 16, 18, 20, 22, 24 and 26 by the respective passengers and commercial users.

The information retrieved from the airline reservation database 32 is typically limited to records associated with individual passengers requesting a remote check-in. In some cases, however, people other than passengers may be authorized to process remote check-in range information that a particular generator may use, based on relevance and personal interests. For example, group travel workers may be authorized to access information from many different group passengers.

In this case, the airline server 28 can retrieve the plurality of records from the database 32 and generate a web page that provides the content. The corporate travel staff may then complete the remote check-in for multiple passengers and issue a boarding pass to the passengers. Also, in some embodiments, the travel agency may be authorized to check in remote check-ins for multiple customers. Time restrictions on check-in will limit the use of remote check-in by travel agencies because the check-in needs to be printed and delivered by couriers or received by passengers. In some embodiments, however, the check-in may not require the passenger to carry a paper boarding pass.

In operation, the devices 12, 16, 18, 20, 22, 24, and 26 access the airline web server 28 via one or more URLs and interact via web pages to request use of information stored in the database 32. In one embodiment, each passenger accesses the special information by entering information (e.g., passenger name and/or user number, such as a so-called "frequent passenger" number). In response to the input of passenger information, airline web server 28 can provide one or more web pages detailing the current status of the passenger flight path and providing instant service options such as ticketing, reselling, mileage status, and remote check-in.

A web page driven dialog may be assisted by conventional input media such as check boxes, wireless dials, text entry boxes, and the like. Furthermore, web browser access provides the advantage that the information is retained in the text entry box for the passenger each time the passenger accesses the web site. In this way, the passenger need not remember such information, which is advantageous when the passenger is not at home or in the office to access the network server 28.

The information provided by the web server 28 may appear in text or graphical format and may include hypertext links to additional information items. Moreover, the information may also include downloadable files that convey additional information, such as in a PDF format. Examples of files that can be delivered to a passenger as downloadable files are flight receipts, account status reports, and the like. In response to the passenger selecting to check in remotely, the airline web server 28 presents a series of interactive web pages requesting user input. For example, a first web page may require entry of a passenger name and frequent passenger numbers. The latter web page prompts entry of the content required for check-in.

Fig.2 is a flow chart of a method for airline passenger check-in remotely. In particular, FIG.2 illustrates the manner in which a passenger accesses the airline web server 28 and checks in a remote check-in via a series of web pages. The method described in fig.2 is purely exemplary, and many different embodiments can be derived. In the example of fig.2, the passenger or business user first accesses the home page ("NW web page") of the airline, represented by block 50. On this homepage, the passenger clicks on the appropriate icon to access the internet boarding website. When entering the internet boarding network site, represented by box 52 in the figure, the user enters his name, the departure city or airport of the flight concerned, the credit card account number, the passenger name record or the frequent passenger number, for example the northwest airline WorldPerks number.

After entering personal information, a web page may appear representing information about the departure airport, as shown in block 54. The web page may present a "please wait" message as indicated at block 56, at which time the web server 28 interacts with the database server 30 to retrieve the appropriate passenger name record. Airport information and "please wait" information may be combined in a single web page. In most embodiments, only a single passenger name may be retrieved for security reasons, as shown by line 57. In some embodiments, however, multiple passenger names may be retrieved, as indicated by line 58. Line 58 is a dashed line indicating selectivity in the process shown in fig. 2. If multiple passenger name records are retrieved, a web page is generated asking for the selection of the particular passenger or passengers from the passenger name records, as shown in block 59. If a single passenger name record is retrieved or a passenger is selected from a plurality of passenger name records, the web server 28 generates a web page that displays the appropriate passenger name record, as shown in block 60.

After the passenger name record is displayed, the user is asked to check for safety issues 1 and 2, i.e. whether the bag carried and checked on the flight will be carried with the passenger as it is already packed, and whether a person unknown to the passenger asks him to carry anything. This operation is represented by block 62. When the passenger checks in for remote boarding himself (which is the case in most cases), he himself can answer the questions. But when a remote check-in is checked in by a travel agency, business user, or other person, the program may be modified to preserve security issues, wait for passengers to arrive at the airport for use, or provide some other form of security verification. The user may also request that security questions be rewritten as indicated in block 64.

If international travel is involved, the airline web server 28 can also display a web page requesting contact and notification information to be entered, as shown in block 66. After the steps represented by blocks 62, 64 and 66 are completed, the web server 28 generates a web page that displays the ticket envelope discard statement information, as represented by block 68. Such information may be announced within the web page or provided by hypertext link access. The web server 28 then generates a web page directing the printing of the boarding pass, as shown in block 70, and drives the printer to print the boarding pass and flight receipt, as shown in block 72.

However, if the devices 12, 16, 18, 20, 22, 24 and 26 are not equipped with a printer, other steps, such as programming a smart card or simply recording the seat assignment confirmation in the airline reservation database 32, are sufficient. In this case, the user may provide the smart card or device with the smart card or other media therein to a reader for use by airline personnel, with information being transmitted to the reader optically, mechanically, wirelessly, or otherwise. Alternatively, the passenger may only present identification to the airline boarding officer at the entrance, such as a driver's license, credit card, or frequent passenger card. After identification, the airline personnel can verify that seat assignment confirmation has been completed by accessing the airline database 30 or by using some other electronic file that indicates that the check-in of a passenger has been completed. Finally, a web page appears indicating that the remote boarding process has been completed, as shown in block 74, and the user is redirected to the airline home page, as shown in loop 76.

After the remote check-in is complete, the airline web server 28 interacts with the database server 30 to update the airline reservation database 32 with the relevant seat assignment confirmation. In this manner, the airline network server 28 provides a seat allocation record for the airline operator operation terminal device 49 query that has access to the database server 30. Thus, the airline personnel can manually operate the terminal device 49 to verify the seat assignment confirmation when the passenger arrives. Alternatively, a reader device (e.g., a bar code scanner, smart card reader, magnetic strip reader, wireless receiver, or the like) may interact with the media carried by the passenger and with the database server 30 or an electronic recorder provided at the gate or elsewhere for confirmation of the assignment, to quickly verify that the check-in has been completed when the passenger boards the aircraft. The airline reservation database 32 can be selectively replicated to the global reservation system 38 and the validated seat allocation records made available to other airline flights and travel agencies.

Many modifications to the procedure described in figure 2 may be readily made. For example, the program may allow a passenger to reserve an elevator car, change seat assignments, enter passport information, and process the change in the case of an irregular job (e.g., late in flight or cancelled). As another example, web server 28 may be configured to provide the above-described time window to limit passenger use of the remote boarding procedure. Further, the use may be limited to a first predetermined time prior to the flight departure and a second predetermined time later than the flight departure. In addition, the airline web server 28 can be configured to differentiate between different passengers to provide different time windows on a selective basis.

For example, for passengers who have little to no waiver for a reservation seat history, the check-in window may be extended to provide for use of remote boarding procedures at an earlier time. On the other hand, passengers with a history of frequently relinquishing reserved seats may be limited to a more strict time window, with a later start of the window and/or having a shorter duration. The criteria for providing an early or late check-in time window may be based not only on the number of times a reserved seat is abandoned, but also on the percentage of the number of times a reserved seat is abandoned to the number of flights taken. Moreover, for more reliable historical information, passengers that fit into a longer check-in window (i.e., use the boarding procedure earlier) may only take a minimum number of flights in the flight history. Thus, over time, as the passenger accumulates more flights and meets the statistics of giving up booked seats, he may become eligible to check in earlier.

As an example, a passenger who took 20 flights in the previous years without any history of giving up reservations may be allowed to check in remotely hours or perhaps days before the start of the regular time window. Each passenger with a qualifying abandoned reserved seat history may be allowed to use the same amount of time before a conventional window is opened for other passengers. Alternatively, the amount of time that can be used before the regular time window can optionally be calculated based on the relinquishing reserved seat history. In this manner, passengers with an unusually superior abandoned reserved seat history may check in remotely before passengers with only a "good" abandoned reserved seat history, while passengers of the latter category may also check in remotely earlier than the regular check-in window. Historical information may be collected from past flight records and used to flag certain passengers who exhibit a low risk of giving up a reserved seat. Tagged passengers may be allowed to check-in earlier while passengers with little or no history and those with a history of frequently giving up booked seats may only use the ordinary time window.

Fig.3 is a flow chart illustrating the management of a check-in time window as part of remote boarding. After passenger identification (e.g., frequent passenger numbers, credit card account numbers, passenger name records, or the like) is entered, as shown at block 77, the web server 28 interacts with the database server 30 to retrieve the appropriate passenger name record, as shown at block 79. The web server 28 then performs a logic operation to determine if the current time of use by the passenger is greater than (or a fraction of) the predetermined number of hours X before the flight takes off, as shown in block 81. If so, the web server 28 refuses to check-in remotely and advises the passenger that the check-in remotely is too early for the designated flight at this time, as shown in block 83. If the usage time is not too early, it is determined if the current usage time is less than a predetermined number of hours Y (or a fraction thereof) before the flight takes off, as shown in block 85. If so, the web server 28 refuses to check-in remotely and advises the passenger that the check-in remotely is late for the designated flight, as shown in block 87. If not, the passenger is allowed to check in, as shown in block 89.

Fig.4 is a flow chart illustrating the management of a selective check-in time window as part of remote boarding. After the passenger identification is entered, as shown in block 91, the web server 28 interacts with the database server 30 to retrieve the appropriate passenger name record, as shown in block 93. The web server 28 then confirms whether the designated passenger is flagged as eligible for an earlier check-in window based on historical drop-out reservation information or other criteria, as shown in block 93. Other criteria may even include the passenger's payment of a fee or membership in a mileage-based category, applicable to earlier time windows. If the passenger is not marked in the earlier check-in window, the web server 28 performs a time window validation substantially in accordance with that shown in FIG. 3. Such confirmation is illustrated by blocks 97, 99, 101, 103 and 105.

If the passenger is flagged as eligible for an earlier check-in window, the web server 28 performs a logical calculation to determine if the passenger's current access time is greater than (or a fraction of) the predetermined number of hours X + Z before the flight departs, as shown in block 107. Z represents an increased number of times provided to the passenger before the standard time X before departure of the flight. If so, the web server 28 refuses to check-in remotely and advises the passenger that the check-in remotely is current for the designated flight at this time, as shown in block 99. If the usage time is not too early, then a determination is made as to whether the current access time is less than a predetermined number of hours Y (or a fraction thereof) before the flight departs, as shown in block 109. If so, the web server 28 refuses to check-in remotely and advises the passenger that the check-in remotely is late for the designated flight, as shown in block 103. If not, the passenger is allowed to check in remotely, as shown in block 105.

Fig.5 is a flowchart illustrating management of an irregular work session as part of remote boarding. After the passenger identification is entered, as shown in block 111, the web server 28 interacts with the database server 30 to retrieve the appropriate passenger name record, as shown in block 113. The network server 28 then analyzes the record to identify irregular jobs ("IRROPS"), such as flight cancellation or late hours, as shown in block 115. If IRROPS is not indicated to occur, the passenger is allowed to check-in remotely according to normal procedures. If IRROPS indicates the occurrence, the network server 28 retrieves the alternative route, as shown in block 119. The alternative routes may be loaded into the database 32 automatically or manually by the booking agent. If the passenger indicates that the alternative route is acceptable, as shown in block 121, the web server 28 transmits a message print or record service credential, as shown in block 123. When the service voucher is submitted to the airline operator, the passenger can obtain various vouchers, such as a charged telephone card, a meal ticket and the like.

If the passenger does not accept the alternative route, the web server 28 queries the database server 30 for more route options, as shown in block 125 of FIG. 5. If the alternative route is acceptable, as shown in block 127, the passenger receives the service credential and completes the remote check-in, as shown in blocks 123 and 117, respectively. If the passenger does not accept, the passenger receives the service credential, as shown in block 129, but is notified to find an airline representative, such as a ticketing agent, as shown in block 131.

Fig. 6-14 illustrate various web pages generated during a typical remote boarding process. Such web pages may be displayed by desktop computers, laptop computers, interactive televisions, PDAs, internet-enabled mobile phones, and other internet devices. For some devices, however, the web content may be shortened, truncated, formatted, or otherwise altered to facilitate display and possibly save transmission bandwidth. For example, fig.6 illustrates a web browser window with a web page 78 displayed to an airline passenger when entering personal identification information during a check-in process. As shown in fig.6, the web page 78 may include text entry boxes for entering the passenger's name, flight departure city, and frequent passenger number, credit card account number, or confirmation number, i.e., passenger name record number.

Fig.7 illustrates a web browser window with a web page 80 displayed to the flight passenger when retrieving reservation records during a check-in process. The web page 80 indicates that the associated subscription has been retrieved, if necessary, and may include selected information. Fig.8 illustrates a web browser window with a web page 82 displayed to an airline passenger when a designated passenger is selected during a check-in procedure. In the case where multiple passenger name records are retrieved, the user selects the relevant passenger from a list of several passengers, for example, by entering media using check boxes appearing on a web page. In the example of fig.8, however, only a single passenger name record is retrieved. The selection using an input medium (e.g., mouse, trackball, stylus, keyboard, and the like) indicates that the passenger name displayed for boarding the check-in is correct.

Fig.9 illustrates a web browser window with a web page 84 displayed to the flight passenger at the time of airline confirmation during the check-in of a remote check-in. As shown in FIG.9, when selected by the passenger, the web page 84 displays relevant passenger route information, including a departure city, an arrival city, departure and arrival times, and a travel date. The displayed route may also allow the passenger to verify that the correct frequent passenger number has been added to the record. After viewing the route, the passenger clicks the "continue" button to complete the boarding pass.

As further shown in fig.9, fig.9 shows the seat allocation for each flight. Seat assignments may be made automatically by the booking application or manually entered by the booking agent or travel agency. In each case, the web server 28 may be configured to generate additional web pages that allow the passenger to modify the assigned seats. In some embodiments, web server 28 may generate a web page, provide a textual list of available seats, graphically display the location of the bookable seats in the aircraft, or generate both.

Fig.10 illustrates a web browser window with a web page 86 displayed to the flight passenger upon security confirmation during the check-in of a remote check-in. For example, web page 86 asks conventional questions: "do you know you ask you to carry an item on the flight? "and" can you travel with an item temporarily out of your direct control during the time that the item is packed onto your airplane? Check boxes on the web page allow the passenger to answer yes or no to the question. The particular problem will be subject to the regulations of the administrative legislation and may be subject to repeated changes and the problems may be different in various regions.

Fig.11 illustrates a web browser window with a web page 88 displayed to the flight passenger when notifying a contact information request during the check-in of a remote check-in the case of international travel. The web page 88 merely suggests that the passenger needs to complete such information upon arrival at the airport. Alternatively, the passenger may be allowed to enter such information online.

Fig.12 illustrates a web browser window with a web page 90 displayed to the flight passenger when notifying the ticket envelope of the waiver statement information during the check-in process. As shown in FIG.12, web page 90 may also provide hypertext links to other informational web pages.

Fig.13 illustrates a web browser window with a web page 92 displayed to the flight passenger when notifying the ticket of printing instructions during a check-in procedure. When the user clicks the continue button, a web page with boarding pass information appears. If the user device is equipped with a printer, the user simply clicks on the print icon in the web browser toolbar to print out a copy of the boarding pass that may be taken to the airport.

Fig.14 illustrates a web browser window with a web page 94 displayed to the flight passenger after the remote check-in is complete. Web page 94 indicates that the check-in is complete and provides a "continue" link to direct the user to the airline home page.

Claims (16)

1. A method for airline passenger check-in, comprising:

receiving a request for checking in a flight passenger through a computer network;

comparing the time at which the check-in request is received with the permitted time period;

if the time at which the check-in request is received is within the permitted time period, the passenger is confirmed for seat assignment on the designated flight in response to the check-in request.

2. The method of claim 1, further comprising: and refusing to perform seat allocation confirmation for the passenger when the time for receiving the check-in request is greater than a first predetermined time period before the departure of the flight or less than a second predetermined time period before the departure of the flight.

3. The method of claim 1, further comprising: different permission periods are specified for different passengers.

4. The method of claim 1, further comprising: different permission periods are specified for different passengers based on the history of each passenger giving up a reserved seat in the past.

5. The method of claim 1, wherein the passenger is located at a location remote from an airport terminal associated with the departure of the designated flight, the method further comprising receiving a check-in request at a server located remote from the passenger.

6. The method of claim 1, further comprising:

confirming whether the designated flight associated with the check-in request is late or cancelled; and is

If so, the seat assignment is confirmed on the other flight in response to the check-in request.

7. The method of claim 1, further comprising: a check-in request is received at a server located a significant distance from the airport terminal associated with the departure of the designated flight.

8. The method of claim 1, wherein the computer network is the internet, further comprising: a check-in request is received at a network server connected to the world wide web.

9. The method of claim 1, further comprising: the method further includes recording the confirmed seat assignment, modifying the seat reservation system database to indicate the confirmed seat assignment, and transmitting the confirmed seat assignment to the passenger over the computer network.

10. The method of claim 1, further comprising: information representing the confirmed seat assignment is printed on a printer associated with the passenger and a security mark is printed with the printed information to verify the authenticity of the confirmed seat assignment.

11. The method of claim 1, wherein the passenger transmits the check-in request from one of a desktop computer, a portable computer, a PDA, a mobile phone, and an interactive television.

12. A system for performing an airline passenger check-in method according to any of claims 1 to 12, the system comprising:

a network client for transmitting a check-in request of the airline passenger through a computer network;

and the network server receives the check-in request through the computer network, compares the time of receiving the check-in request with the allowable time period, and responds to the check-in request to confirm the seat allocation for the passenger on the appointed flight if the time of receiving the check-in request is within the allowable time period.

13. A computer readable medium storing program code which when executed causes one or more programmable processors to perform the method of any one of claims 1 to 11.

14. A method for airline passenger check-in, the method comprising:

receiving a request for checking in a flight passenger through a computer network;

confirming whether the designated flight associated with the check-in request is late or cancelled; and is

If so, the seat assignment is confirmed on another flight in response to the check-in request.

15. A system for performing the airline passenger check-in method of claim 14, the system comprising:

a network client for transmitting a request for check-in of the airline passenger through a computer network;

a web server receiving a check-in request over a computer network, the server determining whether a designated flight associated with the check-in request is late or cancelled, and if so, confirming seat assignment for the passenger on another flight in response to the check-in request.

16. A computer readable medium storing program code that when executed causes one or more programmable processors to perform the method of claim 14.