Air ticket resigning method and device, equipment and storage medium

Abstract

The invention relates to an air ticket resigning method and device, equipment and a storage medium, and the method comprises the steps: receiving an air ticket resigning request sent by a user, verifying parameters corresponding to the request, generating a resigning order according to the request if the verification is passed, and sending the resigning order to a price checking system, and sending the request to a price checking system, so that the price checking system judges whether the user is allowed to resign based on the resigning order, if yes, calling a flight interface according to the requested parameters, matching expected flight information corresponding to the resigning order, generating a resigning confirmation order containing a resigning price based on the expected flight information, and feeding back the resigning confirmation order to the user. According to the invention, automatic processing of air ticket modification is realized, manual intervention in the air ticket modification process is greatly reduced, the efficiency and accuracy of modification operation are improved, a large amount of labor cost is saved for airlines, the customer service experience is improved, and the method and the device have good application prospects through a highly automatic and intelligent processing mode. Complex and changeable market requirements can be better met, and diversified ticket returning and changing requirements of passengers are met.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular, to a method, apparatus, device, and storage medium for changing flight tickets. Background Art

[0002] In the modern air transportation industry, the operation of changing flight tickets is an important part of the daily operations of passengers and airlines. Currently, most traditional ticket change processes rely on manual processing, which is not only inefficient but also prone to calculation errors and processing delays, resulting in poor customer experience and increased operating costs for airlines. The method of relying on manual processing for ticket changes can no longer meet the increasingly complex requirements. Especially during peak periods, the large influx of ticket change requests is likely to cause the system to be overloaded, thereby affecting the service quality.

[0003] Therefore, how to provide a technical solution to improve the efficiency of changing flight tickets has become a technical problem that needs to be solved urgently by those skilled in the art. It should be noted that the information disclosed in the above background art section is only used to enhance the understanding of the background of the present disclosure, and thus may include information that does not constitute the prior art known to those of ordinary skill in the art. Summary of the Invention

[0004] In view of the above, this application provides a method, apparatus, device, and storage medium for changing flight tickets, aiming to solve the above technical problems.

[0005] In a first aspect, this application provides a method for changing flight tickets, the method including:

[0006] Receiving a flight ticket change request sent by a user, and verifying the parameters corresponding to the request;

[0007] If the verification passes, generating a ticket change order according to the request;

[0008] Sending the ticket change order to the price verification system for the price verification system to determine whether to allow the user to change the ticket based on the ticket change order;

[0009] If so, calling a flight interface according to the parameters of the request to match the expected flight information corresponding to the ticket change order;

[0010] Generating a ticket change confirmation order including the ticket change price based on the expected flight information and feeding it back to the user.

[0011] In a second aspect, this application provides a flight ticket change apparatus, the apparatus including:

[0012] A verification module: for receiving a flight ticket change request sent by a user and verifying the parameters corresponding to the request;

[0013] The first generation module: If the parameter verification corresponding to the request passes, it is used to generate a rebooking order according to the request.

[0014] The sending module: It is used to send the rebooking order to the price verification system, so that the price verification system can judge whether to allow the user to rebook based on the rebooking order.

[0015] The matching module: If the user is allowed to rebook, it is used to call the flight interface according to the parameters of the request and match the expected flight information corresponding to the rebooking order.

[0016] The second generation module: It is used to generate a rebooking confirmation order including the rebooking price based on the expected flight information and feedback it to the user.

[0017] Thirdly, the present application provides an electronic device, including a processor, a communication interface, a memory and a communication bus. Among them, the processor, the communication interface and the memory complete mutual communication through the communication bus.

[0018] The memory: It is used to store computer programs.

[0019] The processor: When executing the program stored on the memory, it is used to implement the ticket rebooking method described in any embodiment of the first aspect.

[0020] Fourthly, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, it implements the ticket rebooking method described in any embodiment of the first aspect.

[0021] The above technical solutions provided by the embodiments of the present application have the following advantages compared with the prior art:

[0022] The present application receives a ticket rebooking request sent by a user, verifies the parameters corresponding to the request. If the verification passes, it generates a rebooking order according to the request, sends the rebooking order to the price verification system, so that the price verification system can judge whether to allow the user to rebook based on the rebooking order. If so, it calls the flight interface according to the parameters of the request, matches the expected flight information corresponding to the rebooking order, and generates a rebooking confirmation order including the rebooking price based on the expected flight information and feedbacks it to the user. It realizes the automated processing of ticket rebooking, greatly reduces the manual intervention in the ticket rebooking process, improves the efficiency and accuracy of the rebooking operation, saves a large amount of labor costs for the airline, and improves the customer service experience. Through a highly automated and intelligent processing method, it can better respond to complex and changing market demands and meet the diverse refund and rebooking needs of passengers. Description of the Drawings

[0023] The drawings here are incorporated into the specification and form a part of this specification, showing the embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.

[0024] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0025] Figure 1 This is a flow chart of an embodiment of a method for applying for ticket change;

[0026] Figure 2 This is a module diagram of an embodiment of the air ticket change device of the present application;

[0027] Figure 3 A schematic diagram of an electronic device embodiment of the present application;

[0028] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0029] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, 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 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 making creative work are within the scope of protection of this application.

[0030] The disclosure below provides many different embodiments or examples to realize the different structures of the present application. In order to simplify the disclosure of the present application, the parts and settings of specific examples are described below. Of course, they are only examples, and the purpose is not to limit the present application. In addition, the present application can repeat reference numbers and / or letters in different examples. This repetition is for the purpose of simplification and clarity, and does not itself indicate the relationship between the various embodiments and / or settings discussed.

[0031] This application provides a method for changing a flight ticket. Figure 1 The figure is a flow chart of a method of an embodiment of the ticket change method of the present application. The method can be executed by an electronic device, the electronic device runs a ticket change system, and the electronic device is implemented by software and / or hardware. The ticket change method includes:

[0032] Step S10: receiving a ticket change request sent by a user, and verifying parameters corresponding to the request;

[0033] Step S20: if the verification is passed, a change order is generated according to the request;

[0034] Step S30: Send the ticket change order to the price verification system for the price verification system to determine whether to allow the user to change the ticket based on the ticket change order;

[0035] Step S40: If so, call the flight interface according to the parameters of the request to match the expected flight information corresponding to the ticket change order;

[0036] Step S50: Generate a ticket change confirmation form including the ticket change price based on the expected flight information and feedback it to the user.

[0037] In this embodiment, a user who needs to change the ticket can submit a ticket change application through the order system of the terminal. The ticket change request usually carries multiple parameters. For example, parameters such as the basic information of the passenger, the original flight number, and the expected flight number. After the ticket change system receives the ticket change request sent by the user, the lack of necessary parameters may cause the ticket change process to be interrupted or incorrect, affecting the subsequent ticket change processing. Therefore, it is necessary to verify the parameters corresponding to the request. For example, the legality of the parameters can be verified, and the integrity of the parameters can also be verified.

[0038] Specifically, the verification of the parameters corresponding to the request includes:

[0039] Verify whether the parameters corresponding to the request are complete;

[0040] If so, determine that the parameter verification corresponding to the request passes.

[0041] Verifying whether the parameters corresponding to the request are complete can prevent the ticket change process from being interrupted or incorrect due to data loss. If it is verified that the parameters corresponding to the request are complete, it is determined that the parameter verification corresponding to the request passes. Further, if it is verified that the parameters corresponding to the request are incomplete, the user's ticket change is rejected. It is also possible to verify whether there is data such as a refunded ticket. If so, the user's ticket change is also rejected.

[0042] If the verification passes, it means that the parameters corresponding to the request are compliant and complete. Therefore, a ticket change order can be generated according to the request.

[0043] Since ticket change involves changes in information such as flights and prices, after the parameters corresponding to the request are verified to pass, the ticket change order needs to be sent to the price verification system for the price verification system to determine whether to allow the user to change the ticket based on the ticket change order.

[0044] Specifically, the price verification system determines whether to allow the user to change the ticket based on the ticket change order, including:

[0045] The price verification system requests the verification interface of the supplier system according to the parameters of the supplier;

[0046] Obtain the verification result returned by the verification interface of the supplier system;

[0047] Based on the verification result and the rebooking order, determine whether to allow the user to rebook.

[0048] After the rebooking order is created, request the relevant information to the automatic fare verification system. The automatic fare verification system needs to verify the information returned by the supplier system. For example, according to the corresponding parameters of different organizations of the supplier, the fare verification system requests the interface of the corresponding supplier system to obtain the verification result returned by the verification interface of the supplier system. Since the returned verification result contains the current flight information, the fare verification system can determine whether to allow the user to rebook according to the verification result returned by the verification interface of the supplier system. Among them, the supplier system is the system that provides flight information.

[0049] Further, the determining whether to allow the user to rebook according to the verification result and the rebooking order includes:

[0050] Determine whether there is the corresponding expected flight information in the rebooking order in the verification result;

[0051] If it exists, allow the user to rebook.

[0052] Determine whether there is the corresponding expected flight information in the rebooking order in the verification result returned by the supplier system. If it exists, allow the user to rebook.

[0053] After determining to allow the user to rebook, call the flight interface according to the requested parameters, and filter the result returned by the supplier to match the expected flight information corresponding to the rebooking order.

[0054] After all passengers pass the verification, according to the requested parameters, request the rebooking flight query interface, and filter the verification result returned by the supplier system to match the flight that the user expects to rebook.

[0055] In one embodiment, after calling the flight interface according to the requested parameters and matching the expected flight information corresponding to the rebooking order, the method further includes:

[0056] Verify the key information of the expected flight information, where the key information includes at least one of flight number, departure time, cabin class, and cabin grade data;

[0057] If the key information passes the verification, execute the step of generating a rebooking confirmation form containing the rebooking price and feedbacking it to the user based on the expected flight information.

[0058] Verify the key information of the matched expected flight information. The key information includes at least one of flight number, departure time, cabin class, and class data. Among them, the class data needs to be the same as that of the original flight.

[0059] If the key information verification passes, generate a ticket change confirmation form containing the ticket change price and send it back to the user according to the expected flight information.

[0060] After the flight data verification passes, parse the flight price. If there is a ticket change price and a class difference in the verification result returned by the supplier system, directly generate information containing the ticket change price and service fee and return it to the user. Otherwise, calculate the class difference by calculating the ticket change flight amount. At the same time, since different suppliers have corresponding ticket change service fees, request the supplier configuration system, obtain the corresponding service fee, assemble the total price information and send it to the user. Automatically calculate the fare difference through an algorithm and provide the best alternative flight selection for passengers according to the existing flight situation.

[0061] In one embodiment, after generating a ticket change confirmation form containing the ticket change price and feeding it back to the user, the method further includes:

[0062] Receive the confirmation information fed back by the user based on the ticket change confirmation form;

[0063] Call the payment interface according to the confirmation information for the user to make a payment.

[0064] After generating a ticket change confirmation form containing the ticket change price and sending it back to the user, send an email to the user who has changed the ticket at the same time, waiting for the user to confirm the ticket change amount and confirm the ticket change. After the user confirms, call the interface for successful ticket change confirmation. Specifically, the order system requests the ticket change order generation interface of the supplier, obtains the ticket change order number, verifies whether the ticket change amount is consistent with the queried amount, and returns and verifies the data format.

[0065] After the verification of the order generation result passes, call the payment interface of the supplier system. After the payment is completed, modify the status of the ticket change order. The ticket change order enters the status of waiting for ticket issuance after payment, and the order in this status is obtained through a timer.

[0066] When calling the supplier's ticket change order generation and ticket change payment interfaces, if a server error occurs, or the supplier returns a failure in order generation or payment failure, etc., return the failure status to the order system and modify the status of the ticket change order to "ticket change failed, waiting for refund", waiting to refund the ticket change fee paid by the user to the credit limit of the user.

[0067] Refer to Figure 2 As shown, it is a schematic diagram of the functional modules of the ticket change device 100 of the present application.

[0068] The ticket change device 100 described in this application can be installed in an electronic device. According to the functions achieved, the ticket change device 100 may include a verification module 110, a first generation module 120, a sending module 130, a matching module 140, and a second generation module 150. The modules described in this application may also be referred to as units, which refer to a series of computer program segments that can be executed by the processor of an electronic device and can complete fixed functions, and are stored in the memory of the electronic device.

[0069] In this embodiment, the functions of each module / unit are as follows:

[0070] Verification module 110: used to receive the ticket change request sent by the user and verify the parameters corresponding to the request;

[0071] First generation module 120: used to generate a ticket change order according to the request if the parameters corresponding to the request pass the verification;

[0072] Sending module 130: used to send the ticket change order to the price verification system for the price verification system to judge whether to allow the user to change the ticket based on the ticket change order;

[0073] Matching module 140: used to call the flight interface according to the parameters of the request and match the expected flight information corresponding to the ticket change order if the user is allowed to change the ticket;

[0074] Second generation module 150: used to generate a ticket change confirmation order containing the ticket change price based on the expected flight information and feedback it to the user.

[0075] In one embodiment, the verification of the parameters corresponding to the request includes:

[0076] Verify whether the parameters corresponding to the request are complete;

[0077] If so, determine that the parameters corresponding to the request pass the verification.

[0078] In one embodiment, the price verification system judges whether to allow the user to change the ticket based on the ticket change order, including:

[0079] The price verification system requests the verification interface of the supplier system according to the parameters of the supplier;

[0080] Obtain the verification result returned by the verification interface of the supplier system;

[0081] Judge whether to allow the user to change the ticket according to the verification result and the ticket change order.

[0082] In one embodiment, the judgment of whether to allow the user to change the ticket according to the verification result and the ticket change order includes:

[0083] Determine whether the verification result contains the expected flight information corresponding to the re-booking order;

[0084] If so, the user is allowed to change the ticket.

[0085] In one embodiment, the matching module 140 is further configured to:

[0086] Verifying key information of the expected flight information, wherein the key information includes at least one of flight number, departure time, cabin space, and cabin class data;

[0087] If the key information verification passes, the step of generating a rebooking confirmation form including a rebooking price based on the expected flight information and feeding it back to the user is executed.

[0088] In one embodiment, the ticket change device 100 further includes a calling module, which is used to receive confirmation information fed back by the user based on the ticket change confirmation slip;

[0089] A payment interface is called according to the confirmation information for the user to make payment.

[0090] In one embodiment, the verifying the parameters corresponding to the request further includes:

[0091] If the parameters corresponding to the request are incomplete, the user's request to change the ticket will be rejected.

[0092] Reference Figure 3 , which is a schematic diagram of a preferred embodiment of the electronic device of the present application.

[0093] The electronic device includes a processor 111, a communication interface 112, a memory 113 and a communication bus 114, wherein the processor 111, the communication interface 112, and the memory 113 communicate with each other via the communication bus 114;

[0094] Memory 113, for storing computer programs, for example, a ticket change program;

[0095] In some embodiments, the processor 111 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip. The processor 111 is generally used to control the overall operation of the electronic device, such as performing control and processing related to data interaction or communication. In this embodiment, the processor 111 is used to run the program code stored in the memory 113 or process data, such as running the program code of the ticket change program.

[0096] The communication interface 112 may optionally include a standard wired interface, a wireless interface (such as a WI-FI interface), and this communication interface 112 can also be used to establish a communication connection between the electronic device and other electronic devices.

[0097] The memory 113 includes at least one type of readable storage medium. The readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (such as SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disc, etc. In some embodiments, the memory 113 may be an internal storage unit of the electronic device, such as the hard disk or memory of the electronic device. In other embodiments, the memory 113 may also be an external storage device of the electronic device, such as a plug-in hard disk equipped with the electronic device, a Smart Media Card (SMC), a Secure Digital (SD) card, a Flash Card, etc. Of course, the memory 113 may also include both the internal storage unit of the electronic device and its external storage device. In this embodiment, the memory 11 is generally used to store the operating system installed on the electronic device and various computer programs, such as the program code of the ticket rescheduling program. In addition, the memory 113 can also be used to temporarily store various data that have been output or will be output.

[0098] In an embodiment of the present application, when the processor 111 executes the program stored on the memory 113, it implements the ticket rescheduling method provided by any one of the foregoing method embodiments, including:

[0099] Receiving a ticket rescheduling request sent by a user and verifying the parameters corresponding to the request;

[0100] If the verification passes, generating a rescheduling order according to the request;

[0101] Sending the rescheduling order to the price verification system for the price verification system to determine whether to allow the user to reschedule based on the rescheduling order;

[0102] If so, calling a flight interface according to the parameters of the request to match the expected flight information corresponding to the rescheduling order;

[0103] Generating a rescheduling confirmation order including the rescheduling price based on the expected flight information and feeding it back to the user.

[0104] For a detailed introduction to the above steps, please refer to the above Figure 1Description of the flowchart of the embodiment of the air ticket change method.

[0105] In addition, an embodiment of the present application also proposes a computer-readable storage medium, which can be non-volatile or volatile. The computer-readable storage medium includes a storage data area and a storage program area. The storage program area stores an air ticket change program. When the air ticket change program is executed by a processor, the following operations are implemented:

[0106] Receive the air ticket change request sent by the user and verify the parameters corresponding to the request;

[0107] If the verification passes, generate a change order according to the request;

[0108] Send the change order to the price verification system for the price verification system to judge whether to allow the user to change the ticket based on the change order;

[0109] If so, call the flight interface according to the parameters of the request to match the expected flight information corresponding to the change order;

[0110] Based on the expected flight information, generate a change confirmation order including the change price and feedback it to the user.

[0111] The specific implementation manner of the computer-readable storage medium of the present application is substantially the same as the specific implementation manner of the above air ticket change method, and will not be repeated here.

[0112] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0113] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a general hardware platform, and of course, it can also be implemented by hardware. Based on such an understanding, the essence of the above technical solution, or the part that contributes to the related technology, can be embodied in the form of a software product. The computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0114] It should be noted that the descriptions involving "first", "second", etc. in this application are only for descriptive purposes and should not be construed as indicating or implying their relative importance or implicitly specifying the quantity of the indicated technical features. Thus, features defined with "first" and "second" may explicitly or implicitly include at least one such feature. Additionally, the technical solutions between various embodiments may be combined with each other, but it must be based on the ability of those of ordinary skill in the art to implement. When the combination of technical solutions results in contradictions or cannot be implemented, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection required by this application.

[0115] It should be understood that the terms used herein are for the purpose of describing particular example embodiments only and are not intended to be limiting. Unless the context clearly dictates otherwise, the singular forms "a", "an", and "the" as used herein may also include the plural forms. The terms "comprising", "including", "containing", and "having" are inclusive and thus specify the presence of the stated features, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and / or combinations thereof. The method steps, processes, and operations described herein are not to be construed as necessarily requiring them to be performed in the particular order described or illustrated, unless the order of performance is explicitly stated. It should also be understood that additional or alternative steps may be used.

[0116] The foregoing are only specific embodiments of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application will not be limited to these embodiments shown herein, but rather to the broadest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for changing an air ticket, characterized in that: The method comprises: Receive a ticket change request sent by a user and verify parameters corresponding to the request; If the verification is passed, a change order is generated according to the request; Sending the change order to the price verification system, so that the price verification system can determine whether to allow the user to change the order based on the change order; If yes, call the flight interface according to the parameters of the request to match the expected flight information corresponding to the changed order; Based on the expected flight information, a rebooking confirmation form including the rebooking price is generated and fed back to the user.

2. The ticket change method according to claim 1, characterized in that: The verifying the parameters corresponding to the request includes: Verify whether the parameters corresponding to the request are complete; If so, it is determined that the parameter verification corresponding to the request passes.

3. The ticket change method according to claim 1, characterized in that: The price checking system determines whether to allow the user to change the order based on the changed order, including: The price verification system requests the verification interface of the supplier system according to the supplier's parameters; Get the verification result returned by the verification interface of the supplier system; Based on the verification result and the re-signed order, determine whether the user is allowed to re-sign.

4. The ticket change method according to claim 3, characterized in that: The determining whether to allow the user to change the order according to the verification result and the changed order includes: Determine whether the verification result contains the expected flight information corresponding to the re-booking order; If so, the user is allowed to change the ticket.

5. The ticket change method according to claim 1, characterized in that: After calling the flight interface according to the parameters of the request and matching the expected flight information corresponding to the change order, the method further includes: Verifying key information of the expected flight information, wherein the key information includes at least one of flight number, departure time, cabin space, and cabin class data; If the key information verification passes, the step of generating a rebooking confirmation form including a rebooking price based on the expected flight information and feeding it back to the user is executed.

6. The ticket change method according to claim 1, characterized in that: After generating a change confirmation form including the change price and feeding it back to the user, the method further includes: Receiving confirmation information fed back by the user based on the ticket change confirmation form; A payment interface is called according to the confirmation information for the user to make payment.

7. The ticket change method according to claim 1, characterized in that: The verifying of the parameters corresponding to the request further includes: If the parameters corresponding to the request are incomplete, the user's request to change the ticket will be rejected.

8. A device for changing an air ticket, characterized in that: The device comprises: Verification module: used to receive the ticket change request sent by the user and verify the parameters corresponding to the request; The first generating module is used to generate a change order according to the request if the parameter verification corresponding to the request passes; Sending module: used for sending the change order to the price verification system, so that the price verification system can determine whether to allow the user to change the order based on the change order; Matching module: used to call the flight interface according to the parameters of the request if the user is allowed to change the ticket, and match the expected flight information corresponding to the changed order; The second generating module is used to generate a rebooking confirmation form including a rebooking price based on the expected flight information and feed it back to the user.

9. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor is used to implement the ticket changing method described in any one of claims 1 to 7 when executing the program stored in the memory.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the ticket changing method according to any one of claims 1 to 7 is implemented.

Images