WO2006029637A1

WO2006029637A1 - Method for accomplishing a data communication, system and software product

Info

Publication number: WO2006029637A1
Application number: PCT/EP2004/010217
Authority: WO
Inventors: Klaus Heeder
Original assignee: Sita Information Networking Computing N.V.
Priority date: 2004-09-13
Filing date: 2004-09-13
Publication date: 2006-03-23

Abstract

The invention relates to a method for accomplishing a data communication of a first data processing module with at least two data hosts, comprising the steps of: receiving at least one transaction command of the first data processing module by at least one second data processing module; identification of the received transaction command and identification of the data host with which the transaction has to be accomplished by the second data processing module; converting of the received transaction command into a message sequence comprising at least one message set by the second data processing module, wherein number of message sets comprised in the message sequence depends on the identified data host and the received transaction command; and communicating the message sets of the message sequence between the second data processing module and the identified data host.

Description

SITA Information Networking Computing N.V.

Heathrowstraat 10 (Sloterdijk) 1043CH Amsterdam, Netherlands

Method for accomplishing a data communication, system and software product

The invention relates to a method for accomplishment a data communication of a first data processing module with at least two data hosts, a system and a software product.

In the state of the art different attempts were made to allow the data communication of different elements within a communication system. For example the US 5,912,897 discloses a method for converting different formats in communication systems. To allow a communication using different releases of a software this method uses a conversion table which defines how to convert a single message from one system to another. During this conversion message elements in this single message can be added or deleted. The disadvantage of this method is that it does not allow the communication of different system elements using different message sequences to reach one and the same transaction.

Furthermore, the DE 102 41 197 Al discloses a message conversion method. By this method a conversion of different signalisation protocols of different communication systems is reached. Thus, also by this method only converting signalisation protocols a communication between data servers using different message sequences for one and the same transaction is not possible.

The US 2002/0147823 Al discloses a computer network system comprising a plurality of hosts and plurality of hubs in which at least one host can communicate with a hub through a connection service using one or more host protocols. To allow the communication a message mapping is accomplished to translate a XML message into a native command format of a host and to translate the host response back into a XML message. But this mapping does not allow the communication with a plurality of data hosts using different message sequences for one and the same transaction. In the state of the art also data filtering methods and filter tools are known to evaluate data for different purposes.

For example the US 6,295,527 Bl discloses a filter tool for establishing and viewing groups of devices within a network of devices. A filter mechanism receives information about different network devices by a polling service, that means an automatic, sequential testing of each potential servers of input of the network. The received information are stored and the stored data are later searched for a filtering of the data. The disadvantage of such a filter tool is that the data is not received from selected data sources and that only the data interesting for the filtering are stored. Thus, the filter process is very time consuming and needs a lot of storing resources.

Furthermore, the US 2001/0039540 Al discloses a method and structure for dynamic conversion of data especially to convert a data from multiple sources to multiple clients enabling for each user to see the wished data. To reach this conversion dynamic filters are constructed by using and combining a set of partial filter adapters. The disadvantage of this method is that it cannot be used for filtering data when in one filtering process different filter criteria has to be fulfilled whereby the different filter data are located on different data servers.

Furthermore, different methods of tracking the local position of an object are known in the state of the art.

For example the US 6,741,927 B2 discloses a user definable communication method and system to notify a user in advance of the impending arrival of a vehicle or a user, for example a bus, a train or a delivery van. For the tracking of the object a global position system or a delivery list together with information about accomplished deliveries is used to estimate the location of the object. Thus, additional devices or a complex tracking method are used.

Furthermore, the WO 2004/034721 Al discloses a method of providing information regarding a mobile station. By this method it is indicated whether the mobile station is leaving or entering an area around a respective base station with which the mobile station communicates during the normal use. In the sense of this application check-in means the final seat and/or plane assignment for a passenger, this includes, if necessary, the marking of a boarding pass document as printed in at least one database of at least one transportation company, i.e. the registration of a passenger in a passenger list, preferably followed by a confirmation check-in message issued by the transportation company.

Finally different check-in systems for a passenger, especially an air passenger, were proposed. For the time being when a passenger has planed a flight, he contacts the airline or a travel agency and makes a reservation for a specific trip. After doing so the passenger receives a ticket that is issued by a booking or a reservation (RES) system of the specific airline. Before starting the flight the passenger has to complete a check-in and boarding procedure at the departure airport. For this reason the passenger contacts the airline, after arriving at the airport, either by contacting a airline employee at a counter or using a check-in terminal. In both ways a connection to a database of the airline reservation system is build up to verify the data of the flight ticket. Furthermore the passenger can make a seat selection and can check-in his baggage. After this check-in procedure at the airport a boarding pass is generated by printing out a physical boarding pass which is handed out to the passenger. Additionally the flight data of this passenger is sent and stored in a departure control system (DCS) of the airline. After this check-in procedure the passenger goes to the departure gate. Before entering the gate the passenger has to run through a vetting procedure. During this procedure he hands out his boarding pass and an ID to an employee of the airline or the airport which verifies the data of the boarding pass with the ID of the passenger. In the last phase before the flight a last verification of the data of the boarding pass is made. The boarding pass is for example put into a boarding pass reader which is in data connection to the DCS of the airline. After this final verification of the boarding pass data with the data stored in the departure control system the passenger can board the airplane.

The disadvantage of the above check-in and boarding procedure is that the passenger has to be at the airport during the check-in procedure and he has to locate the representents of the specific airline he wants to travel with.

In the UK patent GB 2361570 B a method of operating and ticketing system for avoiding paper documents is proposed. After a passenger has made a reservation a Passenger Name Record (PNR) code is sent to a mobile station associated with the passenger, like a mobile phone. This PNR code is used as a electronic ticket as follows. In the mobile station the PNR code is converted into a barcode format which is displayed on a display of the mobile station. This barcode can be read by a barcode reader during each phase of the check-in and boarding procedure. The disadvantage of this method is that the barcode reader has to be connected to the airline RES or DCS of the airline to check whether the passenger has a valid ticket and whether this ticket is used by the right person, especially during the vetting procedure before entering the departure gate. This necessitates the installation of additional reading devices which has to be connected to the airline databases and the passenger has still to be present at the airport for the check-in procedure. Furthermore, this method does not allow the handling of passengers using different airlines.

Furthermore, it is know in the state of the art that ticket data, that is transferred to a mobile device can be used to redeem this ticket. For example the US 2004/0039635 Al discloses a ticketing apparatus and method. After a user has purchased a ticket at a ticket centre the ticket centre sends a person user identification ticket to a wireless device, for example a mobile phone. During the purchase the ticket data are read out of the mobile phone, for example by using a barcode reader and a ticket data is compared with tickets data contained in a data base for verification purposes. The disadvantage of this method is that a connection to a data base comprising the details of valid tickets of the reading device has to exist.

The EP 1 341 327 Al discloses a mobile terminal and electronic commerce system. A mobile phone of a consumer can receive via a mobile phone provider an encrypted registration number which is associated with product information. When the consumer goes subsequently to a shop where a reading device is located this information can be transferred to this reading device. After this data transfer a verification of the registration number with a virtual shop is accomplished, which makes the use of a live data connection between the reading device and the virtual shop necessary. Such a connection to a central data base is also necessary if the commerce system is used for a reservation system for airports. Thus, high costs arise when installing the reading devices.

Furthermore, the US 2003/0105954 Al discloses a method, system and computer program product for secure ticketing in a communications device. In this system a mobile device can receive a ticket via a radiolink from an issuing device. To use the electronic ticket the user sends the ticket data to a collection device via a radio connection. To redeem the ticket it is necessary that the mobile device communicates bi-directional with the collection device, wherein the data has to be decrypted, changed and encrypted actively by the mobile device. Thus a complicated method has to be used to redeem the ticket after the ticket data has been sent to the mobile device.

Furthermore, it is known from the US 6,736,322 B2, which discloses a generic method for communicating information in barcode form with a mobile communication device, that a user can request a boarding pass in a barcode form from a special airline to avoid paper documents. After the boarding pass is received from the mobile communication device the user contacts a special ticket airline agent who checks the user identification and scans the barcode displayed on the mobile communication device to enable the user to board the airplane. The barcode scanner is connected to an airline computer to allow the verification of the boarding pass data. Thus, this barcode reader also needs a live connection to a data base and furthermore also this method does not allow the handling of passengers of different airlines.

Thus, it is the object of the present invention to further develop the method and the system for accomplishment a data communication of a first data processing module with at least two data hosts, especially to provide a method and a system that allows the data communication of different system elements using different message sequences to reach one and the same transaction.

According to a first aspect of the invention this object is achieved in that the method comprises the steps of

- receiving at least one transaction command of the first data processing module by at least one second data processing module,

- identification of the received transaction command and identification of the data host with which the transaction has to be accomplished by the second data processing module,

- converting of the received transaction command into a message sequence comprising at least one message set by the second data processing module, wherein number of message sets comprised in the message sequence depends on the identified data host and the received transaction command, and communicating the message sets of the message sequence between the second data processing module and the identified data host. With the invention is preferred that the message sequence comprises at least two message sets which are communicated subsequently between the second data processing module and the identified data host.

In both above two mentioned embodiments it is proposed with the invention that after the receiving of the transaction command the storing of the transaction command, preferably in the second data processing module.

It is also possible that the transaction command comprises at least one first parameter, particularly an identification information concerning the identified data host, a username, a password, a PNR identification, a flight number, a departure airport and/or departure city identifier, a destination airport and/or destination city identifier and/or a seat selection.

It is also suggested that the message set comprises at least one first and at least one second message set element, wherein the first message set element comprises at least a first message that has to be sent to the identified data host by the second data processing module and the second message set element comprises at least one second message received as a response of the identified data host to the first message by the second data processing module.

In this latter embodiment it is preferred that the first message comprises at least one second parameter and the second message comprises at least one third parameter, wherein preferably the first, second and/or third parameter is or are stored at least temporarily preferably by the second data processing module.

In the last mentioned embodiment it is proposed with the invention that the first or second parameter and/or the first, second and/or third parameter is or are further processed into at least one fourth parameter, preferably by the second data processing module, which especially is at least temporarily stored, preferably in the second data processing module.

Furthermore it is in the last mentioned embodiment possible that the fourth parameter is further processed into at least one fifth parameter after the communication of a least one subsequent message set of the message sequence with the identified data host, preferably using the first parameter and/or the second and/or the third parameter of the subsequent message set. With the invention the exchanging of at least one transaction result, particularly the first, second, third, fourth and/or fifth parameter between the first and second data processing module after the communication of the complete message sequence with the identified data host is proposed.

An advantageous embodiment is characterized in that the message sequence is retrieved from at least one interface definition table accessible by the second data processing module.

It is also possible that the transaction command, the transaction result, the at least one message set, the first message and/or the second message are sent, received and/or communicated on the same network layer.

Furthermore there is suggested with the invention a method for a check-in procedure of a passenger, preferably a flight passenger, using a mobile device, wherein the inventive method is used during the procedure to allow a data communication with data hosts of a variety of different airlines.

The object of the invention is furthermore achieved according to a second aspect by a system for accomplishing a data communication equipped to carry out the inventive method, comprising at least one first data processing module at least one second data processing module and at least two data hosts, wherein the data hosts are preferably data hosts storing trip related, especially flight related, data of preferably different transportation companies, especially airlines.

In this embodiment it is preferred that at least one Interface definition table is realised in way of at least one plug-in dynamically loadable into the second data processing module and/or dynamically unloadable out of the second data processing module, wherein the Interface definition table can preferably be amended without the necessity to suspend the execution of the first and/or second data processing module.

With the invention it is further proposed that the system is characterized in that the first data processing module, the second data processing module and the data hosts are exchanging the transaction command, the transaction result, the at least one message set, the first message and/or the second message on the same network layer. Finally it is provided a software product comprising program code information to accomplish all steps of the method according to the first aspect of the invention, in the case the software product is executed by a computer processor.

Furthermore it is preferred that this software product comprising program code information, is stored on a computer-readable storage medium.

It is also suggested that this software product comprises program code information stored on a storage medium to accomplish all steps of the method according to the first aspect of the invention, in the case the program is executed by a computer processor.

Thus, the present invention is based on the astonishing perception that a method for accomplishment a data communication of a first data processing module with at least two data hosts can be designed that this data communication is enabled between data processing modules and data hosts using different message sequences to reach one and the same transaction by implementation of a message sequence normalisation.

By the message sequence normalisation a translation of the different message sequences of different data hosts becomes possible. In contrast to a format normalisation or a protocol normalisation by the message sequence normalisation the number of messages send to and/or received by the different data hosts is adapted to the needs of the respective data hosts. Especially in the branch of airlines different message sequence systems has been developed that are assumed to be incompatible to each other. During the message sequence normalisation by a second data processing module, preferably called message sequence normalisation module, that is connected to different data hosts on the one hand and a data requesting and/or sending client on the other hand, a transaction command that can comprise a plurality of parameters necessary for this transaction is received from a first data processing module. The parameters especially comprises at least one identification information to which data host the data has to be sent or from which data host the data has to be received. In the next phase the second data processing module does communicate a respective sequence of messages with the respective data host, including sending and receiving a variety of further parameters that are stored and/or further processed. After the accomplishing of all messages of the predefined message sequence the second data processing module sends to the first data processing module the result of the communication of the message sequence with the respective data host. Thus the first data communication module only sends one transaction command to the second data communication module and receives in the next communication step the result of this transaction. During this time the second data communication module has translated the transaction command into a respective message sequence and has communicated this sequence with the respective data host. Thus the invention overcomes the barrier existing in the data communication with data hosts using different message sequences for one and the same transaction.

Further features and advantages of the invention will become evident from the following description, in which a preferred embodiment of the invention in form of air passenger check- in system is explained by way of an example with reference to schematic drawings, in which:

Fig. 1 is a flow chart showing the actions taken by the user of the check-in system;

Fig. 2 is a flow chart showing the actions taken by a mobile passenger service module of the check-in system;

Fig. 3 is a block diagram schematically illustrating a check-in system implementing the invention;

Fig. 4 is a block diagram schematically illustrating the interaction of a message sequence normalisation module with other elements;

Fig. 5 a shows an example of a transaction table;

Fig. 5b shows an example of an interface definition table;

Fig. 6 is a schematic diagram showing the interaction of a dynamic filter module with other elements;

Fig. 7 is a schematic diagram showing the interaction of a mobile device with a boarding pass generator; and

Fig. 8 is an example of a data record for a boarding pass. In the following the invention will be explained by the description of an embodiment, i.e. an implementation of the invention in form of a mobile air passenger check-in service system. It has to be understood that the invention is not limited to this implementation.

In Fig. 1 the steps a user has to accomplish to use the mobile check-in service are pictured. In a first step 1 the user has to register for the check-in service. After this registration procedure the registration data of the user are stored in a registration user list in step 3. Once the user has registered for the check-in service the user can contact a registration service of a transportation company in form of an airline or a travel agent to buy a flight ticket. After this ticket purchase in step 5 the ticket data are stored in a reservation (RES) system of the transportation company in form of an airline or air carrier for which the user has purchased a flight in step 7. As shown later these reservation data are stored by a data host of the airline and are accessible by the mobile check-in system, hi a following step the user can start a check-in procedure via a mobile device, for example a mobile phone, a PDA and/or a handheld PC in step 9. Preferably this check-in procedure is realized by a JAVA application or another device specific application stored on the mobile device.

Because a mobile device is used for this check-in procedure, as shown later, the user is flexible when and where to start the check-in procedure, especially he has not to be present at the airport. Especially in the short time prior the departure of an airplane many people want to check-in at the airport during this time. By using the mobile device for the check-in procedure the user can avoid to check-in during such peak hours at crowded check-in counters or check- in terminals. Furthermore, contrary to a check-in procedure via the world wide web (www) the user is not locally fixed to do check-in where he has access to the world wide web.

The details of this check-in procedure are given below and after finishing this check-in procedure the user receives in step 11 via his mobile device boarding pass data from the mobile check-in system. As shown later the boarding pass data are transferred in a special encrypted form and when the user arrives at the airport he uses this data stored in the mobile device to generate a boarding pass.

As shown below in a special embodiment of the check-in system a physical boarding pass as known in the state of the art in which the boarding data are printed on or stored on a magnetic strip is generated. The transfer of the boarding pass data from the mobile device to the boarding pass generator can be reached by a visual transfer of the data for example by using a two-dimensional barcode displayed on the mobile device and scanned by the boarding pass generator or via a wireless connection as short distance communication methods, e.g. Bluetooth^® and/or short distance link (SDL) or infrared connections between the mobile device and the boarding pass generator. After generating the boarding pass the user can show the boarding pass during security checks together with his ID. At the gate the passenger can use this boarding pass to board the airplane in the step 15 as known in the state of the art without the necessity to install additional reading devices for the boarding pass data stored on the mobile device beside the boarding pass generator.

In Fig. 2 the steps accomplished by the mobile check-in system are shown. In the step 21 the mobile check-in system connects, as shown later, to a data host of the operation systems (OPS) of a plurality of airlines to retrieve information concerning the flights provided by the airlines on a variety of different airports. In step 23 a transportation trip list in form of a flight list comprising the retrieved information is stored in the mobile check-in system and this flight list is used in a step 25 to accomplish a passenger eligibility check which user fulfils special criteria mainly specified by the respective airline. As shown later, during this eligibility check the data of the RES systems of the plurality of airlines and the data of the departure control system (DCS) of this airline are used. AU users or passengers which fulfil the eligibility criteria will be stored in step 27 in an eligible passenger list of the mobile check-in system. Depending on different criteria the users stored in the eligible passenger list can be notified in a step 29 to start the mobile check-in service via a mobile device. In step 31, which is identical to the step 9 in Fig. 1, a check-in service is provided to a mobile device of a user and to the departure control system of one or a plurality of airlines. After finishing the check-in service in step 31 a boarding passenger list is stored in the mobile check-in system in step 33 and boarding pass data are transferred to the mobile device of the user in step 35. As in one preferred embodiment no verification of the boarding pass data is necessary with the mobile check-in system, the check-in process is finished with step 35 for the mobile check-in system.

In Fig. 3 a schematic overview is given over the elements comprised by the mobile check-in system and the connections to other elements cooperating with the mobile check-in system are shown. With aid of Fig. 3 the details of the procedures shown in Fig. 1 and 2 are now described. The core element of the mobile check-in system is the mobile passenger service module 15. In a preferred embodiment this mobile passenger service module is realized by a software application executed on a computer processor. The mobile passenger service module 50 is cooperating with a registration module 52.

In a preferred embodiment the registration module 52 is realized by a web based interface application. By the registration module 52 a future user of the mobile check-in system can provide the necessary information to the mobile passenger service module 50. For example the user provides the following details: full name, e-mail address, mobile phone details, frequent flyer account, home or base airport, APIS information (i.e. passport number, nationality, expiry date), a seat selection preference, i.e. whether the user wants to sit in a window/idle/middle seat, near to an emergency exit, on the right or the left side of an airplane and/or on a specific seat, and/or notification preferences, i.e. whether the user wants to be notified in step 29 by receiving a notification on the mobile device 84 a specific time period before the departure of flight and/or by a notification when he approaches an airport, as described later.

Via the registration module 52 it is further possible for the user to modify his personal details, for example changing the mobile phone detail, e-mail address, frequent flyer number, base airport, flight preferences, seat selection preferences and/or notification preferences. As mentioned concerning step 3 in Fig. 1 this details of the user are stored in a registered user list 54. This registered user list 54 is comprised by a relational data base management system (RDBMS) module 56 of the mobile check-in system.

Furthermore, the module 56 comprises a flight list 58. In this flight list 58 all flights are stored in the step 23 shown in Fig. 2 for which a passenger eligibility test in step 25 is accomplished. For building up the flight list 58 the mobile passenger service module 50 contacts a plurality of data hosts of a variety of airlines to receive the respective flight data. The mobile passenger service module 50 does contact especially data hosts 60a, 60b of the operating systems of airlines 1 to N and/or data hosts 62a, 62b of DCS systems of airlines 1 to N. The invention allows the mobile check-in system the communication with the different data hosts of the different airlines, thus that a multi-airline environment can be handled. This communication with the data host 60a, 60b, 62a, 62b becomes possible via the inventive message sequence normalisation module 64. The functionality of the inventive message sequence normalisation module 64 will now be explained with reference to the Figs. 4 to 5b. To allow a communication between the mobile passenger service module 50 representing a first data processing module and a plurality of X data hosts 66a, 66b, for example the data hosts 60a, 60b, 62a, 62b, beside a format normalisation and a protocol normalisation of the communication messages, a message sequence normalisation is accomplished by the message sequence normalisation module 64 representing a second data processing module. During a communication between the mobile passenger service module 50 and the data hosts 66a, 66b a transaction command preferably comprising a plurality of first parameters, like a username, a password, a registration number, is sent from the mobile passenger service module 50 to the message sequence normalisation module 64. In Fig. 5a an example of a transaction list used by the mobile passenger service module 50 is shown. The transaction commands of the transaction list are subsequently sent to the message sequence normalisation module 64. The transaction list comprises N transactions 68a, 68b, 68c, 68d and 68e named as TA₁, TA₂, TA₃, ..., TAN_-1 and TA_N. For example the transaction command 68a stands for the transaction TA₁ for connecting to a data host 66a, 66b, for example the data host 66a. The message sequence normalisation module 64 is cooperating with an interface definition table 70. One example of such an interface definition table 70 is shown in Fig. 5b. The interface definition table 70 comprises message sequences 70a, 70b, 70c, wherein each message sequence 70a, 70b, 70c comprises a first message set element 71a and a second message set element 71b. In each line of the message sequence 70a, 70b, 70c in the first message set element 71a a message that has to be sent to the data host is defined whereas in the second message set element 71b the response message of the data host to the sent message is defined. Thus in the interface definition table 70 it is defined that when the transaction TA₁ has to be accomplished with the data host 1 first a message 1S¹M₁ ¹I , preferably comprising a second parameter, like a registration number, has to be sent and a response message

, preferably comprising a third parameter, like a verification information, is sent back from the data host 1. After receiving the message RM\ 1 the message preferably comprising at least one further second parameter, e.g. the verification information and the username, is sent to the host 1 and no return message will be sent from the host 1. Thus, after sending the message SM₁ ¹2 the message SM₁ ¹3 , e.g. comprising a password is sent to the host 1 and the message RM\ 2 is received from the host 1 by the message sequence normalisation module 64. After sending and receiving further messages to accomplish the transaction TA₁ with the host 1 finally the message

Y is sent and the message

Z is received from the host 1. After finishing the transaction TA₁ the message sequence normalisation module 64 sends the data probably received from the host 1 to the Mobile Passenger Service Module 50. As can be seen from the Fig. 5b in the interface definition table 70 it is defined that for accomplishing the transaction TA₁ with the host 2 in contrary to the accomplishing of the transaction TA₁ with the host 1 only one message has to be sent, namely the message SM₁ ²I and from the host 2 the message RMf I is received. Furthermore it can be seen from Fig. 5b that for accomplishing the transaction TA₁ with the host X only one message SMf 1 has to be sent and no reply is received from the data host X. Thus the message sequence normalisation module 64 allows the communication of the mobile passenger service module 50 with the different data bases of the variety of different airlines using different numbers of messages to accomplish a transaction.

During this communication with the data hosts 60a, 60b, 62a, 62b to build up the flight list 58 the mobile passenger service module 50 communicates with these data hosts via the message sequence normalisation module 64 to monitor a number of flights due for boarding and departure in a predefined time range. The list of flights to be monitored is preferably defined as a set of range defined on basis of a carrier code of the airline, departure time and/or a flight number. It is also possible that special flights are not stored in the flight list 58 using exclusions criteria as date of the flight, day of the week, departure city, arrival city, the number of stopovers etc. Once the flight list 58 is build up only the flights that are listed therein and that are in a predefined coverage time concerning for example the departure time, are monitored preferably with a predefined monitoring frequency. By this monitoring the flight data for the flights already stored in the flight list 58 are updated by receiving the respective data from the data hosts 60a, 60b, 62a, 62b if a change for example in the departure or arrival time will arise or if flights are cancelled. The monitoring frequency could be for example 15 minutes and the coverage time could be 24 hours that all flight within the next 24 hours are monitored every 15 minutes. It is also possible that the mobile passenger service module 50 is configured in this way that blackout periods are defined for example if regular maintenance work is done at the data hosts 60a, 60b, 62a, 62b of the airlines. During this blackout times no flight monitoring is performed by the mobile passenger service module 50 for the respective flights.

Once the flight list 58 is stored a passenger eligibility check for each flight in the flight list 58 is accomplished. The mobile passenger service module 50 retrieves a passenger list from the data hosts 72a, 72b of the reservation system of the respective airlines 1 to N depending which airline is handling the flight in the flight list 58. This data retrieving from the data hosts 72a, 72b is also performed using the inventive message sequence normalisation module 64 and it returns to the mobile passenger service module 50 the passenger data for the passengers booked on that flight, especially the following data of the passenger name record (PNR): passenger name, air segments, urgent indicator, destination indicator, ticket types, group travel indicators, security alerts indicators, frequent flyer details and/or passenger e-mail address. The received data is then filtered to build up a eligible passenger list 74.

These filtering is accomplished as follows and explained with reference to Fig. 6. The mobile passenger service module 50 comprises a dynamic filter module 76 representing a first data processing module. It is possible that each airline can define its own eligibility criteria list in which the criteria are defined which a passenger has to fulfil that he can use the mobile check- in service provided by the mobile passenger service module 50. The dynamic filter module 76 is connected with this eligibility criteria list 78 for each airline. During the eligibility check the dynamic filter module 76 retrieves a first logical record in form of flight information from the flight list 58. For each passenger of each flight listed in the flight list the dynamic filter module 76 receives at least one eligibility criteria from the eligibility criteria list 78 for the respective airline. As can be seen from Fig. 6 the dynamic filter module 76 receives the above mentioned passenger data representing a second logical record via the method sequence normalisation module 64 from the data hosts 62a, 62b, 72a, 72b. In the first step the dynamic filter module 76 checks if the passenger is listed in the registered user list 54. If this is the case the dynamic filter module 76 compares each eligibility criteria of the airline listed in the list 78 for the respective airline with the passenger data received from the data hosts 62a, 62b, 72a, 72b. In the case that a eligibility criteria is given by the airline and the necessary passenger data cannot be received from the data hosts 62a, 62b, 72a, 72b the dynamic filter module 76 contacts a data location table 80. In this data location table 80 the location of respective passenger data is stored. For example it is possible that the reservation data host 72a, 72b can only provide the dynamic filter module 76 with a frequent traveller number or another unique identifier without the information of the frequent traveller mileage account of this passenger. For example this data is stored in one of the data hosts 1 to X, e.g. the data host 1 (82a). In this case in the data location table 80 it is stored that the dynamic filter module 76 needs the frequent travel number received from one of the data hosts 62a, 62b, 72a, 72b and has to sent a request comprising the frequent traveller number to the data host 82a to retrieve the mileage account representing a third logical record of the passenger in dispute. This procedure is repeated for each passenger for each eligibility criteria stored in the eligibility criteria list 78 for the respective airline. If the passenger fulfils every eligibility criteria his data is stored in the eligible passenger list 74. It is preferred that the eligibility check for one passenger is interrupted when one criteria is not fulfilled by the passenger.

In a preferred embodiment the dynamic filter module 76 is realized as a software application and the data location table 80 as well as the eligibility criteria list 78 are realized as dynamically loadable and dynamically unloadable plug-ins for this application. This leads to the advantage that the execution of the dynamic filter module 76 has not to be stopped to implement new eligibility criteria into the list 78 for one airline as well as to add new information where respective data can be found on the different data hosts 62a, 62b, 72a, 72b, 82a, 82b to the data location table 80. Thus a very flexible filter application is provided. Examples for the eligibility criteria are whether the frequent flyer details, mobile phone details and/or e-mail address details received from the reservation or DCS system of the airline match with the data in the registered user list 54. It is also possible that all passengers are excluded when the PNR comprises more than one name or no name, no assignments, no origin destination information, a fraud prompt indicator and/or a group indicator. It is also possible that passengers are excluded which have connecting flights or interline connecting flights or connection taking place at an airport listed in a exclusion list. Furthermore it is possible to exclude passengers from the eligibility passenger list 74 which have made a special service request, for example unaccompanied minors, passengers needing oxygen, prisoners, passengers having animal in hold, passengers that have a pet in the cabin, passengers with fire arms, passengers with a transit without visa or wheelchair passengers. Usually this data are all stored on different data hosts beside the RES and DCS system data hosts of the airlines and thus the dynamic filter tool 76 contacts first the eligibility criteria list 78 to receive the criteria and than uses the data location table 80 to retrieve the information where to find the respective data that has to be filtered/compared with the eligibility criteria.

It has to be noted that the mobile check-in service system also allows the first tune in the state of the art a check-in of a whole group, e.g. a couple, via one mobile device. In these cases the PNR record comprises more than one passenger identification. During the check-in of such a group first the data sets of the passengers are separated, mainly as the check-in procedure via the check-in system is personalized to the user of the respective mobile phone. First the check-procedure for a first passenger of the group, including the sending of the necessary information to the DCS system of the respective airline is accomplished. Subsequently the check-in of the next passenger is accomplished. For identification purposes of this subsequent passenger of the group preferably the personal data stored in the registered user list are used. For example in the registered user list it is stored that the second person can accomplish a check-in also via the mobile device of the passenger checked in prior when they are travelling as one group. After such an identification the check-in for this passenger is accomplished, wherein preferably the data, e.g. flight number of the check-in of at least one prior checked-in person of the group is used. Thus preferably for the subsequent passenger only the seat choice has to be accomplished.

After the eligible passenger list 74 has been stored in step 27 a eligible passenger can initiate a check-in procedure via his mobile device 84. It is preferred that the passenger receives a notification that the check-in service via the mobile device 84 is available for him. Such a notification can comprise a written message like a SMS (Short Message Service), FMS (Flash Message Service) and/or an e-mail that is sent to the mobile device 84 as well as a call via the mobile device 84, for example including an automatic voice message.

It is also possible that the passenger is notified via a so called send/retrieve procedure. The newest generation of mobile devices are all the time switched on, at least in a stand-by mode and allow at any time a communication between with the mobile device via the mobile network. This makes it possible that also when the mobile device is in a stand-by mode via the send/retrieve procedure a notification can be send to the mobile device, that preferably causes the mobile device to change in a operational mode. After the notification is displayed via the mobile device the user may start with preferably one confirmation action, like pressing one key on the mobile device, an application on the mobile device which is predefined by the content of the notification message. Thus the passenger can initiate the check-in procedure in very comfortable and uncomplicated way when receiving such a notification via a send/retrieve procedure.

As described above during the registration procedure a user can define his personal notification preferences. It is for example possible that the user decides that he does not want any notification that he can initiate the mobile check-in service. It is also possible that the user decides that he will be notified a predefined period of time before the flight departure of the flight that he can check-in via the mobile device 84. In a preferred embodiment the notification process uses a local tracking of the mobile device 84. If the user has agreed to authorizing access to a location tracking information concerning his mobile device 84 he will be notified when his mobile device 84 is localized in a predefined area around a departure airport from which the user will depart with a flight for which a mobile check-in service is available as the passenger is stored in the eligible passenger list 74 and the respective flight is stored in the flight list 58. The details when such a location based notification is sent can also be defined by the user with his notification preferences. It is possible that the notification is sent when the mobile device 84 is tracked within a predefined radius around the respective airport or when the mobile device 84 is localized in an area around a predefined address not being a destination airport, for example a parking lot that is usually used by the passenger when departing from a respective airport. For this notification process the mobile passenger service module 50 also comprises a data base table to store a list of notifications. In this internal data base table all notification procedures for the variety of passengers are stored. Especially the status of the notification process is stored, i.e. whether the notification is pending to be send, is send, is discarded or returned an error. To avoid a duplication of notifications new notifications requests are verified against the stored internal database table. It is also possible that new passengers can be added to a list of pending notifications, including a copy of their flight information, PNR and/or customer profile. Via this notification process the check-in processes via mobile devices 84 of the variety of the users or passengers can be timely distributed to avoid peak times and also the comfort for the passenger and user is increased as he can do the check-in procedure via his mobile device 84 when it is comfortable for him.

After finishing this notification process in step 29 of Fig. 2, which can be, as explained above, skipped, the passenger which is stored in the eligible passenger list 74 can initiate a check-in service in step 9 and 31 respectively. The aim of this check-in procedure via the mobile device 84 of the passenger is that the DCS system of the respective airline is provided with the necessary information that the passenger can be put on a passenger list as well as providing the passenger with the necessary boarding pass data as explained below. In a preferred embodiment the mobile check-in procedure is accomplished via an application, especially a java application, that is installed on the mobile device 84. Preferably this installation of the application takes place during the registration process in step 1 via the registration module 52. When starting the check-in process via the mobile device 84, in particular using the before mentioned application, the user preferably has to log in using a user name and a password before allowing access to the check-in steps described below. It is also possible that a combination of a user name, password and/or an identifier of the mobile device 84 are used for authentication purposes. During this procedure the mobile passenger service module 50 especially verifies the data sent by the mobile device 84 with the data of the registered user list 54. After accomplishing this log in procedure the mobile passenger service module 50 starts to query the eligible passenger list 74 using the personal data of the respective user. In particular the PNR reference number, the passenger name or the frequent traveller number can be used to retrieve a list of flights for which the user can check-in via the mobile device 84 during the check-in procedure. It is important to notice that more than one flight can be handled during this mobile check-in procedure. For example it is possible that a passenger has purchased a ticket in step 5 which allows him to use different flights of one airline between one predefined departure airport and one predefined arrival airport within a special time period, for example within one day. Probably the user can check-in in different flights of different airlines between these departure and destination airports within a predefined time period with this ticket. Thus, if the user fulfils the eligibility criteria of the different airlines he can probably choose between different flights, especially of different airlines during this check-in procedure. It is also possible that the ticket allows the user to depart from a variety of different departure airports within a predefined area, for example to depart from one airport in Chicago, e.g. Midway Airport or the OΗare Airport, and to fly to different destination airports within an area, for example the city area of New York, for example the John F. Kennedy Airport, Newark International Airport and/or LaGuardia Airport. Thus the user can chose from a variety flights selected by the mobile passenger service module 50 and displayed via the mobile device 84. In a preferred embodiment the user is informed via the mobile device 84 if one of the departure airports does not provide a baggage drop and that only hand baggage is allowed for the user when accomplishing the check-in procedure via the module device 84.

After selection of a flight the mobile passenger service module 50 contacts via the inventive message sequence normalisation module 64 a respective DCS system of the respective airline of the selected flight. After retrieving information about the available seats from the DCS data host 62a, 62b of the respective airline the user can accomplish a seat selection via the mobile device 84. In a preferred embodiment the mobile passenger service module 50 uses the seat preferences stored in the registered user list 54 to make a pre-assignment of a seat. This pre- assignment is displayed to the user via mobile device 84. It is also possible that a seat preference of the user is retrieved from other data hosts, for example from the data hosts 86a, 86b which preferably store frequent flyer data of the respective user. In a preferred embodiment the passenger has the option to change the seat assignment using a seat map that is retrieved also from the airline DCS system 62a, 62b. If for the connection to the data hosts 62a, 62b of the DCS systems of the airlines APIS data has to be used, the mobile passenger service module 50 uses these APIS data stored in the registered user list 54 to provide this information to a data host 62a, 62b via the message sequence normalisation module 64. If some of the APIS data is not available the user is prompted to enter the necessary APIS data via the mobile device 84 to allow the data communication with the data host 62a, 62b. This information retrieval leads to a significant time saving for the passenger using the mobile check-in service. For the time being this time consuming inquiry concerning APIS data is accomplished for each passenger at the airport. This leads usually to the build up of waiting queues. By using the mobile check-in system the passenger can avoid to be detained in this way.

After making the seat selection the user can, depending on the eligibility criteria of the specific airline, specify the number of bags to be checked-in at the airport if he has to check- in bags beside the hand baggage. In particular the user is prompted to answer security questions concerning the bags, especially whether the user has packed the bags himself and whether the bags have been under attendance all the time. In this case it is preferred that the mobile passenger service module 50 sends the necessary information and instructions to the DCS data hosts 62a₅ 62b of the respective airline that bag tags can be pre-printed at a respective baggage drop desk at the departure airport, where the passenger can drop the baggage. Preferably the user can use, as described below, the boarding pass data sent to the mobile device 84 after finishing the check-in procedure to print the bag tag on his own.

After finishing the check-in procedure as described below the mobile passenger service module 50 sends preferably additional information to the mobile device 84 especially concerning the time the user has to be at the airport in advance for boarding, connection times, the availability of baggage drops and their location information about the terminal configuration and so on. In the final step of the check-in procedure the mobile passenger service module 50 sends boarding pass data to the mobile device 84. As described later these data can be sent in encrypted form and can be used by the user at the airport to print out a boarding pass and/or at least one bag tag. In a preferred embodiment a plurality of boarding pass data is sent to the mobile device 84 if the user has booked additional connecting flights at an airport where a check-in via the mobile device 84 is possible. As a matter of cause before sending additional boarding pass data to the mobile device 84 the check-in procedure described before has to be accomplished by the user also for the connecting flights.

As mentioned before the communication between the mobile passenger service module 50, representing a first data communication module and the data hosts 60a, 60b, 62a, 62b, 72a, 72 and/or 86a, 86b is carried out via the inventive message sequence normalisation by a message sequence normalisation module 64 representing a second data communication module. Typical transaction commands (TA₁, TA₂, TA₃, TAN-I and TAN) for this check-in are "open flight", "check-in", "seat map", "change seat", "add bag", "receive boarding pass data" and/or "receive bag tag data". As described above the single messages that has to be sent to the respective data host and has to be received from this data host to accomplish this transaction is very different from airline to airline. For example one DCS system of a first airline only needs a flight number to open the flight. Thus, only one message comprising the flight number is sent to the DCS system and a verification is received from this data host. This flight number is comprised by the transaction command of the mobile passenger Service Module 50 sent to the message sequence normalisation module 64, and is further processed by the message sequence normalisation module 64 by introducing it in the respective message sent to the data host. It is possible that a for opening a flight it is necessary that a registration number, user name and a password is sent before a message for identifying the flight that has to be opened is sent to the data host. For this transaction preferably only one transaction command comprising as a parameter the flight number is sent from the mobile passenger Service module 50 to the message sequence normalisation module 64, and the further information are retrieved from the Interface definition table 70. With this data host a first message has to be sent comprising the registration number and a verification answer has to be awaited from this data host. After receiving this message another message is sent comprising the user name and the password after sending of which a verification response message has to be awaited. Not until receiving this response message a message is sent to this data host of this airline comprising the flight number. Thus, it can be seen that the communication with the different data hosts of the different airlines makes the use of different message sequences necessary. It has to be noted that the message sequence normalisation module 64 further processes the parameters received with the transaction command from the mobile passenger service module 50 as well as the parameters sent and received with the messages to and from the data hosts to provide the dynamic filter module 76 and/or the mobile passenger service module 50 with the requested data. As a result the accomplishing of a check-in procedure with data hosts of different airlines via the mobile passenger service module 50 is made possible especially by the invention by a message sequence normalisation module 64.

After finishing the check-in procedure via the mobile passengers service module 50 and the mobile device 84 the check-in data is stored in a boarding passenger list 88. Particularly also the boarding pass data sent to mobile device 84 are stored in the boarding passenger list 88 to give the opportunity to resend the boarding pass data in case of a failure of the mobile device 84.

As described above the user receives via his mobile device 84 in the step 11 or 35 the boarding pass data that allows him to accomplish the necessary security checks at the airport and to board the airplane. For these purposes appropriate devices that can communicate with the mobile device 84 are located at the respective locations at the airport, for example at the baggage drop counter, the security check location, where the ID of the passenger is compared with the boarding pass data, and/or at the boarding gate to allow the passenger to board the airplane. The data communication between the mobile device 84 and these devices is preferably accomplished via a wireless connection as blutooth or infrared or by displaying a two-dimensional barcode on the mobile device 84 that can be read by an appropriate reading device.

In a preferred embodiment the already available procedures for a security check and the boarding at a boarding gate are used. In this preferred embodiments the user prints out a boarding pass using the data stored on the mobile device 84. The further security check and the boarding is accomplished in the known way that the passenger shows an ID and his boarding pass to an agent for a security check before entering the departure gate and before boarding the airplane the passenger hands out the boarding pass to a agent who puts the boarding pass into an appropriate reading device to verify the boarding pass data with a central data base for listing the passenger on a passenger list of this flight and to verify the validity of the boarding pass.

In this preferred embodiment the user uses a boarding pass printer 90 as shown in Fig. 7 to generate a boarding pass. The boarding pass generator comprises a receiver device in form of a optical reader 92. The reader 92 receives the boarding pass data from the mobile device 84, preferably by scanning a two-dimensional barcode displayed on a display device of the mobile device 84, that is not shown in Fig. 7. Also a receiving of the data via a wireless connection like blutooth or infrared is possible. The received data are further processed by a controller 94 and sent to a printer 96 which prints out the boarding pass, preferably in a paper form on which the boarding pass data are printed as well as writing the boarding pass data on a magnetic strip of the boarding pass. In a preferred embodiment it is not necessary that the boarding pass generator 90 is connected to a data base for verification purposes of the boarding pass data. In this embodiment the data sent from the mobile device 84 to the reader 92 comprises a data record 98 as shown in Fig. 8. The data record 98 comprises at least two data sets 100, 102. In the first data set 100 the boarding pass data are stored in encrypted form. In the second data set 102 data information is stored that facilitates a decryption of the boarding pass data of the first data set 100. By encryption of the boarding pass data comprised in the first dataset 100 it is secured that these data cannot be changed by a person to generate a boarding pass with deferring information, for example a changed passenger name or deferring flight data. The encrypted data of the first data set 100 are decrypted by the boarding pass generator 90 as follows. After the decryption of the data the decrypted data are directly printed on a boarding pass via the printer 96.

It has to be noted that by using encrypted boarding pass data in the first data set 100 it is not necessary that the decrypted data has to be verified with an central database of the airport or airline. As it is secured by the encryption of the boarding pass data that these data cannot be changed by a third party it is secured that the data printed on the boarding pass generated by the boarding pass generating 90 are identical to the data stored in the DCS system of the airline. The verification of the boarding pass data with the identity of the user is made during the user security check and the verification of the boarding pass data with the DCS system of the airline is accomplished as usual at the boarding gate using the existing boarding pass reader. Thus, the costs for the boarding pass generator 90 are less compared to a device that needs a live connection to a central database of the respective airport or airline.

For the decryption of the data stored in the first data set 100 different procedures can be chosen. For example it is possible that in the boarding pass generator 90 a private decryption key is stored whereas the second data set 102 comprises a public key, which preferably comprises a time stamp information. In preferred embodiments the private decryption key is stored in a decryption key lock-up table in an internal storage device 104 of the boarding pass generator 90. It is preferred that this private decryption key is altered after a periodical or non- periodical period of time. For this purpose the boarding pass generator 90 comprises a reading device 106 for a mobile storage medium, e.g. a diskette, CD, DVD, data storage stick and/or data tape. It is also possible that in the decryption key lock-up table stored in storage device 104 a plurality of private decryption keys is stored wherein these decryption keys are distributed to the different boarding pass generators 90 by using a mobile storage medium that can be read by the reading device 106. In this case the second data set 102 comprises an identification number or decryption key index which represents a special decryption key and the controller 94 uses the second data set 102 to lock up the appropriate decryption key in the decryption lock-up table stored in the storage device 104. After the decryption of the encrypted data of the first data set 100 the boarding pass is printed via the printer 96. Thus a plurality of comparably cheap devices in form of the boarding pass generator 90 can be installed at the respective airport to implement the above described mobile check-in system in the known boarding procedures without leading to an insecurity because of a missing verification of the boarding pass data stored on the mobile device 84 with a central data base.

The features of the invention as disclosed in the above description, in the drawings and in the claims may be essential for the implementation of the various embodiments of the invention individually and in any desired combination.

Reference list

, 3, 5, 7, 9, 11 , 13, 15 step 1, 23, 25 , 27, 29, 31, 33, 35 step 0 mobile passenger service module 2 registration module 4 registered user list 6 relational database management system 8 flight list 0a, 60b, 62a, 62b data host 4 message sequence normalization module 6 data host 8a, 68b, 68c, 68d, 68e transaction 0 interface definition table 0a, 70b, 70c message sequence 1a, 71b message set element 2 data host 4 eligible passenger list 6 dynamic filter module 8 eligibility criteria list 0 data location table 2a, 82b data host 4 mobile device 6 data host 8 boarding passenger list 0 boarding pass generator 2 optical reader 4 controller 6 printer 8 data record 00 data set 02 data set 04 storage device

Claims

1. Method for accomplishing a data communication of a first data processing module with at least two data hosts, comprising the steps of

- identification of the received transaction command and identification of the data host with which the transaction has to be accomplished by the second data processing module, converting of the received transaction command into a message sequence comprising at least one message set by the second data processing module, wherein number of message sets comprised in the message sequence depends on the identified data host and the received transaction command, and communicating the message sets of the message sequence between the second data processing module and the identified data host.

2. Method according to claim 1, wherein the message sequence comprises at least two message sets which are communicated subsequently between the second data processing module and the identified data host.

3. Method according to claim 1 or 2, further comprising after the receiving of the transaction command the storing of the transaction command, preferably in the second data processing module.

4. Method according to one of the preceding claims, wherein the transaction command comprises at least one first parameter, particularly an identification information concerning the identified data host, a username, a password, a PNR identification, a flight number, a departure airport and/or departure city identifier, a destination airport and/or destination city identifier and/or a seat selection.

5. Method according to one of the preceding claims, wherein the message set comprises at least one first and at least one second message set element, wherein the first message set element comprises at least a first message that has to be sent to the identified data host by the second data processing module and the second message set element comprises at least one second message received as a response of the identified data host to the first message by the second data processing module.

6. Method according to claim 5, wherein the first message comprises at least one second parameter and the second message comprises at least one third parameter, wherein preferably the first, second and/or third parameter is or are stored at least temporarily preferably by the second data processing module.

7. Method according to claim 6, wherein the first or second parameter and/or the first, second and/or third parameter is or are further processed into at least one fourth parameter, preferably by the second data processing module, which especially is at least temporarily stored, preferably in the second data processing module.

8. Method according to claim 7, wherein the fourth parameter is further processed into at least one fifth parameter after the communication of a least one subsequent message set of the message sequence with the identified data host, preferably using the first parameter and/or the second and/or the third parameter of the subsequent message set.

9. Method according to claim 4 to 7, further comprising the step of exchanging of at least one transaction result, particularly the first, second, third, fourth and/or fifth parameter between the first and second data processing module after the communication of the complete message sequence with the identified data host.

10. Method according to one of the preceding claims, wherein the message sequence is retrieved from at least one interface definition table accessible by the second data processing module.

11. Method according to one of the preceding claims, wherein the transaction command, the transaction result, the at least one message set, the first message and/or the second message are sent, received and/or communicated on the same network layer.

12. Method for a check-in procedure of a passenger, preferably a flight passenger, using a mobile device, wherein the method according to one of the preceding claims is used during the procedure to allow a data communication with data hosts of a variety of different airlines.

13. System for accomplishing a data communication equipped to carry out a method according to one of the preceding claims, comprising at least one first data processing module (50, 76), at least one second data processing module (64) and at least two data hosts (60a, 60b, 62a, 62b, 66, 82a, 82b), wherein the data hosts (60a, 60b, 62a, 62b, 66, 82a, 82b) are preferably data hosts storing trip related, especially flight related, data of preferably different transportation companies, especially airlines.

14. System according to claim 13, wherein at least one Interface definition table (70) is realised in way of at least one plug-in dynamically loadable into the second data processing module (64) and/or dynamically unloadable out of the second data processing module (64), wherein the Interface definition table (70) can preferably be amended without the necessity to suspend the execution of the first (50, 76) and/or second data processing module (64).

15. System according to one of the claims 13 or 14, wherein the first data processing module (50, 76), the second data processing module (64) and the data hosts (60a, 60b, 62a, 62b, 66, 82a, 82b) are exchanging the transaction command, the transaction result, the at least one message set, the first message and/or the second message on the same network layer.

16. Software product comprising program code information to accomplish all steps according to one of the claims 1 to 12, in the case the software product is executed by a computer processor.

17. Software product comprising program code information according to claim 17, stored on a computer-readable storage medium.

18. Software product comprising program code information stored on a storage medium to accomplish all steps according to one of the claims 1 to 12, in the case the program is executed by a computer processor.