Method and device for changing prepayment luggage, electronic equipment and storage medium

Abstract

The invention discloses a method and a device for changing prepaid luggage, electronic equipment and a storage medium, and relates to the technical field of aviation information or other related technical fields, and the method comprises the following steps: obtaining luggage information of to-be-processed luggage and corresponding user flight information from a following failure processing queue, verifying the to-be-processed luggage based on the luggage information and the user flight information, and determining whether the to-be-processed luggage meets a change requirement; under the condition that the to-be-processed luggage meets the change requirement, calling a ticket checking interface based on the flight information of the user, and querying the luggage freight rate information of the changed flight; and matching the luggage information with the luggage freight rate information, and automatically changing the to-be-processed luggage according to a matching result. According to the method and the device, the technical problem that in the prior art, under the condition that the prepaid luggage is failed to follow, the withdraw process of the prepaid luggage can be automatically triggered, and then the passenger manually rebooks the prepaid luggage of the changed flight, so that the automation degree of luggage change is low is solved.

Description

Technical Field

[0001] This invention relates to the field of aviation information technology or other related technical fields. Specifically, it relates to a method, apparatus, electronic device, and storage medium for changing prepaid baggage. Background Technology

[0002] With the digital transformation of the aviation industry, airlines are constantly introducing new service models to enhance customer experience and operational efficiency. Among these, prepaid baggage service, as an innovative business model, allows passengers to pay for additional baggage online in advance, either at the time of or after purchasing their tickets, thus enjoying a more convenient and personalized travel experience. This service not only simplifies the baggage check-in process at airports but also generates additional revenue for airlines.

[0003] However, prepaid baggage services face challenges in practice, especially when passengers need to change flights. Flight changes typically fall into two categories: one is directly modifying flight information on the existing PNR (Passenger Name Record) and re-issuing a ticket; the other is canceling the existing PNR, creating a new PNR, and issuing a ticket. In the second case, because prepaid baggage services are closely tied to the original flight, the ability to keep up with prepaid baggage services becomes problematic when a ticket is reissued (i.e., the ET ticket number changes after a ticket change, generating a new ET ticket number).

[0004] In existing technologies, the current processing mechanism automatically triggers a refund process for prepaid baggage upon detecting a failure to automatically follow prepaid baggage, requiring passengers to manually rebook the prepaid baggage for the changed flight. While this measure ensures passengers' rights are not compromised, it lacks automation and can also have negative effects. For example, passengers need to rebook the prepaid baggage service after receiving a refund, increasing the risk of double payment and reducing user experience. Furthermore, if passengers do not rebook after receiving a refund, this automatic refund strategy may cause airlines to lose revenue that could otherwise be retained.

[0005] There is currently no effective solution to the above problems. Summary of the Invention

[0006] This invention provides a method, apparatus, electronic device, and storage medium for changing prepaid baggage, to at least solve the technical problem in related technologies where, in the event of a failure to follow prepaid baggage, a refund process for prepaid baggage is automatically triggered, and then passengers manually rebook the prepaid baggage for the changed flight, resulting in a low degree of automation in baggage changing.

[0007] According to one aspect of the present invention, a method for changing prepaid baggage is provided, comprising: obtaining a target change task to be processed from a prepaid baggage follow-failure processing queue, wherein the follow-failure processing queue stores all change tasks corresponding to prepaid baggage that have failed to follow the passenger service system; obtaining baggage information of the baggage to be processed and user flight information corresponding to the baggage to be processed based on the target change task, and verifying the baggage to be processed based on the baggage information and the user flight information to determine whether the baggage to be processed meets the change requirements; if the baggage to be processed meets the change requirements, calling a ticket search interface based on the user flight information to query baggage fare information of the changed flight; matching the baggage information with the baggage fare information, and if the baggage information matches any baggage fare package in the baggage fare information successfully, automatically changing the baggage to be processed to the changed flight.

[0008] Further, the step of verifying the baggage to be processed based on the baggage information and the user flight information to determine whether the baggage to be processed meets the change requirements includes: obtaining fare ticket information from the baggage information and user ticket information from the user flight information; verifying whether the fare ticket information and the user ticket information are consistent, and determining whether the status of the baggage to be processed is valid, obtaining consistency verification results and status verification results; determining the changed flight based on the user flight information, obtaining the scope of prepaid baggage applicable to the changed flight, and comparing the baggage information with the scope of prepaid baggage applicable to determine whether the baggage to be processed is within the applicable scope, obtaining scope verification results; obtaining the baggage following rules of the changed flight, verifying whether the changed flight allows the baggage to be processed to follow the change for free, obtaining rule verification results; and determining whether the baggage to be processed meets the change requirements based on the consistency verification results, the status verification results, the scope verification results, and the rule verification results.

[0009] Furthermore, before retrieving the target change task to be processed from the prepaid baggage follow-up failure processing queue, the method further includes: monitoring user flight change information; determining whether the user has purchased prepaid baggage if the user has a flight change; retrieving the prepaid baggage follow-up information of the user if the user has purchased prepaid baggage; and creating a change task for the user's prepaid baggage and adding the change task to the follow-up failure processing queue if the passenger service system returns a follow-up failure.

[0010] Furthermore, the step of matching the baggage information with the baggage fare information includes: traversing the baggage fare packages in the baggage fare information, extracting the baggage price, baggage size, and baggage weight from the baggage fare packages; and matching the baggage price, baggage size, and baggage weight in the baggage information with the baggage price, baggage size, and baggage weight in the baggage fare packages.

[0011] Furthermore, if the baggage information successfully matches any baggage fare package in the baggage fare information, the step of automatically changing the pending baggage to the changed flight includes: if the baggage information successfully matches any baggage fare package in the baggage fare information, calling the ticketing interface of the changed flight, and purchasing the successfully matched baggage fare package from the ticketing system through the ticketing interface; if the baggage fare package is successfully purchased, generating change information and updating the status of the pending baggage to a change-successful status; and returning the change information and the change-successful status of the pending baggage to the user.

[0012] Furthermore, after matching the baggage information with the baggage fare information, the method further includes: if the baggage information fails to match any baggage fare packages in the baggage fare information, sending a notification of baggage following failure and the baggage fare information of the changed flight to the user terminal; receiving manual change information from the user terminal and calculating the change fee for the baggage to be processed based on the manual change information; generating a change request based on the manual change information and the change fee, and calling the ticketing interface based on the change request to purchase the baggage fare package selected by the user terminal from the ticketing system through the ticketing interface; if the purchase is successful, generating change information for the baggage to be processed and updating the status of the baggage to be processed to a change successful status; and returning the change information and the change successful status of the baggage to the user terminal.

[0013] Furthermore, after purchasing the baggage fare package selected by the user from the ticketing system through the ticketing interface, the method further includes: in the event of a purchase failure, calling the payment interface; accessing the payment system through the payment interface to refund the payment fee for the baggage to be processed to the user.

[0014] According to another aspect of the present invention, a prepaid baggage change device is also provided, comprising: an acquisition unit, configured to acquire a target change task to be processed from a prepaid baggage follow-failure processing queue, wherein the follow-failure processing queue stores all change tasks corresponding to prepaid baggage that have failed to follow the passenger service system; a verification unit, configured to acquire baggage information of the baggage to be processed and user flight information corresponding to the baggage to be processed based on the target change task, and verify the baggage to be processed based on the baggage information and the user flight information to determine whether the baggage to be processed meets the change requirements; a query unit, configured to, if the baggage to be processed meets the change requirements, call a ticket search interface based on the user flight information to query baggage fare information of the changed flight; and a change unit, configured to match the baggage information with the baggage fare information, and if the baggage information matches any baggage fare package in the baggage fare information successfully, automatically change the baggage to be processed to the changed flight.

[0015] Further, the verification unit includes: a first acquisition module, used to acquire fare ticket information from the baggage information and user ticket information from the user flight information; a first verification module, used to verify whether the fare ticket information and the user ticket information are consistent, and to determine whether the status of the baggage to be processed is valid, obtaining a consistency verification result and a status verification result; a first comparison module, used to determine the changed flight based on the user flight information, acquire the scope of prepaid baggage applicable to the changed flight, and compare the baggage information with the scope of prepaid baggage applicable to determine whether the baggage to be processed is within the applicable scope, obtaining a scope verification result; a second verification module, used to acquire the baggage following rules of the changed flight, verify whether the changed flight allows the baggage to be processed to undergo free following changes, obtaining a rule verification result; and a first determination module, used to determine whether the baggage to be processed meets the change requirements based on the consistency verification result, the status verification result, the scope verification result, and the rule verification result.

[0016] Furthermore, the prepaid baggage change device also includes: a first monitoring module, used to monitor user flight changes and determine whether the user has purchased prepaid baggage when there is a flight change; a second acquisition module, used to acquire the prepaid baggage following information of the user from the passenger service system when the user has purchased prepaid baggage; and a first creation module, used to create a change task for the user's prepaid baggage and add the change task to the following failure processing queue when the passenger service system returns a following failure.

[0017] Furthermore, the modification unit includes: a first extraction module, used to traverse the baggage fare packages in the baggage fare information and extract the baggage price, baggage size, and baggage weight from the baggage fare packages; and a first matching module, used to match the baggage price, baggage size, and baggage weight in the baggage information with the baggage price, baggage size, and baggage weight in the baggage fare packages.

[0018] Furthermore, the modification unit also includes: a first invocation module, used to invoke the ticketing interface of the modified flight when the baggage information and any baggage fare package in the baggage fare information are successfully matched, and to purchase the matched baggage fare package from the ticketing system through the ticketing interface; a first generation module, used to generate modification information and update the status of the baggage to be processed to a modification success status when the baggage fare package is successfully purchased; and a first return module, used to return the modification information and the modification success status of the baggage to be processed to the user terminal.

[0019] Furthermore, the prepaid baggage change device further includes: a first sending module, used to send a notification of baggage following failure and the baggage fare information of the changed flight to the user terminal when the baggage information fails to match all baggage fare packages in the baggage fare information; a first calculation module, used to receive manual change information from the user terminal and calculate the change fee for the baggage to be processed based on the manual change information; a second calling module, used to generate a change request based on the manual change information and the change fee, and call the ticketing interface based on the change request to purchase the baggage fare package selected by the user terminal from the ticketing system through the ticketing interface. If the purchase is successful, the change information for the baggage to be processed is generated, and the status of the baggage to be processed is updated to a change successful status; and a second return module, used to return the change information and the change successful status of the baggage to the user terminal.

[0020] Furthermore, the prepaid baggage change device also includes: a third calling module, used to call the payment interface in the event of a purchase failure; and a first refund module, used to access the payment system through the payment interface to refund the payment fee for the baggage to be processed to the user.

[0021] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform any of the above-described methods for changing prepaid baggage.

[0022] According to another aspect of the present invention, an electronic device is also provided, including one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to implement any of the above-described methods for changing prepaid baggage.

[0023] In this application, the following steps are performed: First, the target change task to be processed is obtained from the prepaid baggage follow-failure processing queue. The follow-failure processing queue stores all change tasks corresponding to prepaid baggage that have failed to follow the passenger service system. Based on the target change task, the baggage information of the baggage to be processed and the user flight information corresponding to the baggage to be processed are obtained. The baggage to be processed is verified based on the baggage information and the user flight information to determine whether the baggage to be processed meets the change requirements. Then, if the baggage to be processed meets the change requirements, the ticket search interface is called based on the user flight information to query the baggage fare information of the changed flight. Finally, the baggage information is matched with the baggage fare information. If the baggage information and any baggage fare package in the baggage fare information are successfully matched, the baggage to be processed is automatically changed to the changed flight.

[0024] In this application, prepaid baggage that fails to automatically follow a flight is added to a failure-following processing queue. This triggers an automatic change process, retrieves the target change task from the failure-following processing queue, queries and retrieves a baggage fare package matching the baggage to be processed through interaction with the airline's mainframe, and automatically changes the baggage from the original flight to the new flight. This achieves automated changes for baggage that fails to follow a flight, improves the automation of baggage changes, thereby increasing the success rate of baggage follow-up changes and enhancing the user experience. This solves the technical problem in related technologies where, in the event of a failure to follow a prepaid baggage flight, a refund process for the prepaid baggage is automatically triggered, and then the passenger has to manually rebook the prepaid baggage for the changed flight, resulting in a low degree of automation in baggage changes. Attached Figure Description

[0025] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0026] Figure 1 This is a flowchart of an optional method for changing prepaid baggage according to an embodiment of the present invention;

[0027] Figure 2 This is an architecture diagram of an optional prepaid baggage change system according to an embodiment of the present invention;

[0028] Figure 3This is an optional flowchart of prepaid baggage change according to an embodiment of the present invention;

[0029] Figure 4 This is a schematic diagram of an optional prepaid baggage change device according to an embodiment of the present invention;

[0030] Figure 5 This is a hardware structure block diagram of an electronic device (or mobile device) that performs a method for changing prepaid baggage according to an embodiment of the present invention. Detailed Implementation

[0031] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0032] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0033] To facilitate understanding of the present invention by those skilled in the art, some terms or nouns involved in the various embodiments of the present invention are explained below:

[0034] The Passenger Service System (PSS) is an airline's passenger service system, which includes a reservation system and a departure system. When a user changes their flight, the additional services purchased by the user are automatically transferred to the new flight.

[0035] Passenger Name Record (PNR) is an electronic record stored in an airline's reservation system. It contains detailed data related to air travel, including passengers' personal information, travel itinerary, flight information, seat preferences, catering needs, and baggage information.

[0036] A user ticket, or Electronic Ticket (ET ticket) for short, refers to an electronic ticket generated after a user purchases an airline ticket.

[0037] A fare ticket, or Electronic Miscellaneous Document (EMD) for short, is an electronic ticket used in the aviation industry to record and process additional charges beyond the basic ticket price.

[0038] When a ticket is reissued and the user changes their flight, the ET ticket number changes and a new ET ticket number is generated.

[0039] Prepaid baggage is an add-on service where passengers purchase additional baggage allowance online or through other channels of the airline before the flight departs.

[0040] It should be noted that the method and apparatus for changing prepaid baggage in this application can be used in the field of aviation information technology to automatically change flights for prepaid baggage that has failed to follow, and can also be used in any field other than aviation information technology to automatically change flights for prepaid baggage that has failed to follow. This application does not limit the application field of the method and apparatus for changing prepaid baggage.

[0041] It should be noted that the relevant information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, and displayed data) involved in this application are information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of this data all comply with the relevant laws, regulations, and standards of the relevant regions, have taken necessary confidentiality measures, do not violate public order and good morals, and provide corresponding access points for users to choose to authorize or refuse. For example, this system has an interface with relevant users or organizations. Before obtaining relevant information, a request to obtain the information needs to be sent to the aforementioned user or organization through the interface, and the relevant information is obtained only after receiving consent from the aforementioned user or organization.

[0042] It should be noted that in this application, when collecting and analyzing customer information, users are provided with corresponding operation entry points to choose whether to agree to or reject the automated decision-making results; if the user chooses to reject, the process will proceed to the expert decision-making process.

[0043] The following embodiments of the present invention can be applied to various prepaid baggage change systems / applications / devices. The present invention aims to, in the event of a prepaid baggage follow-up failure, not to directly request a refund for the prepaid baggage, but to attempt to change the prepaid baggage to a new flight for the user free of charge. If a free change to a new flight is not possible, the user is provided with the option of manual change or a refund. This improves the success rate of prepaid baggage follow-up and provides users with more diverse options after follow-up failure, thus enhancing the user experience.

[0044] The present invention will now be described in detail with reference to various embodiments.

[0045] Example 1

[0046] According to an embodiment of the present invention, an embodiment of a method for changing prepaid baggage is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0047] Figure 1 This is a flowchart of an optional method for changing prepaid baggage according to an embodiment of the present invention, such as... Figure 1 As shown, the method includes the following steps:

[0048] In air travel services, when a user changes their itinerary for various reasons, resulting in a ticket reissue, the Passenger Service System (PSS) automatically reassigns the prepaid baggage associated with the ticket, ensuring the baggage travels on the new flight. However, in some scenarios, automatic reassignment may fail, rendering the prepaid baggage purchase invalid. The user then has to manually purchase a new prepaid baggage package for the reassigned flight, leading to a poor user experience.

[0049] Step S101: Obtain the target change task to be processed from the prepaid baggage follow-up failure processing queue.

[0050] The prepaid baggage change system, the main implementation subject of this embodiment of the invention, in step S101 above, creates a follow-failure processing queue to store all change tasks corresponding to prepaid baggage that failed to follow the passenger service system, thereby triggering an automatic change process for the failed baggage. The system continuously monitors the follow-failure processing queue and obtains change tasks from it, thereby triggering the target change task and realizing the automatic change of the target baggage.

[0051] Furthermore, before retrieving the target change task to be processed from the prepaid baggage follow-up failure processing queue, the process also includes: monitoring user flight changes; determining whether the user has purchased prepaid baggage if the user has a flight change; retrieving the user's prepaid baggage follow-up status from the passenger service system if the user has purchased prepaid baggage; and creating a change task for the user's prepaid baggage and adding the change task to the follow-up failure processing queue if the passenger service system returns a follow-up failure.

[0052] In this embodiment of the invention, the creation of the follow-up failure processing queue is the key to realizing automated changes. The system continuously monitors the user's flight change status and determines whether the user who changed the flight purchased prepaid baggage on the original flight. If so, it retrieves the follow-up status of the user's prepaid baggage from the passenger service system. If the passenger service system returns a follow-up failure for the prepaid baggage, it packages the failed baggage service and its related information, such as passenger information, flight change details, prepaid baggage specifications and prices, original PNR and new PNR, original ET and new ET ticket information, etc., and creates a change task. Then, it adds this change task to the follow-up failure processing queue for further processing.

[0053] Step S102: Based on the target change task, obtain the baggage information of the baggage to be processed and the user flight information corresponding to the baggage to be processed, and verify the baggage to be processed based on the baggage information and user flight information to determine whether the baggage to be processed meets the change requirements.

[0054] In step S102, the system extracts two sets of key information from the previously acquired target change task: one is the detailed information of the baggage to be processed, including but not limited to the specifications (such as weight and size), price, EMD ticket number and original ET ticket number in the original fare ticket information of the prepaid baggage; the other set is the user flight change information related to the baggage, mainly including the new PNR (Passenger Name Record) number, the ET ticket number in the changed user ticket information, and the flight identifier of the changed flight.

[0055] Based on baggage information and user flight information, the baggage to be processed can be verified to see if it meets the change requirements. Only if the change requirements are met can the change be automated. If the change requirements are not met, the user needs to manually change the baggage or apply for a refund.

[0056] The verification process for pending baggage includes: information consistency verification, baggage status verification, business rule verification, and verification of the scope of applicable baggage changes. Through these verifications, it can be determined whether the pending baggage meets the change requirements, thus automatically changing the status of baggage that meets the requirements.

[0057] Furthermore, the steps for verifying the baggage to be processed based on baggage information and user flight information to determine whether the baggage meets the change requirements include: obtaining fare ticket information from the baggage information and user ticket information from the user flight information; verifying whether the fare ticket information and user ticket information are consistent, and determining whether the status of the baggage to be processed is valid, obtaining consistency verification results and status verification results; determining the changed flight based on the user flight information, obtaining the scope of prepaid baggage applicable to the changed flight, and comparing the baggage information with the scope of prepaid baggage applicable to determine whether the baggage to be processed is within the applicable scope, obtaining scope verification results; obtaining the baggage following rules of the changed flight, verifying whether the changed flight allows the baggage to be processed to follow the change free of charge, obtaining rule verification results; and determining whether the baggage to be processed meets the change requirements based on the consistency verification results, status verification results, scope verification results, and rule verification results.

[0058] Specifically, when processing change requests for prepaid baggage that have failed to follow the original baggage, the first step is to extract key baggage information from the target change request, especially the baggage fare ticket information, including the EMD ticket number for the prepaid baggage. Simultaneously, the associated user ticket information, i.e., the changed ET ticket number, is extracted from the flight change information. Then, the EMD ticket number and ET ticket number are compared to determine if they match, obtaining a consistency check result. This consistency check result ensures that the baggage change request is directed to the correct baggage service and passenger. At the same time, it is checked whether the prepaid baggage EMD ticket is in a valid and changeable state, such as whether it is OPEN FOR USE, excluding any used, invalid, or refunded EMD tickets to ensure the feasibility and effectiveness of the change request.

[0059] Subsequently, it is necessary to determine the changed flight based on the user's flight information and further obtain the scope of prepaid baggage coverage for that flight, which may include maximum weight limits, maximum size regulations, etc. Then, the specifications, dimensions, and other information of the baggage to be processed are compared with the scope of prepaid baggage coverage for the changed flight to determine whether the baggage is still applicable under the changed flight conditions, thus obtaining the scope verification result.

[0060] Finally, the system retrieves the baggage following rules for the changed flight. These rules may vary depending on the airline's policies and the specific characteristics of the flight. For example, some flights may only allow carry-on baggage and not checked baggage, preventing users from transferring their baggage to the new flight. Alternatively, some flights may require a fee for baggage transfers, prohibiting free transfers and thus preventing automatic baggage transfers. The system checks whether the changed flight allows prepaid baggage to follow the flight free of charge; this verification process is called rule verification. The result of rule verification directly affects the decision-making path for subsequent automatic transfer attempts or manual transfer / refund requests.

[0061] By integrating consistency verification results, status verification results, range verification results, and rule verification results, the system can comprehensively assess whether the baggage to be processed meets the change requirements. If all verifications pass, the system determines that the prepaid baggage can be changed to a new flight free of charge, and the process will proceed to the automatic change stage. Conversely, if any verification fails, such as an invalid EMD ticket status, the prepaid baggage being unsuitable for the changed flight, or free changes not being allowed, the system will determine that the baggage to be processed does not meet the change requirements and will instead provide the user with the option of manual change or refund to complete the subsequent processing.

[0062] By verifying changes before they are made, the success rate of changes is improved, the compliance and rationality of the service change process are ensured, and the overall processing efficiency and user experience are enhanced.

[0063] Step S103: If the baggage to be processed meets the change requirements, call the ticket search interface based on the user's flight information to query the baggage fare information for the changed flight.

[0064] In step S103 above, if the baggage to be processed passes the verification and meets the change requirements, the ticket search interface of the corresponding airline system for the changed flight is called according to the user's flight information to query the baggage fare information of the changed flight. The user's flight information includes, but is not limited to: the flight identifier of the changed flight, the departure airport and the arrival airport, the departure date, the departure time, etc. The baggage fare information includes, but is not limited to: baggage fare packages, baggage specifications (such as baggage weight) in the package, price, applicable conditions (such as flight cabin restrictions), etc. Generally speaking, airlines will preset a series of baggage specifications and price them to generate baggage fare packages. Users can purchase the corresponding baggage fare packages according to their own needs.

[0065] In this embodiment of the invention, interaction with the aviation system is achieved through a ticket search interface. Baggage fare information is retrieved based on accurate flight information, increasing the probability of finding a matching prepaid baggage service on a new flight, thereby improving the overall success rate of automatic fare changes. Automated fare inquiries reduce the need for manual intervention, simplify the service change process, and improve the speed and efficiency of service processing.

[0066] Step S104: Match baggage information with baggage fare information. If any baggage fare package in the baggage information and baggage fare information is successfully matched, the baggage to be processed will be automatically changed to the changed flight.

[0067] In step S104 above, the baggage information of the user's pending baggage is matched with the baggage fare information obtained from the query. If the baggage information successfully matches any baggage fare package recorded in the baggage fare information, the pending baggage is automatically transferred to the changed flight, realizing the automatic transfer of prepaid baggage that failed to follow, thereby improving the continuity and satisfaction of passenger services.

[0068] Furthermore, the steps for matching baggage information with baggage fare information include: traversing the baggage fare packages in the baggage fare information, extracting the baggage price, baggage size, and baggage weight from the baggage fare packages; and matching the baggage price, baggage size, and baggage weight in the baggage information with the baggage price, baggage size, and baggage weight in the baggage fare packages.

[0069] Specifically, when matching baggage fare information, the system first iterates through each fare package in the baggage fare information obtained from the ticketing interface. These packages typically include prepaid baggage services of different sizes, and each package clearly indicates the price, size, and weight of the baggage. By iterating through this information one by one, the system can comprehensively examine all possible matching prepaid baggage service options on the changed flight. During the iteration, the system extracts three key attributes from each fare package: baggage price, baggage size, and baggage weight. Then, it compares these key attributes one by one with the corresponding attributes in the baggage information of the baggage to be processed, looking for a perfect match. If, during the iteration and comparison, at least one baggage fare package is found whose baggage price, size, and weight perfectly match the baggage to be processed, the system will consider the match successful. At this point, the system will automatically execute the change process, attempting to transfer the prepaid baggage service from the original flight to the changed flight, achieving a seamless service transition.

[0070] Furthermore, if any baggage fare package in the baggage information and baggage fare information is successfully matched, the steps to automatically change the pending baggage to the changed flight include: if any baggage fare package in the baggage information and baggage fare information is successfully matched, calling the ticketing interface of the changed flight, and purchasing the successfully matched baggage fare package from the ticketing system through the ticketing interface; if the baggage fare package is successfully purchased, generating change information and updating the status of the pending baggage to a changed success status; and returning the change information and the changed success status of the pending baggage to the user.

[0071] Specifically, when the baggage to be processed is successfully matched with any baggage fare package, it indicates that the baggage can be transferred to the changed flight. The system then calls the ticketing interface of the changed flight, interacts with the airline's reservation system, and executes the baggage fare package reservation and purchase process. The system purchases the matching baggage fare package for the changed flight. If the purchase is successful, change information is generated, including but not limited to the new EMD ticket number, the PNR and ET ticket information of the changed flight, and the specific prepaid baggage specifications and price. Subsequently, the system updates the order status of the baggage to be processed to "Change Successful." The change task corresponding to the successfully changed baggage is removed from the follow-up failed processing queue, and the change information and change success status are fed back to the user, indicating that the user no longer needs to manually purchase prepaid baggage.

[0072] Furthermore, after matching baggage information with baggage fare information, the process also includes: if all baggage fare packages in the baggage information and baggage fare information fail to match, sending a notification of baggage following failure and the baggage fare information for the changed flight to the user; receiving manual change information from the user and calculating the change fee for the pending baggage based on the manual change information; generating a change request based on the manual change information and the change fee, and calling the ticketing interface based on the change request to purchase the baggage fare package selected by the user from the ticketing system through the ticketing interface; if the purchase is successful, generating change information for the pending baggage and updating the status of the pending baggage to a change successful status; and returning the change information and the change successful status of the pending baggage to the user.

[0073] In an optional embodiment, in addition to automatic changes, this embodiment of the invention also retains manual changes and automatic cancellation mechanisms. When the system completes the matching process between baggage information and baggage fare information and finds that none of the fare packages can be successfully matched with the baggage information to be processed, it means that no prepaid baggage service of the same size and price can be found. In this case, the system will send a baggage following failure notification to the user's client, and at the same time provide all baggage fare information for the changed flight, including prepaid baggage of different sizes and their prices. This notification is intended to inform the user of the available options for their prepaid baggage service on the new flight, so as to facilitate subsequent manual change operations.

[0074] After receiving the notification, users can manually change to the most suitable prepaid baggage service based on their needs. The system will receive the manual change information sent by the user, which typically includes the new prepaid baggage type selected by the user and whether they accept the change and the potential costs. Based on the user's selection, the system will calculate the cost of changing the baggage from the original service to the new service, which may include additional baggage service fees and possible change fees.

[0075] After calculating the change fee, the system will generate a change request based on the user's selected manual change information and the calculated change fee. This request includes the user's selected prepaid baggage type, change fee, and all necessary user confirmation information. Subsequently, the system will call the ticketing interface to purchase the user's selected baggage fare package from the airline's ticketing system. The ticketing interface call is based on the change request, and the system will automatically execute the purchase operation to ensure that the user's selected prepaid baggage service is accurately booked on the new flight.

[0076] If the ticketing interface call is successful, meaning the user's selected baggage fare package has been successfully purchased, the system will generate function change information, including the EMD ticket information for the pending baggage, the PNR and ET ticket information for the new flight, and the specific specifications and price of the purchased prepaid baggage service. Simultaneously, the system will update the order status of the pending baggage to "Change Successful," indicating that the change to the prepaid baggage service has been officially completed. Finally, the system will provide real-time feedback on the change information and the success status to the user, ensuring that the user is immediately aware of the latest status of their prepaid baggage service and can enjoy the changed prepaid baggage service.

[0077] Furthermore, after purchasing the baggage fare package selected by the user from the ticketing system through the ticketing interface, the system also includes: in the event of a purchase failure, calling the payment interface; and accessing the payment system through the payment interface to refund the payment fee for the baggage to be processed to the user.

[0078] In one optional embodiment, if the user's manually selected baggage fare package purchase fails, an automatic refund mechanism is triggered. Purchase failure may be due to various reasons, including but not limited to system errors, insufficient inventory, and payment failure. In this situation, maintaining the security of the user's funds is crucial. After a purchase failure, the system will call the payment interface to interact with the payment system. The payment interface's function is not limited to payment; it also supports refund operations. The system will access the payment system through the payment interface and initiate a refund request to return the payment for the pending baggage to the user. Upon receiving the request, the payment system will execute the refund operation, returning the payment for the pending baggage to the user's payment account and notifying the user of the successful refund.

[0079] Through the above steps, the system first retrieves the target change task to be processed from the prepaid baggage follow-up failure processing queue. This queue stores all change tasks corresponding to prepaid baggage that failed to follow the passenger service system. Based on the target change task, the system retrieves the baggage information and the corresponding user flight information of the baggage to be processed. The system then verifies the baggage to be processed based on the baggage information and the user flight information to determine if the baggage meets the change requirements. If the baggage meets the change requirements, the system calls the ticket search interface based on the user flight information to query the baggage fare information for the changed flight. Finally, the system matches the baggage information with the baggage fare information. If the baggage information and any baggage fare package in the baggage fare information match successfully, the baggage to be processed is automatically changed to the changed flight.

[0080] In this embodiment, prepaid baggage that fails to follow automatically is added to the follow failure processing queue, which triggers an automatic change process. The target change task is obtained from the follow failure processing queue, and through interaction with the airline's host, a baggage fare package matching the baggage to be processed is queried and obtained. The baggage to be processed is automatically changed from the original flight to the new flight, realizing the automated change of baggage that fails to follow, improving the automation of baggage change, thereby increasing the success rate of baggage follow change, improving the user experience, and solving the technical problem in related technologies where, in the case of prepaid baggage follow failure, the prepaid baggage refund process is automatically triggered, and then the passenger has to manually rebook the prepaid baggage for the changed flight, resulting in a low degree of automation in baggage change.

[0081] The following describes in detail another optional implementation method.

[0082] Figure 2 This is an architecture diagram of an optional prepaid baggage change system according to an embodiment of the present invention, such as... Figure 3 As shown, the prepaid baggage change system interacts with the PSS system, including a trigger module, a verification module, an automatic change module, and a manual change module. Specifically,

[0083] The trigger module refers to the system adding the prepaid baggage order to the prepaid baggage follow-up failure processing queue after the user's flight change is completed, based on information such as PNR, ET ticket and EMD ticket, and waiting for subsequent business process processing.

[0084] The verification module refers to the system determining whether prepaid baggage can be transferred to a new flight free of charge based on information such as order data, PNR, ET ticket, and EMD ticket. If it is allowed, the system will proceed to the automatic transfer process; if it is not allowed, the system will proceed to the manual transfer process.

[0085] The automatic change module refers to the system automatically querying the airline's mainframe system for prepaid baggage fares when the system allows free changes to prepaid baggage for a new flight. If prepaid baggage of the same size and price is found, the system initiates the mainframe booking process, including service reservation and ticketing. If, during this process, no prepaid baggage of the same size and price is found, the reservation fails, or the ticketing fails, the system will proceed to the manual change process. If the system does not allow free changes to prepaid baggage for a new flight, the system will directly enter the manual change process.

[0086] The manual change module provides a manual change process for users when the system does not allow the free transfer of prepaid baggage to a new flight. The module includes two processing methods: manual change and refund. Manual change involves the user going through the system step-by-step to check prepaid baggage fares, book services, pay fares, and issue tickets. This allows users to change the specifications or price of their prepaid baggage to a new flight by paying a change fee and product price difference. Refund allows users to request a refund for prepaid baggage, serving as the final means to ensure the safety of user funds.

[0087] Figure 3 This is an optional flowchart of a prepaid baggage change according to an embodiment of the present invention, such as... Figure 3 As shown, the process for changing prepaid baggage includes:

[0088] Step 1: The system accesses the PSS system to obtain the auto-following status of prepaid baggage. If the prepaid baggage follows successfully, the system updates the order information and returns the order information to the user. If the prepaid baggage fails to follow, the failed prepaid baggage is added to the follow failure processing queue, and Step 2 is executed.

[0089] Step 2: Obtain the baggage to be processed from the following timekeeping processing queue and enter the baggage change process;

[0090] Step 3: Verify whether the baggage to be processed meets the change requirements. If yes, proceed to Step 4; otherwise, proceed to Step 8.

[0091] Step 4: Send a query request to the airline system corresponding to the changed flight to query the baggage fare for the changed flight. The airline system will return the query results based on the query request.

[0092] Based on the user's flight information recorded in the order, such as: prepaid baggage EMD ticket, EMD ticket associated with the old flight ET ticket, new PNR after ticket change, and new ET ticket after ticket change, call the host ticket query interface to query the baggage fare information of the changed flight.

[0093] The system iterates through the baggage fare packages found in the query, comparing the price, baggage weight, baggage size, and baggage information recorded in the order with the fare package details. If a baggage package with identical information is found, the system purchases the ticket from the ticketing system. If no match is found, it indicates that no fare is available. The system then updates the order information, changes the order status to "change failed," and initiates the manual change process.

[0094] Based on the order record's prepaid baggage EMD ticket, the ET ticket associated with the old flight linked to the EMD ticket, the new PNR after the ticket was issued, the new ET ticket after the ticket was issued, the baggage information for the prepaid baggage, and the successfully matched baggage fare package, the ticketing interface is invoked to purchase the baggage fare package from the ticketing system. Because there is no change fee and the new and old prepaid baggage prices are consistent, no payment is required after booking, and the ticket can be issued directly. If the booking is successful, the order information is updated and the order status is updated to "Change Successful." If the booking or ticketing fails, the order information is updated and the order status is updated to "Change Failed," and the manual change process begins.

[0095] Step 5: Is there a matching baggage rate package? If yes, proceed to step 6; otherwise, proceed to step 8.

[0096] Step 6: Initiate a baggage change request to the ticketing system of the changed flight, purchase a matching baggage fare package, and after successful purchase, change the baggage to be processed to the changed flight and return the change result;

[0097] Step 7: Determine if the change was successful. If yes, update the order information and return the order information to the user. If no, proceed to step 8.

[0098] Step 8: Proceed to the manual change process.

[0099] If a user selects a prepaid baggage order whose status is "failed to change" on the front-end page, and chooses to request a refund, the order will directly enter the refund process to ensure the safety of the user's funds; if the user chooses to manually change the order, the order will enter the manual change process.

[0100] The user selects the prepaid baggage that needs to be manually changed, clicks "Search," and the system calls the ticket search interface based on the prepaid baggage EMD ticket, the ET ticket associated with the old flight, the new PNR after the ticket was changed, the new ET ticket after the ticket was changed, and the baggage information of the prepaid baggage. The system then queries the baggage fare package for the prepaid baggage and returns the available fare packages to the user.

[0101] When a user selects prepaid baggage of a specific price and size, the system calculates the change fee and service difference based on the prepaid baggage selected by the user and other information required for booking, sends a ticket purchase request to the ticketing system, updates the order information based on the booking results, and displays it to the user.

[0102] When a user initiates a payment, the system receives the payment result from the payment service and, based on the payment result, initiates a ticketing request. The system then updates the order information based on the ticketing result. If the ticketing is successful, the order status is updated to "Change Successful".

[0103] The following example illustrates the baggage change process:

[0104] Scenario Example 1: The ticket is changed (a new PNR is generated and reissued), the prepaid baggage tracking fails, the prepaid baggage is manually changed successfully, and it is changed to a new flight free of charge.

[0105] Assumptions: Passenger A booked a ticket for April 7, 2025, from region A to region B, flight number X, class Y, and simultaneously purchased a 5KG prepaid baggage allowance for the current segment. The ET ticket order number is 2025************1, PNR: *****A, ET ticket number: 000*********1, EMD ticket number: 000*********2. Due to personal reasons, the passenger initiated a ticket change, changing the departure date from April 7 to April 8, with all other information remaining unchanged. A new PNR was generated: *****B, and a new ET ticket number: 000*********3. The PSS system triggered EMD ticket tracking, but the tracking failed.

[0106] The system detected that prepaid baggage follow-up for order 2025************1 failed, added the order to the prepaid baggage follow-up failure processing queue, and updated the order status to "under change".

[0107] The automatic process triggers the processing of order 2025************1 in the prepaid baggage follow-up failure handling queue. It verifies that the status of ET ticket number 000*********2 is OPEN FOR USE and that the order status of 2025************1 is under change. It verifies the configuration: the departure airport is airport in region A, the arrival airport is airport in region B, the flight type is one-way, the flight number is X, and the cabin class is Y. It allows prepaid baggage to be changed to a new flight free of charge.

[0108] Based on EMD ticket number 000*********2, new flight PNR number *****B, new flight ET ticket number 000*********3, and prepaid baggage weight of 5KG, the fare system was consulted, and the following fare results were obtained:

[0109] Table 1 Results of Automatically Changed Freight Rate Inquiry

[0110] Serial Number Specification price Price difference 1 5KG 2** 0 2 10KG 4** 2** 3 15KG 6** 4**

[0111] Iterate through the retrieved freight rate results to identify the freight rate package with serial number 1, which has a specification of 5KG and a price difference of 0, thus meeting the requirement of the same specification and price.

[0112] Based on the fare results of EMD ticket number 000*********2, new flight PNR number *****B, new flight ET ticket number 000*********3, prepaid baggage weight 5KG, and serial number 1, the ticketing system is invoked to book the fare package and issue the ticket. A new EMD ticket number 000*********4 is generated, and the EMD ticket number and ticket information are recorded in the order information. The order status is updated to "change successful," thus automatically transferring the prepaid baggage that failed to follow the original flight to the new flight.

[0113] Scenario Example 2: The ticket is changed (a new PNR is generated and reissued), the prepaid baggage cannot be transferred to the new flight for free due to the airline's configuration, and the user chooses to manually transfer the prepaid baggage to the new flight.

[0114] Assumptions: Passenger B booked a ticket on the official website for April 10, 2025, from region C to region D, flight number XX, Y class, and simultaneously purchased a 10KG prepaid baggage allowance for the current flight segment. The ET ticket order number is 2025************2, PNR: *****C, ET ticket number: 000********11, EMD ticket number: 000********22. Due to personal reasons, the passenger initiated a ticket change, changing the departure date from April 10 to April 11, with other information remaining unchanged. A new PNR was generated: *****D, and a new ET ticket number: 000********33. The PSS system triggered EMD ticket tracking, but the tracking failed.

[0115] The system detected that prepaid baggage follow-up for order 2025************2 failed, added the order to the prepaid baggage follow-up failure processing queue, and updated the order status to "under change".

[0116] The automatic process triggers the processing of order 2025************2 in the prepaid baggage follow-up failure processing queue. It verifies that the status of ET ticket number 000********22 is OPEN FOR USE and that the order status of 2025************2 is under change. It also verifies the configuration: the departure airport is a region C airport, the arrival airport is a region D airport, the flight type is one-way, the flight number is XX, the cabin class is Y, and the new flight does not allow free changes to prepaid baggage.

[0117] Because the new flight regulations do not allow free baggage changes, the system modified the order information and updated the order status to "Change Failed".

[0118] When a user views the order information for order number 2025************2 on the front end, the order status is "Change failed," and the user chooses to manually change it.

[0119] Click to check fares. The system will query the fare system based on the user's request, according to EMD ticket number 000********22, new flight PNR number *****D, new flight ET ticket number 000********33, and prepaid baggage weight of 10KG, and obtain the following fare results, which will then be returned to the user.

[0120] Table 2 Results of Manually Changing Freight Rates

[0121] Serial Number Specification price Price difference handling fee 1 10KG 2** 0 2* 2 15KG 4** 2** 2* 3 20KG 6** 4** 2*

[0122] The user selects prepaid baggage number 2 for reservation. Based on the user's selection, the system calls the host to make the reservation, returns the reservation result, and prompts the user to pay.

[0123] The user chooses to pay the price difference and change fee through a third party. The system receives the payment result, calls the ticketing system to issue the ticket, and after the ticket is successfully issued, updates the order information and changes the order status to "change successful," allowing the user to manually change the prepaid baggage that failed to follow to a new flight.

[0124] This invention aims to improve the success rate of prepaid baggage following and provide users with more options after a failed attempt to follow prepaid baggage on a new flight. Instead of directly requesting a refund, it attempts to rebook the baggage onto a new flight free of charge. If a free rebooking is not possible, the user is offered the choice of manual rebooking or a refund. This improves the user experience by offering more diverse options after a failed attempt.

[0125] The following is a detailed description with reference to another embodiment.

[0126] Example 2

[0127] The prepaid baggage change device provided in this embodiment includes multiple implementation units, each of which corresponds to a specific implementation step in the above embodiment one. The specific implementation method and beneficial effects can be referred to the foregoing method embodiment, and will not be repeated here.

[0128] Figure 4 This is a schematic diagram of an optional prepaid baggage change device according to an embodiment of the present invention, such as... Figure 4 As shown, the prepaid baggage change device includes: an acquisition unit 41, a verification unit 42, a query unit 43, and a change unit 44, wherein,

[0129] The acquisition unit 41 is used to acquire the target change task to be processed from the follow failure processing queue of prepaid baggage, wherein the follow failure processing queue stores all change tasks corresponding to prepaid baggage that have failed to follow based on the passenger service system.

[0130] The verification unit 42 is used to obtain the baggage information of the baggage to be processed and the user flight information corresponding to the baggage to be processed based on the target change task, and to verify the baggage to be processed based on the baggage information and the user flight information to determine whether the baggage to be processed meets the change requirements.

[0131] The query unit 43 is used to call the ticket search interface based on the user's flight information to query the baggage fare information of the changed flight when the baggage to be processed meets the change requirements.

[0132] The change unit 44 is used to match baggage information with baggage fare information. If the baggage information and any baggage fare package in the baggage fare information are successfully matched, the baggage to be processed will be automatically changed to the changed flight.

[0133] The aforementioned prepaid baggage change device retrieves the target change task to be processed from the prepaid baggage follow-failure processing queue through the acquisition unit 41. The follow-failure processing queue stores all change tasks corresponding to prepaid baggage that failed to follow the passenger service system. The verification unit 42 retrieves the baggage information of the baggage to be processed and the user flight information corresponding to the baggage to be processed based on the target change task, and verifies the baggage to be processed based on the baggage information and user flight information to determine whether the baggage to be processed meets the change requirements. If the baggage to be processed meets the change requirements, the query unit 43 calls the ticket search interface based on the user flight information to query the baggage fare information of the changed flight. The change unit 44 matches the baggage information with the baggage fare information. If the baggage information and any baggage fare package in the baggage fare information are successfully matched, the baggage to be processed is automatically changed to the changed flight.

[0134] In this embodiment, prepaid baggage that fails to follow automatically is added to the follow failure processing queue, which triggers an automatic change process. The target change task is obtained from the follow failure processing queue, and through interaction with the airline's host, a baggage fare package matching the baggage to be processed is queried and obtained. The baggage to be processed is automatically changed from the original flight to the new flight, realizing the automated change of baggage that fails to follow, improving the automation of baggage change, thereby increasing the success rate of baggage follow change, improving the user experience, and solving the technical problem in related technologies where, in the case of prepaid baggage follow failure, the prepaid baggage refund process is automatically triggered, and then the passenger has to manually rebook the prepaid baggage for the changed flight, resulting in a low degree of automation in baggage change.

[0135] Further, the verification unit includes: a first acquisition module, used to acquire fare ticket information from baggage information and user ticket information from user flight information; a first verification module, used to verify whether the fare ticket information and user ticket information are consistent, and to determine whether the status of the baggage to be processed is valid, obtaining consistency verification results and status verification results; a first comparison module, used to determine the changed flight based on user flight information, acquire the scope of prepaid baggage applicable to the changed flight, and compare the baggage information with the scope of prepaid baggage applicable to determine whether the baggage to be processed is within the applicable scope, obtaining scope verification results; a second verification module, used to acquire the baggage following rules of the changed flight, verify whether the changed flight allows the baggage to be processed to follow the change for free, obtaining rule verification results; and a first determination module, used to determine whether the baggage to be processed meets the change requirements based on the consistency verification results, status verification results, scope verification results, and rule verification results.

[0136] Furthermore, the prepaid baggage change device also includes: a first monitoring module, used to monitor user flight changes and determine whether the user has purchased prepaid baggage when there is a flight change; a second acquisition module, used to acquire the prepaid baggage following information of the user when the user has purchased prepaid baggage from the passenger service system; and a first creation module, used to create a change task for the user's prepaid baggage and add the change task to the following failure processing queue when the passenger service system returns a following failure.

[0137] Furthermore, the modification unit includes: a first extraction module, used to traverse the baggage fare packages in the baggage fare information and extract the baggage price, baggage size, and baggage weight from the baggage fare packages; and a first matching module, used to match the baggage price, baggage size, and baggage weight in the baggage information with the baggage price, baggage size, and baggage weight in the baggage fare packages.

[0138] Furthermore, the modification unit also includes: a first calling module, used to call the ticketing interface of the modified flight when any baggage fare package in the baggage information and baggage fare information is successfully matched, and purchase the matched baggage fare package from the ticketing system through the ticketing interface; a first generating module, used to generate modification information and update the status of the baggage to be processed to a modification success status when the baggage fare package is successfully purchased; and a first returning module, used to return the modification information and the modification success status of the baggage to be processed to the user terminal.

[0139] Furthermore, the prepaid baggage change device also includes: a first sending module, used to send a notification of baggage following failure and the baggage fare information of the changed flight to the user terminal when all baggage fare packages in the baggage information and baggage fare information fail to match; a first calculation module, used to receive manual change information from the user terminal and calculate the change fee for the baggage to be processed based on the manual change information; a second calling module, used to generate a change request based on the manual change information and the change fee, and call the ticketing interface based on the change request to purchase the baggage fare package selected by the user terminal from the ticketing system through the ticketing interface. If the purchase is successful, the change information for the baggage to be processed is generated, and the status of the baggage to be processed is updated to the change successful status; and a second return module, used to return the change information and the change successful status of the baggage to the user terminal.

[0140] Furthermore, the prepaid baggage change device also includes: a third calling module, used to call the payment interface in the event of a purchase failure; and a first refund module, used to access the payment system through the payment interface to refund the payment fee for the baggage to be processed to the user.

[0141] The aforementioned prepaid baggage change device may also include a processor and a memory. The aforementioned acquisition unit 41, verification unit 42, query unit 43, change unit 44, etc., are all stored in the memory as program units, and the processor executes the aforementioned program units stored in the memory to realize the corresponding functions.

[0142] The aforementioned processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured, and changes to a user's prepaid baggage can be made by adjusting kernel parameters.

[0143] The aforementioned memory may include non-permanent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0144] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform any of the above-described methods for changing prepaid baggage.

[0145] According to another aspect of the present invention, an electronic device is also provided, including one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to implement any of the above-described methods for changing prepaid baggage.

[0146] According to another aspect of the present invention, a computer program product is also provided, the computer program product including a computer program, wherein when the computer program is executed by a processor, it implements any of the above-described methods for changing prepaid baggage.

[0147] This application also provides a computer program product, which, when executed on a data processing device, is suitable for executing an initialization program with the following method steps: obtaining a target change task to be processed from a prepaid baggage follow-failure processing queue, wherein the follow-failure processing queue stores all change tasks corresponding to prepaid baggage that have failed to follow the passenger service system; obtaining baggage information of the baggage to be processed and user flight information corresponding to the baggage to be processed based on the target change task, and verifying the baggage to be processed based on the baggage information and user flight information to determine whether the baggage to be processed meets the change requirements; if the baggage to be processed meets the change requirements, calling the ticket search interface based on the user flight information to query the baggage fare information of the changed flight; matching the baggage information with the baggage fare information, and if the baggage information and any baggage fare package in the baggage fare information are successfully matched, automatically changing the baggage to be processed to the changed flight.

[0148] This application also provides a computer program product, which, when executed on a data processing device, is suitable for executing an initialization program with the following method steps: obtaining fare ticket information from baggage information and user ticket information from user flight information; verifying whether the fare ticket information and user ticket information are consistent, and determining whether the status of the baggage to be processed is valid, obtaining consistency verification results and status verification results; determining the changed flight based on the user flight information, obtaining the scope of prepaid baggage applicable to the changed flight, comparing the baggage information with the scope of prepaid baggage applicable, determining whether the baggage to be processed is within the applicable scope, and obtaining a scope verification result; obtaining the baggage following rules of the changed flight, verifying whether the changed flight allows the baggage to be processed to follow the change free of charge, and obtaining a rule verification result; and determining whether the baggage to be processed meets the change requirements based on the consistency verification result, status verification result, scope verification result, and rule verification result.

[0149] This application also provides a computer program product, which, when executed on a data processing device, is suitable for executing an initialization program having the following method steps: monitoring user flight changes; determining whether the user has purchased prepaid baggage if the user has changed their flight; obtaining the user's prepaid baggage following information from the passenger service system if the user has purchased prepaid baggage; and creating a change task for the user's prepaid baggage and adding the change task to the following failure processing queue if the passenger service system returns a following failure.

[0150] This application also provides a computer program product, which, when executed on a data processing device, is suitable for executing an initialization program having the following method steps: traversing baggage fare packages in baggage fare information, extracting baggage price, baggage size, and baggage weight from the baggage fare packages; and matching the baggage price, baggage size, and baggage weight in the baggage information with the baggage price, baggage size, and baggage weight in the baggage fare packages.

[0151] This application also provides a computer program product, which, when executed on a data processing device, is suitable for executing an initialization program with the following method steps: if any baggage fare package in the baggage information and baggage fare information is successfully matched, the program calls the ticketing interface of the changed flight and purchases the matched baggage fare package from the ticketing system through the ticketing interface; if the baggage fare package is successfully purchased, the program generates change information and updates the status of the baggage to be processed to a change success status; and the program returns the change information and the change success status of the baggage to be processed to the user.

[0152] This application also provides a computer program product, which, when executed on a data processing device, is suitable for executing an initialization program with the following method steps: If all baggage fare packages in the baggage information and baggage fare information fail to match, send a notification of baggage following failure and the baggage fare information of the changed flight to the user terminal; receive manual change information from the user terminal and calculate the change fee for the baggage to be processed based on the manual change information; generate a change request based on the manual change information and the change fee, and call the ticketing interface based on the change request to purchase the baggage fare package selected by the user terminal from the ticketing system through the ticketing interface; if the purchase is successful, generate change information for the baggage to be processed and update the status of the baggage to be processed to a change successful status; return the change information and the change successful status of the baggage to the user terminal.

[0153] This application also provides a computer program product that, when executed on a data processing device, is suitable for executing an initialization program with the following method steps: in the event of a purchase failure, calling a payment interface; accessing a payment system through the payment interface to refund the payment for the pending baggage to the user.

[0154] Figure 5 This is a hardware structure block diagram of an electronic device (or mobile device) that performs a method for changing prepaid baggage according to an embodiment of the present invention. Figure 5 As shown, an electronic device may include one or more processors ( Figure 5 The processor, denoted by 502a, 502b, ..., 502n, can include, but is not limited to, a processing device such as a microprocessor (MCU) or a programmable logic device (FPGA), and a memory 504 for storing data. In addition, it may include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports in the I / O interface), a network interface, a keyboard, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 5 The structure shown is for illustrative purposes only and does not limit the structure of the electronic device described above. For example, the electronic device may also include components that are more... Figure 5 The more or fewer components shown, or having the same Figure 5 The different configurations shown.

[0155] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0156] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0157] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0158] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0159] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0160] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0161] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method of changing a pre-paid baggage, characterized by, The method comprises the following steps: obtaining a target change task to be processed from a follow-up failure processing queue of pre-paid baggage, wherein the follow-up failure processing queue stores change tasks corresponding to all pre-paid baggage based on follow-up failure of passenger service system; obtaining baggage information of the baggage to be processed and user flight information corresponding to the baggage to be processed based on the target change task, and checking the baggage to be processed based on the baggage information and the user flight information to determine whether the baggage to be processed meets change requirements; in the case that the baggage to be processed meets change requirements, calling a ticket checking interface based on the user flight information to query baggage transportation price information of a changed flight; matching the baggage information with the baggage transportation price information, and in the case that any of the baggage transportation price information and the baggage transportation price information is matched successfully, automatically changing the baggage to be processed to the changed flight.

2. The method of claim 1, wherein, The step of checking the baggage to be processed based on the baggage information and the user flight information to determine whether the baggage to be processed meets change requirements comprises: obtaining fare ticket information from the baggage information and user ticket information from the user flight information; checking whether the fare ticket information and the user ticket information are consistent and determining whether the state of the baggage to be processed is a valid state to obtain consistency checking results and state checking results; determining a changed flight based on the user flight information, obtaining a pre-paid baggage applicable range of the changed flight, and comparing the baggage information with the pre-paid baggage applicable range to determine whether the baggage to be processed is within the applicable range to obtain range checking results; obtaining baggage follow-up rules of the changed flight, checking whether the changed flight allows the baggage to be processed to be changed for free follow-up, and obtaining rule checking results; determining whether the baggage to be processed meets the change requirements based on the consistency checking results, the state checking results, the range checking results and the rule checking results.

3. The method of claim 1, wherein, Before obtaining the target change task to be processed from the follow-up failure processing queue of pre-paid baggage, the method further comprises the following steps: monitoring user flight change, and in the case that a user has flight change, determining whether the changed user purchases pre-paid baggage; in the case that the changed user purchases pre-paid baggage, obtaining pre-paid baggage follow-up of the changed user from the passenger service system; in the case that the passenger service system returns follow-up failure, creating a change task for the pre-paid baggage of the changed user and adding the change task to the follow-up failure processing queue.

4. The method of claim 1, wherein, The step of matching the baggage information with the baggage transportation price information comprises the following steps: traversing baggage transportation price packages in the baggage transportation price information, and extracting baggage price, baggage size and baggage weight from the baggage transportation price packages; correspondingly matching baggage price, baggage size and baggage weight in the baggage information with baggage price, baggage size and baggage weight in the baggage transportation price packages.

5. The method of claim 1, wherein, If the baggage information matches any baggage fare package in the baggage fare information, the steps for automatically transferring the pending baggage to the changed flight include: If the baggage information and any baggage fare package in the baggage fare information are successfully matched, the ticketing interface of the changed flight is invoked, and the matched baggage fare package is purchased from the ticketing system through the ticketing interface; Upon successful purchase of the baggage fare package, change information is generated, and the status of the baggage to be processed is updated to a successful change status. The change information and the successful change status of the pending baggage will be returned to the user.

6. The method of claim 1, wherein, After matching the baggage information with the baggage fare information, the process also includes: If the baggage information fails to match any baggage fare packages in the baggage fare information, a notification of baggage following failure and the baggage fare information of the changed flight will be sent to the user's terminal. Receive manual change information from the user terminal, and calculate the change fee for the baggage to be processed based on the manual change information; Based on the manual change information and the change fee, a change request is generated, and the ticketing interface is called based on the change request. The baggage fare package selected by the user is purchased from the ticketing system through the ticketing interface. If the purchase is successful, the change information of the baggage to be processed is generated, and the status of the baggage to be processed is updated to the change successful status. The change information and the successful change status of the pending baggage are returned to the user's terminal.

7. The method of claim 6, wherein, After purchasing the baggage fare package selected by the user from the ticketing system through the ticketing interface, the process also includes: In case of purchase failure, invoke the payment interface; By accessing the payment system through the payment interface, the payment fee for the pending baggage can be refunded to the user.

8. A pre-paid baggage change apparatus characterized by comprising: include: The acquisition unit is used to acquire the target change task to be processed from the follow failure processing queue of prepaid baggage, wherein the follow failure processing queue stores all change tasks corresponding to prepaid baggage that have failed to follow based on the passenger service system. The verification unit is used to obtain the baggage information of the baggage to be processed and the user flight information corresponding to the baggage to be processed based on the target change task, and to verify the baggage to be processed based on the baggage information and the user flight information to determine whether the baggage to be processed meets the change requirements. The query unit is used to call the ticket search interface based on the user's flight information to query the baggage fare information of the changed flight when the baggage to be processed meets the change requirements. The change unit is used to match the baggage information with the baggage fare information. If the baggage information and any baggage fare package in the baggage fare information are successfully matched, the baggage to be processed is automatically changed to the changed flight.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored computer program, wherein, when the computer program is executed, it controls the device on which the computer-readable storage medium is located to perform the prepaid baggage change method according to any one of claims 1 to 7.

10. An electronic device, comprising: It includes one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to implement the method for changing prepaid baggage as described in any one of claims 1 to 7.

Images