Flight passenger transfer system and method, readable storage medium and program product
The flight passenger rebooking system automates rebooking processes through an integrated module structure, addressing inefficiencies in current systems by enabling efficient and flexible rebooking operations across airlines and destination changes, leveraging cloud technology for enhanced adaptability and scalability.
Patent Information
- Application Number
- CN202411918630.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-24
- Publication Date
- 2025-03-28
AI Technical Summary
Current passenger rebooking systems for flights are inefficient due to manual operations and lack of automated support for cross-airline or destination changes, especially in scenarios like flight delays or cancellations.
A flight passenger rebooking system comprising an off-departure front-end module, a rebooking processing module, and a seat processing module, which receives user instructions, filters and executes valid rebooking commands, and allocates seats based on predefined rules, utilizing a TCC transaction model for efficient seat management.
The system enhances processing efficiency by automating rebooking processes, supporting various scenarios, and allowing flexible configuration based on user demands, with strong expandability and adaptability using cloud platform technology.
Smart Images

Figure CN119721303A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the technical field of itinerary information management, and in particular to a flight passenger transfer system, method, readable storage medium and program product. Background Art
[0002] When passengers travel by flight, they need to change from one flight to another due to flight delays or their own reasons; or during the daily operation of the flight, sometimes the flight is cancelled due to weather reasons, aircraft deployment or aircraft mechanical failure, and the passengers on the original flight need to be transferred to another flight. These scenarios are all passenger transfers in the departure system. At present, passenger transfers mostly require manual operations, with low processing efficiency, and there is a lack of a transfer system that supports cross-airline or change of destination. Summary of the invention
[0003] The present disclosure aims to solve at least one of the technical problems in the above-mentioned technologies to a certain extent, and proposes a flight passenger transfer system, including:
[0004] Departure front-end module, endorsement processing module and seat processing module; among them,
[0005] The departure front-end module is used to receive the transfer instruction sent by the user;
[0006] The sign-on processing module is used to filter the sign-on instructions that meet the sign-on conditions, and execute the sign-on instructions that meet the sign-on conditions to generate seat allocation instructions;
[0007] The seat processing module is used to allocate seats to passengers corresponding to the check-in instructions.
[0008] Furthermore, the flight passenger transfer system further includes: a rule configuration module; the rule configuration module is used to:
[0009] Storing the configuration rules corresponding to the sign-on instructions;
[0010] Receiving, through the departure front-end module, a configuration rule update instruction sent by a user;
[0011] The configuration rule is updated according to the rule update instruction.
[0012] Furthermore, the transfer instruction includes:
[0013] Destination unchanged transfer instructions and destination changed transfer instructions;
[0014] The configuration rules corresponding to the destination unchanged transfer instruction and the destination changed transfer instruction include: the destination airline to which the original airline can transfer, the target flight number to which the original flight number can transfer, and the destination cabin to which the original cabin can transfer;
[0015] The configuration rules corresponding to the destination change transfer instruction also include: the destination to which the original destination can be transferred.
[0016] Furthermore, the sign-off processing module verifies whether the sign-off instruction satisfies the sign-off condition, and the corresponding method includes:
[0017] Verify the status of the original flight and the status of the target flight, including: verifying whether the flight information matches and verifying whether the flight is operable; if the verification passes, query the passenger information corresponding to the transfer instruction and verify the passenger information;
[0018] If the passenger information verification passes, then based on the configuration rules stored in the rule configuration module, it is verified whether the endorsement instruction meets the endorsement conditions.
[0019] Furthermore, the endorsement processing module is used to verify the legality of the request parameters corresponding to the endorsement instruction before verifying the original flight status and the target flight status.
[0020] Furthermore, the signing-forwarding processing module executes the signing-forwarding instruction, and the corresponding method includes:
[0021] Determine the flight status of the target flight; the flight status includes: unchecked-in to standby status, unchecked-in to unchecked-in status, checked-in to checked-in status, checked-in to standby status, standby to standby status, and standby to checked-in status;
[0022] The corresponding transfer operation is determined and executed according to the flight status.
[0023] Furthermore, the seat processing module is used to allocate seats to passengers based on the TCC transaction model.
[0024] The present disclosure also proposes a flight passenger transfer method based on the above-mentioned flight passenger transfer system, the method comprising:
[0025] The signing-forwarding processing module is used to execute the following method:
[0026] Receiving a transfer instruction sent by a user through the departure front-end module;
[0027] Check whether the sign-on instruction satisfies the sign-on condition. If yes, execute the sign-on instruction and generate a seat allocation instruction and send it to the seat processing module, so that the seat processing module allocates a seat to the passenger corresponding to the sign-on instruction.
[0028] The present disclosure also proposes a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is executed by a processor, it is at least used to implement the above-mentioned flight passenger transfer method.
[0029] The present disclosure also proposes a computer program product, which is stored in a computer-readable storage medium. When the computer program product is executed by a processor, it is at least used to implement the above-mentioned flight passenger transfer method.
[0030] Compared with the prior art, the beneficial effects of the present disclosure are: the flight passenger transfer system provided by the present disclosure can be implemented based on cloud platform technology, the system is rich in functions and is suitable for a variety of transfer business scenarios, and because the system adopts a rule-configuration driven solution, the system has strong scalability and can be flexibly configured according to user needs.
[0031] Other features and advantages of the present disclosure will be described in the subsequent description, and partly become apparent from the description, or be understood by practicing the present disclosure. The purpose and other advantages of the present disclosure can be realized and obtained by the structures particularly pointed out in the written description and the drawings. The technical solution of the present disclosure is further described below through drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS
[0032] The accompanying drawings are used to provide a further understanding of the present disclosure and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the present disclosure and do not constitute a limitation of the present disclosure. In the accompanying drawings:
[0033] Figure 1 A schematic diagram of a flight passenger transfer system provided in an embodiment;
[0034] Figure 2 The following is a flowchart of the flight passenger transfer system provided in the embodiment;
[0035] Figure 3 The following is a workflow diagram of the signing-forwarding processing module provided in the embodiment;
[0036] Figure 4 The following is a flow chart of the transfer of passengers who have not checked in given in the embodiment;
[0037] Figure 5 The following is a flow chart of check-in passenger transfer given in an embodiment;
[0038] Figure 6 A flow chart of waiting passengers provided for an embodiment;
[0039] Figure 7 The following is a flow chart of the TCC transaction mode provided in the embodiment;
[0040] Figure 8 A schematic diagram of an electronic device provided for an embodiment;
[0041] Fig. 9 A schematic diagram of a computer-readable storage medium is provided for an embodiment. DETAILED DESCRIPTION
[0042] The present disclosure is described below in conjunction with the accompanying drawings. The preferred embodiments described herein are only used to illustrate and explain the present disclosure and are not used to limit the present disclosure.
[0043] The present disclosure provides a flight passenger transfer system, including:
[0044] Departure front-end module, endorsement processing module and seat processing module; among them,
[0045] The departure front-end module is used to receive the transfer instruction sent by the user;
[0046] The sign-on processing module is used to filter the sign-on instructions that meet the sign-on conditions, and execute the sign-on instructions that meet the sign-on conditions to generate seat allocation instructions;
[0047] The seat processing module is used to allocate seats to passengers corresponding to the transfer instructions. Furthermore, the flight passenger transfer system also includes: a rule configuration module; the rule configuration module is used to:
[0048] Storing the configuration rules corresponding to the sign-on instructions;
[0049] Receive configuration rule update instructions sent by the user through the departure front-end module;
[0050] Update the configuration rules according to the rule update instruction.
[0051] According to some embodiments of the present disclosure, when passengers travel by flight, if they want to change from one flight to another due to flight delays or their own reasons, they can apply for endorsement transfer at the airport check-in counter. The system provides an operation page for specifying passengers to make endorsement transfers. If the airline has opened an agreement, it can support cross-airline endorsement transfers. On some express city routes, it can also support endorsement transfers for destination changes. Figure 1 As shown, the flight passenger transfer system proposed in the present disclosure includes at least the following modules:
[0052] Departure front-end module: select the designated passenger transfer operation page according to the business scenario, and handle the transfer for the passenger based on the specific information.
[0053] Rule configuration module: responsible for setting passenger transfer rules, including whether cross-airline transfer is possible, destinations that can be transferred to each other, and cabin configurations that can be transferred.
[0054] Endorsement processing module: responsible for parsing front-end requests, querying flight and passenger information of flights before and after the endorsement, judging whether the rule settings are met according to the flight and passenger information query rules, judging whether the various limits of flights before and after the endorsement are sufficient, whether the passengers meet the endorsement conditions, etc. After the verification is passed, the flight and passenger information involved will be updated.
[0055] Seat processing module: responsible for updating the seat information of flights before and after the transfer, releasing passenger seats on the original flight, and allocating seats to passengers on the new flight.
[0056] Furthermore, the signing instruction includes:
[0057] Destination unchanged transfer instructions and destination changed transfer instructions;
[0058] The corresponding configuration rules for the unchanged destination transfer instructions and the changed destination transfer instructions include: the original airline can transfer to the destination airline, the original flight number can transfer to the target flight number, and the original cabin can transfer to the destination cabin;
[0059] The configuration rules corresponding to the destination change transfer instruction also include: the destination to which the original destination can be transferred.
[0060] According to some embodiments of the present disclosure, various scenarios of flight passenger transfer can be configured with rules through the transfer processing module. Transfer is divided into two scenarios: destination unchanged and destination changed. The rule configuration content when the flight segment destination remains unchanged includes: the destination airline to which the original airline can transfer, the target flight number to which the original flight number can transfer, and the destination cabin to which the original cabin can transfer. In addition, the rule configuration when the destination changes also adds the destination to which the original destination can transfer. The present disclosure designs rules that are open to airlines for configuration, and the content of the rules in the following table will be expanded according to business needs, as shown in Table 1.
[0061] Table 1
[0062]
[0063]
[0064]
[0065] Furthermore, the sign-off processing module verifies whether the sign-off instruction satisfies the sign-off condition. The corresponding method includes:
[0066] Verify the status of the original flight and the target flight, including: verifying whether the flight information matches and whether the flight is operable; if the verification passes, query the passenger information corresponding to the transfer instruction and verify the passenger information;
[0067] If the passenger information verification passes, then based on the configuration rules stored in the rule configuration module, it is verified whether the endorsement instruction meets the endorsement conditions.
[0068] Furthermore, the endorsement processing module is used to verify the legality of the request parameters corresponding to the endorsement instruction before verifying the original flight status and the target flight status.
[0069] Furthermore, the signing-forwarding processing module executes the signing-forwarding instruction, and the corresponding method includes:
[0070] Determine the flight status of the target flight; flight status includes: not checked-in to standby status, not checked-in to not checked-in status, checked-in to checked-in status, checked-in to standby status, standby to standby status, and standby to checked-in status;
[0071] Determine and execute the corresponding transfer operation based on the flight status.
[0072] According to some embodiments of the present disclosure, when a passenger is signing for a transfer, the transfer processing module determines whether the transfer rules are met. If no rules are found, an error is reported. If the transfer rules are met, the transfer processing stage is entered. The entire process is as follows: Figure 2 As shown:
[0073] Based on the configuration rules stored in the rule module (rule configuration module), the user processes the endorsement for the designated passenger through the front end (departure front end module) and sends it to the endorsement module (endorsement processing module) for processing. It should be noted here that the user can configure the configuration rules stored in the rule module through the front end.
[0074] The transfer module determines whether the transfer meets the transfer conditions according to the configuration rules stored in the rule module. If yes, it will process the transfer for the passenger and send it to the seat module (seat processing module) to allocate seats for the corresponding passengers. If the allocation is successful, it will notify the transfer module to update the passenger information and send a transfer success message to the front end. If the transfer conditions are not met or the seat allocation fails, a transfer failure message will be sent to the front end.
[0075] According to other embodiments of the present disclosure, the signing-forwarding process is as follows: Figure 3 As shown:
[0076] 1. Verify the legitimacy of request parameters: Verify the legitimacy of parameters such as airline, flight number, flight segment, and passenger ID.
[0077] 2. Flight verification
[0078] (1) Query the original flight based on the airline, flight number, flight suffix, departure date, and departure station in the request. If the original flight does not exist, an error message will be displayed and the user is requested to check the flight number.
[0079] (2) Query the target flight according to the airline, flight number, flight suffix, departure date, and departure station under the recheckOrOutboundFlightInfo node (flight information data). If the target flight does not exist, an error message is displayed and the user is asked to check the target flight number.
[0080] (3) Verify whether the original flight and the target flight are the same, or whether they belong to the same carrier flight. If so, an error message will be displayed and the user is asked to check the target flight number.
[0081] (4) Check whether the target flight destination in the request matches the original flight found in "(1)". If not, report an error that the destination does not match.
[0082] (5) Verify whether the original flight status allows the operation. The verification items are shown in the following table.
[0083] Table 2
[0084]
[0085] (6) Check whether the destination of the target flight under the recheckOrOutboundFlightInfo node (flight information data) matches the target flight found in "(2)". If not, report an error indicating that the destination of the target flight does not match.
[0086] (7) Check whether the target flight status allows the operation.
[0087] (8) Check whether the cabin class category of the passenger under the recheckOrOutboundFlightInfo node (flight information data) exists in the cabin class of the target flight. If not, an error is reported and the user is asked to recheck the cabin class of the target flight.
[0088] (9) Check whether the target flight has restricted check-in and has not enabled standby. If so, an error message will be displayed and the user is asked to check the flight status of the target flight.
[0089] 3. Check passengers
[0090] Query passenger information, including connecting flight information, based on the airline, flight number, flight suffix, departure date, departure station, and hostNumber in the request.
[0091] 4. Passenger verification
[0092] (1) Check whether the passengers in the request exist. If at least one passenger does not exist, an error PSGR ID (passenger ID) is reported.
[0093] (2) Check whether the passenger cabin class matches. When multiple people are operating, use the cabinId input from the outer layer of the interface. The passenger's sub-cabin or main cabin can match. When a single person is operating, use the cabin classId input from the passenger. The sub-cabin or main cabin can match. If they do not match, an error is reported: cabin class does not match.
[0094] (3) Check whether the passenger's destination matches. If not, report an error that the destination does not match.
[0095] (4) Check whether the passenger status is consistent, either all checked in, all not checked in, or all on standby. If the status is inconsistent, report a status conflict error.
[0096] (5) Verify other passenger attributes as shown in the following table.
[0097] Table 3
[0098]
[0099] (6) If the transfer destination is changed, check whether the passenger has Segment O (the latter part of the connecting flight). If yes, report an error indicating that the transfer airport is inconsistent.
[0100] 5. Rule verification: Determine whether the transfer rules are met, see above for details.
[0101] 6. Transfer logic
[0102] Passengers in different check-in statuses will be processed differently based on the check-in restrictions and quotas of the target flight. There are several scenarios: Not checked-in to standby status; Not checked-in to Not checked-in status; Checked-in to checked-in status; Checked-in to standby status; Standby status to standby status; Standby status to checked-in status. Figure 4 As shown, it includes: judging whether the target flight is in a restricted check-in state, if not, judging whether the target flight has a passenger limit, if the target flight has no passenger limit, directly entering the NACC-SB endorsement process (see above), assigning a seat to the passenger, and then ending the process; if the target flight has a passenger limit, entering the NACC-ACC endorsement process. If the target flight is in a restricted check-in state, judging whether the target flight is in a restricted check-in standby state (HOLD: S), if yes, entering the NACC-SB endorsement process, if not (that is, the target flight is in the HOLD: R state), then reporting an error.
[0103] Checked-in passenger (ACC) transfer process Figure 5 As shown in the figure, the process of signing for a standby passenger (SB) is as follows Figure 6 As shown, the processes for these two are the same as the check-in process for passengers who have not checked in. The difference lies in the different processes entered after the judgment, so I will not go into details.
[0104] In summary, the transfer logic scheme provided by the present disclosure includes: adjusting different interfaces of the seat processing module for different transfer scenarios, processing the seats of passengers on the original flight, and allocating seats for passengers on the new flight; performing a quota pull-down operation on passengers on the original flight, adding and deleting record XRES marks for passengers on the original flight, and recording passenger operation logs; adding passengers to the target flight, receiving them as "checked in" or on-call status, setting URES marks for passengers without reservations, recording passenger operation logs, and recording the relationship with the original transfer flight; if the passenger is received as checked in, setting the check-in channel, and generating a boarding pass data stream for the passenger on the target flight; automatically adding luggage for the passenger according to the original luggage information, and generating a luggage tag data stream for the passenger on the target flight.
[0105] Furthermore, the seat processing module is used to: allocate seats to passengers based on the TCC transaction model.
[0106] According to some embodiments of the present disclosure, different signing scenarios involve different interface interactions with the seat processing module, as shown in Table 4 below:
[0107] Table 4
[0108]
[0109] The interaction between the transfer processing module and the seat processing module adopts a high-performance TCC transaction mode. Figure 7 As shown: DC (sign-in processing module) sends a seat allocation lock request to DST (seat processing module). After receiving it, DST locks the seat allocation and feeds back to DC. DC updates the passenger status and data. DC sends a seat confirmation submission request to DST. DST confirms the submission and releases the seat allocation lock. In addition, DST will regularly check the locked but unreleased seats and release them if the lock times out.
[0110] The present disclosure also proposes a flight passenger transfer method based on the above-mentioned flight passenger transfer system, the method comprising:
[0111] Using the sign-on processing module, execute the following method:
[0112] Receive the endorsement instruction sent by the user through the departure front-end module;
[0113] Check whether the sign-on instruction meets the sign-on conditions. If yes, execute the sign-on instruction and generate a seat allocation instruction and send it to the seat processing module, so that the seat processing module allocates seats to the passengers corresponding to the sign-on instruction.
[0114] like Figure 8As shown, the present disclosure provides an electronic device, which includes a memory and a processor. The memory stores a computer program or instruction. When the computer program or instruction is executed by the processor, it is at least used to implement the above-mentioned flight passenger transfer method.
[0115] like Fig. 9 As shown, the present disclosure provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is executed by a processor, it is at least used to implement the above-mentioned flight passenger transfer method.
[0116] The present disclosure also provides a computer program product, which is stored in a computer-readable storage medium. When the computer program product is executed by a processor, it is at least used to implement the above-mentioned flight passenger transfer method.
[0117] It is obvious that a person skilled in the art can make various changes and modifications to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and their equivalents, the present disclosure is also intended to include these modifications and variations.
Claims
1. A flight passenger transfer system, characterized in that: include: Departure front-end module, endorsement processing module and seat processing module; among them, The departure front-end module is used to receive the transfer instruction sent by the user; The sign-on processing module is used to filter the sign-on instructions that meet the sign-on conditions, and execute the sign-on instructions that meet the sign-on conditions to generate seat allocation instructions; The seat processing module is used to allocate seats to passengers corresponding to the check-in instructions.
2. The system according to claim 1, characterized in that Also includes: A rule configuration module; the rule configuration module is used to: Storing the configuration rules corresponding to the sign-on instructions; Receiving, through the departure front-end module, a configuration rule update instruction sent by a user; The configuration rule is updated according to the rule update instruction.
3. The system according to claim 2, characterized in that The transfer instruction includes: Destination unchanged transfer instructions and destination changed transfer instructions; The configuration rules corresponding to the destination unchanged transfer instruction and the destination changed transfer instruction include: the destination airline to which the original airline can transfer, the target flight number to which the original flight number can transfer, and the destination cabin to which the original cabin can transfer; The configuration rules corresponding to the destination change transfer instruction also include: the destination to which the original destination can be transferred.
4. The system according to claim 3, characterized in that The sign-on processing module verifies whether the sign-on instruction satisfies the sign-on condition, and the corresponding method includes: Verify the status of the original flight and the status of the target flight, including: verifying whether the flight information matches and verifying whether the flight is operable; if the verification passes, query the passenger information corresponding to the transfer instruction and verify the passenger information; If the passenger information verification passes, then based on the configuration rules stored in the rule configuration module, it is verified whether the endorsement instruction meets the endorsement conditions.
5. The system according to claim 4, characterized in that The endorsement processing module is used to verify the legality of the request parameters corresponding to the endorsement instruction before verifying the original flight status and the target flight status.
6. The system according to claim 4, characterized in that The signing-off processing module executes the signing-off instruction, and the corresponding method includes: Determine the flight status of the target flight; the flight status includes: unchecked-in to standby status, unchecked-in to unchecked-in status, checked-in to checked-in status, checked-in to standby status, standby to standby status, and standby to checked-in status; The corresponding transfer operation is determined and executed according to the flight status.
7. The system according to claim 1, characterized in that The seat processing module is used to allocate seats to passengers based on the TCC transaction model.
8. A flight passenger transfer method based on the flight passenger transfer system according to any one of claims 1 to 7, characterized in that: include: The signing-forwarding processing module is used to execute the following method: Receiving a transfer instruction sent by a user through the departure front-end module; Check whether the sign-on instruction satisfies the sign-on condition. If yes, execute the sign-on instruction and generate a seat allocation instruction and send it to the seat processing module, so that the seat processing module allocates a seat to the passenger corresponding to the sign-on instruction.
9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program or instruction, and when the computer program or instruction is executed by the processor, it is at least used to implement the method of claim 8.
10. A computer program product, the computer program product being stored in a computer-readable storage medium, characterized in that: When the computer program product is executed by a processor, it is used to at least implement the method of claim 8.