Global bag tag system and instructions for use

Abstract

A global bag tag system and method of use are provided, the method of which includes assigning a tracking device to a passenger's luggage by at least one of at least one processors, loading information from a baggage source message (BSM) into the tracking device by at least one of at least one processors, and transmitting location information by the tracking device to a network interface of a computing system associated with at least one processor, wherein the location information includes location coordinate data of the tracking device and information from the BSM.

Description

Technical Field

[0001] Cross - Reference to Related Applications This application claims the benefit of priority of U.S. Provisional Patent Application No. 63 / 598,824, filed on November 14, 2023, and U.S. Provisional Patent Application No. 63 / 543,667, filed on October 11, 2023.

[0002] This application is also a partial continuation of each of the following and claims the benefit of priority of each of the following: U.S. Patent Application No. 18 / 418,972, filed on January 22, 2024, which is a continuation of U.S. Patent Application No. 18 / 197,840, filed on May 16, 2023.

[0003] This application is also a partial continuation of each of the following and claims the benefit of priority of each of the following: U.S. Patent Application No. 18 / 337,288, filed on June 19, 2023, which is a partial continuation application of U.S. Patent Application No. 18 / 332,377, filed on June 9, 2023, which is a continuation application of U.S. Patent Application No. 18 / 201,908, filed on May 25, 2023 (currently U.S. Patent Application No. 11,881,057), which is a continuation application of U.S. Patent Application No. 18 / 311,566, filed on May 3, 2023. Here, U.S. Patent Application No. 18 / 337,288 as a partial continuation application of U.S. Patent Application No. 18 / 104,359, filed on February 1, 2023 (current U.S. Patent No. 11,682,241), U.S. Patent Application No. 18 / 332,377 as a continuation application directly claiming the benefit of its priority, U.S. Patent Application No. 18 / 201,908, and U.S. Patent Application No. 18 / 311,566 respectively. Also, to avoid doubt and without limiting the generality described above, U.S. Patent Application No. 18 / 311,566 is a continuation application of U.S. Patent Application No. 18 / 104,359.

[0004] This application is also based on and claims priority rights from the following concurrently pending applications: International Application No. PCT / US2024 / 013083, International Application No. PCT / US24 / 13221 and International Application No. PCT / US24 / 13226, all filed on January 26, 2024; International Application No. PCT / US2024 / 012226 and International Application No. PCT / US2024 / 012231, both filed on January 19, 2024; International Application No. PCT / US24 / 13257 and International Application No. PCT / US24 / 132 International applications No. 58, PCT / US24 / 13259, PCT / US24 / 13261, PCT / US24 / 13262, and PCT / US24 / 13263 were all filed on January 27, 2024; and PCT / US24 / 13594, PCT / US24 / 13597, and PCT / US24 / 13599 were all filed on January 30, 2024.

[0005] This application is also a continuation of part of the following concurrently pending applications, and claims priority and interest in the following concurrently pending applications: U.S. Patent Application No. 18 / 529,705, filed on 5 December 2023, and U.S. Patent Application Nos. 18 / 421,581, 18 / 421,595, and 18 / 421,601, all filed on 24 January 2024, all continuations of U.S. Patent Application No. 18 / 337,288; U.S. Patent Application No. 18 / 418,972, filed on 22 January 2024; U.S. Patent Application No. 18 / 406 / 785, filed on 8 January 2024; and U.S. Patent Application Nos. 18 / 514,015 and 18 / 514,82 Patent applications 6, 18 / 514,195, 18 / 514,877, 18 / 514,914, 18 / 514,937, 18 / 514,924, 18 / 514,295, 18 / 515,004, 18 / 514,369, and 18 / 515,060; all filed on November 20, 2023; and U.S. Patent applications 18 / 427,323, 18 / 427,396, 18 / 427,438, 18 / 427,469, and 18 / 427,516, all filed on January 30, 2024.

[0006] All of the above are incorporated herein by reference in their entirety. [Background technology]

[0007] 1. Field The embodiments relate to the field of baggage handling and delivery, and more specifically to a global bag tag system and its usage.

[0008] 2. Explanation of related technologies Millions of passengers travel daily using various modes of transport. When families or groups travel, their luggage can affect their travel experience and limit their ability to explore their destination. One challenge affecting the travel experience is luggage management. Families often find it difficult to fit everyone and their luggage into a single vehicle (i.e., a rental car or taxi). Another challenge for traveling families is the safety of their luggage before arriving at their accommodation or cruise ship, for example, if it is left unattended during the journey.

[0009] Accommodations may store your luggage until you officially check in. However, arriving at the accommodation or sightseeing spot may not be convenient for sightseeing before check-in. [Overview of the project] [Means for solving the problem]

[0010] According to aspects of the present disclosure, the method includes assigning a tracking device to a passenger's luggage using at least one of at least one processors, loading information from a baggage source message (BSM) into the tracking device using at least one of at least one processors, and transmitting location information by the tracking device to a network interface of a computing system associated with at least one processor, wherein the location information includes location coordinate data of the tracking device and information from the BSM.

[0011] Assigning may include providing a tracking device with at least one of the following: a passenger reservation record (PNR) number, an International Air Transport Association (IATA) number plate number, or a global multimode movement (GMMT) bag tag number, and the method may further include receiving location information via a network interface of a computing system, and locating the luggage using the tracking device, by at least one of the at least one processor.

[0012] Passengers may include registered passengers with a baggage handling system, and BSM may include a Global Tracking Extended Baggage Source Message (GTE-BSM) that links the GMMT bag tag number with either the PNR number or the IATA license plate number.

[0013] The method according to claim 3, wherein the information from the BSM may include the IATA license plate number of another piece of luggage associated with the registered passenger.

[0014] Information from the BSM may include the IATA license plate number of another piece of luggage associated with an unregistered passenger linked to the PNR number.

[0015] BSM could be an airline BSM.

[0016] The computing system may be associated with an airline, a baggage handling system, or a mobile vehicle.

[0017] Tracking devices may include inertial navigation systems for environments where Global Navigational Satellite Systems (GNSS) are not present.

[0018] The method may further include, when a tracking device is within range of an ad-hoc connection, a Wi-Fi device, a Bluetooth®-enabled device, or a cellular tower, communicating current location information to the network interface of a computing system using one of the ad-hoc communication protocol, the Wireless Fidelity (Wi-Fi) communication protocol, the Bluetooth communication protocol, and the cellular communication protocol.

[0019] The method may further include: determining by at least one of the at least one processors that the BSM reference indicator represents the normal route of the package; determining by at least one of the at least one processors that the reference indicator of the received Type B message represents an unstructured route of the package; accessing location information generated by the tracking device to find the current location of the package; and generating a delivery order to reroute the package using the current location.

[0020] According to aspects of the present disclosure, the system includes a computing system comprising at least one processor and a network interface, at least one non-temporary tangible memory communicably coupled to the at least one processor, wherein the at least one memory stores at least one instruction, and a tracking device configured to transmit location information to the network interface, wherein the at least one processor is configured to execute at least one instruction to assign the tracking device to a passenger's luggage and to load information into the tracking device from a baggage source message (BSM), the location information comprising location coordinate data of the tracking device and information from the BSM.

[0021] At least one processor of the system may be further configured to execute at least one instruction to assign a tracking device to a piece of cargo by providing at least one of a passenger reservation record (PNR) number, an International Air Transport Association (IATA) license plate number, or a Global Multi-Mode Mobility (GMMT) bag tag number to the tracking device, receive location information by means of a network interface, and locate the piece of cargo using the tracking device.

[0022] The passenger may include a registered passenger having a carry-on handling system, and the BSM may include a Global Tracking Extended Carry-On Source Message (GTE-BSM) that links a GMMT bag tag number with one of a PNR number or an IATA license plate number.

[0023] The information from the BSM may include an IATA license plate number of another piece of cargo associated with a registered passenger.

[0024] The information from the BSM may include an IATA license plate number of another piece of cargo associated with an unregistered passenger associated with the PNR number.

[0025] The BSM may be an airline BSM.

[0026] The computing system may be associated with one of an airline, a carry-on handling system, or a moving vehicle.

[0027] The tracking device may include an inertial navigation system for an environment where a Global Navigation Satellite System (GNSS) does not exist.

[0028] When the tracking device is one of an ad hoc connection being within range, a Wi-Fi device being within range, a Bluetooth-enabled device being within range, or a cellular tower being within range, it can be further configured to communicate current location information to a network interface of a computing system using one of an ad hoc communication protocol, a Wireless Fidelity (Wi-Fi) communication protocol, a Bluetooth communication protocol, and a cellular communication protocol.

[0029] At least one processor of the system can be further configured to execute at least one instruction to determine whether a reference indicator of a BSM represents a normal route of the cargo, determine that a reference indicator of a received B-type message represents an abnormal route of the cargo, access location information generated by a tracking device to find the current location of the cargo, and generate a delivery instruction for rerouting the cargo using the current location.

[0030] According to an aspect of the present disclosure, a non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause the at least one processor to assign a tracking device to a passenger's cargo by at least one of the at least one processor, load information from a baggage source message (BSM) into the tracking device by at least one of the at least one processor, and transmit location information to a network interface of a computing system associated with the at least one processor by the tracking device, the location information including location coordinate data of the tracking device and information from the BSM.

[0031] With respect to a method performed in response to an instruction stored in a non-temporary computer-readable medium, the assignment may include providing a tracking device with at least one of the following: a passenger reservation record (PNR) number, an International Air Transport Association (IATA) license plate number, or a Global Multimode Movement (GMMT) bag tag number, and the method may further include receiving location information via a network interface of a computing system, and locating the luggage using the tracking device, by at least one of the following:

[0032] With respect to a method of execution in response to instructions stored in a non-temporary computer-readable medium, a passenger may include a registered passenger with a baggage handling system, and a BSM may include a Global Tracking Extended Baggage Source Message (GTE-BSM) linking a GMMT bag tag number with either a PNR number or an IATA license plate number.

[0033] Regarding the method of execution in response to instructions stored in a non-temporary computer-readable medium, the information from the BSM may include the IATA license plate number of another piece of luggage associated with the registered passenger.

[0034] Regarding the method of execution in response to instructions stored in a non-temporary computer-readable medium, the information from the BSM may include the IATA license plate number of another piece of luggage associated with an unregistered passenger associated with a PNR number.

[0035] Regarding the method of execution in response to instructions stored in a non-temporary computer-readable medium, a BSM could be an airline BSM.

[0036] With regard to a method of execution in response to instructions stored in a non-temporary computer-readable medium, a computing system may be associated with one of the following: an airline, a baggage handling system, or a mobile vehicle.

[0037] With regard to methods of execution in response to instructions stored in a non-temporary computer-readable medium, tracking devices may include inertial navigation systems for environments where global navigation satellite systems (GNSS) are absent.

[0038] With respect to a method of being executed in response to an instruction stored in a non-temporary computer-readable medium, the method may further include a tracking device communicating current location information to a network interface of a computing system using one of the ad-hoc communication protocol, the Wireless Fidelity (Wi-Fi) communication protocol, the Bluetooth communication protocol, and the cellular communication protocol when an ad-hoc connection is within range, a Wi-Fi device is within range, a Bluetooth-enabled device is within range, or a cellular tower is within range.

[0039] With respect to a method executed in response to an instruction stored in a non-temporary computer-readable medium, the method may further include: at least one of at least one processors determining that a reference indicator of a BSM represents the normal route of the package; at least one of at least one processors determining that a reference indicator of an received B-type message represents an unstructured route of the package; at least one of at least one processors accessing location information generated by a tracking device to find the current location of the package; and at least one of at least one processors generating a delivery instruction to reroute the package using the current location.

[0040] According to aspects of the present disclosure, the method includes storing a travel request number associated with a passenger in at least one memory of a tracking device; pairing the tracking device with a service device associated with an airline, airport, government agency, or entity; transmitting the travel request number to the service device by the tracking device; and causing the service device to perform a function based on the received travel request number, wherein the tracking device is attached to the passenger's luggage.

[0041] The method may further include a tracking device storing a digital certificate, and a tracking advisory requesting authentication from a service device using the digital certificate.

[0042] The method involves a tracking device communicating location information to a computing system associated with tracking luggage, independently of the passenger's mobile communication device, the location information representing the location of the luggage, and the communication may further include this.

[0043] The travel request number may include a passenger reservation record (PNR) number, the service device may include a kiosk with a bag tag printer, and its function may include printing bag tags compliant with the International Air Transport Association (IATA).

[0044] The move request number may include an International Air Transport Association (IATA) license plate number, the service device may include a baggage handling device in the airport baggage handling system, its function may include communicating a unique bag identification number to a security screening machine, its function may include communicating a pseudo-identification number to a security screening machine, and the tracking device may be configured to receive the pseudo-identification number when the baggage is in close proximity to the service device and the security screening machine.

[0045] The pseudo-identification number may include a primary number associated with a stored security screening image captured by the security screening machine.

[0046] The move request number may include the International Air Transport Association (IATA) license plate number, the service device may include a baggage handling device in the airport baggage handling system, the function may include communicating a unique bag identification number to a security screening machine, and the tracking device may be configured to receive the unique bag identification number when the baggage is in close proximity to the service device and the security screening machine.

[0047] The unique bag identification number may include a primary number associated with a stored security screening image captured by the security screening machine.

[0048] The method may include pairing a tracking device with a passenger's mobile communication device and communicating a travel request number via the mobile communication device, the travel request number may include a passenger reservation record (PNR) number.

[0049] The method may further include receiving personally identifiable information from the passenger's mobile communication device via a tracking device.

[0050] The method may further include storing personally identifiable information in at least one memory.

[0051] Personally identifiable information may include at least one of the following: the passenger's date of birth, the passenger's name, the passenger's social security number, the passenger's passport identification number, or a government-issued identification number.

[0052] Storing a move request number in at least one memory of the tracking device further includes storing baggage source message (BSM) information, the BSM information may include multiple move request numbers.

[0053] Multiple travel application numbers may include passenger reservation record (PNR) numbers and International Air Transport Association (IATA) license plate numbers.

[0054] BSM information may include reference indicators, and the method may further include: the tracking device receiving at least one reference indicator from a second service device; the tracking device comparing at least one reference indicator with reference indicators included in the BSM information; the tracking device determining that an unstructured reference indicator has been received; and the tracking device providing notification of the unstructured reference indicator to a computing system associated with tracking the package.

[0055] The method involves a tracking device communicating location information by notifying a computing system associated with tracking a package, the location information representing the location of the package, and may further include communicating this information.

[0056] The tracking device may be configured to communicate using at least one of the following protocols: Wireless Fidelity (Wi-Fi) communication protocol, Bluetooth communication protocol, cellular communication protocol, long-range radio frequency communication protocol, short-range communication protocol, near-field communication protocol, and Global System for Mobile Communications. The method may further include the tracking device communicating current location information to a computing system associated with tracking the package.

[0057] The move request number may include an International Air Transport Association (IATA) license plate number, and the method may further include a tracking device transmitting the move request number to a radio frequency identification (RFID) receiver of a baggage handling system (BHS), which then routes the baggage based on baggage source message (BSM) information accessed using the move request number.

[0058] The tracking device may include a display screen, the movement application number may include an International Air Transport Association (IATA) license plate number, and the method may further include causing the tracking device to display an IATA license plate having the IATA license plate number on the display screen.

[0059] According to aspects of the present disclosure, a system includes a tracking device comprising at least one processor and at least one non-temporary tangible memory communicably coupled to the at least one processor, wherein the at least one memory stores at least one instruction, the at least one processor being configured to execute at least one instruction to store a travel request number associated with a passenger in at least one memory, to pair the tracking device with a service device associated with an airline, airport, government agency, or entity, and to transmit the travel request number to the service device by the tracking device, the travel request number being configured to cause the service device to perform a function when the travel request device is received by the service device, and the tracking device being affixed to the passenger's luggage.

[0060] At least one processor in the system may be further configured to execute at least one instruction to store a digital certificate in at least one memory, and to request authentication by a service device using the digital certificate.

[0061] At least one processor of the system may be further configured to perform at least one instruction to communicate location information to a computing system associated with tracking luggage, independently of the passenger's mobile communication device, wherein the location information represents the location information of the luggage.

[0062] The travel request number may include a passenger reservation record (PNR) number, the service device may include a kiosk with a bag tag printer, and its function may include printing bag tags compliant with the International Air Transport Association (IATA).

[0063] The move request number may include an International Air Transport Association (IATA) license plate number, the service device may include a baggage handling device in an airport baggage handling system, the function includes communicating a pseudo-identification number to a security screening machine, and at least one processor of the system may be further configured to execute at least one instruction to receive the pseudo-identification number when the baggage is in close proximity to the service device and the security screening machine.

[0064] The pseudo-identification number may include a primary number associated with a stored security screening image captured by the security screening machine.

[0065] The move request number may include an International Air Transport Association (IATA) license plate number, the service device may include a baggage handling device in an airport baggage handling system, the function may include communicating a unique bag identification number to a security screening machine, and at least one processor of the system may be further configured to execute at least one instruction to receive a unique bag identification number when the baggage is in close proximity to the service device and the security screening machine.

[0066] The unique bag identification number may include a primary number associated with a stored security screening image captured by the security screening machine.

[0067] At least one processor of the system may be configured to execute at least one instruction to pair a tracking device with a passenger's mobile communication device and to cause the mobile communication device to communicate a travel request number, the travel request number including a passenger reservation record (PNR) number.

[0068] At least one processor in the system may be further configured to execute at least one instruction to receive personally identifiable information from a passenger's mobile communication device.

[0069] At least one processor in the system may be further configured to execute at least one instruction to store personally identifiable information in at least one memory.

[0070] Personally identifiable information may include at least one of the following: the passenger's date of birth, the passenger's name, the passenger's social security number, the passenger's passport identification number, or a government-issued identification number.

[0071] At least one processor of the system may be further configured to execute at least one instruction to store baggage source message (BSM) information in at least one memory, the BSM information may include a plurality of travel request numbers.

[0072] Multiple travel application numbers may include passenger reservation record (PNR) numbers and International Air Transport Association (IATA) license plate numbers.

[0073] BSM information includes reference indicators, and at least one processor of the system may be further configured to execute at least one instruction to receive at least one reference indicator from a second service device, compare at least one reference indicator with reference indicators included in the BSM information, determine that an unstructured reference indicator has been received, and provide notification of the unstructured reference indicator to a computing system associated with tracking a package.

[0074] At least one processor of the system may be further configured to perform at least one instruction to communicate location information by notification to a computing system associated with tracking luggage, wherein the location information represents the location information of the luggage.

[0075] The tracking device may be configured to communicate using at least one of the following protocols: Wireless Fidelity (Wi-Fi) communication protocol, Bluetooth communication protocol, cellular communication protocol, long-range radio frequency communication protocol, short-range communication protocol, near-field communication protocol, and a global system for mobile communications, and at least one processor of the system may be configured to execute at least one instruction to communicate current location information to a computing system associated with tracking the package.

[0076] The move request number may include an International Air Transport Association (IATA) license plate number, and at least one processor of the system may be further configured to execute at least one instruction to transmit the move request number to a radio frequency identification (RFID) receiver of a baggage handling system (BHS), which then routes, transmits, and transmits the baggage based on baggage source message (BSM) information accessed using the move request number.

[0077] The tracking device may further include a display screen, the movement application number may include an International Air Transport Association (IATA) license plate number, and at least one processor of the system may be further configured to execute at least one instruction to cause the display screen to display an IATA license plate having the IATA license plate number.

[0078] According to aspects of the present disclosure, a non-temporary computer-readable medium storing instructions, wherein when the instructions are executed by at least one processor, the at least one processor performs a method including: storing a travel request number associated with a passenger in at least one memory of a tracking device; pairing the tracking device with a service device associated with an airline, airport, government agency, or entity; transmitting the travel request number to the service device; and causing the service device to perform a function based on the received travel request number, wherein the tracking device is affixed to the passenger's luggage.

[0079] With regard to a method executed in response to an instruction stored in a non-temporary computer-readable medium, the method may further include, by a tracking device, storing a digital certificate, and by tracking advice, requesting authentication by a service device using the digital certificate.

[0080] With respect to a method performed in response to instructions stored in a non-temporary computer-readable medium, the method further includes communicating location information by a tracking device to a computing system associated with tracking luggage, independently of a passenger's mobile communication device, wherein the location information represents the location information of the luggage.

[0081] With respect to a method of execution in response to instructions stored on a non-temporary computer-readable medium, the travel request number may include a passenger reservation record (PNR) number, the service device may include a kiosk including a bag tag printer, and its function may include printing bag tags compliant with the International Air Transport Association (IATA).

[0082] With regard to a method of execution in response to instructions stored on a non-temporary computer-readable medium, the move request number may include an International Air Transport Association (IATA) license plate number, the service device may include a baggage handling device in an airport baggage handling system, the function may include communicating a unique bag identification number to a security screening machine, the function may include communicating a pseudo-identification number to a security screening machine, and the tracking device may be configured to receive the pseudo-identification number when the baggage is in close proximity to the service device and the security screening machine.

[0083] With respect to a method executed in response to an instruction stored in a non-temporary computer-readable medium, the pseudo-identification number may include a primary number associated with a stored security screening image captured by a security screening machine.

[0084] With respect to a method of execution in response to instructions stored on a non-temporary computer-readable medium, the move request number may include an International Air Transport Association (IATA) license plate number, the service device may include a baggage handling device in an airport baggage handling system, the function may include communicating a unique bag identification number to a security screening machine, and the tracking device may be configured to receive the unique bag identification number when the baggage is in close proximity to the service device and the security screening machine.

[0085] With respect to a method of execution in response to instructions stored on a non-temporary computer-readable medium, the unique bag identification number may include a primary number associated with a stored security screening image captured by a security screening machine.

[0086] With respect to a method of being performed in response to an instruction stored in a non-temporary computer-readable medium, the method may further include pairing a tracking device with a passenger's mobile communication device, and communicating a travel request number by the mobile communication device, the travel request number may include a passenger reservation record (PNR) number.

[0087] With regard to a method of being executed in response to an instruction stored in a non-temporary computer-readable medium, the method may further include receiving personally identifiable information from a passenger's mobile communication device by a tracking device.

[0088] Regarding a method of performing an action in response to an instruction stored in a non-temporary computer-readable medium, the method may further include storing personally identifiable information in at least one memory.

[0089] With respect to a method of execution in response to an instruction stored in a non-temporary computer-readable medium, personally identifiable information may include at least one of the following: the passenger's date of birth, the passenger's name, the passenger's social security number, the passenger's passport identification number, or a government-issued identification number.

[0090] With respect to a method of being executed in response to an instruction stored in a non-temporary computer-readable medium, storing a move request number in at least one memory of a tracking device may further include storing baggage source message (BSM) information, the BSM information may include a plurality of move request numbers.

[0091] With regard to methods of execution in response to instructions stored in a non-temporary computer-readable medium, multiple travel request numbers may include passenger reservation record (PNR) numbers, International Air Transport Association (IATA) license plate numbers, etc.

[0092] With respect to a method executed in response to an instruction stored in a non-temporary computer-readable medium, the BSM information may include a reference indicator, and the method may further include: the tracking device receiving at least one reference indicator from a second service device; the tracking device comparing at least one reference indicator with a reference indicator included in the BSM information; the tracking device determining that an unstructured reference indicator has been received; and the tracking device providing notification of the unstructured reference indicator to a computing system associated with tracking a package.

[0093] With respect to a method performed in response to an instruction stored in a non-temporary computer-readable medium, the method may further include communicating location information by a tracking device to a computing system associated with tracking a package, wherein the location information represents the location information of the package.

[0094] With respect to a method of being executed in response to instructions stored in a non-temporary computer-readable medium, the tracking device may be configured to communicate using at least one of the following: Wireless Fidelity (Wi-Fi) communication protocol, Bluetooth communication protocol, cellular communication protocol, long-range radio frequency communication protocol, short-range communication protocol, near-field communication protocol, and global system for mobile communications, and the method may further include the tracking device communicating current location information to a computing system associated with tracking the package.

[0095] With respect to a method performed in response to an instruction stored in a non-temporary computer-readable medium, the movement request number may include an International Air Transport Association (IATA) license plate number, and the method may further include a tracking device transmitting the movement request number to a radio frequency identification (RFID) receiver of a baggage handling system (BHS), which then routes the baggage based on baggage source message (BSM) information accessed using the movement request number.

[0096] With respect to a method performed in response to an instruction stored in a non-temporary computer-readable medium, the tracking device may include a display screen, the movement application number may include an International Air Transport Association (IATA) license plate number, and the method may further include causing the tracking device to display an IATA license plate having the IATA license plate number on the display screen.

[0097] For a more complete understanding of the embodiments, the following detailed disclosures should be referenced in relation to the attached drawings. [Brief explanation of the drawing]

[0098] [Figure 1A] An embodiment of a multimode baggage management (MMBM) system for managing the transport of at least one piece of baggage during a baggage transfer is shown. [Figure 1B] An embodiment of a multimode baggage management (MMBM) system for managing the transport of at least one piece of baggage during a baggage transfer is shown. [Figure 2A] A flowchart of a method for generating a permanent bag tag identifier (P-BTI) according to an embodiment is shown. [Figure 2B] This shows a global bag tag having a P-BTI according to an embodiment. [Figure 2C] A flowchart of a method for forming a global bag tag according to an embodiment is shown. [Figure 3A]A flowchart illustrating an embodiment of a method for assigning a tracking device and initiating tracking of a package is shown. [Figure 3B] A flowchart of a method for tracking luggage according to an embodiment is shown. [Figure 4A] A flowchart of a method for contactless parking payment according to an embodiment is shown. [Figure 4B] A flowchart illustrating a method for accessing a Type B message for travelers using contactless parking payment, according to an embodiment, is shown. [Figure 5] A flowchart illustrating a method for generating and / or updating a cargo item list record according to an embodiment is shown. [Figure 6A] This document describes a system for digitizing baggage management and baggage check-in according to an embodiment. [Figure 6B] A flowchart of a method for checking in passengers and / or generating a baggage inventory according to an embodiment is shown. [Figure 6C] A flowchart of a method for checking in passengers and / or generating a baggage inventory according to an embodiment is shown. [Figure 6D] A flowchart of a method for checking in passengers and / or generating a baggage inventory according to an embodiment is shown. [Figure 7] An exemplary, verified itinerary for an air flight is shown according to the embodiment. [Figure 8] This shows the format of an airline baggage source message (BSM). [Figure 9A] The format of the Global Tracking Extended Baggage Source Message (GTE-BSM) according to the embodiment is shown. [Figure 9B] This shows the Global Tracking Extended Baggage Source Message (GTE-BSM) link structure according to an embodiment. [Figure 10A]A flowchart of a method for generating a Global Tracking Extended Baggage Source Message (GTE-BSM) for a registered passenger and / or a Temporary Baggage Source Message (T-BSM) for the current travel itinerary for one or more unregistered passengers, according to an embodiment, is shown. [Figure 10B] A flowchart of a method for generating a Global Tracking Extended Baggage Source Message (GTE-BSM) for a registered passenger and / or a Temporary Baggage Source Message (T-BSM) for the current travel itinerary for one or more unregistered passengers, according to an embodiment, is shown. [Figure 10C] A flowchart of a method for generating a Global Tracking Extended Baggage Source Message (GTE-BSM) for a registered passenger and / or a Temporary Baggage Source Message (T-BSM) for the current travel itinerary for one or more unregistered passengers, according to an embodiment, is shown. [Figure 11A] This document illustrates baggage transfer route recording for different travel itineraries, according to one or more embodiments. [Figure 11B] This document illustrates baggage transfer route recording for different travel itineraries, according to one or more embodiments. [Figure 11C] This document illustrates baggage transfer route recording for different travel itineraries, according to one or more embodiments. [Figure 12] This is a block diagram showing an electronic device in a network environment according to one or more embodiments. [Figure 13A] A flowchart illustrating an embodiment of a method for managing the retrieval of missing, lost, rerouted, delayed, or mishandled packages is shown. [Figure 13B] A flowchart illustrating an embodiment of a method for managing the retrieval of missing, lost, rerouted, delayed, or mishandled packages is shown. [Figure 14] A flowchart illustrating an embodiment of a method for locating missing, lost, rerouted, delayed, or mishandled luggage is shown. [Figure 15] A diagram of the abnormal package item detection model is shown. [Figure 16A] A block diagram of the tracking device according to the embodiment is shown. [Figure 16B] A block diagram of a contactless bag tag printing manager according to an embodiment is shown. [Figure 16C] A block diagram of a security screening manager according to an embodiment is shown. [Figure 16D] A block diagram of a mobile-tracker pairing manager according to an embodiment is shown. [Figure 16E] A block diagram of an unstructured reference indicator detection manager according to an embodiment is shown. [Figure 17A] A block diagram of a contactless baggage tag printing process using a tracking device, according to an embodiment, is shown. [Figure 17B] A block diagram of a pseudo-identification (ID) recording process using a tracking device according to an embodiment is shown. [Figure 17C] This diagram shows a process for communicating location information from a Global Navigation Satellite System (GNSS) platform according to an embodiment. [Figure 17D] A diagram of the process for a tracking device to communicate location information with at least one radio frequency (RF) access point, according to an embodiment, is shown. [Figure 18] A block diagram of the tracking system according to the embodiment is shown. [Modes for carrying out the invention]

[0099] The following detailed description refers to the attached drawings, which form part of this specification and illustrate specific embodiments. It should be understood that other embodiments may be utilized and modified without departing from the scope of this disclosure.

[0100] Glossary A-BTI stands for "Airline Bag Tag Identifier." Also known as a baggage tag or baggage label, an Airline Bag Tag Identifier is a baggage tag or label attached to a passenger's baggage that contains identification information about the passenger and their flight with the airline. It is used by airlines to track and handle passengers' checked baggage. Tags carrying A-BTIs typically include the passenger's name, flight information (flight number, departure and destination airports, and travel date and time), and a unique identifier such as a bag tag number or barcode. Each A-BTI corresponds to a unique International Air Transport Association (IATA) number plate, which airlines use to track baggage via the Baggage Handling System (BHS), match baggage to the passenger's flight and route, and identify the owner of baggage in case of misplacement, loss, or delay. A-BTIs are usually issued at check-in, and passengers either attach them to their baggage or they are attached by counter staff before receiving their baggage at the baggage claim counter.

[0101] A Departure Control System (DCS) refers to a system that controls various airline operations, including airport check-in, baggage check-in, generation of passenger bag tag identifiers (BTIDs), and printing of bag tags. Bag tags are formatted according to rules published by IATA, and include, for example, a 10-digit IATA number. Typically, one or more IATA Type B messages are created, containing the 10-digit number and flight information.

[0102] Type B (or Type B) messaging refers to a specific format of communication used by airlines and other entities in the aviation industry to send and receive critical operational data. These messages are standardized and used for a wide range of applications, including flight planning, passenger booking and check-in, baggage tracking, weather updates, and other critical air transport operations. The Type B messaging standard is overseen by IATA. Compared to more modern data types and formats such as XML (Extensible Markup Language) and JSON (JavaScript Object Notation) that carry message payloads, Type B messages employ a strict structure. Type B messages operate on a "store-and-forward" mechanism, where the message sender transmits data through a service provider, which is then stored for a contracted period, often seven days. The data is delivered directly to selected recipients or, if they reside on different networks, through a gateway provider. In case of delivery failure, contractual agreements allow for retransmission of the data, and accidental incidents are reflected in the PDM (Possible Duplicate Message) header.

[0103] Accommodation facilities, in a non-limiting sense, refer to businesses or operations that provide residential accommodation services, such as hotels, resorts, ferries, and cruise ships.

[0104] Mode of transport refers to the mode of intermediate or long-distance transport of travelers or passengers from a point of origin to a destination. Modes of transport may include automobiles, rental cars, buses, trains, ferries, airplanes, or any other commercial means of transport or passenger transport. A cruise ship may be a mode of transport.

[0105] Multimode travel means functionally using Type B messages and IATA messages, and extending the use of such messages to accommodation entities. The IATA message name, PNR number, and form become the bag tags for the entire trip and any mode of travel.

[0106] A Source Hardcopy Bag Tag Identifier (OH-BTI) refers to a unique identifier associated with or printed on a baggage tag from the departing airline. Generally, all baggage on airline travel is tagged with a unique identifier for tracking purposes. This is typically attached to the baggage at check-in and scanned at various points along its journey to ensure it reaches its correct destination.

[0107] P-BTI stands for "Permanent Bag Tag Identifier." A P-BTI is a specially issued bag tag identifier with a portion compliant with IATA regulations and is associated with the Global Multimode Movement (GMMT) bag tag number of a registered passenger's baggage. A P-BTI is an identifier linked to a registered passenger or traveler using the multimode baggage handling service. Specially issued P-BTIs are affixed to the passenger's baggage, including identification information about the registered passenger and, if grouped, passengers traveling with the registered passenger. P-BTIs are used by the multimode baggage handling service to track and process passengers' baggage and, if grouped, any traveling vehicles, including multiple vehicles, with the registered passenger and associated passengers traveling with them. P-BTIs are assigned to registered passengers for a predetermined validity period. P-BTIs may be renewable or expire upon death. The IATA-compliant portion of the P-BTI may include the letter code and / or corresponding numeric code of the non-boarding airline.

[0108] A passenger manifest is a record containing an array of data, including data for checking in passengers for their return journey segments by a designated return travel carrier.

[0109] PNR stands for "Passenger Reservation Record." It is a record in an airline or travel agency's database containing all the details of a passenger's itinerary and travel information. This information includes the passenger's name, contact information, flight details, seat preferences, and any special requests. The PNR also includes reservation information such as the booking date, fare, and ticketing status. It is used by airlines and travel agencies to manage and track passengers' itineraries and travel plans. A PNR number is unique to at least one passenger and is used as a reference for the passenger, airline, and travel agency's PNR. The PNR is also used for checking in, checking flight status, and making any changes to a reservation. The PNR number itself is typically six characters long and is often a combination of letters and numbers. While regulatory bodies like IATA do not specify a universal format for PNRs, each PNR has five required fields, including: (1) the telephone number associated with the traveler or agent; (2) the person who last changed the PNR; (3) the itinerary, which must include at least one segment of the journey; (4) the names of one or more passengers, including full first and last names; and (5) information specifying when and how the ticket will be issued. All modes of travel may use a PNR for their travel itinerary. Travel platforms may use a super PNR to associate several PNRs of a travel itinerary together.

[0110] PMM travel information is an abbreviation for "priority multimode" travel information. PMM travel information includes information in a database associated with a travel membership number or a membership number in a travel management system or online travel booking engine. The database may contain instructions for accessing travel booking information made by passengers registered using their travel membership number.

[0111] A registered passenger means a person, user, or passenger who has registered to manage the transport of at least one piece of luggage in the baggage transport process using a global baggage tag identifier.

[0112] A Travel Management System (TMS) is a type of service that users can access online to book one or more bookings for a single trip by finding or offering bookings according to the cheapest or discounted rates from different suppliers such as airlines, hotels, and car rental companies. Examples of TMSs include, but are not limited to, Travelocity®, Expedia®, Orbitz®, Priceline®, Trivago®, and Booking.com®. Examples of TMSs include, but are not limited to, online leisure rental platforms such as Airbnb®, Vrbo®, Vacasa®, Kayak.com®, and Hometogo®. A Travel Management System (TMA) can be an online travel booking engine.

[0113] A Travel Membership Number (TMN) is a number assigned to a user or member of an entity to earn reward points or discounts, which are converted into non-transferable monetary value usable only by the member entity. A TMN may include an airline mileage membership number, a hotel membership number, a rental car membership number, or a cruise line membership number, and is used by the member to make reservations.

[0114] A Global Tracking Extended Baggage Source Message (GTE-BSM) is a baggage source message that conforms to IATA Type B messages and is configured to independently link to booking information and global baggage tag numbers for multiple modes of travel. For airline modes of travel, the GTE-BSM includes fields for the global bag tag number and originating IATA license plate for the travel segment of the current itinerary. The GTE-BSM includes a link to PMM travel information.

[0115] A Global Multimode Travel (GMMT) bag tag number refers to a permanently assigned number or P-BTI for a registered passenger's luggage. Permanently assigned numbers comply with IATA regulations and are either renewable or expire after a specified one-month validity period or upon death.

[0116] A global bag tag refers to a bag tag configured to be affixed to luggage for multiple uses, including a substrate on which a GMMT bag tag number is printed, engraved, embossed, etched, or otherwise applied. The permanently assigned number plate or P-BTI is applied to the substrate with a barcode or quick response (QR) code that complies with IATA regulations. A global bag tag may include the registered passenger name and at least one PMM code associated with PMM travel information.

[0117] A Vehicle of Transportation (VOT) means accommodation and / or means of transport used by passengers or luggage during a journey. The term "transportation" is not limited to locomotives, ground transport, air transport, water transport, or moving transport. Rather, transportation is a medium for providing travel, accommodation, or entertainment to travelers during a journey based on a reservation.

[0118] In one or more embodiments, the system may be configured to link different travel members of a passenger and modes of travel members so that the system can access reservations for any travel vehicle related to the travel itinerary of the system's travel members (i.e., passengers). This allows the system to collect more accurate information for the traveler's luggage itinerary and travel independently and / or in parallel with the traveler.

[0119] According to the embodiment, the system can cause one or more reservation systems to provide updates to the baggage handling itinerary segments regarding changes to reservations for baggage handling. Alternatively, the system can query the travel member's reservation system again to determine, for example, any changes to reservations within a travel slot.

[0120] The system can generate GTE-BSMs that comply with IATA regulations. GTE-BSMs can be used by airline baggage handling systems to handle and transport baggage through airline infrastructure, outside airline infrastructure, and / or at locations where airline infrastructure and outside airline infrastructure overlap.

[0121] System 100 can receive updates from registered passengers for changes or cancellations of reservations.

[0122] In one or more embodiments, the system's processor is configured to link a Global Multi-Mode Travel (GMMT) bag tag number to at least one travel membership number for a registered passenger, and to access booking information associated with at least one travel mode associated with at least one travel membership number associated with the registered passenger. The system's processor is configured to collect booking information for the current travel itinerary of at least one piece of luggage traveling independently or in parallel with the registered passenger in the registered passenger profile linked to the GMMT bag tag number. The system's processor is configured to construct a Baggage Travel Route Record (BTJR) for the retrieval and delivery of at least one piece of luggage based on the collected booking information, and the BTJR is linked to the GMMT bag tag number.

[0123] Figures 1A and 1B show a multimode baggage management (MMBM) system 100 according to an embodiment for managing the transport of at least one piece of baggage during a baggage transport journey. The system 100 in Figure 1A is shown below the dotted line AA. The MMBM system 100 is designed to manage the transport of baggage for registered passengers independently of and / or in parallel with the passenger journey, using P-BTI 134 printed, embossed, etched, engraved, or coated on the substrate 233 of a global bag tag 230 (Figure 2B).

[0124] System 100 may include a website 110 having a web server 112 that runs a web operating system and web applications. When the website 110 is run by one or more processors of the web server 112, it may include a memory device 115 that stores programming code that runs one or more of the blocks described herein. The programming code may include MMBM programming modules 120. One or more programming modules 120 may include software, hardware, firmware, or a combination of software, hardware, and firmware for performing the functions described herein when run by one or more processors of System 100.

[0125] The memory device 115 may contain a master travel inventory 109, which contains passengers traveling on that day. The MMBM programming module 120 may contain programming instructions, which, when executed, use the data in the inventory to locate the traveling passengers and their luggage. The MMBM programming module 120 may contain programming instructions, when executed, to update the master travel inventory 109 with the IATA bag tag number when the passenger's baggage is checked in by the system 100's processor at home, accommodation, or another location. The MMBM programming module 120 may contain programming instructions, when executed, to update the master travel inventory 109 with baggage source message information and information generated in the development of the GTE-BSM structure 950. The MMBM programming module 120 may contain programming instructions, when executed, to receive a Type B message from an airline for passengers or travelers traveling on a particular day or time frame.

[0126] Website 110 can be accessed by a computing device 50 associated with a user or passenger in order to register with system 100 via an online session through a web server 112.

[0127] When executed, the MMBM programming module 120 may include programming instructions that cause the passenger registration graphical user interface (GUI) 124 to collect information for registering a passenger, traveler, or user. As used herein, a user, traveler, or passenger is referred to as a registered passenger. The computing device 50 can register a user or passenger by interacting with the website 110 using the passenger registration GUI 124.

[0128] The passenger registration GUI 124 may include programming instructions that, when executed, request and receive passenger personal information (PI) 129 from the personal information collector 125 to register the passenger and create a registered passenger profile 122. The PI 129 may include one or more of the registered passenger's name, home address, telephone number, date of birth, and email address. The PI 129 may include at least one of the following: driver's license information and passport information with a passport identifier. An image of the driver's license can be uploaded and stored in the PI 129, for example. The driver's license information and passport information each include an image of the passenger / traveler's face. In one or more embodiments, the PI 129 may include an image of at least one of the passenger / traveler.

[0129] In one or more embodiments, the passenger registration GUI 124 may include data input fields for requesting demographic information such as work, hobby, and trading memberships, social media accounts, and entertainment membership accounts. Demographic information may be stored as part of the PI 129. The system 100 can use the user's history to identify meetings or events previously attended. Meetings or events may be related to demographic information, for example, demographic information or past history to predict the use of contactless parking services without a hotel reservation.

[0130] In one or more embodiments, the GUI 124 or other graphical user interface can receive instructions from the user that enable the system 100's processor to track the user's location using those mobile communication devices. In one or more embodiments, tracking the user's location can help find the fastest route to deliver an unusual package to its owner. In one or more embodiments, tracking the user's location can help find available parking when finding a parking spot is difficult.

[0131] In one or more embodiments, the passenger registration GUI 124 may request permission from the system 100 via the processor to provide certain personally identifiable information, such as the passenger's name and date of birth, along with security screening images, to a government agency such as the Traffic Safety Administration (TSA).

[0132] When executed, the passenger registration GUI 124 may include programming instructions that cause the luggage information collector 126 to receive images of the luggage, which can then be matched with the physical luggage as needed. Registered passengers can update the images of their luggage in storage when their luggage is replaced or exchanged.

[0133] In one or more embodiments, PI129 may include credit card or bank transaction information for billing baggage fees from airlines, parking fees as described in relation to Figure 4A, or other fees necessary for delivering and handling the luggage of registered passengers. The bank transaction information may be arranged in a secure wallet 980 (Figure 9B).

[0134] The passenger registration GUI 124 may include programming instructions that, when executed, cause the priority multimode (PMM) travel information collector 127 to query and receive travel preference information. The PMM travel information collector 127 is described in relation to Figure 2A. As a non-limiting example, the travel preference information may include travel member information (TMI) 128.

[0135] The collected TMI128 may include at least one travel membership number. System 100 can autonomously retrieve other company information associated with the entered TMI128 (i.e., travel membership number), such as the name of the company sponsoring the membership, the company's address, and company contact information. Alternatively, passengers may enter business information, or a portion thereof. The TMI128 may include information associated with one or more of the following: mileage membership number, hotel membership number, travel membership number, travel management system (TMS) number, etc. The information is stored in a database to access the reservation information associated with the TMI128.

[0136] TMI128 can be associated with TMS. System 100 can access multiple reservations made via TMS and build a travel record of luggage that is independent of the passenger (i.e., the luggage owner).

[0137] When executed, the MMBM programming module 120 can include programming instructions that cause the contactless parking payment service 139 to collect information from passengers, travelers, and users for registration in contactless parking payment. This can be achieved using a graphical user interface in which the user enters the license plate number of their vehicle, such as for road trips they are taking, and links to hotel reservations, and in one or more embodiments, rental car reservations and hotel reservations. Details of the contactless parking payment service 139 can be described in more detail with reference to Figure 4A.

[0138] According to one or more embodiments, the MMBM programming module 120, when executed, may include programming instructions that cause a global bag tag generator 130 to generate a P-BTI 134. The global bag tag generator 130, when executed, may include programming instructions that cause a P-BTI generator 133 to assemble the P-BTI 134. In one or more embodiments, a portion of the P-BTI 134 may be IATA compliant. The P-BTI generator 133, when executed, may include programming instructions that cause a permanent number plate (P-LP) generator 135 to generate a permanent bag tag number plate (P-LP) 136 that may be IATA compliant. The P-LP 136 may include a series of numbers. The P-BTI generator 133, when executed, may include programming instructions that cause a PMM code generator 137 to generate at least one PMM code 138. According to embodiments, each PMM code may be directly associated with a traveler membership number associated with a TMI 128.

[0139] According to one embodiment, P-BTI134 may include both a series of alphanumeric characters and the associated barcode or quick response (QR) code of P-LP136. PMM code 138 may include a series of alphanumeric characters and associated barcodes or QR codes (registered trademarks). According to one or more embodiments, the assembled P-BTI 134 may include a first portion including a P-LP 136. In some cases, the registered passenger does not need to enter a TMI 128. In one or more embodiments, the assembled P-BTI 134 may include a first portion including a P-LP 136 and a section portion including a PMM code that does not represent TMI information. However, if the registered passenger adds TMI information to the passenger profile, the assembled P-BTI 134 may include a second portion including at least one PMM code 138. As a non-limiting example, the assembled P-BTI 134 may include a space or gap between the end of the first portion (i.e., P-LP 136) having at least one PMM code 138 and the second portion. As a non-limiting example, the assembled P-BTI 134 may include a dash between the end of the first portion (i.e., P-LP 136) having at least one PMM code 138 and the second portion. As a non-limiting example, the assembled P-BTI134 may include a first portion (i.e., P-LP136) located at a first position (Figure 2B) on the substrate 233, and a second portion having at least one PMM code 138 located at a second position (Figure 2B) on the substrate 233, where the first position is different from the second position.

[0140] An assembled P-BTI134 may include PMM codes 138 for different TMI128s for one or more travel membership numbers. In one or more embodiments, an assembled P-BTI134 may include one PMM code 138 for accessing all TMI128s. In one or more embodiments, an assembled P-BTI134 may include one PMM code 138 for each different TMI128. An assembled P-BTI134 may include one PMM code 138 for each category of TMI128.

[0141] P-BTI134 may be associated with GTE-BSM141, and both may have a predetermined duration. P-BTI134 and GTE-BSM141 may, for example, expire after a predetermined validity period, or be renewed after expiration. The permanent duration of P-BTI and GTE-BSM may be during the validity period. The predetermined validity periods of P-BTI134 and GTE-BSM141 may be 1 month to 1 year, 5 years, 10 years, or 20 years. This disclosure is not limited to the aforementioned validity periods, and other predetermined validity periods may include, for example, more than 1 month but between 1 and 5 years, or less than 10 years.

[0142] According to the embodiment, the passenger's P-BTI 134 may include a permanent number plate (P-LP) 136 that can comply with IATA regulations now and in the future. The P-BTI 134 may include at least one preferred multimode (PMM) travel code 138 based on at least one travel membership number of the registered passenger.

[0143] According to one or more embodiments, the MMBM programming module 120, when executed, can include programming instructions that cause a GTE-BSM generator 140 to generate a GTE-BSM 141, as described in relation to Figure 9A. The GTE-BSM generator 140 can include programming instructions that, when executed, can create BSM fields such that several fields have permanent information assigned to specific fields. For example, the GTE-BSM 141 may have a field with a registered passenger name (RPN) 143. The GTE-BSM 141 may have a field for P-BTI 134 with at least P-LP 136. In the GTE-BSM 141, a special character or digit may separate P-LP 136 from the first PMM travel code 138. Similarly, a special character or digit may separate each PMM travel code 138 from the next PMM travel code. Other coding schemes for separating code sequences may be used and are not limited to those described herein.

[0144] GTE-BSM141 can be updated with the current Passenger Reservation Record (PNR) number 142 associated with the current travel itinerary within a specific travel slot. PNR number 142 may have one or more passengers in the passenger list, provided that one of the passengers is a registered passenger matching RPN143.

[0145] System 100 may be configured to autonomously associate a Passenger Reservation Record (PNR) number 142 with a GTE-BSM 141 for a particular travel slot if one of the listed passengers is a passenger with a P-BTI 134. For example, a registered passenger can book their current travel itinerary using any travel membership number from which a PNR number may be created. In one or more embodiments, a super PNR number may be created for multiple travel modes, with or without multiple passengers connected to / associated with the super PNR number. In response to a travel booking being made, the travel itinerary can be retrieved by accessing the corresponding booking system, as will be described in more detail with reference to Figure 1B.

[0146] The MMBM programming module 120 may include programming instructions that, when executed, link multiple unregistered passengers together to the Follow PNR baggage link 144 with the registered passenger's GTE-BSM and P-BTI, all associated with the same PNR number for the current itinerary. In the example, some passengers associated with a super PNR number may initially be traveling with the same airline and / or arriving at their final destination at different times, disembarking from a cruise ship or staying at a resort. The Follow PNR baggage link 144 may include programming instructions that, when executed, link each unregistered passenger's A-BSM and / or A-BTI to the registered passenger's GTE-BSM 141, so that all passengers are associated with the PNR number for the current itinerary. Unregistered passenger names may be referred to as "other passenger names".

[0147] The follow-up PNR baggage link 144, when executed, may include programming instructions to cause the temporary BSM (T-BSM) generator 145 to generate a T-BSM 146, as described in relation to Figure 10B. The T-BSM 146 is similar to the GTE-BSM, except that it is for unregistered passengers. After the travel journey, the T-BSM 146 may be deleted in its entirety. The MMBM programming module 120, when executed, may include programming instructions to cause the moving vehicle BSM (VOT-BSM) generator 149 to generate a VOT-BSM 151, as described in relation to Figure 10C. An example of the link will be described later in relation to the steps related to block 507.

[0148] The MMBM programming module 120 may include programming instructions that, when executed, cause the baggage handling resource allocator 147 to determine the resources necessary to handle the tracking and / or handling of baggage at one or more destinations related to the baggage transport journey.

[0149] The baggage handling resource allocator 147 may, when executed, include a programming instruction that causes the departure allocator 148A to allocate resources (i.e., personnel and ground transport) for baggage to be picked up from the passenger's home or another designated address and delivered to a departure-type transport location such as an airport, bus stop, train station, ferry or cruise ship dock, or accommodation. The baggage handling resource allocator 147 may, when executed, include a programming instruction that causes the multimode location allocator 148B to allocate resources for baggage to be picked up from: a first vehicle that delivers to a second vehicle, and / or a vehicle that delivers to the next vehicle. The baggage handling resource allocator 147 may, when executed, include a programming instruction that causes the return allocator 148C to allocate resources for baggage to be picked up from the location of a vehicle and delivered to the passenger's home or another designated address. When executed, the baggage handling resource allocator 147 may include program instructions that assign one or more entries in the baggage movement route record for registered passengers to one or more baggage delivery resources to deliver or retrieve the baggage to a location associated with the baggage movement route location data.

[0150] Referring particularly to Figure 1B, the website 110 of system 100 can communicate with one or more of the following: cruise line reservation system 60, airline reservation system 62, train reservation system 64, bus reservation system 66, rental car reservation system 68, and accommodation reservation system 70. Access to one or more of these reservation systems can be used to retrieve travel information of registered passengers associated with the TMI 128 of the registered passenger profile 122. The accommodation reservation system 70 can be associated with hotels, accommodations, or resorts that may have associated parking facilities (PK) 71. The parking facilities 71 may include a computing system connected to a scanner 75. The scanner 75 can scan the license plates of vehicles to detect and register vehicles entering the parking lot or garage. Generally, the owner or user of a vehicle may be charged a parking fee for parking in the parking lot or garage.

[0151] In some scenarios, parking facilities can use facial recognition technology to identify the owner or user of a vehicle, with or without license plate scanning.

[0152] TMI128 may include travel members to a travel management system (TMS) 72 such as Travelocity®. System 100 can access the booking system of TMS 72 to retrieve bookings and construct travel itineraries. Registered passengers may have multiple TMS accounts, such as TMS 74 for vacation rental online platforms or online travel booking engines. System 100 can access each travel membership to determine the occurrence of the current travel itinerary.

[0153] In one embodiment, the system 100 via the web server 112 may include programming instructions that, when executed, access one or more reservation systems to obtain PNR numbers or itinerary confirmation numbers associated with the mode of travel carrier, and enable the web server 112 to update reservation data for multiple modes of travel carriers associated with the baggage transfer process for the current travel itinerary.

[0154] The MMBM programming module 120 may include a Baggage Transfer Route Record (BTJR) builder 150. The BTJR builder 150 may include programming instructions that, when executed, cause the creation of a BTJR 154 for the baggage of a registered passenger. The BTJR 154 is created or constructed for a specific (current) route based on a PNR number or itinerary confirmation number. For example, the BTJR 154 may include a PNR trigger 152 that can be entered by the registered passenger or received by the web server 112. Once the trigger is received, the programming instructions, when executed, can cause the creation of a baggage item inventory record 153 for the current route. An exemplary BTJR is described with reference to Figures 11A-11C. The trigger 152 may be received from the registered passenger when the registered passenger accesses their account and enters the current route. In embodiments, this may occur for the first time when the passenger is registered and obtains a global bag tag. In one or more embodiments, the web server 112 may receive information about a booked travel itinerary (i.e., a PNR trigger) from either the booking system associated with the TMI 128 or the booking system of the TMS 72. For example, when the booking system associated with the TMI 128 or the TMS 72 generates a PNR number for a registered passenger in system 100, a trigger may be sent to system 100 via the web server 112.

[0155] BTJR154 may be based on whether the baggage is being collected at the registered passenger's home, office, or other designated location. BTJR154 may include baggage drop-off locations for the first travel segment, the second travel segment, and / or end-to-end travel route records. Baggage drop-off locations may include government-authorized locations such as customs, and one or more security screening locations.

[0156] The BTJR builder 150 may include programming instructions that, when executed, cause the BTJR 154 to read BSM data for baggage associated with registered passengers and any unregistered passengers associated with the PNR number to which the registered passengers are associated.

[0157] Furthermore, regarding the current travel itinerary, the BTJR builder 150 via the web server 112 may include programming instructions that, when executed, can communicate with the cruise line reservation system 60, the airline reservation system 62, the train reservation system 64, and the bus reservation system 66 based on the passenger reservation record (PNR) number 142 or the itinerary confirmation number associated with one or more of the reservation systems. The BTJR builder 150 via the web server 112 may include programming instructions that, when executed, can retrieve travel information details such as the flight number, flight date, and flight arrival and departure data from the airline reservation system 62. The BTJR builder 150 via the web server 112 may include programming instructions that, when executed, can retrieve travel information details such as the cruise voyage number, voyage date and time, and cabin number, as a non-limiting example. The programming instructions can store passenger reservations in the passenger reservation database 121. Details of baggage travel information may match passenger reservations. However, passengers may have specific instructions to separate the route of their luggage from their own route.

[0158] The BTJR builder 150 via the web server 112 may include programming instructions that, when executed, allow access to reservations from the reservation system by accessing at least one travel membership number of a registered passenger associated with the TMI 128. The system 100 via the web server 112 may include programming instructions that, when executed, allow automatic retrieval of reservations associated with a travel membership number, since the reservation system for a travel membership number can store reservations for one or more establishments. For example, a passenger may have a reservation for a flight or travel mode to, for example, Orlando, Florida, and may have a travel membership with, for example, Hilton® Corporation. The BTJR builder 150 via the web server 112 may include programming instructions that, when executed, allow automatic querying of the Hilton® Corporation reservation system to find a reservation that matches the travel dates booked under the registered passenger name 143. However, if no such reservation is found, the system may send a communication to the passenger via email, telephone, or text to determine if other reservations are booked. A passenger may have travel memberships with multiple accommodations. The BTJR Builder 150 via the web server 112 may include programming instructions that, when executed, can query an accommodation reservation system with a recorded travel member number for reservations in Orlando, Florida, within the travel slot. The BTJR Builder 150 via the web server 112 may also include programming instructions that, when executed, can search for reservations within a specific radius of a mode of travel, such as an airline, cruise line, bus stop, or train station, for registered passengers within the travel slot.

[0159] The BTJR builder 150, via the web server 112, may include programming instructions that, when executed, can communicate with any reservation system for any mobile vehicle identified in the registered passenger profile 122.

[0160] Using a travel membership to access reservations involves providing the system with address and contact information for multiple accommodations associated with a single travel membership number. This limits the need to manually enter or remember accommodation addresses for specific travel itineraries.

[0161] The MMBM programming module 120 can include programming instructions that, when executed, cause the baggage check-in module 155 to check in baggage based on the pick-up process from home as shown in Figure 6A and the return travel segment as shown in Figures 6B-6C. The baggage check-in module 155 can access return flight data associated with the PNR number or itinerary confirmation number. The baggage check-in module 155 can include programming instructions that, when executed, allow the baggage to be checked in in the manner of a transport carrier, such as an airline, for the departure flight and / or return flight.

[0162] Passengers can check in for airline flights using a mobile communication device or computing device. In some cases, baggage for a passenger cannot be checked in until the passenger has checked in. In one or more embodiments, the MMBM programming module 120 may include programming instructions that, when executed, cause the passenger check-in module 163 to check in the passenger shown in Figure 10B. The passenger check-in module 163 can access return flight data associated with a PNR number or itinerary confirmation number.

[0163] The MMBM programming module 120 may contain programming instructions that, when executed, cause the departure bag tag receiving receiver 170 to receive an departure bag tag (O-BT) image 171 of a registered passenger departure bag tag number plate issued by the airline. Passengers can capture an O-BT image 171 of their bag tag number plate on a departure bag tag issued by the airline's counter agent or on a marker sticker on their ticket jacket. Passengers can transmit images to the system 100's web server 112 using a mobile communication device, laptop, notebook, or other computing device with a built-in camera and capable of internet, Wi-Fi, or wireless communication. The received images can be used, for example, to digitally create an A-BTI and access an airline baggage source message (A-BSM) or another B-type message. Printed A-BTIs can be digitally created using optical character recognition, and the printed text of the A-BTI can be converted into machine-coded text of the IATA license plate number. Alternatively, the passenger's mobile device may have a GUI that guides the user to scan an IATA barcode to digitally generate machine-encoded text of the IATA license plate number to be sent to the web server 112.

[0164] The MMBM programming module 120 can contain programming instructions, which, when executed, cause the GTE-BSM link module 173 to use the IATA license plate number digitally created from the O-BT image 171, allowing, for example, the GTE-BSM 141 to link with the airline BSM from the airline. The airline BSM (A-BSM) can take in data from various fields, as described in relation to Figure 8. Data from the origin A-BSM can be merged into fields of the GTE-BSM where permanent information has not been taken in.

[0165] The GTE-BSM link module 173, when executed, may include programming instructions that allow other messages of the travel mode for the current itinerary for registered passengers and / or unregistered passengers associated with the PNR number of the current itinerary to be linked together. The GTE-BSM link module 173 may include programming instructions that, when executed, allow information of registered passenger profiles 122 to be linked to the GTE-BSM so that when a registered passenger's global baggage tag or IATA license plate number is scanned and a P-BTI or printed A-BTI is electronically created on the global baggage tag, access to the registered passenger's travel information becomes possible for at least one of the following: a) checking in a registered passenger for a return flight, b) checking in a registered passenger for a vehicle, c) obtaining information for delivering luggage to its next scheduled location, d) obtaining information for moving luggage in parallel with and independently of its owner, and e) obtaining luggage location information. For unregistered passengers, scanning the A-BTI with the IATA bag tag provides access to location data and other information based on a link to the registered passenger's P-BTI.

[0166] The programming instructions for the GTE-BSM link module 173 will become clearer based on the description in Figure 9B.

[0167] The MMBM programming module 120 can include programming instructions that, when executed, cause the baggage transfer itinerary reservation tracker 175 to track reservation details to determine updates to any reservation fields. The baggage transfer itinerary reservation tracker 175 can also include programming instructions that, when executed, cause the travel update log 177 to update in response to baggage movement, such as when the global bag tag 230 is scanned. For example, the departure time may change.

[0168] The baggage transfer itinerary reservation tracker 175 may include programming instructions that, when executed, cause the message communication unit 178 to communicate status messages to the system, the computing devices of system personnel, and / or designated communication devices of passengers. The message communication unit 178 may provide passengers with messages regarding changes in departure or changes in the status of the location of the owner's baggage. In another example, the status of a hotel room may change from unavailable to available. The message communication unit 178 may provide passengers with messages regarding room availability. For example, a room may be in the process of being serviced or cleaned and not yet ready for passenger occupancy. Regarding modes of transport, a flight may have its gate changed at the airport. The message communication unit 178 may provide passengers with messages regarding changes in the gate for their flight or changes in the status of any transport vehicle.

[0169] The baggage transfer itinerary reservation tracker 175 may include programming instructions that, when executed, periodically check the reservation status of reservations associated with the travel itinerary record. For example, the baggage transfer itinerary reservation tracker 175 may check for updates to accommodation reservations in the travel itinerary record. In one or more embodiments, accommodation reservations may be based on information obtained from a reservation system associated with the registered passenger's accommodation travel membership. The baggage transfer itinerary reservation tracker 175 may obtain updates to the mode of travel, such as changes in airline gates, train stations, accommodation rooms, or cancellations.

[0170] In one or more embodiments, the web server 112 may include programming instructions that, when executed, activate the baggage transfer schedule tracker 175 during the baggage transfer process. The message communication unit 178 of the baggage transfer schedule tracker 175 can communicate baggage handling information regarding the transfer of luggage from the passenger to the baggage delivery resource to the passenger's mobile communication device. This may include communicating to the passenger via the message communication unit 178 an acknowledgment or receipt that the passenger's luggage has been picked up. If the luggage has not been checked in with the airline at this point, and is later checked in with the airline via the baggage check-in module 155, an electronic receipt with the airline's IATA bag tag number is electronically communicated by the message communication unit 178 to the passenger's mobile communication device or computing device.

[0171] In one or more embodiments, the web server 112 may include programming instructions that, when executed, activate the baggage transfer route reservation tracker 175 during the baggage transfer route to communicate changes to reservation information related to the delivery of baggage to a specified location to the passenger's mobile communication device. This may include informing the passenger that their baggage has been delivered to their room.

[0172] The message communication unit 178 may, for example, send text messages or emails.

[0173] The MMBM programming module 120 can include programming instructions that, when executed, cause the baggage retrieval manager 180 to electronically locate and retrieve lost baggage and manage the rerouting of found baggage. As will be described in more detail with reference to Figures 13A, 13B, and 14, baggage may become lost, missing, rerouted, delayed, or mishandled after being checked into a moving vehicle. The system 100 is configured to find and locate the abnormal baggage, keep the passenger informed of its current status, and work with the moving vehicle to quickly transport the found baggage and meet the passenger on the current route. The current route may be based on the passenger's current reservation information stored in the passenger reservation database 121.

[0174] The luggage retrieval manager 180 may include programming instructions that, when executed, cause the luggage finder 181 to detect abnormal luggage.

[0175] In one or more embodiments, for example, those luggage items having an assigned / registered tracking device 40 can be found using location data 984 (Figure 9B) stored in the travel history 184. In one or more embodiments, the system 100 can receive, access, and / or store Type B messages from a computer system associated with the airline for passengers registered on the day using the airline and associated unregistered travel. The Type B messages of those passengers in the master travel inventory 109 (Figure 1B) can be stored in the Type B message database 107 (Figure 1B). As a non-limiting example, luggage items that have been mishandled or rerouted may be delayed luggage items.

[0176] If it is determined that the luggage is missing, lost, rerouted, or mishandled, the luggage route data analyzer 182 can determine the route taken by the luggage and search and sort data from one or more B-type messages in the B-type message database 107 or from tracking device data in the travel history 184 to find data representing a location, airport, or other indicator for finding and recovering the luggage.

[0177] Certain types of Type B messages, such as Baggage Unconfirmed Messages (BNS), can be used to determine lost or unconfirmed baggage. This message may be generated when it is determined that baggage was not loaded (visible) on the same plane as the passenger. However, in a non-limiting example, baggage handlers or passengers may not be able to determine an anomaly until the point in time when they acquire possession of the baggage after it should have arrived at the airport. The Type B message database 107 may contain messages with data from BHS63B, which can be used to identify the current or last scanned location of the IATA bag tag on the baggage. For example, baggage with an IATA bag tag matching a passenger name in the master transfer inventory 109 may have been scanned at an airport different from the expected final destination airport for the passenger and / or baggage. In another example, baggage may have been scanned at the same airport as the passenger's departure flight after the flight had left the airport and has not been scanned since. As is understood, there are numerous scenarios in which baggage may be lost, and it would be impractical to describe every single one.

[0178] Alternatively, or in addition to the above, the location of the luggage can be determined using tracking device data in the travel history 184.

[0179] The MMBM programming module 120 may include programming instructions that, when executed, cause the travel history tracker 183 to generate and store a member's travel history 184, which includes data for travel itineraries, including flights, rental cars, accommodations, and other modes of transport. To improve baggage allocation, the travel history data can be analyzed for data statistics. The travel history data may also be used to push advertisements based on the travel history data of registered passengers. In one or more embodiments, the advertisements may be based on data analysis of the travel history data of the registered passenger's current travel itinerary. Data from the travel history tracker 183 can be used for data analysis to predict future resource scheduling. Data from the travel history tracker 183 can be used for data analysis based on end-BSM data linked to passenger history data to predict local future business volume for airports.

[0180] The MMBM programming module 120 may include programming instructions that, when executed, can, for example, cause registered passengers to receive advertisements via an advertising application programming interface (API) 185 for communication with the message communication unit 178, or via other communication modules for pushing advertisements based on current travel data (i.e., BTJR 154) and / or data in the member's travel history 184. The travel history 184 data may be used by the travel member's company to provide member benefits or discounts. BTJR 154 may be used by companies to prepare advertisements for registered passengers to restaurants, venues, hotels, or other establishments for passengers going to or passing through locations within a radius of a location identified by BTJR 154. For example, BTJR 154 can identify accommodations. Restaurants within a specific radius of or near the accommodation's location may offer discounts to registered passengers. Entertainment venues may offer advertisements for special events or special meals for times when passengers may be in the area, with or without discounts. Other accommodations may similarly offer advertisements. Advertisements may be delivered via social media platforms linked to accounts associated with passengers on their mobile communication devices or personal computing devices. BTJR154 may be linked to GTE-BSM (Figure 9B).

[0181] Advertisements are sent to the message communication unit 178 via the advertising API 185 and can be communicated to passengers' mobile communication devices via text or another computing device. Advertisements may also be sent via email via the message communication unit 178 or another communication module. Advertisements may also be sent as window overlays within applications viewed by passengers interacting with their mobile communication devices or personal computing devices.

[0182] The MMBM programming module 120 may include programming instructions that, when executed, cause the baggage tracker registration module 190 to register or assign a wireless tracker to be attached to the baggage. The tracker (i.e., tracking device) may have a tracking device identifier (ID) stored in the tracker or tracking device.

[0183] The luggage may also be fitted with a global bag tag. In one or more embodiments, the luggage may be equipped with a radio tracking device 40 (Figure 1A) provided by the passenger. In a non-limiting example, the radio tracking device 40 may be a tracking device that includes an accelerometer (ACC) and / or gyroscope 1282 (Figure 12), a Global Positioning System (GPS) 1280 (Figure 12), and / or an Inertial Navigation Unit (INU) 1284 (Figure 12) to determine its own location, and such location may be transmitted to a travel history tracker 183 where the received geographic location of the luggage is recorded. The radio tracking device 40 may have a unique identifier such as a registered serial number, a Media Access Control (MAC) address, or another assigned unique identifier. The wireless tracking device 40 may also be programmed with a unique identifier for the passenger and / or luggage, such as the passenger name, PNR number, Super PNR number, IATA license plate number, portion of the data from a Type B message, or any combination thereof. The wireless tracking device 40 can also be programmed with the GMMT bag tag number.

[0184] The wireless tracking device 40 may be an AIRTAG by APPLE Inc., 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 / or a long-range communication device using a suitable wireless communication protocol.

[0185] The wireless tracking device 40 can be configured for short-range communications such as Wi-Fi, Bluetooth Low Energy (BLE), and Bluetooth, but is not limited to these. Mobile vehicles, carrier stations, and other public infrastructure may include remote network devices that can connect to the wireless tracking device 40.

[0186] In one or more embodiments, the wireless tracking device 40 may be temporarily assigned to the luggage by the processor of the MMBM system 100. In one or more embodiments, the wireless tracking device 40 may be permanently assigned by the processor of the MMBM system 100. In one or more embodiments, the wireless tracking device 40 may be assigned by a computer system associated with the airline.

[0187] The wireless tracking device 40 may include, but is not limited to, long-range communication devices such as AIRTAG, Global Positioning System (GPS) trackers, Global System for Mobile Communications (GSM) trackers, and GSM-5G trackers from Apple Inc., and may communicate with cellular, satellite, and GSM communication service providers. The geolocation signal may be transmitted to a web server 112 or other designated computing device for access by a travel history tracker 183, which records the received geolocation of the luggage. In one or more embodiments, the long-range communication device may also be configured to communicate using a short-range communication protocol.

[0188] Depending on the configuration of the wireless tracking device 40, it may be used to track its location during travel using any mode of travel or the following modes of travel using long-range or short-range communication.

[0189] System 100 may include an acquisition device 195 (i.e., a scanning device, a mobile communication device, a video-enabled computing device, and an RF communication device) capable of scanning IATA-compliant license plates, including origin hard copy bag tags, global bag tags, marker tags, bingo tags, and RFID displays. The acquisition device 195 may provide geolocation information codes in communications, including digitally created bag tag identifiers (BTIs) (i.e., A-BTI or P-BTI).

[0190] As a non-limiting example, the acquisition device 195 may communicate a registered serial number, Media Access Control (MAC) address, or other unique identifier to the web server 112 of system 100. The acquisition device 195 may electronically acquire a representation of the GMMT bag tag number on the board at a location associated with the location data derived by the acquisition device 195. The acquisition device 195 may be, for example, a computing device or another computing system configured to generate electronic communications to the web server 112. The communications may include tracking information, which may include Global Positioning System (GPS) location data, time, date, and the GMMT bag tag number associated with the acquisition device 195. System 100 may record tracking information, including the current location of the luggage in the travel update log 177.

[0191] Generation of Permanent Bag Tag Identifiers (P-BTIs) Figure 2A shows a flowchart of Method 200 for generating a Permanent Bag Tag Identifier (P-BTI) according to an embodiment. Method 200 may include, in block 202, having a processor generate a P-BTI generator 133 or a Permanent Unique Identifier or Permanent Number Plate (P-LP) 136 that conforms to an IATA license plate. Both a number and a barcode can be generated in block 202.

[0192] Method 200 may include, in block 204, having the processor determine whether there is Travel Member Information (TMI). If the determination in block 204 is "yes", Method 200 may include, having the processor search for the TMI in block 206. Method 200 may also include, in 208, having the processor generate a PMM code 138 based on the TMI.

[0193] Method 200 may include, in block 210, having the processor determine whether there is another travel membership listed in the travel membership information. If the determination in block 210 is "yes", the method can return to block 206. Blocks 206, 208, and 210 are repeated for one or more travel members in the travel member information. If the determination in block 210 is "no", method 200 may include, having the processor assemble the P-BTI.

[0194] In block 204, if the determination is "no", method 200 can loop to block 212, and the P-BTI is assembled by the processor.

[0195] Method 200 may include, in block 214, having the processor determine whether the registered passenger has another piece of luggage. If the determination in block 214 is "no", method 200 may include, in block 216, having the processor set the first P-BTI as the main BTI. If the determination in block 214 is "yes", method 200 may include, in block 216, having the processor set the first P-BTI as the main BTI. The same P-BTI can be used for multiple pieces of luggage of a registered passenger. The luggage may be virtually linked using an image of a second piece of luggage stored in the registered passenger profile 122.

[0196] Figure 2B shows a global bag tag 230 having a permanent bag tag identifier (P-BTI) according to an embodiment. The global bag tag 230 may include, for example, a P-BTI 236 that conforms to IATA rules. The P-BTI 236 may be a 10-digit number plate with an adjacent barcode 240. In this example, the digit "000" is used as an airline code, such as a non-boarding airline code. Other codes of non-boarding airlines may be used. Furthermore, if the P-BTI is assigned by an airline, its IATA airline code is used. The digit "7" is the leading digit used in IATA license plate numbers, but is not limited to this. The digit "123456" can represent a permanent passenger baggage number.

[0197] The license plate may be extended to include other numbers. In this example, the two-digit letter code "TT" in P-BTI236' could represent a two-digit airline code for a non-boarding airline. The numbers "123456" represent the permanent passenger baggage number. P-BTI236' may also be a 10-digit license plate with an adjacent barcode 240'.

[0198] PMM code 238 uses the digit "AAA" which is representative only to represent the difference between P-BTI236 or 236' and PMM code 238. PMM code 238 may have a barcode 242 or a QR code. PMM codes can use other encoding schemes such as alphanumeric code digits of 1 to 10 digits in length, such as 1 to 3 digits, 1 to 5 digits, and 1 to 8 digits.

[0199] When creating a P-BTI, a two-digit airline code or a three-digit code may be associated with the airline code when the airline is not flying. In other embodiments, the two-digit carrier code may be a code assigned by IATA or other regulated entity for assigning carrier codes to airlines or other entities. The global bag tag 230 may include a passenger name 246 associated with a registered passenger to whom the P-BTI has been assigned for repeated use across multiple airlines and multiple flights. The P-BTI may be readable by BHS63B of airport infrastructure, but more importantly, it may be readable if the origin bag tag or other airline bag tagging system is damaged or lost.

[0200] According to one or more embodiments, the P-BTI may include a code representing the issuer of the GMMT bag tag number 250. The code may be associated with an airline, a non-boarding airline, or a baggage handling service.

[0201] The GMMT bag tag number 250 may include a two-letter airline code and a six-digit or three-digit airline code and a six-digit number. The six-digit number represents the passenger's bag number. In one or more embodiments, the passenger's bag number conceals the passenger's personal information. As the IATA license plate number expands, the GMMT bag tag number may also expand. For example, the two-letter airline code may expand. The three-digit airline code may expand over time. The six-digit passenger bag number may expand in length, or both alphabetic letters and numbers may be used instead of just numbers.

[0202] A computing device or web server 112 can communicate with a printing device or other machine to form a GMMT code representation on the substrate 233 representing the GMMT bag tag number 250. The GMMT code representation may include an IATA barcode representing the IATA license plate number and license plate number. The GMMT code representation may include a PMM code which may include a PMM number and a PMM barcode representing the PMM number.

[0203] In one or more embodiments, the global bag tag 230 may include a tracking device 40', shown as a dashed circle. In this example, the global bag tag 230 may include a housing with an enclosure for surrounding the tracking device 40'. The tracking device 40' may include a patch antenna. The GPS-5G tracking device may connect to one or more range-compatible radio frequency networks for cell tower positioning, Wi-Fi positioning, Global Navigation Satellite System (GNSS) positioning, and Bluetooth Low Energy.

[0204] The tracking device may be configured to connect to an ad-hoc connection when Wi-Fi or a cellular communication tower is unavailable.

[0205] Figure 2C shows a flowchart of Method 270 for forming a global bag tag according to an embodiment. Method 270 may include generating a Global Multi-Mode Movement (GMMT) bag tag number 250 for the registered passenger's luggage using at least one of the processors.

[0206] GMMT bag tag number 250 may include, in block 272, a permanently assigned number plate in compliance with IATA regulations, which is renewable or expires after a specified validity period or upon death. The specified validity period may range from one month to one year, one month to three years, one month to five years, one month to ten years, one month to twenty years, or until death.

[0207] Method 270 may also include, in block 274, generating a Global Tracking Extended Baggage Source Message (GTE-BSM) 900, which includes the GMMT bag tag number 250 and the passenger name of the registered passenger, by at least one of the at least one processors.

[0208] Method 270 may include, in block 276, forming a global bag tag 230 (Figure 2B) by a printing device on a substrate 233 to be attached to the luggage, which will have a GMMT code representation representing the GMMT bag tag number 250.

[0209] Tracking device - geographical location In the first quarter of 2022, it is estimated that 684,000 pieces of luggage were lost or mishandled by major US airlines. [Jake Hardiman and Anita Gallagher, “Luggage items g Why & How Often Does Luggage Get Lost?”, updated May 22, 2023, www.simpleflying.com / why-and-how-often-does-luggage-get-lost / .] Numerous attempts have been made to track luggage, but these have failed for a variety of reasons.

[0210] While RFID bag tags allow luggage to be tracked along its route through an airport, this solution faces two challenges. The first challenge is that every airport would need to be retrofitted with RFID receivers, and every bag tag would need to be RFID-enabled. This solution would be extremely expensive, and upgrading all airports to the point where they could track the luggage of millions of passengers using RFID technology would take years. The second challenge is that RFID technology may be limited to airport infrastructure and cannot provide extended baggage tracking outside of airports or tracking in structures with multiple modes of movement.

[0211] Another tracking function is the user's tracking device. Users can use various tracking devices that interface with their mobile communication devices, for example, to display the location of luggage on a map. However, this type of tracking is known to present challenges in correlating the user and the airport's location within the airport infrastructure when using Google Maps or another road map layout. In some cases, the location of luggage needs to be quickly identified before passengers move to another mode of transport. Another challenge is the ability of user-based tracking devices to communicate underground, such as when they are handled within the airport infrastructure.

[0212] In one or more embodiments, the global bag tag 230 may include a tracking device 40'.

[0213] In one or more embodiments, the tracking device may be configured to perform multiple modes or functions.

[0214] Figure 3A shows a flowchart of Method 300A for assigning a tracking device 40 and starting tracking of a package, according to an embodiment. Method 300A may include attaching the tracking device 40 to the package in block 302A. Method 300A may include assigning the tracking device 40 to the package by a processor in block 304A. The assignment may include programming by the processor, and the tracking device has at least one of the following in memory: a PNR number, an IATA license plate number, or a GMMT bag tag number. In the example, the assignment may include the processor programming the tracking device with BSM information including a reference indicator. The assignment may include the processor programming the tracking device with a tracking device ID, or the processor receiving a tracking device ID from the tracking device.

[0215] The tracking device may be programmed with or configured to receive a movement request number. For example, in one or more embodiments, the movement request number may include a PNR number. For example, in one or more embodiments, the movement request number may include an IATA license plate number. For example, in one or more embodiments, the movement request number may include a GMMT bag tag number.

[0216] However, during operation, as will be described later in relation to Figures 16A to 16E and Figures 17A to 17D, the tracking device may receive the travel request number (information) after the assignment or setting.

[0217] Block 304A may include, in Block 306A, the processor determining whether the tracking device 40 is assigned remotely. For example, the tracking device may be assigned by a baggage handling service that picks up the baggage from the passenger's or traveler's home or another designated address and transports the baggage to an airport or another vehicle. If the determination in Block 306A is "no", the route from Block 306A may terminate in Block 307A. If the determination in Block 306A is "yes", Method 300A may include, in Block 312A, the processor obtaining BSM information from the airline. The BSM information may be from the originating airline's BSM. The BSM information may be from a Global Tracking Extended Baggage Source Message (GTE-BSM) that links the baggage's Global Multimode Movement (GMMT) bag tag number with either a PNR number or an IATA license plate number. However, airline BSM information is available if the passenger has checked in with the airline using a personal computing device or mobile communication device. In this example, it is possible to program itinerary information into a tracking device from a remote location. The itinerary information may include a PNR number, a booking number, or other itinerary confirmation numbers from the vehicle's itinerary.

[0218] Method 300A may include, in block 308A, the processor determining whether the tracking device 40 is assigned from the destination airport / location. If the determination in block 308A is "no", the method from block 308A may terminate in block 307A. If the determination in block 308A is "yes", Method 300A may include, for example, in block 314A, the processor obtaining BSM information from the termination BSM. The BSM may be an airline termination BSM. The tracking device may also be programmed with the information described in relation to block 312A. In embodiments, the tracking device may be offered as a service to passengers as a reward for frequently purchasing cruises or staying at a particular hotel (i.e., a vehicle for travel).

[0219] Block 304A may include, in Block 310A, a determination by the system 100's processor whether the tracking device 40 has been assigned from the origin airport. If the determination in Block 310A is "no", the method from Block 310A may terminate in Block 311A. If the determination in Block 310A is "yes", method 300A may include, for example, in Block 316A, a determination by the processor to obtain A-BSM information from the originating airline BSM. In this example, an airline may provide a tracking device to passengers as a service for their travel itinerary. The travel itinerary may be one-way or round-trip. The tracking device may be assigned to a counter by an airline agent. In another embodiment, the tracking device may be provided to passengers as a service at a different time, such as as a reward for frequent flying. In another embodiment, the tracking device may be provided as a service to passengers who always fly in first class.

[0220] Block 304A may include, during the allocation process, having the processor load BSM information or information obtained in one of blocks 312A, 314A, or 316A into the tracking device in block 318A.

[0221] In the example, the information loaded from the BSM may include the IATA license plate number for each piece of luggage associated with a registered passenger. In the example, the information loaded from the BSM may include the IATA license plate numbers for luggage associated with unregistered passengers sharing the same PNR number. If the airline computing system assigns a tracking device, the tracking device is loaded into a processor associated with the airline's computer system. In the example, the processor may be the processor of system 100.

[0222] In the example, method 300A may include loading tracking device information into the GTE-BSM by the processor of system 100 in block 320A.

[0223] In the example, method 300A may include loading tracking device information into a Type B message by the processor in block 322A. The Type B message may be a BPM, BCM, BTM, or other IATA Type B compliant message. The Type B message may be generated by system 100 or by another designated entity or computer system associated with an airline or airport. The tracking device information may include a tracking device ID. The tracking device ID may be permanent or assigned.

[0224] Type B messages carrying information related to tracking devices may be used by baggage handling systems to recognize tracking devices within the baggage handling system and signals emitted from such tracking devices. Type B messages carrying information related to tracking devices may also be used within security screening areas to recognize authorized tracking devices within those areas.

[0225] In the example, method 300A may include, in block 324A, initiating tracking of the baggage using a tracking device by the processor of system 100 or another computer system designated to track it. For example, an airline may have a designated computer system for tracking baggage tracking devices.

[0226] In the example, method 300A may include, in block 326A, having a tracking device find an available radio communication platform for establishing a communication connection. The tracking device may include a GPS-GSM communication device configured to receive Global Navigation Satellite System (GNSS) signals. The tracking device may be configured to communicate with a Wi-Fi radio communication platform, a Bluetooth radio communication platform, a Long-Term Evolution (LTE) radio communication platform, a cellular radio communication platform, a GSM-5G radio communication platform, a long-range communication platform, a short-range communication platform, a radio frequency identification communication platform, and a near-field communication platform. In one or more embodiments, the tracking device may establish a radio RF communication connection using an ad-hoc protocol or connect with an Internet of Things (IoT) device. The tracking device may be configured to communicate using one of the radio communication platforms and transmit location information to a network interface of a computing system.

[0227] In the example, method 300A may include, in block 328A, obtaining location information by a tracking device, and in block 330A, transmitting location information by the tracking device via an available wireless communication platform.

[0228] The tracking device may include an Inertial Navigation System (INS) for environments where a Global Navigation Satellite System (GNSS) is not available. In environments without GNSS, acquired position information can be obtained from the INS. The tracking device may include a Global Positioning System (GPS) unit. If available, the tracking device may include other positioning protocols or position-derivable locations based on the location of surrounding devices such as IoT devices, Bluetooth-enabled devices, or RF access points. IoT devices, Bluetooth-enabled devices, or RF access points can be found, for example, in hotels, cruise ships, airports, restaurants, shops, and buildings. RF access points may support a variety of RF communication platforms, including but not limited to Wi-Fi communication protocols or GSM-5G communication protocols.

[0229] In underground locations, the tracking device may be an ad-hoc node for airport personnel devices to distribute location information from underground to either a wired or wireless network above ground, and therefore the mobile ad-hoc communication protocol can be used.

[0230] Location information can be transmitted to a network interface of a computing system associated with at least one processor of system 100, a computer system designated to track the tracking device, or a computer system associated with an airline or other mobile vehicle. The location information may include location coordinate data of the tracking device and information loaded from the BSM.

[0231] In addition to providing location information, tracking devices can operate in other modes to interact with devices in moving vehicles, including but not limited to kiosks, RFID receivers, baggage handling systems, and passengers' mobile communication devices.

[0232] As a non-limiting example, tracking devices may be collected or removed at the end of a travel segment, such as at the end of a flight, the end of a cruise, or the end of a stay at an accommodation. After removal, tracking devices may be reprogrammed for different passengers' luggage to be reused in a travel mode, for example.

[0233] In one or more embodiments, the tracking device may be assigned to the entire round trip, including multiple modes of travel. At the end of the round trip, the detached tracking device may be reprogrammed, for example, for reuse during the entire round trip, for different luggage belonging to a different passenger.

[0234] Figure 3B shows a flowchart of method 300B for tracking luggage according to an embodiment. Method 300B may include determining whether there is a baggage tracking device (i.e., a wireless tracking device 40). If the determination in block 302B is "no", method 300B may terminate in block 303B. If the determination in block 302B is "yes", method 300B may include entering the registered passenger's baggage tracking device information into the registered passenger profile in block 304B.

[0235] Method 300B may include determining in block 306B whether the passenger is on the current journey. If the determination in block 306B is "no", method 300B may return to the beginning of block 306B. If the determination in block 306B is "yes", method 300B may obtain geolocation data in block 308B using a baggage tracking device on the luggage. Method 300B may include recording the obtained geolocation data in a travel history tracker in 310B.

[0236] Contactless parking payment Figure 4A shows a flowchart of a method 400 for contactless parking payment according to an embodiment. The system 100 can enable registered passengers (i.e., registered users) to store data in their registered passenger profile 122, thereby enabling contactless parking payments when the registered user drives the vehicle to a hotel, leisure site, or accommodation.

[0237] Currently, parking lots allow users to pay for parking in advance by exiting the transportation system and paying at a dedicated payment machine or kiosk. However, there can be long queues to use the payment machines. In other cases, users may feel uneasy when in dark or unfamiliar places. Furthermore, at other times, the machines may malfunction or the user's payment method may not be accepted for various reasons. Considering these reasons, users may be able to download an application for parking lots to pay for parking. However, each parking lot owned by a different company may require users to download a different application to their mobile device. This can be even more difficult if the user is an out-of-town traveler who does not have direct knowledge of the parking lot / garage owner to obtain the application from.

[0238] When popular events are held at the venue, parking can become more difficult. Nearby parking lots and garages can fill up quickly. Finding an available parking space can be difficult because one may not realize that there are no available parking spaces until they have moved from one floor to another. In one or more embodiments, a computing system for a parking lot or garage can transmit information representing available parking spaces to a processor in system 100.

[0239] Method 400 may include determining in block 402 whether the registered user has signed up for the contactless parking payment service in the registered user profile (i.e., registered passenger profile 122, Figures 1A-1B). The registered user profile may store the global multi-mode mobile bag tag number associated with the registered user's luggage.

[0240] If the determination in block 402 is "no", method 400 may terminate in block 403. If the determination in block 402 is "yes", method 400 may include entering the registered passenger's vehicle license plate number (VLPN) 196 into the registered passenger profile 122 (i.e., registered user or registered traveler) in block 404. The VLPN 196 can be entered using the passenger registration GUI 124. Method 400 may allow a user or traveler (i.e., passenger) to pre-register their vehicle for the contactless parking payment service. However, the user or traveler may rent a vehicle as an alternative, which will be discussed later.

[0241] In one or more embodiments, a user can provide an image of the license plate of their vehicle. The processor can also use computer vision or machine learning algorithms to convert the digits into machine-encoded, readable text and store the digits of the text as a registered VLPN.

[0242] For example, a registered user may be traveling to a hotel, resort, or accommodation using their own transportation. The hotel, resort, or accommodation may have a transportation license plate scanner that determines the entry of the transportation into the parking lot. System 100 can pay parking fees without the user needing to use a credit card or to activate a parking ticket using the hotel, resort, or accommodation. Scanned license plates read by the scanner 75 (Figure 1B) in the parking garage associated with the hotel, resort, or accommodation, or a vendor of the hotel, resort, or accommodation, may then be transmitted to the web server 112 for payment of parking fees. In one or more embodiments, System 100 may offer discounts on parking fees or other member value points that can be transferred to services provided directly or indirectly by System 100.

[0243] Method 400 may include determining in block 406 whether a registered user has a reservation, either by PNR number or from TMI information received from a reservation system. The reservation may be, for example, for a hotel, amusement park, or accommodation. The reservation may also be for a rental car. For brevity, in this example, “reservation” may also refer to information that matches demographic information stored as PI129. The matching information may include information that includes location data, historical data from past events attended or registered via hotel reservations, etc. Method 400 may include determining in block 407 whether a registered user has a hotel reservation. If the determination is “no”, Method 400 can proceed to block 409.

[0244] In one or more embodiments, in block 406, TMI information may be received before or after the VPLN information is received from the computing device of the parking system by a process of system 100. The PNR database 63C (Figure 1B) may be accessed using the PNR number. In block 406, method 400 may include the system 100 processor querying a hotel reservation system associated with a hotel company to determine whether a hotel reservation exists for the traveler. In one or more embodiments, in block 406, method 400 may include the system 100 processor accessing stored PMM travel information stored in the traveler profile to retrieve reservation information. In block 406, method 400 may include the system 100 processor querying demographic information, membership, and travel history 184. In block 406, method 400 may include the system 100 processor querying recent purchases of tickets for sporting events, entertainment events, conferences, trade shows, etc. The information associated with these purchases can be used to identify the dates, locations, and time slots when parking sports may be required.

[0245] If the determination in block 406 is "no", then in block 409, it can be determined whether the system has identified that the user is tracking their location. If the determination in block 409 is "no", then method 400 can terminate in block 403. If the determination in block 409 is "yes", then method 400 can proceed to block 411, as described later. In block 409, it should be understood that if the user provides permission to track the location of their mobile communication device either over any travel section or locally to get to an event, for example, they can use system 100 to find a parking space.

[0246] If the determination in block 407 is "yes", method 400 may include determining in block 408 whether a rental car reservation has been found. The rental car reservation may be received from TMI information or from a query by the system 100's processor. If the determination in block 408 is "no", method 400 may set the current VLPN in block 410 to a VLPN stored in the registered passenger profile 122. If the determination in block 408 is "yes", method 400 may include receiving the rental car (RC) license plate number (LPN) in block 412. In one or more embodiments, for example, it may be possible to determine whether there is a match between a registered traveler's rental car reservation and a hotel reservation during overlapping time slots.

[0247] In one or more embodiments, the license plate number of the rental car may be received via the reservation system. In one or more embodiments, the license plate number of the rental car may be received by the system's processor from the registered user's or traveler's mobile communication device. The license plate may be registered under the contactless parking service function. As a non-limiting example, a registered user may capture an image of the rental car's license plate and transmit it to the system 100 for registration under the contactless parking service function. Since it is a rental car, the use of the license plate may be valid, for example, for the duration (i.e., time window) of the rental car reservation.

[0248] The processor can, for example, use a computer vision or machine vision algorithm to convert the digits in the image into machine-encoded, readable text. The text of the VLPN associated with the rental car may be stored in the registered passenger profile. Method 400 may include having the processor store the digits of the registered VLPN associated with the rental car.

[0249] Method 400 may include setting the current VLPN to the rental car (RC) license plate number (LPN) in block 414.

[0250] Method 400 may include, in block 416, having the processor receive information representing an acquired VLPN from a parking garage scanner 75 that communicates with a computing device of a hotel, resort, or accommodation facility's parking system.

[0251] In one or more embodiments, a parking garage may include a scanner for capturing the face of a transport vehicle driver. The computing system of PK71 can perform facial recognition to recognize and match the driver's identity. The computing system of PK71 can transmit facial identification information or images to the processor of system 100. In one or more embodiments, the computing system of PK71 can transmit information about the availability of parking spots to system 100. For brevity, the processor of system 100 can communicate with the computing systems of other parking lots or parking garages to determine their availability. These parking lots and garages can enable contactless parking via system 100 by communicating VLPN, driver identification information, or facial images in accordance with contractual agreements.

[0252] Method 400 may include in block 417 determining whether a match has been found between the VLPN and / or face (i.e., identification information) stored in profile 122 and the system's processor. If the determination in block 417 is "yes", method 400 may proceed to block 418. In block 418, method 400 may include notifying the user of the match result via the user's mobile communication device. In this case, the amount of the parking fee may also be sent to the user.

[0253] Method 400 may include, in block 420, having the processor of system 100 deduct or charge a fee from the passenger's (i.e., user) account (i.e., credit card or bank transaction information) using a payment method recorded in the registered passenger profile 122. Method 400 may also include, in block 422, having the processor of system 100 make a payment to a hotel, leisure facility, accommodation, or corresponding parking facility 71 (Figure 1B). Block 422 may include, having the processor of system 100 cause a financial institution to transfer funds to an account for the hotel, leisure facility, accommodation, or corresponding parking facility 71 (Figure 1B) via an automated clearinghouse (ACH) network. Alternatively, Method 400 may record the use of the service and the amount of the parking fee.

[0254] If the determination in block 417 is "no", method 400 can proceed to block 424, where the traveler may be notified of the match result via their mobile communication device. Method 400 can then proceed from block 417 to block 403 and terminate the process.

[0255] Returning to block 411, system 100 can, with the user's permission, track the location of its mobile communication device. The GUI of system 100 can enable the system to automatically find parking spaces in block 411, or at the user's request, for events or other purposes.

[0256] Method 400 may include, in block 413, having the system 100's processor identify the location of a parking space (i.e., a parking lot or garage). Identifying the location of a parking spot may include having the system's processor display its location on a map shown on a display screen showing the user's current location on their mobile communication device. The system 100's processor may use the mobile communication device's current location data to indicate the proximity of a parking spot and the direction to that parking spot. In one or more embodiments, the system 100's processor may use the mobile communication device's current location data to indicate the proximity of multiple parking spots and the direction to those parking spots. Multiple parking spots may be ranked by their proximity to the user's current location. Multiple parking spots may be ranked by their proximity to an event location. Multiple parking spots may be ranked by their parking fee. Metadata such as proximity data, parking fee, and direction may be superimposed on the map.

[0257] Figure 4B shows a flowchart of a method 430 for accessing Type B messages for travelers using contactless parking payment, according to an embodiment. Type B messages are generated by BHS63B (Figure 1B) and can be stored, for example, in a computing system associated with the airline the passenger is traveling with. In one or more embodiments, system 100 can receive Type B messages and sort the messages based on a master travel inventory.

[0258] In one or more embodiments, method 430 may include matching a Type B message in block 432 against a registered passenger in a master travel inventory 109 having a registered passenger record created by the system 100 processor from a registered passenger profile 122 for multimode travel management. The Type B message may be stored in a Type B message database 107. In this case, the matching may include matching at least one of the following: passenger name, PNR number, or IATA bag tag number. For example, a passenger may not be using baggage handling services and may not be transporting their own baggage. In one or more embodiments, a passenger may allow baggage handling services to bring their luggage onto the cruise ship for transport or special handling while they are staying at a hotel for one or more nights before commencing sailing.

[0259] Method 430 may include, in block 434, determining by the system 100's processor that the Type B message is a departure baggage source message to the destination airport. If the determination in block 434 is "no", method 430 terminates in block 436.

[0260] In block 434, if the determination is "yes", the Type B message indicates that the luggage has finished its journey from the current airport's perspective. However, the registered passenger may have hotel and / or rental car reservations and travel independently of their luggage. Reservations may be obtained from a corresponding reservation computing system or by querying a computing system using PMM information. In this case, method 430 can loop to Figure 4A in block 402 to determine whether the registered passenger is registered for contactless parking payment.

[0261] The method in Figure 4B can be used for travelers using airline travel segments followed by hotel stays. The method in Figure 4A may be used alone, such as when a traveler travels along a travel segment to a hotel, resort, or accommodation using their own car or a rental car. A master inventory may contain one or more master inventories. A master inventory may include an inventory for travelers traveling by airline. A master inventory may include an inventory for travelers traveling by train. A master inventory may include an inventory for travelers traveling by bus. A master inventory may include an inventory for travelers traveling by ground vehicles such as rental cars. A master inventory may include an inventory for travelers who have made reservations at accommodations, on cruise ships, or with other modes of transport.

[0262] Baggage item list Figure 5 illustrates a flowchart of Method 500 for generating and / or updating a baggage item inventory record according to an embodiment. Method 500 may include, in block 502, using at least one electronic acquisition device to acquire a representation of a Global Multimode Movement (GMMT) code indication on a circuit board associated with a permanent bag tag on a first piece of baggage of a registered passenger, in order to create a digital GMMT data record linked to a registered passenger. The GMMT code indication may be conformed to an IATA license plate.

[0263] Method 500 may include, in block 504, the processor accessing the GTE-BSM, which includes the passenger reservation record (PNR) number of a registered passenger, using a unique identifier representing a digital GMMT data record created from a computer system related to the multimode baggage handling service.

[0264] Method 500 may include, in block 506, having the processor retrieve reservation information for travel segments having travel modes for registered passengers from a computing system associated with travel modes based on PNR numbers.

[0265] In one or more embodiments, block 506 can include the processor retrieving check-in information for the return travel segment of a registered passenger by a designated return carrier using information associated with the PNR number. The checked item list record can be loaded with the retrieved check-in information for the return travel segment of the trip.

[0266] In one or more embodiments, the steps of block 506 can include the processor retrieving reservation information for a travel segment having a travel mode for a registered passenger from a computing system associated with the travel mode based on the PNR number.

[0267] The steps in block 506 can include the processor querying a reservation system associated with an airline for the airport location of the destination of the checked item travel itinerary, the processor querying a reservation system associated with a hotel company for a hotel reservation location for the checked item travel itinerary, and the processor querying a reservation system associated with a cruise line company for a cruise reservation location for the checked item travel itinerary, including one or more of the foregoing. Querying the reservation system for PMM travel information and any reservation data found can be used to construct the checked item travel itinerary records shown in FIGS. 11A-11C.

[0268] The steps of block 506 can include entering at least one of destination airport location information, hotel reservation location information, and cruise reservation location information into the checked item travel itinerary record. In one or more embodiments, the reservation information can include an airline reservation.

[0269] Method 500 may include, in block 507, having the processor link the registered passenger's GTE-BSM to at least one airline baggage source message (A-BSM) for each baggage item, including a first baggage item associated with the registered passenger in the GTE-BSM, each baggage item having a corresponding A-BSM. The A-BSM includes the IATA license plate number of the registered passenger's baggage.

[0270] The steps in block 507 may include, by the processor, accessing an airline baggage source message (A-BSM) stored in a memory device coupled to a computer system associated with an airline travel company, merging one or more fields of the A-BSM into a GTE-BSM, and storing, indexing, or addressing the GTE-BSM having the merged fields of the A-BSM in a computer system for multimode baggage handling services. While the foregoing is intended to link with airline messages, the disclosure is not limited to and may include adding other message types or information obtained from databases of other modes of transport or vehicles.

[0271] Method 500 may include the processor entering a baggage inventory record at one or more of the destination airport location, hotel reservation location, or cruise reservation location. Other modes of travel may include train, bus, and / or ferry vehicles.

[0272] Method 500 may include, in block 508, having the processor automatically create a baggage item list record from one or more of the reservation information, GTE-BSM, or PNR numbers.

[0273] Method 500 may include, in block 510, having the processor determine whether another passenger is part of or associated with a PNR number in addition to the name of the registered passenger. If the determination in block 510 is "no", method 500 may terminate in block 512. If the determination in block 510 is "yes", method 500 may include, in block 514, having the processor link the registered passenger's GTE-BSM to each passenger name associated with a PNR number within the GTE-BSM.

[0274] In a scenario where the booking information includes an airline booking, the step in block 514 may include the processor linking the registered passenger's GTE-BSM to each airline baggage source message (A-BSM) for each piece of baggage for each passenger name (unregistered passenger) associated with the PNR number in the GTE-BSM, with each piece of baggage having a corresponding A-BSM. For other vehicles, other messages may be appended to the GTE-BSM for each passenger name associated with the PNR number.

[0275] Method 500 may include, in block 516, having the processor create a baggage inventory record for each piece of luggage of each passenger linked to the GTE-BSM. The baggage inventory record may include the names of registered passengers and each unregistered passenger.

[0276] The baggage item inventory record may be merged with the passenger inventory record of the inventory. In one or more embodiments, the inventory may be associated with a mode of transport (i.e., a vehicle).

[0277] Departure point transfer segment check-in Figure 6A shows a system 600 for digitizing baggage management and baggage check-in according to an embodiment. In one or more embodiments, system 600 may be part of system 100. System 600 may include its elements / components below the dashed line BB. However, the system may also include global bag tags 230 affixed to passengers' luggage, shown above the dashed line BB.

[0278] System 600 may include at least one first processor 610 and at least one second processor 626 that communicate with each other via wired or wireless communication. At least one second processor 626 may be connected to a tangible non-temporary memory storage device 690. System 600 may include at least one baggage storage area 634 for temporarily storing luggage. System 600 may include other computing devices 648 for retrieving bag tag identifiers or other information attached to luggage, as described later. The second processor 626 may communicate with one of the computing systems of computing system 628 via a network 624 such as the Internet or a public communication network. The second processor 626 may communicate with other computing systems with which passengers book travel segments.

[0279] In one or more embodiments, system 600 can interface with system 100 to receive P-BTI and link it to information in registered passenger profile 122 (Figures 1A-1B). The terms “registered passenger profile,” “registered traveler profile,” and “registered user profile” may be used as appropriate herein. For multimode travel itineraries, luggage 614 tagged with global bag tags 230 can be retrieved at any designated location entered, for example, by a registered passenger 616. This can be entered using a graphical user interface on a computing device or mobile communication device.

[0280] The first processor 610 may be a scanner or acquisition device for scanning the P-BTI 236 or 236' on the global bag tag 230, from which a representation of the P-BTI 236 on the board is acquired. The first processor 610 may capture an image of the registered passenger's driver's license 982 (Figure 9B) or identification information (ID) 620 to verify the identity of the registered passenger. In the case of trains, buses, and cruise ships, luggage may not need to be checked in within a specific slot. Therefore, luggage can be transported to the baggage storage area 634 before being transported to the destination for loading onto a train, bus, or cruise ship. However, in the airline's mode of transport, check-in slots are regulated for both passengers and luggage.

[0281] In one or more embodiments, the first processor 610 may receive a PNR number 630 or other identifier from a confirmed itinerary 718 (Figure 7) for a flight of at least one airline. The itinerary or booking data may be stored in a PNR database 63C. The first processor 610 can receive information from the confirmed itinerary 718 to verify the identity of the passenger associated with the PNR number in order to retrieve the baggage associated with the PNR number and transport it from passenger position 605 to baggage position 634. The confirmed itinerary 718 (Figure 7) may be created, for example, by a computer system 628 (i.e., booking system 62 in Figure 1B) associated with an airline or travel management system (TMS). In one or more embodiments, the confirmed itinerary may be for other modes of travel for which the PNR number is generated by other booking systems or TMSs described herein. Each booking system may have a PNR database containing booking information. The PNR database 63C may include check-in information for the return travel segment of a registered passenger by a designated return travel carrier. Data for the return journey can be accessed using the PNR number and instructions from the airline.

[0282] In one embodiment, the system 600 includes an imaging device that communicates with a first processor 610. The imaging device and the first processor 610 may be integrated into a single device such as a smartphone, mobile communication device, tablet, notebook, or other camera-enabled portable computing device. The imaging device can capture images (hereinafter referred to as "LI images 606") of each piece of luggage (LI) 614 associated with P-BTI 612 before departing from passenger position 605.

[0283] In one embodiment, the imaging device may capture an image of an identification device 620 assigned to a passenger (hereinafter referred to as "ID image 604"). The user of the first processor 610 and the imaging device may verify the passenger's identification information to match the PNR number 630 and P-BTI 612. The PNR number 630 may be associated with at least one person. However, when collecting at least one piece of luggage 614, it may be sufficient to verify only one individual in the PNR number. In one or more embodiments, all passengers must be present, and all identification information of adult passengers is verified.

[0284] The first processor 610 may communicate the PNR number 630, verification 602, ID image 604, LI image 606, geographic location (LOC) information 608, and P-BTI 612 (i.e., P-BTI 236 or 236') in bracket 632 to the second processor 626. In a non-limiting example, a smartphone or other mobile computing device may include a Global Positioning System (GPS) receiver that receives signals from GPS to locate the first processor 610. The digitized information in bracket 632 may be used to eliminate the need for printed valet tags for tagging luggage. Verification 602 may include, for example, verification of the identity of a registered passenger. Verification 602 may include verification of other information, such as confirmation of the purchase of a ticket or other ticket for travel on a moving vehicle.

[0285] Verification 602 may include verifying a passenger's identity using a state-issued eligible driver's license or identification information in a TSA-approved digital wallet on a mobile communication device. In one or more embodiments, a passenger may download a TSA-approved digital ID application. TSA.gov provides examples of mobile driver's license and digital identification information requirements for Apple Wallet, Google Wallet, and Samsung Wallet. Other applications are from state DMVs, such as the California DMV Wallet Application. Yet another application, such as the American Airline Digital ID Application, may be available from airlines.

[0286] Verification may include confirmation of a reservation. Verification 602 may include, for example, verification of the identity of an unregistered passenger listed in a PNR database and associated with a PNR number. This may include verification of the person's identity and, in one or more embodiments, verification of the purchase of a ticket or other ticket for travel. The verification process may include performing facial recognition based on images of registered passengers and stored images of registered passengers. The verification process may authenticate the person's identity using the Department of Transportation (DMV) records or other authenticated facial recognition databases. In one or more embodiments, other biometric data such as fingerprints or retinal scans may be used.

[0287] The carry-on position 634 can accommodate other items 638 and 686. The item 686 can include a tracking device 680. The item 638 can include a tracking device 642. As a non-limiting example, when the frame of each item is open for check-in, the tracking device may be activated by a computing device 648 via a signal 650 to locate a particular item, and the tracking device 642 or 680 may transmit an audible alarm or a voice or visual indicator. Items can check in with a DCS 63A (Figure 1B) (i.e., a computer system) associated with an airline using an Internet communication or the infrastructure of a public communication utility.

[0288] The tracking devices 642 and 680 are examples of temporarily assigned tracking devices. These tracking devices can be programmed, for example, with a GMMT bag tag number and / or a PNR number. Any of the group of items can be programmed with a GMMT bag tag number or a PNR number.

[0289] Figures 6B - 6D show flowcharts of methods for checking in passengers and / or generating an item inventory according to an embodiment.

[0290] Referring particularly to Figure 6B, the method 660 can include, at block 662, electronically obtaining, by an electronic acquisition device, a representation of a global multi-mode mobility (GMMT) code display associated with a global bag tag on a substrate on a first item of a registered passenger to create a digital GMMT data record linked to the registered passenger.

[0291] The method 660 can include, at block 664, by at least one processor, accessing a GTE-BSM including a PNR number of a registered passenger using a unique identifier representing a digital GMMT data record from a computer system associated with a multi-mode baggage handling service.

[0292] Method 660 may include, in block 666, using information associated with the PNR number, retrieving check-in information for a passenger's travel segment by a specified mobile carrier using at least one processor.

[0293] Method 660 may include, in block 668, checking in a first piece of luggage with a designated transport carrier by at least one processor based on the retrieved transport segment check-in information. The check-in process may vary depending on the type of transport vehicle. For example, checking in for a transport segment via a cruise ship may differ from the check-in process for a transport segment via an airline. The airline check-in process is illustrated with Figure 10B. An exemplary process 668' for checking in with an airline for a return flight is illustrated with reference to Figure 6C. To check in with a cruise ship, it may be necessary to present a passport, driver's license, real ID, birth certificate, or other certificate of nationality required by the government of each country.

[0294] Method 660 may include, in block 670, having a processor automatically create a baggage item inventory record from digital GMMT data records and PNR numbers. The baggage item inventory record may include data for checking in baggage for the travel segment by a designated mobile carrier. The check-in data may vary based on the mobile vehicle.

[0295] In one or more embodiments, baggage item inventory records may be merged into or imported into a VOT inventory. This may be part of the check-in process for a particular VOT. The VOT check-in process may verify that a ticket has been purchased. The VOT check-in process may verify the identity of the passenger.

[0296] Referring particularly to Figure 6C, process 668' may include determining in block 672 whether the check-in is a return flight check-in. If the determination is "no", process 668' may terminate in block 676. If the determination in block 672 is "yes", process 668' may include, in block 674, electronically obtaining, using an electronic acquisition device, a representation of the Departure Airline Bag Tag Identifier (A-BTI) associated with or printed on a printed bag tag from the Departure Airline on the first piece of baggage of the registered passenger, and creating a digital A-BTI data record linked to the Departure Airline. The A-BTI includes the IATA license plate, and the A-BTI data record represents the IATA license plate number. The acquisition device may scan a barcode on an IATA bag tag or another marker that has the IATA license plate number and convert the barcode into a digital number plate number. The step for creating a baggage item inventory record may include using information from the digital A-BTI data record and the PNR number in block 670.

[0297] Process 668' may include, in block 678, scanning an IATA bag tag to obtain a return flight from, for example, a PNR database associated with an air travel company, and then, based on the retrieved or stored return flight data, checking in a first piece of luggage or passenger and the first piece of luggage to a designated return travel carrier by at least one processor. The process may check in other pieces of luggage in the same process.

[0298] Process 668' may include, in block 679, causing at least one processor to cause a printing device to print an IATA bag tag for the return flight with a specified return travel carrier. Once the baggage is checked in, the DCS can generate an IATA bag tag for the return flight. However, scanning either the origin IATA bag tag or the GMMT bag tag may be used to print an IATA bag tag for the return flight later using a graphical user interface.

[0299] The check-in process can be repeated for unregistered passengers, as described in relation to Figures 10B and 10C. Therefore, the process in Figure 6C can be performed for unregistered passengers, including those with IATA bag tags from their departure flight. This process can be repeated for additional baggage.

[0300] Referring particularly to Figure 6D, block 664 may include the various steps shown in Figure 6D. The process of method 660 or block 664' may include, in block 663A, obtaining from an electronic acquisition device a representation of an acquired global multimode movement (GMMT) code display associated with a global bag tag on a substrate on the first piece of luggage of the registered passenger, in order to create a digital GMMT data record linked to the registered passenger.

[0301] The process of method 660 or block 664' may include, in block 663B, electronically obtaining by at least one processor a representation of at least one preferred multimode (PMM) travel code display representing at least one PMM travel code on a circuit board associated with a bag tag on a first piece of luggage, in order to create a digital PMM data record linked to a registered passenger.

[0302] The process of method 660 or block 664' may include, in block 663C, the processor receiving electronic communications from an acquisition device, the communications including tracking information including the acquisition device, time, date, and geographic location data related to GMMT data recording or PMM data recording.

[0303] The process of method 660 or block 664' may include, in block 665, accessing PMM movement information related to digital PMM data recording in a database of a computer system associated with a multimode baggage handling service by at least one processor.

[0304] The process of method 660 or block 664' may include recording, in block 665', tracking information in a registered passenger profile or registered passenger travel history database by at least one processor.

[0305] Figure 7 shows an exemplary confirmed itinerary 718 for an air flight according to an embodiment. The confirmed itinerary 718 includes at least one of the PNR number 630, passenger name, flight reservation information, and purchased ticket number.

[0306] Figure 8 shows an airline baggage source message (A-BSM) 800 for an airline. The airline generates and / or stores one or more B-type messages. One or more of the B-type messages may be generated by BHS63B (Figure 1B) when baggage is transported and tracked through the airport environment. The B-type messages may include one or more of the following: baggage transfer messages (BTM), baggage source messages (BSM), baggage processing messages (BPM), baggage unloading messages (BUM), baggage unconfirmed messages (BNS), baggage control messages (BCM), baggage inventory messages (BMM), and baggage requests (BRQ). The IATA bag tag number is part of the baggage message. System 100 can also store or access B-type messages generated on the day of travel by BHS63B (Figure 1B) for the airline for registered passengers and associated unregistered passengers to assist in the recovery of anomalous baggage.

[0307] The A-BSM800 can be communicated via teletex or other communication methods. It should be understood that each airline has its own A-BSM format. The accessed A-BSM should have a Passenger Reservation Record (PNR) number. The PNR number may contain alphanumeric characters. The A-BSM is an IATA-compliant BSM created by the airline's computing system, for example, when a passenger checks in for their flight, and can indicate, for example, the intention to check in luggage. The A-BSM is created by the airline's computer system, for example, when a passenger checks in for their flight at the airline's counter.

[0308] An A-BSM is a BSM that is a Type B message. The "A" is used to distinguish it from global BSMs created by System 100. A Type B message may contain multiple data fields, including encoded characters. For example, the encoded characters may include, for instance, American Standard Code for Information Interchange (ASCII) code, Baudot, and Padded Baudot. The code and format for baggage information messages or Type B messages are, for example, "Recommended Practice 1745 Baggage Information Messages" by IATA, in the Passenger Services Resolution Manual, June 2010, 30 th This is explained in Edition, pp. 1110-1205.

[0309] A Type B message may include a field or line 802 containing a header. For example, the header may be labeled "BSM," representing the initial heading of an A-BSM. A field or line 804 may include ".V / " followed by a set of alphanumeric characters at the beginning of the line. As a non-restrictive example, the ".V / " at the beginning of the line may indicate the version and supplementary data. For example, the supplementary data may include the transfer station in an airline environment. The .V / data field may indicate whether a Type B message, such as a BSM, is a termination BSM. The .V / data field includes a number after the " / " indicating the version number of the data dictionary. The following character may be a baggage source indicator, indicated by "L" for Local, "T" for Transfer, "X" for Terminating, or "R" for Remote. The baggage source indicator is followed by a three-digit airport code. In this example, the BSM is a transfer BSM with version number 1 and airport code JFK.

[0310] Field or row 806 may contain a series of alphanumeric characters representing the departure flight number and date, starting with "F / ". These alphanumeric characters can be separated by the " / " symbol. For example, the data "22MAY" could represent the arrival date. The code "IST" represents Istanbul Airport.

[0311] Field or row 808 may contain a series of alphanumeric characters representing the flight number and date of an arriving flight, following the line prefix "I / ". These alphanumeric characters can be separated by the symbol " / ". For example, the data "12MAY" could represent the departure date. The code "SLC" represents Salt Lake City Airport.

[0312] Field or line 812 may contain a set of numbers followed by a line prefix ".N / ", some of which represent A-BTI as printed on the IATA bag tag. Field or line 810 may contain a set of letters followed by a line prefix ".P / ", which represents the passenger's name. The name may be separated by a surname and a slash " / ".

[0313] Field or line 818 may contain a set of alphanumeric characters followed by a line prefix ".L / ", which represents a Passenger Reservation Record (PNR) number. The PNR number also points to a locator. Field or line 820 may contain a message end indicator such as "ENDBSM".

[0314] Between lines 802 and 820, other fields or lines may exist, such as fields 814 and 816. Field or line 814 has the prefix ".S / " and is matching data. Field or line 816 has the prefix ".W / " related to the weight, pieces, dimensions, and type data of the luggage. Thus, the airline type B message is known in the art. No further explanation will be given for type B messages. Some fields / lines are mandatory, while others are optional depending on the type B message.

[0315] The exemplary A-BSM800 is provided for illustrative purposes only and is not intended to be limiting. Each airline may make changes to its airline BSM. Type B messages have required fields, but some fields may be changed at the airline's discretion.

[0316] Figure 9A shows a Global Tracking Extended Baggage Source Message (GTE-BSM) 900 (i.e., GTE-BSM 141) according to an embodiment. Figure 9B shows a Global Tracking Extended Baggage Source Message (GTE-BSM) link structure 950 according to an embodiment. The GTE-BSM link structure 950 will be described together with Figure 9A. The GTE-BSM link module 173 may be configured to link information to each other as described in the GTE-BSM link structure 950 by addressing, indexing, and storing information, which may be accessible by scanning the passenger's global bag tag registered during the journey and / or by scanning the IATA bag tag if an air travel agency was used for at least one of the journey segments.

[0317] GTE-BSM900 can be permanent, as it continues for the same registered passenger with the same name and P-BTI for a predetermined validity period ranging from one month up to 10 years, one month up to 20 years, or until death or death. The information in GTE-BSM900 may be updated with new booking information associated with a new PNR number each time a new trip is made. As a non-limiting example, the new booking information may include arrival and departure information for flights, accommodation information, or other multimode travel information including information about cruise ship voyages, bus reservations, or train reservations. The fields in GTE-BSM900 are not limited to airline information. Instead, a GTE-BSM in GTE-BSM link structure 950 may include multiple vehicle travel information. A GTE-BSM may be used for a first travel segment, for example, with priority given to travel segments performed by an airline. The GTE-BSM template (hereinafter referred to as the "BSM template") may differ depending on the vehicle traveling (VOT). For example, if an airline is not used for any segment of the current travel itinerary from end to end, not all fields are required. GTE-BSM may not require certain fields from A-BSM, and only fields with relevant information for baggage tracking and handling may be required and retained. BSM templates for other vehicles may require information such as location, check-in time, departure time, gate, station, etc.

[0318] A Type B message may include a field or line 902 containing a header. For example, the header may be labeled "GTEBSM," representing the initial heading of GTE-BSM900. A field or line 904 may include ".V / " followed by a set of alphanumeric characters at the beginning of the line. As a non-restrictive example, the ".V / " at the beginning of the line may indicate the version and supplementary data. For example, the supplementary data may include transfer stations in an airline environment. The .V / data field may indicate whether a Type B message such as a BSM is a terminating BSM. The .V / data field includes a number after the " / " indicating the version number of the data dictionary. The following character may be a baggage source indicator, indicated by "L" for Local, "T" for Transfer, "X" for Terminating, or "R" for Remote. A three-digit airport code may follow the baggage source indicator. GTE-BSM can use the baggage source indicator in a similar manner to IATA Type B messages. However, in one or more embodiments, if a traveler is traveling by a means of transport other than an airplane, the three-digit airport code may be replaced with a different coding scheme to reflect the means of transport, such as a vehicle or other means of transport. VOT codes may be created using both numbers and letters. In one or more embodiments, VOT codes may contain more than two or three digits.

[0319] Field or line 906 may contain a sequence of alphanumeric characters representing the departure flight number and date, following the line prefix "F / ". The alphanumeric characters may be separated by the symbol " / ". A train number, ship number, or bus number may be used instead of the flight number.

[0320] Field or line 908 may contain a series of alphanumeric characters representing the flight number and date of the arriving flight, following the line prefix "I / ". The alphanumeric characters may be separated by the symbol " / ". A train number, ship number, or bus number may be used instead of the flight number.

[0321] Field or line 912 may begin with "N / " followed by a set of numbers, some of which represent the A-BTI digital BTI data record of the registered passenger's luggage. Field or line 910 may begin with ".P / " followed by a set of letters, which represents the passenger's name. The name may be separated by the suffix " / ", starting with the surname.

[0322] Field or line 918 may contain a set of alphanumeric characters followed by a line prefix ".L / ", which represents the Passenger Reservation Record (PNR) number. The PNR number also points to a locator. Field or line 920 may contain a message end indicator such as "ENDGTEBSM".

[0323] Between lines 902 and 920, other fields or lines may exist, such as fields 914 and 916. Field or line 914 has the prefix ".S / " and is matching data. Field or line 916 has the prefix ".W / " related to the weight, pieces, dimensions, and type data of the luggage. Thus, the airline type B message is known in the art. The type B message will not be described further.

[0324] The GTE-BSM900 may include a field or line 922 for the GMMT bag tag number, for example, with a prefix ".Z / ". The GMMT bag tag number may be "000123456 / 111". The code "000" may be an IATA code assigned to a non-boarding airline. However, other codes may be used. The sequence "123456" is, for example, the passenger's bag number. The code "111" may represent a PMM code. The " / " may separate the two digits or may be omitted.

[0325] The GTE-BSM900 may include the GMMT bag tag number in the ".Z / " field or another available field. The GTE-BSM900 of the GTE-BSM link structure 950 may include a field of the BSM outside the airline infrastructure to add current location data 984 from the tracking device 40 attached to the luggage. The tracking device 40 can receive primary ID (PID) data from the baggage handling device as described in relation to Figure 16A. The tracking device ID may be stored in the GTE-BSM900 of the GTE-BSM link structure 950, which has the location data.

[0326] The GTE-BSM900 may include, for example, fields in the BSM outside of the airline infrastructure for adding a link or locator number to banking information. The GTE-BSM900 may include fields in the BSM outside of the airline infrastructure for adding a link or locator number to personal information, such as information from a driver's license 982, as shown in Figure 9B.

[0327] As used herein, the term “link” may include, for example, the Hypertext Transfer Protocol (HTTP) or the Hypertext Transfer Protocol Secure (HTTPS). The GTE-BSM900 can communicate using a variety of protocols, including, but not limited to, Transmission Control Protocol / Internet Protocol (TCP / IP), File Transfer Protocol (FTS), Hypertext Transfer Protocol (HTTP), Hypertext Transfer Protocol Secure (HTTPS), Secure Sockets Layer (SSL), Secure File Transfer Protocol (SFTP), and User Datagram Protocol (UDP). Data may be indexed or addressed using hypertext links.

[0328] In one or more embodiments, if one of the moving vehicles is an airline, when the baggage is checked in with the airline, the GTE-BSM900 is updated and merged with the A-BSM data. The airline may have priority over other moving vehicles. This is because, if necessary, return flight information can be obtained using a departure hardcopy bag tag having an RFID bag tag displaying a printed A-BTI961 or IATA bag tag number (i.e., A-BTI), shown as 960 in Figure 9B of the GTE-BSM link structure 950. The departure hardcopy (airline) bag tag with a printed A-BTI or RFID bag tag can be used as a secondary linking mechanism for unregistered passengers in a group linked to registered passengers. The departure hardcopy bag tag, shown as 960 in Figure 9B, can also display a PNR number. This PNR number can be used to access PNR data from a database connected to a computer system associated with the airline. The PNR data in the PNR database 63C (Figures 1B and 6A) may include booking data.

[0329] The GTE-BSM link module 173, when executed, may include programming instructions that, in one or more embodiments, link one or more temporary baggage source messages (T-BSMs) 146 to the GTE-BSM 900, as shown in the dashed box 990 within the GTE-BSM link structure 950. The T-BSM 146 may include fields similar to those of the GTE-BSM, except that field or line 902 contains the header "TBSM". Furthermore, field or line 918 may contain a prefix ".L / " followed by a set of alphanumeric characters, which represents a passenger reservation record (PNR) number. The PNR number may be the same as or different from the PNR number of the registered passenger.

[0330] Field or line 910 may contain a line prefix ".P / " followed by a set of characters, which represents the name of an unregistered passenger. Field or line 912 may contain a line prefix "N / " followed by a set of numbers, some of which represent a digital BTI data record of the A-BTI of a registered unregistered passenger's luggage. The A-BTI in T-BSM146 can be printed on a departure hard copy bag tag 965 affixed to the unregistered passenger's luggage. In one or more embodiments, T-BSM146 may input airline carrier information if at least one of the means of transport is an airline.

[0331] Since T-BSM146 can be linked to GTE-BSM900, whenever a departure hard copy bag tag 965 is scanned, the scanning or retrieving device may provide baggage handler information about the group, but may be limited to the appropriate unregistered passengers. For example, in the case of a cruise ship, when a baggage handler scans a departure hard copy bag tag 965, the room number of a specific unregistered passenger may be presented. This allows for the saving of valuable resources by recycling the airline's printed departure hard copy bag tags 965 for use in other moving vehicles.

[0332] If the flights are the same, other information will also be the same. However, if the flights are different, the information within T-BSM146 may differ.

[0333] The T-BSM may include the GMMT bag tag number in the ".Z / " field or another available field. This links the T-BSM to the registered passenger's GTE-BSM900. The field may use other prefixes permitted by IATA regulations. The field may use two or three-digit prefixes such as ".XXX / ", where X represents a letter.

[0334] System 100 may include a mobile vehicle (VOT)-BSM generator 149 (Figure 1A) which may include programming instructions that, when executed, can generate a VOT-BSM. A VOT-BSM may be assigned to a registered passenger and linked to a GTE-BSM 900. Each VOT-BSM may be created for each additional travel segment and may be used to construct a travel route record that includes arrival and departure times and dates, as well as location. A VOT-BSM may include its own PNR number or may be linked to a single PNR number or a super PNR number.

[0335] For registered passengers, VOT-BSM151 may include the GMMT bag tag number in the ".Z / " field or another available field. This allows VOT-BSM151 to be linked to the registered passenger's GTE-BSM900 in the GTE-BSM link structure 950. In one or more embodiments, the PNR number may be a PMM code or travel member number linked to the travel segment reservation for the current travel itinerary. Field or line 910 may include ".P / " followed by a set of characters, which represents the name of the registered passenger. If the VOT does not have a baggage bag tag number, field or line 912 may include "N / " followed by a set of digits, some of which may represent the A-BTI digital BTI data record of the registered passenger's baggage or duplicate the GMMT bag tag number. In one or more embodiments, the three-digit airport code may be replaced with another encoding scheme to reflect the means of travel, such as the vehicle or mode of transport.

[0336] Box 995, indicated by the dashed line, includes at least one VOT-BSM 151 linked to GTE-BSM 900 of GTE-BSM link structure 950. Each T-BSM 146 for each unregistered passenger may also travel in one or more VOTs together with registered passengers, so one or more VOT-BSMs indicated by the dashed box 995' in GTE-BSM link structure 950 may be created via VOT generator 149 for each unregistered passenger and linked to their corresponding T-BSM 146. The PNR number may be the same as or different from that of a registered passenger. However, the VOT location, date slot and time slot should be the same so that reservations generally overlap.

[0337] In one or more embodiments, a registered passenger may have a longer stay reservation than at least one unregistered passenger.

[0338] Data from T-BSM and VOT-BSM may be stored in the member's travel history and linked as part of the GTE-BSM link structure 950. Unregistered passengers may also have their travel history stored for use in data analysis for future travel, resource allocation, and advertising.

[0339] Because a registered passenger may check in multiple pieces of luggage, an extra baggage BSM called "gte-BSM" 955 may be created when checking in the luggage of a registered passenger. Here, lowercase "gte" is used for distinction. Gte-BSM 955 may contain fields similar to GTE-BSM 900. In this case, the field or line 912 may contain a line-leading "N / " followed by a set of numbers, some of which represent a digital BTI data record of the A-BTI of the registered passenger's additional luggage. The origin hard copy (IATA) bag tag 962 may have the A-BTI of the additional luggage and can be affixed to the luggage, for example, as required by the airline. In some cases, the travel agency bag tag may be an RFID bag tag. An e-ink RFID display can display the A-BTI, which can be scanned by a scanner or received by an RFID reader. The ".Z / " field may contain the GMMT bag tag number. In one or more embodiments, the RFID reader acquires an RF signal to obtain an electronic representation of A-BTI.

[0340] Unregistered passengers may also check in more than one piece of luggage. In this case, one or more T-BSM146 forms may be generated for each unregistered passenger.

[0341] This specification describes the IATA Type B message code format for GTE-BSM. However, based on this specification, other coding formats and schemes can be used to create unique identifiers, structured message formats, and electronic linking media to link luggage to one another across multiple moving vehicles and communicate using Transport Control Protocol (TCP) / Internet Protocol (IP) communication technology and currently and future available control protocols.

[0342] Each of the T-BSM, gte-BSM, and / or VOT-BSM can be populated with the corresponding passenger's name, a link to the GMMT bag tag number, and a PNR number or super PNR number. Each of the T-BSM, gte-BSM, and VOT-BSM can be updated with travel section information or booking data and location data when the corresponding luggage enters its journey in parallel with and / or independently of its owner.

[0343] Figures 10A to 10C show flowcharts of Method 1000 for generating Global Tracking Extended Baggage Source Messages (GTE-BSM) for registered passengers and / or T-BSMs for current travel routes for one or more unregistered passengers, according to embodiments. A current travel route may have one or more travel vehicles (VOTs). Method 1000 is described in relation to the GTE-BSM 900 in Figure 9A and the GTE-BSM link structure 950 in Figure 9B.

[0344] Method 1000 may include, in block 1002, having the processor retrieve a GTE-BSM template, and in block 1004, entering P-BTI-related information into the GTE-BSM900 (Figure 9A). The GTE-BSM may include the P-BTI and the name of the registered passenger. Block 1001 includes blocks 1002 and 1004, which may be executed when the global bag tag is created. Other fields of the GTE-BSM900 (Figure 9A) may be updated for any travel itinerary of the registered passenger. For brevity, the BTM template may include a structure for storing or arranging the information necessary to track and handle luggage along an end-to-end travel itinerary using multiple travel modes or transport formats.

[0345] Method 1000 may include, in block 1006, having the processor obtain the PNR number of the current travel path.

[0346] Method 1000 may include, in block 1008, having the processor access the computer system of the reservation system associated with the PNR number to obtain a passenger list and travel itinerary information.

[0347] Method 1000 may include, in block 1010, having the processor determine whether there is a match between a passenger in the passenger list associated with a PNR number and a registered passenger. If the determination in block 1010 is "no", method 1000 terminates in block 1012. This means that the registered passenger may not be associated with the PNR number, or the PNR may be an incorrect number. System 100 may store programming instructions for accessing pre-stored instructions for accessing PNR data from a computer system associated with the source of the PNR number (mobile carrier or PMM mobile information).

[0348] If the determination in block 1010 is "yes", method 1000 may include, in block 1014, having the processor input a GTE-BSM template having a PNR number. Method 1000 may also include, in block 1016, having the processor obtain one or more VOTs from the PNR number of the baggage transfer record.

[0349] Method 1000 may include, in block 1018, if available, having the processor input inbound (arrival) and / or outbound (departure) information for the luggage of a first VOT from the PNR number into the GTE-BSM. A travel itinerary may include multiple VOTs. The GTE-BSM may be input with first VOTs occurring in the time series of the travel vehicle. In one or more embodiments, the GTE-BSM may include information that is merged from non-airline booking information, as described below, but subsequently updated with merged data from the A-BSM of registered passengers.

[0350] The GTE-BSM can be extended to include other fields or notes. Furthermore, the GTE-BSM may be updated during the current travel itinerary. For example, during the travel of an airline's baggage and / or passengers, the fields of the GTE-BSM may be merged with the A-BSM. The added fields may be used to add links to other Vehicles of Travel (VOTs) or VOT-BSMs. In one or more embodiments, the GTE-BSM900 may have the original hard copy bag tag number from the IATA license plate in the ".N / " field 912 if one of the VOTs is an airline. The ".Z / " field or other designated field may have the GMMT bag tag number.

[0351] Method 1000 may include determining in block 1019 whether there is an airline reservation. If the determination in block 1019 is "no", method 1000 can proceed to block 1046 in Figure 10C. If the determination in block 1019 is "yes", method 1000 can proceed to block 1020 in Figure 10B.

[0352] Referring here to Figure 10B, method 1000 may include in block 1020 having the processor determine whether the passenger has checked in with the airline. For example, in one or more embodiments, if registered passengers are traveling through an airline, they must check in with the airline within their check-in slot. For baggage handling services to check in their luggage within their check-in slot, the airline may require passengers to check in before checking in their luggage. If the determination in block 1020 is "no", method 1000 may check in the passenger in block 1022. Method 1000 may include in block 1025 sending the passenger a communication containing the passenger's ticket and / or a message indicating that the passenger has checked in for their flight. Block 1025 may then proceed to block 1026.

[0353] The check-in process in block 1022 or 1026 is also described in relation to Figure 6A. For example, when a passenger and / or their luggage are checked in for a departure flight with an airline, it may be necessary to verify the passenger's identity, as shown in Figure 6A, and / or for the purchase of a confirmed ticket. It may be necessary to verify the passenger's identity regardless of whether the passenger and / or their luggage were checked in from home, accommodation, resort, or cruise ship, or from a flight (outbound or return).

[0354] When a passenger specifies the baggage to be checked in, the airline's associated computer system can be instructed to create an A-BSM containing the IATA bag tag number. This process allows the airline's associated computer system to send the passenger a ticket. As a result, if the determination in block 1020 is "yes", method 1000 may include, in block 1024, accessing the A-BSM associated with the airline's computer system with respect to, for example, the passenger name and PNR number of the checked-in passenger or the airline reservation information. The A-BSM may include arrival and departure flight information that can be extracted for the current travel itinerary and added to the GTE-BSM.

[0355] Method 1000 may include checking in luggage for a registered passenger in block 1026 using information from A-BSM.

[0356] Method 1000 may include, in block 1028, for example, obtaining the A-BTI from the A-BSM associated with the airline's computer system when the passenger is a registered passenger, and merging the data from the A-BSM into the GTE-BSM900.

[0357] Method 1000 may include, in block 1030, having the processor access return flight information on a designated airline based on either the PNR number or airline reservation information, and adding the return flight information to the baggage item inventory record. Method 1000 may also include, in block 1032, having the processor print the origin IATA bag tags for checked baggage to a printer.

[0358] Method 1000 may include, in block 1034, having the processor count the checked baggage items.

[0359] A registered passenger may want to check in more than one piece of luggage. This requires checking in each piece of luggage. Therefore, method 1000 may include determining in block 1036 whether there is another piece of luggage. If the determination in block 1036 is "yes", method 1000 may include repeating blocks 1024, 1026, 1028, 1030, and 1032 for each extra piece of luggage (XL) that should be checked by the registered passenger. In the extra luggage scenario, in block 1028, method 1000 may include retrieving the A-BTI from the A-BSM associated with the airline's computer system and, for example, merging the data from the A-BSM into the gte-BSM if the passenger is a registered passenger. Here, the new A-BTI is inserted into the ".N / " field 912 but is located in the gte-BSM, which is linked to the registered passenger's GTE-BSM. The link to GTE-BSM is described in relation to block 507.

[0360] If the determination in block 1036 is "no", method 1000 may include determining in block 1038 whether there is another unregistered (NR) passenger in the group.

[0361] A registered passenger may, but is not required, be the primary passenger on the PNR number. For example, a parent may travel with a child. The data associated with the PNR number can list the child and parent. The registered passenger may be the parent. Method 1000 allows tracking and handling of other luggage using the registered passenger's P-BTI. System 100 can link unregistered passengers to a different PNR number than the registered passenger's for purposes such as retrieving or delivering luggage to a cruise ship voyage, resort, or accommodation for a group including unregistered and registered passengers.

[0362] Method 1000 also allows for the check-in of unregistered passengers and their luggage, or luggage only. This is achieved by blocks 1020, 1022, 1024, 1026, 1028, 1030, and 1032, but for unregistered passengers. In this case, once the A-BTI information is obtained, the data is merged into the T-BSM instead of the GTE-BSM. The T-BSM is linked to the GTE-BSM of registered passengers.

[0363] If the determination in block 1038 is "yes", method 1000 may include creating a T-BSM in block 1040 and linking it to the registered passenger's GTE-BSM. Block 1040 can then return to blocks 1020 and 1042, and method 1000 may include tracking unregistered passenger names, luggage, and PNR numbers.

[0364] If the result in block 1038 is "no", method 1000 may include proceeding to block 1046 in Figure 10C.

[0365] Referring to Figure 10C, many travel itineraries involve two vehicles. The first vehicle may be a mode of transport such as an airplane, train, bus, ferry, cruise ship, or rental car. The second vehicle may be accommodation. In some cases, the mode of transport may also provide other vehicles such as accommodation. In other examples, the travel itinerary may include a single vehicle.

[0366] Method 1000 may include determining in block 1046 whether there is another VOT in the current journey. If the determination in block 1046 is "no", method 1000 may terminate in block 1048. If the determination in block 1046 is "yes", method 1000 may proceed to block 1050, where a VOT-BSM is created and may be linked to a GTE-BSM for registered passengers or a T-BSM for unregistered passengers. An exemplary operation of block 1050 is described below.

[0367] In block 1050, method 1000 may include obtaining a VOT-BSM template for VOT in block 1052, entering information related to the VOT reservation into the VOT-BSM in block 1054, and linking the VOT-BSM to the GTE-BSM if the passenger is a registered passenger, or to the T-BSM if the passenger is an unregistered passenger, in block 1056.

[0368] Method 1000 may include determining in block 1058 whether there is another unregistered passenger. If the determination in block 1058 is "yes", method 1000 may return to the beginning of block 1050 and repeat blocks 1052, 1054, and 1056. If the determination in block 1058 is "no", method 1000 may include determining in block 1060 whether there is another VOT. If the determination in block 1060 is "no", method 1000 may terminate in block 1062. If the determination in block 1060 is "yes", method 1000 may repeat block 1050 for the next VOT, and block 1050 includes the aforementioned blocks 1052, 1054, and 1056.

[0369] Method 1000 may include determining whether there is another unregistered passenger in block 1064. If the determination in block 1064 is "yes", method 1000 may return to the beginning of block 1050 and repeat blocks 1052, 1054, and 1056. If the determination in block 1064 is "no", method 1000 may include returning to block 1060.

[0370] Once all moving vehicles have been entered into the BSM template and linked to the GTE-BSM for registered passengers and any unregistered passengers of their associates, method 1000 can terminate in block 1062.

[0371] Figures 11A to 11C show a Baggage Transfer Route Record (BTJR) according to an embodiment. The BTJR can create one or more records of the baggage item inventory.

[0372] Figure 11A shows a BTJR1154A created for a passenger registered for a round-trip journey using multiple modes of travel, according to an embodiment. The passenger can receive communications via the message communication unit 178 to a mobile communication device designated by the passenger or another computing device. Messages may be sent by text, email, or computer-generated communication. Messages may indicate status updates as described herein.

[0373] The system uses a scanner or other acquisition device to acquire the P-BTI (Figure 2B) from the global bag tag 230. The scanner may be part of the system described in U.S. Patent No. 11,682,241, issued June 20, 2023, “RETURN LEG REMOTE PASSENGER CHECK-IN,” which is incorporated herein by reference. The scanner may be dockside, on a moving vehicle, or carried by baggage delivery and handling personnel and may be configured to scan barcodes, such as the P-BTI, and to communicate the P-BTI to the system 100. The system may update BTJR1154A, 1154B, and 1154C, for example, by confirming the presence of passenger baggage ready to be loaded onto any moving vehicle of the currently listed PNR. The system uses a scanner or other acquisition device to acquire the representation of the printed origin hardcopy bag tag identifier (OH-BTI) associated with the printed bag tag from the originating airline, or the IATA bag tag number plate for use in a calculation device.

[0374] With each scan, the scanner or acquisition device communicates its and the acquisition device's location, as well as P-BTI, to the system. Messages to the system may also include date and time data. In the case of a scanner or acquisition device with GPS or positioning capabilities, GPS data or other location data can be transmitted to the system to identify the location of the luggage. GPS data from the scanner or acquisition device is compared with predicted map location data to correlate the predicted location (EL) in BTJR with the scan point (POS). If there is a correlation between EL and POS, the indicator box described later may change color, symbol, or status.

[0375] In one or more embodiments, a passenger's mobile communication device or personal computing device may include a graphical user interface (GUI) configured to access a BTJR such as BTJR1154A, 1154B, or 1154C to be notified of the current location and / or status of their luggage.

[0376] In one or more embodiments, luggage may have a tracking device 40 attached to it. Such a tracking device may include a display device for displaying BTJR details. Passengers can access location data associated with the tracking device 40.

[0377] BTJR1154A may include one or more baggage handling fields 1102, 1104, 1106, 1108, 1110, 1112, 1114, 1116, 1118, 1120, 1122, 1124, 1126, 1128, and 1130. Each field includes an indicator box 1101 on the first side of the field. Each indicator box may be configured to show the status of the baggage when the P-BTI on the global bag tag 230 is scanned. For example, when the P-BTI on the global bag tag is scanned for arrival or departure, the indicator box 1101 may display an icon or color representing the status. A first color or icon may indicate an expected baggage that has not been scanned for arrival or departure. A second color or icon may indicate an expected baggage that has been scanned for arrival or departure. A third color or icon may indicate a "in transit" status between expected locations. Other colors and icons may be used to indicate other status states.

[0378] The baggage handling field provides instructions on the display device regarding how to handle the baggage, such as whether to pick it up or ship it. In some cases, for example, the baggage may need to be sent through customs.

[0379] Each baggage handling field may include various icons 1132 on a second side opposite to the first side of the field. The icons 1132 can distinguish different locations and modes of travel or vehicles to which the baggage should travel during the trip, whether parallel or independent to its owner. As a non-limiting example, the icons 1132 are for illustrative purposes only and are not intended to be limiting. BTJR can be displayed on a computing device, scanner, acquisition device, or display device associated with a web server in System 100.

[0380] To avoid congestion, some fields may be omitted. For example, possible additional fields related to the collection and delivery of luggage at the cruise ship's dockside in fields 1118 and 1120 shown in bracket 1140 are described in relation to Figure 11B. For example, fields 1118 and 1120 may include baggage handling fields 1152, 1153, 1156, 1158 and 1160, as described later in Figure 11B.

[0381] In the example, the registered passenger may be requesting to pick up their luggage from a designated address, such as their home address, but not limited to, as shown in field 1102. Once the baggage delivery and handling personnel have processed the luggage and / or the passenger, the P-BTI can be scanned on the global bag tag 230. This can cause the indicator box 1101 to change color or display an icon indicating a status update.

[0382] As a non-limiting example, system 100 can check in luggage for a flight with ABC Airlines. Personnel handling luggage check-in can scan the P-BTI on the global bag tag 230. This causes the indicator box 1101 to change color or display an icon indicating the status.

[0383] In one or more embodiments, the system can automatically update the status of field 1104 when baggage is checked in, for example, by electronically receiving communication with an IATA bag tag number plate. The system can also automatically update the status of field 1104 when baggage is checked in by printing an IATA bag tag for the flight.

[0384] When the status is updated in BTJR1154A, a message may be sent to the passenger. In one or more embodiments, the passenger may also be checked in by the system.

[0385] When baggage delivery and handling personnel process baggage and / or passengers for check-in with the airline, the P-BTI may be scanned on the global bag tag 230. This can cause the indicator box to change color or display an icon representing the status field 1104. Baggage and passengers can be verified, for example, up to 24 hours before the flight departure.

[0386] When baggage delivery and handling personnel deliver the baggage to the departure airport / airline for the flight, P-BTI can scan it on the global bag tag 230. This can cause the indicator box to change color or display an icon representing the status field 1106. BTJR1154A can receive updates regarding the flight. The indicator box in field 1108 can display a color or icon representing a change in the itinerary due to a flight arrival. Similarly, the indicator box in field 1106 can display a color or icon representing a change in the itinerary due to a flight departure or cancellation.

[0387] When baggage delivery and handling personnel retrieve the luggage from the airport / airline at the flight's destination, the P-BTI can be scanned on the global bag tag 230. This allows the indicator box to change color or display an icon representing the status in field 1110 to indicate that the luggage has been retrieved from that location. The status can also represent "in transit" to further transport, such as a hotel.

[0388] When baggage delivery and handling personnel deliver the luggage to the next vehicle, such as a hotel, the P-BTI can scan it on the global bag tag 230. This can cause the indicator box to change color or display an icon representing the status field 1112. The reservation status can also communicate any changes, including passengers and check-out times, in field 1114. In a non-limiting example, fields 1112 and 1114 may be used as a luggage inventory record for accommodation.

[0389] When baggage delivery and handling personnel pick up the luggage from the hotel, the P-BTI can be scanned on the global bag tag 230. This allows the indicator box to change color or display an icon representing the status in field 1116 to indicate that the luggage has been picked up for its location. The status can also represent "in transit" to further transport, such as to a hotel.

[0390] The operation of fields 1118 and 1120 will become clear from the following description in Figure 11B. In a non-limiting example, fields 1118 and 1120 may be used as a luggage inventory record for accommodation or VOT.

[0391] When baggage delivery and handling personnel retrieve luggage from the cruise ship, the P-BTI can be scanned on the global bag tag 230. This allows the indicator box to change color or display an icon representing the status in field 1122 to indicate that the luggage has been retrieved from that location. In this example, the passenger can return home via a return flight with a designated carrier.

[0392] In one or more embodiments, the system can automatically update the status of field 1124 when luggage is checked in, for example by receiving an IATA bag tag number plate. The system can also automatically update the status of field 1124 when luggage is checked in, for example by printing an IATA bag tag for a flight.

[0393] When the status is updated with BTJR1154A, a message may be sent to the passenger. In some cases, the passenger may also be checked in by the system. The message may include an IATA barcode with an IATA license plate indicating receipt that the baggage has been checked in on the airline's flight and / or an IATA license plate indicating receipt.

[0394] When baggage delivery and handling personnel process baggage and / or passengers for check-in with the airline, the P-BTI may be scanned on the global bag tag 230. This can cause the indicator box to change color or display an icon representing the status field 1124. Baggage and passengers can be verified up to 24 hours before the flight departure.

[0395] The operation of fields 1126 and 1128 is the same as that of fields 1106 and 1108 described above. Therefore, no further explanation is necessary.

[0396] When baggage delivery and handling personnel arrive at the baggage collection point from the airport, the P-BTI can be scanned on the global bag tag. This allows field 1130 to indicate the status of baggage collection from the airport for delivery to a designated address, such as a home address.

[0397] Additional fields may be provided for each location where the package is delivered or picked up. In this case, when the package is delivered to the home address or another designated address, the P-BTI can be scanned on the global bag tag. This allows another field, such as field 1164 (Figure 11B), to indicate the status of the package delivery to the home address.

[0398] Figure 11B shows a BTJR1154B created according to an embodiment for a registered passenger with luggage delivered for a cruise voyage. The registered passenger already has a P-BTI for use in any mode of travel. The description herein also applies to similar baggage handling fields 1118 and 1120 in bracket 1140 of Figure 11A.

[0399] In this case, BTJR1154B may include field 1156 for boarding the cruise from the port for LMN Cruise Line. Field 1156 may refer to cabin number "1234". While the description in Figure 11B illustrates a travel itinerary on a cruise ship, BTJR1154B may also be created, for example, when registered passengers' luggage is delivered to a resort, accommodation, or other vehicle.

[0400] The message communication unit 178 can identify when a cabin is ready for occupancy. System 100 may not have delivered luggage to the cabin, but it can still provide registered passengers with updated messages regarding the reservation status, including any delays in cabin availability.

[0401] BTJR1154B may include one or more baggage handling fields 1150, 1152, 1153, 1156, 1158, 1160, 1162, and 1164. Each field includes an indicator box 1151 on the first side of the field. Each indicator box may indicate the status of the baggage when the P-BTI on the global bag tag 230 is scanned. For example, when the P-BTI on the global bag tag is scanned for arrival or departure, the indicator box 1151 may display an icon or color representing the status. A first color or icon may indicate an expected baggage that has not been scanned for arrival or departure. A second color or icon may indicate an expected baggage that has been scanned for arrival or departure. Field 1152 displays the code “MNO”. This code is intended to represent a location code. However, an address may be used instead. Other code formats may be used and should not be limited to three characters.

[0402] Each baggage handling field may include various icons 1166 on a second side opposite to the first side of the field. The icons 1166 can distinguish different locations and modes of transport or vehicles to which the baggage should travel during that trip, depending on whether they are parallel to or independent of their owner.

[0403] In some cases, registered passengers request to pick up their luggage from a designated address, such as their home address, as shown in field 1150, but are not limited to this. When baggage delivery and handling personnel process the luggage and / or passenger, the P-BTI can be scanned on the global bag tag. This may cause indicator box 1151 to change color or display an icon indicating the status. When the luggage arrives at the cruise line location (i.e., dockside), the P-BTI may be scanned on the global bag tag. This may cause indicator box 1151 to change color or display an icon indicating the status.

[0404] When the luggage arrives at the dockside, the global bag tag 230 may be scanned by a scanner or other acquisition device to obtain the P-BTI (Figure 2B). The scanner may be at the dockside and may be configured to scan at least a barcode such as the P-BTI and communicate the P-BTI to system 100. The system can update BTJR1154B with confirmation of the presence of luggage of registered passengers who are ready to board the cruise listed in the currently listed PNR.

[0405] In the example, luggage can be delivered to the passenger cabin by delivery and handling personnel or other personnel, who scan the P-BTI and record its location in system 100 once the luggage is delivered to the passenger cabin, scanner, or acquisition device. This allows field 1156 to indicate the status of luggage delivery to the passenger cabin.

[0406] In the example, luggage is handled by delivery and handling personnel or other personnel, and can be retrieved from the passenger cabin. Once the luggage is retrieved from the cabin, a scanner or retrieval device scans the P-BTI and records its location in system 100. A message can be communicated to the registered passenger via a designated communication device at the location of the luggage. This allows field 1158 to indicate the status of luggage retrieval from the passenger cabin.

[0407] Security screening fields 1153 and 1160 will be described later. Security screening fields are applied, for example, to travel routes that can cross national borders. In other embodiments, screening by the TSA may be added. For example, in the scenario of Figure 11B, if the flight crosses a national border, security checks would be conducted, for example, by airport customs.

[0408] Any scanner or barcode acquisition device on the cruise ship or dockside may be configured to communicate with system 100 to record the location of luggage by acquiring P-BTI from global bag tags 230, for example by providing location data of the scanner or acquisition device.

[0409] Whenever the P-BTI is scanned by a scanning or acquisition device, additional baggage handling fields can be added to the BTJR1154B, and a communication is sent to the system 100 along with the P-BTI, and the location data of the baggage is communicated.

[0410] When a registered passenger disembarks from the cruise ship, a scanner or barcode acquisition device may obtain a P-BTI representation from the global bag tag 230 substrate for use by a computing device. The location data may also be transmitted to system 100 to update BTJR1154B to indicate that the luggage has left its location.

[0411] BTJR1154B may include security screening fields 1153 and 1160. In non-limiting examples, luggage and / or passengers may need to pass through customs, security screening locations in a second mode of transport, or other government security screening points. Security checks may take place at designated locations within the means of transport or in a vehicle, or at locations associated therewith. Customs may take place at designated locations, for example, at an airport.

[0412] Any scanner or barcode acquisition device located on a cruise ship or at a security screening point can be configured to record the location of luggage by acquiring a P-BTI representation from the global bag tag 230 substrate, for example, by communicating with system 100 and providing location data of the scanner or acquisition device. Furthermore, information related to passing or failing security screening can be transmitted to and recorded by system 100.

[0413] In some cases, registered passengers may request baggage retrieval from a designated address, such as the cruise ship's address, as shown in field 1162, but not limited to this. When baggage delivery and handling personnel arrive at the baggage retrieval location, the P-BTI may be scanned on the global bag tag. This allows field 1162 to indicate the status of baggage retrieval from the cruise ship. When the baggage is delivered to the home address or other designated address, the P-BTI may be scanned on the global bag tag. This allows field 1164 to indicate the status of baggage retrieval from the cruise ship. In non-limiting examples, fields 1162 and 1164 may be used as baggage inventory records for delivery to a designated address, such as a home address, company address, or other address.

[0414] Figure 11C shows a BTJR1154C created for the luggage of a registered passenger arriving at the dockside for a cruise voyage, according to an embodiment. In this example, the luggage arrives at the dockside with the passenger and includes a global bag tag 230. In other words, delivery and handling personnel did not deliver the luggage to the dockside. The BTJR1154C may include a field 1174 for boarding the cruise from the port. Field 1174 may refer to cabin number "1234". Although the description of Figure 11C illustrates travel on a cruise ship, the BTJR1154C may also be created, for example, when the luggage of a registered passenger arrives at a resort, accommodation, or other vehicle of transport.

[0415] BTJR1154C includes one or more baggage handling fields 1170, 1172, 1174, 1176, 1178, and 1180. Each field includes an indicator box 1171 on the first side of the field. Each indicator box may be configured to show the status of the baggage when the P-BTI on the global bag tag 230 is scanned. For example, when the P-BTI on the global bag tag is scanned for arrival or departure, the indicator box 1171 may display an icon or color representing the status. In one or more embodiments, field 1170 is created when the baggage arrives and the GMMT bag tag is scanned. This baggage may not have arrived when the passenger used a taxi, Uber, Lyft, or other ground transport without being checked into the system in advance. If the system 100 has received the sailing reservation in advance, BTJR1154C may be generated in advance. Alternatively, BTJR1154C may be generated on the fly when the passenger arrives at the vehicle or means of transport. Upon leaving security at Field 1178, GMMT bag tags can be scanned to record the departure of luggage from security and the cruise ship.

[0416] Each baggage handling field may include various icons 1182 on a second side opposite to the first side of the field. The icons 1182 can distinguish different locations and modes of transport or vehicles to which the baggage should travel during that trip, depending on whether they are parallel to or independent of their owner.

[0417] When the luggage arrives at the dockside, the global bag tag 230 may be scanned by a scanner or other acquisition device to obtain the P-BTI (Figure 2B). The scanner may be at the dockside and may be configured to scan at least a barcode such as the P-BTI and communicate the barcode (e.g., P-BTI) to system 100. The system can update BTJR1154C with confirmation of the presence of luggage of a registered passenger who is ready to board a cruise listed in the currently listed PNR.

[0418] When a registered passenger disembarks from the cruise ship, a scanner or barcode acquisition device may obtain a P-BTI representation from the global bag tag 230 substrate for use by a computing device. The location data may also be transmitted to system 100 to update the BTJR1154C to indicate that the luggage has left its location.

[0419] BTJR1154C may include security check fields 1172 and 1178. In non-limiting examples, luggage and / or passengers may need to pass through customs, a security screening location in a second mode of movement, or other government security screening points. Any scanner or barcode acquisition device at a cruise ship or security screening point may be configured to record the location of luggage by acquiring a P-BTI representation from the substrate of the global bag tag 230, for example, by communicating with system 100 to provide location data of the scanner or acquisition device. Furthermore, information related to passing or failing security screening may be transmitted to and recorded by system 100.

[0420] Considering the above, Global Bag Tag can be used to record the arrival and departure of luggage to any mode of transport during the end-to-end journey, without the luggage having to travel by plane.

[0421] Considering the above, Global Bag Tags can be used to record the arrival and departure of luggage to any mode of transport without the luggage having to travel by plane before arriving in that mode of transport.

[0422] In consideration of the foregoing, the system and method described herein links a Global Multi-Mode Travel (GMMT) bag tag number to at least one travel membership number of a registered passenger in order to access reservation information associated with at least one travel vehicle associated with at least one travel membership number of the registered passenger. This allows the system and method to collect reservation information for the current travel itinerary of at least one piece of luggage traveling independently or in parallel with the registered passenger in the registered passenger profile linked to the GMMT bag tag number. Based on the collected reservation information, the system and method can construct a Baggage Travel Route Record (BTJR) for the retrieval and delivery of at least one piece of luggage, the BTJR being linked to the GMMT bag tag number.

[0423] The system and method can link one or more pieces of luggage belonging to a registered passenger to the GMMT bag tag number and PNR number of the current travel itinerary.

[0424] The system and method may, for example, link one or more pieces of luggage belonging to an unregistered passenger in a group that shares a PNR number with a registered passenger. The travel booking data of the unregistered passenger may be linked by a GMMT bag tag, the group's PNR number, and, optionally, a non-discarded IATA bag tag placed on the luggage.

[0425] Figures 13A and 13B show flowcharts of Method 1300 for managing the retrieval of missing, lost, rerouted, delayed, or mishandled luggage according to an embodiment. As used herein, anomalous luggage may be missing, lost, rerouted, delayed, or mishandled. Luggage retrieval manager 180 (Figure 1B) may be configured to perform one or more of the following blocks of Method 1300 to electronically locate and / or retrieve anomalous luggage and to manage the rerouting of retrieved anomalous luggage. Luggage can be associated with a registered passenger or an unregistered passenger associated with a GTE-BSM link structure 950 by matching the passenger name in either the GTE-BSM field, the gte-BSM field, or the T-BSM field. In the case of anomalous luggage lost while traveling using another mobile vehicle, data in the VOT-BSM field is used.

[0426] Method 1300 may include, in block 1302, having the processor generate a master travel inventory. The master travel inventory 109 (Figure 1A) may include passengers traveling on that day. Passengers may include registered passengers. Once the travel inventory 109 is generated in block 1302, Method 1300 can proceed to blocks 1304 and 1310. In one or more embodiments, the luggage may not be traveling with the airline. As a result, Type B messages may not be received from the airline.

[0427] As time progresses and a GTE-BSM structure 950 can be formed with unregistered passengers, the master travel inventory may be updated. For example, if a passenger checks in for a flight or another VOT, the master inventory may be updated. In the case of an airline, the A-BSM can be collected first to determine the departure flight data.

[0428] When baggage is checked in, the A-BSM provides "normal" routing information for the planned route the baggage will take. The V / data field 804 includes the baggage source indicator "T" indicating transfer. The baggage source indicator is followed by the three-digit airport code "JFK". Field 806 in Figure 8 shows the departure flight number, airline code, and date "22MAY". The airline code "IST" represents Istanbul Airport. Field 808 is the arrival flight number, airline code, and date "12MAY". The airline code "SLC" represents Salt Lake City Airport.

[0429] In this example, the luggage is routed through the BHS at airports with codes "SLC", "IST", and "JFK". The transfer function is provided by the baggage source indicator in the .V field. This is an international flight, and the luggage may need to be inspected at security. This is still a normal process. Each BHS has a machine that indicates the location of the airport. The luggage may be placed in a container containing an RFID chip that can be scanned by the machine at the BHS at a specific airport. All BHS scanning activity may be tracked and stored in memory by the BHS's computer system or a computer system associated with the airline. For example, information related to luggage traveling with an airline may be stored in memory and accessible by a computer system associated with the airline, regardless of which BHS scanned the luggage.

[0430] Method 1300 may include receiving at least one Type B message by the processor of System 100 in block 1304. Type B messages may also be used in other methods described herein, such as the non-limiting methods shown in Figure 4B.

[0431] Method 1300 may include, in block 1306, having a processor in system 100 sort type B messages for reference indicators representing possible atypical routed luggage. The processor in system 100 (i.e., web server 112) searches or sorts references to possible atypical routed luggage in type B messages. Method 1300 may, for example, in block 1307A, sort reference indicators in the BNS for departure flights from master movement inventory 109. Reference indicators for possible atypical routed luggage may make luggage an anomalous item. Reference indicators may include airport codes. A normal route may identify a specific airport code in the BSM information. Receiving information with an airport code different from the normal route airport code may indicate a non-routed route.

[0432] For example, the processor of system 100 (i.e., the web server 112) can search for any unconfirmed baggage messages for a passenger in the master transfer inventory 109. To save processing time, the received or accessed BNS can focus on departure flight data for passengers associated with baggage handling services using GMMT bag tags. When an A-BSM is received, the IATA bag tag number is obtained to identify those B-type messages for searching or sorting.

[0433] In block 1307, further reference indicators to possible atypically routed luggage within a type B message may be found within the BPM. For example, the BPM may include a reference indicator for an unconfirmed bag. The BPM may include a reference indicator for unevenness in field B. The BPM may include reference indicators representing other atypical routing of luggage. The BPM includes various fields, such as field J, for communicating data about the scanner scanning the luggage, including its date, time, and location. The BPM data may be used to trace the route or to track the current location of an unusual piece of luggage. The BHS may include scanner data, scan date, and location data to find the route the luggage has taken after its route has branched from a typical or normal route to an atypical route. Atypical routes can be caused by many unpredictable factors, such as flight delays, equipment failures, bad weather, or damaged bag tags.

[0434] Another reference within a Type B message to possible atypically routed luggage may be a reference indicator for irregular behavior and / or involuntary route changes in the BTM, in block 1307C. This can be represented, for example, in a Type B message within the field ".E / IROP" from the BTM. A further reference within a Type B message to possible atypically routed luggage may be a reference to unaccompanied luggage indicated in the field ".E / UNAC". A further reference within a Type B message to possible atypically routed luggage may include a reference to a reference indicator for luggage route changes, indicated as ".E / RRTE". The reference indicator can represent information that can be considered for unusual luggage that is not following its usual route to its final destination. Delays in luggage arrival can have a significant impact on the travel and leisure experience of its owner, especially if the passenger is on a cruise or traveling long distances from the airport.

[0435] Another reference indicator within a Type B message, representing possible atypically routed packages, may include a reference for re-tagging packages indicated as "E / STCK" that may be found within the BSM.

[0436] As can be understood, there are many scenarios in which the combination of data within a Type B message can indicate an atypically routed piece of luggage that may be considered anomalous. For passengers on a cruise ship, delayed luggage can ruin their overall enjoyment. The method described herein is intended to identify a potential piece of luggage that may be atypically routed so that it can be identified early in the travel process. Based on the scan time, system 100 can determine that the luggage may be delayed.

[0437] Type B messages are associated with the airline's computing system, BHS63B (Figure 1B), or Type B messages may be received from other computer systems that receive and store them. Received Type B messages may include A-BSM messages associated with passengers in catalog 109. As described above, when a passenger begins their journey, their luggage may receive an IATA bag tag to be attached to the luggage, or it may already have an RFID bag tag. The A-BSM may provide departure flight information.

[0438] Method 1300 may include, in block 1308, having the system 100's processor compare travel information (passenger name, IATA bag tag number, and / or PNR number) from the master travel inventory 109 with the passenger name, IATA bag tag number, and / or PNR number in a Type B message. In one or more embodiments, block 1308 may be executed before block 1306.

[0439] Method 1300 may include determining, in block 1312 of Figure 13B, whether the processor of System 100 has detected a match related to a reference indicator for an unstructured routed baggage item for any passenger in the master travel inventory. If the determination in block 1312 is "no", the method may return to the beginning of block 1312. If the determination in block 1312 is "yes", method 1300 may include baggage item discovery / tracking by executing a baggage item discovery process in block 1314. The baggage finder 181 is described in more detail with reference to Figure 14.

[0440] You can return to block 1310 to determine if the package is missing or abnormal. If the determination in block 1310 is "no", the method can return to the beginning of block 1310. If the determination in block 1310 is "yes", the method can proceed to block 1314.

[0441] A BHS63B (Figure 1B) or other airport scanner or RFID reader interacting with the baggage may determine that the baggage was not loaded onto the airline. (Referenced herein is "Recommended Practice 1745 Baggage Information Messages" by IATA, in the Passenger Services Resolution Manual, June 2010, 30) th See "Edition". In one or more embodiments, the IATA bag tag or other bag tag mechanism may be damaged, unreadable, or malfunctioning, which may cause atypical routing. In other embodiments, the scanner may scan the location of the luggage in an unusual location because the luggage may have been loaded onto the wrong airline and arrived at the wrong airport.

[0442] In block 1314, if a reference indicator for unstructured routing of a package is detected, routing information from BHS and / or B-type messages before or after the occurrence of the reference indicator may be retrieved and analyzed by the system 100's processor for the purpose of locating and tracking the package.

[0443] Method 1300 may include, by the processor of system 100, determining in block 1316 an adjusted time of arrival at the intended final destination for tracked luggage on an unstructured route. The intended final destination may be for both the tracked luggage and the associated passenger, or for the tracked luggage only. Differences in the final destination may depend on the time it takes to find the luggage, the location of the luggage at the time it is found, and the distance required to bring the found luggage from the unstructured route to meet the passenger.

[0444] Method 1300 may include, in block 1318, having the processor of system 100 notify the passenger associated with the luggage of the current status of the luggage. Until the passenger receives the luggage, the passenger may be alerted of the current status of lost luggage, found luggage, and / or rerouted luggage, as well as any status changes.

[0445] Method 1300 may include, by the processor of System 100, determining the planned delivery location of the luggage upon arrival in Block 1320 from the current BTJR schedule. The processor of System 100 may be configured to consider the BTJR of the luggage on the current journey to determine the location to be picked up and delivered. Using data from BTJR, including past deliveries and / or pick-ups, the current location of the luggage, the current location of the passenger or accommodation to which the passenger will return at the end of the day, the found / tracked luggage can be rerouted, for example, to meet the passenger.

[0446] Method 1300 may include, in block 1322, having the processor of system 100 adjust the BTJR based on the time difference from the scheduled arrival time with the passenger according to the original schedule and / or any delays, the current time, the mode of transport for rerouting the found / tracked baggage, and the adjusted arrival time change resulting from the new arrival time to ensure the passenger and baggage meet on the passenger's route.

[0447] Method 1300 may include, in block 1324, having the processor of system 100 verify that the luggage matches when picked up for delivery. This may include scanning the IATA bag tag to match the IATA license plate with the IATA license plate number in profile 122. Alternatively, the global bag tag may be scanned to match the GMMT bag tag number with the GMMT bag tag number in profile 122. Furthermore, the image of the luggage may be compared with a stored image of the luggage in profile 122. Method 1300 may also include, in block 1326, notifying the passenger of the arrival and / or delivery of the luggage.

[0448] Figure 14 shows a flowchart of block 1304 method (hereinafter referred to as "method 1304") for finding abnormal baggage according to an embodiment. The baggage finder 181 may be configured to find abnormal baggage according to the steps in Figure 14. The blocks in Figure 14 are unique to an airline. However, some blocks may be used by other mobile carriers.

[0449] Method 1304 may include, in block 1402, having the processor of system 100 determine whether the tracking device 40 is available for the luggage. If the determination in block 1402 is "no", method 1304 may proceed to block 1412. If the determination in block 1402 is "yes", method 1304 may include, in block 1404, having the processor of system 100 retrieve location data 984 from the tracking device 40. The location data 984 is linked to the luggage via the IATA license plate and the GMMT bag tag number of the global bag tag affixed to the luggage.

[0450] Method 1304 may include determining in block 1406 whether the package has been found by the processor of system 100. If the determination in block 1406 is "no", method 1304 proceeds to block 1412. If the determination in block 1406 is "yes", method 1304 proceeds to block 1416, as will be described in more detail later.

[0451] Method 1304 may include, in block 1412, having the processor of system 100 retrieve B-type message data of the BHS for IATA bag tag numbers associated with matched baggage in a B-type message associated with an IATA baggage or GMMT bag tag number. In other words, system 100 may retrieve any B-type message or machine reading before or after a B-type message having a reference indicator representing an unstructured routed baggage to find where the baggage was last recorded or is currently recorded. Routing of baggage may result, for example, from damage to or loss of an IATA bag tag. The BHS may include a scanner for scanning the barcode of an IATA bag tag. The BHS may include an RFID reader for receiving an RFID signal representing an IATA bag tag.

[0452] BHS63B (Figure 1B) generates many Type B messages when a package is tracked and sent. Each Type B message may include tracking information for the package generated by BHS63B (Figure 1B), for example, before or after the creation of a Type B message with a detected reference indicator. The tracking information within a particular Type B message provides location information of places where the package has been scanned, both past and future. This information can be useful for tracing and tracking the route the package has traveled. This information can be useful for tracking the route the package has traveled to its current location, even if it is in an incorrect or rerouted location.

[0453] For training purposes, scanners, Type B messages, reference indicators, and / or BHS information can be used to find patterns for determining cause and effect.

[0454] Method 1304 may include, in block 1414, having the processor find a route to the anomalous baggage that will transport the baggage to its intended destination or meet with the passenger. The route may be a back-on-track route. When the route is found by the processor of system 100, the route may include a journey within the airline and along the BHS to the final destination. A back-on-track route may include other routes that retrieve the baggage from the airline and use a different mode of transport for the baggage.

[0455] Analysis to find a back-on-track route can be achieved by using an artificial intelligence (AI) algorithm that uses data from retrieved Type B messages before or after the occurrence of a reference indicator of atypical routing of the luggage detected by system 100. The data may include other information if the IATA bag tag is damaged or missing, as this may prevent the luggage from being sent to the correct airline. The point of the last scan or the point of the current scan can determine the proximity for retrieving the lost luggage. The luggage route data analyzer 182 can analyze data from the Type B message database 107, flight information, and / or location data from the tracking device 40 to develop a route to find the luggage or to find a back-on-track route that carries the anomalous luggage to its destination and meets the passenger's travel path.

[0456] Method 1340 may include, in block 1416, having the processor generate a claim for an anomalous piece of luggage. A claim may be generated when luggage is lost and its proximity is determined. In one or more embodiments, a baggage handler may search and locate anomalous luggage within the airport based on retrieved Type B message data.

[0457] Method 1304 may include, in block 1418, having the processor generate a delivery order for the claim. Once the actual location of the discovered package is found, system 100 can determine the delivery location of the package to be sent based on the current BTJR 154 (Figure 1B). The delivery order may include adjustments with the passenger depending on whether any of the passenger's travel segments have changed in the current travel itinerary.

[0458] Method 1304 may include, in block 1420, having the processor submit the claim to VOT.

[0459] Method 1304 may include, in block 1422, having the processor notify the passenger of the submission of the bill. System 100 may communicate confirmation of receipt of the bill submission using the passenger's email address, the phone number of their mobile communication device, or other communication medium. System 100 may also send a warning or communication to the passenger regarding the submission of the bill to VOT.

[0460] Figure 15 shows a diagram of the abnormal baggage detection model. Model 1500 can receive data-related B-type messages. As a non-restrictive reference, Model 1500 can receive reference indicators associated with one or more BSMs on line 1504, BPMs on line 1506, BTMs on line 1508, or BNSs on line 1510. Although there is a single line, it should be understood that various information for each message, including date, field, airport data, flight information, etc., may need to be entered. The original A-BSM can be used to predict the expected route of baggage within normal limits. Reference indicators from BPM data, BTM data, or BNS data can be used to predict unstructured routes.

[0461] Model 1500 can receive location data on line 1512 if the package has a tracking device 40. In the embodiment, when a reference indicator for an unstructured route is detected using the location data, reliance on tracking type B message data may be weighted less than reliance on location data from the tracking device.

[0462] Model 1500 can receive Type B message training data on line 1520, indicating both normal and atypical reference indicators. Model 1500 can receive BHS training data on line 1522, which relates to scanners and other devices associated with airport BHS. Model 1500 can receive current flight delays or flight changes on line 1524 from airlines or airports. Model 1500 can receive variable thresholds on line 1526. Depending on the next travel segment of the journey, the threshold for the deviation between the current route and the normal route may vary depending on the type and location of the next travel segment. For example, boarding a cruise ship can be very costly due to the need to deliver delayed or lost baggage after passengers have set sail.

[0463] Model 1500 can, for example, receive passenger names (PNs) on line 1530. In one or more embodiments, Model 1500 may receive PNR numbers or IATA license plate numbers on line 1530. Model 1500 can receive flight data on line 1532 to derive a normal route using the origin BSM. Model 1500 can use various machine learning or artificial intelligence algorithms to 1) predict the normal route of luggage and / or 2) predict an unconventional route of luggage to find unusual luggage. In one or more embodiments, the unconventional route may need to deviate from the normal route by a predetermined amount of time and / or distance.

[0464] Model 1500 can output information representing unusual baggage on line 1540. The output information may include flight data, IATA license plate number, passenger name, and / or PNR number. The output information may include location information for the atypical route and the time difference between the expected normal route and the current atypical route. Distance thresholds can be expressed in miles, airport codes, or city codes. Time thresholds can be expressed in days, hours, minutes, and seconds.

[0465] The machine learning (ML) or artificial intelligence (AI) algorithm 1502 may include neural networks, Bayesian networks, tree-based models, supervised learning algorithms, and reinforcement learning algorithms. In one or more embodiments, the ML / AI algorithm may use a classification model based on a reference indicator.

[0466] As used herein, the terms “model” and / or “machine learning model” have their usual technical meanings, broadly referring to various types of machine learning models, as understood by those skilled in the art. Each type of machine learning model is suited to different types of tasks and has relative advantages and disadvantages. Representative machine learning models may include, for example, (1) supervised learning, (2) unsupervised learning, (3) semi-supervised learning, (4) reinforcement learning, and (5) deep learning. Each of these models, along with its various subtypes and more detailed implementations, is described below in detail. In the embodiments disclosed herein, various types of models described below can be combined and modified to suit a particular task at hand.

[0467] Machine learning algorithms Supervised Learning: Supervised learning machine learning algorithms are trained using labeled data, i.e., input data tagged with the correct output. The model learns to predict the output from the input data. There are several different subtypes of supervised learning models, such as (1) linear regression, (2) logistic regression, (3) decision trees, (4) random forests, (5) support vector machines, and (6) neural networks.

[0468] Linear Regression: Linear regression machine learning algorithms can be useful for predicting continuous outcome variables based on one or more predictor variables. These types of algorithms model the relationship between dependent and independent variables by fitting a linear equation to observed data.

[0469] Logistic regression: The logistic regression machine learning algorithm can be useful for predicting the probability that a given instance belongs to a particular class.

[0470] Decision Trees: Decision tree models can use a tree-like graph of decisions to make predictions. In various embodiments of implementing decision tree models, such algorithms can be useful for both regression and classification tasks.

[0471] Random Forest: The Random Forest machine learning algorithm can include an ensemble of decision trees, which are typically used to improve prediction accuracy and control overfitting.

[0472] Support Vector Machines (SVMs): Support vector machine learning algorithms can be particularly well-suited to determining and / or solving a variety of problems surrounding the classification of issues and objects. These types of algorithms are effective in high-dimensional spaces and work by finding a hyperplane that optimally separates classes in the feature space.

[0473] Neural Networks: This type of machine learning algorithm is often used as a catch-all term referring to various types of algorithms. The term "neural network" is inspired by the structure of the human brain, and these models are particularly effective for complex problems such as image and speech recognition. They can model nonlinear relationships and learn complex patterns in data. Examples include image analysis training and decision making.

[0474] Unsupervised Learning: These algorithms are used when the training data is unlabeled. The system attempts to learn patterns and structures from the data. Examples of unsupervised learning algorithms are described below.

[0475] Clustering algorithms (e.g., K-means, hierarchical clustering): These are used to group data points into clusters such that data points within the same cluster are more similar to each other than data points in other clusters.

[0476] Principal Component Analysis (PCA): A technique used to highlight variability within a dataset and extract strong patterns. It is often used to make data easier to explore and visualize.

[0477] Autoencoder: A type of neural network typically used to learn an efficient representation of data, usually with the aim of reducing dimensionality.

[0478] Additional machine learning algorithms will be discussed later.

[0479] Semi-supervised learning: These algorithms fall between supervised and unsupervised learning because they use both labeled and unlabeled data for training.

[0480] Reinforcement Learning: This type of machine learning uses a reward and penalty system to enable computers to solve problems on their own. It is used in a variety of applications, such as training models to play video games or robotic hands to grasp objects.

[0481] Deep learning: A subset of machine learning that uses neural networks, especially those with many layers (deep networks). It is particularly powerful for processing unstructured data such as images and text. Examples of deep learning models are described below.

[0482] Convolutional neural networks (CNNs) are primarily used for image recognition and processing, and can capture spatial and temporal dependencies within an image by applying relevant filters.

[0483] Recurrent neural networks (RNNs): Due to their ability to use their internal memory to store information about previous inputs, they are well-suited for processing time-series or sequential data such as natural language.

[0484] Each of these models and algorithms has its own strengths and weaknesses, making them suitable for various types of data and problems. The choice of algorithm often depends on the size, quality, and nature of the data, the task being performed, and the available computing resources.

[0485] Figure 16A shows a block diagram of a tracking device 1640 (i.e., tracking device 40 or 40') according to an embodiment. The tracking device 1640 may include a subscriber identification module (SIM) card 1641, a GPS-GSM tracking component 1642, and an antenna ANT. The GPS-GSM tracking component 1642 may be configured to perform cell tower positioning via the GSM / cellular positioning protocol 1656, Wi-Fi positioning via the Wi-Fi positioning protocol 1652, GNSS positioning via the GNSS positioning protocol 1658, and Bluetooth positioning via the Bluetooth positioning protocol 1654. In one or more embodiments, the subscriber identification information of the SIM card 1641 may be associated with a baggage handling service, a baggage tracking service, an airline, or a mobile vehicle. In one or more embodiments, the subscriber identification information of the SIM card 1641 may be associated with a passenger. The GPS-GSM tracking component 1642 may include at least one processor. The tracking device 1640 may include at least one processor 1644.

[0486] The tracking device 1640 can route within a building along above-ground and / or underground routes, which may create GNSS-denied environments. Therefore, the tracking device 1640 can provide location information in GNSS-denied environments. However, for use outside of airport infrastructure, the tracking device 1640 can have GNSS access. Therefore, the tracking device 1640 can provide location information derived from GNSS data.

[0487] While GSM or cellular networks are readily available, these networks do not have 100% global coverage. For example, cellular communication may be blocked in underground buildings. Depending on the building's construction or nearby buildings, communication within a building may be blocked or intermittent. As a result, since luggage travels both inside and outside buildings, tracking devices may need to be able to acquire location information using various methodologies and adapt to their surrounding and contextual communication parameters.

[0488] In one or more embodiments, the tracking device 1640 can use available RF access points, which may include Bluetooth access points and / or Wi-Fi access points, as described later.

[0489] In the example, the tracking device 1640 may include an RFID unit 1643 configured to communicate using RFID frequencies. In a non-limiting example, the tracking device 1640 having the RFID unit 1643 may be configured to communicate with an RFID receiver in a baggage handling system. Some baggage handling systems have an RFID receiver that reads or receives RFID signals from IATA-compliant RFID bag tags.

[0490] In one or more embodiments, the tracking device 1640 can function as an RFID bag tag that is IATA compliant while within the airport infrastructure but also provides tracking capabilities outside the airport infrastructure.

[0491] The tracking device 1640 may include at least one digital certificate 1646. In embodiments, the digital certificate 1646 may be an organization-level digital certificate, which enables the encryption and decryption of organization-level information. In a non-limiting example, the organization-level digital certificate may be for interacting with an airline kiosk 1710 (Figure 17A) and / or a BHS device 1760 (Figure 17B). The tracking device 1640 may include a digital certificate 1646 to enable a passenger's mobile device to pair with the tracking device 1640. The tracking device 1640 may include a digital certificate 1646 for communicating with various communication platforms.

[0492] The tracking device 1640 may include a display 1648 having a display screen, a power supply, and a memory 1650. The memory 1650 may store BSM information 1660. The BSM information 1660 may include at least one of the following: GMMT bag tag number 1662, PNR number 1664, or IATA license plate number (IATA LPN) 1666. The BSM information 1660 may be extracted from GTE-BSM, origin A-BSM, or destination BSM, depending on when the tracking device was assigned to the luggage. In one or more embodiments, the memory 1650 may be loaded with itinerary information 1674. For example, the itinerary information 1674 may include a PNR number, a booking number, or other confirmation number for the vehicle being transported.

[0493] In one or more embodiments, the power source may be a battery having one or more battery-saving modes. A first battery-saving mode may be based on the detected altitude of the tracking device. A second battery-saving mode may be based on the detected speed of the tracking device. For example, when the tracking device is on board during flight, the tracking device may be turned off or put into sleep mode. A third battery-saving mode may be based on the selected communication mode of the tracking device. For example, the Bluetooth communication protocol may use less power than other communication protocols. As a result, the tracking device may select a communication protocol to conserve battery power.

[0494] In one or more embodiments, the display 1648 may be configured to display stored information. In a non-limiting example, the display 1648 may display the IATA license plate number and the corresponding IATA license plate. The display 1648 may be compatible with an RFID bag tag.

[0495] In one or more embodiments, the BSM information 1660 may include information printed on the IATA-compliant bag tag, such as arrival flight information, departure flight information, PNR number, and passenger name, as described in relation to Figure 8.

[0496] In one or more embodiments, the surface of the tracking device 1640 may include the GMMT bag tag number 1662. In one or more embodiments, the display may show the GMMT bag tag number 1662.

[0497] In this example, memory 1650 can store a primary ID (PID) 1668 created by the baggage handling system via the BHS device 1760 (Figure 17B). The primary ID may be, for example, a pseudo-ID sent from the baggage handling system to the security screening machine 1762 (Figure 17B). In this example, the primary ID 1668 may be a TSA compliance number that needs to be sent by the baggage handling system to the security screening machine 1762 to identify the baggage.

[0498] In the example, memory 1650 may store passenger personally identifiable information (PII) 1670. PII 1670 may include the passenger's date of birth associated with the passenger. In the example, PII 1670 may include a driver's license, social security number, passport identifier, or government-issued identification number. In one or more embodiments, the primary ID and / or passenger personally identifiable information may be retrieved from a tracking device for use when retrieving security screening images stored in a cloud storage system, and as a result, the security screening images may be retrieved and re-analyzed by a security screening station.

[0499] Access to memory 1650 may be controlled by different authentication procedures. For example, pairing with a kiosk may differ from pairing with the mobile device of the luggage owner (i.e., the passenger).

[0500] In the example, the tracking device 1640 can operate in RFID mode, where the display 1648 can display the IATA license plate and other IATA compliance information for the IATA RFID bag tag.

[0501] In this example, memory 1650 can store various applications 1672 for performing different operating modes, as illustrated in Figures 16B, 16C, 16D, and 16E. Applications 1672 may include software, hardware, firmware, or a combination thereof. Applications 1672 may include programming modules configured to be executed by the processor to perform the functions and operations described later.

[0502] A tracking device can communicate with one or more service devices and be configured to cause different types of service devices to perform functions, as will become apparent from the following description.

[0503] Figure 16B shows a block diagram of a contactless bag tag printing manager 1680B according to an embodiment. Figure 17A shows a block diagram of a contactless baggage bag tag printing process 1700A using a tracking device according to an embodiment. Currently, a checked-in passenger can walk to kiosk 1710 to print their IATA bag tag. In one example, the passenger can enter a PNR number or itinerary confirmation number using a key 1716 which may be displayed on screen 1712. Alternatively, the passenger may have already checked in themselves using the airline application and be asked to digitally check in their luggage. In this case, the passenger receives a ticket in the form of a code such as a QR code. At kiosk 1710, the passenger places their handheld device 1701 under scanner 1714. However, it may be difficult to get the scanner to capture the QR code or other code to be scanned. Generally, the passenger's hands are filled with personal belongings, including a wallet, jacket, coat, or carry-on luggage.

[0504] The contactless bag tag printing manager 1680B may include a tracker printer pairing unit 1682B and an authentication unit 1684B. The contactless bag tag printing manager 1680B may include a print code sequence communication unit 1686B. The print code sequence may be, for example, a PNR number or another code sequence sent from the tracking device's memory to the kiosk 1710 (Figure 17A) to print an IATA bag tag for a passenger to the printer. The contactless bag tag printing manager 1680B may include a PNR number or another code sequence required by the airline. In this example, the PNR number or other code sequence for printing may be a travel application number. In one or more embodiments, the kiosk may print tickets or other tags for other travel vehicles.

[0505] The pairing unit 1682B may use Bluetooth pairing, for example, to pair with the Bluetooth activation unit 1720. The Bluetooth activation unit 1720 may be configured to pair with the tracking device having the strongest signal strength. For example, the package 1750 may be placed directly in front of the kiosk 1710. For security purposes, the authentication unit 1684B may require a specific digital certificate to enable Bluetooth pairing with the kiosk 1710 and the tracking device 1640.

[0506] The kiosk 1710 includes a processor 1705 and a printer 1718. In this case, the PNR number or another code sequence may be a mobile request number used to control the functions of the kiosk 1710. The processor 1705 can receive the mobile request number to authorize the printing of IATA bag tags.

[0507] In one or more embodiments, the kiosk 1710 may be located at an airport or remote location where luggage is processed for attaching IATA bag tags.

[0508] In one or more embodiments, the tracking device 1640 may include a button or mechanism for initiating the transmission of a code to a kiosk or other printing device for printing an IATA bag tag.

[0509] In one or more embodiments, the tracking device 1640 is independent of the passenger P's mobile communication device, but may be configured to receive information from or control signals from the passenger's mobile communication device 1701 via a graphical user interface.

[0510] In one or more embodiments, the tracking device 1640 can receive information from a mobile communication device and program BSM information or a mobile application number into its memory.

[0511] Figure 16C shows a block diagram of the security screening manager 1680C according to an embodiment. The security screening manager 1680C will be described in conjunction with Figure 17B. Figure 17B shows a diagram of the pseudo-ID (i.e., primary ID) recording process 1700B using the tracking device 1640 according to an embodiment. In this example, memory 1650 can store pseudo-IDs (i.e., PID 1668) created by the baggage handling system via the BHS device 1760 (Figure 17B) and presented to the security screening machine 1762 (Figure 17B). The security screening manager 1680C may include a pairing unit 1682C and an authentication unit 1684C for the tracker BHS device. The pairing unit 1682C may use, for example, Bluetooth pairing. The authentication unit 1684C may require a specific item digital certificate to enable Bluetooth pairing between the BHS device 1760 (Figure 17B) and the tracking device on the package 1750 for security purposes. The BHS device and the tracking device can be paired when the tracking device / package is in proximity to the BHS device 1760 entering the security screening machine 1762. The BHS device may be programmed to communicate a primary ID, pseudo-ID, or other TSA compliance number to the tracking device in order to identify the package entering the security screening machine.

[0512] In this example, the IATA LPN communication unit 1686C can communicate the IATA LPN to the BHS device 1760 (Figure 17B) before receiving the primary ID, pseudo ID, or other TSA compliance number. In this case, the IATA LPN may function as a travel application number. The primary ID, pseudo ID, or other TSA compliance number may be received by the PID receiver 1688C. The received PID is then stored in the tracking device's memory.

[0513] Figure 16D shows a block diagram of a mobile-tracker pairing manager 1680D according to an embodiment. The mobile-tracker pairing manager 1680D may include a tracker-to-mobile pairing unit 1682D and an authentication unit 1684D. The mobile-tracker pairing manager 1680D may include a print code sequence receiver 1688D and a personally identifiable information receiver 1690D. In one or more embodiments, a passenger can communicate a print code sequence to the tracking device via data input using the tracking device's display or via wireless communication. In one or more embodiments, a passenger can communicate personally identifiable information via data input using the tracking device's display or via wireless communication to the tracking device. Personally identifiable information can be stored using an authentication protocol to authenticate the identity of the user or passenger.

[0514] The mobile-tracker pairing manager 1680D may include a mobile information communication unit 1686D configured to communicate any BSM or itinerary information stored in memory. The information may be transmitted to a display or by wireless communication.

[0515] Figure 16E shows a block diagram of an unstructured reference indicator detection manager 1680E according to an embodiment. The unstructured reference indicator detection manager 1680E may include a pairing unit 1682E and an authentication unit 1684E for the tracker and a second device. The second device may include a device in a baggage handling system.

[0516] The non-standard reference indicator detection manager 1680E may include a reference indicator receiver 1688E and a non-standard reference indicator detection unit 1690E. The reference indicator may include an airport code. The original BSM information may include a reference indicator for the normal route for the flight. It is possible to detect the reception of a reference indicator from within the airport that represents a non-standard indicator as described herein.

[0517] The unstructured reference indicator detection manager 1680E may include a notification communication unit 1692E configured to communicate notifications of unstructured routes in response to the detection of one or more unstructured reference indicators.

[0518] Figure 17C shows a diagram of process 1700C for communicating location information from a Global Navigation Satellite System (GNSS) platform according to an embodiment. Satellite 1765C shows a GNSS communicating with a tracking device 1640 attached to a package 1750. The tracking device 1640 can communicate location information with a cell tower 1767C. The cell tower can communicate location information via network 1775 to a computing device 1763C configured to track the package via the tracking device 1640. Network 1775 may be the Internet or a public utility network.

[0519] Figure 17D shows a diagram of process 1700D of a tracking device 1640 for communicating location information with at least one radio frequency (RF) access point, according to an embodiment. In the figure, the RF access points are shown as 1777A, 1777B, 1777C, and 1777D. The tracking device 1640 is closest to RF access point 1777B, pairs with location information via network 1775, and can transmit the location information to computing device 1763C (Figure 17C). In one or more embodiments, the tracking device can select RF access point 1777B based on signal strength.

[0520] Figure 18 shows a block diagram of a tracking system 1800 according to an embodiment. The tracking system 1800 may include a plurality of tracking devices 1640 that communicate with a tracking station 1810 (i.e., a computing device) via a network 1830. The network 1830 may be the Internet or another public utility communication network.

[0521] The tracking station 1810 may include a display 1815 that shows the location of the tracking device indicated by the locator 1820. The tracking station 1810 may also display a comment window 1825 associated with the locator 1820. The comment window 1825 may include notifications of unstructured routes due to the detection of unstructured reference indicators. The comment window 1825 may include address or location information. The location information may include detailed information such as building level, floor, room number, and building number. The location information may include information related to nearby or surrounding Internet of Things (IoT) devices, mobile communication devices, or other RF access points.

[0522] Figure 12 is a block diagram showing an electronic device in a network environment according to one or more embodiments. As used herein, the electronic device 1201 may include, for example, a tracking device 40, a computing device 50, a web server 112, components of reservation systems 60, 62, 64, 66, 68, and 70, components of TMS 74, an acquisition device 195, a processor 610, at least one second processor 626, a computer system 628, and a computing device 648.

[0523] The systems described herein may be implemented via one or more electronic devices operating in a network environment. For example, an electronic device 1201 (e.g., computing device 50) in the network environment 1200 may communicate with an electronic device 1202 via a first network 1298 (e.g., a short-range wireless communication network), or with at least one of an electronic device 1204 or a server 1208 via a second network 1299 (e.g., a long-range wireless communication network). According to one embodiment, an electronic device 1201 can communicate with an electronic device 1204 via a server 1208. According to the embodiment, the electronic device 1201 may include a processor 1220, memory 1230, input module 1250, audio output module 1255, display module 1260, audio module 1270, sensor module 1276, interface 1277, connection terminal 1278, tactile module 1279, camera module 1280, power management module 1288, battery 1289, communication module 1290, subscriber identification module (SIM) 1296, or antenna module 1297. In certain embodiments, at least one of the components (e.g., connection terminal 1278) may be omitted from the electronic device 1201, or one or more other components may be added to the electronic device 1201. In certain embodiments, some of the components (e.g., sensor module 1276, camera module 1280, or antenna module 1297) may be implemented as a single component (e.g., display module 1260). The processor 1220 can, for example, execute software (e.g., program 1240) to control at least one other component (e.g., hardware or software component) of the electronic device 1201 coupled to the processor 1220, and can perform various data processing or calculations.According to the embodiment, as part of data processing or calculation, the processor 1220 may store commands or data received from another component (e.g., a sensor module 1276 or a communication module 1290) in a volatile memory 1232, process the commands or data stored in the volatile memory 1232, and store the resulting data in a non-volatile memory 1234. According to the embodiment, the processor 1220 may include a main processor 1221 (e.g., a central processing unit (CPU) or an application processor (AP)), or an auxiliary processor 1223 (e.g., a graphics processing unit (GPU), a neural processing unit (NPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that can operate independently of or together with the main processor 1221. For example, if the electronic device 1201 includes a main processor 1221 and an auxiliary processor 1223, the auxiliary processor 1223 may be adapted to consume less power than the main processor 1221 or to be unique to a specified function. The auxiliary processor 1223 may be implemented separately from the main processor 1221, or as part of the main processor.

[0524] The auxiliary processor 1223 can control at least some functions or states related to at least one component of the electronic device 1201 (e.g., display module 1260, sensor module 1276, or communication module 1290) on behalf of the main processor 1221 when the main processor 1221 is inactive (e.g., sleep), or together with the main processor 1221 when the main processor 1221 is active (e.g., running an application). According to the embodiment, the auxiliary processor 1223 (e.g., image signal processor or communication processor) may be implemented as part of another component functionally related to the auxiliary processor 1223 (e.g., camera module 1280 or communication module 1290). According to the embodiment, the auxiliary processor 1223 (e.g., neural processing unit) may include a hardware structure designated for processing artificial intelligence models. The artificial intelligence model may be generated by machine learning. Such learning may be performed, for example, by the electronic device 1201 on which the artificial intelligence is run, or via a separate server (e.g., server 1208). The learning algorithm may include, but is not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning. The artificial intelligence model may include multiple artificial neural network layers. The artificial neural network may be, but is not limited to, a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), a deep Q network, or two or more combinations thereof. The artificial intelligence model may additionally or alternatively include software structures other than hardware structures.

[0525] Memory 1230 can store various data used by at least one component of the electronic device 1201 (e.g., processor 1220 or sensor module 1276). This data may include, for example, input or output data for software (e.g., program 1240) and related instructions. Memory 1230 may include volatile memory 1232 or non-volatile memory 1234.

[0526] The program 1240 may be stored as software in memory 1230 and may include, for example, an operating system (OS) 1242, middleware 1244, or an application 1246.

[0527] The input module 1250 can receive commands or data used by another component of the electronic device 1201 (e.g., the processor 1220) from outside the electronic device 1201 (e.g., the user). The input module 1250 may include, for example, a microphone, a mouse, a keyboard, keys (e.g., buttons), or a digital pen (e.g., a stylus pen).

[0528] The audio output module 1255 may output audio signals to the outside of the electronic device 1201. The audio output module 1255 may include, for example, a speaker or a receiver. The speaker may be used for general purposes such as multimedia playback or playback of recordings. The receiver may be used to receive incoming calls. According to the embodiment, the receiver may be implemented separately from the speaker or as part of the speaker.

[0529] The display module 1260 can visually provide information to an external party (e.g., a user) outside of the electronic device 1201. The display module 1260 may include, for example, a display, a hologram device, or a projector, and a control circuit for controlling the corresponding display, hologram device, or projector. According to the embodiment, the display module 1260 may include a touch sensor adapted to detect touches, or a pressure sensor adapted to measure the intensity of force generated by a touch.

[0530] The audio module 1270 can convert sound into electrical signals and vice versa. According to one embodiment, the audio module 1270 can acquire sound via the input module 1250, or output sound directly (e.g., wired) or wirelessly coupled with the electronic device 1201 via headphones of the audio output module 1255 or an external electronic device (e.g., electronic device 1202).

[0531] The sensor module 1276 can detect the operating state of the electronic device 1201 (e.g., power or temperature) or the external environmental state of the electronic device 1201 (e.g., user status), and then generate an electrical signal or data value corresponding to the detected state. According to the embodiment, the sensor module 1276 may include, for example, a gesture sensor, a gyroscope sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biosensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

[0532] Interface 1277 may support one or more designated protocols to be used for the electronic device 1201 to be coupled directly (e.g., wired) or wirelessly to an external electronic device (e.g., electronic device 1202). According to embodiments, interface 1277 may include, for example, a High Resolution Multimedia Interface (HDMI®), a Universal Serial Bus (USB) interface, a Secure Digital (SD) card interface, or an audio interface.

[0533] The connection terminal 1278 may include a connector that allows the electronic device 1201 to be physically connected to an external electronic device (e.g., electronic device 1202). According to the embodiment, the connection terminal 1278 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0534] The tactile module 1279 can convert electrical signals into mechanical stimuli (e.g., vibration or movement) or electrical stimuli that can be perceived by the user through the user's sense of touch or kinesthetics. According to the embodiment, the tactile module 1279 may include, for example, a motor, a piezoelectric element, or an electrical stimulator.

[0535] The camera module 1280 can capture still images or videos. According to the embodiment, the camera module 1280 may include one or more lenses, image sensors, image signal processors, or flashes.

[0536] The power management module 1288 can manage the power supplied to the electronic device 1201. According to one embodiment, the power management module 1288 may be implemented, for example, as at least part of a power management integrated circuit (PMIC).

[0537] The battery 1289 may supply power to at least one component of the electronic device 1201. According to the embodiment, the battery 1289 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0538] The communication module 1290 may support the establishment of a direct (e.g., wired) or wireless communication channel between the electronic device 1201 and an external electronic device (e.g., electronic device 1202, electronic device 1204, or server 1208), and the execution of communication over the established communication channel. The communication module 1290 may include one or more communication processors that can operate independently of the processor 1220 (e.g., an application processor (AP)) and support direct (e.g., wired) or wireless communication. According to embodiments, the communication module 1290 may include a wireless communication module 1292 (e.g., a cellular communication module, a near-field communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 1294 (e.g., a local area network (LAN) communication module or a power line communication (PLC) module). Corresponding communication modules among these communication modules may communicate with external electronic devices via a first network 1298 (e.g., a short-range communication network such as Bluetooth®, Wireless Fidelity (Wi-Fi) Direct, or Infrared Data Association (IrDA)) or a second network 1299 (e.g., a long-range communication network such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or wide area network (WAN))). These various communication modules may be implemented as a single component (e.g., a single chip) or as multiple components separated from each other (e.g., a multi-chip). The wireless communication module 1292 may use subscriber information (e.g., International Mobile Subscriber Identification Information (IMSI)) stored in the subscriber identification module 1296 to identify and authenticate electronic devices 1201 within the communication network, such as the first network 1298 or the second network 1299.

[0539] The wireless communication module 1292 can support 5G networks following 4G networks, and next-generation communication technologies, such as new radio (NR) access technology. NR access technology can support extended mobile broadband (eMBB), massive machine-type communication (mMTC), or ultra-reliable low-latency communication (URLLC). The wireless communication module 1292 can support high frequency bands (e.g., mmWave band) to achieve high data transmission speeds. The wireless communication module 1292 can support various techniques to ensure performance in high frequency bands, such as beamforming, massive multiple-input multiple-output (massive MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, or large antennas. The wireless communication module 1292 can support various requirements specified by electronic device 1201, external electronic devices (e.g., electronic device 1204), or network systems (e.g., second network 1299). According to the embodiment, the wireless communication module 1292 can support a peak data rate (e.g., 20 Gbps or more) for implementing eMBB, loss coverage (e.g., 164 dB or less) for implementing mMTC, or U-plane latency (e.g., 0.5 ms or less for each of the downlink (DL) and uplink (UL), or a round trip of 1 ms or less) for implementing URLLC.

[0540] The antenna module 1297 can transmit or receive signals or power to or from outside the electronic device 1201 (e.g., an external electronic device). According to the embodiment, the antenna module 1297 may include an antenna that includes a radiating element composed of a conductive material or conductive pattern formed in or on a substrate (e.g., a printed circuit board (PCB)). According to the embodiment, the antenna module 1297 may include a plurality of antennas (e.g., an array antenna). In such a case, for example, the communication module 1290 (e.g., a wireless communication module 1292) may select at least one antenna from the plurality of antennas that is suitable for a communication scheme used in a communication network such as a first network 1298 or a second network 1299. The signal or power may then be transmitted or received between the communication module 1290 and the external electronic device via the selected at least one antenna. According to the embodiment, other components other than radiating elements (e.g., a radio frequency integrated circuit (RFIC)) may be additionally formed as part of the antenna module 1297.

[0541] According to one or more embodiments, the antenna module 1297 may form an mmWave antenna module. According to the embodiment, the mmWave antenna module may include a printed circuit board, an RFIC disposed on or adjacent to a first surface (e.g., bottom surface) of the printed circuit board and capable of supporting a specified high-frequency band (e.g., mmWave band), and a plurality of antennas (e.g., array antennas) disposed on or adjacent to a second surface (e.g., top or side surface) of the printed circuit board and capable of transmitting or receiving signals in the specified high-frequency band.

[0542] At least some of the above components may be connected to one another and communicate signals (e.g., commands or data) using a peripheral device communication method (e.g., bus, general-purpose input / output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)).

[0543] According to the embodiment, commands or data may be transmitted to or received between the electronic device 1201 and the external electronic device 1204 via a server 1208 connected to a second network 1299. Each of the electronic devices 1202 or 1204 may be of the same type as electronic device 1201 or of a different type. According to the embodiment, all or part of the operations performed by electronic device 1201 may be performed by one or more of the external electronic devices 1202, 1204, or 1208. For example, if electronic device 1201 is to perform a function or service automatically or in response to a request from a user or another device, electronic device 1201 may request one or more external electronic devices to perform at least part of the function or service instead of performing it, or in addition to performing it. One or more external electronic devices receiving the request may perform at least part of the requested function or service, or additional functions or additional services related to the request, and transfer the results of the execution to electronic device 1201. The electronic device 1201 can provide results as at least part of a response to a request, with or without further processing of the results. For this purpose, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology can be used. The electronic device 1201 can provide ultra-low latency services using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device 1204 may include an Internet of Things (IoT) device. The server 1208 may be an intelligent server using machine learning and / or neural networks. According to the embodiment, the external electronic device 1204 or the server 1208 may be included in the second network 1299. The electronic device 1201 can be applied to intelligent services based on 5G communication technology or IoT-related technologies (e.g., smart homes, smart cities, smart cars, or healthcare).In the embodiment, the electronic devices 1202 and / or 1204 may be printing devices. The printing devices may be engraving devices, etching devices, computer-aided design (CAD) manufacturing devices, 3D printing devices, laser printing devices, or other printing devices.

[0544] An electronic device according to one or more embodiments may be one of various types of electronic devices. An electronic device may include, for example, a mobile communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a printer, a camera, a wearable device, or a home appliance. According to embodiments of this disclosure, an electronic device is not limited to those described above.

[0545] The embodiments described herein are explained with reference to the attached drawings, which use similar reference numerals throughout and indicate similar or equivalent elements. The drawings are not drawn to scale and are provided solely to illustrate the embodiments disclosed herein. Some of the disclosed embodiments are described herein by reference to non-limiting illustrative uses. It should be understood that a number of specific details, relationships, and methods are described in order to give a full understanding of the embodiments disclosed herein. However, those skilled in the art will readily recognize that the disclosed embodiments may be carried out without or in other ways of certain details. In other examples, well-known structures or operations are not shown in detail to avoid obscuring the embodiments disclosed herein. Embodiments are not limited by the illustrated order of operations or events, as some operations may occur in different orders and / or simultaneously with other operations or events. Furthermore, not all illustrated operations or events are required to carry out the methodologies of the embodiments.

[0546] Although numerical ranges and parameters representing a wide range are approximations, the numerical values ​​shown in certain non-limiting examples are reported as accurately as possible. However, any numerical value inherently contains certain errors that inevitably arise from the standard deviation observed in each test measurement. Furthermore, all ranges disclosed herein should be understood to encompass all subranges contained within them. For example, the range "less than 10" may include all subranges between (and including) the minimum value 0 and the maximum value 10, i.e., all subranges having a minimum value greater than or equal to 0 and a maximum value less than or equal to 10, for example, from 1 to 4.

[0547] According to various embodiments of the present disclosure, each of the above-described components (e.g., a module or a program) may include a single entity or multiple entities, and some of the multiple entities may be located separately in different components. According to various embodiments of the present disclosure, one or more of the above-described components may be omitted, or one or more other components may be added. Alternatively or additionally, multiple components (e.g., a module or a program) may be integrated into a single component. In such cases, according to various embodiments of the present disclosure, the integrated component may still perform one or more functions of each of the multiple components in the same or similar manner as they were performed by the corresponding one of the multiple components before integration. According to various embodiments of the present disclosure, operations performed by a module, program, or another component may be performed sequentially, in parallel, repeatedly, or heuristically, or one or more operations may be performed in a different order, or omitted, or one or more other operations may be added.

[0548] Various embodiments described herein can be implemented as software (e.g., program 1240) containing one or more instructions stored in a storage medium (e.g., internal memory 1236 or external memory 1238) readable by a machine (e.g., electronic device 1201). For example, the machine's processor (e.g., processor 1220 of electronic device 1201) can invoke at least one of the one or more instructions stored in the storage medium and execute it with or without the use of one or more other components under the control of the processor. This can cause the machine to operate to perform at least one function in accordance with the invoked at least one instruction. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-temporary storage medium. Here, the term “non-temporary” simply means that the storage medium is a tangible device and does not contain signals (e.g., electromagnetic waves), but the term does not distinguish between places where data is stored semi-permanently in the storage medium and places where data is stored temporarily in the storage medium.

[0549] According to various embodiments of this disclosure, the methods according to various embodiments of this disclosure may be included in and provided as a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., a compact disc read-only memory (CD-ROM)), or online via an application store, or directly between two user devices (e.g., smartphones) (e.g., by download or upload). If distributed online, at least a portion of the computer program product may be temporarily generated or at least temporarily stored in a machine-readable storage medium such as the memory of a manufacturer's server, an application store server, or an intermediary server.

[0550] The electronic device 1201 may include an accelerometer (ACC) and / or a gyroscope 1282, a Global Positioning System (GPS) 1280 and / or an inertial navigation device (INU) 1284 to determine its own position.

[0551] The aspects of the embodiments will be described below with reference to flowcharts and / or block diagrams of the methods, apparatus (systems), and computer program products according to the embodiments. It will be understood that each block in the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by machine-readable program instructions.

[0552] The “step-by-step process” for performing the functions claimed herein is a specific algorithm, which may be shown in the text and / or in a flowchart as a mathematical formula. Instructions in a software program create a dedicated machine for performing the specific algorithm. Thus, in any means-plus-function claim herein where the disclosed structure is a computer or microprocessor programmed to perform the algorithm, the disclosed structure is not a general-purpose computer but rather a dedicated computer programmed to perform the disclosed algorithm.

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

[0554] Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as those commonly understood by those skilled in the art in the field to which the embodiments belong. Terms such as those defined in commonly used dictionaries should be interpreted as having the same meaning as their meanings in the context of the relevant art, and it will be further understood that they should not be interpreted in an idealized or overly formal sense unless expressly defined herein.

[0555] In particular, as is evident from the discussion, unless otherwise specified, any discussion using terms such as “processing,” “computing,” “calculating,” “determining,” or “displaying” throughout the explanation is understood to refer to the operation and processes of a computer system or similar electronic computing device that manipulates data represented as physical (electronic) quantities in the registers and memory of a computer system and converts it into other data similarly represented as physical quantities in the memory or registers of a computer system or other such data storage, transmission device, or display device.

[0556] "Communication medium" typically includes computer-readable instructions, data structures, program modules, or other data within a modulated data signal, such as a carrier or other transmission mechanism. A communication medium may also include any information distribution medium. The term "modulated data signal" means a signal having one or more of its properties configured or modified to encode information within the signal. Examples, but not limited to, include wired media such as wired networks or direct wired connections, and wireless media such as acoustic, infrared, and other wireless media. Any combination of the above also falls within the scope of computer-readable media.

[0557] Alternatively or additionally, any of the functions and programming modules described herein may be performed, at least in part, by one or more hardware logic components. For example, but not limited to, 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, and complex programmable logic devices.

[0558] As used herein, the terms “module” and “component” generally refer to software, firmware, hardware, or a combination thereof. In the case of a software implementation, a module or component represents program code that performs a specified task to be executed on a processor. The program code may be stored in one or more computer-readable memory devices, otherwise known as non-temporary devices. The features of the embodiments described herein are platform-independent, meaning that the technology can be implemented on a variety of commercial computing platforms having various processors (e.g., set-top boxes, desktops, laptops, notebooks, tablet computers, personal digital assistants (PDAs), mobile phones, smartphones, game consoles, wearable devices, IoT devices, etc.).

[0559] According to various embodiments, each of the above-described components (e.g., a module or a program) may include a single entity or multiple entities, and some of the multiple entities may be placed separately in different components. According to various embodiments, one or more of the above-described components may be omitted, or one or more other components may be added. Alternatively or additionally, multiple components (e.g., a module or a program) may be integrated into a single component. In such cases, according to various embodiments, the integrated component can still perform one or more functions of each of the multiple components in the same or similar manner as they were performed by the corresponding one of the multiple components before integration. According to various embodiments, the operations performed by a module, program, or another component may be performed sequentially, in parallel, repeatedly, or heuristically, or one or more operations may be performed in a different order, or omitted, or one or more other operations may be added.

[0560] The terms used herein are intended to describe only specific embodiments and are not intended to limit them. Where used herein, the singular forms “a,” “an,” and “the” are intended to include the plural form unless the context clearly indicates otherwise. Furthermore, wherever the terms “including,” “includes,” “having,” “has,” and “with,” or their variations thereof, are used in either the detailed description and / or the claims, such terms are intended to be as comprehensive as the term “comprising.” Furthermore, unless otherwise specified, the use of terms such as “first,” “second,” etc., does not indicate any order or importance; rather, terms such as “first,” “second,” etc., are used to distinguish one element from another.

[0561] While various disclosed embodiments have been described above, it should be understood that they are presented only as examples and not as limitations. Many modifications, omissions, and / or additions to the subject matter disclosed herein can be made in accordance with the embodiments disclosed herein without departing from the spirit or scope of the embodiments. Equivalents can also be used in place of elements without departing from the spirit and scope of the embodiments. Furthermore, while certain features may be disclosed in relation to only one of several implementations, such features can be combined with one or more other features of other implementations so as may be desired and advantageous for any given or particular application. Furthermore, many modifications can be made without departing from the scope to adapt the teachings of the embodiments to specific circumstances or materials.

[0562] Furthermore, the purpose of the abstract is to enable the public to quickly determine the nature and essence of this technical disclosure from a rough examination. The abstract is not intended in any way to limit the scope of this disclosure.

[0563] Therefore, the breadth and scope of the subject matter provided herein should not be limited by any of the embodiments explicitly described above. Rather, the scope of the embodiments should be defined according to the following claims and their equivalents.

[0564] Wherever an element is referred to as being "connected" to or from another element in this specification, that element may be connected to the other element directly or indirectly, and indirect connection shall be understood to include "connection via a wireless communication network."

[0565] Throughout this specification, when one member is "on" another member, this includes not only when the member is in contact with the other member, but also when there is another member between the two members.

[0566] Here, the expression "at least one of a, b [and / or] c" means "a only," "b only," "c only," "both a and b," "both a and c," "both b and c," or "all of a, b and c."

[0567] The various exemplary methods described herein may represent a particular set of operations, but such a set of operations can be modified without departing from the scope of this disclosure. For example, some of the operations described may be performed in parallel or in a different order that does not substantially affect the function of the method. In other examples, different components of an exemplary device or system implementing the method may perform their functions substantially simultaneously or in a particular order. In one or more embodiments, consecutive blocks may be omitted or added.

Claims

1. Assigning a tracking device to a passenger's luggage using at least one of the processors, At least one of the aforementioned processors loads information from the baggage source message (BSM) into the tracking device, and The tracking device transmits location information to a network interface of a computing system associated with the at least one processor, wherein the location information includes location coordinate data of the tracking device and the information from the BSM. Methods that include...

2. The assignment includes providing the tracking device with at least one of the following: a passenger reservation record (PNR) number, an International Air Transport Association (IATA) license plate number, or a global multimode travel (GMMT) bag tag number, by at least one of the at least one processors. The aforementioned method, The network interface of the computing system receives the location information, and At least one of the aforementioned processors uses the tracking device to locate the package, The method according to claim 1, further comprising:

3. The aforementioned passengers include registered passengers who have a baggage handling system, The method according to claim 2, wherein the BSM includes a Global Tracking Extended Baggage Source Message (GTE-BSM) that links the GMMT bag tag number with the PNR number or the IATA license plate number.

4. The method according to claim 3, wherein the information from the BSM includes the IATA license plate number of another piece of luggage associated with the registered passenger.

5. The method according to claim 3, wherein the information from the BSM includes the IATA license plate number of another piece of luggage associated with an unregistered passenger associated with the PNR number.

6. The method according to claim 1, wherein the BSM is an airline BSM.

7. The method according to claim 1, wherein the computing system is associated with one of an airline, a baggage handling system, or a mobile vehicle.

8. The method according to claim 1, wherein the tracking device includes an inertial navigation system for environments where a Global Navigation Satellite System (GNSS) is absent.

9. The method according to claim 8, further comprising: the tracking device communicating current location information to the network interface of the computing system using one of the ad-hoc communication protocol, Wireless Fidelity (Wi-Fi) communication protocol, Bluetooth communication protocol, and cellular communication protocol when an ad-hoc connection is within range, a Wi-Fi device is within range, a Bluetooth-enabled device is within range, or a cellular tower is within range.

10. At least one of the aforementioned processors determines that the reference indicator of the BSM represents the normal route of the luggage. At least one of the aforementioned processors determines that the reference indicator of the received Type B message represents the unstructured route of the luggage. At least one of the above-mentioned processors accesses the location information generated by the tracking device to find the current location of the luggage, and At least one of the above-mentioned processors generates a delivery command to reroute the package using the current location. The method according to claim 1, further comprising:

11. A computing system including at least one processor and a network interface, At least one non-temporary tangible memory communicably coupled to the at least one processor, wherein the at least one memory stores at least one instruction, and A tracking device configured to transmit location information to the aforementioned network interface, The at least one processor executes the at least one instruction, Assigning the aforementioned tracking device to the passenger's luggage, and Loading information from the baggage source message (BSM) into the tracking device, It is configured to do the following: The system includes the positional coordinate data of the tracking device and the information from the BSM.

12. The at least one processor executes the at least one instruction, Assigning the tracking device to the baggage by providing the tracking device with at least one of the following: passenger reservation record (PNR) number, International Air Transport Association (IATA) license plate number, or Global Multimode Movement (GMMT) bag tag number. The network interface receives the location information, and The system according to claim 11, further configured to locate the package using the tracking device.

13. The aforementioned passengers include registered passengers who have a baggage handling system, The system according to claim 12, wherein the BSM includes a Global Tracking Extended Baggage Source Message (GTE-BSM) that links the GMMT bag tag number with the PNR number or the IATA license plate number.

14. The system according to claim 13, wherein the information from the BSM includes the IATA license plate number of another piece of luggage associated with the registered passenger.

15. The system according to claim 13, wherein the information from the BSM includes the IATA license plate number of another piece of luggage associated with an unregistered passenger associated with the PNR number.

16. The system according to claim 11, wherein the BSM is an airline BSM.

17. The system according to claim 11, wherein the computing system is associated with one of an airline, a baggage handling system, or a mobile vehicle.

18. The system according to claim 11, wherein the tracking device includes an inertial navigation system for environments in which a Global Navigation Satellite System (GNSS) is not present.

19. The system according to claim 18, wherein the tracking device is further configured to communicate current location information to the network interface of the computing system using one of the ad-hoc communication protocol, Wireless Fidelity (Wi-Fi) communication protocol, Bluetooth communication protocol, and cellular communication protocol when an ad-hoc connection is within range, a Wi-Fi device is within range, a Bluetooth-enabled device is within range, or a cellular tower is within range.

20. The at least one processor executes the at least one instruction, Determining whether the BSM reference indicator represents the normal route of the luggage, The reference indicator of the received Type B message is determined to represent the non-standard route of the luggage. Accessing the location information generated by the tracking device in order to find the current location of the luggage, and To generate a delivery order to reroute the package using the current location. The system according to claim 11, further configured to perform the following:

21. A non-temporary computer-readable medium storing instructions, wherein when an instruction is executed by at least one processor, the at least one processor receives At least one of the aforementioned processors assigns a tracking device to the passenger's luggage. At least one of the aforementioned processors loads information from the baggage source message (BSM) into the tracking device, and A non-temporary computer-readable medium that causes the tracking device to perform a method of transmitting location information to a network interface of a computing system associated with the at least one processor, wherein the location information includes location coordinate data of the tracking device and the information from the BSM.

22. The assignment includes providing the tracking device with at least one of the following: a passenger reservation record (PNR) number, an International Air Transport Association (IATA) license plate number, or a global multimode travel (GMMT) bag tag number, by at least one of the at least one processors. The aforementioned method, The network interface of the computing system receives the location information, and At least one of the aforementioned processors uses the tracking device to locate the package, The non-temporary computer-readable medium according to claim 21, further comprising:

23. The aforementioned passengers include registered passengers who have a baggage handling system, The non-temporary computer-readable medium according to claim 22, wherein the BSM includes a Global Tracking Extended Baggage Source Message (GTE-BSM) that links the GMMT bag tag number with the PNR number or the IATA license plate number.

24. The information from the BSM includes the IATA license plate number of another piece of luggage associated with the registered passenger, in the non-temporary computer-readable medium according to claim 23.

25. The non-temporary computer-readable medium according to claim 23, wherein the information from the BSM includes the IATA license plate number of another piece of luggage associated with an unregistered passenger associated with the PNR number.

26. The non-temporary computer-readable medium according to claim 21, wherein the BSM is an airline BSM.

27. The computing system is associated with one of an airline, a baggage handling system, or a mobile vehicle, as described in claim 21, for the non-temporary computer-readable medium.

28. The tracking device includes an inertial navigation system for environments where a Global Navigation Satellite System (GNSS) is absent, as described in claim 21, for the non-transient computer-readable medium.

29. The aforementioned method, The non-temporary computer-readable medium according to claim 28, further comprising the tracking device communicating current location information to the network interface of the computing system using one of the ad-hoc communication protocol, Wireless Fidelity (Wi-Fi) communication protocol, Bluetooth communication protocol, and cellular communication protocol when one of the following is within range: an ad-hoc connection, a Wi-Fi device, a Bluetooth-enabled device, or a cellular tower.

30. The aforementioned method, At least one of the aforementioned processors determines that the reference indicator of the BSM represents the normal route of the luggage. At least one of the aforementioned processors determines that the reference indicator of the received Type B message represents the unstructured route of the luggage. At least one of the above-mentioned processors accesses the location information generated by the tracking device to find the current location of the luggage, and At least one of the above-mentioned processors generates a delivery command to reroute the package using the current location. The non-temporary computer-readable medium according to claim 21, further comprising:

31. The tracking device stores the travel request number associated with the passenger in at least one memory location. The aforementioned tracking device is paired with a service device associated with an airline, airport, government agency, or business entity. The tracking device transmits the mobile application number to the service device, and The service device is to perform a function based on the received travel request number, and the tracking device is to be attached to the passenger's luggage. A method that includes this.

32. The aforementioned tracking device stores digital certificates, and The aforementioned tracking advice requires the service device to request authentication using the digital certificate. The method according to claim 31, further comprising:

33. The method according to claim 31, further comprising communicating location information to a computing system associated with tracking the luggage, independently of the passenger's mobile communication device, wherein the location information represents the location information of the luggage.

34. The method according to claim 31, wherein the transfer request number includes a passenger reservation record (PNR) number, the service device includes a kiosk including a bag tag printer, and the function includes printing an International Air Transport Association (IATA) compliant bag tag.

35. The aforementioned travel application number includes the International Air Transport Association (IATA) license plate number, the service device includes the baggage handling device of the airport's baggage handling system, and the function includes communicating a pseudo-identification number to a security screening machine. The method according to claim 31, wherein the tracking device is configured to receive the pseudo-identification number when the package is in close proximity to the service device and the security screening machine.

36. The method according to claim 35, wherein the pseudo-identification number includes a primary number associated with a stored security screening image captured by the security screening machine.

37. The aforementioned transfer application number includes the International Air Transport Association (IATA) license plate number, the service device includes the baggage handling device of the airport's baggage handling system, and the function includes communicating a unique bag identification number to a security screening machine. The method according to claim 31, wherein the tracking device is configured to receive the unique bag identification number when the package is in close proximity to the service device and the security screening machine.

38. The method according to claim 37, wherein the unique bag identification number includes a primary number associated with a stored security screening image captured by the security screening machine.

39. The tracking device will pair with the passenger's mobile communication device, and To communicate the aforementioned travel application number via a mobile communication device, wherein the aforementioned travel application number includes the passenger reservation record (PNR) number. The method according to claim 31, further comprising:

40. The method according to claim 39, further comprising receiving personally identifiable information from the passenger's mobile communication device by a tracking device.

41. The method according to claim 40, further comprising storing the personally identifiable information in at least one memory.

42. The aforementioned personally identifiable information is, The passenger's date of birth, The name of the passenger mentioned above, The aforementioned passenger's social security number, The passenger's passport identification number, or Government-issued identification number, The method according to claim 41, comprising at least one of the following.

43. Storing the movement application number in at least one memory of the tracking device is, The method according to claim 31, further comprising storing baggage source message (BSM) information by the tracking device, wherein the BSM information includes a plurality of move request numbers.

44. The aforementioned multiple transfer application numbers are, Passenger reservation record (PNR) number, and International Air Transport Association (IATA) license plate number, The method according to claim 43, including the method described in claim 43.

45. The aforementioned BSM information includes a reference indicator. The aforementioned method, The tracking device receives at least one reference indicator from the second service device. The tracking device compares the at least one reference indicator with the reference indicator included in the BSM information. The tracking device determines that an unstructured reference indicator has been received, and The tracking device provides notification of an unstructured reference indicator to a computing system associated with tracking the package. The method according to claim 43, further comprising:

46. The method according to claim 31, further comprising communicating location information by the tracking device to the computing system associated with tracking the package, wherein the location information represents location information of the package.

47. The tracking device is configured to communicate using at least one of the following: Wireless Fidelity (Wi-Fi) communication protocol, Bluetooth communication protocol, cellular communication protocol, long-range radio frequency communication protocol, short-range communication protocol, near-field communication protocol, and global system for mobile communications. The aforementioned method, The method according to claim 31, further comprising communicating the current location information to a computing system associated with tracking the package using the tracking device.

48. The aforementioned mobile application number includes the International Air Transport Association (IATA) license plate number, The aforementioned method, The method according to claim 31, further comprising the tracking device transmitting the move request number to a radio frequency identification (RFID) receiver of a baggage handling system (BHS), the BHS routing the baggage based on baggage source message (BSM) information accessed using the move request number.

49. The tracking device is equipped with a display screen, and the mobile application number includes the International Air Transport Association (IATA) license plate number. The aforementioned method, The method according to claim 31, further comprising causing the tracking device to display the IATA license plate having the IATA license plate number on the display screen.

50. It is a tracking device, At least one processor, and A tracking device comprising at least one non-temporary tangible memory communicably coupled to the at least one processor, wherein the at least one memory stores at least one instruction, The at least one processor executes the at least one instruction, The memory contains the travel application number associated with the passenger. Pairing the aforementioned tracking device with a service device associated with an airline, airport, government agency, or business entity, and To transmit the aforementioned mobile application number to the service device. It is configured to do the following: The aforementioned mobile application number is configured to cause the service device to perform a function when the mobile application device is received by the service device. The tracking device is attached to the passenger's luggage, and the system is such that the tracking device is attached to the passenger's luggage.

51. The at least one processor executes the at least one instruction, Storing the digital certificate in at least one of the memories, and The service device requests authentication using the aforementioned digital certificate. The system according to claim 50, further configured to perform the following:

52. The at least one processor executes the at least one instruction, The system according to claim 50, further configured to communicate location information to a computing system associated with tracking the luggage, independently of the passenger's mobile communication device, wherein the location information represents the location information of the luggage.

53. The system according to claim 50, wherein the transfer request number includes a passenger reservation record (PNR) number, the service device includes a kiosk including a bag tag printer, and the function includes printing an International Air Transport Association (IATA) compliant bag tag.

54. The aforementioned travel application number includes the International Air Transport Association (IATA) license plate number, the service device includes the baggage handling device of the airport's baggage handling system, and the function includes communicating a pseudo-identification number to a security screening machine. The at least one processor executes the at least one instruction, The system according to claim 50, further configured to receive the pseudo-identification number when the package is in close proximity to the service device and the security screening machine.

55. The system according to claim 54, wherein the pseudo-identification number includes a primary number associated with a stored security screening image captured by the security screening machine.

56. The aforementioned transfer application number includes the International Air Transport Association (IATA) license plate number, the service device includes the baggage handling device of the airport's baggage handling system, and the function includes communicating a unique bag identification number to a security screening machine. The at least one processor executes the at least one instruction, The unique bag identification number is received when the luggage is in close proximity to the service device and the security screening machine. The system according to claim 50, further configured to perform the following:

57. The system according to claim 56, wherein the unique bag identification number includes a primary number associated with a stored security screening image captured by the security screening machine.

58. The at least one processor executes the at least one instruction, Pairing the tracking device with the passenger's mobile communication device, The mobile communication device is to transmit the travel application number, wherein the travel application number includes the passenger reservation record (PNR) number. The system according to claim 50, further configured to perform the following:

59. The at least one processor executes the at least one instruction, The system according to claim 58, further configured to receive personally identifiable information from the passenger's mobile communication device.

60. The at least one processor executes the at least one instruction, The system according to claim 59, further configured to store the personally identifiable information in at least one memory.

61. The aforementioned personally identifiable information is, The passenger's date of birth, The name of the passenger mentioned above, The aforementioned passenger's social security number, The passenger's passport identification number, or Government-issued identification number, The system according to claim 60, comprising at least one of the following.

62. The at least one processor executes the at least one instruction, The memory to store baggage source message (BSM) information, wherein the BSM information includes a plurality of travel request numbers. The method according to claim 50, further configured to perform

63. The aforementioned multiple transfer application numbers are, Passenger reservation record (PNR) number, and International Air Transport Association (IATA) license plate number, The method according to claim 62, including the method described in claim 62.

64. The aforementioned BSM information includes a reference indicator. The at least one processor executes the at least one instruction, Receiving at least one reference indicator from the second service device, Comparing the at least one reference indicator with the reference indicator included in the BSM information, Determining that an unstructured reference indicator has been received, and To provide a notification of an unstructured reference indicator to a computing system associated with tracking the aforementioned package, The method according to claim 62, further configured to perform the following:

65. The at least one processor executes the at least one instruction, The system according to claim 50, further configured to communicate location information by notification to the computing system associated with tracking the said package, wherein the location information represents location information of the package.

66. The tracking device is configured to communicate using at least one of the following: Wireless Fidelity (Wi-Fi) communication protocol, Bluetooth communication protocol, cellular communication protocol, long-range radio frequency communication protocol, short-range communication protocol, near-field communication protocol, and global system for mobile communications. The at least one processor executes the at least one instruction, The system according to claim 50, further configured to communicate current location information to a computing system associated with tracking the aforementioned package.

67. The aforementioned mobile application number includes the International Air Transport Association (IATA) license plate number, The at least one processor executes the at least one instruction, The system according to claim 50, further comprising transmitting the transfer request number to a radio frequency identification (RFID) receiver of a baggage handling system (BHS), wherein the BHS is configured to route and transmit the baggage based on baggage source message (BSM) information accessed using the transfer request number.

68. The tracking device further comprises a display screen, and the mobile application number includes the International Air Transport Association (IATA) license plate number. The at least one processor executes the at least one instruction, The system according to claim 50, further configured to display an IATA license plate having the IATA license plate number on the display screen.

69. A non-temporary computer-readable medium storing instructions, wherein when an instruction is executed by at least one processor, the at least one processor receives The tracking device stores the travel request number associated with the passenger in at least one memory location. The aforementioned tracking device is paired with a service device associated with an airline, airport, government agency, or business entity. The tracking device transmits the mobile application number to the service device, and A non-temporary computer-readable medium that causes the service device to perform a function based on the received travel request number, the tracking device being affixed to the passenger's luggage, and the method of causing the service device to perform such a function.

70. The aforementioned method, The aforementioned tracking device stores digital certificates, and The aforementioned tracking advice requires the service device to request authentication using the digital certificate. A non-temporary computer-readable medium according to claim 69, further comprising:

71. The aforementioned method, The non-temporary computer-readable medium according to claim 69, further comprising communicating location information to a computing system associated with tracking the luggage, independently of the passenger's mobile communication device, wherein the location information represents the location information of the luggage.

72. The non-temporary computer-readable medium according to claim 69, wherein the transfer request number includes a passenger reservation record (PNR) number, the service device includes a kiosk including a bag tag printer, and the function includes printing an International Air Transport Association (IATA) compliant bag tag.

73. The aforementioned travel application number includes the International Air Transport Association (IATA) license plate number, the service device includes the baggage handling device of the airport's baggage handling system, and the function includes communicating a pseudo-identification number to a security screening machine. The non-temporary computer-readable medium according to claim 69, wherein the tracking device is configured to receive the pseudo-identification number when the package is in close proximity to the service device and the security screening machine.

74. The non-temporary computer-readable medium according to claim 73, wherein the pseudo-identification number includes a primary number associated with a stored security screening image captured by the security screening machine.

75. The aforementioned transfer application number includes the International Air Transport Association (IATA) license plate number, the service device includes the baggage handling device of the airport's baggage handling system, and the function includes communicating a unique bag identification number to a security screening machine. The non-temporary computer-readable medium according to claim 69, wherein the tracking device is configured to receive the unique bag identification number when the package is in close proximity to the service device and the security screening machine.

76. The non-temporary computer-readable medium according to claim 75, wherein the unique bag identification number includes a primary number associated with a stored security screening image captured by the security screening machine.

77. The aforementioned method, The tracking device will pair with the passenger's mobile communication device, and To communicate the aforementioned travel application number via a mobile communication device, wherein the aforementioned travel application number includes the passenger reservation record (PNR) number. A non-temporary computer-readable medium according to claim 69, further comprising:

78. The aforementioned method, The non-temporary computer-readable medium according to claim 77, further comprising receiving personally identifiable information from the passenger's mobile communication device by a tracking device.

79. The aforementioned method, The non-temporary computer-readable medium according to claim 78, further comprising storing the personally identifiable information in at least one of the memories.

80. The aforementioned personally identifiable information is, The passenger's date of birth, The name of the passenger mentioned above, The aforementioned passenger's social security number, The passenger's passport identification number, or Government-issued identification number, A non-temporary computer-readable medium according to claim 79, comprising at least one of the following.

81. Storing the movement application number in at least one memory of the tracking device is, The non-temporary computer-readable medium according to claim 69, further comprising storing baggage source message (BSM) information, wherein the tracking device stores a plurality of move request numbers.

82. The aforementioned multiple transfer application numbers are, Passenger reservation record (PNR) number, and International Air Transport Association (IATA) license plate number, A non-temporary computer-readable medium according to claim 81, including the following:

83. The aforementioned BSM information includes a reference indicator. The aforementioned method, The tracking device receives at least one reference indicator from the second service device. The tracking device compares the at least one reference indicator with the reference indicator included in the BSM information. The tracking device determines that an unstructured reference indicator has been received, and The tracking device provides notification of an unstructured reference indicator to a computing system associated with tracking the package. A non-temporary computer-readable medium according to claim 81, further comprising:

84. The aforementioned method, The non-temporary computer-readable medium according to claim 69, further comprising communicating location information by the tracking device to the computing system associated with tracking the package, wherein the location information represents location information of the package.

85. The tracking device is configured to communicate using at least one of the following: Wireless Fidelity (Wi-Fi) communication protocol, Bluetooth communication protocol, cellular communication protocol, long-range radio frequency communication protocol, short-range communication protocol, near-field communication protocol, and global system for mobile communications. The aforementioned method, The non-temporary computer-readable medium according to claim 69, further comprising communicating current location information to a computing system associated with tracking the package via the tracking device.

86. The aforementioned mobile application number includes the International Air Transport Association (IATA) license plate number, The aforementioned method, The non-temporary computer-readable medium according to claim 69, further comprising the tracking device transmitting the movement request number to a radio frequency identification (RFID) receiver of a baggage handling system (BHS), the BHS routing the baggage based on baggage source message (BSM) information accessed using the movement request number.

87. The tracking device is equipped with a display screen, and the mobile application number includes the International Air Transport Association (IATA) license plate number. The aforementioned method, The non-temporary computer-readable medium according to claim 69, further comprising the tracking device causing the display screen to display the IATA license plate having the IATA license plate number.

Images