Flight changing method and device, computer program product and electronic equipment

Abstract

The invention discloses a flight changing method and device, a computer program product and electronic equipment. The method relates to the field of civil aviation information or other related fields, and comprises the following steps: receiving a flight change request sent by a target user through a client, and verifying the flight change request to obtain a verification result; under the condition that the verification result represents that the target user is allowed to carry out flight change, destination updating information is extracted from the flight change request; calculating a change amount according to the destination update information, and sending the change amount to the client; under the condition that a flight reservation request sent by the client side is received, a passenger ticket changing order is generated, the historical passenger ticket is subjected to withdraw operation, and the flight reservation request is used for indicating that the target user completes payment of the changing amount. According to the invention, the method solves a problem that the operation steps are tedious when a passenger changes the destination of a flight and needs to refund the flight.

Description

Technical Field

[0001] The present application relates to the field of civil aviation information or other related fields, and specifically, to a flight change method, device, computer program product, and electronic device. Background Art

[0002] The prosperity of the civil aviation market is closely related to passengers' travel needs, economic affordability and travel schedule. In a highly dynamic market environment, passengers may need to change the travel time or destination of the purchased tickets due to unforeseen factors, such as personal plan adjustments, weather changes, flight cancellations, etc. However, ticket rescheduling services are usually limited to adjusting the departure date of the booked flight, and do not involve changes in the destination. When passengers face the need to change their itinerary, especially when they need to change their destination, the traditional way of handling it is to refund the original ticket first, and then rebook a flight to the new destination. This process is not only cumbersome and increases the complexity of passengers' operations, but may also incur additional refund fees, affecting the overall travel experience.

[0003] Regarding the related technology, when passengers change the destination of their flight, they need to refund their tickets and then buy them again, which has a cumbersome operation process and no effective solution has been proposed yet. Summary of the invention

[0004] The main purpose of the present application is to provide a flight change method, device, computer program product and electronic device to solve the problem in the related art that when passengers change the destination of a flight, they need to refund the ticket and then buy it again, which has cumbersome operation steps.

[0005] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a flight change method is provided. The method comprises: receiving a flight change request sent by a target user through a client, verifying the flight change request, and obtaining a verification result, wherein the flight change request refers to a request by the target user to adjust the destination of a historical ticket; if the verification result indicates that the target user is allowed to change the flight, extracting the destination update information from the flight change request; calculating the change amount according to the destination update information, and sending the change amount to the client; if a flight booking request sent by the client is received, generating a ticket change order, and performing a refund operation on the historical ticket, wherein the flight booking request is used to indicate that the target user has paid the change amount.

[0006] Furthermore, the flight change request is verified to obtain a verification result including: extracting historical booking information of historical tickets from the flight change request, wherein the historical booking information includes at least one of the following: ticket nature, itinerary type, and passenger type; extracting a change type of the target user from the flight change request, and verifying the historical booking information according to the change type to obtain a verification result, wherein the change type includes a voluntary change type and an involuntary change type.

[0007] Furthermore, the historical booking information is verified according to the change type, and the verification result obtained includes: when the change type is an involuntary change type, the change reason and the first change requirement submitted by the target user are obtained, and the change reason is verified according to the first change requirement, wherein the first change requirement is used to verify the change reason of the target user; when the change reason does not meet the first change requirement, a verification result is generated that the target user is not allowed to change the flight; when the change reason meets the first change requirement or the change type is a voluntary change type, a second change requirement is obtained, and the historical booking information is verified using the second change requirement to obtain a verification result, wherein the second change requirement is used to verify the booking category in the historical booking information.

[0008] Furthermore, the historical booking information is verified using the second change requirement, and the verification result obtained includes: when the historical booking information does not meet the second change requirement, a verification result is generated that does not allow the target user to change the flight; when the historical booking information meets the second change requirement, a verification result is generated that allows the target user to change the flight.

[0009] Furthermore, after sending the change amount to the client, the method also includes: querying the ticket inventory data of the preset change ticket according to the destination update information, wherein the preset change ticket refers to the ticket generated after the destination is changed; obtaining the ticket threshold, and generating a first prompt message when the ticket inventory data is lower than the ticket threshold, wherein the first prompt message is used to prompt the target user that the change has failed; when the ticket inventory data is higher than the ticket threshold, determining the refund amount according to the historical booking information, generating a refund prompt message based on the refund amount, and sending the refund prompt message to the client, wherein the target user generates flight confirmation information after comparing the refund amount and the change amount, and the flight confirmation information is used to indicate that the target user agrees to perform the flight change operation; upon receiving the flight confirmation information sent by the target user, generating a ticket booking order according to the change amount, and sending the ticket booking order to the client.

[0010] Furthermore, after sending the changed amount to the client, the method also includes: identifying the order payment status of the target user, wherein the order payment status includes paid, unpaid, and payment canceled; when the order payment status is unpaid or payment canceled, deleting the ticket booking order, wherein the ticket booking order is generated based on the changed amount; and when the order payment status is paid, receiving a flight booking request.

[0011] Furthermore, after generating the change ticket order, the method also includes: determining whether to generate a change ticket associated with the change ticket order; and in the event that the change ticket generation fails, sending a second prompt message to the client, wherein the second prompt message is used to prompt the target user to re-initiate a flight booking request.

[0012] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a flight change device is provided. The device includes: a first receiving unit, which is used to receive a flight change request sent by a target user through a client, verify the flight change request, and obtain a verification result, wherein the flight change request refers to a request by the target user to adjust the destination of a historical ticket; an extraction unit, which is used to extract the destination update information from the flight change request when the verification result indicates that the target user is allowed to change the flight; a calculation unit, which is used to calculate the change amount according to the destination update information and send the change amount to the client; a first generation unit, which is used to generate a ticket change order when receiving a flight booking request sent by the client, and perform a refund operation on the historical ticket, wherein the flight booking request is used to indicate that the target user has paid the change amount.

[0013] According to another aspect of an embodiment of the present invention, a computer storage medium is provided. The computer storage medium is used to store a program. When the program is executed, the device where the computer storage medium is located is controlled to execute a flight change method.

[0014] According to another aspect of an embodiment of the present invention, there is also provided an electronic device comprising one or more processors and a memory; the memory stores computer-readable instructions, and the processor is used to execute the computer-readable instructions, wherein a flight change method is executed when the computer-readable instructions are executed.

[0015] According to another aspect of an embodiment of the present invention, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, a flight changing method is performed.

[0016] Through the present application, the following steps are adopted: receiving a flight change request sent by a target user through a client, verifying the flight change request, and obtaining a verification result, wherein the flight change request refers to a request by the target user to adjust the destination of a historical ticket; when the verification result indicates that the target user is allowed to change the flight, extracting the destination update information from the flight change request; calculating the change amount according to the destination update information, and sending the change amount to the client; when receiving a flight booking request sent by the client, generating a ticket change order, and performing a refund operation on the historical ticket, wherein the flight booking request is used to indicate that the target user has paid the change amount, solving the problem of complicated operation steps in the related art that when a passenger changes the destination of a flight, the ticket needs to be refunded and repurchased, and the flight change request sent by the target user is verified to obtain a verification result, when the verification result indicates that the target user is allowed to change the flight, extracting the destination update information from the flight change request, and calculating the change amount based on the destination update information, when receiving the flight booking request sent by the client, generating a ticket change order, and performing a refund operation on the historical ticket, thereby achieving the effect of simplifying the flight change process, improving change efficiency, and improving passenger satisfaction and experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings constituting a part of the present application are used to provide a further understanding of the present application. The illustrative embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0018] Figure 1 is a flow chart of a flight change method provided according to an embodiment of the present application;

[0019] Figure 2 is a schematic diagram of an optional flight change system provided according to an embodiment of the present application;

[0020] Figure 3 is a schematic diagram of an optional flight change method provided according to an embodiment of the present application;

[0021] Figure 4 is a schematic diagram of a flight change device provided according to an embodiment of the present application;

[0022] Figure 5 is a schematic diagram of an electronic device provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0023] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0024] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0025] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0026] 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 for display, data for analysis, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties. For example, an interface is set between this system and the relevant user or organization. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or organization through the interface, and obtain relevant information after receiving the consent information fed back by the aforementioned user or organization.

[0027] It should be noted that the collected information used in this application is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with the relevant laws, regulations and standards of the relevant regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse to use it.

[0028] The present invention is described below in conjunction with preferred implementation steps. Figure 1 is a flow chart of a flight change method provided in accordance with an embodiment of the present application, such as Figure 1 As shown, the method comprises the following steps:

[0029] Step S101, receiving a flight change request sent by a target user through a client, verifying the flight change request, and obtaining a verification result, wherein the flight change request refers to a request by the target user to adjust the destination of a historical ticket.

[0030] Specifically, the target user refers to a passenger who needs to change the flight destination. When the passenger's personal itinerary changes or is affected by external force majeure factors, such as weather changes, flight cancellations, etc., resulting in the need to change the destination in the purchased itinerary, in order to enhance the passenger's travel experience, the target user can submit a flight change request through the client. When receiving the flight change request sent by the client, the received request is parsed to obtain key information, such as the passenger's identity, flight information of the original itinerary (departure place, destination, flight date, cabin class, etc.), the destination to be changed, the expected change date, etc. Then the flight change request is verified to obtain the verification result, for example, checking the passenger's identity information to ensure that it is consistent with the information on the original ticket to avoid subsequent problems caused by inconsistent information; checking the status of the original flight, including whether it has taken off, whether there are involuntary change factors (such as flight cancellations, delays), etc.; evaluating whether there are available flights for the destination and date to be changed.

[0031] Step S102: if the verification result indicates that the target user is allowed to change the flight, extract the destination update information from the flight change request.

[0032] Specifically, firstly, the destination update information is accurately extracted from the flight change request, and other key parameters in the flight change request are parsed. For example, the parameters may include the desired departure date, time, cabin type, and special needs of passengers (such as unaccompanied children services, etc.) to ensure that the new flight matches the passenger's request.

[0033] Furthermore, based on the extracted destination update information, flights can be queried to obtain a list of flights that meet the change requirements and the availability of corresponding seats. Then, through intelligent algorithms, such as giving priority to flights with similar time to the original flight or filtering the best flight options based on passenger preferences.

[0034] Step S103, calculating the changed amount according to the destination update information, and sending the changed amount to the client.

[0035] Specifically, in order to ensure that passengers can quickly understand the cost changes caused by the destination adjustment after submitting a change request, after extracting the destination update information, the change amount that the passenger needs to pay after the change can be calculated based on the flight corresponding to the changed destination, and then send detailed cost breakdown information containing the change amount to the client, including fare differences, tax changes, possible rescheduling fees and refund fees, etc., so that passengers can understand the cost structure. When the passenger confirms the change amount and agrees to the change conditions, the passenger can be helped to complete the creation of the change request.

[0036] Step S104, upon receiving the flight booking request sent by the client, a ticket change order is generated, and a refund operation is performed on the historical ticket, wherein the flight booking request is used to indicate that the target user has paid the change amount.

[0037] Specifically, after the target user completes the payment of the change amount for the destination change through a mobile application or other booking platform, the received flight booking request can be parsed to extract information such as the passenger's identity, original flight information, new flight information, and payment details, and then the received payment details can be verified. Once the payment verification is successful, the status of the original flight booking request can be updated to "change payment completed", which indicates that the passenger has fulfilled the payment obligation and can start processing the change request, that is, generating a change ticket order based on the new flight information, wherein the order contains the target user's changed travel arrangements, including the departure place, new destination, flight date, cabin class and other detailed information, and the order number and PNR (Passenger Name Record) can be set for the order. PNR can record passenger information and flight details in detail to ensure the accuracy of subsequent services and operations. At the same time, in order to complete the flight change, it is also necessary to apply for a refund for the historical ticket, that is, to update the status of the historical ticket to "refund pending", and return the refund amount to the passenger's account.

[0038] In addition, in order to improve the passenger service experience, after the new ticket is successfully issued and the refund of the historical ticket is completed, a notification can be sent to the passenger via SMS or email to inform the passenger of the changed itinerary details, the new ticket number, the specific refund amount and the estimated arrival time, so as to improve passenger satisfaction.

[0039] The flight change method provided in the embodiment of the present application receives a flight change request sent by a target user through a client, verifies the flight change request, and obtains a verification result, wherein the flight change request refers to a request by the target user to adjust the destination of a historical ticket; when the verification result indicates that the target user is allowed to change the flight, extracts the destination update information from the flight change request; calculates the change amount according to the destination update information, and sends the change amount to the client; when a flight booking request sent by the client is received, generates a ticket change order, and performs a refund operation on the historical ticket, wherein the flight booking request is used to indicate that the target user has paid the change amount, which solves the problem of complicated operation steps in the related art that when a passenger changes the destination of a flight, the ticket needs to be refunded and repurchased. The flight change request sent by the target user is verified to obtain a verification result. When the verification result indicates that the target user is allowed to change the flight, the destination update information is extracted from the flight change request, and the change amount is calculated based on the destination update information. When the flight booking request sent by the client is received, a ticket change order is generated, and a refund operation is performed on the historical ticket, thereby achieving the effect of simplifying the flight change process, improving change efficiency, and improving passenger satisfaction and experience.

[0040] In order to ensure the rationality and feasibility of the flight change request, optionally, in the flight change method provided in the embodiment of the present application, the flight change request is verified, and the verification result obtained includes: extracting historical booking information of historical tickets from the flight change request, wherein the historical booking information includes at least one of the following: ticket nature, itinerary type and passenger type; extracting the change type of the target user from the flight change request, and verifying the historical booking information according to the change type to obtain a verification result, wherein the change type includes a voluntary change type and an involuntary change type.

[0041] Specifically, when a passenger submits a flight change request through the client, it is first necessary to accurately extract historical booking information and the change type of the target user from the request. The historical booking information can be the nature of the ticket, the itinerary type (one-way, round-trip, transfer or connecting) and the passenger type (adult, child or infant); the change type includes voluntary change type and involuntary change type. If the original flight is unable to travel as planned due to airline reasons (such as flight cancellation, serious delay), it is an involuntary change. If the passenger actively proposes a change for personal reasons (such as itinerary adjustment, health problems), it is a voluntary change. Based on this information, the basic attributes of the change request can be quickly determined to provide support for subsequent process decisions.

[0042] The change type can be further used to verify the historical booking information. For example, for voluntary changes, it is necessary to verify the relationship between the change time and the flight departure time to determine whether a specific rebooking fee is applicable. It is also necessary to verify whether the itinerary type supports destination change and whether the passenger type complies with the change policy. In the case of involuntary changes, it is necessary to verify whether there is indeed a flight operation problem, whether the passenger has received a flight adjustment notification, and whether the change request is submitted within the involuntary change time limit specified by the airline. In this way, a verification result is generated, wherein the verification result includes whether the change conditions are met, the applicable change policy, possible fees or refunds, and any specific restrictions or requirements. This embodiment can timely and accurately evaluate the passenger's change request by accurately extracting historical booking information from the flight change request and verifying the change type, reducing unnecessary waiting time and communication costs, enabling passengers to quickly understand the feasibility and cost of the change. At the same time, through early verification, possible flight change risks, such as insufficient seat inventory and mismatched cabin classes, can be identified and handled, thereby reducing operational risks caused by changes.

[0043] Optionally, in the flight change method provided in an embodiment of the present application, the historical booking information is verified according to the change type, and the verification result obtained includes: when the change type is an involuntary change type, obtaining the change reason and the first change requirement submitted by the target user, and verifying the change reason according to the first change requirement, wherein the first change requirement is used to verify the change reason of the target user; when the change reason does not meet the first change requirement, generating a verification result that does not allow the target user to change the flight; when the change reason meets the first change requirement, or the change type is a voluntary change type, obtaining the second change requirement, and using the second change requirement to verify the historical booking information to obtain a verification result, wherein the second change requirement is used to verify the booking category in the historical booking information.

[0044] Specifically, when verifying historical booking information, when the change request belongs to the involuntary change type, it is first necessary to obtain the reason for the change from the passenger. The reason for the change can be flight cancellation, delay, weather conditions, health reasons, equipment failure, etc., and then after obtaining the first change request including the involuntary change policy, passenger rights protection clauses, and applicable conditions in specific circumstances, the reason for the change is verified according to the first change request. For example, involuntary changes caused by flight cancellation or delay can be proposed within a certain range of the original scheduled departure time of the flight.

[0045] If the reason for the change provided by the passenger cannot meet the first change requirement, a verification result that does not allow the flight change is generated, and a detailed explanation message needs to be sent to the passenger through the client, and possible alternatives or suggestions are provided, such as converting to a voluntary change. After the reason for the change meets the first change requirement, the historical booking information is required for further verification. At this time, the second change requirement for the booking category in the historical booking information can be obtained, and the booking details can be verified using this requirement to ensure that the changed flight can still meet the specific needs of the passenger, such as one-way or round-trip, flight cabin class, passenger type (adult, child, infant), and whether special services or additional products are included. For example, for passengers who have booked special services (such as unaccompanied children services), it is necessary to ensure that the new flight can provide corresponding services. This embodiment identifies and verifies involuntary change requests to ensure that passengers can obtain flight change services in a timely manner when facing force majeure factors, avoid travel inconveniences caused by flight problems, reduce the error rate of manual intervention, improve the efficiency and accuracy of flight change processing, and shorten passenger waiting time.

[0046] Optionally, in the flight change method provided in an embodiment of the present application, the historical booking information is verified using the second change requirement, and the verification result obtained includes: when the historical booking information does not meet the second change requirement, generating a verification result that does not allow the target user to change the flight; when the historical booking information meets the second change requirement, generating a verification result that allows the target user to change the flight.

[0047] Specifically, when processing a flight change request, it is also necessary to verify the historical booking information to determine whether the request meets the change conditions specified by the airline, and then decide whether to allow the passenger to change the flight. That is, after extracting the historical booking information from the flight change request, the information is verified according to the second change requirement to determine whether the change requirements are met: first check the nature of the ticket (domestic or international), the type of itinerary (one-way, round-trip, transfer or connecting) and the type of passenger (adult, child, infant), and determine whether this information complies with the voluntary change policy. For example, Airline A does not allow infants or unaccompanied children to change their destinations, or only allows voluntary changes for specific types of tickets.

[0048] If any item in the historical booking information does not meet the second change requirement, a verification result is generated that does not allow the target user to change the flight, and it is pointed out which services or conditions cannot be met in the new flight, and remedial measures are provided to the passenger, such as canceling special services that cannot be replaced. For example, if a passenger wants to change the destination, but the type of ticket does not allow voluntary change of destination, the passenger needs to be informed that the change is not feasible and explain the reason; when the historical booking information fully meets the change conditions, a verification result can be generated that allows the target user to change the flight, and the result can also include the specific policy of the change, the possible costs, and any details that the passenger needs to pay attention to. This embodiment helps to improve the overall passenger service experience by verifying the historical booking information. By verifying the feasibility of the change in advance, it can avoid unnecessary resource occupation, such as unnecessary consumption of invalid flight seat reservations, etc., thereby improving operational efficiency and reducing the risk of operational errors.

[0049] In order to meet the needs of passengers, optionally, in the flight change method provided in the embodiment of the present application, after sending the change amount to the client, the method also includes: querying the ticket inventory data of the preset change ticket according to the destination update information, wherein the preset change ticket refers to the ticket generated after the destination is changed; obtaining the ticket threshold, and when the ticket inventory data is lower than the ticket threshold, generating a first prompt message, wherein the first prompt message is used to prompt the target user that the change has failed; when the ticket inventory data is higher than the ticket threshold, determining the refund amount according to the historical booking information, generating a refund prompt message based on the refund amount, and sending the refund prompt message to the client, wherein the target user generates flight confirmation information after comparing the refund amount and the change amount, and the flight confirmation information is used to indicate that the target user agrees to perform the flight change operation; when the flight confirmation information sent by the target user is received, generating a ticket booking order according to the change amount, and sending the ticket booking order to the client.

[0050] Specifically, when the target user makes a flight change request including updated destination information, the inventory data of the preset changed tickets is first queried through the booking system based on the updated destination and expected departure date. If the inventory data is lower than the preset ticket threshold, it means that the change has failed. At this time, the first prompt information can be generated, and alternative solutions or suggestions can be provided to the passenger, such as changing to another date. If the query result shows that the ticket inventory data is higher than the ticket threshold, that is, the inventory is sufficient, the refund amount that the passenger needs to bear due to the flight change can be calculated based on the original flight details and refund and change policies in the historical booking information, and a refund prompt information is generated after the calculation is completed, detailing the refund amount, cost composition, and comparison with the change amount. At the same time, the refund prompt information is displayed to the passenger through the client to help the passenger intuitively understand the change situation and make a more optimal decision.

[0051] After receiving the refund prompt information, the passenger can compare and analyze the refund amount and the change amount. When the passenger agrees to the flight change operation and confirms that the cost change caused by the change of destination is acceptable, the flight confirmation information sent by the passenger can be received at this time, and a ticket booking order containing the changed new flight information, passenger details, cost details and other data can be generated based on the change amount. The ticket booking order is displayed to the passenger through the client, and subsequent steps such as order confirmation and payment processing are provided to ensure the transparency and smoothness of the change process. This embodiment ensures the immediate feasibility of the change and the accuracy of passenger information through real-time query of inventory data, simplifies the passenger operation process, improves the efficiency of change processing, and enhances passenger satisfaction.

[0052] In order to ensure the smooth progress of the change process, optionally, in the flight change method provided in the embodiment of the present application, after sending the change amount to the client, the method also includes: identifying the order payment status of the target user, wherein the order payment status includes paid, unpaid and payment canceled; when the order payment status is unpaid or payment canceled, deleting the ticket booking order, wherein the ticket booking order is generated according to the change amount; when the order payment status is paid, receiving a flight booking request.

[0053] Specifically, in order to ensure financial security, it is necessary to identify the order payment status of the target user in real time after sending the change amount to the client to avoid invalid orders occupying resources, that is, to determine whether the passenger has paid the change amount. When the passenger has successfully paid, the passenger is allowed to perform flight booking operations after confirming the payment status, such as seat confirmation, generating a new PNR, etc., to ensure that the passenger can change flights smoothly. If the passenger has submitted a change request but has not completed the payment, the order needs to be kept in the ready state, but the flight seat is not reserved to avoid waste of resources; when the passenger chooses to cancel the payment, the preset change ticket booking order needs to be deleted at this time to release the occupied flight seat resources for other passengers to book. This embodiment can quickly release flight seat resources, avoid invalid occupation of resources, and improve seat utilization by monitoring the order payment status in real time and taking corresponding processing strategies. For paid orders, it can quickly respond to passengers' flight booking requests and improve passengers' service satisfaction.

[0054] Optionally, in the flight change method provided in an embodiment of the present application, after generating a change ticket order, the method also includes: determining whether to generate a change ticket associated with the change ticket order; in case the change ticket generation fails, sending a second prompt message to the client, wherein the second prompt message is used to prompt the target user to re-initiate the flight booking request.

[0055] Specifically, after generating a change ticket order, that is, after the passenger confirms the flight change operation, in order to ensure the effective management of flight resources, a change ticket order can be generated based on the new flight information selected by the passenger (including departure place, new destination, departure date, cabin class, passenger information, etc.), that is, the passenger's PNR record is generated or updated according to the new flight information to ensure that the complete information of the new order is accurately recorded, and at the same time, the key information of the original order is retained in the PNR to facilitate subsequent refund processing and customer service.

[0056] When generating a change ticket order, it is necessary to lock the seat of the new flight. If a problem occurs during the generation of the change ticket order, resulting in a failure to generate the change ticket, such as due to full seats, system failure, or failure to verify passenger information, it is necessary to promptly send a second prompt message to the client to explain the reason for the change failure, and provide guidance information to the passenger, such as re-initiating a flight reservation request. This embodiment verifies the change ticket and helps passengers quickly adjust their plans through instant feedback, thereby avoiding travel delays caused by failed changes, ensuring the reasonable allocation of flight resources, and improving the passenger service experience.

[0057] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0058] The present application also provides a flight change system, which can be used to execute the optional flight change method provided in the present application. Figure 2 is a schematic diagram of an optional flight change system provided according to an embodiment of the present application, Figure 3 is a schematic diagram of an optional flight change method provided according to an embodiment of the present application, such as Figure 2 , Figure 3 As shown, the system includes:

[0059] When a passenger logs in to the airline sales platform of the airline's e-commerce system and decides to reschedule and wants to change the destination, the passenger needs to enter the departure place, new destination, desired departure date, and whether the destination change is involuntary. At this time, the rescheduling condition restriction module in the airline's e-commerce information processing platform makes a basic judgment on the rescheduling condition restriction based on the passenger's selected rescheduling type, that is, it needs to judge whether the passenger and itinerary type selected by the passenger meet the involuntary change of destination conditions, such as no unaccompanied children and infants, no unrefundable additional products, etc. When the passenger changes the destination voluntarily, he can directly enter the rescheduling flight query page; if the passenger changes the destination involuntarily, he can judge whether the ticket meets the involuntary change conditions according to the involuntary change rules. If it meets the involuntary change rules, he can enter the rescheduling flight query page, otherwise an error prompt will be reported and the process will end.

[0060] When passengers are allowed to change their destinations, they first enter their new destination. At this time, the system can query through the "Civil Aviation Reservation System" interface and provide query results of a list of flights that meet the conditions. At this time, passengers can select new flights and cabins in the query results, and can also view the amount to be paid for rescheduling the new flight and the amount that can be refunded for the original flight. It should be noted that the above amount needs to be calculated by the rescheduling fee calculation module in the airline's e-commerce information processing platform. This module can calculate the rescheduling fee for voluntary or involuntary change of destination based on the passenger's choice and the information provided by the "Freight Inquiry System".

[0061] After the passenger compares and analyzes the amount to be paid for the new flight and the refundable amount of the original flight and agrees to make the change, he or she can book a new flight based on the flight selected by the passenger, that is, enter the new ticket booking process. At this time, it is also necessary to verify whether the changed flight has seats. If there are seats, a new order and PNR will be generated. At the same time, the rescheduling fee will be recorded in the original itinerary order as the refund fee for the original order, which indicates the production of a new ticket order; if there are no seats, it means that the booking has failed and an error needs to be reported to the passenger.

[0062] After generating the order and PNR for the new ticket, you need to update the sales report in the "Report Module" to record the booking information of the new ticket. In the original ticket processing module, the original ticket is marked as "changing". According to the rescheduling type (voluntary or involuntary), the system calculates the refund fee and indicates it in the original order, and updates the refund report at the same time.

[0063] If the passenger cancels payment manually or the system fails to pay, the process ends; after the passenger confirms payment of the rescheduling fee, the passenger order is processed through the "New Ticket Processing" and "Original Ticket Processing" modules, and the new ticket is issued using the "New Ticket Processing" module. If the ticket is issued successfully, the "Original Ticket Processing" module will apply for a refund of the original ticket; if the ticket fails, such as K-seat guarantee or ticket failure guarantee, the guarantee mechanism module can be triggered at this time to notify the passenger and the airline's guarantee personnel via SMS and email, and provide order cancellation and error refund functions, and apply for a refund of the original ticket to ensure that the rights and interests of the passengers are not harmed.

[0064] After the new ticket is successfully issued, the system notifies the passenger of the successful ticket issuance and updates the sales report in the "Report Module". At this time, the "Original Ticket Processing" module will complete the rescheduling review of the original ticket and send a refund success notification to the passenger. After the entire process is completed, the passenger will receive the PNR information of the new ticket and the refund details of the original ticket, ensuring that the passenger has a clear understanding of the entire change process.

[0065] This embodiment ensures the accuracy of flight inquiries, the fairness of rescheduling fee calculations, the efficiency of handling new and old tickets, and the reliability of the guarantee mechanism through interaction among various modules, while reducing the inconvenience and costs caused to passengers by changing their destinations and improving operational efficiency.

[0066] The present application also provides a flight change device. It should be noted that the flight change device of the present application can be used to execute the flight change method provided by the present application. The flight change device provided by the present application is introduced below.

[0067] Figure 4 is a schematic diagram of a flight change device provided according to an embodiment of the present application, such as Figure 4 As shown, the device includes: a first receiving unit 40, an extracting unit 41, a calculating unit 42, and a first generating unit 43.

[0068] The first receiving unit 40 is used to receive a flight change request sent by a target user through a client, verify the flight change request, and obtain a verification result, wherein the flight change request refers to a request by the target user to adjust the destination of a historical ticket;

[0069] An extraction unit 41 is used to extract the destination update information from the flight change request when the verification result indicates that the target user is allowed to change the flight;

[0070] A calculation unit 42, configured to calculate a change amount according to the destination update information, and send the change amount to the client;

[0071] The first generating unit 43 is used to generate a ticket change order and perform a refund operation on the historical ticket when receiving a flight booking request sent by the client, wherein the flight booking request is used to indicate that the target user has paid the change amount.

[0072] The flight change device provided in the embodiment of the present application receives a flight change request sent by a target user through a client through a first receiving unit 40, verifies the flight change request, and obtains a verification result, wherein the flight change request refers to a request by the target user to adjust the destination of a historical ticket; the extraction unit 41 extracts the destination update information from the flight change request when the verification result indicates that the target user is allowed to change the flight; the calculation unit 42 calculates the change amount according to the destination update information and sends the change amount to the client; the first generation unit 43 generates a ticket change order when receiving a flight booking request sent by the client, and performs a refund operation on the historical ticket The flight booking request is used to indicate that the target user has paid the change amount, which solves the problem in the related art that when passengers change the destination of the flight, they need to refund the ticket and then buy it again, which has complicated operation steps. The flight change request sent by the target user is verified to obtain the verification result. When the verification result indicates that the target user is allowed to change the flight, the destination update information is extracted from the flight change request, and the change amount is calculated based on the destination update information. When the flight booking request sent by the client is received, a ticket change order is generated, and a refund operation is performed on the historical ticket, thereby simplifying the flight change process, improving the change efficiency, and improving passenger satisfaction and experience.

[0073] Optionally, in the flight change device provided in the embodiment of the present application, the first receiving unit 40 includes: a first extraction module, used to extract historical booking information of historical tickets from the flight change request, wherein the historical booking information includes at least one of the following: ticket nature, itinerary type and passenger type; a second extraction module, used to extract the change type of the target user from the flight change request, verify the historical booking information according to the change type, and obtain a verification result, wherein the change type includes a voluntary change type and an involuntary change type.

[0074] Optionally, in the flight change device provided in the embodiment of the present application, the first receiving unit 40 includes: a first acquisition module, which is used to obtain the change reason and the first change requirement submitted by the target user when the change type is an involuntary change type, and verify the change reason according to the first change requirement, wherein the first change requirement is used to verify the change reason of the target user; a first generation module, which is used to generate a verification result that does not allow the target user to change the flight when the change reason does not meet the first change requirement; a second acquisition module, which is used to obtain the second change requirement when the change reason meets the first change requirement or the change type is a voluntary change type, and use the second change requirement to verify the historical booking information to obtain a verification result, wherein the second change requirement is used to verify the booking category in the historical booking information.

[0075] Optionally, in the flight change device provided in an embodiment of the present application, the first receiving unit 40 includes: a second generating module, used to generate a verification result that does not allow the target user to change the flight when the historical booking information does not meet the second change requirement; a third generating module, used to generate a verification result that allows the target user to change the flight when the historical booking information meets the second change requirement.

[0076] Optionally, in the flight change device provided in the embodiment of the present application, the device also includes: a query unit, which is used to query the ticket inventory data of the preset change ticket according to the destination update information after sending the change amount to the client, wherein the preset change ticket refers to the ticket generated after the destination is changed; an acquisition unit, which is used to obtain the ticket threshold, and generate a first prompt message when the ticket inventory data is lower than the ticket threshold, wherein the first prompt message is used to prompt the target user that the change has failed; a determination unit, which is used to determine the refund amount according to the historical booking information when the ticket inventory data is higher than the ticket threshold, generate the refund prompt information from the refund amount, and send the refund prompt information to the client, wherein the target user generates flight confirmation information after comparing the refund amount and the change amount, and the flight confirmation information is used to indicate that the target user agrees to perform the flight change operation; a second generation unit, which is used to generate a ticket booking order according to the change amount when receiving the flight confirmation information sent by the target user, and send the ticket booking order to the client.

[0077] Optionally, in the flight change device provided in the embodiment of the present application, the device also includes: an identification unit, used to identify the order payment status of the target user after the change amount is sent to the client, wherein the order payment status includes paid, unpaid and payment canceled; a deletion unit, used to delete the ticket booking order when the order payment status is unpaid or payment canceled, wherein the ticket booking order is generated based on the change amount; a second receiving unit, used to receive a flight booking request when the order payment status is paid.

[0078] Optionally, in the flight change device provided in the embodiment of the present application, the device also includes: a judgment unit, used to judge whether to generate a change ticket associated with the change ticket order after generating a change ticket order; a sending unit, used to send a second prompt message to the client when the change ticket generation fails, wherein the second prompt message is used to prompt the target user to re-initiate the flight booking request.

[0079] The flight change device includes a processor and a memory. The first receiving unit 40, extraction unit 41, calculation unit 42, first generation unit 43, etc. are all stored in the memory as program units, and the processor executes the program units stored in the memory to implement corresponding functions.

[0080] The processor includes a kernel, which retrieves the corresponding program unit from the memory. One or more kernels can be set, and the kernel parameters can be adjusted to solve the problem in the related art that when passengers change the destination of the flight, they need to refund the ticket and then buy it again, which has cumbersome operation steps.

[0081] The memory may include non-permanent memory in a computer-readable medium, 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.

[0082] An embodiment of the present invention provides a computer storage medium, which is used to store a program. When the program is running, the device where the computer storage medium is located is controlled to execute a flight change method.

[0083] Figure 5 is a schematic diagram of an electronic device provided according to an embodiment of the present application, such as Figure 5 As shown, an embodiment of the present invention provides an electronic device, the electronic device 50 includes a processor, a memory, and a program stored in the memory and executable on the processor, the processor is used to execute computer-readable instructions, wherein the computer-readable instructions execute a flight change method when executed. The device in this article can be a server, a PC, a PAD, a mobile phone, etc.

[0084] The present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of a flight change method in each embodiment of the present application.

[0085] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0086] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0087] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0088] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0089] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0090] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0091] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0092] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0093] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A flight change method, characterized in that: include: Receiving a flight change request sent by a target user through a client, verifying the flight change request, and obtaining a verification result, wherein the flight change request refers to a request by the target user to adjust the destination of a historical ticket; If the verification result indicates that the target user is allowed to change the flight, extracting the destination update information from the flight change request; Calculate the change amount according to the destination update information, and send the change amount to the client; When receiving the flight booking request sent by the client, a ticket change order is generated, and a refund operation is performed on the historical ticket, wherein the flight booking request is used to instruct the target user to pay the change amount.

2. The method according to claim 1, characterized in that: The flight change request is verified, and the verification results include: Extracting historical booking information of the historical ticket from the flight change request, wherein the historical booking information includes at least one of the following: ticket nature, itinerary type, and passenger type; The change type of the target user is extracted from the flight change request, and the historical booking information is verified according to the change type to obtain the verification result, wherein the change type includes a voluntary change type and an involuntary change type.

3. The method according to claim 2, characterized in that The historical booking information is verified according to the change type, and the verification result obtained includes: In a case where the change type is the involuntary change type, obtaining a change reason and a first change requirement submitted by the target user, and verifying the change reason according to the first change requirement, wherein the first change requirement is used to verify the change reason of the target user; If the change reason does not meet the first change requirement, generating a verification result that does not allow the target user to change the flight; When the change reason satisfies the first change requirement or the change type is the voluntary change type, a second change requirement is obtained, and the historical booking information is verified using the second change requirement to obtain the verification result, wherein the second change requirement is used to verify the booking category in the historical booking information.

4. The method according to claim 3, characterized in that: The historical booking information is verified using the second change request, and the verification result obtained includes: If the historical booking information does not meet the second change requirement, generating a verification result that does not allow the target user to change the flight; In a case where the historical booking information meets the second change requirement, a verification result is generated that allows the target user to change the flight.

5. The method according to claim 1, characterized in that After sending the changed amount to the client, the method further includes: querying the ticket inventory data of the preset changed ticket according to the destination update information, wherein the preset changed ticket refers to the ticket generated after the destination is changed; Acquire a ticket threshold, and generate a first prompt message when the ticket inventory data is lower than the ticket threshold, wherein the first prompt message is used to prompt the target user that the change fails; In the case that the ticket inventory data is higher than the ticket threshold, a refund amount is determined according to historical booking information, refund prompt information is generated from the refund amount, and the refund prompt information is sent to the client, wherein the target user generates flight confirmation information after comparing the refund amount with the change amount, and the flight confirmation information is used to indicate that the target user agrees to perform the flight change operation; When the flight confirmation information sent by the target user is received, a ticket booking order is generated according to the change amount, and the ticket booking order is sent to the client.

6. The method according to claim 1, characterized in that After sending the changed amount to the client, the method further includes: Identify the order payment status of the target user, wherein the order payment status includes paid, unpaid, and payment canceled; When the order payment status is the unpaid or the payment is canceled, deleting the ticket booking order, wherein the ticket booking order is generated according to the changed amount; When the order payment status is the paid status, the flight booking request is received.

7. The method according to claim 1, characterized in that After generating the ticket change order, the method further includes: Determining whether to generate a change ticket associated with the change ticket order; In the case where the ticket change generation fails, a second prompt message is sent to the client, wherein the second prompt message is used to prompt the target user to re-initiate the flight booking request.

8. A flight change device, characterized in that: include: a first receiving unit, configured to receive a flight change request sent by a target user through a client, verify the flight change request, and obtain a verification result, wherein the flight change request refers to a request by the target user to adjust the destination of a historical ticket; An extraction unit, configured to extract destination update information from the flight change request if the verification result indicates that the target user is allowed to change the flight; a calculation unit, configured to calculate a change amount according to the destination update information, and send the change amount to the client; The first generating unit is used to generate a ticket change order and perform a refund operation on the historical ticket when receiving a flight booking request sent by the client, wherein the flight booking request is used to instruct the target user to pay the change amount.

9. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the flight changing method according to any one of claims 1 to 7 is implemented.

10. An electronic device, characterized in that: The invention comprises one or more processors and a memory, wherein the memory is 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 implement the flight change method described in any one of claims 1 to 7.

Images