Automated Baggage Transportation and Check-in Using Simulated Baggage Source Messages

Abstract

The present disclosure relates to methods and systems for checking in passenger baggage items. The system may include various hardware necessary to implement the disclosed methods. At least one method may include receiving a passenger name record (PNR) number for a confirmed itinerary of an airline carrier flight. The passenger's baggage items may be picked up from the passenger's location and transported to another location, such as a baggage item handling or storage location. A simulated baggage source message (SBSM) compatible with an International Air Transport Association (IATA) B-type message can be generated using the passenger's itinerary information, allowing the passenger's baggage items to be checked in whether or not they are within or outside of the specified check-in window. The PNR number may be a temporary unique identifier for use within the SBSM.

Description

[Technical Field]

[0001] Priority claims

[0002] This application claims priority to U.S. Patent Application No. 18 / 421,595, entitled "Automated Baggage Transportation and Check-in Using Simulated Baggage Source Messages," filed January 24, 2024, which is a continuation of U.S. Patent Application No. 18 / 529,705, entitled "Baggage Check-in System," filed December 5, 2023, and U.S. Patent Application No. 18 / 421,601, entitled "Baggage Check-in System and Method," filed January 24, 2024. This application is a continuation of U.S. patent application Ser. No. 18 / 529,705, entitled "Baggage Check-in System," filed December 5, 2023, and a continuation of U.S. patent application Ser. No. 18 / 337,288, entitled "Baggage Check-in System," filed June 19, 2023, which is a continuation-in-part of U.S. patent application Ser. No. 18 / 332,377, entitled "Baggage Check-in Method and System," filed June 9, 2023. This application claims priority to U.S. patent application Ser. No. 18 / 201,908, entitled "Return Remote Passenger Check-in From Baggage Tag Identifier," filed May 25, 2023, which issued January 23, 2024 as U.S. Patent No. 11,881,057. This application claims priority to U.S. Patent Application No. 18 / 104,359 (filed February 1, 2023, entitled "Remote Passenger Check-In for Return Travel"), which claims priority to U.S. Patent Application No. 18 / 311,566, filed May 3, 2023, entitled "Multi-Leg Travel Baggage Tracking," the disclosures of which are incorporated herein by reference in their entirety.

[0003] Background of the Invention

[0004] 1. Field of the Invention

[0005] FIELD Embodiments of the present disclosure relate generally to baggage check-in, and more particularly to a system and method for extracting data that would otherwise be discarded and reusing the discarded data to trigger the printing of baggage tags for return flights. [Background technology]

[0006] 2. Overview of related technologies

[0007] Mobile carriers typically offer passengers the ability to check in baggage containing personal items, with or without a baggage fee. Baggage is often weighed to determine whether an additional fee applies. The baggage is then affixed with a baggage tag printed by the airline. Each mobile carrier may have its own unique baggage tag printing format at its counters. This process consumes resources, as behind-the-counter staff must complete passenger check-in, print boarding passes, check in baggage, and print and affix baggage tags. Airline mobile carriers also offer kiosks that allow passengers to print their own baggage tags, freeing up counter staff time. This allows passengers to affix printed tags without using counter staff resources.

[0008] According to the Federal Aviation Administration (FAA), the average daily passenger volume for fiscal year 2021 was approximately 1.6 million. In fiscal year 2019, the average daily passenger volume was approximately 2.9 million. Some of these passengers are returning from vacations. Additionally, the returning passengers include those returning from cruise ships and large resorts.

[0009] Many attempts have been made to reduce baggage handling costs, particularly those related to baggage handling from accommodation, passenger departure, and return flight check-in. To simplify baggage handling during transit, passengers are given the option to select services from third-party vendors to pick up passengers and / or baggage and transport them to the airport as needed. Baggage can be picked up from any location, such as a home, office, or hotel, and delivered to a designated location without the passenger being present.

[0010] Another method of handling baggage is to utilize dual-role hotel and other accommodation staff. The biggest drawback of dual-role staff is that they are unable to handle tasks generated by other passengers using the accommodation facilities. In recent years, the impact of COVID-19 has made it difficult to hire additional employees. Furthermore, labor costs have risen. For facilities such as cruise ships, adding additional staff to handle additional tasks is not only cost-unrealistic, but also reduces the profitability of the cruise, as it requires sacrificing paying passengers to cover the cost of employing employees. Printing baggage tags and boarding passes occupies space on cruise ships that could be used for passenger accommodation or as an additional revenue opportunity.

[0011] Some baggage handling services affix valet receipts or tags to baggage. This process also requires the acceptance of IATA-standard printed baggage tags (with baggage identification numbers) in place of valet receipts or tags. This process is cost-impractical in the highly competitive lodging business. Overall, baggage handling services require passengers to order services via a website or mobile app, enter various passenger information that may be incorrect, and pay a fee. Passengers can remotely check in for their flights by providing the necessary flight information for their travel itinerary in advance via a website or mobile app. While this process may seem straightforward, it is prone to data entry errors and can become prohibitively expensive when combined with baggage handling fees and the additional costs of temporary valet tickets.

[0012] In many cases, upon arrival, passengers remove and discard their baggage tags to make room for return baggage tags. Summary of the Invention [Problem to be solved by the invention]

[0013] The average large cruise ship can accommodate approximately 3,000 passengers. Larger ships can accommodate up to 5,400 passengers. While onboard staff can assist passengers with advance check-in for their return flight and baggage check-in, this task takes up valuable human resources that could otherwise be used for disembarkation. There is a need for systems and processes that address these challenges, are cost- and time-efficient, and are easy to use for all passengers. [Means for solving the problem]

[0014] Summary of the Invention

[0015] The present invention includes a method and system for checking in a passenger's return baggage using an outbound origin hardcopy baggage tag identifier (OP-BTI). The method includes electronically capturing, by at least one electronic capture device, an OP-BTI associated with or printed on an outbound airline mobile carrier's printed baggage tag affixed to the passenger's baggage, thereby generating a digital baggage tag identifier (BTI) data record linked to the airline mobile carrier. The method includes querying a database, by at least one processor, using the OP-BTI as a unique identifier to retrieve the passenger's return flight data. The method includes checking in, by the at least one processor, each of the passenger's baggage items for the return flight with the return mobile carrier identified in the retrieved return flight data.

[0016] An embodiment of the present invention includes an electronic method for streamlining return baggage check-in. The method begins by obtaining an OP-BTI associated with or printed on the outbound airline mobile carrier baggage tag attached to a passenger's baggage. This process generates a digital BTI data record linked to the airline mobile carrier. The OP-BTI is used as a unique identifier to query a database and obtain the passenger's return flight data. Once the return flight data is obtained, the passenger's baggage is checked into the return flight with the return mobile carrier.

[0017] Passengers typically depart from lodging facilities such as hotels, resorts, cruise ships, short-term and long-term rental homestays, homes, buildings, etc. The OP-BTI is acquired by one of several methods: capturing via radio frequency communication, scanning a tag with a barcode scanner, or receiving information via radio frequency identification (RFID) or near field communication (NFC).

[0018] The OP-BTI often includes the International Air Transport Association (IATA) license plate. The queried database may be part of the airline's travel information system. This system queries the database and uses the digital BTI data record to access B-type or universal B-type messages, which may include baggage forwarding and baggage origination messages.

[0019] In this process, the system may generate a record in a database containing a universal B-type message for multimodal travel indicating different modes of travel in the passenger's itinerary. The database is queriable by at least a substring of the integer characters that comprise the OP-BTI. Additionally, the method may involve printing a baggage tag for the return flight that conforms to International Air Transport Association (IATA) standards.

[0020] The database stores the manifest and, in response to obtaining the OP-BTI, triggers a baggage check-in process with the return carrier for the passenger's return flight. The system can simulate an airline B-type message containing return flight data, passenger name, and passenger name record. The system can also assign a new OP-BTI to the baggage item for the return flight and generate a new digital BTI data record representing the assigned OP-BTI in the simulated B-type message.

[0021] Additionally, the system can access passenger name records stored in the airline mobile carrier's information system using the digital BTI data record. Finally, the method can receive updated reservation information for the passenger and update the corresponding passenger itinerary linked to the passenger's enhanced B-type message in the database, which triggers a process to communicate the updated reservation information to the computing device in response to obtaining the OP-BTI.

[0022] BRIEF DESCRIPTION OF THE DRAWINGS

[0023] For a more complete understanding of the present invention, reference should be made to the following detailed description taken in conjunction with the accompanying drawings. [Brief explanation of the drawings]

[0024] [Figure 1A] FIG. 1A shows a block diagram illustrating a system for baggage check-in on a passenger's return leg, according to one embodiment.

[0025] [Figure 1B] FIG. 1B shows a block diagram illustrating a system for checking in passenger baggage on the return leg of a trip after disembarking from an accommodation, according to one embodiment.

[0026] [Figure 2A] FIG. 2A shows a partial view of a prior art airline baggage tag.

[0027] [Figure 2B] FIG. 2B shows a prior art airline baggage tag marker.

[0028] [Figure 2C] FIG. 2C shows an example of attaching a baggage tag marker to passenger baggage.

[0029] [Figure 3A] FIG. 3A illustrates a scanner according to one embodiment.

[0030] [Figure 3B] FIG. 3B illustrates a scanner with a display message according to one embodiment.

[0031] [Figure 4] FIG. 4 illustrates a block diagram of programming modules for passenger baggage check-in, manifest generation for travel segment departure, and enhanced B-type message generation, according to one embodiment.

[0032] [Figure 5] FIG. 5 illustrates a method for checking in passenger baggage according to one embodiment.

[0033] [Figure 6] FIG. 6 illustrates a block diagram of programming modules for generating a master manifest according to one embodiment.

[0034] [Figure 7] FIG. 7 illustrates a computing system according to one embodiment.

[0035] [Figure 8] FIG. 8 illustrates a flowchart of a method for checking in luggage for a passenger departing from a lodging facility according to one embodiment.

[0036] [Figure 9A] FIG. 9A illustrates a flowchart of a method for integrating a passenger manifest with accommodation information according to one embodiment.

[0037] [Figure 9B] FIG. 9B illustrates a flowchart of a method for initiating an extended B-type message according to one embodiment.

[0038] [Figure 10] FIG. 10 shows a flowchart of a method for checking in passenger baggage according to one embodiment.

[0039] [Figure 11] FIG. 11 illustrates a method for generating a universal B-type message for a passenger's return journey according to one embodiment.

[0040] [Figure 12A] FIG. 12A shows a conventional Baggage Source Message (BSM) for an airline.

[0041] [Figure 12B] FIG. 12B illustrates a simulated BSM according to one embodiment.

[0042] [Figure 13] FIG. 13 illustrates a smart baggage travel system for multi-modal travel and accommodation according to one embodiment.

[0043] [Figure 14A] FIG. 14A illustrates an extended (universal) B-type message for multi-modal travel, lodging, and origin baggage tag recycling according to one embodiment.

[0044] [Figure 14B] FIG. 14B illustrates an extended (universal) B-type message for a return flight according to one embodiment.

[0045] [Figure 15] FIG. 15 illustrates a block diagram of linking multi-modal travel and lodging data to augmented data according to one embodiment.

[0046] [Figure 16] FIG. 16 illustrates an extended (universal) B-type message for multi-modal travel, overnight stays, and departures according to one embodiment.

[0047] [Figure 17] FIG. 17 illustrates a block diagram of linking departing flight multi-modal travel and lodging data to enhanced data according to one embodiment.

[0048] [Figure 18] FIG. 18 illustrates a system for digitizing baggage drop and baggage check-in according to one embodiment.

[0049] [Figure 19] FIG. 19 illustrates a flowchart of a method for generating a simulated baggage origination message according to one embodiment.

[0050] [Figure 20] FIG. 20 illustrates a method for recording a passenger itinerary according to one embodiment.

[0051] [Figure 21] FIG. 21 illustrates an example of a confirmed airline itinerary according to one embodiment.

[0052] [Figure 22] FIG. 22 illustrates a graphical user interface on a mobile communication device for capturing passenger identification information according to one embodiment.

[0053] [Figure 23] FIG. 23 illustrates a flowchart of a process for tracking baggage before it is loaded onto an aircraft, according to one embodiment.

[0054] [Figure 24] FIG. 24 illustrates the FIND MY application displayed on a mobile communication device according to one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0055] Detailed Description of the Preferred Embodiments

[0056] Embodiments are described below with reference to the accompanying drawings. Like reference numerals are used in the drawings to designate similar or equivalent elements. The drawings are not to scale and are provided solely to illustrate aspects disclosed herein. The disclosed aspects are described below with reference to illustrative, non-limiting example applications. It should be understood that numerous specific details, relationships, and methods are described to fully understand the embodiments disclosed herein. However, one of ordinary skill in the relevant art will readily recognize that the disclosed embodiments can be practiced without one or more of the specific details or using other methods. In other instances, well-known structures or operations have not been shown in detail so as not to obscure aspects disclosed herein. The embodiments are not limited by the order of acts or events shown, as some acts may occur in different orders and / or in parallel with other acts or events. Furthermore, not all illustrated acts or events are required to implement a methodology in accordance with an example embodiment.

[0057] Notwithstanding that the numerical ranges and parameters setting forth broad ranges are approximations, the numerical values ​​set forth in the specific, non-limiting examples are reported as precisely as possible. However, any numerical value inherently contains certain errors necessarily resulting from the standard deviation in their respective testing measurements. Moreover, all ranges disclosed herein should be understood to include all subranges subsumed therein. For example, the range "less than 10" includes all subranges between a minimum of zero and a maximum of 10 (inclusive), i.e., all subranges with a minimum of zero or more and a maximum of 10 or less (e.g., 1 to 4).

[0058] The Departure Control System (DCS) manages various airline operations, such as airport check-in, baggage check-in (drop-off), passenger baggage tag identifier (BTID) generation, and baggage tag printing. Baggage tags are formatted according to rules published by the International Air Transport Association (IATA), and typically contain a 10-digit license plate number. One or more IATA Type B messages are generated, typically containing the 10-digit license plate number and flight information.

[0059] The inventors have discovered that what has traditionally been considered waste (i.e., discarded airline baggage tags) is in fact, by way of non-limiting example, a missing link in the cost-effective and time-efficient handling of baggage by accommodation facilities such as resorts and cruise lines.

[0060] Baggage tags on departing flights are typically linked to the passenger's identifying information. For example, passengers must be identified before they can check in for a flight. The Real ID Act of 2005, enacted by Congress, requires passengers to have a state-issued license that complies with the Act's requirements. For example, licenses and identification cards that comply with the 2005 Act may have a star in the upper right corner.

[0061] "Passenger Baggage Reconciliation" is an international regulation that determines whether a passenger has boarded a flight with checked baggage. If the passenger is not confirmed as boarding, the baggage is removed from the flight. In the United States, Title 49 of the United States Code (USC) § 44901 imposes similar requirements. Thus, when a passenger arrives at their destination, the "waste" left behind at the end of their journey holds valuable security information for lodging facilities such as resorts and cruise ships, as well as other modes of transportation following the flight.

[0062] Typically, passengers are prompted to remove their printed baggage tags after collecting their baggage from the baggage claim conveyor at their destination. However, the inventors have discovered that the origin printed baggage tags contain useful information and have concluded that, instead of discarding the origin printed baggage tags, they can be used: 1) as an alternative to printing and / or affixing temporary valet tags, and 2) to eliminate the need for passengers or other employees to retrieve the passenger's personal information and return flight information through autonomous data entry and retrieval.

[0063] Passenger baggage may be tagged with an adhesive marker by the airline carrier, which may include an IATA license plate barcode. This marker may be attached anywhere on the baggage and may be used to print and affix a temporary valet tag or to replace a lost IATA baggage tag. For example, an airline's IATA baggage tag may become damaged or removed during transit through an airline's baggage handling system. Thus, airline baggage markers may be used in the processes disclosed herein.

[0064] In some examples, airline IATA baggage tags and other special-purpose tags may include a printed IATA license plate and / or radio frequency identification (RFID) that can be read by an RFID reader. However, RFID technology is not yet widely adopted, with adoption rates at approximately 10%. The systems and methods disclosed herein can utilize RFID tags that are part of baggage tags, as a non-limiting example, when printed baggage tags, especially for departing flights, are damaged or unreadable by barcode scanners. As is known, RFID is used throughout airline baggage handling systems because scanning 10-digit license plates can be challenging for scanners. This is because the printed characters can be damaged or the attached baggage tag can be in a position that prevents barcode capture. In this system, an RFID reader can be used to capture 10-digit license plates in parallel with a barcode scanner or as needed.

[0065] The inventors have discovered that not only can non-discarded departing (original) IATA baggage tags be used as an alternative to valet tags, but that leveraging IATA baggage tags can automate the process, reduce the incidence of data entry errors, ease passenger friction, save time and increase cost efficiency.

[0066] The disclosed system employs a parallel approach to capturing passenger identification information to address damaged or lost IATA baggage tags, enabling retrieval of 10-digit license plates without input from the passenger or other personnel. For example, the process of scanning airline IATA baggage tags from undiscarded outbound flights can capture passenger information (particularly return flight information) and autonomously retrieve passenger records and return flight information for remote check-in of the passenger's baggage (baggage items) upon return travel. Printed IATA baggage tags from undiscarded outbound flights can be used as a machine-readable medium by a smart baggage travel system independent of the airline environment to locate and track baggage items for a portion of a multi-modal return journey prior to the return flight.

[0067] Scanning of all non-discarded baggage tags may include scanning at the dockside of the accommodation facility such as a cruise line, scanning at the destination airport or intermediate mobile carrier upon arrival, scanning at the accommodation facility such as a hotel resort, and / or scanning anywhere between the destination airport or intermediate mobile carrier and the accommodation facility.

[0068] Scanning of all non-discarded baggage tags may include scanning of non-discarded baggage tags at any transportation station prior to loading of baggage items onto a transportation vehicle (e.g., van, train, bus, ferry).

[0069] The inventors have determined that an airline mobile carrier's original printed / paper baggage tag contains valuable information that can be used to automate the check-in process for a return passenger and / or baggage for the mobile carrier's flight and / or to create a passenger record for a manifest used by a lodging facility. Instead of removing the original printed baggage tag after arrival at a destination associated with a lodging facility, the code embedded in the license plate on the original printed baggage tag can be electronically captured, digitized, and used to retrieve personal or personally identifiable information (PII) associated with the passenger from the mobile carrier's flight, which is then made available to the lodging facility or other vendors.

[0070] Furthermore, the inventors have determined that the license plate on the origin printed baggage tag can be used to autonomously obtain a passenger's return flight information without the need for the passenger or hotel employee to manually enter the return flight itinerary information. For example, the inventors have determined that this can be achieved using the origin printed baggage tag from the airline carrier, even if the passenger is not present.

[0071] Type B messages are customized by airline carriers based on their requirements, provided that they are compatible with IATA regulations, SITA procedures, or other Type B message communication equipment.

[0072] The inventors have determined that an extended Type B message can be generated with return flight information and accommodation information, as well as other transportation options. Accommodation information may include building name or number, address, and cabin number. In some embodiments, accommodation information may include, for example, cabin, cabin number, and floor.

[0073] Airline B-type messages are used by airport baggage handling systems to track baggage as it travels through and is screened at multiple airports. The baggage handling systems include mechanical readers that read the printed contents of the baggage tags as it travels between airports, essentially tracking and locating the bag while it is in the airport's custody.

[0074] However, for travelers using multiple modes of transportation, there is no universal Type B message that tracks and locates baggage along its travel path. The inventors have determined that other modes of transportation do not have the same ability to track and locate a passenger's baggage as it moves through their itinerary using a secure device that links the baggage to the passenger.

[0075] Without wishing to be bound by theory, machine-readable OP-BTI developed for air travel and facial recognition performed at rail or bus stations may be used to verify that a passenger has boarded a train or bus with their baggage. However, there are also cases where passengers and baggage travel on different trains or in different transport vehicles, for example, when passengers travel by rail while their baggage is transported in a truck or van.

[0076] The inventors have determined that airline Type B messages can be extended and updated in near real time outside the airline and airport facilities, and that the extended Type B messages can be converted into universal Type B messages for use. The extended Type B messages can be extended to include at least one transportation and accommodation reservation linked by a machine-readable OP-BTI. In some embodiments, the extended Type B messages can be extended to include and link multi-modal transportation and / or accommodation reservations for a passenger on a journey.

[0077] In some embodiments, the universal B-type messages are stored in a database and act as a near real-time digital reservation and baggage tracking and handling coordinator for multi-modal travel and lodging. At any time during travel outside of the airport, a printed baggage tag at the point of origin can be scanned to obtain up-to-date travel and lodging information and display it on, for example, a computing device, scanning device, or display device associated with the mobile computing device.

[0078] In some embodiments, the inventors have determined that printed baggage tags bearing the OP-BTI, which are discarded at the end of a flight, can be used as a machine-readable primary key or unique identifier to access near real-time reservation information for multiple modes of transportation and / or accommodation reservations, thereby reducing environmental impact, reducing manpower requirements, and enhancing security and logistics planning.

[0079] Return segment baggage tag information

[0080] Checking in using airline baggage tags at origin (departure) addresses a key deficiency in the current remote check-in process. Cruise ship check-in has traditionally revolved around valet tags, allowing cruise ships to check passengers in for their flights and collect their boarding passes and valet tags while at sea. However, the entire check-in process relies on overworked, time-constrained onboard staff. Implementing this process onboard requires building a hybrid airline check-in function, making check-in difficult and unreliable. Another challenge is that, despite extending the airline check-in window to 48 hours to ease the burden on cruise ships, processing time remains challenging. Efforts to reduce onboard workloads include patenting a single-page document to expedite document printing for all passengers checking in onboard and delivering valet tags and boarding documents to each stateroom of every passenger using the service. All of these barriers limit the product's throughput and economic success. This invention eliminates the need for onboard staff and the delivery of cabin documents to each passenger. A lightweight, simplified technology using baggage tags (traditionally discarded items) at the point of origin or a Type B message check-in process allows for seamless check-in off-board, with key searchable data already attached to the bag, allowing passengers to access the airline's check-in process. This seamless baggage handling allows already tagged baggage to flow through the process with its identifier, enabling information flow for airline check-in. IATA baggage tag scanning at the point of origin can also be applied to other remote operations, such as at hotels and resorts, requiring limited technology, workstations, printers, and space. This enables a seamless, cost-effective system across the remote check-in network, enabling an economically sustainable process.

[0081] 1A shows a block diagram of a system 100 for checking in passenger baggage items on a return leg, according to one embodiment. In some embodiments, the system 100 can also be used to check in passengers on a return leg.

[0082] System 100 is shown between lines A-A and B-B. System 100 can communicate with travel information system 108 of first mode mobile carrier 104, travel information system 110 of any intermediate mobile carrier 106, and / or travel information system 128 of accommodation 126. In embodiments disclosed herein, accommodation 126 is a cruise ship. Travel information systems 108, 110, 128 may include, for example, web-based servers connected to the Internet. One or more components of system 100 are located proximate destination point DP 107, which is also proximate the accommodation. In some embodiments, accommodation 126 may be a resort or hotel.

[0083] The first mode mobile carrier 104 may be an airline, bus company, or railroad company, although for ease of explanation, the first mode mobile carrier will be described as an airline carrier in the illustrative example. The optional intermediate mobile carrier 106 may be an airline, bus company, or railroad company.

[0084] Travel path 140 (shown by a dashed line) depicts the route of travel legs L1, L2, and L3 taken by a passenger and passenger baggage 138 from an origin (i.e., home 102) to an overnight stay at accommodation 126 or embarkation point via path L4. Leg L1 is the travel path from home 102 to a first-mode mobile carrier 104. Leg L2 is the route traveled using a first-mode mobile carrier 104 to a destination point DP107 or an optional leg L3 associated with an intermediate mobile carrier 106. Optional leg L3 is the route traveled to destination point DP107 using an intermediate mobile carrier 106. For example, a passenger may end their travel path at the end of leg L2, board a different mobile carrier or flight, and begin traveling to destination point DP107 along leg L3. It should be further noted that the travel path of leg L3 may include one or more intermediate mobile carriers. In some cases, a passenger's itinerary may include zero (0) intermediate mobile carriers. For example, this may be the case for a direct or nonstop journey along a travel route 140 to a destination DP.

[0085] Figure 1B illustrates a block diagram of a system 100 for passenger baggage check-in for return travel after disembarking from a lodging facility, according to one embodiment. The system of Figure 1B is identical to the system 100 of Figure 1A, except that the components of system 100 may be distributed to different locations outside the airport to obtain the OP-BTI.

[0086] According to some embodiments, the return route may include travel segments L2' and L1' after leaving the accommodation on travel segment L4'. The return route may include, for example, L3', L2', and L1'. In some embodiments, the passenger itinerary may include an overnight stay reservation after L2' and before the start of itinerary L1'. Thus, there may be multiple travel modes and overnight stays in the passenger travel experience.

[0087] On the return journey, the origin (outbound) printed baggage tag 142' may be used for tracking, locating, and / or collecting information on other modes of transportation before baggage check-in for the return flight. In some embodiments, baggage items may be separated from the passenger on certain modes of transportation. The passenger may be able to travel without baggage on other modes of transportation, if desired.

[0088] According to some embodiments, system 100 may be integrated or connected with systems 1300 (FIG. 13) and / or 1800 (FIG. 18) to separate baggage from the passenger in other transportation for check-in to a return flight within a restricted check-in window, print and affix a baggage tag for the return flight to the baggage, and release the baggage to the custody of the airline carrier.

[0089] According to some embodiments, the system 100, 1300, and / or 1800 can cause a printer associated with the airline carrier or a kiosk at the airline carrier to print a return IATA-compatible baggage tag for the return flight by the airline mobile carrier. In some embodiments, the system 100, 1300, and / or 1800 can include a printing device to print the return IATA baggage tag and replace the recycled universal printed baggage tag with the return IATA baggage tag.

[0090] In some embodiments, the printed IATA baggage tag number on the return IATA baggage tag is recycled as a recycled unique identifier for use in off-airport facilities and temporary accommodations on the return leg after the baggage has been unloaded from the airline carrier and picked up from the airline's infrastructure. The return IATA baggage tag on the return leg serves as a non-discarded machine-readable baggage tag for other transportation and accommodations (including temporary accommodations) after completing the return leg with the airline carrier.

[0091] The destination point DP 107 is within the region of the embarkation port of accommodation 126. The system 100 or one or more components of the system may be managed and operated by a third-party service provider independent of any mobile carrier. The system 100 may be managed and operated by a mobile carrier within the region of the destination point DP 107. The mobile carrier within the region of the destination DP 107 may be an air carrier, a rail carrier, a bus carrier, a cruise ship carrier, or a combination thereof. The acquisition devices disclosed herein may be distributed to off-airport facilities to locate and track baggage items, such as during alternative modes of transportation.

[0092] In some cases, the route taken by the first mode mobile carrier and the route taken by any intermediate mobile carrier 106 may be reversed, in which case the route taken by the passenger in section L2 will be taken by the intermediate mobile carrier 106, and the route taken by the passenger in section L3 to destination DP107 will be taken by the first mode mobile carrier.

[0093] Components of the system 100 may include a scanner 116 that scans a baggage tag (BT) 142. An example of an airline BT 142 is described in more detail in connection with FIG. 2A. The BT 142 is an origin paper baggage tag (OP-BT) issued by, for example, a first mode mobile carrier 104 for the first leg of travel, and that has an origin baggage tag identifier (O-BTI) 114. The O-BTI 114 may be stored in a database by the first mode mobile carrier 104.

[0094] In some embodiments, components of the system 100 may also include a radio frequency (RF) communication device 150 (also referred to as an RFID-R 150). The RF communication device 150 may be an RFID reader or a near field communication (NFC) identification reader. An RFID reader receives an electromagnetic field to automatically identify and track tags. In some cases, passenger baggage 138 may use RFID or NFC-compatible tags that generate a 10-digit license plate or equivalent identifier. However, most baggage still uses printed or paper tags as the primary means of identifying passenger baggage 138.

[0095] The baggage item may include an RF communication device (not shown), which is defined herein as any of a Global Positioning System (GPS) tracker, a Global System for Mobile Communications (GSM) tracker, a GSM-5G tracker, a Wi-Fi enabled communication device, a Bluetooth® Low Energy (BLE) device, a Bluetooth enabled communication device, a short-range RF communication device, and a long-range communication device using a compatible wireless communication protocol.

[0096] The term passenger baggage 138 may include one or more baggage items. The one or more baggage items may include a first baggage item. In some cases, only the BT 142 of the first baggage item may need to be scanned to digitally recreate the passenger's baggage number.

[0097] The stored digital O-BTI 114 may be converted into a format compatible with IATA baggage tag codes and other carrier standardized formats. For example, airline baggage tags may include an IATA code, which includes a three-character alphanumeric geographic code designating an airport and metropolitan area. The IATA code is also known as an IATA location identifier. IATA also publishes industry-standard rules for creating baggage tags for the airline industry. The printed BT 142 may include a 10-digit license plate and corresponding barcode, as shown in FIG. 2A. The O-BTI 114 may include IATA geographic code generation information, original flight information, the 10-digit license plate, and other BT information printed on the BT 142, as described below with reference to FIG. 2A. The BT 142 may utilize license plates used by other mobile carriers.

[0098] Components of the system 100 may include an imaging device 118 for capturing images of passenger baggage 138. Components of the system 100 may include an optional printing device 120 configured to print markers (MK) 136 on a substrate. Components of the system 100 may include a computing device 122, which is described in more detail in connection with FIG. 7 . The computing device 122 can communicate with the scanner 116, the imaging device 118, and the printing device 120 via wireless communications, indicated by reference numeral 130. In some embodiments, the computing device 122 can communicate with the scanner 116, the imaging device 118, and / or the printing device 120 using a wired communications protocol. The printing device 120 may be a laser printer, an inkjet printer, or other printer device.

[0099] It should be understood from this disclosure that the system accommodates many possible outcomes that various passengers may experience. MK136 is required because some baggage may arrive at its destination without the originally printed baggage tag or airline marker (both of which may include an IATA barcode). In these situations, the system must prepare a marker to temporarily tag the baggage.

[0100] The system can obtain passenger information by scanning a barcode or QR code associated with a departing flight's boarding pass. In some cases, a passenger's ticket may include information related to a 10-digit license plate number, which can be retrieved from the passenger and affixed to their baggage without the need to print the MK136. For example, a passenger may receive an adhesive-backed marker from an airline agent when checking in their baggage at the airport.

[0101] The marker may include a 10-digit license plate number or other information that can be used by passengers to identify their baggage, for example, in the event of loss.

[0102] The system, by a printing device in communication with the at least one processor, creates an MK136 having a marker identifier for linking the passenger manifest record to the first baggage item if an Origin Paper Baggage Tag Identifier (OP-BTI) associated with or on the printed baggage tag of the first baggage item is damaged or missing, and enters the marker identifier into the passenger manifest record, the marker identifier being a barcode readable by a barcode scanner device, and the marker identifier including either the OP-BTI or a new passenger tracking identifier.

[0103] The computing device 122 can communicate with the scanner 116, the imaging device 118, and / or the printing device 120 using the NFC protocol and the BLUETOOTH protocol. The computing device 122 can communicate with the scanner 116, the imaging device 118, and / or the printing device 120 using wireless LAN (WI-FI) communication based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. The computing device 122 can communicate with the scanner 116, the imaging device 118, and / or the printing device 120 using, for example, ZIGBEE® wireless technology that is compatible with IEEE 802.15. The computing device 122 can communicate with the scanner 116, the imaging device 118, and / or the printing device 120 using long-range communication protocols, short-range communication protocols, cellular radio frequency protocols, or other mobile radio frequency protocols.

[0104] In other embodiments, the scanner 116 may be a software application stored on the computing device 122 that is programmed to interact with a video or camera device built into or integrated with the computing device 122 or connected via a cable. In one embodiment, the computing device 122, the imaging device 118, and the scanner 116 are a single device, such as a smartphone, tablet, or other portable computing device with video capabilities, hereinafter referred to as a "smart communication device." In some embodiments, the system 100 may include a local computing device or server 148 for communicating with the smart communication devices and the travel information systems 108, 110, and / or 128. The local computing device (i.e., the server 148) communicates with at least one smart communication device and / or travel information system 108, 110, 128 using wired or wireless communications.

[0105] In one embodiment, the computing device 122, the imaging device 118, the scanner 116, and the RFID-R 150 are a single device, such as a smartphone, tablet, or other portable computing device with video capabilities, also referred to hereinafter as a "smart communication device."

[0106] The imaging device 118, scanner 116, and RFID-R 150 may be electronic devices that capture barcodes and other information associated with IATA license plates, such as 10-digit license plates. As should be understood from this disclosure, although the IATA standard uses 10-digit license plates, other license plate formats with different numbers of digits may also be used.

[0107] Components of the system 100 may include any baggage claim device 124 for transporting received baggage, such as on a conveyor belt. As passenger baggage 138 moves along the conveyor belt, at least one scanner 116 and at least one imaging device 118 may scan or capture information representative of the O-BTI 114. In some embodiments, the imaging device 118 captures images of one or more passenger baggage pieces 138. Additionally, the RFID-R 150 may read RFID or NFC tags attached to the baggage claim device 124. In some embodiments, the scanner 116 may scan QR code-enabled baggage tags. RFID, NFC, and QR code-enabled baggage tags may include specific personal information or PU. This passenger's personal information and PNR 112 information are used to verify the personal information. The RFID or NFC tag should be compatible with, for example, IATA RP1740c.

[0108] In other embodiments, the baggage claim device 124 includes a designated pad or surface for placement of a single piece of passenger baggage 138, with a scanner, imaging device 118, and / or RFD-R 1503 located adjacent the pad to scan the O-BTI 114 and / or capture an image of the passenger baggage 138. The scanner 116 and imaging device 118 may be the same device, operable in one process to locate and scan a barcode bearing the O-BTI 114, and in a second, optional process to locate a portion or side of the body of the passenger baggage 138 and capture an identifiable baggage feature. In some embodiments, if the printed BT 142 is unreadable, the scanned O-BTI data receiver 402 may be bypassed. In this case, the user may directly input the 10-digit license plate 210 and enter it into the license plate analyzer 404 to determine the mobile carrier identification and the passenger baggage number. The scanner 116, imaging device 118, and RFID-R 150 can be integrated into the same device, and if a printed baggage tag is not present, the RFID-R 150 reads the RFID or NFC tag and generates personal information for the manifest.

[0109] In the process of capturing the baggage's identifying features using techniques such as computer vision, it may be determined that the passenger baggage 138 does not have an original paper baggage tag. In this case, information received from the RFID-R 150 is used. In some cases, the passenger baggage 138 may have both an RFID or NFC tag and an original paper baggage tag, because the original paper baggage tag may contain information related to the travel carrier for the return leg to home 102.

[0110] The computing device 122 and / or server 148 of the system 100 establishes a communication session with the travel information system 108 or 110 to access the PNR 112 based on the scanned BT 142 and obtain information representing the original O-BTI 114, including the passenger's baggage number embedded code, as described below. The travel information system 108 or 110 then establishes communication with passenger file data 132, including the passenger's return travel information and personally identifiable information (PII). The received passenger file data 132 is assembled into a manifest file 134 or transmitted to the travel information system 128, where the manifest file 134 is created. In some cases, the server 148 creates the manifest file. Either the computing device 122 and / or the server 148 communicates the manifest file to the travel information system 128 of the accommodation 126.

[0111] The computing device 122 and / or the server 148 may consolidate all passenger file data 132 into a single manifest file 134 of checked-in passenger baggage. The computing device 122 and / or the server 148 then communicates the manifest file 134 to the travel information system 128 of the accommodation facility 126.

[0112] The DCS may control the management of the check-in process for the airline mobile carrier. The travel information system 108 or 110 may include a check-in indicator 144 that indicates that those baggage items have been checked in for travel within a specific time window. In some embodiments, the mobile carrier may include a baggage check-in database 146 for baggage that has been checked in for travel. In some embodiments, the check-in database 146 may also include data regarding checked-in passengers.

[0113] An exemplary scenario will now be described in detail. A passenger, ready to travel, begins at, for example, home 102, where passenger baggage 138 departs, and travels leg L1 of a travel itinerary 140. Passenger baggage 138 travels with the passenger or via a baggage transport service to an airline mobile carrier 104, where leg L2 of the journey begins. At the airline mobile carrier 104, passenger baggage 138 receives a BT 142, as shown in FIG. 2A. BT 142 contains printed information representing the O-BTI 114 in accordance with the IATA baggage tag format. BT 142 is printed on paper or a paper composite at an airline counter by airline personnel, a baggage transport service, or a kiosk operated by the passenger. When used as described below, BT 142 remains attached to passenger baggage 138 and travels leg L3.

[0114] The passenger's itinerary includes accommodation 126. In this example, assume accommodation 126 is a cruise ship. In some embodiments, before the passenger boards the cruise (i.e., accommodation 126), scanner 116 scans BT 142 with O-BTI 114 and digitizes a printed representation of O-BTI 114.

[0115] In various scenarios, the passenger's travel itinerary may include travel segment L2 and travel segment L3. For example, if the airline is the only mobile carrier, travel segment L3 is omitted. In this case, the airline mobile carrier may offer direct flights to a city or destination near or local to the accommodation 126. In other examples, the passenger's travel route includes an intermediate mobile carrier 106, providing travel segment L3. For example, the passenger's travel route may include at least one connecting flight or segment to a city or destination proximate to the accommodation 126. This connecting segment is denoted as segment L3, which begins at the end of segment L2 and ends at destination DP 107.

[0116] FIG. 2A shows a partial view of a prior art printed airline baggage tag 200 (i.e., BT142). The baggage tag 200 is one half of a baggage tag. The baggage tag 200 includes two sides that are mirror images of each other, allowing the two ends of the baggage tag 200 to be attached to each other. In the illustrated example, the baggage tag 200 includes a three-digit origin airport flight identifier 202 and a three-digit destination airport flight identifier 204. The baggage tag 200 also includes at least one barcode flight identifier 206. In this illustrated example, the baggage tag 200 includes a first barcode flight identifier 206 with the bars of the barcode arranged in a first orientation and a second barcode flight identifier 208 with the bars of the barcode arranged in a second orientation different from the first orientation. The format of baggage tags may vary slightly depending on the country and airline.

[0117] In some embodiments, the passenger's name may appear on the baggage tag 200 .

[0118] The baggage tag 200 includes a 10-digit license plate number 210 that complies with IATA regulations. The 10-digit license plate number consists of an initial integer ranging from 0 to 9, followed by a three-digit airline code, and then a six-digit license plate number. The last six digits of the license plate number correspond to the passenger baggage number. The numeric font can be difficult to read. The 10-digit license plate 210 is positioned adjacent to the first barcode flight identifier 206 and / or the second barcode flight identifier 208.

[0119] Human-readable license plates include a two-letter or three-digit IATA airline code, for example "AA509795" or "001509795", where "AA" is the two-letter IATA code for American Airlines and "001" is the three-digit IATA airline code, but the barcode is always in the full 10-digit format.

[0120] The first barcode flight identifier 206 is a label that can conceal personal information and flight information. For example, the first barcode flight identifier 206 is coded to include the passenger's name, information about the baggage's destination (i.e., destination), and other information, such as the arrival airport name, departure time, the IATA airport code of the arrival airport, the airline code, the flight number, and the passenger name (first name, last name) associated with the baggage. The first barcode flight identifier 206 is a modified version of the license plate 210.

[0121] The baggage tag number consists of a two-character airline code and six digits. The six digits represent the passenger's baggage number. The passenger's baggage number can be used to search for the PNR 112. In some embodiments, the passenger's baggage number can also mask the passenger's identity.

[0122] The airline generates and stores one or more B-type messages 152. The B-type messages 152 may include one or more of a baggage transfer message (BTM), a baggage source message (BSM), a baggage processed message (BPM), a baggage unloaded message (BUM), a baggage not confirmed message (BNS), a baggage control message (BCM), a baggage manifest message (BMM), and a baggage request (BRQ). The baggage tag number may be part of the baggage message. Additionally, the B-type message may include the passenger name and PNR, which allows access to other information based on the baggage tag number.

[0123] The license plate 210 embedded in either the first barcode flight identifier 206 or the second barcode flight identifier 208 is known as the index number (IN), which links the baggage source message (BSM) sent from the airline's DCS to the airport's baggage handling system. Each digit of the license plate 210 has a specific meaning. For example, the BSM contains flight details and passenger information for the second leg L2.

[0124] The inventor has determined that an index number (IN) embedded in the license plate 210, the first barcode flight identifier 206, or the second barcode flight identifier 208 can be used to access the passenger's PNR 112.

[0125] The example in Figure 2A is a self-tag airline baggage tag printed by a passenger via an airport kiosk. Airline baggage tags may include a similar license plate format.

[0126] 2B shows a prior art airline baggage tag marker 212. The airline baggage tag marker 212 may include a passenger name 214, an origin airport flight identifier 215, a destination airport flight identifier 216, a 10-digit license plate 218, and an adjacent barcode flight identifier 220.

[0127] In some embodiments, the airline baggage tag marker 212 is affixed to one end of the conventional airline baggage tag 200 and is removable for passenger storage. The airline baggage tag marker 212 is printed on paper or a paper composite.

[0128] The MK 136 printed by the printing device 120 may include personal information for the PNR 112 to enter the passenger's name. In some cases, the MK 136 may include a temporary baggage tag with an embedded code for accommodation 126 or a return trip.

[0129] 3A illustrates a scanner 116 according to one embodiment. The scanner 116 includes a software application (i.e., scanner application 310) that is loaded onto a computing device 302, such as computing device 122. A user of the scanner 116 points a camera lens 308 toward the printed baggage tag 200. The camera lens 308 is located on the back side of the device, opposite the side on which the display screen 304 is located. A processor of the computing device causes an image (input) representing the printed baggage tag 200 captured by the camera lens 308 to be displayed on the display screen 304.

[0130] The scanner application 310 may provide a barcode window 306 (shown in dashed lines) positioned to capture all the bars of, for example, the second barcode flight identifier 208, to highlight and identify the printed barcode in the image, or to guide the user toward the barcode. Alternatively or additionally, the scanner application 310 may scan the first barcode flight identifier 206. The barcode window 306 may be automatically displayed upon launch of the scanner application 310. The scanner application 310 may, for example, search for a linear or 1D barcode and convert the barcode of the first barcode flight identifier 206 or the second barcode flight identifier 208 to generate a series of numbers representing, for example, a license plate 210. A human can visually recognize a license plate 210; however, entering each number is time-consuming and prone to human error.

[0131] The first barcode flight identifier 206 or the second barcode flight identifier 208 associated with the license plate 210 is used, for example, as an index number (IN) to link to a baggage source message (BSM) containing passenger information, enabling retrieval and access of the PNR 112 corresponding to the passenger and their return flight information.

[0132] In some embodiments, the scanner application is also used to capture the QR code baggage tag identifier on the QR code baggage tag affixed to the passenger baggage 138. This information is used to verify the PNR 112 and access personal information.

[0133] 3B illustrates a scanner (computing device 302) with a display message 360 ​​according to one embodiment. Message 360 ​​may include text indicating the cabin number to which the baggage item whose printed baggage tag was scanned in FIG. 3A will be delivered. The display message also includes message 355 indicating that the cabin is ready. In some embodiments, the display message may include message 350 indicating the name of the accommodation. Additionally, the display message may include the scanned baggage number.

[0134] For other lodging facilities, such as hotel resorts, the cabin number may be replaced with a room number, or a building number, floor number, and room number. In some embodiments, messages 350, 355, and / or 360 are generated and communicated by messaging system 1390 via server 1310 of FIG. 13, as described below.

[0135] 4 shows a block diagram of programming modules 400 for passenger baggage check-in, manifest generation for travel leg boarding (embarkation), and enhanced B-type message generation according to one embodiment. Programming modules 400 may be located on computing device 122, server 148, or a combination thereof.

[0136] One or more of the programming modules 400 may include software, hardware, firmware, or a combination of software, hardware, and firmware. The computing device 122 and / or the server 148 may include at least one processor and / or hardware for executing instructions of the programming modules 400.

[0137] Programming module 400 may include a scanned O-BTI data receiver 402 and a license plate analyzer 404. Scanned O-BTI data receiver 402 receives the 10-digit number embedded in the captured barcode of first barcode flight identifier 206 or second barcode flight identifier 208, and license plate analyzer 404 parses the string of numbers received from scanner application 310. License plate analyzer 404 may track the number with a mobile carrier ID locator 420 to identify a mobile carrier identifier (ID). License plate analyzer 404 may track the number (e.g., the last six digits) with a baggage number locator 422 to identify a baggage number.

[0138] License plate analyzer 404 extracts the first digit of the converted barcode, which in this example is the number 7. This digit may be discarded. License plate analyzer 404 then extracts the next three digits using mobile carrier ID locator 420. In this case, the next three digits include "001," which corresponds to the mobile carrier ID. In this case, the travel agency ID corresponds to American Airlines®. License plate analyzer 404 then extracts the next six digits ("509795") using baggage number locator 422. These six digits correspond to the passenger's baggage number.

[0139] In some embodiments, the scanned O-BTI data receiver 402 can be bypassed in the event that the printed BT 142 cannot be read. In this case, the user may directly enter the 10-digit license plate 210, which is received by the license analyzer 404 to identify the mobile carrier identifier and the passenger baggage number.

[0140] The programming module 400 may include a communication session generator 406 for communicating with at least one of the first mode mobile carrier 104 and / or the intermediate mobile carrier 106. The communication session generator 406 may include a mobile carrier Internet Protocol (IP) address lookup database 424 and PNR access instructions 426. The mobile carrier ID of the license plate 210 is used to retrieve predefined instructions for generating electronic communication packets to a server of the first mode mobile carrier 104 and / or the intermediate mobile carrier 106 associated with the mobile carrier ID. The communication session generator 406 also retrieves stored instructions for accessing return leg information from the stored PNR access instructions 426 using a digitally generated passenger baggage number extracted from the first barcode flight identifier 206 or the second barcode flight identifier 208 associated with the license plate 210. The communication instructions may identify information related to tools (i.e., programming instructions) compatible with Transmission Control Protocol / Internet Protocol (TCP / IP), File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), Secure Hypertext Transfer Protocol (HTTPS), Secure Sockets Layer (SSL), Secure File Transfer Protocol (SFTP), and User Datagram Protocol (UDP).

[0141] In some embodiments, the instructions may identify a link in the scanned license plate 210 to a Baggage Source Message (BSM) containing passenger information to retrieve and access the passenger's PNR 112 and their return flight information. The link, in some embodiments, may include, but is not limited to, an HTTP-compatible link. Each airline may format the BSM or other B-type message with additional data fields, however, the B-type message is compatible with IATA B-type codes.

[0142] During the communication session, the computing device 122 executes programming instructions of the passenger travel return leg obtainment unit 408. Here, the return leg refers to the route or portion of the travel route traveled to return to home 102. For example, if the passenger is returning home on the same travel carrier as the original printed baggage tag, the PNR 112 will include the return flight information. Otherwise, the return flight information may be marked as null by the system 100.

[0143] The programming module 400 may include a passenger baggage identification module 410. Image data from the imaging device 118 may be processed by machine learning software to generate an image of the passenger baggage 138. This image is stored in a database for the passenger baggage identification process. In some cases, it may be necessary to search for or identify the passenger's baggage. The computing device 122 or the server 148 may store the image of the passenger baggage 138 for later retrieval. Machine learning algorithms are then used to recognize the baggage and match passengers to their baggage.

[0144] The computing device 122 or the server 148 may use machine learning algorithms to identify whether a particular baggage item has been processed by one or more components of the system 100.

[0145] The programming module 400 may include a marker generator 412 that generates a barcode for use in the MK136 format that can be printed by the printing device 120 and affixed to passenger baggage 138. As mentioned above, the MK136 is used when the original baggage tag or airline marker is unavailable or unscannable, for example due to damage.

[0146] Programming module 400 may include a passenger manifest record generator 414, a return leg manifest generator 416, and a manifest communicator 418. A passenger manifest created from non-discarded origin printed baggage tags may be used to match passengers arriving at lodging facilities and determine cabin or guest room numbers. Non-discarded printed baggage tags registered in the manifest may be used to deliver the passenger's baggage to the guest room and / or lodging facility, for example, without the need to generate a temporary valet tag. Non-discarded printed baggage tags may also be used upon departure of the passenger, for example, returning home from the lodging facility, without the need to print another temporary valet tag.

[0147] The passenger manifest record generator 414 may store passenger information 428 and associated PNRs 112 in one or more files for passengers whose passenger baggage 138 was scanned by the system 100. The passenger information may include the passenger's first name, middle name or initial, last name, and contact information. For example, the contact information may also include the passenger's address. The passenger information may include personally identifiable information (PII).

[0148] Components of the system 100 store a passenger list for one or more accommodations 126 within the region of the destination DP 107, thereby ensuring that baggage 138 of passengers not traveling through the accommodation 126 is not commingled with baggage 138 destined for the accommodation 126. In some embodiments, the file of passenger information 428 may include passenger information associated with prepaid services with a third-party service provider, a first mode mobile carrier 104, or an accommodation 126. In some embodiments, the file of passenger information 428 may include cabin numbers assigned to passengers. Accordingly, the marker generator 412 may communicate with the passenger manifest record generator 414 to obtain information such as cabin numbers and passenger names, and format and populate fields in the markers printed by the marker generator 412.

[0149] The return leg manifest generator 416 may extract information from the PNR 112, including return leg travel information, including, but not limited to, the travel carrier for the return transport, the departure time of the return transport, the flight number, and / or the estimated number of baggage items that need to be checked in for the return leg of the return journey. The return leg manifest generator 416 may register the return leg travel information in corresponding data fields in the manifest file.

[0150] The manifest file includes a conduit for baggage check-in for multiple passengers with a designated return travel carrier. The conduit may include a graphical user interface for remotely checking in each baggage item for passengers departing the accommodation within a designated (time) window prior to the return flight departure. In some embodiments, the passenger manifest record includes digital BTI data, PNR, and data identifying check-in for the passenger's return travel leg with a designated return travel carrier.

[0151] In some embodiments, server 148 and server 1310 may include a conduit for passenger baggage check-in for at least one airline carrier for the return leg.

[0152] The manifest communication unit 418 is configured to establish a communication session with a travel information system 128 associated with the accommodation 126. The manifest communication unit 418 may have different instructions for each travel information system 128 of multiple cruise ship carriers. The communication instructions identify information related to tools (i.e., programming instructions) compatible with Transmission Control Protocol / Internet Protocol (TCP / IP), File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), Secure Hypertext Transfer Protocol (HTTPS), Secure Sockets Layer (SSL), Secure File Transfer Protocol (SFTP), and User Datagram Protocol (UDP).

[0153] The programming module 400 may include an expanded type B message generator 430. An example of an expanded type B message is shown in FIG. 14A, as described below. The programming module 400 may include an origin IATA baggage tag recycler 409A and a return origin IATA baggage tag recycler 409B. The return origin IATA baggage tag recycler 409B initiates the expansion of type B messages created for the return flight. The origin IATA baggage tag recycler 409A initiates the expansion of type B messages for the departing flight. For example, when the baggage check-in process for the return flight begins, the recycling process by the origin IATA baggage tag recycler 409A must be completed.

[0154] The programming module 400 may include a simulated type B message generator 431 that generates a simulated type B message for a return or departure flight, as shown and described in connection with FIG. 12B . According to some embodiments, the extended type B message may include at least three data fields from the airline type B message. The first field includes a field with the IATA baggage tag number. The second field may include the passenger name. The third field may include the PNR. These fields allow for retrieval of return flight information at any time using the origin IATA baggage tag number (including update information). In some embodiments, if the IATA baggage tag number is not available at the time of generating the simulated type B message, a temporary unique identifier is used in a field or row with the “.N / ” prefix used for the numeric string representing the baggage tag number. In the departure flight example, the field or row beginning with the “.N / ” prefix contains the temporary unique identifier until the IATA baggage tag number can be obtained from the airline's DCS or a simulated DCS that generates IATA baggage tag numbers remotely from the airline's infrastructure. In some embodiments, the simulated DCS may have a unique IATA two-letter or two-digit code.

[0155] Programming module 400 may include a multi-mode reservation synchronizer 432. Each passenger's itinerary to an accommodation, such as a resort or cruise ship, may include air travel and other modes of transportation, such as bus, rail, or ferry. The ferry may include accommodation for travel from one port to another, which may be in different countries. This type of travel differs from a cruise, in which passengers depart and return to the same port.

[0156] A passenger's itinerary may include multi-modal reservations with multiple accommodation stays across multiple states or countries. The origin baggage tag number from the printed airline license plate and / or the associated RF unique identification code representing the origin baggage tag number linked to the baggage item may be used as a primary key for logging and tracking all travel reservations and updates accessible via recycled, non-discarded machine-readable tags.

[0157] The passenger itinerary 1314 (FIG. 13) may change before departure for the first leg of the trip, after boarding the first leg and arriving at the destination, or before boarding any leg of the return journey. The systems 100, 1300, and / or 1800 may synchronize the modes of transportation (travel modes) by updating the reservation information data and communicating the updates to the passenger.

[0158] In some embodiments, before the start of a travel leg, the server 148 or 1310 may contact any of the reservation systems associated with the passenger itinerary 1314 to obtain any changes to flight, bus, train, or accommodation information. An extended B-type message may be updated.

[0159] The programming module 400 may include a baggage tracker 434. The origin (original) IATA baggage tag is used as a recycled machine-readable tag and remains attached to the baggage item until, for example, the passenger disembarks from their accommodation and begins their return journey, without the need for another tag, unless the original IATA baggage tag is damaged or lost. If the recycled unique identifier of a non-discarded machine-readable baggage tag is acquired, such as by scanning or an RF communication device, a location code or geotag can be added to the resulting image data communication stream and logged with the data. This allows the acquisition device to track the location of the baggage item as it moves.

[0160] While airlines allow baggage items to be checked in via remote check-in at off-airport facilities (e.g., cruise ships or train stations), the inventors have determined that the outbound (origin) pre-printed baggage tag can be utilized as a marker and conduit to check in baggage for a return flight, such as after a flight. The remote check-in process at off-airport facilities requires robust workstations and printers. These printers capable of printing IATA baggage tags at off-airport facilities are very expensive and can occasionally become overloaded. The inventors have determined that recycling the outbound (origin) pre-printed IATA baggage tag and associated unique identifier, accessing return flight information, such as within a regulated check-in window, and printing return flight baggage tags at a designated printing location remote from the cruise ship can expedite the baggage check-in process and eliminate the need for valet tags.

[0161] As a non-limiting example, passenger baggage disembarking from a cruise ship must be processed within 24 or 48 hours. This may require printing boarding passes, valet tags, baggage tags, or a combination thereof. However, cruise ships carry thousands of passengers, each of whom may carry multiple pieces of baggage. One attempt to address this logistical challenge is the "Separable Single-Page Printable Boarding Pass and Tag Identification Document" disclosed in U.S. Design Patent No. D862590, issued October 8, 2019. This document allows boarding passes and baggage tags to be printed on a single document. The document includes perforations for separating baggage tags and adhesive for attaching them to baggage items. However, these advances, which conserve manpower, paper resources, and other processing infrastructure, remain insufficient to process thousands of passengers disembarking from cruise ships and other high-volume resorts, much less address delays caused by radio communication outages, equipment failures due to inclement weather, or other computer technology glitches. Additionally, printing baggage tags on cruise ships, for example, requires space on board, space that could be used for other revenue streams.

[0162] In some embodiments, passengers may travel a different route than their baggage items during portions of their itinerary. Current processes do not provide seamless baggage identification throughout the entire travel experience. This can result in a complicated and costly travel experience for all parties involved in the travel and destination network. For example, itinerary changes can result in lost baggage, late arrivals, or a less seamless baggage movement experience. A late arrival on a cruise ship or lost baggage during a trip can have devastating effects on a passenger.

[0163] The inventors have determined that the origin printed baggage tag attached to a baggage item should remain with the baggage item and be recycled until the baggage item is checked into a return flight, thereby preserving the origin IATA baggage tag number already recorded on the printed machine-readable medium and keeping it linked to the verified passenger identity.

[0164] Before the passenger lands from the departing flight, system 100 or 1300 may initiate a recycling process to recycle the origin (departure flight) IATA baggage tag number into a universal baggage tag unique identifier for use outside the airport infrastructure. The transition to the universal baggage tag unique identifier is seamless and becomes available at off-airport facilities from the moment the passenger's baggage is unloaded from the first mode or intermediate transfer carrier aircraft and leaves the control of the airport infrastructure, without the need for the passenger to be present.

[0165] The (recycled) origin IATA baggage tag number is captured by a capture device at an off-airport facility to create a digital data record used as a primary key or unique identifier to log the baggage's mode of transportation and itinerary location and timestamp, which may trigger updates to the baggage item's location information without the passenger's presence. The capture device (e.g., scanning device, mobile communication device, video-enabled computing device, RF communication device) may provide a location code via communication with image data captured by the capture device or via RF communication from the RF communication device.

[0166] The programming module 400 may include an accommodation coordinator 436 programmed to determine if any changes have occurred to the accommodation reservation (e.g., room number or cabin number) and notify the passenger or baggage handler of any reservation changes before checking in the baggage. In some embodiments, the cabin number or cabin number may not be in a cleaned / ready state. Once the cabin number or cabin number is in a ready state, the enhanced type B message is updated with the current status. The accommodation coordinator 436 may communicate with or receive communications from the smart baggage travel system 1300 of FIG. 13 , described below. As a non-limiting example, the enhanced type B message may be enhanced with a link to the reservation data for the passenger's itinerary.

[0167] The programming module 400 may include a smart baggage movement communicator 438. If information associated with the extended type B message changes, the smart baggage movement communicator 438 is configured to communicate the updated information to either a baggage handler's or passenger's computing device. The computing device may be a mobile communication device or an acquisition device. Communication details will become more apparent in the following description. The communication instructions identify information associated with tools (i.e., programming instructions) compatible with Transmission Control Protocol / Internet Protocol (TCP / IP), File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), Secure Hypertext Transfer Protocol (HTTPS), Secure Sockets Layer (SSL), Secure File Transfer Protocol (SFTP), and User Datagram Protocol (UDP). The smart baggage travel communicator 438 may communicate with the smart baggage movement system 1300 of FIG. 13, described below.

[0168] 5 illustrates a passenger baggage check-in method 500 according to one embodiment. While the exemplary method 500 illustrates a particular order of operations, the order may be changed without departing from the scope of the present disclosure. For example, some of the illustrated operations may be performed in parallel or in a different order without substantially affecting the functionality of the method 500. In other examples, different components of an exemplary device or system implementing the method 500 may perform functions substantially simultaneously or in a particular order. In some embodiments, one or more blocks disclosed herein may be omitted or blocks may be added.

[0169] The method 500 creates a digital license plate number from the printed BT, which is used, for example, to obtain return flight information. At block 502, the method 500 begins after the passenger completes a travel leg upon arrival at a destination. At block 504, the method 500 includes obtaining an origin baggage tag identifier (O-BTI), such as a 10-digit license plate. The origin baggage tag identifier obtaining process includes scanning the origin baggage tag identifier (O-BTI) on the printed baggage tag of the first baggage item with a scanner to create scanned or digital BTI data. The printed O-BTI is linked to a first mode travel carrier. As a non-limiting example, the scanner may be a barcode scanner.

[0170] In some cases, acquiring the origin baggage tag identifier may include receiving an RFID signal containing information representative of the origin baggage tag identifier. In other embodiments, acquiring the 10-digit license plate may include scanning an adhesive-backed airline marker affixed to the baggage.

[0171] In summary, assume the first mode mobile carrier is an airline, in which case electronic capture by the at least one electronic capture device includes at least one of the following: i) scanning, with a barcode scanner, the OP-BTI on an airline carrier-issued printed paper baggage tag affixed to the passenger's first baggage; ii) scanning, with a barcode scanner, the OP-BTI on an airline-issued printed marker affixed to the first baggage; iii) reading or capturing, with an RFID reader, RFID information associated with the OP-BTI; and iv) receiving, with radio frequency communications, a wireless communication including the OP-BTI.

[0172] At block 506, method 500 may include extracting, by at least one processor, a passenger baggage number from the scanned O-BTI data. Block 506 may include extracting a mobile carrier code from the scanned or digital BTI data.

[0173] At block 508, the method 500 may include, by at least one processor, accessing a passenger name record (PNR) from a second processor associated with the first mode mobile carrier based on the digitally generated passenger baggage number or the digitally generated 10-digit license plate number. At block 510, the method 500 may include, by at least one processor, autonomously creating a passenger manifest record for the passenger's return travel leg with the designated return mobile carrier from the accessed PNR 112. The passenger manifest record includes the digital BTI data and the PNR, and includes data identifying check-in of the passenger's baggage for the return travel leg with the designated return mobile carrier. The passenger manifest record may be populated with the scanned O-BTI or a mobile carrier code embedded in the accessed PNR 112. The passenger manifest record is associated with the passenger's digital BTI data for tracking and handling of the passenger's baggage items before and after their stay at the accommodation. For example, the lodging may be located within a Disney® property or other resort with lodging facilities.

[0174] At block 512, method 500 includes repeating blocks 504 through 510 for multiple passengers boarding (embarking) a travel segment involving an accommodation. At block 514, method 500 may include performing a baggage check-in process for each passenger for the return segment to the designated return travel carrier. The repetition of blocks 504 through 510 may autonomously generate a manifest file for multiple passengers beginning a stay associated with an accommodation, which may have a conduit for baggage check-in to the designated outbound travel carrier. In some embodiments, baggage checked in on the outbound journey to the accommodation may be stored in a separate manifest so that baggage check-in and baggage tag printing for the return flight can be performed by any operator.

[0175] In some embodiments, the method 500 may include populating, by at least one processor, at least one manifest file with each generated passenger manifest record for an accommodation facility.

[0176] Block 508 of method 500 may include identifying a mobile carrier from the scanned O-BTI data and identifying a stored communication session procedure for communicating with the mobile carrier based on the scanned or digital O-BTI data, the stored communication session procedure specifying a communication protocol for at least one processor to access passenger name records (PNRs) from a remote second processor (i.e., travel information system 108 or 110) associated with the mobile carrier via a communication network.

[0177] Communication formats may include tools compatible with Transmission Control Protocol / Internet Protocol (TCP / IP), File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), Secure Hypertext Transfer Protocol (HTTPS), Secure Sockets Layer (SSL), Secure File Transfer Protocol (SFTP), and User Datagram Protocol (UDP).

[0178] The process of performing the baggage check-in process of block 514 for the return leg with the designated return mobile carrier may also use stored communications instructions to control a remote second processor to check in baggage for the return leg to the passenger's home, for example, within a predetermined check-in window. In some embodiments, the passenger may check in themselves with the airline carrier or other entity for their return flight using a computing device or mobile communications device, such as a smartphone, tablet, notebook, or laptop. Passenger check-in may be entirely separate from the baggage check-in process. In some embodiments, the passenger may be checked in by, for example, a computing system at an accommodation facility that communicates with the return airline carrier.

[0179] 6 shows a block diagram of a programming module 600 for generating a master manifest according to one embodiment. The programming module 600 is capable of communicating with multiple computing devices on which the programming module 400 is executing. The programming module 600 may be stored on a computing device associated with the travel information system 128 or other travel management system. In some embodiments, one or more programming modules 600 may be stored on computing devices associated with the server 148 and the travel information system 128.

[0180] In some embodiments, server 148 and travel information system 128 may be integrated into the same computing system. In other embodiments, server 148 may be integrated into travel information system 108 or 110.

[0181] The programming modules 600 may include a manifest aggregator 602, a master manifest generator 604, and a return leg sorter 606. One or more of the programming modules 600 may include software, hardware, firmware, or a combination of software, hardware, and firmware. A computing device associated with the travel information system 128 may include at least one processor and / or hardware for executing instructions of the one or more programming modules 600.

[0182] The programming module 600 includes a manifest graphical user interface (GUI) 608, which includes a manifest aggregator 602, that can aggregate (merge) passenger manifest files from multiple computing devices 122, servers 148, or systems 100 for the current voyage. For example, a computing device associated with the travel information system 128 can communicate with multiple systems 100, and each system 100 may have multiple computing devices 122. The passenger manifest file includes multiple passenger manifest records created by the passenger manifest record generator 414 and the return leg manifest generator 416, which are composed of information accessed from the PNR 112.

[0183] It should be understood from this disclosure that there may be multiple local destinations, each serviced by a different system 100. For example, destination point DP 107 may be at a local train station within the port region of accommodation 126. Destination point DP 107 may be at a local bus terminal within the port region of accommodation 126. Destination point DP 107 may also be located at a regional airport within the port region of accommodation 126. "Local" means, for example, that the travel distance to accommodation 126 is less than 5-20 miles, 20-50 miles, or 51-100 miles. For example, a lodging facility may be docked at a port within a state that has multiple airports, train stations, bus terminals, etc., any of which a passenger may use to arrive as close as possible to the port based on their origin and travel costs.

[0184] The manifest GUI 608 interacts with the master manifest generator 604 and the return leg sorter 606. The master manifest generator 604 aggregates files received from one or more systems 100 and booked passenger manifests stored by the travel information system 128 into a master manifest file comprised of information derived from the digitized O-BTI. The master manifest file stores accessed information for PNRs 112 associated with the return leg of a trip for passengers whose BTs 142 have been scanned and processed by the system 100.

[0185] For example, at a cruise ship port of call, some passengers may arrive on the day of embarkation. In other instances, some passengers may arrive one or more days before embarkation. Additionally, PNRs 112 for multiple passengers embarking on the same cruise voyage may be consolidated into a master manifest file. As a non-limiting example, a third-party service provider may manage baggage for multiple cruise ships at port.

[0186] Each cruise ship has its own master manifest file. The manifest passenger records, populated based on the information in the PNR 112, are displayed on a display device using the manifest GUI 608. The manifest GUI 608 is a computer program that allows a user to view passenger information records, return leg flight information, etc. The passenger records may also include the passenger's cabin number for the current voyage. The return leg flight information may include, but is not limited to, one or more of travel carrier information, the travel carrier's geographic location, the flight number, the flight departure time, the flight arrival time, etc.

[0187] The master manifest generator 604 can display the generated master manifest file using a manifest GUI 608. The manifest GUI 608 can include a return leg sorter 606 that sorts the manifest by data related to return flights or modes of return travel that meet the check-in window for the return leg of travel.

[0188] Without intending to be bound by theory, accessing PNR112 data based on a digital reproduction of the 10-digit license plate and using that accessed data to automate the passenger manifesting and / or baggage check-in process for the return travel leg can save valuable cruise ship human resources and return travel carrier resources.

[0189] The processor may use the manifest GUI 608 to sort a master manifest file containing information associated with passenger manifest records by return flight time or other designated time. The processor may execute baggage check-in processing for the return leg for each passenger's designated return travel carrier based on the sorted master manifest file. In some embodiments, the master manifest file is for a resort destination that may include at least one hotel.

[0190] The baggage check-in data for the return leg may include at least a return leg flight time, an airline carrier, and a PNR. The method may include sorting, by at least one processor, a master manifest file including information related to the return leg flight times of a plurality of passengers, and performing, by the at least one processor, remote check-in processing of the return leg baggage with each passenger's designated return leg carrier based on the sorted master manifest file.

[0191] Referring to FIG. 7, in a basic configuration, the computing device 700 (i.e., the computing device 122 or local computing device) may include any type of fixed computing device, server 148, 1310, or 1826, a personal computer (PC), or a mobile computing device 302 and 1810.

[0192] Computing device 700 may include one or more processing devices 706 and system memory within a hard drive. Depending on the exact configuration and type of computing device 700, the system memory may be volatile (e.g., RAM 702), non-volatile (e.g., read-only memory (ROM 704), flash memory, etc.), or a combination of both. The system memory may store an operating system and one or more applications 724, and may include program data for executing at least one of programming modules 400 described above in connection with FIG. 4 and programming modules 600 described above in connection with FIG. 6.

[0193] The computing device 700 may execute any of the methods 500 of FIG. 5, 800 of FIG. 8, 900 of FIG. 9A, 950 of FIG. 9B, 1000 shown in FIG. 10, 1100 shown in FIG. 11, 1900 shown in FIG. 19, 2000 shown in FIG. 20, and 2300 shown in FIG. 23 via the application 724. The computing device 700 may have additional functionality or features. By way of non-limiting example, the computing device 700 may also include additional data storage media devices 708 (removable and / or non-removable), such as magnetic disks, optical disks, or tape. The computer storage media devices 708 may include volatile and non-volatile, non-transitory, removable, and non-removable media implemented in any method or technology for storage of data, such as computer-readable instructions, data structures, program modules, and other data. System memory, removable storage, and non-removable storage are all non-limiting examples of computer storage media. Computer storage media include RAM 702, ROM 704, electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other physical medium capable of storing desired data and accessible by computing device 700. Such computer storage media may be part of the device.

[0194] The computing device 700 may also include an input / output (I / O) interface 712 for an input module 714, such as a keyboard, mouse, pen, voice input device, or touch input device. The input module 714 may include the video device, imaging device 118, and / or scanner 116 shown in FIGS. 1A or 1B. The computing device includes or has an I / O interface 712 for connecting to output devices, such as a display, a presentation module 716, or speakers. A graphical user interface (GUI) 718 is displayed on the presentation module 716. The computing device 700 includes a peripheral bus 710 for connecting to peripherals. The computing device 700 may include communication connections that allow it to communicate with other computing devices over a network or wireless network.

[0195] By way of example, and not limitation, communication connections include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared, and other wireless media. Computing device 700 may include a network interface 720 (e.g., a network interface card) for connecting (wired or wirelessly) to a network or other communication path 722.

[0196] The computing device 700 may include an accelerometer (ACC) 735, a gyroscope, a global positioning system (GPS) 737, and / or an inertial navigation unit (INU) 740 to determine the location of the computing device 700, such as a mobile communication device, a scanning device, a computing device, or other RF communication device. The location data of the computing device 700 used to obtain the OP-BTI includes the location data of the baggage item and a timestamp associated with the location data.

[0197] Computer program code for carrying out the operations described above can be written in various programming languages, including, but not limited to, high-level programming languages ​​such as C, C++, Python®, and Java, for ease of development. Additionally, computer program code for carrying out the operations of the embodiments described herein can also be written in other programming languages, including, but not limited to, interpreted languages. Some modules and routines may be written in assembly language or microcode for improved performance and memory utilization. Furthermore, some or all of the functionality of the program modules may be implemented using discrete hardware components, one or more application-specific integrated circuits (ASICs), or programmable digital signal processors (DSPs) or microcontrollers. The program code for the embodiments may be included as firmware in RAM, ROM, or flash memory. Alternatively, the code may be stored on a tangible computer-readable storage medium, such as a magnetic tape, a floppy disk, a hard disk, a compact disc, a photomagnetic disk, or a digital versatile disc (DVD).

[0198] The present embodiment may be configured for use in a computer or data processing device that includes a central processing unit (CPU), RAM, ROM, and a storage medium such as a hard disk.

[0199] In some embodiments, when the computing device is a server, the server may be one or more servers, and the server may be a virtual server.

[0200] 8 illustrates a flowchart of a method 800 for checking in baggage for a passenger departing or leaving a lodging facility, according to one embodiment. While the exemplary method 800 depicts a specific order of operations, the order can be changed without departing from the scope of the present disclosure. For example, some of the illustrated operations may be performed in parallel or in a different order without substantially affecting the functionality of the method 800. In other examples, different components of an exemplary device or system implementing the method 800 may perform functions substantially simultaneously or in a specific order. In some embodiments, one or more blocks disclosed herein may be omitted or blocks may be added.

[0201] According to some examples, method 800 includes checking in baggage for the passenger's return flight from the accommodation at block 802. If the first-mode mobile carrier is an airline, method 800 may determine whether a baggage check-in window has opened. For example, passengers and / or their baggage may be allowed to check in 24 to 48 hours before the return flight departure time. Rail carriers may have different check-in times.

[0202] According to some examples, method 800 includes generating a baggage tag identifier and an IATA license plate at block 804. In some examples, the return IATA license plate may be generated by a DCS or other airline host computer system designated to generate IATA license plates for airline carriers. "Generating" may vary from airline to airline, mode to mode, and situation to situation. For example, server 1310 or server 148 may include a programming module that assigns a unique identifier compatible with an IATA license plate and associated barcode. Server 1310 or server 148 may include a programming module for formatting the baggage tag in a format compatible with the IATA baggage tag format, such as that shown in FIG. 2A.

[0203] According to some examples, method 800 includes printing a baggage tag with the license plate by a printing device at block 806. When a passenger's baggage is checked in for a flight or the like, one or more IATAB-type messages are generated that include baggage details such as arrival and departure airport codes, date, and a 10-digit baggage tag identifier, passenger name, and PNR information.

[0204] In some embodiments, the printing device is capable of printing marker tags that can be adhesively attached to luggage.

[0205] In some embodiments, the method includes communicating to the passenger information related to the return flight's 10-digit baggage tag identifier, thereby enabling the passenger to locate and track their baggage upon arrival on the final leg of their journey, such as using the IATA 10-digit baggage tag identifier.

[0206] Method 800 may include, during the remote / return baggage check-in process, obtaining, by at least one processor, airline baggage tag information for the return leg of the passenger's checked-in baggage, and printing, by a printer, new baggage tags for the return leg that are compatible with IATA license plates for each of the passenger's checked-in baggage.

[0207] Method 800 may include replacing the printed baggage tag from the outbound flight with a new return baggage tag for the return leg of travel.

[0208] In some embodiments, when the origin printed baggage tag is removed and replaced, the passenger's baggage item can be tracked along other modes of travel using a new return baggage tag, which is used to track the baggage's location for delivery to the lodging on the return journey.

[0209] 9A illustrates a flowchart of a method 900 for integrating passenger manifest information and accommodation information, according to one embodiment. While the illustrated routine depicts a specific order of operations, the order can be changed without departing from the scope of the present disclosure. For example, some of the illustrated operations may be performed in parallel or in a different order without substantially affecting the functionality of the routine. In other examples, different components of an example device or system implementing the routine may perform functions substantially simultaneously or in a specific order. In some examples, one or more blocks disclosed herein may be omitted or blocks may be added.

[0210] Accommodations include cruise ships, resorts, hotels, short-term rental homestays, long-term rental homestays, homes, buildings, etc.

[0211] According to some examples, method 900 may include searching and identifying lodging information from an accommodation database for each passenger in the manifest file at block 902. As a non-limiting example, the accommodation database may include the passenger's room, suite, or cabin number.

[0212] Method 900 may be an inbound process for handling passenger baggage when the passenger or their baggage arrives at an accommodation. In some embodiments, the passenger does not need to be present at the destination or accommodation for inbound registration of the baggage. The manifest file 1316 may be from an airport. Other reservation information may be obtained from manifests of a rail (train) reservation system 1318, a bus reservation system 1320, a ferry reservation system (not shown), and an accommodation reservation system 1322 shown in FIG. 13 .

[0213] In some embodiments, travel reservations for multiple modes of transportation and / or accommodations may be consolidated to provide passenger baggage delivery and check-in information in a passenger-agnostic manner, and in some cases, the centralized consolidated manifest may not be tied to a specific mode of transportation or accommodation.

[0214] According to some examples, method 900 may include updating a manifest file with lodging information at block 904. According to some examples, method 900 may include selectively providing the lodging information to the passenger from the updated manifest at block 906. According to some examples, method 900 may include providing the updated manifest to the accommodation facility at block 908. The updated manifest includes the lodging information from the accommodation facility and passenger information such as passenger name, return flight information for at least the first mode mobile carrier, and origin baggage tag ID.

[0215] According to some examples, method 900 may include communicating the accommodation information to type B message server 1310 (FIG. 13). According to some examples, method 900 may include, at block 912, determining whether an update to the accommodation information has been received. If the determination is "YES," the method returns to block 910 and communicates the updated accommodation information to type B message server 1310. If the determination is "NO" at block 912, method 930 returns to block 912 and waits for an update.

[0216] 9B illustrates a flowchart of a method 950 for initiating an extended B-type message according to one embodiment. Method 950 will be described in conjunction with FIG.

[0217] FIG. 13 illustrates a smart baggage movement system 1300 for multimodal travel and accommodation according to one embodiment. The smart baggage movement system 1300 may include a server 1310 and a database 1308 for facilitating tracking, locating, and checking in passenger baggage items independent of the passenger and the passenger's check-in process. The database 1308 is an extended B-type message database or a universal B-type message database. For example, the extended B-type message database includes an extended BSM with a departure BSM obtained from an airline carrier, and created accommodation data or a link to the accommodation data is added to the departure BSM in an extended or universal B-type message. The extended message includes an extended or universal start header and an end-of-message identifier code at the end of the extended message (see FIG. 14A). The terms "extended B-type message" and "universal B-type message" may be used interchangeably herein. The terms "extended BSM" and "universal BSM" may also be used interchangeably.

[0218] Server 1310 or server 148 may have access to reservation information related to other modes of transportation, such as a ferry reservation system or a manifest file 1316 related to other modes of transportation. Server 1310 or server 148 may have access to a train reservation system 1318. Server 1310 or server 148 may have access to a bus reservation system 1320. Server 1310 or server 148 may have access to an accommodation reservation system 1322.

[0219] Server 1310 or server 148 may obtain airline reservation information related to departing flight 1302 from an airline manifest, a B-type message, an airline reservation system, or a passenger. Server 1310 or server 148 may obtain intermediate travel reservations 1304, for example, from a rail reservation system 1318 or a passenger.

[0220] The server 1310 or the server 148 can obtain the accommodation reservation information 1306 from the accommodation reservation system 1322 or the passenger. The server 1310 or the server 148 can obtain the intermediate travel reservation from the bus reservation system 1320 or the passenger.

[0221] At least one or more of an outbound flight reservation 1302, an intermediate travel reservation 1304, an accommodation reservation 1306, and a return flight 1312 are stored in a universal passenger itinerary 1314. The passenger itinerary information 1314 may include outbound travel information to a destination point and return route travel information to home 102. The database 1308 may store the passenger itinerary information 1314 alone or as part of an extended (universal) B-type message for baggage check-in, baggage handling, and delivery for one or more travel legs.

[0222] Although the exemplary method 950 depicts a particular order of operations, the order can be changed without departing from the scope of the present disclosure. For example, some of the depicted operations can be performed in parallel or in a different order without substantially affecting the functionality of the routine. In other examples, different components of an exemplary device or system implementing the method 950 may perform functions substantially simultaneously or in a particular order. In some embodiments, one or more blocks disclosed herein may be omitted or blocks may be added.

[0223] According to some examples, method 950 may include, at block 914, retrieving at least one transportation reservation associated with the passenger's itinerary while the passenger is in transit. While the passenger is in transit, such as on an aircraft, one or more B-type messages are generated. For example, an airline host computing system generates a BSM when baggage is checked in at an airport or airline. In some embodiments, baggage may be checked in at a port, such as a home, a train station, or a port associated with a cruise ship. In these cases, the IATA B-type message may include an additional code indicating the type of remote check-in. The additional code is included in the BSM and stored or communicated to the airline host computer system or other related computer system. Typically, to ensure proper routing in an aviation environment, the airline host computer system or other related computer system communicates the B-type message to one or more baggage handling systems, sorting systems, matching systems, and industry tracking systems, thereby tracking the baggage's location within the airport environment. However, the B-type message may be deleted shortly after the passenger arrives at their destination.

[0224] Thus, in some embodiments, the system 100 can access B-type messages to obtain baggage tag numbers while the passenger is in flight.

[0225] According to some examples, method 950 may include accessing, by at least one processor, a passenger B-type message associated with the departing airline, which at least one processor resides outside the airline's computing environment in block 916. The at least one processor may be part of system 100 or system 1300, for example. System 1300 may include messaging system 1390 in communication with server 1310 and may communicate travel information in response to a trigger caused by scanning or otherwise obtaining the OP-BTI on a recycled, non-discarded, origin-printed IATA baggage tag.

[0226] According to some examples, method 950 may include extracting a digital IATA baggage tag number from the B-type message at block 918. As shown in FIG. 12A, the digital IATA baggage tag number is represented by several digits in a field beginning with ".N / ".

[0227] According to some examples, the method 950 may include, at block 920, obtaining an airline B-type message, such as from the airline's host computer system or other related computer system.

[0228] According to some examples, method 950 may include, at block 922, initiating creation of an extended B-type message with an airline B-type message that includes an IATA baggage tag number associated with a printed baggage tag for the outbound flight (origin), as shown in Figure 14A, where the fields within brackets 1200A' represent an airline B-type message format that is compatible with the IATA B-type message described in Figure 12A.

[0229] According to some examples, the method 950 may include, at block 924, obtaining return flight information for the passenger.

[0230] According to some examples, method 950 may include, at block 926, updating the extended type B message with the return flight data, which includes the simulated type B message shown in FIG. 12B. FIG. 12B illustrates the simulated type B message. The return flight data is queued within the extended type B message or within a designated separate simulated type B message until the passenger is ready to depart the accommodation. Due to clutter, the simulated type B message is not shown in FIG. 14A. The simulated type B message may be generated by simulated type B message generator 409 of FIG. 4.

[0231] According to some examples, the method 950 may include proceeding to FIG. 11 at block 928 for additional transportation options.

[0232] 10 illustrates a flowchart of a method 1000 for checking in passenger baggage, according to one embodiment. While the exemplary method 1000 illustrates a specific order of operations, the order can be changed without departing from the scope of the present disclosure. For example, some of the illustrated operations may be performed in parallel or in a different order without substantially affecting the functionality of the method 1000. In other examples, different components of an exemplary device or system implementing the method 1000 may perform functions substantially simultaneously or in a specific order. In some embodiments, one or more blocks disclosed herein may be omitted, or blocks may be added.

[0233] At block 1002, the method 1000 may include electronically acquiring, by at least one electronic acquisition device, an origin hard copy baggage tag identifier (OP-BTI) associated with or printed on a printed baggage tag from an outbound airline mobile carrier affixed to the passenger's baggage item, and creating a digital data record linked to the airline mobile carrier.

[0234] In block 1004, method 1000 may include, by at least one processor, querying a database using the OP-BTI as a unique identifier to obtain return flight data for the passenger. In some examples, block 1004 may include, by at least one processor, accessing an airline B-type message using the digital BTI data record in block 1008. In another example, the database is a manifest containing the digital BTI data record.

[0235] In block 1006, the method 1000 may include, by at least one processor, checking in each baggage of the passenger for a return flight with a mobile carrier for a return flight identified in the obtained return flight data. In some embodiments, the passenger is departing from the accommodation.

[0236] Accommodations include hotels, resorts, cruise ships, short-term rental homestays, long-term rental homestays, homes and buildings.

[0237] In some embodiments, at block 1010, the method 1000 may include causing, by at least one processor, a printing device to print an International Air Transport Association (IATA) compliant baggage tag for the return flight.

[0238] In some embodiments, a passenger may use multiple modes of transportation and / or temporary accommodations during the return journey or travel to the point of origin.

[0239] 11 illustrates a method 1100 for generating an extended (universal) B-type message for a passenger's return journey, according to one embodiment. While the exemplary method 1100 illustrates a specific order of operations, the order can be changed without departing from the scope of the present disclosure. For example, some of the illustrated operations may be performed in parallel or in a different order without substantially affecting the functionality of the method 1100. In other examples, different components of an exemplary device or system implementing the method 1100 may perform functions substantially simultaneously or in a specific order. In some embodiments, one or more blocks disclosed herein may be omitted or blocks may be added.

[0240] According to some examples, method 1100 may include inputting, by a server (i.e., server 1310), data including an extended (universal) B-type message for multi-modal travel and overnight accommodation reservations into records in database 1308. The extended (universal) B-type message includes a set of data fields corresponding to each mode of transportation in at least one passenger's itinerary and identifies the multi-modal travel and overnight accommodation reservations linked by the unique identifier in block 1102.

[0241] In some embodiments, a passenger may enter a passenger itinerary using a website portal that is part of or accessible by system 100, 1300, or 1800. The passenger may enter information such as other transportation and accommodation reservations. In other embodiments, the passenger may enter a PNR or itinerary confirmation number using a website portal that is part of or accessible by system 100, 1300, or 1800.

[0242] In some embodiments, the website portal may be part of an accommodation facility (such as, but not limited to, a resort or a cruise ship).

[0243] According to some examples, method 1100 may include determining whether the passenger is traveling by bus at block 1104. If the determination is "NO," a value "NULL" 1106 is returned to the server. If the determination at block 1104 is "YES," the server at block 1108 receives bus mode reservation data from bus reservation system 1320 of FIG. 13 in a bus data field set with the unique identifier as a primary key.

[0244] According to some examples, method 1100 may include determining whether the passenger is traveling by train at block 1110. If the determination is "NO," a value of "NULL" 1112 is returned to the server. If the determination at block 1110 is "YES," the server at block 1114 receives train mode reservation data from the rail reservation system 1318 of FIG. 13 in a set of train data fields with the unique identifier as a primary key.

[0245] According to some examples, method 1100 may include determining whether the passenger has an accommodation at block 1116. If the determination is "NO," a value of "NULL" 1118 is returned to the server. If the determination at block 1116 is "YES," the server receives, at block 1120, accommodation data in a set of accommodation data fields from accommodation reservation system 1322 of FIG. 13, with the unique identifier as a primary key. Blocks 1108, 1114, and 1120 flow to block 1122.

[0246] According to some examples, method 1100 may include determining whether there are updates to either transportation or lodging at block 1122. If the determination at block 1122 is "NO," the method loops at line 1128 to wait for an update. If the determination at block 1122 is "YES," method 1100 triggers a communication update at block 1124 and causes a display of the update at block 1126. In some embodiments, the communication does not occur until the server is triggered by a communication representing received image data from the acquisition device.

[0247] The server 1301 may update the corresponding passenger itinerary linked to the universal B type message in the database 1308 .

[0248] FIG. 12A shows a conventional BSM 1200A for an airline carrier. The BSM is a B-type message. A B-type message may have multiple data fields containing coded characters. For example, the coded characters may include the American Standard Information Interchange Code (ASCII code), board dots, padded board dots, etc. The codes and formats of baggage information messages (B-type messages) are described, for example, in IATA's "Recommended Practice 1745 Baggage Information Messages" (Passenger Service Resolution Manual, June 2010, 30th Edition, pp. 1110-1205).

[0249] A B-type message may include a field or line 1202 containing a header. For example, the header may be labeled "BSM" and represent a heading indicating the beginning of an airline BSM. Field or line 1204 may include a line prefix ".V / " followed by a set of alphanumeric characters. As a non-limiting example, the line prefix ".V / " may indicate version and supplemental data. For example, the supplemental data may include layover locations in an airline environment.

[0250] Field or row 1206 may contain the row prefix ".F / " followed by a set of alphanumeric characters representing the flight number and date of departure. The alphanumeric characters may be separated by the symbol " / ". For example, the data "22MAY" may represent the arrival date. The code "IST" represents Istanbul Airport.

[0251] Field or row 1208 may include the row prefix ".I / " followed by a set of alphanumeric characters representing the flight number and date of arrival. The alphanumeric characters may be separated by the symbol " / ". For example, the data "12MAY" may represent the departure date. The code "SLC" represents Salt Lake City Airport.

[0252] Field or row 1212 may contain a line prefix ".N / " followed by a set of numbers, which represents the digital BTI data record of the OP-BTI. Field or row 1210 may contain a line prefix ".P / " followed by a set of letters, which represents the passenger's first and last name. The first and last name may be separated by the symbol " / ".

[0253] Field or line 1218 may contain the line prefix ".L / " followed by a set of alphanumeric characters representing a passenger name record (PNR) number. Field or line 1220 may contain an end of message indicator, such as "ENDBSM."

[0254] Between lines 1202 and 1220, there may be other fields or lines, such as fields 1214 and 1216. Field or line 1214 has the prefix ".S / " and is matching data. Field or line 1216 has the prefix ".W / " and relates to weight, number, dimensions, and type data of baggage items. Since airline B-type messages are well known in the art, a detailed description of the B-type message will be omitted. Some of the fields / lines are mandatory and others are optional depending on the B-type message.

[0255] However, system 100 may access other Type B messages from an airline-associated computer system to, for example, determine if baggage is lost or missing. System 100 may access other Type B messages stored in an airline-associated computer system to determine the status of baggage, for example, before a passenger begins their stay at an accommodation, or at other times to track the status of baggage as it moves through an airport environment.

[0256] The exemplary BSM 1200A is provided for illustrative purposes and is not intended to be limiting in any way. Each airline may make modifications to its Airline BSM.

[0257] 12B illustrates a simulated BSM 1200B for a return flight that may be generated within or outside of a restricted check-in window, according to one embodiment. This simulated BSM 1200B may serve as a placeholder for generating a larger number of BSMs, for example, within or outside of an airline or other mode of transportation's restricted check-in window.

[0258] A B-type message may include a field or line 1222 containing a header. For example, the header may be labeled "SBSM," representing a heading indicating the beginning of an airline BSM. Alternatively, it may include another B-type message header. For purposes of explanation and illustration, the simulated BSM in this example has the same format and layout as the BSM in FIG. 12A. Therefore, only the differences will be described. For simplicity, the same code references may be used. However, slight variations may occur. For example, the simulated BSM header or other B-type message may begin with an "S," resulting in a header called "SBSM." As another example, the simulated BSM header or other B-type message may end with a symbol (e.g., "*"). These examples are not limiting. The starting character "S" may include an alphanumeric combination of two letters or two-digit codes.

[0259] A field or row 1224 may include a row prefix ".V / " followed by a set of alphanumeric characters. As a non-limiting example, the row prefix ".V / " may indicate version and supplemental data. Because this is a simulated BSM outside of the regulated check-in window, the ".V / " field is marked as "NULL."

[0260] Field or row 1226 may contain the row prefix ".F / " followed by a set of alphanumeric characters representing the flight number and date of departure. The alphanumeric characters may be separated by the symbol " / ". For example, the data "31MAY" may represent the arrival date. The code "SLC" represents Salt Lake City Airport.

[0261] A field or row 1228 may contain the row prefix ".I / " followed by a set of alphanumeric characters representing the flight number and date of an arriving flight. The alphanumeric characters may be separated by the symbol " / ". For example, the data "30MAY" may represent the departure date. The code "IST" represents Istanbul Airport.

[0262] Field or row 1230 may contain the line prefix ".N / " followed by the string "NULL", which indicates that the baggage tag identifier is unassigned. Field or row 1236 may contain the line prefix ".P / " followed by a string representing the passenger name. The first and last names may be separated by the " / " symbol.

[0263] In some embodiments, the simulated type B message generator 431 may assign a baggage tag identifier that is compatible with the 10-digit IATA baggage tag number printed on baggage tags for airline carriers. In this case, the ".N / " prefix is ​​followed by the assigned baggage tag identifier or the 10-digit IATA baggage tag number. The number in the field following the ".N / " prefix may represent the number of checked baggage items.

[0264] The assignment of baggage tag identifiers by server 148 or server 1310 outside the air travel information system may vary by airline and country.

[0265] Fields or rows 1238 and 1240 may be used for remote check-in. For example, field row 1238 may include a row prefix ".D / " followed by a set of alphanumeric or alphabetic characters indicating baggage check-in details. Each ".D / " code field differs based on location data depending on the type of remote check-in. For example, field 1238 includes at least location data, date, time, etc. Field or row 1240 includes a prefix ".C / " followed by a string representing a company or group name, etc.

[0266] Field or line 1242 may contain the line prefix ".L / " followed by a set of alphanumeric characters representing a passenger name record (PNR) number. Field or line 1244 may contain an end of message indicator, such as "ENDBSM."

[0267] Between rows 1222 and 1240, there may be other fields or rows, such as fields 1232 and 1234. Field 1232 has the prefix ".S / " and field 1234 has the prefix ".W / ", but both are marked "NULL." Fields or rows marked "NULL" cannot be populated with return flight data because airline systems, such as DCS, do not allow baggage to be checked in until the restricted check-in window opens.

[0268] The simulated B-type message or simulated BSM can be used as a placeholder to pre-populate a BSM for baggage check-in that assigns an IATA license plate number or other B-type message.

[0269] In some embodiments, the third party provider or the company checking in the baggage may be configured to assign a unique identifier compatible with an IATA license plate number that includes a barcode format for printing on the IATA baggage tag.

[0270] Universal Luggage Tag

[0271] The inventors recognized a critical need to address the baggage handling disconnect across the passenger transportation system. Leveraging originating airline baggage tags (traditionally discarded) can address current passenger experience challenges and significantly reduce the significant system costs associated with moving and identifying baggage across multiple modes of transportation and accommodations. Leveraging origin baggage tags not only provides bags with an identifier containing critical information, but also provides access to a messaging system, enabling a smart baggage travel experience. This removes the burden of baggage from passengers during their travels, while providing the same seamless travel experience for the baggage. By enabling smart baggage with identifiers and messaging across all modes of transportation and accommodations, recycling original airline baggage tags and an enhanced system associated with provisioning OP-BTI for use at off-airport facilities enables a new, cost-effective and seamless travel experience.

[0272] Figure 14A illustrates an enhanced (universal) B-type message 1400A for multi-modal travel and accommodation and origin baggage tag recycling, according to one embodiment. Figure 14B illustrates an enhanced (universal) B-type message 1400B for a return flight, according to one embodiment.

[0273] For purposes of explanation and illustration, the extended (universal) B-type message may be a universal BSM. The extended B-type message 1400A includes the BSM 1200A' described above in connection with FIG. 12A. According to some embodiments, the BSM 1200A' is a light airline BSM version of the BSM 1200A of FIG. 12A. Generally, fields 1202, 1210, 1212, 1218, and 1220 are preserved. In some embodiments, all fields may be preserved. In some embodiments, a different BSM structure may be created. Additionally, the extended B-type message 1400A may use other encoding formats.

[0274] In this example, the B-type message 1200A' may be immediately followed by the simulated B-type message 1200B shown in Figure 12B. The header of the extended B-type message 1400A may use, for example, the code "UBSMRC" shown in Figure 14A, reference numeral 1402. The "U" indicates that the message is universal and can be used outside the airport. The "BSM" indicates the type of B-type message format. The "RC" indicates that the format of the universal message is for recycling IATA printed baggage tags at the point of origin.

[0275] After the end designator "ENDSBSM," one or more fields or lines 1420, 1430, 1440, 1450, 1460 may be added. The extended B-type message 1400A may have an end-of-message identifier "UENDBSMRC" in field 1410. The code term "RC" stands for recycle and the code term "RT" stands for return trip.

[0276] For purposes of explanation and example, the prefix ".L / " in field 1430 may include a link to the lodging PNR number listed in itinerary 1314. However, lodging data including lodging address, room or cabin number, etc., may be entered directly, as non-limiting examples. Also, the prefix may use a different encoding scheme.

[0277] The prefix ".L / " in row 1420 may contain data representing a link to an intermediate transfer PNR number or alternative travel data.

[0278] The prefix ".PL / " in field 1440 may represent a code for a link to a passenger baggage image. The prefix ".PL / " in field 1450 may represent a code for a link to a passenger ID image. The prefix ".LL / " in field 1460 may represent a code for a link to a log of baggage location data.

[0279] Once the checked-in baggage's return baggage tag replaces the printed baggage tag from the departure point, the return baggage tag becomes machine-readable, allowing for continued tracking, locating, and check-in of the baggage across multiple modes of transportation and multiple lodgings on the return journey.

[0280] The simulated B-type message 1200B can vary depending on whether the baggage was checked in remotely, at the airport, or with the airline. For example, there are recommended BSM formats for baggage checked in remotely from home, a train station, or a cruise ship at a port. As a non-limiting example, the field or code ".D / " can be used to enter check-in location information. If the baggage was checked in at a train station, the train station name, date, and time can be added to the ".D" field, separated by a " / " character. If the baggage was checked in at a port, the port name, port identifier, date, and time can be added to the ".D / " field, separated by a " / " character. This is shown in the simulated BSM because the example assumes check-in from a cruise ship. Different location data may be used for other approved remote check-in locations.

[0281] The ".M" and ".Z" symbols may be unused in IATA messages, however this may change in the future, and therefore other code combinations may be used to distinguish different fields in Extended / Universal B-type messages.

[0282] This disclosure refers to the encoding scheme for IATA Type B messages for illustrative purposes, although other encoding schemes may be used for extended Type B messages outside of an airline environment.

[0283] FIG. 14B illustrates an enhanced (universal) B-type message 1400B for a return flight, according to one embodiment. Field 1402′ is a header and may include the code “UBSMRT,” where “U” indicates universal, “BSM” indicates the type of B-type message, and “RT” indicates return. Bracketed field 1250 represents the lite airline BSM, as described above for bracketed field 1200A′. In this case, field “.N / ” is updated with the IATA baggage tag number from the printed baggage tag for the return flight, which is different from the “.N / ” number in lite BSM 1200A′. In this case, the lite airline BSM 1250 may be followed by universal B-type message 1400A. FIG. 14B illustrates an enhanced (universal) B-type message 1400B for a return flight, according to one embodiment.

[0284] In some embodiments, the UBSMRC 1400A may be followed by fields 1440', 1450', and 1460' (collectively 1470), as described above, although the data in these fields may be for the return leg of the journey. The extended (universal) B-type message 1400B includes an end-of-message designator 1410', which may be "UENDBSMRT."

[0285] 15 shows a block diagram of linking multi-modal travel and lodging data to extended data according to one embodiment. The extended B-type message 1400A may access or have links to outgoing airline reservations 1302, intermediate travel reservations 1304, accommodation reservations 1306, and return airline flights 1312 stored in the universal passenger itinerary 1314. The extended B-type message 1400A may access or have links to baggage location data log 1325 in database 1308, baggage images 1330 in database 1308, and passenger ID images 1335 in database 1308.

[0286] FIG. 16 illustrates an extended (universal) B-type message for multimodal travel and lodging and departures, according to one embodiment. B-type message 1600 (i.e., UBSMO) may include the header "UBSMO" in field 1620. Field 1620 is followed by a simulated BSM or other B-type message 1200B', as described in FIG. 12B. In message 1200B', field 1630 may contain a temporary unique identifier as a placeholder until the IATA baggage tag number is generated. Simulated BSM 1200B' may be followed by fields 1640, 1650, and 1660 (collectively 1670) containing links to passenger baggage image data for the departure segment, passenger ID image data for the departure segment, and location data for the departure segment, respectively. Details will become clearer in the discussion of FIGS. 18 through 24 below. B-type message 1600 may include an end-of-message identifier, such as "UENDBSMO" 1610.

[0287] Once the baggage item is ready to check in, simulated message 1200B' is integrated with, for example, the airline's BSM to obtain the IATA baggage tag identifier and other remaining information. An implementation of the IATA baggage tag identifier according to system 1800 is described below.

[0288] 17 shows a block diagram of linking departing multi-modal travel and accommodation data to extended data according to one embodiment. A B-type message 1600 (i.e., UBSMO) may access or have links to departing airline reservations 1302, intermediate travel reservations 1304, accommodation reservations 1306, and return airline flights 1312 stored in a universal passenger itinerary 1314. The B-type message 1600 may access or have links to location data 1325, baggage images 1330, and passenger ID images 1335.

[0289] Baggage check-in at departure point

[0290] Remote check-in at home began around 2001 and has taken various forms over the years, but has been difficult to implement due to the significant technology costs at remote sites and the logistical challenges of pre-printing documents such as valet tags and baggage tags. Valet tags are discarded and replaced with permanent IATA baggage tags, creating environmental waste. While a single valet tag itself is not considered a significant problem, the cumulative waste of paper, ink, and equipment used to print millions of valet tags over the years creates environmental waste that contributes to long-term climate change.

[0291] Remote check-in challenges in some environments include strict time constraints, such as 24-hour check-in windows, making process management and profitability extremely challenging. The present embodiment addresses these concerns and provides an environmentally friendly, on-demand, lightweight technology. Specifically, it combines simulated BSM and / or assignable IATA baggage tag codes for ID verification and validation, location verification, itinerary verification, ticket purchase verification, baggage image capture, and / or temporary wireless baggage tracker attachment. This allows airline B-type messages to trigger baggage tag printing, resulting in a seamless baggage check-in experience.

[0292] 18, 19, 20, and 23 may be performed by programming instructions stored on a tangible, non-transitory computer-readable medium that, when executed by one or more processors or servers, cause the processors or servers to perform the operations of the blocks described below.

[0293] 18 illustrates a digitized baggage storage and baggage check-in system 1800 according to one embodiment. System 1800 may be part of systems 100 and / or 1300 in some embodiments. In some embodiments, the present disclosure provides an integrated system that integrates the operation of systems 100, 1300, and 1800 to enhance the baggage items and travel experience of passengers 1816 while eliminating environmental waste.

[0294] System 1800 may include at least one first processor 1810 and at least one second processor 1826 in wired or wireless communication with each other. System 1800 does not include the items within the dashed-dotted box. System 1800 may include at least one baggage storage location 1834 for temporarily storing baggage. System 1800 may include other computing devices 1848 for obtaining baggage tag identifiers and other information attached to the baggage, as described below.

[0295] In some embodiments, the system 1800 may include a baggage check-in module 1870 and a simulated BSM generator 1875. The simulated BSM generator has been described above and therefore no further description is necessary.

[0296] In some embodiments, the system 1800 may include an assignable baggage tag code module 1860. The assignable baggage tag code module 1860 bypasses the IATA baggage tag codes generated by the airline carrier's DCS and assigns IATA baggage tag codes by the system 1800. The assigned IATA baggage tag codes are populated into a simulated BSM and further integrated with missing airline BSM data to form a unified BSM. The unified BSM is an integration of information from the simulated BSM and the airline BSM. This unified BSM is used to create an extended BSM. The same process for creating a unified BSM can be used to create a unified B-type message.

[0297] It should be noted that system 1800 can be used for origin tags at lodging facilities. Additionally, as shown in FIG. 1A, in some embodiments, route L1 can be provided by system 1800, where baggage 138 is collected at home 102 and checked in before delivery to first mode mobile carrier 104. This generates baggage tag 142 by system 1800 using the methods disclosed herein.

[0298] In some embodiments, first processor 1810 may receive a PNR number 1830 or other identifier from a confirmed itinerary 1818 for a flight with at least one airline carrier. From the confirmed itinerary 1818, first processor 1810 receives information confirming the identity of the passenger associated with the PNR number 1816 and picks up and transports baggage associated with that PNR number from passenger location 1812 to baggage storage location 1834. Confirmed itinerary 1818 ( FIG. 21 ) may be generated by a computer system 1828 associated with the airline carrier.

[0299] 21 illustrates an example of a confirmed itinerary 1818 for an airline flight according to one embodiment. The confirmed itinerary 1818 includes at least one of a passenger record number (PNR), a passenger name, flight booking information, and a purchased ticket number.

[0300] In some embodiments, the system 1800 may include a tracker assignment module 1865, which includes an application that names wireless trackers and assigns them information associated with a unique code, such as a PNR or other identifier, as described below in FIG.

[0301] In one embodiment, the system 1800 includes an imaging device in communication with a first processor 1810. The imaging device and the first processor 1810 may be integrated into a single device, such as a smartphone, mobile communication device, tablet, notebook, or other portable computing device with camera capabilities. As shown in FIG. 1 , the imaging device may capture an image (hereinafter referred to as an “LI image 1806”) of each baggage item (LI) 1814 associated with the PNR 1830 prior to departure from the passenger location 1812.

[0302] In one embodiment, the imaging device can capture an image of the identification 1820 issued to the passenger (hereinafter referred to as "ID image 1804"). The first processor 1810 and the user of the imaging device can verify the passenger's identity and match it with the PNR in the confirmed itinerary 1818. The PNR is associated with at least one person. However, at the time of pick-up of at least one bag of baggage 1814, only one individual in the PNR may need to be verified. In some embodiments, all passengers must be present, and all adult passenger identification must be verified.

[0303] 22 illustrates a graphical user interface 2208 on a mobile communication device 2210 capturing a passenger identification document 1820 according to one embodiment. After an image of the passenger identification document 1820 is captured, the image is sent to a verification process 1880. For example, the verification process 1880 may have policies and procedures for verifying the identification document depending on the state of issuance of the identification document and the type of identification document, such as a driver's license or passport. Communication procedures for contacting a Department of Motor Vehicles (DMV) database may be stored in the verification process module 1880 for subsequent lookup. The verification process 1880 completes the verification process and communicates a signal representing the verification received from the DMV, for example, to the first processor 1810. This signal is then displayed on a display device.

[0304] In one embodiment, the first processor 1810 may receive data input representing verification of the passenger by a user of the first processor 1810. For example, the user may receive the identification document 1820 and visually match the passenger's name listed on the confirmed itinerary with the name on the identification document 1820. In some embodiments, the first processor 1810 may be configured to extract the name of the individual in the identification document 1820 using optical character recognition (OCR) or other software applications, such as converting a PDF or JPEG file to a DOCX (MICROSOFT WORD) file.

[0305] In one embodiment, the imaging device of the first processor 1810 can capture an image of the confirmed itinerary 1818, an image of a barcode, or an image of a QR code. Information related to the confirmed itinerary 1818 (e.g., but not limited to, names of other passengers associated with the confirmed itinerary 1818, origin airline carrier, destination airline carrier, departure date and time, destination arrival time, etc.) can be received. The first processor 1810 can receive the itinerary information and PNR by performing optical character recognition (OCR) on an image of a paper copy of the confirmed itinerary 1818 or using other artificial intelligence (AI) software to convert hard copy text into digital data. The first processor 1810 can receive the itinerary information and PNR by, for example, accessing the same information from a web portal linked to the passenger account.

[0306] In one embodiment, the passenger record may include at least one of the PNR of the confirmed itinerary 1818, images of each of the claimed baggage items, and a copy of identification 1820.

[0307] The first processor 1810 can communicate the PNR 1830, verification 1802, ID image 1804, LI image 1806, geographic location information 1808, and itinerary information 1846, grouped together in brackets 1832, to the second processor 1826. As a non-limiting example, a smartphone or other mobile computing device may include a Global Positioning System (GPS) receiver that receives signals from a GPS to determine the location of the first processor 1810. The digitized information in 1832 is used to eliminate the need for printed valet tags for tagging baggage items.

[0308] In one embodiment, the second processor 1826 may generate a simulated baggage source message (BSM) using the received PNR 1830, as shown in Figure 12B. The second processor is independent of the airline and the computer system 1828. The BSM is compatible with the International Air Transport Association (IATA) B-type message.

[0309] The second processor 1826 may cause an IATA license plate to be created for each baggage item associated with the PNR 1830 and related itinerary information.

[0310] In one embodiment, the second processor 1826 may update the virtual BSM with the created IATA license plate and communicate the updated BSM to a computer system 1828 associated with the airline.

[0311] The trackers 1840, 1842 attached to the baggage 1838 may be AIRTAG trackers from Apple®. The trackers 1840, 1842 may be Global Positioning System (GPS) trackers, GSM trackers, or other trackers. This step can be performed at any time, including when the baggage is brought into the baggage claim area 1834.

[0312] The AIRTAG tracker comprises a mobile application called FIND MY 2420 that appears on the display of a mobile communication device 2410, as shown in Figure 24. Other types of trackers may be programmed to transmit data to a computing device in response to a ping signal.

[0313] Baggage items are tagged with baggage tags that conform to the International Air Transport Association (IATA) baggage tag code and / or other carrier standardized formats. For example, airline baggage tags may include an IATA code, which includes a three-character alphanumeric geographic code that designates an airport or metropolitan area. This IATA code is also known as the IATA location identifier. IATA also publishes industry-standard rules for creating baggage tags for the airline industry. Printed baggage tags may include a 10-digit license plate number and a corresponding barcode. Printed baggage tags may include IATA geographic code generation information, departing airline flight information, the 10-digit license plate, and other baggage tag information that appears on hard-copy printed baggage tags.

[0314] 19 illustrates a flowchart of a method 1900 for generating a simulated baggage source message according to one embodiment. While the exemplary method 1900 illustrates a specific order of operations, the order can be changed without departing from the scope of the present disclosure. For example, some of the illustrated operations may be performed in parallel or in a different order without substantially affecting the functionality of the method 1900. In other examples, different components of an exemplary device or system implementing the method 1900 may perform functions substantially simultaneously or in a specific order. In some embodiments, one or more blocks may be omitted or blocks may be added.

[0315] According to some examples, method 1900 may include receiving a passenger name record (PNR) and itinerary information for a confirmed flight itinerary created by a computer system associated with an airline or a third-party travel coordinator (e.g., a travel agency or other entity independent of the airline) at block 1902. The process of block 1902 is described in more detail with respect to FIG. 20 below.

[0316] According to some examples, the method 1900 may include, at block 1903, capturing an image of the baggage item, geographic location information, a timestamp, and passenger identification information.

[0317] According to some examples, method 1900 may include, at block 1904, receiving information from the confirmed itinerary confirming the identity of a passenger associated with the PNR, and picking up baggage associated with the PNR from the passenger's location and transporting it to a baggage claim location.

[0318] According to some examples, method 1900 may include, at block 1906, generating a simulated baggage source message including the received PNR and itinerary information at a time prior to the start time of the check-in window, the simulated baggage source message being compatible with an International Air Transport Association (IATA) B-type message.

[0319] According to some examples, the method 1900 may include, at block 1908, causing an IATA license plate to be generated for each baggage item associated with the PNR during the check-in window.

[0320] According to some examples, the method 1900 may include, at block 1910, updating the SBSM with the generated IATA license plate.

[0321] According to some examples, method 1900 may include merging the BSM with an SBSM created by the airline carrier during the check-in window to create a unified BSM at block 1912. One or more of blocks 1908, 1910, and 1912 may be part of a baggage check-in process for picking up baggage from a passenger's home.

[0322] According to some examples, the method 1900 may include, at block 1916, printing an IATA-compatible baggage tag using the digital BSM.

[0323] Although this description discloses an example of home location baggage collection and passenger verification, this process can be carried out at any remote location outside of airport facilities.

[0324] 20 illustrates a method 1902 for recording a passenger itinerary according to an embodiment. In some embodiments, the method 1902 may include identifying an origin airline carrier from the itinerary at block 2002. In some embodiments, the method 1902 may include identifying a destination airline carrier from the itinerary at block 2004. In some embodiments, the method 1902 may include identifying a PNR number from the itinerary at block 2006. In some embodiments, the method 1902 may include identifying a departure date from the itinerary at block 2008.

[0325] Figure 23 illustrates a flowchart of a method 2300 for tracking baggage prior to attaching a baggage tag to a baggage item, according to one embodiment. Figure 24 illustrates a mobile communications device displaying Apple's FIND MY application, according to one embodiment. The FIND MY application is an example of a tracker, but other trackers may be used, and this disclosure is not limited to Apple's AIRTAG.

[0326] Although method 2300 depicts a particular sequence of operations, the sequence may be modified without departing from the scope of the present disclosure. For example, some of the illustrated operations may be performed in parallel or in a different order without substantially affecting the functionality of method 2300. In other examples, different components of an exemplary device or system implementing method 2300 may perform functions substantially simultaneously or in a particular order. In some embodiments, one or more blocks may be omitted or blocks may be added.

[0327] According to some embodiments, the method 2300 may include, at block 2302, assigning a temporary wireless baggage tracker 1840 or 1842 to the passenger's baggage.

[0328] As a non-limiting example, the collected PNR and travel date and time shown in Figure 20 may be saved in a manifest or other file used to notify personnel of the check-in window for the baggage item. Assigning a temporary wireless baggage tracker to a passenger baggage item may include, for example, naming the temporary wireless tracker 1840 with the passenger's PNR.

[0329] According to some examples, the method 2300 may include, at block 2304, attaching a temporary wireless baggage tracker to the baggage item.

[0330] According to some examples, the method 2300 may include, at block 2306, transporting the baggage item to a baggage storage location.

[0331] According to some examples, the method 2300 may include, at block 2308, pinging 1850 a baggage tracker at the storage location to notify an employee of the location of the passenger's baggage item. For example, an AIRTAG may be controlled to sound a sound.

[0332] According to some examples, method 2300 may include, at block 2310, after the baggage item is located, matching passenger information with the PNR and / or printed baggage tag at a communication device linked to the tracker.

[0333] According to some examples, method 2300 may include attaching printed baggage tags and / or markers to the baggage items matching the passenger information at block 2312. The baggage tag information may be communicated to the passenger.

[0334] According to some examples, method 2300 may include removing 2314 the temporary wireless baggage tracker. The temporary wireless baggage tracker may be reused for other baggage items.

[0335] This process may eliminate the need for printed valet tags, instead using temporary wireless trackers as a replacement for valet tags.

[0336] In some embodiments, digital images of baggage items combined with digital geolocation data and passenger name data on passenger identification linked to a PNR can be used as an alternative to printed valet tags.

[0337] In some embodiments, the processes disclosed herein allow for the check-in process of a baggage item to begin before a regulated check-in window.

[0338] In view of the above, this embodiment provides a method including: receiving, by a first processor, a passenger name record (PNR) from a confirmed itinerary for an airline, wherein the confirmed itinerary is created by a computer system associated with an airline; receiving, by the first processor, information confirming the identity of a passenger associated with the PNR from the confirmed itinerary; picking up baggage associated with the PNR from the passenger's location and transporting it to a predetermined location; and generating, by a second processor in communication with the first processor, a simulated baggage source message (BSM) using the received PNR, wherein the second processor is independent of the airline, and the BSM is compatible with an International Air Transport Association (IATA) B-type message.

[0339] For purposes of explanation and example, a BSM message will be described, although any B-type message containing relevant passenger information accessible using the IATA baggage tag number can be used.

[0340] In view of the above, the present embodiment provides a system 1800 and method for checking in baggage items, including a first processor that receives a passenger name record (PNR) for a confirmed airline itinerary. The confirmed itinerary is created, for example, by a computer system associated with an airline carrier. The first processor receives information from the confirmed itinerary that identifies the passenger associated with the PNR and picks up and transports baggage associated with the PNR from the passenger's location to a processing location (i.e., a baggage storage location). The system 1800 and method employ a second processor in communication with the first processor that generates a simulated baggage source message (SBSM) using the temporary unique identifier 1630. The second processor is independent of the airline carrier's computer system. The simulated BSM is compatible with International Air Transport Association (IATA) B-type messages.

[0341] The system 1800 and method may use a second processor to generate an origin IATA license plate for each baggage item associated with the PNR.

[0342] The system 1800 and method may update the simulated BSM with the generated IATA license plate using a second processor, which may communicate the updated BSM to a computer system associated with the airline.

[0343] The system 1800 and method may use a first processor to receive information verifying the identity of the passenger, which may include capturing an image of an identification card issued to the passenger using an imaging device in communication with the first processor.

[0344] The system 1800 and method may employ an imaging device in communication with the first processor to capture an image of each baggage item associated with the PNR prior to departure from the passenger location.

[0345] The simulated BSM may include information related to arrival and departure airports and dates.

[0346] The system 1800 and method may include a server or processor for checking in passenger baggage and integrating the airline's BSM with the simulated BMS.

[0347] The system 1800 and method may include a printing device for printing an IATA baggage tag at the origin. The system and method may employ a communication device for communicating the 10-digit IATA baggage tag number to the passenger's mobile communication device.

[0348] The system 1800 and method may provision 10-digit IATA baggage tag numbers as universal baggage tag numbers, which are recycled at off-airport facilities.

[0349] The system 1800 and method may include a temporary, reassignable baggage tracker that can be temporarily associated with a baggage item so that when the flight's IATA printing check-in window opens, the baggage tracker can be pinged to locate the baggage. After printing the departure IATA baggage tag and locating the baggage, the baggage tracker can be removed and then reassigned for another baggage item.

[0350] Although this discussion describes the creation of a BSM, it also applies to the creation of any other B-type message used outside of an airline environment and its baggage handling system, such as a Baggage Transfer Message (BTM), Baggage Source Message (BSM), Baggage Processing Message (BPM), Baggage Drop Message (BUM), Baggage Not Confirmed Message (BNS), Baggage Control Message (BCM), Baggage Manifest Message (BMM), Baggage Request (BRQ), etc. The baggage tag number may be part of the baggage message.

[0351] For example, a computing device may access the extended B-type message and create a BUM if a delivery service is scheduled to pick up a baggage at a destination but the baggage location does not exist, such as when a baggage is lost from a train station or bus terminal.

[0352] In some embodiments, the method may include electronically receiving lodging reservation data associated with accommodations and an itinerary for at least one passenger for at least one mode of transportation including an air travel mode with an outbound airline mobile carrier. The method may include generating, by server 1310, a universal baggage source message (BSM) for multi-modal travel. The universal BSM includes a set of data fields related to the airline travel mode and the lodging reservation, which are linked by a digital unique identifier representing an origin (outbound flight) hard-copy baggage tag identifier (OP-BTI) associated with or printed on a printed baggage tag affixed to the passenger's baggage at the outbound airline mobile carrier. The method may include recycling the printed baggage tag and the OP-BTI using the universal BSM to check in the passenger's baggage items for a return flight associated with the at least one passenger's itinerary.

[0353] The method may include, in response to the capture device capturing the recycled printed baggage tag, provisioning the recycled printed baggage tag at an off-airport facility as a locator for locating the baggage until a new printed baggage tag is generated for the return flight. This may be accomplished, for example, by establishing a database 1308 to keep the OP-BTI valid after the departure flight. The machine-readability of the OP-BTI allows it to be repeatedly scanned or read by anyone needing to obtain updated travel information, such as lodging information or other transportation options, solely for the purposes of tracking, locating, or obtaining updated information.

[0354] According to some embodiments, generating database 1308 containing a universal BSM such as that shown in FIG. 14 may include obtaining a digital data record representing the OP-BTI by accessing the departing airline's travel carrier's airline BSM 1200A (see FIG. 12A) while the passenger is en route. This allows for very rapid expansion of the airline's BSM with OP-BTI, which is useful when thousands of passengers are soon arriving to board a cruise ship or resort. Performing the expansion process more quickly for some passengers minimizes overloading employees with processing subsequent passengers. The expanded airline BSM includes a set of data fields that link messaging system 1390 with updated lodging reservation data. Server 1310 stores the expanded BSM in database 1308 as a universal multi-travel and lodging BSM.

[0355] Although this description discloses an extended BSM, this disclosure also relates to extended B-type messages that contain information specific to passengers and their baggage.

[0356] The Airline BSM 1200A (FIG. 12A) includes a set of data fields. These fields include at least a baggage tag data field (i.e., field 1212) that includes a series of numbers representing the OP-BTI. This series of numbers may include the number of checked-in baggage items. These fields may include a passenger name data field that includes the passenger name, and a passenger name record (PNR) data field (i.e., field 1218).

[0357] In some embodiments, extending the Airline BSM may include recycling the OP-BTI data field (i.e., field 1212), the passenger name data field, and the PNR data field (i.e., field 1218) from the set of data fields to create a Lite Airline BSM 1200A' (FIG. 14A). Fields from the Lite Airline BSM are added to the extended BSM. In some embodiments, all fields from the origin (original) Airline BSM are retained and added to the extended BSM.

[0358] In some embodiments, extending the airline BSM may include adding, by server 1310, to the lite airline BSM 1200A', a link to lodging reservation data associated with the passenger in accommodation field 1430. However, in some embodiments, instead of a link to data, data field 1430 may include data representing an assigned room or cabin number. Data field 1430 may include at least one data field. For example, the accommodation data field may include geolocation data or an address of the accommodation.

[0359] In some embodiments, extending the airline BSM may include adding, by server 1310, a link to travel mode booking data for a second travel mode different from the air travel mode in field 1420 to the light airline BSM. However, in some embodiments, instead of a link to data, data field 1420 may include data representing a train station or gate, date, and departure time. Data field 1420 may include at least one data field. For example, a transportation mode data field may include geolocation data or a station address.

[0360] In some embodiments, extending the airline BSM may include at least any of the following: a) linking data to at least one stored image of the baggage item (such as baggage image 1330 in database 1308) to the lite airline BSM in field 1440; b) linking data to location data of the baggage item in field 1460 in response to acquisition of the OP-BTI by the acquisition device; and c) linking data to an identification image of the passenger, such as in database 1308 for passenger ID image 1335 (FIG. 13), to the lite airline BSM in field 1450. Baggage location data log 1325 may be stored in database 1308.

[0361] The messaging system 1390 may be used to generate messages to the capture device in response to the capture device acquiring the OP-BTI. The capture device transmits an image of the OP-BTI, which creates a digital BTI data record, and queries information from the database 1308. The messaging system may provide updated information to the capture device to direct the baggage item to its next location in the travel experience.

[0362] 12B and 14A, the method may further include creating a simulated BSM 1200B, checking in the baggage using the simulated BSM, and creating an OP-BTI. The method may include printing, by a printing device 1340, a printed baggage tag 142′ with the new OP-BTI for the return flight.

[0363] The method may include, by the server 1310, the passenger accessing the airline BSM 1200A with the PNR before arrival at the destination. The method may include, by the server 1310, retrieving an OP-BTI associated with the PNR in the airline BSM 1200A, and retrieving, by the server 1310, return flight data linked to the PNR and / or the OP-BTI.

[0364] The method may include creating, by the server 1310, a lite airline BSM 1200A' and generating, by the server 1310, a simulated BSM including the return flight data. The method may include generating, by the server 1310, a universal BSM (i.e., universal B-type message 1400A) that concatenates and appends the lite airline BSM 1200A' and the simulated BSM 1200B.

[0365] The method may include electronically capturing, by a capturing device, the OP-BTI on the recycled printed baggage tag; logging, by the capturing device, an instance and location associated with the OP-BTI affixed to the read baggage item in a baggage location data log 1325 of the database 1308; and adding a link to information representing the logged instance and location to the universal BSM 1400A.

[0366] The method may include linking accommodation reservation data to the universal BSM 1400A; receiving updated assigned accommodation reservation data; and communicating the updated assigned accommodation reservation data to at least one of a mobile communication device, a computing device, or a scanning device via a messaging system 1390 in response to the acquisition device reading the recycled printed baggage tag at the off-airport location.

[0367] The method may include electronically acquiring, by a capturing device, an origin hardcopy baggage tag identifier (OP-BTI) on a recycled printed baggage tag affixed to the baggage; querying, by a server 1310, a database (itinerary 1314) for an assigned cabin associated with a digital data record of the OP-BTI in the universal BSM in response to receiving the acquired OP-BTI; and, in response to the query, causing a display device of the capturing device to display information associated with the assigned cabin, as shown in FIG. 3B.

[0368] The method may include: using the OP-BTI as a machine-readable unique identifier, by at least one processor, querying database 1308 or system 108 to obtain return flight data for the passenger departing from the accommodation; and checking in, by the at least one processor, each baggage item of the departing passenger for the return flight with a travel carrier for the return flight identified in the obtained return flight data.

[0369] The method may include causing at least one processor to create a new OP-BTI including return flight data, a passenger name, and a passenger name record; and printing, by a printing device 1340, a new baggage tag 1350 having the new OP-BTI for the return flight.

[0370] The method may include generating, by the server 1310, a simulated BSM 1200B for the outbound flight including return flight data, passenger names, and passenger name records; assigning a new OP-BTI to the return flight baggage; and registering a new digital BTI record representing the assigned OP-BTI in the simulated BSM.

[0371] Systems 1300 and 1800 may include a remote simulated departure control system (DCS) in communication with server 1310 or 1826 that can assign IATA-compatible baggage tags that can be processed by traditional airline baggage handling systems for non-flying airline carriers with unique IATA-assigned airline codes. The assigned OP-BTIs are assigned by remote server 1826 in communication with the simulated DCS. Universal B-type messages can be created for all IATA B-type messages.

[0372] The "step-by-step process" for performing the functions claimed herein is a particular algorithm, which may be represented mathematically in the body of the specification as text and / or as flow charts. Software program instructions configure special-purpose machines for performing the particular algorithm. Thus, in means-plus-function claims herein where the disclosed structure is a computer or microprocessor programmed to execute an algorithm, the disclosed structure is not a general-purpose computer, but rather a special-purpose computer programmed to execute the disclosed algorithm.

[0373] A general-purpose computer or microprocessor can be programmed to execute algorithms / steps to create a new machine. A general-purpose computer becomes a special-purpose computer when programmed to perform specific functions according to instructions from the program software of the embodiments described herein. The software program's instructions to execute the algorithms / steps electrically modify the general-purpose computer by creating electrical pathways within the device. These electrical pathways create a special-purpose machine for performing the specific algorithms / steps.

[0374] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by a person skilled in the art to which the present embodiment belongs. Furthermore, terms defined in commonly used dictionaries should be interpreted as meanings consistent with the meanings in the context of the relevant technical field, and unless explicitly defined in this specification, should not be interpreted in an idealized or overly formal sense.

[0375] In particular, unless otherwise specified as is clear from the description, discussions throughout this specification using terms such as "processing," "computing," "calculating," "determining," and "displaying" will be understood to refer to acts and processes by which a computer system or similar electronic computing device manipulates and transforms data represented as physical (electronic) quantities in its registers or memory, and converts it into other data represented as similar physical quantities in the computer system's memory, registers, or other data storage, transmission, or display device.

[0376] "Communication media" typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal (including carrier waves or other transport mechanisms). Communication media may include any information delivery media. A "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media (such as a wired network or direct-wired connection) and wireless media (such as acoustic, infrared, and other wireless media). Combinations of any of the above are also included within the scope of computer-readable media.

[0377] Alternatively or additionally, any of the functions and programming modules disclosed herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products, system-on-a-chip systems, complex programmable logic devices, etc.

[0378] As used herein, the terms "module" and "component" generally refer to software, firmware, hardware, or a combination thereof. In a software implementation, a module or component represents program code that performs specific tasks when executed on a processor. The program code may be stored in one or more computer-readable memory devices, also referred to as non-transitory devices. Features of the embodiments disclosed herein are platform-independent; that is, these techniques can be implemented on a variety of commercial computing platforms with a variety of processors (e.g., set-top boxes, desktops, laptops, notebooks, tablet computers, personal digital assistants (PDAs), mobile phones, smartphones, game consoles, wearable devices, Internet of Things (IoT) devices, etc.).

[0379] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. Furthermore, to the extent that the terms "comprise," "including," "have," "have," "having," or variations thereof are used in the detailed description and / or claims, these terms are intended to be used in the same inclusive sense as the term "comprise." Additionally, unless otherwise specified, the use of terms such as "first," "second," etc., does not denote any order or importance, but rather is used merely to distinguish one element from another.

[0380] While various disclosed embodiments have been described above, it should be understood that these are illustrative and not limiting. Numerous modifications, omissions, and / or additions may be made to the subject matter disclosed herein in accordance with the embodiments disclosed herein without departing from the spirit or scope thereof. Elements may also be substituted with equivalents without departing from the spirit and scope of the embodiments. Furthermore, even if a particular feature is disclosed only with respect to one of multiple embodiments, that feature may be used in combination with one or more of the other features of the other embodiments, if desired or advantageous in any particular application. Furthermore, many modifications may be made to adapt a particular situation or material to the teachings of the embodiments without departing from their scope.

[0381] Moreover, the purpose of the foregoing Abstract is to enable the U.S. Patent and Trademark Office and the general public, particularly scientists, engineers, and practitioners in the relevant art who may not be familiar with patent and legal terminology, to quickly assess the nature and substance of the present technical disclosure at a glance. The Abstract is not intended to limit the scope of the present disclosure in any way.

[0382] Thus, the scope and breadth of the subject matter described herein should not be limited by any of the explicitly described embodiments above. Rather, the scope of the embodiments should be defined in accordance with the following claims and their equivalents.

[0383] Computer and Software Technology

[0384] The present invention may be embodied on a variety of platforms. The following provides a preliminary foundation of information technology that may be utilized to implement the present invention.

[0385] Embodiments of the present invention may be implemented in hardware, firmware, software, or any combination thereof. Embodiments of the present invention may also be implemented as instructions stored on a machine-readable medium, which may be read and executed by one or more processors. A machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computing device). For example, machine-readable media include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, electrical, optical, acoustical, or other propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.), and the like.

[0386] Furthermore, firmware, software, routines, or instructions may be described herein as performing particular operations, however, it should be understood that such description is for convenience only and that in reality, such operations are caused by computing devices, processors, controllers, or other devices executing the firmware, software, routines, instructions, etc.

[0387] Machine-readable media include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, devices, or any suitable combination of the foregoing. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection having one or more conductors, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this document, computer-readable storage media means a non-transitory, tangible medium capable of holding or storing a program used by or in connection with an instruction execution system, apparatus, or device. Virtual servers, storage, and services can reside on-premise or in a remote environment such as the "cloud" (through vendors operating under brand names such as MICROSOFT AZURE, AMAZON WEB SERVICES, RACKSPACE, KAMATERA, etc.).

[0388] A machine-readable signal medium may include a propagated data signal in which machine-readable program code is embodied, for example, as part of a baseband or carrier wave. Such a propagated signal may take various forms, including, but not limited to, electromagnetic, optical, or any suitable combination thereof. A machine-readable signal medium is not a computer-readable storage medium, but is any machine-readable medium that can convey, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. However, due to the statutory subject matter scope limitations on circuits, as noted above, claims of the invention as a software product may be embodied on a non-transitory software medium, such as a computer hard drive, flash RAM, or optical disk.

[0389] Program code embodied in a machine-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, fiber optic cable, radio frequency, etc., or any suitable combination of the former. Machine-readable program code for carrying out operations of aspects of the present invention may be written in any combination of object-oriented programming languages ​​such as Java, C#, C++, Visual Basic, etc., and conventional procedural programming languages ​​such as the "C" programming language. Additional languages ​​may include scripting languages ​​such as PYTHON, LUA, PERL, etc.

[0390] Embodiments of the present invention are described below with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by machine-readable program instructions.

[0391] Claims Glossary

[0392] Airline Mobile Carrier means a company that provides air transportation services for passengers and / or cargo.

[0393] BTI stands for "Baggage Tag Identifier." A baggage tag identifier (also called a baggage tag or baggage label) is a small tag or label affixed to a passenger's baggage that contains identifying information about the passenger and their flight. It is used by airlines to track and handle the passenger's checked-in baggage. The tag typically includes the passenger's name, flight information (flight number, departure and arrival airports, and travel date), and a unique identifier such as a baggage tag number or barcode. The baggage tag identification number is unique to each piece of baggage and is used by airlines as a reference for tracking the baggage through their baggage handling systems, linking the baggage to the passenger's flight and routing, and identifying the owner of the baggage in the event of loss or delay. The baggage tag identification number is typically issued at check-in and attached to the passenger's baggage before dropping it off at the baggage drop counter.

[0394] A database is an organized collection of data that is stored, updated, and accessed electronically. Databases are typically designed to hold data, facilitate efficient retrieval and manipulation of data, and manage how data is stored and retrieved.

[0395] First Mode Mobile Carrier (FMTC) refers to the first carrier to affix a tangible, machine-readable indicium to a passenger's baggage, which, in accordance with the present invention, is used to look up the passenger's PNR and build a passenger manifest for one or more return flights without manual data re-entry.

[0396] The International Air Transport Association (IATA) is a trade association of airlines (both cargo and passenger carriers) worldwide that regulates the airline industry, establishing standards, procedures, and practices.

[0397] A license plate refers to the 10-digit numeric code on a baggage tag issued by a carrier to an agent upon check-in for a travel itinerary. In this context, "license plate" is the official term used by IATA. The license plate is encoded in a machine-readable barcode, but is also presented in a human-readable format and includes a two- or three-digit IATA carrier code. For example, "CZ728359" or "784728359." "CZ" is the two-letter IATA code for China Southern Airlines, and "784" is the three-digit IATA airline code. For American Airlines®, the IATA designator is "AA" and the IATA code is "001."

[0398] Accommodation refers to a business or operation that provides lodging services, including, but not limited to, hotels, resorts, and cruise ships.

[0399] Multimodal travel refers to the functional co-use of Type B and IATA messages, extending their use all the way to the accommodation. The IATA message name, PNR number, and slip of paper become the baggage tag for the entire journey and all modes of transportation.

[0400] Origin Hardcopy Baggage Tag Identifier (OP-BTI) refers to a unique identifier associated with or printed on a baggage tag issued by the departing airline carrier. Typically, each piece of baggage in an air journey is given a unique identifier for tracking purposes. This is usually affixed to the baggage at check-in and scanned at various points throughout the journey to ensure the baggage reaches the correct destination.

[0401] Passenger manifest means a record containing an array of data containing data for check-in of a passenger's return travel leg with a designated return travel carrier.

[0402] PNR is an abbreviation for "Passenger Name Record." It is a record in an airline or travel agency's database that contains all details of a passenger's itinerary and travel information. This information includes the passenger's name, contact information, flight details, seat assignment, and any special requests. The PNR also contains reservation information such as booking date, fare, and ticketing status. Airlines and travel agencies use it to manage and track passenger itineraries and travel plans. PNR numbers are unique to each passenger and are used as a reference for passengers, airlines, and travel agencies. PNRs are also used to check in, check flight status, and make reservation changes. The PNR number itself is usually six characters long and often a combination of letters and numbers. Although regulatory bodies such as IATA (see above) do not prescribe a universal format for PNRs, each PNR contains five required elements: (1) the traveler's or agent's telephone number; (2) the person who last made a change to the PNR; (3) the itinerary (which must include at least one segment of the itinerary); (4) the passenger's name (including the full first and last name); and (5) an indication of how and when the ticket was issued.

[0403] Radio frequency identification (RFID) refers to a technology that uses electromagnetic fields to automatically identify and track tags attached to objects.

[0404] A Return Transfer Carrier (RTC) refers to the carrier (e.g., airline) that a passenger will use upon completion of their stay at a lodging facility. The RTC, in this context, is extracted during the process of creating a return passenger manifest by accessing the passenger's PNR using the license plate printed by the FMTC. This reduces or eliminates data entry work, particularly at lodging facilities where passengers are checked in for the RTC.

[0405] Type B (or B-type) messages refer to a specific communication format used by airlines and other operators in the aviation industry to send and receive critical operational data. These messages are standardized and are used for a wide range of purposes, including flight planning, passenger reservations and check-in, baggage tracking, weather updates, and other critical air transport operations. The Type B messaging standard is maintained by the International Air Transport Association (IATA). Compared to more modern data types and formats, such as XML (Extensible Markup Language) and JSON (JavaScript Object Notation), which carry message payloads, Type B messages have a rigid structure. Type B messages operate on a "store-and-forward" mechanism, whereby the sender transmits data via a service provider, which stores the data for a contracted period (usually seven days). The data is delivered to the intended recipient directly or via a gateway provider if the recipient resides on a different network. Retransmission is possible in the event of a delivery failure, as contracted, and this contingency is reflected in the PDM (Possible Duplicate Message) header.

[0406] The advantages listed above and those apparent from the foregoing description are efficiently attained. Because certain changes may be made in the above construction without departing from the scope of the invention, it is intended that all matter contained in the above description and shown in the accompanying drawings be interpreted as illustrative and not in a limiting sense.

Claims

1. 1. A method comprising: receiving, by a first processor, a passenger name record (PNR) number for a confirmed itinerary for the flight created by a computer system associated with the air carrier; receiving, by the first processor, information from the confirmed itinerary confirming the identity of the passenger associated with the PNR number, and picking up baggage items associated with the passenger from a passenger location and transporting them to a storage location; and generating, by a second processor in communication with the first processor, a simulated baggage source message (SBSM) compatible with an International Air Transport Association (IATA) B-type message using the PNR number as a temporary unique identifier for the baggage item; method.

2. The method of claim 1, further comprising: generating, by the second processor, an outbound IATA license plate for the baggage item; method.

3. 3. The method of claim 2, wherein the second processor is independent of the computer system associated with the airline carrier, and further comprises: updating, by the second processor, the SBSM with the created IATA license plate; and transmitting the updated SBSM to the computer system associated with the air carrier; method.

4. 10. The method of claim 1, wherein receiving the information confirming the identity of the passenger by the first processor includes: capturing, by an imaging device in communication with the first processor, an image of an identification card issued to the passenger; method.

5. The method of claim 4, further comprising: capturing an image of the baggage item by the imaging device in communication with the first processor before the baggage item is transported from the passenger location; method.

6. 10. The method of claim 1, wherein the SBSM includes information associated with arriving and departing flights. method.

7. The method of claim 1, further comprising: checking in the baggage item of the passenger and integrating an airline's BSM with the SBMS for the baggage item; method.

8. 10. The method of claim 7, further comprising: printing an IATA compatible baggage tag and communicating the IATA baggage tag number to said passenger's mobile communication device; method.

9. 9. The method of claim 8, wherein the IATA baggage tag number is provisioned as a universal baggage tag number. method.

10. 10. The method of claim 8, further comprising: attaching a temporary baggage tracker to the baggage item; and After printing the IATA baggage tag, locating the baggage item using the baggage tracker and attaching the IATA baggage tag to the baggage item; method.

11. 10. The method of claim 1, wherein the SBSM is created outside a regulated airline check-in window. method.

12. 1. A method comprising: receiving, by a first processor, a passenger name record (PNR) number for a confirmed itinerary for the flight created by a computer system associated with the air carrier; receiving, by the first processor, information from the confirmed itinerary confirming the identity of the passenger associated with the PNR number, and picking up a baggage item associated with the passenger from a first location and transporting it to a second location; generating, by at least one second processor in communication with the first processor, a simulated baggage source message (SBSM) using the temporary unique identifier and information from the confirmed itinerary; causing at least one of the at least one second processor to generate an IATA license plate for the baggage item; and updating, by at least one of the at least one second processor, the SBSM with the created IATA license plate; method.

13. 13. The method of claim 12, wherein the first location is a passenger designated location and the second location is a baggage handling location. method.

14. 13. The method of claim 12, further comprising: transmitting the updated SBSM to a computer system associated with the air carrier; method.

15. 13. The method of claim 12, further comprising: attaching a temporary baggage tracker to the baggage item; and Locating the baggage item using the baggage tracker and attaching a printed IATA baggage tag to the baggage item; method.

16. 13. The method of claim 12, wherein the SBSM is created outside a regulated airline check-in window. method.

17. 1. A method comprising: generating, by at least one processor, a simulated baggage source message (SBSM) using the temporary unique identifier for the passenger's baggage item and information from the confirmed itinerary; integrating, by the at least one processor, an airline baggage source message with the SBSM after check-in of the passenger's baggage item; causing the at least one processor to print an International Air Transport Association (IATA) compatible baggage tag having an IATA license plate number; and provisioning, by the at least one processor, the IATA license plate number into a universal baggage tag number for tracking multi-modal movement of the baggage item; method.

18. 18. The method of claim 17, further comprising: attaching a baggage tracker to the baggage item; and locating the baggage item using the baggage tracker; method.

19. 18. The method of claim 17, wherein the confirmed itinerary information includes data representing arriving and departing flights. method.

20. 1. A system comprising: a first processor configured to receive a passenger name record (PNR) number of a confirmed itinerary for a flight created by a computer system associated with an air carrier, the first processor further configured to receive information from the confirmed itinerary confirming the identity of a passenger associated with the PNR number, pick up a baggage item associated with the passenger from a passenger location, and transport the baggage item to a storage location; and a second processor in communication with the first processor, the second processor configured to generate a Simulated Baggage Source Message (SBSM) using the PNR number as a temporary unique identifier for the baggage item, wherein the SBSM is compatible with an International Air Transport Association (IATA) B-type message; system.

21. 21. The system of claim 20, wherein the second processor is further configured to generate an outbound IATA license plate for the baggage item. system.

22. 22. The system of claim 21, wherein the second processor is independent of the computer system associated with the airline carrier; and further configured to update the SBSM with the created IATA license plate and communicate the updated SBSM to the computer system associated with the air carrier. system.

23. 21. The system of claim 20, wherein the first processor is further configured to receive the information confirming the identity of the passenger; and further comprising an imaging device in communication with the first processor and configured to capture an image of an identification card issued to the passenger. system.

24. 24. The system of claim 23, wherein the imaging device in communication with the first processor is further configured to capture an image of the baggage item. system.

25. 21. The system of claim 20, wherein the SBSM includes information associated with arriving and departing flights. system.

26. 21. The system of claim 20, wherein the second processor is further configured to check in the baggage item of the passenger and integrate an airline's Baggage Source Message (BSM) with the SBSM for the baggage item. system.

27. 27. The system of claim 26, wherein the second processor is further configured to cause a printing device to print an IATA-compatible baggage tag and to communicate an IATA baggage tag number to the passenger's mobile communication device. system.

28. 28. The system of claim 27, wherein the IATA baggage tag number is provisioned as a universal baggage tag number. system.

29. 28. The system of claim 27, wherein the second processor is further configured to locate the baggage item using a baggage tracker and attach the IATA baggage tag to the baggage item. system.

30. 21. The system of claim 20, wherein the SBSM is created outside of a regulated airline check-in window. system.

31. 1. A system comprising: a first processor that receives a passenger name record (PNR) number of a confirmed itinerary for a flight created by a computer system associated with an air carrier, receives information from the confirmed itinerary confirming the identity of a passenger associated with the PNR number, and picks up and transports a baggage item associated with the passenger from a first location to a second location; and at least one second processor in communication with the first processor, the second processor generating a simulated baggage source message (SBSM) using the temporary unique identifier and information from the confirmed itinerary, causing an International Air Transport Association (IATA) license plate for the baggage item to be created, and updating the SBSM with the created IATA license plate; system.

32. 32. The system of claim 31, wherein the first location is a passenger designated location and the second location is a baggage handling location. system.

33. 32. The system of claim 31, further comprising: transmitting the updated SBSM to the computer system associated with the air carrier; system.

34. 32. The system of claim 31, wherein the at least one second processor is further configured to locate the baggage item using the baggage tracker and attach a printed IATA baggage tag to the baggage item. system.

35. 32. The system of claim 31, wherein the SBSM is created outside a regulated airline check-in window. system.

36. 1. A system comprising: at least one processor; and a memory for storing instructions; The instructions, when executed by the at least one processor, are configured to cause the at least one processor to perform the following operations: generating a simulated baggage source message (SBSM) using the temporary unique identifier for the passenger's baggage item and information from the confirmed itinerary; integrating an airline baggage source message with the SBSM after checking in the baggage item of the passenger; Printing an International Air Transport Association (IATA) compatible baggage tag bearing an IATA license plate number; and provisioning the IATA license plate number to a universal baggage tag number for tracking multi-modal movement of the baggage item; system.

37. 1. A method comprising: electronically capturing, by at least one electronic capturing device, an origin hard copy baggage tag identifier (OP-BTI) associated with or printed on the origin mobile carrier's printed baggage tag affixed to the passenger's baggage item; querying, by at least one processor, a database having at least one extended type B message using the OP-BTI as a unique identifier, wherein the extended type B message lists travel routes for the passenger by a mode of travel different from the origin mobile carrier; and checking in, by the at least one processor, each baggage item of the passenger for the travel route of the passenger using information from the at least one extended B-type message; method.

38. 38. The method of claim 37, wherein the travel route is to an accommodation. method.

39. 39. The method of claim 38, wherein the accommodation comprises any one of a hotel, a resort, a cruise ship, a short-term rental homestay, a long-term rental homestay, a house, and a building. method.

40. 38. The method of claim 37, wherein the OP-BTI associated with the origin mobile carrier attached to the baggage item of the passenger is obtained from radio frequency communications. method.

41. 38. The method of claim 37, wherein electronically capturing by the at least one electronic capturing device includes any of the following: scanning the OP-BTI on the origin airline mobile carrier's printed paper baggage tag attached to the baggage item with a bar code scanner; scanning the OP-BTI on the origin airline mobile carrier's printed marker affixed to the baggage item with a bar code scanner; receiving, by a radio frequency identification (RFID) reader, RFID information associated with the OP-BTI; or receiving, by a near field communication (NFC) reader, an NFC signal associated with the OP-BTI; method.

42. 38. The method of claim 37, wherein the OP-BTI includes an International Air Transport Association (IATA) license plate number. method.

43. 38. The method of claim 37, wherein the at least one extended type B message listing the passenger's travel route includes an International Air Transport Association (IATA) baggage tag number, a passenger name, and a passenger name record (PNR). method.

44. 38. The method of claim 37, further comprising: entering, by the server, a record into a database for said extended type B message data field for each transportation mode in said passenger's itinerary, wherein said extended type B message identifies each transportation mode and accommodation reservation linked by said unique identifier; method.

45. 38. The method of claim 37, further comprising: causing, by the at least one processor, a printing device to print an International Air Transport Association (IATA) format compliant baggage tag for the travel route; method.

46. 38. The method of claim 37, further comprising: receiving updated booking information for said passenger; updating the corresponding passenger itinerary linked to the at least one extended B-type message for the passenger in the database; and triggering communication of the updated subscription information to a computing device in response to obtaining the OP-BTI; method.

47. 38. The method of claim 37, wherein the origin mobile carrier is an air carrier. method.

48. 38. The method of claim 37, further comprising the steps of: adding, by said at least one processor, additional fields to at least one extended B-type message in response to check-in of each baggage item of said passenger; method.

49. 49. The method of claim 48, wherein the added additional fields include one or more of a location identification, a date, and a time. method.

50. 38. The method of claim 37, wherein the at least one extended B-type message includes a header field designating it as universal. method.

51. 38. The method of claim 37, further comprising the steps of: updating a baggage tag number field in the at least one extended B-type message for any newly issued International Air Transport Association (IATA) baggage tags for the travel route; method.

52. 38. The method of claim 37, wherein the at least one extended B-type message includes access to or links to at least one or more of data records referencing a departure flight, an intermediate transfer reservation, an accommodation reservation, an airline return flight, a baggage location, a baggage image, and a passenger identification image. method.

53. 1. A method comprising: electronically capturing, by at least one electronic capture device, an Origin Carrier Hardcopy Baggage Tag Identifier (OP-BTI) associated with or printed on an Origin Carrier printed baggage tag affixed to the passenger's baggage item booked on the return flight, and creating a Digital Baggage Tag Identifier (BTI) data record linked to said Origin Carrier; querying, by at least one processor, a database using the OP-BTI as a unique identifier to obtain return flight data for the passenger; and checking in, by the at least one processor, each baggage item of the passenger for a return flight of a return mobile carrier identified in the obtained return flight data; method.

54. 54. The method of claim 53, wherein the passenger departs from a lodging facility. method.

55. 55. The method of claim 54, wherein the accommodation comprises any one of a hotel, a resort, a cruise ship, a short-term rental homestay, a long-term rental homestay, a house, and a building. method.

56. 54. The method of claim 53, wherein the OP-BTI associated with the origin airline mobile carrier affixed to the passenger's baggage item is obtained from radio frequency communications. method.

57. 54. The method of claim 53, wherein electronically capturing by the at least one electronic capturing device includes any of the following: scanning, with a barcode scanner, the OP-BTI on the origin airline mobile carrier's printed paper baggage tag affixed to the baggage item; scanning the P-BTI on the origin airline mobile carrier printed marker affixed to the baggage item with the bar code scanner; receiving, by a radio frequency identification (RFID) reader, RFID information associated with the OP-BTI; or receiving, by a near field communication (NFC) reader, an NFC signal associated with the OP-BTI; method.

58. 54. The method of claim 53, wherein the OP-BTI includes an International Air Transport Association (IATA) license plate number. method.

59. 54. The method of claim 53, wherein querying the database to obtain the return flight data for the passenger using the OP-BTI as a unique identifier by the at least one processor includes accessing a B-type message of the origin airline mobile carrier using the digital BTI data record; wherein the B-type message includes an International Air Transport Association (IATA) license plate number and a passenger name record (PNR) number; method.

60. 60. The method of claim 59, wherein the database is an integral component of the origin airline mobile carrier's travel information system. method.

61. 60. The method of claim 59, wherein the B-type message comprises either a Baggage Transfer Message (BTM) or a Baggage Source Message (BSM). method.

62. 54. The method of claim 53, further comprising: entering, by the server, a record into the database containing a universal B-type message for multi-modal travel, wherein the universal B-type message includes a set of data fields for each mode of transportation in at least one passenger itinerary and identifies multi-modal travel and accommodation reservations linked by the unique identifier; method.

63. 63. The method of claim 62, wherein the unique identifier is a machine-readable OP-BTI. method.

64. 63. The method of claim 62, wherein querying the database to obtain the return flight data for the passenger using the OP-BTI as the unique identifier by the at least one processor includes accessing the universal B-type message using the digital BTI data record. method.

65. 54. The method of claim 53, wherein the database is queried by at least a substring of the integer string that constitutes the OP-BTI. method.

66. 54. The method of claim 53, further comprising: causing, by the at least one processor, a printing device to print, for the return flight, a return flight baggage tag conforming to an International Air Transport Association (IATA) format; method.

67. 54. The method of claim 53, wherein the database stores a manifest. method.

68. 54. The method of claim 53, further comprising: triggering, by the at least one processor, in response to obtaining the OP-BTI, check-in with a mobile carrier on the return flight for each baggage item of the passenger on the return flight; method.

69. 69. The method of claim 68, further comprising: generating, by a server, a simulated airline B-type message having said return flight data, passenger name, and passenger name record number; queuing, by the server, the simulated airline B-type message; and merging the simulated airline B-type message with a carrier B-type message of the return travel carrier during a check-in window; method.

70. 70. The method of claim 69, further comprising: assigning a new OP-BTI to each baggage item on the return flight; and entering a new digital BTI record representing the assigned OP-BTI into the simulated airline B-type message; method.

71. 54. The method of claim 53, wherein querying the database to obtain the return flight data for the passenger using the OP-BTI as a unique identifier, by the at least one processor, further comprises using the digital BTI data record to access a passenger name record (PNR) stored by an information system of the origin airline mobile carrier. method.

72. 54. The method of claim 53, further comprising: receiving updated booking information for said passenger; updating the corresponding passenger itinerary linked to the passenger's extended type B message in the database; and triggering communication of the updated subscription information to a computing device in response to obtaining the OP-BTI; method.

73. 1. A system comprising: at least one processor; and at least one non-transitory, tangible memory communicatively coupled to the at least one processor and storing at least one instruction; The at least one processor is configured to execute the at least one instruction to: electronically acquiring, from an electronic acquisition device, an Origin Carrier Hardcopy Baggage Tag Identifier (OP-BTI) associated with or printed on an Origin Carrier printed baggage tag affixed to a passenger's baggage item booked for the return flight, to create a Digital Baggage Tag Identifier (BTI) data record linked to said Origin Carrier; querying a database to obtain return flight data for the passenger using the OP-BTI as a unique identifier; and checking in each baggage item of the passenger for the return flight with a return flight mobile carrier identified in the obtained return flight data; system.

74. 74. The system of claim 73, wherein the passenger is departing from a lodging facility. system.

75. 75. The system of claim 74, wherein the accommodation comprises any one of a hotel, a resort, a cruise ship, a short-term rental homestay, a long-term rental homestay, a house, and a building. system.

76. 74. The system of claim 73, wherein the OP-BTI associated with the origin airline mobile carrier affixed to the passenger's baggage item is obtained from radio frequency communications. system.

77. 74. The system of claim 73, wherein the electronic acquisition device includes any of the following: a bar code scanner configured to scan the OP-BTI on the origin airline mobile carrier's printed paper baggage tag affixed to the baggage item; a bar code scanner configured to scan the OP-BTI on the origin airline mobile carrier printed marker affixed to the baggage item; a radio frequency identification (RFID) reader configured to receive RFID information associated with the OP-BTI; or a near field communication (NFC) reader configured to receive an NFC signal associated with the OP-BTI; system.

78. 74. The system of claim 73, wherein the OP-BTI includes an International Air Transport Association (IATA) license plate number. system.

79. 74. The system of claim 73, wherein the at least one processor, upon executing the at least one instruction configured to query a database using the OP-BTI as a unique identifier to obtain the return flight data for the passenger, is further configured to execute the at least one instruction to: accessing a B-type message of the origin airline mobile carrier using the digital BTI data record, wherein the B-type message includes an International Air Transport Association (IATA) license plate number and a Passenger Name Record (PNR) number; system.

80. 80. The system of claim 79, wherein the database is an integral component of the origin airline mobile carrier's travel information system. system.

81. 80. The system of claim 79, wherein the B-type message comprises either a Baggage Transfer Message (BTM) or a Baggage Source Message (BSM). system.

82. 74. The system of claim 73, wherein the at least one processor is configured to execute the at least one instruction and further perform the following: entering a record into said database containing a universal B-type message for multi-modal travel, said universal B-type message including a set of data fields for each mode of transportation in at least one passenger itinerary and identifying multi-modal travel and accommodation reservations linked by said unique identifier; system.

83. 83. The system of claim 82, wherein the unique identifier is a machine-readable OP-BTI. system.

84. 83. The system of claim 82, wherein the at least one processor, upon executing the at least one instruction configured to query a database using the OP-BTI as a unique identifier to obtain the return flight data for the passenger, is further configured to execute the at least one instruction to: accessing said universal B-type message using said digital BTI data record; system.

85. 74. The system of claim 73, wherein the database is queried by at least a substring of integer characters that make up the OP-BTI. system.

86. 74. The system of claim 73, wherein the at least one processor is configured to execute the at least one instruction to further perform the following: causing a printing device to print a return flight baggage tag conforming to an International Air Transport Association (IATA) format for said return flight; system.

87. 74. The system of claim 73, wherein the database stores a manifest. system.

88. 74. The system of claim 73, wherein the at least one processor is configured to execute the at least one instruction and further perform the following: responsive to obtaining the OP-BTI, triggering check-in of each baggage item of the passenger for the return flight by the return flight's mobile carrier; system.

89. 90. The system of claim 88, wherein the at least one processor is configured to execute the at least one instruction and further perform the following: generating a simulated airline B-type message having said return flight data, passenger name, and passenger name record; queuing the simulated airline B-type message; and merging the simulated airline B-type message with a carrier B-type message of the return travel carrier during a check-in window; system.

90. 90. The system of claim 88, wherein the at least one processor is configured to execute the at least one instruction and further perform the following: assigning a new OP-BTI to each baggage item on the return flight; and entering a new digital BTI record representing the assigned OP-BTI into the simulated airline B-type message; system.

91. 74. The system of claim 73, wherein the at least one processor, upon executing the at least one instruction configured to query the database using the OP-BTI as the unique identifier to obtain the return flight data for the passenger, is further configured to execute the at least one instruction to: using said digital BTI data record to access a passenger name record (PNR) stored in said origin airline mobile carrier's information system; system.

92. 74. The system of claim 73, wherein the at least one processor is configured to execute the at least one instruction and further perform the following: receiving updated booking information for said passenger; updating the corresponding passenger itinerary linked to the passenger's extended type B message in the database; and triggering communication of the updated subscription information to a computing device in response to obtaining the OP-BTI; system.

93. 74. The system of claim 73, further comprising: an electronic capture device configured to electronically capture the Origin Hardcopy Baggage Tag Identifier (OP-BTI) associated with or printed on the Origin Airline Mobile Carrier's printed baggage tag affixed to the passenger's baggage item booked on the return flight; system.

94. 1. A non-transitory computer-readable medium having stored thereon instructions configured, when executed by at least one processor, to cause the at least one processor to perform the following operations, the operations including the steps of: obtaining, from an electronic capture device, an Origin Carrier-printed or printed baggage tag associated with an Origin Carrier-printed baggage tag affixed to the passenger's baggage item for the return flight, said OP-BTI being utilized to create a Digital Baggage Tag Identifier (BTI) data record linked to said Origin Carrier-printed baggage tag; querying a database using the OP-BTI as a unique identifier to obtain return flight data for the passenger, by at least one processor; and checking, by the at least one processor, each baggage item of the passenger for the return flight with a return flight mobile carrier identified in the obtained return flight data. Non-transitory computer-readable medium.

95. 95. The non-transitory computer-readable medium of claim 94, wherein the passenger departs from a lodging facility. Non-transitory computer-readable medium.

96. 96. The non-transitory computer-readable medium of claim 95, wherein the accommodation comprises any one of a hotel, a resort, a cruise ship, a short-term rental homestay, a long-term rental homestay, a home, and a building. Non-transitory computer-readable medium.

97. 95. The non-transitory computer-readable medium of claim 94, wherein the OP-BTI associated with the origin airline mobile carrier attached to the baggage item of the passenger is obtained from radio frequency communications. Non-transitory computer-readable medium.

98. 95. The non-transitory computer-readable medium of claim 94, wherein the act of capturing the OB-BTI by the electronic capture device includes any of the following: acquiring, with a barcode scanner, the OP-BTI on the origin airline mobile carrier's printed paper baggage tag or the origin airline mobile carrier's printed marker attached to the baggage item; receiving, by a radio frequency identification (RFID) reader, RFID information associated with the OP-BTI; or receiving, by a near field communication (NFC) reader, an NFC signal associated with the OP-BTI; Non-transitory computer-readable medium.

99. 95. The non-transitory computer-readable medium of claim 94, wherein the OP-BTI includes an International Air Transport Association (IATA) license plate number. Non-transitory computer-readable medium.

100. 95. The non-transitory computer-readable medium of claim 94, wherein the act of querying the database using the OP-BTI as the unique identifier to obtain the return flight data for the passenger further comprises: accessing a B-type message of the origin airline mobile carrier using the digital BTI data record; and the B-type message includes an International Air Transport Association (IATA) license plate number and a passenger name record (PNR) number; Non-transitory computer-readable medium.

101. 101. The non-transitory computer-readable medium of claim 100, wherein the database is an integral component of the origin airline mobile carrier's travel information system. Non-transitory computer-readable medium.

102. 101. The non-transitory computer-readable medium of claim 100, wherein the B-type message comprises either a Baggage Transfer Message (BTM) or a Baggage Source Message (BSM). Non-transitory computer-readable medium.

103. 95. The non-transitory computer-readable medium of claim 94, wherein the operations further include: entering, by the at least one processor, a record into the database containing a universal B-type message for multi-modal travel, wherein the universal B-type message includes a set of data fields for each mode of transportation in at least one passenger itinerary and identifies multi-modal travel and accommodation reservations linked by the unique identifier; Non-transitory computer-readable medium.

104. 104. The non-transitory computer-readable medium of claim 103, wherein the unique identifier is a machine-readable OP-BTI. Non-transitory computer-readable medium.

105. 104. The non-transitory computer-readable medium of claim 103, wherein the act of querying the database using the OP-BTI as the unique identifier to obtain the return flight data for the passenger further comprises: accessing said universal B-type message using said digital BTI data record; Non-transitory computer-readable medium.

106. 95. The non-transitory computer-readable medium of claim 94, wherein the database is queried by at least a substring of integer characters that make up the OP-BTI. Non-transitory computer-readable medium.

107. 95. The non-transitory computer-readable medium of claim 94, wherein the operations further include: causing, by the at least one processor, a printing device to print an International Air Transport Association (IATA) format compliant return baggage tag for the return flight; Non-transitory computer-readable medium.

108. 95. The non-transitory computer-readable medium of claim 94, wherein the database stores a manifest. Non-transitory computer-readable medium.

109. 95. The non-transitory computer-readable medium of claim 94, wherein the operations further include: triggering, by the at least one processor, in response to obtaining the OP-BTI, check-in of each baggage item of the passenger for the return flight with the return flight's mobile carrier; Non-transitory computer-readable medium.

110. 110. The non-transitory computer-readable medium of claim 109, wherein the operations further include: generating, by said at least one processor, a simulated airline B-type message having said return flight data, passenger name, and passenger name record; queuing, by the at least one processor, the simulated airline B-type message; and merging, by the at least one processor, the simulated airline B-type message with a carrier B-type message of the return travel carrier during a check-in window; Non-transitory computer-readable medium.

111. 111. The non-transitory computer-readable medium of claim 110, wherein the operations further include: assigning, by the at least one processor, a new OP-BTI to each baggage item on the return flight; and entering, by the at least one processor, a new digital BTI record representing the assigned OP-BTI into the simulated airline B-type message; Non-transitory computer-readable medium.

112. 95. The non-transitory computer-readable medium of claim 94, wherein the act of querying the database using the OP-BTI as the unique identifier to obtain the return flight data for the passenger further includes: accessing, by said at least one processor, a passenger name record (PNR) stored in an information system of said origin airline mobile carrier using said digital BTI data record; Non-transitory computer-readable medium.

113. 95. The non-transitory computer-readable medium of claim 94, wherein the operations further include: receiving, by the at least one processor, updated reservation information for the passenger; updating, by at least one of said at least one processor, a corresponding passenger itinerary linked to said passenger's extended type B message in said database; and triggering, in response to obtaining the OP-BTI, communication of the updated subscription information to a computing device by at least one of the at least one processor; Non-transitory computer-readable medium.

Images