METHOD AND SYSTEM FOR TRANSFER OF BAGGAGE BETWEEN CONNECTING FLIGHTS

Abstract

The invention relates to a method and a system for transfer of baggage between connecting flights from airlines not having an arrangement for baggage check-through. The passenger books a journey and check-in at a departure airport, shifts to a connecting flight at a transit airport and completes the journey at a destination airport. The passenger check-in the baggage at the departure airport and collects the baggage at the destination airport. The journey comprises transfer of baggage at a transit airport between connecting flights from airlines, not having an arrangement for baggage check-through, by having no alliance, codeshare, or interline agreement between one another.

Claims

1. A method for transfer of baggage between connecting flights books a journey and check-in at a departure airport, shifts to a connecting flight at one or more transit airport(s) and completes the journey at a destination airport, and the passenger check-in the baggage before the journey at the departure airport or remotely and collects the baggage after the journey, wherein, the journey comprises transfer of baggage at the one or more transit airport(s) between connecting flights from at least two airlines not having an arrangement for baggage check-through, the method comprises: providing a computer-implemented travel control system, the travel control system receiving booking information of a journey from a booking portal, or any other source generating booking information, connected to the computer-implemented travel control system, the travel control system receiving, when the journey is booked, passenger data generated for each connecting flight by the respective airlines, storing the booking information and the passenger data in a database in the travel control system, and the travel control system updating one or more databases for a departure control system and/or airport control systems at the departure airport and/or the one or more transit airport(s) with booking data comprising the passenger data.

2. The method according to claim 1, wherein the booking data being updated in the databases is the data for each connecting flight needed for transfer of baggage from the incoming flight to the connecting flight.

3. The method according to claim 1, wherein the travel control system is updating the departure control system and/or the airport control systems to ensure the baggage is transported from the incoming flight to the connecting flight.

4. The method according to claim 1, wherein the method further comprises avoiding problems with transfer of baggage between the connecting flights at the transit airport.

5. The method according to claim 4, wherein the method further comprises avoiding that the passenger would have to, at the transit airport, to pick up the baggage at a arrival carousel and check-in the baggage again for the next connecting flight.

6. The method according to claim 1, wherein the method further comprises, that at check-in the baggage is tagged with a bag tag, and the bag tag comprises information indicating baggage transfer towards the destination airport.

7. The method according to claim 6, wherein the bag tag comprises information indicating baggage transfer through the one or more transit airport(s) to the destination airport.

8. The method according to claim 1, wherein the databases at the departure airport after the journey is booked is updated with the booking data from the travel control system, including check-through requirement for the one or more transit airport(s).

9. The method according to claim 6, wherein the bag tag comprises information for transfer of the baggage to the next airport of the one or more transit airport(s), and the baggage is labelled with a transfer bag label indicates that the baggage is a transfer bag, and at the one or more transit airport(s), the baggage labelled with the transfer bag label, is tagged with a bag tag for the next airport on the journey of the passenger.

10. The method according to claim 9, wherein at the one or more transit airport(s), if the baggage is labelled with a transfer bag label and the next airport is the destination airport, the transfer bag label is removed and the baggage is tagged by the bag tag as direct baggage.

11. The method according to claim 1, wherein the databases, comprising data for the airport control system of the baggage handling systems at the departure airport and/or the one or more transit airport(s), are updated with the booking data comprising the passenger data after the journey is booked.

12. The method according to claim 9, wherein at the one or more transit airport(s), if the baggage is labelled with a transfer bag label and the next airport is another of the one or more transit airport(s), the baggage remains labelled as transfer baggage with the transfer bag label or is relabelled with another transfer bag label.

13. The method according to claim 9, wherein at the departure airport, the airport control system identifies the baggage as transfer baggage needing a transfer bag label; the baggage is transferred to a relabelling station to be labelled with a transfer bag label.

14. The method according to claim 9, wherein at arrival at the one or more transit airport(s) the baggage labelled with the transport bag label is transported to the relabelling station, where the baggage is tagged with a bag tag for the next airport.

15. The method according to claim 9, wherein at the transfer baggage handling system, the airport control system identifies the baggage for relabelling and the baggage is transferred to the relabelling station.

16. The method according to claim 9, wherein at the relabelling station a bag tag for the next airport is written, based on information in the passenger data and tagged to the baggage.

17. A computer-implemented travel control system, wherein the travel control system is arranged to support the transfer of baggage between connecting flights, wherein a passenger books a journey and check-in at a departure airport, shifts to a connecting flight at one or more transit airport(s) and completes the journey at a destination airport, and the passenger check-in the baggage before the journey at the departure airport or remotely and collects the baggage after the journey, the journey comprises transfer of baggage at the one or more transit airport(s) between connecting flights from at least two airlines not having an arrangement for baggage check-through, wherein the travel control system is further arranged to support: the travel control system receiving booking information from a booking portal, or any other source generating booking information, connected to the travel control system, the travel control system receiving, when the journey is booked, passenger data generated for each connecting flight by the respective airlines, storing the booking information and the passenger data in a database in the travel control system, and the travel control system updating one or more databases for a departure control system and/or airport control systems at the departure airport and/or the one or more transit airport(s) with booking data comprising the passenger data.

18. The computer-implemented travel control system according to claim 17, wherein the databases for the departure control system and/or airport control systems at the departure airportafter the journey is bookedfrom the travel control system are updated with the booking data, comprising check-through requirement for the one or more transit airport(s).

19. The computer-implemented travel control system according, to claim 17, wherein the databases of the airport control systems of the baggage handling systems, at the departure airport and the one or more transit airport(s) are updatedafter the journey is bookedwith the booking data, comprising the passenger data, from the travel control system.

20. A computer program for a travel control system comprising instructions which, when the program is executed by a computer, cause the computer to carry out running a travel control system arranged to support the transfer of baggage between connecting flights, wherein a passenger books a journey and check-in at a departure airport, shifts to a connecting flight at one or more transit airport(s) and completes the journey at a destination airport, and the passenger check-in the baggage before the journey at the departure airport or remotely and collects the baggage after the journey, the journey comprises transfer of baggage at the one or more transit airport(s) between connecting flights from at least two airlines not having an arrangement for baggage check-through, wherein the travel control system is further arranged to support: the travel control system receiving booking information of a journey from a booking portal, or any other source generating booking information, connected to the travel control system, the travel control system receiving, when the journey is booked, passenger data generated for each connecting flight by the respective airlines, storing the booking information and the passenger data in a database in the travel control system, and the travel control system updating one or more databases for a departure control system and/or airport control systems at the departure airport and/or the one or more transit airport(s) with booking data comprising the passenger data.

21. A computer program for a booking portal comprising instructions which, when the program is executed by a computer, cause the computer to interacts with a computer-implemented travel control system arranged to support the transfer of baggage between connecting flights, wherein a passenger books a journey and check-in at a departure airport, shifts to a connecting flight at one or more transit airport(s) and completes the journey at a destination airport, and the passenger check-in the baggage before the journey at the departure airport or remotely and collects the baggage after the journey, the journey comprises transfer of baggage at the one or more transit airport(s) between connecting flights from at least two airlines not having an arrangement for baggage check-through, wherein the travel control system is further arranged to support: the travel control system receiving booking information of a journey from a booking portal, or any other source generating booking information, connected to the travel control system, the travel control system receiving, when the journey is booked, passenger data generated for each connecting flight by the respective airlines, storing the booking information and the passenger data in a database in the travel control system, and the travel control system updating one or more databases for a departure control system and/or airport control systems at the departure airport and/or the one or more transit airport(s) with booking data comprising the passenger data.

Description

BRIEF DESCRIPTION OF THE FIGURES

[0111] The method and system according to the invention will now be described in more detail with regard to the accompanying figures. The figures show one way of implementing the present invention and is not to be construed as being limiting to other possible embodiments falling within the scope of the attached claim set.

[0112] FIG. 1 illustrates a diagram for booking a journey and updating the travel control system and the systems at the departure airport and transit airports with booking data.

[0113] FIG. 2 illustrates the journey from departure airport to destination airport.

[0114] FIG. 3 illustrates the first scenario of transporting the baggage from departure airport to destination airport.

[0115] FIG. 4 illustrates the second scenario of transporting the baggage from departure airport to destination airport.

[0116] FIG. 5 illustrates the passenger name record transmitted from airline booking system to the travel control system.

[0117] FIG. 6 illustrates an embodiment of a possible implementation of the system in the transit airport.

[0118] FIG. 7 illustrates an embodiment of a possible implementation, where all bag tags are crated and printed at the first airport.

DETAILED DESCRIPTION OF AN EMBODIMENT

[0119] FIG. 1 illustrates that when a passenger 102 wants to go out on a journey the passenger 102 may book the journey using a booking portal 110. The journey may comprises one or more shift to connecting flights and the connecting flight may be from different airlines without an alliance, codeshare, or interline agreement between one another.

[0120] The booking portal 110 is connected to the travel control system 120 exchanging travel information 115. The travel control system 120 connects to the airlines booking systems 130 of different airlines. After booking, flights at an airline booking system 130 passenger data, usually in the form of passenger name records, are generated and the travel control system 120 receives data related to the booking from the airline booking system 130. The information received from the airlines are stored as part of the booking data 140 in the travel control system 130.

[0121] The airlines usually updates travel information and booking data in the departure control system and/or other airport control systems, but not having an agreement or even knowledge about connecting flights, the airlines do not update information for baggage check-through.

[0122] Data relating to transport of baggage and baggage check-through in the booking data 140 is by the travel control system 120 transmitted to, and updated directly in, the departure control system 150 or other airport control systems at the departure airport and/or in airport control systems 160 in transit airports.

[0123] At the departure airport, the booking data 140 for the passenger and the baggage check-through is stored in databases 155, 175 for the departure control system 150 and the airport control systems 170. At transit airports, the data is stored in databases 165 for the airport control systems 160. The airport control system can also include a departure control system at the transit airports even though this is not shown in FIG. 1.

[0124] The airports also have baggage handling systems 180, 190 using data from relevant databases 155, 165, 175. The baggage handling systems 180, 190 can be independent systems or they can be part of the airport control systems 160, 170 or the departure control systems 150.

[0125] FIG. 2 illustrates the journey 100. The passenger 102 check-in the baggage 200 at the departure airport 210. The baggage 200 and the passenger 102 goes with the flight 220 from the departure airport to a transit airport 230. The journey 100 may comprise several transit airports 230. At the transit airport 230 the passenger 102 goes to a connecting flight 240 and the baggage 200 is transported through the airport according to the method of the invention and goes on to the connecting flight 240. The connection flight 240 flies either to another transit airport 230 or to the destination airport 250. At the destination airport 250, the passenger 102 collects the baggage 200 and leaves the airport.

[0126] FIG. 3 illustrates the seven steps of scenario 1 for how the baggage is transported from the departure airport to the destination airport. The skilled person will understand that the steps may be combined or performed in a different order than described below. In scenario 1, the travel control system 120 is integrated with the departure control system 150 and other airport control systems 170 of the departure airport in agreement with partner airlines.

[0127] The process comprises the following steps. [0128] 1. The passenger 102 accesses an airline branded booking portal 110 hosted by the travel control system 120 but integrated on sales pages. [0129] 2. The passengers books virtual interline flight tickets 302 on one of the sales pages for flights that are normally not connected through interline/codeshare agreements. (APIs are delivered by two Airlines to the travel control system 120 in order to show this extra flight service to passenger in the booking portals web pages) [0130] 3. Passenger data 303 in the form of passenger name records (PNR) are generated for each flight after booking. Booking code and reference is generated for the PNRs by the two Airline booking systems 130 and transmitted to the travel control system 120. [0131] 4. The travel control system 120 updates the departure control system 150 and if needed, updates other airport control systems 170 at the departure airport 210 with the complete passenger booking data 140. This data comprises information about the check-through requirement in transit airports 230. [0132] 5. The passenger 102 check-in at the departure airport 210 and gets a bag tag 305 that covers the baggage transfer at the transit airports 230 as both Airlines 135, 136 for the connecting flights consent that data from the travel control system 120 can update the check-through labelling and code and status of the specific baggage for the transfer passenger 102 at the control systems in the departure airport and the transit airports. [0133] 6. The baggage 200 is immediately and automatically handled as a transfer bag by the baggage handling system (BHS) 180 at the departure airport 210 and the ground handlers at the departure airport 210. The baggage goes to the transfer storage in the airplane 220 as the bar codes on the bag tag 305 designate this position of the baggage 200. [0134] 7. When the baggage 200 arrives at the transit airport 230, the baggage 200 is taken from the transfer compartment in the airplane 220 and transferred to the final destination airplane 240 as normal check-through baggage 200 on the transfer belt in the transit airport 230.

[0135] FIG. 4 illustrates the 14 steps of scenario 2 for how the baggage is transported from the departure airport 210 to the destination airport 250 through a transit airport 230. The skilled person will understand that the steps may be combined or performed in a different order than described below. In scenario 2, there is not a complete integration between the travel control system and the destination airports departure control system and partner airlines, but there is airport system integration between the travel control system 120 and the airport control systems. That there is not complete integration with the departure control system means the departure control system from the departure airport is not able to update airport control system at transit airports with baggage check-through information.

[0136] The process of scenario 2 comprises the following steps: [0137] 1. The passenger 102 accesses an airline branded booking portal 110 hosted by the travel control system 120 but integrated on sales pages. [0138] 2. The passenger 102 books virtual interline flight tickets 302 on one of the sales webpages for flights that are normally not connected through interline/codeshare agreements. (APIs are delivered by two Airlines to the travel control system in order to show this extra flight service to passenger in the sales web pages) [0139] 3. Passenger data 303, in the form of two sets of passenger name records (PNR), are generated for each flight after booking. Booking code and reference is generated for the PNRs by the two airline booking systems 130 and transmitted to the travel control system 120. [0140] 4. The travel control system 120 stores the passenger data 303 in form of the passenger name records (PNR) and automatically transmits these two sets of PNR data to the airport control systems 160, usually known as high-level controls (HLC), integrated with the baggage handling systems of the departure airport and the transit airports. Here the two sets of PNR data are the basic info for the routing of the baggage on the carousels once the baggage 200 is registered in the airport control systems via a bag tag scan. [0141] 5. The passenger 102 check-in at the departure airport 210 and gets a bag tag 305 for the first flight. This normal bag tag 305 designates that the transit airport 230 is the arrival airport and NOT a transit airport. From here the process can be either scenario A or B below [0142] a. Scenario A handling methodmanual intervention at check-in. To avoid that the baggage goes to the arrival belt in the transit airport 230 the passenger's baggage is labeled with a separate visual transfer bag label 415 by check-in personnel 416 at the departure airport as transfer bag. [0143] i. The check-in personnel 416 attaches a special transfer bag label 415 that the ground handling crew recognizes as a transfer bag label 415 that requires manual handling. (GOTO section 6) [0144] b. Scenario B handling methodautomatic i.e. NO manual check-in handling. [0145] i. The check-in scanning of the baggage in the departure airport (based on airport control systems and baggage handling system tag scanning) when the baggage runs through the carousel, the data on the bag tag 305 cross references with the travel control system database. The travel control system database is integrated to the airport control systems 160, and identifies the baggage as a virtual interline bag that needs special side loading in the Airport baggage sorting system. [0146] ii. The airport control systems 160 of the departure airport 210 therefore automatically instructs the BHS of the departure airport 210 to sort the baggage to the re-labelling station 405, operated by the departure airport personnel where crew can manually address the airport control systems specific requirement of the handling of the baggage as a non-direct bag, but as a transfer bag. (check/control data is available through a travel control system app provided to the BHS staff if necessary) [0147] iii. The BHS staff at the departure airports relabeling station 405 attach a special transfer bag label 415 and thereby indicate that the baggage requires that the baggage is put into the transfer baggage compartment of the airplane 220 baggage space. [0148] 6. The baggage 200 is then put back on the belt 406 in departure airport 210 and sorted by the baggage handling system (BHS) to the correct pier/gate in the departure airport. [0149] 7. The baggage 200 is placed on the airplane 220 as a transfer bag and the airplane leaves for transit airport 230. [0150] 8. At the transit airport 230, a ground handler sees the transfer bag label 415 and takes the baggage 200 to the transfer BHS 408. At the BHS, the airport control systems 160 knows the status of the baggage 200 due to travel control system 120 integration with airport control system 160 at the transit airport 230. However, the airport control system 160 has been instructed by the travel control system 120 to sort the baggage to the relabelling station 409. [0151] 9. The baggage is sorted by the BHS 408 to the manual relabelling station 409, where the crew identifies the baggage as a transfer bag that needs manual handling by special procedure. [0152] 10. Staff at the relabeling station 409 rips up the existing tags, and places a direct-flight bag tag 305 for the connecting flight 240. The flight data is retrieved through the travel control system integration with the passenger data 303 from the passenger name record (i.e. the crew at the relabeling station essentially checks the passengers in again). [0153] 11. The travel control system 120 informs the passenger 102 of the new bag tag ID via an email or an SMS text message 411. [0154] 12. The baggage 200 is sorted and transported to a belt 412 to the correct pier/gate/as a direct flight baggage. [0155] 13. The baggage is loaded on to the airplane 240 as direct baggage. [0156] 14. The passenger 102 arrives in the destination airport 250, and the baggage 200 is sent to arrival where the passenger 102 picks up the baggage 200 at the arrival carousel 414.

[0157] FIG. 5 illustrates that when a journey has been ordered, the airline booking system 130 for each flight transmits the passenger data 303, usually in form of a passenger name record, from the airline booking system 130 to the travel control system 120, where the passenger data 303 from the passenger name record is stored in the booking data 140.

[0158] FIG. 6 illustrates an embodiment of a possible implementation of the system in the transit airport. When a passenger makes a booking 601, for two connecting flights, passenger name records (PNR) are generated 602 by the airlines. The PNRs and possible other booking information is sent to the travel control system. The travel control system creates baggage check through information for the transit airport 603.

[0159] The baggage check through information is transmitted to the airport control system of the transit airport. The airport control system checks 604 no later than when baggage from the first flight arrives at the airport, whether the license plate for the baggage is stored in the airport control system database. A license plate is a unique number applied to a piece of baggage to identify the baggage. If the license plate is not stored in the airport control system database, then the airport control system queries the DCS for the first flight for the license plate 605. The DCS returns the license plate information 606, which is received by the Airport Control System 607 and now the Travel Control System uses the license place to ask the baggage handling system (BHS) at the airport to identify the baggage with the license plate and transfer the baggage to the relabelling station. While the baggage is transferred to the relabelling station the travel control system, fetch onward flight information 609 and check in the luggage 610 in the airport control system, which updates the DCS for the second flight. The DCS for the second flight generate license plate and BMS for the second flight 611. The BSM information is sent to the Baggage Handling System 612, and a new bag tag is printed 613 by the Airport control System at a relabelling station and the Travel Control System has instructed the staff at the relabelling station to attach the bag tag to the baggage 614. The instruction may be done indirectly by the travel control system updating the system, possible the airport control system or the baggage handling system, used at the relabelling station. The baggage handling system is then taking the baggage to the departure flight 615.

[0160] In the embodiment illustrated in FIG. 6 the baggage is handled by the computer systems, the airport control system, in the airport, the airport control system communicates with the DCS for the two flights and possible the travel control system and the baggage handling system to get needed information and data for the baggage to be transported from the arriving flight to the departure flight. The only human intervention is that an operator need to attach the bag tag for the second flight to the baggage at the relabelling station. Otherwise, the computer systems handles the transport form the first flight to the second flight.

[0161] FIG. 7 illustrates an embodiment of a possible implementation, where all bag tags are crated and printed at the first airport so that no manual relabelling need in the second airport.

[0162] When a passenger makes a booking 701, for two connecting flights, passenger name records (PNR) are generated 702 by the airlines. The PNRs and possible other booking information is sent to the travel control system. The travel control system creates baggage check through information 703 and send it to the airport control system in the departure airport where the check through information is stored in the database for the airport control system. Now the airport control system can handle the baggage. The passenger check in at the departure airport 704, where a license plate and BSM is created 705 by the DCS for the first flight. At check-in, the airport control system uses the baggage check through information it has received from the travel control system and use it for each piece of baggage checked in by the passenger.

[0163] If the airport control system at the first airport has access to send information to the departure control system (DCS) for the second flight 706, then the license plate information is injected into the DCS for the second flight 707 and one bag tag is printed with information of both destinations 708. Then the baggage is processes normally in both departure and transit airport 712 without need for relabelling.

[0164] If the airport control system at the first airport do not have access the DCS for the second flight then the airport control system in the first airport check in the baggage for the second flight in the airport control system for the transit airport 709 and the airport control system in the second airport gets license plate information and BSM from the DCS 710 for the second flight and sends the information to the airport control system at the departure airport which then prints two bag tags which is both attached to the baggage 711. One bag tag for the first flight and one bag tag for the second flight. The baggage is now handle normally in both the departure airport and the transit airport and no manual relabelling will be required at the second airport 712.

[0165] The baggage check-thru invention reduces the minimum connection times (MCT) between transfer flights at airports. Today, passengers with two separate flight bookings are required to leave the airside at the transit airport to reclaim their luggage and check-in once again, hence limiting the number of total flight connections.

[0166] Instead, by enabling the luggage to be processed according to the invention, passengers can simply proceed to their next gate upon landing. This subsequently enables passengers to book a much wider range of flight connections over any given transit airport.

[0167] A further embodiment of the invention is that when the bag arrives in the transit airport, and it only has a one-way tag (hence transit airport appears as the destination), and it has no visual transfer bag label, the bag is scanned by a device that has the travel control system database integrated. The scanning can happen at a) unloading from the aircraft, b) at unloading at the arrivals belt, c) on the arrivals belt, d) on the reclaims belt. Scanning the bag tag notifies the ground handler and/or the baggage handling system that this was an bag for relabelling.

[0168] From this point on, the ground handler can interfere to remove the luggage from the system. They can either retag it by printing a new correct tag from our interface, and then put it back into the BHS, or, they can put it directly into the BHS, and our integration with the BHS will ensure that the bag is sorted to an encoding station and/or departure chute, where a skilled personnel will use the travel control system interface to print a new bag tag and retag it.

EXAMPLES

[0169] In order to quantify the problem, the applicant has used its proprietary self-transfer algorithm Compass to analyze the connection possibilities at two major airports with and without the processing of luggage according to the invention. Compass is a software that calculates the passenger walking & processing time between two flights at any airport by combining the physical map of the airport with flight and itinerary information.

[0170] Below are the results for two analyses for the applicant's partner airports for pilot projects:

Dsseldorf Airport

[0171] Average MCT without the product of the invention: 74 minutes [0172] Average MCT with the product of the invention: 25 minutes [0173] % decrease of MCT because of the invention: 66% [0174] Growth in the number of connection possibilities: 27%

Arlanda Airport

[0175] Average MCT without the product of the invention: 70 minutes [0176] Average MCT with the product of the invention: 20 minutes [0177] % decrease of MCT because of the invention: 71% [0178] Growth in the number of connection possibilities: 31%

[0179] As can be seen from the analysis, the technical effect of the invention is that it reduces the minimum connection times (MCT) considerable. Further, this also increases the number of possible connections, making it possible to reduce the duration of the journey. Thereby, the invention solves the problem of transfer of baggage between two airlines not having an interline agreement or other arrangement for baggage check-through.

Summarizing the Full Concept and Possibilities of the Invention

[0180] To summarize the full concept and possibilities of the invention:

[0181] A) The travel control system centralises and merges data about passengers, their different flights across non-allianze airlines, and the baggages which they have booked under their respective itineraries.

[0182] B) At the departure airport, the travel control system can be integrated in a number of ways. It can be integrated into the departure control systems directly, and/or into a common use platform where multiple departure control systems are integrated, and/or only into an airport control system. This integration allows the travel control system to exchange information between multiple departure control systems as well as airport control systems at the transit airport and/or at the departure airport. Therefore, either a bag tag can be printed with both destinations, or a visual transfer bag label can be printed and attached to the bag at check-in or at an encoding at the BHS in the departure airport, and/or enable the bag to be identified at the transit airport based on different characteristics.

[0183] C) At the transit airport, the travel control system integrates with airport control systems to inform the systems and skilled personnel about incoming flights, which have baggage registred in the travel control system, how many bags per flight, how the baggages are meant to be identified and processed, and which flights they are meant to be checked into next. This allows ground handlers and/or scanning systems to identify baggage registred in the travel control system based on their visual characteristics and/or bag tag information and/or visual transfer bag label. Then the travel control system instructs the personnel and/or the BHS to process the bag onwards by sorting it to a specific location and then having it retagged, or by having it retagged automatically.

[0184] The invention can be implemented by means of hardware, software, firmware or any combination of these. The invention or some of the features thereof can also be implemented as software running on one or more data processors and/or digital signal processors.

[0185] The individual elements of an embodiment of the invention may be physically, functionally and logically implemented in any suitable way such as in a single unit, in a plurality of units or as part of separate functional units. The invention may be implemented in a single unit, or be both physically and functionally distributed between different units and processors.

[0186] Although the present invention has been described in connection with the specified embodiments, it should not be construed as being in any way limited to the presented examples. The scope of the present invention is to be interpreted in the light of the accompanying claim set. In the context of the claims, the terms comprising or comprises do not exclude other possible elements or steps. Also, the mentioning of references such as a or an etc. should not be construed as excluding a plurality. The use of reference signs in the claims with respect to elements indicated in the figures shall also not be construed as limiting the scope of the invention. Furthermore, individual features mentioned in different claims, may possibly be advantageously combined, and the mentioning of these features in different claims does not exclude that a combination of features is not possible and advantageous.

ANNEX

[0187] In other embodiments, the present invention also relates to: [0188] 1. A method for transfer of baggage (200) between connecting flights (220, 240), wherein a passenger (102) books a journey (100) and check-in at a departure airport (210), shifts to a connecting flight (240) at one or more transit airport(s) (230) and completes the journey (100) at a destination airport (250), and [0189] the passenger (102) check-in the baggage (200) before the journey at the departure airport (210) or remotely and collects the baggage after the journey, [0190] wherein, [0191] the journey (100) comprises transfer of baggage (200) at the one or more transit airport(s) (230) between connecting flights (220, 240) from at least two airlines (135, 136) not having an arrangement for baggage check-through, [0192] the method comprises: [0193] providing a computer-implemented travel control system (120), [0194] receiving booking information (115) of a journey (100) from a booking portal (110), or any other source generating booking information (115), connected to the computer-implemented travel control system (120), [0195] receiving, when the journey (100) is booked, passenger data (303) generated for each connecting flight (220, 240) by the respective airlines (135, 136), [0196] storing the booking information (115) and the passenger data (303) in the travel control system (120), and [0197] updating one or more databases (155, 165, 175) for a departure control system (150) and/or airport control systems (160, 170) at the departure airport (210) and/or the one or more transit airport(s) (230) with booking data (140) comprising the passenger data (303). [0198] 2. The method according to embodiment 1, wherein the method further comprises, [0199] that at check-in the baggage (200) is tagged with a bag tag (305), and [0200] the bag tag (305) comprises information indicating baggage transfer towards the destination airport (250). [0201] 3. The method according to embodiment 2, wherein the bag tag (305) comprises information indicating baggage transfer through the one or more transit airport(s) (230) to the destination airport (250). [0202] 4. The method according to embodiment 1-3, wherein the databases (155, 165) at the departure airport (210) after the journey (100) is booked is updated with the booking data (140) from the travel control system (120), including check-through requirement for the one or more transit airport(s) (230). [0203] 5. The method according to embodiment 2, wherein the bag tag (305) comprises information for transfer of the baggage (200) to the next airport of the one or more transit airport(s) (230), and the baggage (200) is labelled with a transfer bag label (415), the transfer bag label (415) indicates that the baggage (200) is a transfer bag, and at the one or more transit airport(s), (230) the baggage (200) labelled with the transfer bag label (415), is tagged with a bag tag (305) for the next airport on the journey (100) of the passenger (102). [0204] 6. The method according to embodiment 5, wherein at the one or more transit airport(s) (230), if the baggage (200) is labelled with a transfer bag label (415) and the next airport is the destination airport (250), the transfer bag label (415) is removed and the baggage (200) is tagged by the bag tag (305) as direct baggage. [0205] 7. The method according to any of the embodiment 1-2, 5 or 6, wherein the databases (155, 165, 175), comprising data for the airport control system (160, 170) of the baggage handling systems (180, 190) at the departure airport (210) and/or the one or more transit airport(s) (230), are updated with the booking data (140) comprising the passenger data (303) from the travel control system (120) after the journey (100) is booked. [0206] 8. The method according to any of the embodiment 5-7, wherein at the one or more transit airport(s) (230), if the baggage (200) is labelled with a transfer bag label (415) and the next airport is another of the one or more transit airport(s) (230), the baggage (200) remains labelled as transfer baggage with the transfer bag label (415) or is relabelled with another transfer bag label (415). [0207] 9. The method according to any of the embodiment 5-8, wherein at the departure airport (210), the airport control system (170) identifies the baggage (200) as transfer baggage needing a transfer bag label (415); the baggage (200) is transferred to a relabelling station (405, 409) to be labelled with a transfer bag label (415). [0208] 10. The method according to any of the embodiment 5-9, wherein at arrival at the one or more transit airport(s) (230) the baggage (200) labelled with the transport bag label (415) is transported to the relabelling station (405, 409), where the baggage (200) is tagged with a bag tag (305) for the next airport. [0209] 11. The method according to any of the embodiment 5-10, wherein at the transfer baggage handling system (BHS, 190), the airport control system (160) identifies the baggage (200) for relabelling and the baggage (200) is transferred to the relabelling station (409). [0210] 12. The method according to any of the embodiment 9-11, wherein at the relabelling station (409) a bag tag (305) for the next airport is written, based on information in the passenger data (303), and tagged to the baggage (200). [0211] 13. A computer-implemented travel control system (120), wherein the travel control system (120) is arranged to support the transfer of baggage (200) between connecting flights (220, 240), wherein a passenger (102) books a journey (100) and check-in at a departure airport (210), shifts to a connecting flight (220, 240) at one or more transit airport(s) (230) and completes the journey (100) at a destination airport (250), and the passenger (102) check-in the baggage (200) before the journey at the departure airport (210) or remotely and collects the baggage after the journey, [0212] the journey (100) comprises transfer of baggage (200) at the one or more transit airport(s) (230) between connecting flights (220, 240) from at least two airlines not having an arrangement for baggage check-through, [0213] wherein the travel control system (120) is further arranged to support: [0214] receiving booking information (115) of a journey (100) from a booking portal (110), or any other source generating booking information (115), connected to the travel control system (120), [0215] receiving, when the journey (100) is booked, passenger data (303) generated for each connecting flight (220, 240) by the respective airlines (135, 136), [0216] storing the booking information (115) and the passenger data (303) in the travel control system (120), and [0217] updating one or more databases (155, 165, 175) for a departure control system (150) and/or airport control systems (160, 170) at the departure airport (210) and/or the one or more transit airport(s) (230) with booking data (140) comprising the passenger data (303). [0218] 14. The computer-implemented travel control system according to embodiment 13, wherein the databases (155, 175) for the departure control system (150) and/or airport control systems (160) at the departure airportafter the journey (100) is bookedfrom the travel control system (120) are updated with the booking data (140), comprising check-through requirement for the one or more transit airport(s) (230). [0219] 15. The computer-implemented travel control system according to embodiment 13, wherein the databases (165, 175) of the airport control systems (160, 170) of the baggage handling systems (180, 190) at the departure airport (210) and the one or more transit airport(s) (230) are updatedafter the journey (100) is bookedwith the booking data (140), comprising the passenger data (303), from the travel control system (120). [0220] 16. A computer program for a travel control system comprising instructions which, when the program is executed by a computer, cause the computer to carry out running a travel control system (120) arranged to support the transfer of baggage (200) between connecting flights (220, 240), wherein a passenger (102) books a journey (100) and check-in at a departure airport (210), shifts to a connecting flight (220, 240) at one or more transit airport(s) (230) and completes the journey (100) at a destination airport (250), and the passenger (102) check-in the baggage (200) before the journey at the departure airport (210) or remotely and collects the baggage after the journey, [0221] the journey (100) comprises transfer of baggage (200) at the one or more transit airport(s) (230) between connecting flights (220, 240) from at least two airlines (135, 136) not having an arrangement for baggage check-through, [0222] wherein the travel control system (120) is further arranged to support: [0223] receiving booking information (115) of a journey (100) from a booking portal (110), or any other source generating booking information (115), connected to the travel control system (120), [0224] receiving, when the journey (100) is booked, passenger data (303) generated for each connecting flight (220, 240) by the respective airlines (135, 136), [0225] storing the booking information (115) and the passenger data (303) in the travel control system (120), and [0226] updating one or more databases (155, 165, 175) for a departure control system (150) and/or airport control systems (160, 170) at the departure airport (210) and/or the one or more transit airport(s) (230) with booking data (140) comprising the passenger data (303). [0227] 17. A computer program for a booking portal comprising instructions which, when the program is executed by a computer, cause the computer to interacts with a computer-implemented travel control system (120) arranged to support the transfer of baggage (200) between connecting flights (220, 240), wherein a passenger (102) books a journey (100) and check-in at a departure airport (210), shifts to a connecting flight (220, 240) at one or more transit airport(s) (230) and completes the journey (100) at a destination airport (250), and [0228] the passenger (102) check-in the baggage (200) before the journey at the departure airport (210) or remotely and collects the baggage after the journey, [0229] the journey (100) comprises transfer of baggage (200) at the one or more transit airport(s) (230) between connecting flights (220, 240) from at least two airlines not having an arrangement for baggage check-through, [0230] wherein the travel control system (120) is further arranged to support: [0231] receiving booking information (115) of a journey (100) from a booking portal (110), or any other source generating booking information (115), connected to the travel control system (120), [0232] receiving, when the journey (100) is booked, passenger data (303) generated for each connecting flight (220, 240) by the respective airlines (135, 136), [0233] storing the booking information (115) and the passenger data (303) in the travel control system (120), and [0234] updating one or more databases (155, 165, 175) for a departure control system (150) and/or airport control systems (160, 170) at the departure airport (210) and/or the one or more transit airport(s) (230) with booking data (140) comprising the passenger data (303).