Dynamic freight rate refund and change operation method and device and electronic equipment

Abstract

The invention discloses a dynamic freight rate refund and change operation method and device and electronic equipment, and relates to the technical field of aviation freight rate search or other related technical fields, and the method comprises the steps: receiving dynamic freight rate order data issued by each airline, generating an airline order issuing record based on the dynamic freight rate order data, and sending the dynamic freight rate order issuing record to a server; the airline company order release record is used for mapping the reference freight rate before adjustment and the adjusted freight rate, associating a refund rule between the freight rates, and executing an air ticket refund operation based on the refund rule, and the dynamic freight rate order data at least comprises an order identifier field, an order time field and a reference ticket price field. According to the method and the device, the technical problem of low returning and changing efficiency caused by the fact that the returning and changing rule of the original air ticket cannot be extracted when a passenger performs dynamic freight rate returning and changing operation in the prior art is solved.

Description

Technical Field

[0001] The present invention relates to the field of freight rate search technology or other related fields, and in particular to a dynamic freight rate refund and change operation method, a device thereof, and an electronic device. Background Art

[0002] In the related art, the dynamic fare adjustment of airlines is a complex and delicate process, which involves many variables and factors, including market demand, competition conditions and cost changes, all of which will affect the airline's fare adjustment strategy. This adjustment strategy is not static, but needs to be carried out according to the characteristics of the airline itself and the dynamic response of the market. By adjusting the dynamic fare, airlines can achieve the best revenue and benefits, thereby achieving the purpose of differentiated sales. However, the implementation of dynamic fare strategies in the existing technology is only the first step in differentiated sales. When subsequent passengers make refund and change operations based on dynamic fares, they often cannot retrieve the refund and change rules of the original ticket, resulting in the lack of knowledge of the difference information of ticket refunds and changes, which brings some problems to the airline's operations.

[0003] To address the above-mentioned problems, no effective solutions have been proposed so far. Summary of the Invention

[0004] The embodiments of the present invention provide a dynamic fare refund and change operation method and device, as well as an electronic device, to at least solve the technical problem in related technologies that when passengers perform dynamic fare refund and change operations, they cannot retrieve the refund and change rules of the original ticket, resulting in low refund and change efficiency.

[0005] According to one aspect of an embodiment of the present invention, a dynamic fare refund and change operation method is provided, comprising: receiving dynamic fare order data published by various airlines, wherein the dynamic fare order data includes at least: an order identifier field, an order time field, and a base fare field; generating an airline order release record based on the dynamic fare order data, wherein the airline order release record is used to map the base fare before adjustment with the fare after adjustment, and associate refund and change rules between the fares; and performing a ticket refund and change operation based on the refund and change rules.

[0006] Optionally, before receiving the dynamic fare order data released by each airline, it also includes: receiving the mandatory order fields and corresponding field data released by each airline, wherein the mandatory order fields include at least one of the following: order identifier field, order time field, base fare booking code, base fare amount, airline code, base fare rules, base fare starting city code, base fare destination city code, base fare type, base fare class code, base fare one-way round-trip indicator, ticket indicator, ticketing code, base currency code, the order identifier field includes: order code field or ticket number field, the order time field includes: booking creation date field, sales date field ... The method comprises: receiving the order optional fields and corresponding field data issued by each airline, wherein the order optional fields include at least one of the following: point of sale information of each fare component, base fare currency code, base fare rule number, base fare itinerary information, base fare footer, base fare passenger type code, base fare ticket indicator, base fare ticketing code, adjusted fare basis code, adjusted ticket indicator, adjusted ticketing code, adjusted fare amount, adjusted currency code, and adjusted award mileage; and obtaining the dynamic fare order data based on the order mandatory fields and corresponding field data and the order optional fields and corresponding field data.

[0007] Optionally, the step of generating an airline order release record based on the dynamic fare order data includes: mapping the dynamic fare order data to an order release template of each airline respectively, and constructing a formatted airline order release record.

[0008] Optionally, after generating the airline order release record based on the dynamic fare order data, it also includes: receiving a subscription instruction from the airline, wherein the subscription instruction is an instruction for the subscriber to browse the order release records of each airline; responding to the subscription instruction, after detecting the dynamic fare order data released by the airline, distributing the airline order release record to the subscriber.

[0009] Optionally, after distributing the airline order release record to the subscriber end, it also includes: after detecting that the airline order release record is distributed to the subscriber end, receiving a cancellation instruction from the subscriber end, and outputting a cancellation record, wherein the termination date of the cancellation record is recorded as the date of sending the cancellation record.

[0010] Optionally, after generating an airline order release record based on the dynamic fare order data, it also includes: receiving the order number and ticket number sent by the airline; matching the airline order release record corresponding to the order number; if the airline order release record corresponding to the order number is not matched, matching the airline order release record corresponding to the ticket number.

[0011] Optionally, after generating an airline order release record based on the dynamic fare order data, it also includes: receiving an order number or ticket number sent by the airline; matching the airline order release record corresponding to the order number; or, if no order number sent by the airline is received, matching the airline order release record corresponding to the ticket number based on the quasi-fare tariff number, airline code, base fare starting city code, base fare destination city code, fare category code, ticketing code, ticket designator or fare amount.

[0012] Optionally, after generating an airline order release record based on the dynamic fare order data, it also includes: in the case where the order number and ticket number sent by the airline are not received, matching the corresponding airline order release record based on the quasi-fare tariff number, airline code, base fare starting city code, base fare destination city code, fare category code, ticketing code, ticket designator or fare amount.

[0013] According to another aspect of an embodiment of the present invention, a dynamic fare refund and change operation device is also provided, including: an order data receiving unit, used to receive dynamic fare order data issued by each airline, wherein the dynamic fare order data at least includes: an order identifier field, an order time field, and a base fare field; an order release record generating unit, used to generate an airline order release record based on the dynamic fare order data, wherein the airline order release record is used to map the base fare before adjustment with the fare after adjustment, and associate the refund and change rules between the fares; and an air ticket refund and change operation unit, used to perform air ticket refund and change operations based on the refund and change rules.

[0014] Optionally, the dynamic fare refund and change operation device also includes: a first field data receiving unit, which is used to receive the mandatory order fields and corresponding field data issued by each airline before receiving the dynamic fare order data issued by each airline, wherein the mandatory order fields include at least one of the following: order identifier field, order time field, base fare booking code, base fare amount, airline code, base fare rules, base fare starting city code, base fare destination city code, base fare type, base fare class code, base fare one-way round-trip indicator, ticket indicator, ticketing code, base currency code, the order identifier field includes: order code field or ticket number field, the order time field includes: booking creation date field, sales date field a second field data receiving unit, configured to receive optional order fields and corresponding field data published by each airline, wherein the optional order fields include at least one of the following: point of sale information of each fare component, base fare currency code, base fare rule number, base fare itinerary information, base fare footer, base fare passenger type code, base fare ticket indicator, base fare ticketing code, adjusted fare basis code, adjusted ticket indicator, adjusted ticketing code, adjusted fare amount, adjusted currency code, and adjusted bonus mileage; a fare order data generating unit, configured to obtain the dynamic fare order data based on the required order fields and corresponding field data and the optional order fields and corresponding field data.

[0015] Optionally, the order release record generating unit includes: a template mapping module, configured to map the dynamic freight rate order data to the order release template of each airline respectively, and construct a formatted airline order release record.

[0016] Optionally, the dynamic fare refund and change operation device also includes: a subscription instruction receiving unit, which is used to receive the subscription instruction of the airline after generating the airline order release record based on the dynamic fare order data, wherein the subscription instruction is an instruction for the subscription end to read the order release record of each airline; an instruction response unit, which is used to respond to the subscription instruction and distribute the airline order release record to the subscription end after detecting the dynamic fare order data released by the airline.

[0017] Optionally, the dynamic fare refund and change operation device also includes: a cancellation record output unit, which is used to receive the cancellation instruction from the subscription end after distributing the airline order release record to the subscription end, and output the cancellation record after detecting that the airline order release record is distributed to the subscription end, wherein the termination date of the cancellation record is recorded as the date of sending the cancellation record.

[0018] Optionally, the dynamic fare refund and change operation device also includes: a first number receiving unit, used to receive the order number and ticket number sent by the airline after generating the airline order release record based on the dynamic fare order data; a first matching unit, used to match the airline order release record corresponding to the order number; and a second matching unit, used to match the airline order release record corresponding to the ticket number when the airline order release record corresponding to the order number is not matched.

[0019] Optionally, the dynamic fare refund and change operation device also includes: a second number receiving unit, which is used to receive the order number or ticket number sent by the airline after generating the airline order release record based on the dynamic fare order data; a third matching unit, which is used to match the airline order release record corresponding to the order number; or, a fourth matching unit, which is used to match the airline order release record corresponding to the ticket number based on the quasi-fare tariff number, airline code, base fare starting city code, base fare destination city code, fare category code, ticketing code, ticket designator or fare amount when the order number sent by the airline is not received.

[0020] Optionally, the dynamic fare refund and change operation device also includes: a fifth matching unit, which is used to match the corresponding airline order release record based on the quasi-fare tariff number, airline code, base fare starting city code, base fare destination city code, fare category code, ticketing code, ticket designator or fare amount after generating the airline order release record based on the dynamic fare order data, if the order number and ticket number sent by the airline are not received.

[0021] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is further provided, wherein the computer-readable storage medium includes a stored computer program, wherein when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute any one of the above-mentioned dynamic fare refund and change operation methods.

[0022] According to another aspect of an embodiment of the present invention, an electronic device is also provided, comprising 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 any one of the above-mentioned dynamic fare refund and change operation methods.

[0023] According to another aspect of an embodiment of the present invention, a computer program product is provided, including a computer program, which, when executed by a processor, implements the steps of any one of the above-mentioned dynamic fare refund and change operation methods.

[0024] In the present invention, dynamic fare order data released by various airlines are received, and based on the dynamic fare order data, an airline order release record is generated. The airline order release record is used to map the base fare before adjustment with the adjusted fare, associate the refund and change rules between the fares, and perform the ticket refund and change operation based on the refund and change rules, wherein the dynamic fare order data at least includes: an order identifier field, an order time field, and a base fare field. In the present invention, an airline order release record can be generated based on the dynamic fare order data. By associating the refund and change rules between the fares through the airline order release record, the refund and change information of the original ticket can be extracted, and the airline can accurately handle the refund and change operation of the dynamic fare ticket to ensure that its refund and change operation meets the refund and change requirements, while enhancing the user experience of passengers, thereby solving the technical problem in the related art that when passengers perform dynamic fare refund and change operations, they cannot extract the refund and change rules of the original ticket, resulting in low refund and change efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0026] Figure 1 This is a flow chart of an optional dynamic fare refund and change operation method according to an embodiment of the present invention;

[0027] Figure 2 2 is a schematic diagram of an optional dynamic fare refund and change operation device according to an embodiment of the present invention;

[0028] Figure 3 The present invention is a hardware structure block diagram of an electronic device (or mobile device) for executing a dynamic fare refund and change operation method according to an embodiment of the present invention. DETAILED DESCRIPTION

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

[0030] It should be noted that the terms "first", "second", etc. in the description 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 numbers 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 clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0031] It should be noted that the dynamic fare refund and change operation method and its device in the present disclosure can be used in the field of airline fare search technology. When the dynamic air ticket fare refund and change service is implemented based on the airline fare search, it can also be used in any field other than the field of airline fare search technology. When the dynamic air ticket fare refund and change service is implemented based on the airline fare search, the application field of the dynamic fare refund and change operation method and its device in the present disclosure is not limited.

[0032] It should be noted that the information (including but not limited to user ticket information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) collected by this disclosure are 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 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 portals for users to choose to authorize or refuse. For example, an interface is set up between this system and relevant users or institutions. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or institution through the interface, and obtain relevant information after receiving the consent information fed back by the aforementioned user or institution.

[0033] It should be noted that in this disclosure, when collecting and analyzing customer information, the corresponding operation entrance is provided for users to choose to agree or reject the automated decision-making results; if the user chooses to reject, the expert decision-making process will be entered.

[0034] The following embodiments of the present invention can be applied to various systems / applications / devices for dynamic fare refund and change operations. In the retail sales process, efficiently and effectively handling ticket refunds and changes is a crucial aspect that airlines cannot ignore. In this invention, airlines maintain detailed records of ticket orders to provide dynamic fare refund and change services. Implementing dynamic fare refund and change applications requires airlines to use certain methods to track and record information about sold tickets and related fees. This record typically includes information such as order number, fare, and purchase date. By recording this detailed information, airlines can accurately extract the corresponding fare adjustments and thus obtain the refund and change information rules corresponding to the original ticket. When refunding and changing tickets at adjusted fares, airlines need to clearly understand the refund and change information associated with the original ticket. Airlines can gradually obtain the refund and change rules and conditions corresponding to the original ticket based on the ticket number information stored in the order record. By extracting the refund and change information for the original ticket, airlines can accurately handle dynamic fare ticket refund and change operations, ensuring that their refund and change operations meet refund and change requirements. Only when the refund and change operations comply with the refund and change procedures and rules can passengers get their due rights and airlines can truly realize the benefits of dynamic fares.

[0035] The present invention is based on a refund and change system, that is, an existing refund and change system. After the airline dynamically sets prices, refund and change rules are associated with the content of the dynamic pricing. The premise of the present invention is that the user has experienced dynamic price adjustments and the user already has a self-built or subscribed refund and change system.

[0036] This invention complements the missing steps in dynamic fare refund and modification, making up for the shortcomings of airlines in dynamic fare refund and modification, and further enriching the service content of airlines throughout the dynamic fare process. In this way, airlines can not only improve their own economic benefits, but also enhance the user experience of passengers, achieving a win-win situation. The dynamic fare refund and modification operation method is a universal and complex method that deeply integrates market demand, cost control, and customer service. Through refined order record keeping and management, airlines can better meet this challenge, thereby realizing the refund and modification advantages of dynamic fares and improving service quality and economic benefits.

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

[0038] Example 1

[0039] According to an embodiment of the present invention, an embodiment of a method for dynamic fare refund and change operation is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0040] Figure 1 Flowchart of an optional dynamic fare refund and change operation method according to an embodiment of the present invention. Figure 1 As shown, the method includes the following steps:

[0041] Step S101: receiving dynamic fare order data issued by various airlines, wherein the dynamic fare order data at least includes: an order identifier field, an order time field, and a base fare field.

[0042] Step S102: Generate an airline order release record based on the dynamic fare order data, wherein the airline order release record is used to map the base fare before adjustment with the fare after adjustment, and associate the cancellation and change rules between the fare rates.

[0043] Step S103: Execute the ticket refund and change operation based on the refund and change rules.

[0044] Through the above steps, the dynamic fare order data released by each airline can be received, and based on the dynamic fare order data, an airline order release record can be generated. The airline order release record is used to map the base fare before adjustment with the adjusted fare, associate the refund and change rules between the fares, and perform the ticket refund and change operation based on the refund and change rules, wherein the dynamic fare order data at least includes: an order identifier field, an order time field, and a base fare field. In this embodiment, an airline order release record can be generated based on the dynamic fare order data. By associating the refund and change rules between the fares through the airline order release record, the refund and change information of the original ticket can be extracted. The airline can accurately handle the refund and change operation of the dynamic fare ticket to ensure that its refund and change operation meets the refund and change requirements, while improving the user experience of passengers, thereby solving the technical problem in the related art that when passengers perform dynamic fare refund and change operations, they cannot extract the refund and change rules of the original ticket, resulting in low refund and change efficiency.

[0045] This embodiment can be applied to the fare search platform connected to each airline, and can also be directly applied to the ticket ordering platform or application APP used by each airline. Taking the fare search platform as an example, the fare search platform may include: an order data collection component and an order data processing component. The function of the order data collection component is to receive the dynamic fare order data released by the airline. The function of the order data processing component is to map the data in the order data collection component and generate an airline order release record. The function of this record is to reuse the refund and change rules related to the original fare, map the base fare before the dynamic fare adjustment with the fare after the dynamic fare adjustment, and thus associate the refund and change rules between the fares.

[0046] The embodiment of the present invention is described in detail below in conjunction with the above steps.

[0047] Optionally, before receiving the dynamic fare order data released by each airline, it also includes: receiving the mandatory order fields and corresponding field data released by each airline, wherein the mandatory order fields include at least one of the following: order identifier field (or unique identifier field, including: order code or ticket number), order time field (including: booking creation date, sales date and time), base fare booking code (for uniquely identifying the booking code of the base fare), base fare amount (the amount of the base fare, i.e. the standard price of the ticket), airline code (international standard code for identifying the airline), base fare rules (specifying the specific rules of the base fare, such as refund and change regulations, usage restrictions, etc.), base fare starting city code (the starting city of the base fare), and the corresponding field data. The following fields include: international standard code for the base fare destination city (the international standard code for the base fare destination city), base fare type (identifies the type of the base fare, such as adult ticket, child ticket, group ticket, etc.), base fare class code (identifies the class code to which the base fare applies), base fare one-way round-trip indicator (indicates whether the base fare applies to a one-way or round-trip flight), ticket indicator (identifies whether the base fare requires a physical ticket or an electronic ticket), ticketing code (identifies the code for the issuing airline or ticket agency), base currency code (the currency code used for the base fare); order identifier fields include: order code field or ticket number field; order time fields include: booking creation date field, sales date field, and sales time field;Receive the order optional fields and corresponding field data published by each airline, wherein the order optional fields include at least one of the following: sales point information of each fare component (specify the channel or sales point information for purchasing the ticket, which may include the airline's official website, third-party travel website, travel agency, etc.), the base fare currency code generated according to the rules (the currency code of the base fare specified in international standards), the rule number of the base fare generated according to the rules (the rule number of the base fare generated according to the rules of the International Air Transport Association (IATA)), the base fare itinerary information (including the flight information, cabin type, departure and destination of the ticket, etc.), the base fare footnote (special instructions or restrictive information for the base fare), the base fare passenger type code (the traveler type code of the base fare determined according to the identity or qualifications of the passenger). The following items are used to determine the following: passenger type code), base fare ticket indicator (used to indicate whether the fare requires a physical ticket or an electronic ticket), base fare issuance code (specifies which sales outlets or channels can issue the fare), adjusted fare basis code (the basis code for the fare adjusted based on specific conditions or rules), adjusted ticket indicator (indicator of whether the adjusted fare requires a physical ticket or an electronic ticket), adjusted issuance code (specifies which sales outlets or channels can issue the adjusted fare), adjusted fare amount (the fare amount adjusted based on specific conditions or rules), adjusted currency code (the currency code used for the adjusted fare amount), and adjusted award miles; dynamic fare order data is obtained based on the required order fields and corresponding field data, as well as the optional order fields and corresponding field data.

[0048] The Order Data Collection component mentioned in this example receives dynamic fare order data published by airlines. To ensure the Order Data Collection component has all the necessary information to construct the airline's order release record, the airline is required to provide data for required fields. This data is sent to the Order Data Collection component via an API method in a proprietary format. If required field elements are missing, a failure will occur, and a message will be displayed indicating the missing data.

[0049] Required fields include: unique identifier, which can be either a booking ID or a ticket number; booking creation date, sale date, and time; fare owner's airline code, which may not always be the data provider's code, e.g., airline ZZ sends a request to airline XX; base fare tariff number (Tar iff); base fare rules; base fare origin city code; base fare destination city code; base fare type; base fare class code; base fare one-way round-trip indicator; base fare booking code (RBD); base fare amount, including decimals, which is the fare amount before the fare amount is adjusted, excluding taxes and surcharges. This amount can be a one-way amount or half of a round-trip amount. The order data collection component will double the round-trip half amount for publication; base currency code, which is used in conjunction with the base fare amount; base award miles. If both fare amount and award miles are provided, the order data collection component will use the fare amount for processing.

[0050] Optional fields: Point of sale information for each fare component; Base fare currency code generated according to the rule; Rule number for the base fare generated according to the rule; Base fare itinerary information, if left blank, defaults to blank; Base fare footer, if left blank, defaults to blank; Base fare passenger type code, if filled, defaults to adult; Base fare ticket indicator; Base fare ticket code; Adjusted fare basis code, if not provided, uses the base fare basis code; Adjusted ticket indicator; Adjusted ticket code; Adjusted fare amount, including decimals, if not provided, uses the base fare amount, including decimals; Adjusted currency code, if not provided, defaults to US dollars; Adjusted award miles.

[0051] The following fields explain the base fare, ticket indicator, and ticketing code. The base fare is the base fare before dynamic fare adjustments. The ticket indicator primarily indicates the ticket type, such as a booking number or ticket number. The ticketing code is the specific encoding of the booking number or ticket number. The booking number is a unique number generated when a customer makes a flight reservation. It is used to track and manage the customer's reservation information, including flight, seat selection, and passenger information. The booking number is typically generated immediately after a customer completes a reservation and sent to the customer via email or other means. It plays an important role in communication and coordination between the customer and the airline or travel agent. The ticket number is a unique identification code obtained after a customer purchases a ticket. It uniquely identifies the ticket and is used for verification and verification at boarding. The ticket number is typically generated by the airline and consists of an airline code and a numerical sequence. Customers can obtain the ticket number through either an e-ticket or a physical ticket. Therefore, the booking number is used to track and manage the customer's reservation information, while the ticket number is used to verify and verify the identity of the customer's ticket.

[0052] Optionally, the step of generating an airline order release record based on the dynamic fare order data includes mapping the dynamic fare order data to each airline's order release template to construct a formatted airline order release record. Table 1 below illustrates a structured format of an airline order release record.

[0053] Table 1 Structured format of airline order release records

[0054]

[0055] Among them, Tariff refers to the base fare tariff number, Orig refers to the passenger's departure point, Dest refers to the passenger's destination, Fare Class refers to the passenger's cabin class, Rule refers to the refund and change policy, Rtg refers to the return information, OW refers to the passenger's one-way trip, RT refers to the passenger's round-trip trip, SRC refers to the passenger's departure city, Eff refers to the ticket validity period, Disc refers to discount information, Amount Order ID / refers to the order amount number, Tkt Nbr refers to the ticket number, and Ref Trf refers to transfer information.

[0056] Table 2 below illustrates a structure of a base fare record.

[0057] Table 2 Structure of base fare records

[0058]

[0059] In this embodiment, an order data collection component is used to collect order data from airlines, and an order data processing component is used to create an airline order release record, which is mapped to the refund and change rules of the previous fare benchmark to implement the refund and change operation of dynamic fares.

[0060] The following examples illustrate the data collection, distribution, and usage process for dynamic fare refund and change operations.

[0061] After the airline's quotation / order management system converts the quotation into an order, the order is sent to the order data collection component in a standard format to create the airline's order release record.

[0062] After cutting, filtering and cleaning the information, the order data collection component pushes the valuable order data to the order data processing component. The order data processing component receives the order data and maps the order data information to each new airline order release record to construct a formatted airline order release record.

[0063] That is, by executing steps S101 to S103, by receiving dynamic fare order data released by various airlines, generating airline order release records based on the dynamic fare order data, and performing ticket refund and change operations based on refund and change rules.

[0064] The fare basis record in the historical database contains a unique order ID or ticket number, depending on the fulfillment status of each airline's quote order. The fare basis record in the historical database is Record1 in the following four scenarios. The order ID is OrderID in all four scenarios, and the ticket number is Ticket Number TKTNUM in all four scenarios.

[0065] Table 3 below illustrates a structured format of a fare basis record.

[0066] Table 3 Structured format of fare basis records in the historical database

[0067]

[0068] In Table 3, the fare basis record structure includes the base fare tariff number Tariff, the refund and change policy Rule, the cabin class Fare Class, the ticket validity period Eff, the discount information Disc, the flight segment #Seg (referring to a section of the flight between takeoff and landing, usually each flight segment corresponds to a flight number and flight time), the base fare ticket code TicketCode, the base fare ticket indicator Ticket Desig, and the base fare booking code RBD.

[0069] Optionally, after generating the airline order release record based on the dynamic fare order data, the order data distribution operation can be performed. When executing the distribution operation, it also includes: receiving the airline's subscription instruction, wherein the subscription instruction is an instruction for the subscriber to view the order release records of each airline; responding to the subscription instruction, after detecting the dynamic fare order data released by the airline, the airline order release record is distributed to the subscriber.

[0070] In this embodiment, airline order release records are distributed to subscribers during their first subscription after receiving order data, according to the airline's instructions. When a customer selects a flight, the system generates an order. The order contains flight details, such as the flight number (YABC123 / DP), the price ($800), and a unique order ID (Order IDXX123456). The system sends the order and fare rules. The order ID and ticket number are stored on the server for retrieval by the seller / vendor for fare adjustments. The system may adjust fares based on market demand and other factors. The adjusted fares and rules are resubmitted to the Order Data Processing component. Upon receiving the order data, the Order Data Processing component creates a new fare record and a fare basis record in the history database. The new fare record contains the adjusted fare information, such as $800, and links to the original fare rules. Offline systems, such as settlement systems or ticket change / refund systems, use the fare record published by the Order Data Processing component. These systems process customer ticket change and refund requests based on the published fare record.

[0071] Optionally, after distributing the airline order release record to the subscriber end, it also includes: after detecting that the airline order release record is distributed to the subscriber end, receiving the cancellation instruction from the subscriber end, and outputting the cancellation record, wherein the termination date of the cancellation record is recorded as the date of sending the cancellation record.

[0072] In the subscription after the Airline Order Release record is distributed, a Cancellation record will be sent, where the Suspension Date of the record will be recorded as the date the Cancellation Record was sent.

[0073] Airline order release records can be used by downstream refund and change processing systems, such as voluntary change and refund services.

[0074] Airline order release records are used by downstream systems for ticket changes, refunds, and settlement processing. These records can be stored in a separate database or mixed in with other fare records. It's important to note that airline order release records are used only for downstream processing, not for sales. In any case, systems executing downstream processes must first resolve the most specific match and use that record in their processing. For example, if a system has an order number and ticket number, and there is an airline order release record that matches that order number or ticket number and also matches all other matching fields, that record should be used before matching fare basis records in historical databases that don't have order numbers or ticket numbers. Similarly, if a system doesn't have an order number or ticket number and resolves an airline order release record with a fare record that matches the customer's ticket issue date, that airline order release record should be used before attempting to match historical data covering a larger date range.

[0075] The following will specifically explain the four scenarios during use:

[0076] Scenario 1: The downstream system knows both the order number and the ticket number.

[0077] Optionally, after generating an airline order release record based on dynamic fare order data, it also includes: receiving the order number and ticket number sent by the airline; matching the airline order release record corresponding to the order number; if the airline order release record corresponding to the order number is not matched, then matching the airline order release record corresponding to the ticket number.

[0078] If an airline issues a ticket with a specific ticket number and creates an order number, then this scenario applies to Scenario 1. However, during this process, only one of the ticket number and order number will be reflected in the airline's order release record, depending on which data element (order number or ticket number) the airline sends to the order data collection component for release. The airline sends the order number to the order data collection component for distribution in the airline's order release record.

[0079] In this case, the order data processing component will try to match: the airline order release record with the known order number, and if not found, it will try to match the airline order release record with the known ticket number.

[0080] Scenario 2: The downstream system only knows the order number.

[0081] Optionally, after generating the airline order release record based on the dynamic fare order data, the method further includes: receiving the order number or ticket number sent by the airline; and matching the airline order release record corresponding to the order number.

[0082] The ticket number is unknown or not applicable. This may happen when the airline implements a one-bill system and no ticket is issued. In the old system, a separate record is generated for each step of the passenger's ticket purchase, baggage check-in, additional service purchase, etc. These records include ticket records, e-tickets, and miscellaneous receipts, which are independent of each other and unrelated. The goal of the one-bill system is to integrate all these related records into one order, that is, "one order." In this way, whether it is ticket purchase, baggage check-in, or additional service purchase, it will be recorded and managed in the same order. This is why under the one-bill system, there may be a situation where there is no ticket number, because all services are integrated into the same order and a separate ticket number is no longer required.

[0083] In this case where the ticket number is unknown or not applicable, the order data processing component will try to match the airline order release record with a known order number. However, it will not try to match the airline order release record with a ticket number.

[0084] Scenario 3: The downstream system only knows the ticket number.

[0085] Optionally, if the order number sent by the airline is not received, the airline order release record corresponding to the ticket number is matched based on the quasi-fare tariff number, airline code, base fare origin city code, base fare destination city code, fare category code, ticketing code, ticket designator or fare amount.

[0086] The order number is unknown or not applicable. This may happen if the airline has not yet created an order number in its quotation order implementation and is relying on legacy processing. Alternatively, the airline may have created an order number and issued the ticket, but the downstream system does not recognize the order number.

[0087] In such cases where the order number is unknown or not applicable, the order data processing component will attempt to match:

[0088] Airline order release record for known ticket number. If no such record is found, an attempt is made to match an airline order release record for known order number. The matching logic is as follows: Apply the current resolution logic when matching other data in the airline order release record, such as the base fare tariff number (Tar iff), fare owner's airline code, base fare origin city code, base fare destination city code, fare category code, including deconstructing the fare basis code to identify the fare category code, ticketing code, ticket designator, fare amount, etc. for matching.

[0089] Scenario 4: The downstream system knows neither the order number nor the ticket number.

[0090] Optionally, after generating an airline order release record based on dynamic fare order data, it also includes: in the case where the order number and ticket number sent by the airline are not received, matching the corresponding airline order release record based on the quasi-fare tariff number, airline code, base fare starting city code, base fare destination city code, fare category code, ticketing code, ticket designator or fare amount.

[0091] In the case of neither the order number nor the ticket number being known, this can occur when the airline has implemented a single-ticket system, while downstream systems have not yet adopted this system and rely on the fare structure in the current historical database. However, the airline still distributes airline order release records to support legacy processes, such as with interline partners. This can lead to the downstream system not having the ticket number. Another possible scenario is that the airline does create the order number and / or ticket number, but these elements are unknown to downstream systems due to the system's implementation solution.

[0092] In this case where neither the order number nor the ticket number is known, the order data processing component will try to match: the airline order release record containing the order number or ticket number. The matching logic is: apply the current resolution logic when matching other data in the airline order release record, such as the base fare tariff number (Tar iff), the fare owner's airline code, the base fare origin city code, the base fare destination city code, the fare category code, including deconstructing the fare basis code to identify the fare category code, ticketing code, ticket specifier, fare amount, etc. for matching.

[0093] Through the above embodiments, the following technical effects can be achieved:

[0094] 1. Efficient Order Processing: The data collection, distribution, and utilization process for the dynamic fare cancellation and change method provides an efficient way to process airline order data. This process not only converts order data into a standard format but also distributes it according to the airline's instructions.

[0095] 2. Flexible data matching: Regardless of whether the downstream system knows the order or ticket number, the data processing component can apply the corresponding matching logic. This ensures that the system can find the most accurate match in any case, thereby improving the accuracy of refund and cancellation data processing.

[0096] 3. Support for downstream processing fills the gap in process standardization in dynamic fare cancellation and change services: Airline order release records can be used in downstream cancellation and change processing systems, such as voluntary change services and refund services, thereby providing comprehensive services.

[0097] 4. It promotes the implementation of a single-order system: Consolidating all passenger-related records into a single order simplifies data processing and management, improving efficiency. The data collection, distribution, and utilization processes for dynamic fare refund and change procedures support the implementation of a single-order system, helping airlines improve service quality.

[0098] The following describes it in detail with reference to another embodiment.

[0099] Example 2

[0100] A dynamic fare refund and change operation device provided in this embodiment includes multiple implementation units, each implementation unit corresponds to each implementation step in the above-mentioned embodiment 1. The specific implementation process of each implementation unit refers to the embodiment corresponding to each implementation step in the above-mentioned embodiment 1, and will not be repeated here.

[0101] Figure 2 Schematic diagram of an optional dynamic fare refund and change operation device according to an embodiment of the present invention. Figure 2 As shown, the dynamic fare refund and change operation device may include: an order data receiving unit 21, an order release record generating unit 22, and a ticket refund and change operation unit 23.

[0102] The order data receiving unit 21 is used to receive dynamic fare order data issued by various airlines, wherein the dynamic fare order data at least includes: an order identifier field, an order time field, and a base fare field.

[0103] The order release record generating unit 22 is used to generate an airline order release record based on the dynamic fare order data, wherein the airline order release record is used to map the base fare before adjustment with the fare after adjustment, and associate the refund and change rules between the fares.

[0104] The ticket refund and change operation unit 23 is used to perform the ticket refund and change operation based on the refund and change rules.

[0105] The dynamic fare refund and change operation device can utilize an order data receiving unit to receive dynamic fare order data published by various airlines. An order release record generating unit 22 generates an airline order release record based on the dynamic fare order data. The airline order release record maps the pre-adjusted base fare to the adjusted fare and associates the refund and change rules between the fares. A ticket refund and change operation unit 23 performs a ticket refund and change operation based on the refund and change rules. The dynamic fare order data includes at least an order identifier field, an order time field, and a base fare field. In this embodiment, an airline order release record can be generated based on the dynamic fare order data. By associating the refund and change rules between fares in the airline order release record, the refund and change information of the original ticket can be extracted. This allows airlines to accurately process refund and change operations for dynamic fare tickets, ensuring that their refund and change operations meet refund and change requirements while improving the passenger experience. This resolves the technical issue in related art where passengers cannot retrieve the refund and change rules for the original ticket when performing a dynamic fare refund and change operation, resulting in low refund and change efficiency.

[0106] Optionally, the dynamic fare refund and change operation device also includes: a first field data receiving unit, which is used to receive the mandatory order fields and corresponding field data issued by each airline before receiving the dynamic fare order data issued by each airline, wherein the mandatory order fields include at least one of the following: order identifier field, order time field, base fare booking code, base fare amount, airline code, base fare rule, base fare starting city code, base fare destination city code, base fare type, base fare class code, base fare one-way round-trip indicator, ticket indicator, ticketing code, base currency code, order identifier field includes: order code field or ticket number field, order time field includes: booking creation date field, sales date field and sales time field ; A second field data receiving unit is used to receive optional order fields and corresponding field data published by each airline, wherein the optional order fields include at least one of the following: point of sale information of each fare component, a base fare currency code generated according to the rules, a rule number of the base fare generated according to the rules, base fare itinerary information, a base fare footer, a base fare passenger type code, a base fare ticket indicator, a base fare ticketing code, an adjusted fare basis code, an adjusted ticket indicator, an adjusted ticketing code, an adjusted fare amount, an adjusted currency code, and adjusted bonus miles; A fare order data generating unit is used to obtain dynamic fare order data based on the required order fields and the corresponding field data and the optional order fields and the corresponding field data.

[0107] Optionally, the order release record generating unit includes: a template mapping module, which is used to map the dynamic freight rate order data to the order release template of each airline respectively, and construct a formatted airline order release record.

[0108] Optionally, the dynamic fare refund and change operation device also includes: a subscription instruction receiving unit, which is used to receive the airline's subscription instruction after generating the airline's order release record based on the dynamic fare order data, wherein the subscription instruction is an instruction for the subscriber to read the order release records of each airline; an instruction response unit, which is used to respond to the subscription instruction and distribute the airline's order release record to the subscriber after detecting the dynamic fare order data released by the airline.

[0109] Optionally, the dynamic fare refund and change operation device also includes: a cancellation record output unit, which is used to receive the cancellation instruction from the subscriber end after distributing the airline order release record to the subscriber end, and output the cancellation record after detecting that the airline order release record is distributed to the subscriber end, wherein the termination date of the cancellation record is recorded as the date of sending the cancellation record.

[0110] Optionally, the dynamic fare refund and change operation device also includes: a first number receiving unit, used to receive the order number and ticket number sent by the airline after generating the airline order release record based on the dynamic fare order data; a first matching unit, used to match the airline order release record corresponding to the order number; and a second matching unit, used to match the airline order release record corresponding to the ticket number when the airline order release record corresponding to the order number is not matched.

[0111] Optionally, the dynamic fare refund and change operation device also includes: a second number receiving unit, which is used to receive the order number or ticket number sent by the airline after generating the airline order release record based on the dynamic fare order data; a third matching unit, which is used to match the airline order release record corresponding to the order number; or, a fourth matching unit, which is used to match the airline order release record corresponding to the ticket number based on the quasi-fare tariff number, airline code, base fare starting city code, base fare destination city code, fare category code, ticketing code, ticket designator or fare amount when the order number sent by the airline is not received.

[0112] Optionally, the dynamic fare refund and change operation device also includes: a fifth matching unit, which is used to match the corresponding airline order release record based on the quasi-fare tariff number, airline code, base fare starting city code, base fare destination city code, fare category code, ticketing code, ticket designator or fare amount after generating the airline order release record based on the dynamic fare order data, if the order number and ticket number sent by the airline are not received.

[0113] The above-mentioned dynamic fare refund and change operation device may further include a processor and a memory. The above-mentioned order data receiving unit 21, order release record generating unit 22, ticket refund and change operation unit 23, etc. are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to implement corresponding functions.

[0114] The processor includes a core, which retrieves the corresponding program unit from the memory. One or more cores can be set, and dynamic fare refund and change operations can be implemented by adjusting the core parameters.

[0115] The above-mentioned 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.

[0116] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is further provided. The computer-readable storage medium includes a stored computer program, wherein when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute the dynamic fare refund and change operation method of any one of the above-mentioned embodiments.

[0117] According to another aspect of an embodiment of the present invention, an electronic device is also provided, including 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 one or more processors, the one or more processors implement the dynamic fare refund and change operation method of any one of the above-mentioned embodiments.

[0118] The present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of the dynamic fare refund and change operation method described in each embodiment of the present application.

[0119] The present application also provides a computer program product, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the dynamic fare refund and change operation method described in each embodiment of the present application are implemented.

[0120] Figure 3 This is a hardware structure block diagram of an electronic device (or mobile device) that performs a dynamic fare refund and change operation method according to an embodiment of the present invention. Figure 3 As shown, the electronic device may include one or more ( Figure 3 The computer system includes a processor (the processor may include but is not limited to a microprocessor MCU or a programmable logic device FPGA, etc.), and a memory 304 for storing data. In addition, the computer system may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a keyboard, a power supply, and / or a camera. It will be understood by those skilled in the art that Figure 3 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 3 More or fewer components than shown, or with Figure 3 Different configurations shown.

[0121] The serial numbers of the above embodiments of the present invention are for description only and do not represent the advantages or disadvantages of the embodiments.

[0122] In the above embodiments of the present invention, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0123] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

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

[0125] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0126] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk, etc. Various media that can store program codes.

[0127] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as within the scope of protection of the present invention.

Claims

1. A dynamic freight rate refund and change operation method, characterized in that: include: Receiving dynamic fare order data issued by various airlines, wherein the dynamic fare order data at least includes: an order identifier field, an order time field, and a base fare field; Based on the dynamic fare order data, an airline order release record is generated, wherein the airline order release record is used to map the base fare before adjustment with the fare after adjustment, and associate the refund and change rules between the fare; The ticket refund and change operation is performed based on the refund and change rules.

2. The method according to claim 1, characterized in that Before receiving the dynamic freight rate order data released by various airlines, it also includes: Receive the mandatory order fields and corresponding field data issued by each of the airlines, wherein the mandatory order fields include at least one of the following: order identifier field, order time field, base fare booking code, base fare amount, airline code, base fare rule, base fare origin city code, base fare destination city code, base fare type, base fare class code, base fare one-way round-trip indicator, ticket indicator, ticketing code, base currency code, the order identifier field includes: order code field or ticket number field, the order time field includes: booking creation date field, sales date field and sales time field; Receive the optional order fields and corresponding field data published by each of the airlines, wherein the optional order fields include at least one of the following: point of sale information of each fare component, base fare currency code, base fare rule number, base fare itinerary information, base fare footer, base fare passenger type code, base fare ticket indicator, base fare ticketing code, adjusted fare basis code, adjusted ticket indicator, adjusted ticketing code, adjusted fare amount, adjusted currency code, and adjusted award miles; The dynamic freight rate order data is obtained based on the required order fields and the corresponding field data and the optional order fields and the corresponding field data.

3. The method according to claim 1, characterized in that The step of generating an airline order release record based on the dynamic freight rate order data includes: The dynamic freight rate order data is mapped to the order release template of each airline respectively to construct a formatted airline order release record.

4. The method according to claim 1, characterized in that: After generating the airline order release record based on the dynamic freight rate order data, the method further includes: Receiving a subscription instruction from the airline, wherein the subscription instruction is an instruction for the subscriber to view order release records of each airline; In response to the subscription instruction, after detecting the dynamic fare order data released by the airline, the airline order release record is distributed to the subscription end.

5. The method according to claim 4, characterized in that After distributing the airline order release record to the subscriber, it also includes: After detecting that the airline order release record is distributed to the subscriber, a cancellation instruction from the subscriber is received and a cancellation record is output, wherein the termination date of the cancellation record is recorded as the date of sending the cancellation record.

6. The method according to claim 1, characterized in that After generating an airline order release record based on the dynamic freight rate order data, the method further includes: Receive the order number and ticket number sent by the airline; Matching the airline order release record corresponding to the order number; If no airline order release record corresponding to the order number is matched, then the airline order release record corresponding to the ticket number is matched.

7. The method according to claim 1, characterized in that After generating an airline order release record based on the dynamic freight rate order data, the method further includes: Receive the order number or ticket number sent by the airline; Match the airline order release record corresponding to the order number; or, In the case where the order number sent by the airline is not received, the airline order release record corresponding to the ticket number is matched based on the quasi-fare tariff number, airline code, base fare origin city code, base fare destination city code, fare category code, ticketing code, ticket designator or fare amount.

8. The method according to claim 1, characterized in that After generating an airline order release record based on the dynamic freight rate order data, the method further includes: If the order number and ticket number sent by the airline are not received, the corresponding airline order release record is matched based on the quasi-fare tariff number, airline code, base fare origin city code, base fare destination city code, fare category code, ticketing code, ticket designator or fare amount.

9. A dynamic freight rate refund and change operation device, characterized in that: include: An order data receiving unit is used to receive dynamic fare order data issued by various airlines, wherein the dynamic fare order data at least includes: an order identifier field, an order time field, and a base fare field; An order release record generating unit, configured to generate an airline order release record based on the dynamic fare order data, wherein the airline order release record is used to map the base fare before adjustment with the fare after adjustment, and associate the refund and change rules between the fare; The air ticket refund and change operation unit is used to perform the air ticket refund and change operation based on the refund and change rules.

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 dynamic fare refund and change operation method as described in any one of claims 1 to 8.

Images