Nfc triggered chain of responsibility generation method and system for air travel check-in

By reading the unique identification code at the handover node using NFC smart baggage tags, encapsulating the responsibility transfer event unit, and performing gating judgment, the problems of incomplete records and responsibility traceability in air travel baggage handover management are solved, and the generation of a continuous and accurate responsibility transfer chain is realized.

CN123070832APending Publication Date: 2026-11-10CIVIL AVIATION FLIGHT UNIV OF CHINA
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611595199.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-10-15
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

Existing methods for managing air travel baggage handover suffer from problems such as incomplete records, difficulty in tracing responsibility, low efficiency, fragmented data, and a lack of mechanisms for encapsulating responsibility transfer events and handling anomalies.

Method used

The method of generating a responsibility transfer chain using NFC-triggered method reads the unique identification code at the handover node through an NFC smart luggage tag, encapsulates the responsibility transfer event unit, and performs write gating judgment based on the historical responsibility chain to form a continuous responsibility transfer chain, supporting offline temporary storage and online compensation.

Benefits of technology

It ensures the continuity and accuracy of baggage handover records, can quickly locate responsible nodes, prevents abnormal records from polluting the formal chain, and supports data synchronization in offline environments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123070832A_ABST
    Figure CN123070832A_ABST
Patent Text Reader

Abstract

The application discloses an NFC trigger type responsibility transfer chain generation method and system for air travel luggage handover, and belongs to the field of logistics information technology. The method aims at the technical problems of unclear responsibility definition, easily tampered records and lost data in the process of multi-subject handover of air travel luggage, takes the NFC tag touch behavior as the responsibility transfer trigger entry, collects order, node, handover party, receiving party, space-time and state information through a mobile terminal, and encapsulates the information into a structured responsibility transfer event unit. The application maps the handover node to a standard contact system, introduces a responsibility chain writing gate mechanism, carries out connection verification on the current event based on the historical responsibility chain, and only allows writing into the formal responsibility chain when the score meets the standard, thereby avoiding abnormal records such as node jumping or authority inconsistency to pollute the data. The integrity, continuity and traceability of the whole-process responsibility chain of the luggage from the door-to-door collection to the destination delivery are ensured, and the efficiency of luggage abnormal disposal and responsibility division is significantly improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of logistics information technology, specifically to an NFC-triggered responsibility transfer chain generation method and system for air baggage handover. Background Technology

[0002] During air travel, passenger baggage typically undergoes multiple handover stages, including door-to-door pickup, transport handover, city terminal handover, airport handover, security check or sorting handover, and final delivery to the destination. These stages often involve multiple stakeholders, including passengers, pickup personnel, transport personnel, airport handover personnel, delivery personnel, and back-office management personnel. The accuracy of each handover record directly impacts the traceability of the baggage transfer process, the allocation of responsibility, and the efficiency of handling anomalies.

[0003] Current baggage handover management methods mainly rely on paper documents, manual signatures, barcode scanning, QR code recognition, RFID reading, or manual data entry in the back office to complete the record-keeping. While these methods can record baggage transfer information to some extent, they still have the following shortcomings.

[0004] First, traditional paper-based handover records are easily lost, damaged, or tampered with, making it difficult to establish a complete, continuous, and reliable handover chain. When luggage is delayed, misdelivered, lost, or damaged, it is difficult to quickly locate the responsible party and personnel.

[0005] Second, while ordinary barcodes, QR codes, or RFID / NFC tags can identify baggage numbers, they are essentially used to identify baggage identity or record where baggage has passed through a certain location. They cannot directly express the complete relationship of "who hands over, who receives, and at what point the transfer of responsibility is completed" in a handover operation.

[0006] Third, in the existing baggage handover process, staff rely heavily on manual verification of orders, baggage tags, and handover slips, which is inefficient and prone to problems such as missed scans, incorrect scans, duplicate scans, and missing node records.

[0007] Fourth, in multi-party collaborative scenarios such as door-to-door pickup, transportation handover, city terminal or airport handover, and destination delivery, the systems of the participating parties may not be fully interconnected, resulting in baggage handover data being stored in a scattered manner, making it difficult to form a unified and continuous chain of responsibility for tracking.

[0008] Fifth, existing baggage end-to-end tracking standards and data exchange specifications mainly focus on tracking key baggage touchpoints, tag reading and writing rules, and data exchange between systems. They can solve problems such as whether baggage is identified and how baggage data is exchanged, but they have not yet provided a mechanism for encapsulating responsibility transfer events, writing responsibility chains into gating, anomaly diversion, and offline compensation merging for each NFC-triggered handover behavior.

[0009] Therefore, it is necessary to propose an NFC-triggered responsibility transfer chain generation method and system for air baggage handover, so that NFC tags are no longer used merely as baggage identification, but as trigger entry points for baggage responsibility transfer. After reading the unique NFC identification code, the system organizes order information, handover node, handover party, recipient, operation time, operation location, terminal device, baggage status, and historical responsibility records into responsibility transfer event units. Based on the responsibility chain writing gating mechanism, it determines whether the event can be continued into the formal responsibility chain, thereby realizing continuous generation of responsibility, anomaly diversion, and offline compensation synchronization in the multi-party handover process of air baggage. Summary of the Invention

[0010] To address the aforementioned shortcomings in the prior art, this invention provides an NFC-triggered responsibility transfer chain generation method and system for air baggage handover.

[0011] To achieve the above-mentioned objectives, the technical solution adopted by this invention is as follows: A method for generating an NFC-triggered responsibility transfer chain for air travel baggage handover includes the following steps: S1. Construct a baggage handover responsibility transfer system architecture, which includes a front-end baggage identification device, a staff mobile terminal, a responsibility transfer event processing unit, a back-end responsibility chain management platform, and an offline compensation synchronization unit. The front-end baggage identification device is a smart baggage tag with a built-in NFC tag. The NFC tag contains a unique identification code corresponding to the baggage. The unique identification code is used to associate passenger order, baggage number, flight information, destination information, and service type business data. S2. Staff members use their mobile terminals to touch and read the NFC smart luggage tag set on the luggage at the luggage handover point, generating an NFC trigger event. S3. Collect the associated information of the current handover based on the NFC trigger event, and encapsulate it to form a responsibility transfer event unit; S4. Map the current handover node to the preset baggage tracking standard contact point system and establish node sequence constraints; S5. Perform continuity verification on the responsibility transfer event unit based on the historical responsibility chain, and execute the responsibility chain write gating judgment; S6. Based on the gating judgment result, write the responsibility transfer event unit into the formal responsibility chain, divert it to the exception handling queue, or temporarily store it as an offline record to be compensated.

[0012] Furthermore, S2 specifically includes: S21. When staff perform handover operations at door-to-door pickup, transportation handover, city terminal or airport handover, and destination delivery nodes, they can approach or touch the NFC smart baggage tag using a mobile terminal. S22. The mobile terminal reads the unique identification code in the NFC tag and simultaneously collects the current operation time, operation location and terminal device number information.

[0013] Furthermore, the responsibility transfer event unit encapsulated in S3 is represented as follows:

[0014] in, This indicates the unique identification code of the NFC smart luggage tag; This indicates the currently matched passenger order information; Indicates the current handover node; Indicates the party currently handing over the goods; Indicates the current recipient; Indicates the current operation time; Indicates the current operation location; Indicates the current terminal device number; Indicates the current status of baggage service; This indicates the previous valid liability record.

[0015] Furthermore, S4 specifically includes: S41. Preset handover node sequence in door-to-door air baggage service ,in, Indicates the door-to-door pickup point; Indicates the transportation handover node; Indicates a junction point between a city terminal or airport; Indicates the destination delivery node; S42. Establish node mapping relationships Map each handover node to a standard baggage tracking contact point. The standard contacts include receiving, loading, transferring, and arriving contacts.

[0016] Furthermore, S5 specifically includes: S51, Calculate the responsibility link continuation score The calculation formula is:

[0017] in, Indicates order consistency score; Indicates node continuity score; This indicates a matching score between the sender and receiver; Indicates the scoring of time sequence; Indicates location continuation scoring; Indicates baggage status connection score; These are weight parameters; S52, Set the scoring threshold ,when When the current responsibility transfer event meets the write condition, the gating result is "write allowed"; when If the current responsibility transfer event does not meet the write conditions, the gating result is to prohibit writing.

[0018] Furthermore, step S6 specifically includes the following steps: S61. When the gating result indicates write permission is granted, a formal handover record is generated. ,in This represents the function that generates the handover record; S62. Link the current record with the previous valid responsibility record through an append operation. Update the chain of responsibility: The For the chain of historical responsibility; S63. When the gating result is write prohibited, the responsibility transfer event unit is diverted to the corresponding queue according to the exception type. The queue includes the order exception queue, node exception queue, personnel exception queue, spatiotemporal exception queue, duplicate read queue, offline conflict queue and queue awaiting manual review. S64. When the mobile terminal is in a state of no network or weak network, the responsibility transfer event unit and the corresponding hash digest will be transferred. Stored locally to create offline records. Offline recording Represented as:

[0019] In the formula, This indicates the unique identification code of the NFC smart luggage tag; This indicates the currently matched passenger order information; Indicates the current handover node; Indicates the party currently handing over the goods; Indicates the current recipient; Indicates the current operation time; Indicates the current operation location; Indicates the current terminal device number; Indicates the current status of baggage service; S65. Once the network is restored, the mobile terminal will record offline. Upload to the backend chain of responsibility management platform; S66. The backend platform performs synchronous verification on offline records. If they are consistent with the historical chain of responsibility, compensation is written; if there is a conflict, the offline record is written to the offline conflict queue. An NFC-triggered responsibility transfer chain generation system for air travel baggage handover includes: The front-end baggage identification module is configured to set an NFC smart baggage tag on the passenger's baggage, wherein the NFC smart baggage tag has a built-in NFC tag that stores a unique identification code; The mobile terminal module is configured to allow staff to touch and read the NFC smart luggage tag at the luggage handover point, generating an NFC trigger event; The event processing module is configured to collect associated information based on the NFC-triggered event and encapsulate it into a responsibility transfer event unit, map the current handover node to the standard contact system, and perform write gating judgment based on the historical responsibility chain; The responsibility chain management module is configured to write responsibility transfer event units into the formal responsibility chain or divert them to the exception handling queue based on the gating judgment result. The offline synchronization module is configured to temporarily store the responsibility transfer event unit as an offline record when the network is abnormal, and perform compensation verification and link merging after the network is restored.

[0020] Furthermore, the event handling module includes: The event encapsulation unit is configured to construct an event feature vector containing the NFC unique identifier, order information, handover node, handover party, recipient, operation time, operation location, terminal device number, luggage status, and previous responsibility record; The touchpoint mapping unit is configured to map door-to-door pickup, transportation handover, city terminal or airport handover, and destination delivery nodes to the standard baggage tracking touchpoint system. The gating judgment unit is configured to calculate the responsibility link continuity score and compare the score result with a preset threshold to output the gating result.

[0021] Furthermore, the offline synchronization module includes: Offline storage unit, configured to store offline responsibility transfer events and their corresponding hash digests locally; The conflict verification unit is configured to compare the consistency between offline records and the historical responsibility chain in the background after the network is restored. The compensation write unit is configured to append offline records to the formal chain of responsibility after the consistency check passes.

[0022] The present invention has the following beneficial effects: First, this invention expands the NFC smart baggage tag from a single identification carrier to a trigger entry point for the baggage responsibility transfer chain. Traditional barcodes, QR codes, RFID, or ordinary NFC tags are mainly used to read baggage numbers, while this invention, based on reading the unique identification code, further encapsulates the information of the giver, receiver, node, time, location, device, and status, so that each baggage handover can form a responsibility transfer event unit.

[0023] Secondly, this invention can improve the continuity and accuracy of baggage handover records. After staff touch and read the NFC tag, the system does not save a record in isolation, but determines whether the current handover event can be continued to the previous valid node based on the historical chain of responsibility, thereby reducing problems such as omissions, errors, node jumps, and process reversals.

[0024] Third, this invention enables the formation of a complete and traceable chain of responsibility for baggage transfer. Each handover record is associated with the previous valid responsibility record, thus fully describing the responsibility transfer process from baggage pickup to delivery to the destination. When baggage is delayed, misdelivered, lost, or damaged, the corresponding handover node, the handover party, the receiving party, and the operation time can be quickly located.

[0025] Fourth, this invention can prevent abnormal records from directly contaminating the formal chain of responsibility. Before writing records, the system verifies them through a chain of responsibility write gating mechanism. Events that fail the verification are diverted to an abnormal queue, a pending audit queue, or an offline conflict queue, instead of being directly written to the formal chain.

[0026] Fifth, this invention supports offline temporary storage and online compensation synchronization. In environments without network or with weak network, staff can still complete NFC tag reading and temporary storage of responsibility transfer events; after the network is restored, the system automatically uploads the offline records and compares, deduplicates, and verifies the continuity with the background responsibility chain to avoid responsibility chain breaks or duplicate writing due to network anomalies.

[0027] Sixth, this invention differs from and complements existing baggage tracking standards, RFID access specifications, baggage data exchange specifications, and visual anomaly detection methods. Existing technologies mainly focus on baggage touchpoint tracking, tag reading and writing, data exchange, or image anomaly detection, while this invention focuses on how responsibility is transferred, continued, and incorporated into the formal chain of responsibility during each baggage handover, as well as how abnormal events are diverted and compensated. Attached Figure Description

[0028] Figure 1 This is a schematic diagram of the overall structure of the NFC-triggered responsibility transfer chain generation method and system for air travel baggage handover according to the present invention. Figure 2 This is a schematic diagram of the NFC-triggered responsibility transfer chain generation mechanism of the present invention.

[0029] Figure 3 This is a simulation diagram of the timing evolution of the responsibility transfer chain for a single piece of air travel baggage according to the present invention.

[0030] Figure 4 This is a simulation diagram of the responsibility link scoring and write gate determination of the present invention.

[0031] Figure 5 This is a simulation diagram of the injection and diversion of multiple types of abnormal events in this invention.

[0032] Figure 6 This is a simulation diagram of offline compensation synchronization under weak network / network outage conditions according to the present invention. Detailed Implementation

[0033] The specific embodiments of the present invention are described below to enable those skilled in the art to understand the present invention. However, it should be understood that the present invention is not limited to the scope of the specific embodiments. For those skilled in the art, various changes are obvious as long as they are within the spirit and scope of the present invention as defined and determined by the appended claims. All inventions utilizing the concept of the present invention are protected.

[0034] This invention does not simply use NFC tags as a tool for reading baggage numbers, but rather as an entry point for triggering the transfer of responsibility during baggage handover. When staff touch and read the NFC smart baggage tag at different handover points, the system automatically collects information such as the order, node, handover party, recipient, time, location, device, and baggage status corresponding to that handover, and organizes it into a responsibility transfer event unit. The system further reads the historical responsibility chain of the same baggage to determine whether the current responsibility transfer event can be continued to the previous valid responsibility record, and decides accordingly to write it into the formal responsibility chain, enter the exception queue, or temporarily store it as an offline pending compensation record.

[0035] like Figure 1 As shown, the system of the present invention mainly includes a front-end baggage identification device, a staff mobile terminal, a responsibility transfer event processing unit, a back-end responsibility chain management platform, and an offline compensation synchronization unit.

[0036] The front-end baggage identification device is an NFC smart baggage tag attached to passenger luggage. This tag contains a built-in NFC label with a unique identifier corresponding to each piece of luggage. This unique identifier is used to link business data such as passenger order, baggage number, flight information, destination information, and service type.

[0037] Staff mobile terminals are used to read NFC smart baggage tags during baggage handover. When performing handover operations at various points such as door-to-door pickup, transportation handover, city terminal or airport handover, and destination delivery, staff can bring their mobile terminals close to or touch the NFC smart baggage tags to read the unique identification code in the tag and collect information such as the current point, operator, time, location, and terminal device.

[0038] The responsibility transfer event processing unit is used to organize the information read by the mobile terminal into responsibility transfer event units. This unit queries the corresponding order and historical responsibility chain based on the NFC unique identification code, identifies the current handover node, handover party, recipient, operation time, operation location, terminal device number and baggage status, and determines whether the current handover event meets the responsibility chain continuation conditions.

[0039] The back-end responsibility chain management platform is used to uniformly manage formal responsibility chains, exception records, pending review records, and offline compensation records. After generating a handover record, the system links it with the previous valid responsibility record, thus forming a responsibility transfer chain for the entire process of baggage pickup and delivery to the destination.

[0040] The offline compensation synchronization unit is used to handle handover events generated in environments with no or weak network connectivity. When the mobile terminal cannot connect to the network in real time, the system temporarily stores the handover event and summary information locally; after the network is restored, the offline records are uploaded to the backend for comparison, deduplication, continuity verification, and compensation merging with the existing chain of responsibility.

[0041] This invention proposes an NFC-triggered responsibility transfer chain generation mechanism, such as... Figure 2 As shown, this mechanism uses the act of staff touching and reading the NFC smart luggage tag as the trigger point for responsibility transfer. It transforms each luggage handover action into a verifiable responsibility transfer event unit, and determines whether the current event can be connected to the previous valid responsibility record based on the historical responsibility chain of the same luggage.

[0042] Existing RFID or NFC baggage tracking methods typically focus on reading tags at specific locations and recording the baggage's location or status. In contrast, this invention does not treat NFC read results as isolated track points, but rather as triggering indices for responsibility transfer events. After reading the unique NFC identifier, the system simultaneously acquires order information, the current handover node, the handover party, the recipient, the operation time, the operation location, the terminal device number, the baggage status, and the previous responsibility record, and encapsulates this information into a responsibility transfer event unit.

[0043] First, NFC triggers event generation. After a staff member's mobile terminal touches and reads the NFC smart luggage tag, the system generates the current handover event using the unique NFC identification code as an index.

[0044] Second, responsibility transfer event encapsulation. The system encapsulates information such as order, node, sender, receiver, time, location, equipment, status, and previous responsibility record into responsibility transfer event units.

[0045] Third, standard contact point mapping. Based on the baggage business process, the system maps nodes such as door-to-door pickup, transportation handover, city terminal or airport handover, and destination delivery to a standard contact point system for baggage tracking, forming node sequence constraints.

[0046] Fourth, the chain of responsibility is written into the gating system. The system reads the historical chain of responsibility for the same piece of luggage and determines whether the current responsibility transfer event meets the requirements of order matching, node continuation, personnel permissions, spatiotemporal consistency, state consistency, and offline conflict verification.

[0047] Fifth, abnormal traffic diversion and offline compensation. For handover events that do not meet the write conditions, the system diverts them as abnormal records, pending review records, or offline temporary records; after the network is restored, the system performs compensation verification and link merging according to the backend responsibility chain.

[0048] Through the above mechanism, this invention unifies NFC identification, baggage handover, responsibility transfer, and anomaly handling into a single responsibility transfer chain, so that each baggage handover is no longer an isolated record, but a verified responsibility chain update operation.

[0049] For any piece of travel baggage, when a staff member touches the NFC smart baggage tag using a mobile terminal, the system generates a liability transfer event. The iiith liability transfer event is represented as: (1) in, This indicates the unique identification code of the NFC smart luggage tag; This indicates the currently matched passenger order information; Indicates the current handover node; Indicates the party currently handing over the goods; Indicates the current recipient; Indicates the current operation time; Indicates the current operation location; Indicates the current terminal device number; Indicates the current status of baggage service; This indicates the previous valid liability record.

[0050] For the same piece of luggage, the process of transferring historical responsibility can be represented as follows: (2) This sequence corresponds to the transfer of responsibility for baggage from door-to-door pickup, transportation handover, handover at the city terminal or airport, to delivery at the destination. This sequence is only used to describe the responsibility transfer relationship of a single piece of baggage and does not involve flight operation status prediction or spatiotemporal prediction of the entire airport support process.

[0051] like Figure 3As shown, during the continuous handover of a single piece of air travel baggage, responsibility transfer events are generated sequentially according to the business order of door-to-door pickup, transportation handover, city terminal or airport handover, and destination delivery. Responsibility transfer events that meet the write gating conditions generate corresponding formal handover records, which are then associated with the previous valid responsibility record and sequentially added to the formal responsibility chain, thus forming a continuous sequence of responsibility transfer records. For abnormal events that do not meet the continuation conditions, such as node jumps or time conflicts, the system blocks them from entering the formal responsibility chain through write gating and diverts them to the corresponding exception handling queue.

[0052] Traditional NFC luggage tags typically only provide tag numbers, making it difficult to directly reflect responsibility transfer information such as the giver, receiver, handover node, and previous responsibility record in the handover process. Therefore, this invention transforms an NFC touch action into a responsibility transfer event unit with responsibility semantics.

[0053] For the iiith responsibility transfer event, the system constructs an event feature vector: (3) in, This represents an event encapsulation function used to organize NFC unique identifiers, orders, nodes, givers, receivers, time, location, devices, status, and previous responsibility records into a unified responsibility transfer event unit.

[0054] In this way, the system no longer treats NFC tags as isolated numbers, but transforms each NFC touch into a structured input containing responsibility transfer semantics.

[0055] In the process of baggage handover during air travel, there is a clear sequence between different stages. A piece of baggage usually needs to be picked up from the door first, then enter the transportation handover process, then arrive at the city terminal or airport for handover, and finally be delivered to its destination.

[0056] The system's default sequence of handover nodes for door-to-door air travel baggage service is as follows: (4) in, Indicates the door-to-door pickup point; Indicates the transportation handover node; Indicates a junction point between a city terminal or airport; This indicates the destination delivery node.

[0057] To enhance compatibility with industry baggage tracking touchpoints, the system maps the above nodes to the standard baggage tracking touchpoint system: (5) in, This represents the standard contact points for baggage tracking, including receiving, loading, transfer, and arrival. Through this mapping, the system can determine whether the current handover node conforms to the standard sequence of baggage flow and provide node constraints for subsequent gating of the responsibility chain.

[0058] The current responsibility transfer event is not directly written into the formal responsibility chain after it is generated, but is first written into the gating judgment through the responsibility chain.

[0059] The system is based on the current responsibility transfer event. and existing chain of responsibility Calculate the write gating result: (6) in, Indicates whether the current liability transfer event is allowed to be included in the formal chain of responsibility; This represents the responsibility link continuation judgment function. The responsibility link continuation score is defined as: (7) in, Indicates order consistency score; Indicates node continuity score; This indicates a matching score between the sender and receiver; Indicates the scoring of time sequence; Indicates location continuation scoring; Indicates baggage status connection score; These are the weight parameters.

[0060] when: (8) At that time, the system determines that the current responsibility transfer event meets the write conditions: (9) when: (10) At that time, the system determines that the current responsibility transfer event does not meet the write conditions: (11) This gating mechanism is used to prevent node jumping, unauthorized handover, time and location conflicts, inconsistent order status, duplicate reads, or offline conflict events from being directly written into the formal responsibility chain.

[0061] like Figure 4As shown, the responsibility link continuity scoring and write gating judgment process can be compared and illustrated through different scenarios such as normal handover, node skipping, personnel mismatch, time anomalies, location deviation, state conflict, and offline conflict. The system calculates scoring items such as order consistency, node continuity, personnel matching, time continuity, location continuity, and state continuity to form a comprehensive continuity score, which is then compared with a preset threshold. When the comprehensive continuity score meets the threshold requirements and there are no additional constraints such as offline conflicts, the gating result is write allowed; otherwise, the gating result is write prohibited and the exception handling process is initiated. The scoring intensity, bar relationship, and threshold position in the figure are used to illustrate the gating judgment logic, without limiting specific weight parameters and threshold values.

[0062] when At that time, the system generates a formal handover record: (12) in, This indicates the function for generating handover records.

[0063] The system links the current record with the previous valid responsibility record and writes it into the formal chain of responsibility: (13) in, This indicates an additional operation in the chain of responsibility.

[0064] The handover record includes at least the NFC tag unique identifier, passenger order number, baggage number, current handover node, handover party, recipient, operation time, operation location, terminal device number, current handover status, previous responsibility record number, next expected node, and write status.

[0065] Through this chain of responsibility, the system can fully record the entire process of baggage transfer from handover by the passenger to delivery to the destination. In the event of subsequent baggage delays, misdelivery, missed handovers, or disputes over responsibility, the back-end platform can quickly locate the corresponding node, personnel, and operation time based on this chain of responsibility.

[0066] when In such cases, the system does not directly write the current event into the formal chain of responsibility, but instead triages it according to the exception type: (14) in, This indicates the corresponding exception handling queue.

[0067] The exception handling queue includes: The order exception queue is used to store events where NFC tags are not bound to orders or where the order status does not allow for handover. The node exception queue is used to store events such as node skipping, process reversal, or node missing. The personnel exception queue is used to store events where the permissions of the sender, receiver, or operator do not match. The spatiotemporal anomaly queue is used to store events such as abnormal time intervals, location deviations, or equipment location conflicts. The repeated read queue is used to store handover events that are repeatedly triggered within a short period of time; The offline conflict queue is used to store events that are inconsistent with the backend chain of responsibility after offline synchronization; The queue awaiting manual review is used to store boundary events that the system cannot automatically determine.

[0068] By handling abnormal events, the system can prevent abnormal events from contaminating the formal chain of responsibility, while retaining evidence of abnormalities for backend querying, tracing, and manual review.

[0069] like Figure 5 As shown, the system illustrates the anomaly identification and triage process through various scenarios, including unbound or disallowed orders, skipped nodes or reversed processes, mismatched permissions between the sender and receiver, abnormal time or location, repeated readings within a short period, conflicts between offline records and the backend responsibility chain, and boundary events that the system cannot automatically determine. Based on feature consistency verification, continuation scoring, and anomaly type identification results, the system triages anomaly events to queues for order anomalies, nodes, personnel, time and space, repeated readings, offline conflicts, or pending manual review. These anomalies are not directly written into the formal responsibility chain, but corresponding evidence is retained to support backend queries, responsibility tracing, and manual review.

[0070] In scenarios such as airports, underground parking lots, transport vehicles, and warehouse areas, staff mobile terminals may be in a state of no network or weak network. To avoid the handover record being interrupted due to network anomalies, this invention sets up an offline compensation synchronization mechanism.

[0071] When the terminal is offline and order information is cached locally, the system generates an offline responsibility transfer event: (15) When the terminal is offline and order information is not cached locally, the system must at least save the NFC tag's unique identifier, handover node, handover party, recipient, operation time, operation location, terminal device number, and offline record summary. (16) in, This is an offline record summary used to verify whether local records have been tampered with.

[0072] Offline records are temporarily stored on staff mobile devices. Once the network is restored, the devices will upload the offline responsibility transfer events to the backend responsibility chain management platform. The backend platform will then perform synchronization verification based on order status, timestamp, node order, device number, hash digest, and historical responsibility chains.

[0073] If the offline records match the backend responsibility chain, then perform compensation write: (17) If an offline record conflicts with the backend chain of responsibility, it will be written to the offline conflict queue. (18) This mechanism enables staff to complete NFC tag reading and handover event storage even in the absence of a network. After the network is restored, the system will not write directly and blindly, but will perform compensation verification and link merging based on the backend responsibility chain, thereby avoiding the breakage of the responsibility chain or duplicate writing.

[0074] like Figure 6 As shown, responsibility transfer events generated during network availability are written into the formal responsibility chain according to the normal online process. When the mobile terminal enters a weak network or out-of-network state, responsibility transfer events generated during the offline period are not written into the background formal responsibility chain, but are temporarily stored locally and a corresponding hash digest is generated. After the network is restored, the terminal uploads the offline responsibility transfer events and their digest information. The background platform performs a consistency check by combining the order status, timestamp, node order, terminal number, hash digest, and historical responsibility chain. If the check is consistent, the offline event compensation is written into the formal responsibility chain; if there is a conflict, the corresponding event is transferred to the offline conflict queue for processing, thereby ensuring the continuity of the responsibility chain and avoiding duplicate or conflicting writes.

[0075] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0076] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0077] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0078] Specific embodiments have been used to illustrate the principles and implementation methods of this invention. The descriptions of the embodiments above are only for the purpose of helping to understand the method and core ideas of this invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this invention. Therefore, the content of this specification should not be construed as a limitation of this invention.

[0079] Those skilled in the art will recognize that the embodiments described herein are intended to help the reader understand the principles of the invention, and should be understood that the scope of protection of the invention is not limited to such specific statements and embodiments. Those skilled in the art can make various other specific modifications and combinations based on the technical teachings disclosed in this invention without departing from the spirit of the invention, and these modifications and combinations are still within the scope of protection of this invention.

Claims

1. A method for generating an NFC-triggered responsibility transfer chain for air travel baggage handover, characterized in that, Includes the following steps: S1. Construct a baggage handover responsibility transfer system architecture, which includes a front-end baggage identification device, a staff mobile terminal, a responsibility transfer event processing unit, a back-end responsibility chain management platform, and an offline compensation synchronization unit. The front-end baggage identification device is a smart baggage tag with a built-in NFC tag. The NFC tag contains a unique identification code corresponding to the baggage. The unique identification code is used to associate passenger order, baggage number, flight information, destination information, and service type business data. S2. Staff members use their mobile terminals to touch and read the NFC smart luggage tag set on the luggage at the luggage handover point, generating an NFC trigger event. S3. Collect the associated information of the current handover based on the NFC trigger event, and encapsulate it to form a responsibility transfer event unit; S4. Map the current handover node to the preset baggage tracking standard contact point system and establish node sequence constraints; S5. Perform continuity verification on the responsibility transfer event unit based on the historical responsibility chain, and execute the responsibility chain write gating judgment; S6. Based on the gating judgment result, write the responsibility transfer event unit into the formal responsibility chain, divert it to the exception handling queue, or temporarily store it as an offline record to be compensated.

2. The NFC-triggered responsibility transfer chain generation method for air baggage handover according to claim 1, characterized in that, S2 specifically includes: S21. When staff perform handover operations at door-to-door pickup, transportation handover, city terminal or airport handover, and destination delivery nodes, they can approach or touch the NFC smart baggage tag using a mobile terminal. S22. The mobile terminal reads the unique identification code in the NFC tag and simultaneously collects the current operation time, operation location and terminal device number information.

3. The NFC-triggered responsibility transfer chain generation method for air travel baggage handover according to claim 1, characterized in that, The responsibility transfer event unit encapsulated in S3 is represented as follows: in, This indicates the unique identification code of the NFC smart luggage tag; This indicates the currently matched passenger order information; Indicates the current handover node; Indicates the party currently handing over the goods; Indicates the current recipient; Indicates the current operation time; Indicates the current operation location; Indicates the current terminal device number; Indicates the current status of baggage service; This indicates the previous valid liability record.

4. The NFC-triggered responsibility transfer chain generation method for air travel baggage handover according to claim 1, characterized in that, S4 specifically includes: S41. Preset handover node sequence in door-to-door air baggage service ,in, Indicates the door-to-door pickup point; Indicates the transportation handover node; Indicates a junction point between a city terminal or airport; Indicates the destination delivery node; S42. Establish node mapping relationships Each handover node Mapped to standard baggage tracking touchpoints The standard contacts include receiving, loading, transferring, and arriving contacts.

5. The NFC-triggered responsibility transfer chain generation method for air travel baggage handover according to claim 1, characterized in that, S5 specifically includes: S51, Calculate the responsibility link continuation score The calculation formula is: in, Indicates order consistency score; Indicates node continuity score; This indicates a matching score between the sender and receiver; Indicates the scoring of time sequence; Indicates location continuation scoring; Indicates baggage status connection score; These are weight parameters; S52, Set the scoring threshold ,when When the current responsibility transfer event meets the write condition, the gating result is "write allowed"; when If the current responsibility transfer event does not meet the write conditions, the gating result is to prohibit writing.

6. The NFC-triggered responsibility transfer chain generation method for air travel baggage handover according to claim 1, characterized in that, S6 specifically includes the following steps: S61. When the gating result indicates write permission is granted, a formal handover record is generated. ,in This represents the function for generating handover records. As a responsibility transfer event unit; S62. Link the current record with the previous valid responsibility record through an append operation. Update the chain of responsibility: The For the chain of historical responsibility; S63. When the gating result is write prohibited, the responsibility transfer event unit is diverted to the corresponding queue according to the exception type. The queue includes the order exception queue, node exception queue, personnel exception queue, spatiotemporal exception queue, duplicate read queue, offline conflict queue and queue awaiting manual review. S64. When the mobile terminal is in a state of no network or weak network, the responsibility transfer event unit and the corresponding hash digest will be transferred. Stored locally to create offline records. Offline recording Represented as: In the formula, This indicates the unique identification code of the NFC smart luggage tag; This indicates the currently matched passenger order information; Indicates the current handover node; Indicates the party currently handing over the goods; Indicates the current recipient; Indicates the current operation time; Indicates the current operation location; Indicates the current terminal device number; Indicates the current status of baggage service; S65. Once the network is restored, the mobile terminal will record offline. Upload to the backend chain of responsibility management platform; S66. The backend platform performs synchronous verification on offline records. If they are consistent with the historical chain of responsibility, compensation is written; if there is a conflict, the offline records are written to the offline conflict queue.

7. An NFC-triggered responsibility transfer chain generation system for air travel baggage handover, characterized in that, include: The front-end baggage identification module is configured to set an NFC smart baggage tag on the passenger's baggage, wherein the NFC smart baggage tag has a built-in NFC tag that stores a unique identification code; The mobile terminal module is configured to allow staff to touch and read the NFC smart luggage tag at the luggage handover point, generating an NFC trigger event; The event processing module is configured to collect associated information based on the NFC-triggered event and encapsulate it into a responsibility transfer event unit, map the current handover node to the standard contact system, and perform write gating judgment based on the historical responsibility chain; The responsibility chain management module is configured to write responsibility transfer event units into the formal responsibility chain or divert them to the exception handling queue based on the gating judgment result. The offline synchronization module is configured to temporarily store the responsibility transfer event unit as an offline record when the network is abnormal, and perform compensation verification and link merging after the network is restored.

8. The NFC-triggered responsibility transfer chain generation system for air travel baggage handover according to claim 7, characterized in that, The event handling module includes: The event encapsulation unit is configured to construct an event feature vector containing the NFC unique identifier, order information, handover node, handover party, recipient, operation time, operation location, terminal device number, luggage status, and previous responsibility record; The touchpoint mapping unit is configured to map door-to-door pickup, transportation handover, city terminal or airport handover, and destination delivery nodes to the standard baggage tracking touchpoint system. The gating judgment unit is configured to calculate the responsibility link continuity score and compare the score result with a preset threshold to output the gating result.

9. The NFC-triggered responsibility transfer chain generation system for air baggage handover according to claim 8, characterized in that, The offline synchronization module includes: Offline storage unit, configured to store offline responsibility transfer events and their corresponding hash digests locally; The conflict verification unit is configured to compare the consistency between offline records and the historical responsibility chain in the background after the network is restored. The compensation write unit is configured to append offline records to the formal chain of responsibility after the consistency check passes.