System and method for creating luggage manifest using a b-type message and a passenger name record number
US-2024404325-A1 · Dec 5, 2024 · US
US12536841B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12536841-B2 |
| Application number | US-202418913028-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 11, 2024 |
| Priority date | Feb 1, 2023 |
| Publication date | Jan 27, 2026 |
| Grant date | Jan 27, 2026 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Provided is a system and method for passenger matching and baggage release, the method including: generating a manifest listing passengers, wherein the manifest includes a passenger manifest data record having manifest data fields for each passenger listed therein; monitoring at least one computer system associated with a security authority, wherein the security authority processes the plurality of passengers for border crossing at a border crossing airport; detecting a clearance processing event of a passenger record of a respective passenger among the passengers created by the at least one computer system associated with the security authority, by matching the passenger record with a respective passenger manifest data record; and based on detecting the clearance processing event, communicating a baggage release message to a baggage scanning system of an identified airline, a computing device of a baggage handler or a baggage handling system, wherein the baggage release message is configured to cause a held checked-in luggage item associated with the respective passenger to be released.
Opening claim text (preview).
What is claimed is: 1 . A method comprising: a) generating, by at least one of at least one processor, at least one manifest listing a plurality of passengers, wherein each of the at least one manifest comprises a passenger manifest data record having manifest data fields for each passenger listed therein; b) monitoring, by a passenger matching and bag release system, at least one computer system associated with a security authority, wherein the security authority processes the plurality of passengers for border crossing at a border crossing airport; c) detecting, in near real time by the passenger matching and bag release system, a clearance processing event of a passenger record of a respective passenger among the plurality of passengers created by the at least one computer system associated with the security authority, by matching the passenger record with a respective passenger manifest data record; and d) based on detecting the clearance processing event, communicating, through a network interface coupled to the passenger matching and bag release system and a communication network, a baggage release message to a baggage scanning system of an identified airline, a computing device of a baggage handler or a baggage handling system, wherein the baggage release message is configured to cause a held checked-in luggage item associated with the respective passenger to be released. 2 . The method of claim 1 , further comprising, prior to a): e) obtaining, by at least one of the at least one processor, from an electronic passenger list information message (PLIM) having a message format, passenger data for the plurality of passengers, the passenger data comprising a unique passenger identifier (UPID) assigned by a Departure Control System (DCS) of an originating airline for each of the plurality of passengers, wherein the electronic PLIM identifies a flight carrying the plurality of passengers that will border cross at the border crossing airport; and f) depersonalizing the passenger data by replacing personal identifying information with a computer generated identifier. 3 . The method of claim 2 , further comprising, prior to e): receiving, through a second network interface coupled to at least one of the at least one processor and a second communication network, the electronic PLIM from the DCS or from a computer messaging system associated with the originating airline. 4 . The method of claim 2 , wherein the manifest data fields comprise at least one of the UPID of the respective passenger and a baggage tag identifier of each checked-in luggage item of the respective passenger, and wherein the method further comprises: g) repeating b)-d) for each of the plurality of passengers listed in the at least one manifest. 5 . The method of claim 2 , wherein e) further comprises: obtaining, by at least one of the at least one processor, a baggage tag identifier for each checked-in luggage item of each of the plurality of passengers, and wherein the communicating, through the network interface coupled to the passenger matching and bag release system and the communication network, comprises: communicating the baggage tag identifier for each checked-in luggage item of the passenger in at least one baggage release message to the baggage scanning system of the identified airline or to the baggage handling system, wherein the at least one baggage release message is configured to cause the baggage scanning system of the identified airline to release each check-in luggage item to be transferred to another flight or to cause the baggage handling system to release each checked-in luggage item to a carousel to leave the border crossing airport. 6 . The method of claim 2 , wherein the electronic PLIM comprises one of a passenger final sales message, a passenger reconcile message, a passenger name list message, an advance passenger information (API) message, a passenger list message, or a PNRgov message. 7 . The method of claim 1 , further comprising, prior to a): e) obtaining, by at least one of the at least one processor, from an electronic passenger list information message (PLIM) having a message format, passenger data for the plurality of passengers, wherein the electronic PLIM identifies a vehicle associated with a mode of travel carrying the plurality of passengers that will border cross at a border crossing port. 8 . The method of claim 7 , further comprising: g) repeating b)-d) for each of the plurality of passengers listed in the at least one manifest. 9 . The method of claim 7 , wherein the vehicle is a cruise ship. 10 . The method of claim 7 , further comprising: determining, by at least one of the at least one processor, each checked-in luggage item identified in the baggage release message that is associated with corresponding return flight information for a return flight with a designated air carrier; and processing, by at least one of the at least one processor, each checked-in luggage item associated with the corresponding return flight information, after each such checked-in luggage item is released. 11 . The method of claim 7 , further comprising: determining, by at least one of the at least one processor, each checked-in luggage item identified in the baggage release message that is associated with corresponding luggage item handling instructions for at least one vehicle of travel; and processing, by at least one of the at least one processor, each checked-in luggage item associated with the corresponding luggage item handling instructions for the at least one vehicle of travel according to the corresponding luggage item handling instructions, after each such checked-in luggage item is released. 12 . A system comprising: at least one memory storing one or more instructions; and at least one processor configured to execute the one or more instructions, wherein the one or more instructions, when executed by the at least one processor, cause the system to: a) generate at least one manifest listing a plurality of passengers, wherein each of the at least one manifest comprises a passenger manifest data record having manifest data fields for each passenger listed therein, b) monitor, by a passenger matching and bag release system, at least one computer system associated with a security authority, wherein the security authority processes the plurality of passengers for border crossing at a border crossing airport, c) detect, in near real time by the passenger matching and bag release system, a clearance processing event of a passenger record of a respective passenger among the plurality of passengers created by the at least one computer system associated with the security authority, by matching the passenger record with a respective passenger manifest data record, and d) based on detecting the clearance processing event, communicate, through a network interface of the system coupled to the passenger matching and bag release system and a communication network, a baggage release message to a baggage scanning system of an identified airline, a computing device of a baggage handler or a baggage handling system, wherein the baggage release message is configured to cause a held checked-in luggage item associated with the respective passenger to be released. 13 . The system of claim 12 , wherein the one or more instructions, when executed by the at least one processor, cause the system to, prior to a): e) obtain, from an electronic passenger list information message (PLIM) having a message format, passenger data for the plurality of passengers, the passenger data comprising a unique passenger identifier (UPID) assig
in the form of a badge to be worn by a person · CPC title
Forms specially designed for commercial use, e.g. bills, receipts, offer or order sheets, coupons · CPC title
Apparatus for validating or cancelling issued tickets · CPC title
Business processing using cryptography · CPC title
Business processes related to the transportation industry (shipping G06Q10/083) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.