Airline order data processing method and device

Abstract

The present invention discloses a method and device for processing airline order data, relating to the field of aviation data processing technology. The method comprises: marking order status and performing hierarchical parsing on order data; the hierarchical parsing includes order global information parsing, passenger information parsing, flight segment information parsing, and flight section information parsing; the order status reflects whether the order data has an impact on revenue settlement; based on the order identifier, searching for multiple orders with a parent-child relationship in an order database to construct an order fission mapping relationship; combining the order status, reading target orders that have an impact on revenue settlement from the order database to obtain parsed data corresponding to each passenger in the target order; using the parsed data corresponding to each passenger in the target order to perform order freight rate allocation, order package service disassembly, and order tax splitting, to obtain order allocation and splitting results. The present invention can improve the efficiency, accuracy, and real-time performance of revenue settlement processing for low-cost airlines.

Description

Technical Field

[0001] The present invention relates to the technical field of aviation data processing, and in particular to a method and device for processing airline order data. Background Art

[0002] This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. No statement herein is admitted to be prior art by virtue of its inclusion in this section.

[0003] Currently, the vast majority of full-service airlines primarily utilize a system based on electronic tickets and electronic incidental charges to provide air transportation services and various non-air transportation ancillary services to passengers. The predecessor of this system, paper tickets and incidental charges, has been widely used in the global civil aviation industry since the 1920s. The International Air Transport Association (IATA) has established complex and comprehensive rules governing the entire process of ticket and incidental charge, from sales and use to financial settlement. Since the introduction of computers in the civil aviation revenue settlement field in the 1960s, three generations of management information systems have been developed internationally to manage revenue settlement operations: those based on ticket operation information (uplift base), those based on ticket information first entering the revenue settlement system (primary base), and those based on ticket sales information (salesbase). Today, revenue settlement systems, established based on industry rules and business processes, cover all aspects of revenue settlement operations for full-service airlines.

[0004] However, low-cost airlines have replaced the ticket / fee bill system with a model where all air and non-air services are carried out in one order. Under this low-cost airline order model, the Order Management System (OMS) manages comprehensive information from order sales and payment to the use of air transportation and non-air ancillary services included in the order. This consolidates information management tasks currently distributed across multiple application systems within a full-service airline environment into a single system, enabling airlines to centrally manage upstream and downstream information. Furthermore, the low-cost airline order model does not adhere to the industry rules established by IATA based on the ticket / fee bill system, resulting in significant differences between the processes of low-cost airlines and full-service airlines, from service product sales to revenue settlement.

[0005] The airfare / coupon used by full-service airlines consists of a two-tiered structure: (i) the ticket; and (ii) the coupon. The ticket contains the price and itinerary information for the entire ticket; the coupon includes the itinerary information for a specific leg of the ticket (flight, class, flight date, etc.). Because this two-tiered structure limits the information contained within, air transport services and non-air transport ancillary services must be included in the ticket and coupon, respectively.

[0006] Low-cost airlines generally rely on order management systems to provide their data source. This data covers all services, including sales information and service usage information. It is the sole source of data required to complete revenue settlement processing.

[0007] Full-service airlines, however, rely on numerous sales and usage data sources from numerous upstream systems. Due to the varying data formats and information content of these data sources, their revenue settlement systems, which rely on ticket and incidental fee data as the source of revenue settlement processing, are unable to handle the order-based revenue settlement business of mainstream international low-cost airlines. Existing low-cost airline revenue settlement is primarily handled manually, a method that is both inefficient and prone to errors. Furthermore, as business volume grows, the volume of data required to be processed also increases, placing greater pressure on manual systems and potentially leading to processing backlogs. This results in poor real-time performance of revenue settlement for low-cost airlines, making it difficult to quickly respond to market changes or adjustments to business needs. Summary of the Invention

[0008] An embodiment of the present invention provides an airline order data processing method applicable to low-cost airline order data processing, for improving the efficiency, accuracy, and real-time processing of low-cost airline revenue settlement services. The method includes:

[0009] Receive order data; the order data has an order identifier, and the order identifier includes a parent order identifier and a child order identifier;

[0010] Parse the order data to obtain parsed data, and store the parsed data in the order database; the parsing includes marking the order status and hierarchical parsing; the hierarchical parsing includes parsing global order information, passenger information, flight segment information, and flight segment information; the parsed data includes order status, global order information, passenger information, flight segment information, and flight segment information; the order status reflects whether the order data has an impact on revenue settlement;

[0011] According to the order ID, multiple orders with parent-child relationships are searched in the order database to build an order fission mapping relationship; the order fission mapping relationship is the mapping relationship of all fission orders under the original order;

[0012] Combined with the order status, read the target orders that affect revenue settlement from the order database;

[0013] Obtain the parsed data corresponding to each passenger in the target order using the parsed data of the target order and the order fission mapping relationship including the target order identifier;

[0014] The parsed data corresponding to each passenger in the target order is used to perform order fare allocation, order package service disassembly, and order tax splitting to obtain the order allocation and splitting results; the order allocation and splitting results include: air fare, ancillary service price allocated to each flight segment of the passenger's itinerary, the price of each detailed service in the ancillary service, each detailed service split into each flight node, and taxes split into each flight segment and flight node.

[0015] An embodiment of the present invention further provides an airline order data processing device, which is suitable for processing order data of low-cost airlines and is used to improve the efficiency, accuracy, and real-time processing of revenue settlement services of low-cost airlines. The device includes:

[0016] A data acquisition module is used to receive order data; the order data has an order identifier, and the order identifier includes a parent order identifier and a child order identifier;

[0017] An order information parsing module is used to parse order data, obtain parsed data, and store the parsed data in an order database. The parsing includes marking order status and hierarchical parsing. The hierarchical parsing includes parsing global order information, passenger information, flight segment information, and flight segment information. The parsed data includes order status, global order information, passenger information, flight segment information, and flight segment information. The order status reflects whether the order data has an impact on revenue settlement.

[0018] The fission order identification and processing module is used to search for multiple orders with parent-child relationships in the order database based on the order identifier and build an order fission mapping relationship; the order fission mapping relationship is the mapping relationship of all fission orders under the original order;

[0019] The allocation and splitting processing module is used to read the target order that has an impact on revenue settlement from the order database in combination with the order status; use the parsed data of the target order and the order fission mapping relationship including the target order identifier to obtain the parsed data corresponding to each passenger in the target order; use the parsed data corresponding to each passenger in the target order to allocate the order fare, disassemble the order packaging service and split the order taxes and fees to obtain the order allocation and splitting results; the order allocation and splitting results include: the air fare and ancillary service prices allocated to each flight segment of the passenger's itinerary, the prices of each detailed service in the ancillary service, each detailed service split into each flight node, and the taxes and fees split into each flight segment and flight node.

[0020] An embodiment of the present invention further provides a computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned airline order data processing method when executing the computer program.

[0021] An embodiment of the present invention further provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the computer program implements the above-mentioned airline order data processing method.

[0022] An embodiment of the present invention further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the above-mentioned airline order data processing method.

[0023] In the embodiment of the present invention, after receiving the order data, a mark is printed on it to indicate whether it has an impact on the revenue settlement, and the order global information, passenger information, flight segment information and flight section information are fully analyzed and stored in the order database. An order fission mapping relationship is also constructed so that data will not be missed during the subsequent allocation and splitting. Finally, the target order that has an impact on the revenue settlement is read from the order database, and the parsed data corresponding to each passenger in the target order is used to perform order fare allocation, order package service disassembly and order tax splitting to obtain the order allocation and splitting results. Compared with the manual processing method in the prior art, the embodiment of the present invention is particularly suitable for the revenue settlement business processing of low-cost airlines. Through the order data analysis, order fission mapping relationship construction and order fare allocation, order package service disassembly and order tax splitting processing, the efficiency of the revenue settlement business processing of low-cost airlines and the accuracy of order data allocation and splitting processing are improved. It can also support real-time accounting and can quickly respond to business needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0025] Figure 1 Schematic diagram of the process of processing airline order data according to an embodiment of the present invention;

[0026] Figure 2 This is a diagram showing a specific example of a method for processing airline order data according to an embodiment of the present invention;

[0027] Figure 3 This is a schematic diagram of the airline order data structure in an embodiment of the present invention;

[0028] Figure 4 This is a schematic diagram of airline order data parsing and processing in an embodiment of the present invention;

[0029] Figure 5 This is a schematic diagram of airline order fission in an embodiment of the present invention;

[0030] Figure 6 Schematic diagram of airline order fission identification and processing in an embodiment of the present invention;

[0031] Figure 7 This is a schematic diagram of the airline order rate allocation and packaging service disassembly in an embodiment of the present invention;

[0032] Figure 8 This is a schematic diagram of the splitting of tax and fee information for airline orders in an embodiment of the present invention;

[0033] Figure 9 Schematic diagram of an airline order data processing device in an embodiment of the present invention. DETAILED DESCRIPTION

[0034] To make the purpose, technical solutions and advantages of the embodiments of the present invention more clear, the embodiments of the present invention are further described in detail below with reference to the accompanying drawings. Here, the exemplary embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.

[0035] In order to clearly describe the technical solutions of the embodiments of the present invention, in the embodiments of the present invention, words such as "first" and "second" are used to distinguish between identical or similar items with basically the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order.

[0036] First, the technical terms involved in the embodiments of the present invention are explained.

[0037] 1. Full Service Carrier (FSC): An airline that provides a complete range of services, typically offering multiple cabin classes (such as first class, business class, and economy class), a variety of services, and a full range of services. They cover a wide range of markets, serving both high-end business travelers seeking comfort and leisure travelers. Key characteristics of full-service airlines include:

[0038] Multi-class service: First class, business class and economy class are provided to meet the needs of different passengers;

[0039] Free checked baggage allowance: Usually provides passengers with free checked baggage allowance;

[0040] Free meals on board: Free meals are provided on board.

[0041] 2. Low Cost Carrier (LCC): An airline that eliminates some traditional air passenger services to keep operating costs lower than full-service airlines, allowing it to offer low fares on a large scale over a long period of time. The main characteristics of a low-cost airline include:

[0042] Operating Cost Control: Low-cost airlines achieve cost leadership by effectively controlling various costs. This includes using a single aircraft type, reducing non-essential services, adopting a direct sales model, and increasing cabin density.

[0043] Simplified service: To reduce operating costs, low-cost airlines usually do not provide free meals, charge extra for checked baggage, and may charge for seat selection. In addition, they usually do not have first class and business class, but only provide economy class services.

[0044] Direct sales model: Low-cost airlines primarily sell directly through their websites and call centers, eliminating intermediary costs. This model not only reduces costs but also provides more flexible service options.

[0045] 3. Electronic Ticket (ET), Electronic Miscellaneous Document (EMD): Full-service airlines' services are primarily divided into air transport services and non-aviation ancillary services. Electronic tickets and electronic miscellaneous documents are typically used as vouchers for air transport and various ancillary services, respectively.

[0046] 4. Low-cost airline order (Order or Booking): The transportation services and various additional services provided by most international low-cost airlines are all carried by the order as the only certificate. There is no longer the concept of air tickets and miscellaneous fee invoices used by full-service airlines. One order can include all air transportation and non-air transportation services for multiple passengers.

[0047] 5. Packaged Services: Full-service airlines typically include the necessary free checked baggage allowance and in-flight meals as part of their air transportation services. Low-cost airlines, on the other hand, offer additional services beyond basic air transportation, such as checked baggage and in-flight meals, as ancillary services. Therefore, ancillary service revenue accounts for a significantly larger proportion of low-cost airlines' than full-service airlines. When a passenger purchases multiple ancillary services, low-cost airlines typically offer a package price that includes all selected air transportation and various ancillary services. This package price is typically lower than purchasing each service individually. Low-cost airline orders include the services provided and the total price of the package. During revenue settlement, for refined management, packaged services must be broken down so that revenue can be recognized separately for each service, providing a complete and accurate picture of the profit contribution of each service to the airline.

[0048] 6. Itinerary: The entire journey from departure to arrival, including the departure point, destination, and stops along the way. An itinerary consists of one or more flight segments.

[0049] 7. Segment: This refers to the flight process from the departure airport to the destination airport. From the passenger's perspective, a segment describes the components of a passenger's itinerary. Each segment consists of one or more flight segments.

[0050] 8. Leg: This refers to the flight operations from one scheduled departure station to the next scheduled arrival station. A leg describes the actual portion of an aircraft's flight from a flight operations perspective.

[0051] Current ICAO industry regulations stipulate that air ticket / charge sheet data utilize a two-tier structure: ticket and coupon. Ticket information includes the ticket price and all itinerary information; coupon information includes itinerary information for a specific leg within the ticket (flight, class, flight date, etc.). Due to the limited information contained in this two-tier structure, air transport services and non-air transport ancillary services must be represented by the ticket and charge sheet, respectively. Low-cost airline orders, however, are the source of all revenue settlement data, encompassing orders, all passengers, flight segments, and flight sections within the order. This data format and structure differ from ticket / charge sheet data. Therefore, revenue settlement systems built on this two-tiered ticket / charge sheet structure struggle to process low-cost airline order data. Low-cost airlines typically process this data manually, a method that is both inefficient and error-prone. At the same time, as business volume grows, the amount of data that needs to be processed also increases accordingly, which will put greater pressure on the manual system and may lead to processing backlogs, resulting in poor real-time revenue settlement for low-cost airlines and difficulty in quickly responding to market changes or adjustments to business needs.

[0052] To this end, the embodiment of the present invention has designed a new method that can parse the data of the order management system of international mainstream low-cost airlines, including parsing the order data of low-cost airlines, disassembling the various aviation and non-aviation service package products in the order, and allocating (splitting) the value of various services and taxes to each flight segment / knot, laying the foundation for the subsequent completion of low-cost airline revenue settlement.

[0053] Figure 1 FIG. 1 is a flow chart of a method for processing airline order data according to an embodiment of the present invention. Figure 1 As shown, the method includes:

[0054] Step 101: Receive order data; the order data has an order ID, which includes a parent order ID and a child order ID;

[0055] Step 102: Parse the order data to obtain parsed data, and store the parsed data in an order database; the parsing includes marking the order status and hierarchical parsing; the hierarchical parsing includes parsing global order information, passenger information, flight segment information, and flight segment information; the parsed data includes order status, global order information, passenger information, flight segment information, and flight segment information; the order status reflects whether the order data has an impact on revenue settlement;

[0056] Step 103: Search the order database for multiple orders with a parent-child relationship based on the order identifier, and construct an order fission mapping relationship; the order fission mapping relationship is a mapping relationship of all fission orders under the original order;

[0057] Step 104: Read target orders that have an impact on revenue settlement from the order database based on the order status;

[0058] Step 105: Obtain the parsed data corresponding to each passenger in the target order using the parsed data of the target order and the order fission mapping relationship including the target order identifier;

[0059] Step 106: Use the parsed data corresponding to each passenger in the target order to perform order fare allocation, order package service disassembly, and order tax splitting to obtain the order allocation and splitting results; the order allocation and splitting results include: air fare, auxiliary service price allocated to each flight segment of the passenger's itinerary, the price of each detailed service in the auxiliary service, each detailed service split into each flight node, and taxes split into each flight segment and flight node.

[0060] It can be seen that the low-cost airline order data processing method in the embodiment of the present invention is mainly divided into the following four parts:

[0061] (1) Order data analysis;

[0062] (2) Order fission identification;

[0063] (3) Disassembly of various aviation and non-aviation service packaged products in the order;

[0064] (4) The value of various services and taxes is allocated (split) to each flight segment / knot.

[0065] The following describes in detail a method for processing low-cost airline order data in an embodiment of the present invention.

[0066] Figure 2 FIG is a specific example of the airline order data processing method according to an embodiment of the present invention, referring to Figure 2 According to the low-cost airline order data processing method of the embodiment of the present invention, a low-cost airline revenue settlement system is proposed. The system receives order data and performs the following processing:

[0067] (1) Identification of order addition / change status;

[0068] (2) Order information analysis;

[0069] (3) Identification of order fission, disassembly of aviation and non-aviation services, and allocation of freight rates / taxes / ancillary service values;

[0070] (4) Store the processed data in the order database.

[0071] During specific implementation, in step 101, order data is first obtained.

[0072] Low-cost airline order data can consist of a four-layer structure: (i) the order; (ii) all passengers in the order; (iii) the flight segments corresponding to each passenger; and (iv) the corresponding flight segments, with information such as the price, taxes, and ancillary services added to the corresponding layers. This four-layer order structure provides greater flexibility and scope to encompass all passengers in the order and all corresponding services (including air transportation and various non-air services), as well as payment and tax information, without requiring any additional information beyond the order itself.

[0073] Figure 3 This is a schematic diagram of the airline order data structure in an embodiment of the present invention, referring to Figure 3 , order data obtained can include: the first level of orders, including all passengers under the order and all corresponding services; the second level of passengers, including the itineraries and all services of all passengers under the order; the third level of itinerary segments, including the specific information, fares, taxes and ancillary service information of each segment in the itinerary; the fourth level of flight segment information, including the information of each flight segment in the flight segment.

[0074] The order data has an order number, which is the unique identifier of the order and will remain unchanged. No matter how the information in the order changes subsequently, the order number / order ID will not change. After the order is created, any subsequent voluntary or involuntary changes to the information in the order, such as changes in flight information, order amount, itinerary, auxiliary services, passenger boarding status, etc., are considered order changes. Whenever a new order is created or the information of a previously created order changes, the order management system configured in the embodiment of the present invention transmits the current latest information of the order and the historical information of the order to the downstream revenue settlement system (the system of the embodiment of the present invention or the method of the embodiment of the present invention) for subsequent processing. In the embodiment of the present invention, the revenue settlement processing is subsequently completed by identifying the information that changes each time an order is created.

[0075] In step 102, the order data is parsed to obtain parsed data, which is then stored in an order database; the parsing includes marking order status and hierarchical parsing.

[0076] In the embodiment, the order status reflects whether the order data has an impact on the revenue settlement. The hierarchical analysis includes Figure 3 The order data structure shown performs order global information parsing, passenger information parsing, flight segment information parsing and flight section information parsing.

[0077] The order status is used to identify whether the order data received this time has an impact on revenue settlement, thereby determining whether the order data will be processed for revenue settlement in the future. Through layered analysis, detailed information about order sales, payment, passengers, flight distance, flight segments, and flight nodes in the order data is obtained.

[0078] In one embodiment, the order data further includes an order version number and a history record code. The order version number reflects the number of times the information in the order has been changed, and the history record code reflects the specific content of a single change in the order.

[0079] The order history records complete information about order changes that occur sequentially throughout the order's lifecycle, starting from its initial creation. Each order change is tagged with a unique version number. When an order is created, its version number is 1, and it increments by 1 with each subsequent change. The order history also stores the time (in the form of a timestamp) of each order change. This history is crucial for identifying the content of each order change and determining the appropriate approach for subsequent revenue settlement. As mentioned earlier, an order contains four levels of information, carrying information about all air transport and non-air transport ancillary services. Within the order history information provided by the upstream order management system, each type of order change is assigned a unique "history code." By reading this history code, the specific content of each order change can be determined. During revenue settlement processing, it is necessary to identify the history code that appears in the order and determine whether the change impacts revenue settlement. Using the order history code, order changes that impact revenue settlement can be identified, allowing for the appropriate revenue settlement processing.

[0080] Step 102 parses the order data to obtain parsed data, which may include: marking the order status of the order data using the order version number and the history record code.

[0081] Use the order version number and history code to mark the order status of the order data, which can further include:

[0082] When the order version number reflects that the number of times the order information has been changed is 0, the order status of the order data is marked as a new order and is related to revenue settlement;

[0083] When the order version number reflects that the number of times the information in the order has been changed is greater than 0, the historical record code in the order data is obtained, and the historical record code in the order data is matched with the first preset reference file. When the match is successful, the order status of the order data is marked as a changed order but related to revenue settlement, or a changed order but not related to revenue settlement according to the matching result; the first preset reference file stores a historical record code field that affects revenue settlement.

[0084] For example, after receiving order data from the upstream order management system, the revenue settlement system in this embodiment of the present invention begins to verify the accuracy of the "order version number, history code, and timestamp" in the order. If the "order version number, history code, and timestamp" are correct, the order version number is used to determine whether the order is a new order (order version number is 1) or a previously established order with information changed (order number greater than 1). For a small number of orders with missing or inaccurate "order version number, history code, and timestamp", the received order data is compared with the order information of the same order number already stored in the order database to determine whether the newly received order is a new order or a changed order.

[0085] If it is a new order, it will be marked as "new order" on the order. Since all new orders need to be processed for revenue settlement, this type of order needs to be marked as "new order and related to revenue settlement" and then saved in the order database;

[0086] If the order has changed information, it's necessary to determine whether the change affects revenue settlement (this is determined by comparing the "Historical Information Code Affecting Revenue Settlement" in the first preset reference file in the revenue settlement system). If the order change has no impact on revenue settlement, the order is marked "Changed Order but Not Related to Revenue Settlement" and saved to the order database. This "Order Change" information is only used for information storage and query purposes and is not included in subsequent revenue settlement processing. If the order change does affect revenue settlement, the order is marked "Changed Order and Related to Revenue Settlement" and saved to the order database.

[0087] Through the above processing, orders are classified according to the "new" and "changed" status, and orders that need to be processed for revenue settlement and those that do not need to be processed for revenue settlement are marked with different labels respectively, and then enter the subsequent "order information analysis" link.

[0088] Figure 4 FIG. 1 is a schematic diagram of airline order data parsing and processing in an embodiment of the present invention. Figure 4 As shown, order information identification and parsing is mainly divided into five parts:

[0089] (1) Temporary storage: After receiving the order data sent by the upstream, the order data is first temporarily stored in a temporary database for subsequent processing;

[0090] (2) Read the order data from the temporary database and verify the accuracy of order information such as the order version number, historical record code, and timestamp; if the verification is wrong, compare the order information with the order history record and then make an order status judgment; if the verification is correct, make an order status judgment;

[0091] (3) Order status judgment: judge whether new orders or changes are made, and analyze the historical record code in the order history information to determine whether it affects the revenue settlement;

[0092] (3) Marking: According to Figure 4 In the middle process, mark the order status according to the judgment result;

[0093] (4) Order information analysis: hierarchical analysis according to the order data structure;

[0094] (5) Persistent storage: Save order data to the order database.

[0095] Table 1 below illustrates the relationship between the historical record code and the "whether it affects income settlement" flag in the first preset reference file.

[0096] Table 1

[0097]

[0098] In one embodiment, when the order version number indicates that the number of times the order information has been changed is greater than 0, the method may further include:

[0099] When the historical record code in the order data cannot be obtained, or the historical record code in the order data fails to match the first preset reference file, comparing the order identifier in the received order data with the order identifier in the order database;

[0100] When there is no order with the same order ID in the order database, the order status of the order data is marked as a new order and is related to revenue settlement;

[0101] When an order with the same order ID exists in the order database, the set key fields of the received order data are compared with the order data with the same order ID in the order database. Based on the comparison result, the order status of the order data is marked as a changed order but related to revenue settlement, or a changed order but not related to revenue settlement.

[0102] This embodiment takes into account the situation where the historical record code fails to match the first preset reference file, or the historical record code is not obtained. For example, the received order information is compared with the order information with the same order ID already stored in the order database. The comparison steps are as follows:

[0103] Step 1: Configure the key field information in the order and load the set key field information into the revenue settlement system server memory.

[0104] Step 2: Calculate the incoming order data based on the specified key fields to form set T. Then, read the data from the order database to form set R, and convert the order data comparison into a set operation. The data in the result set of the difference operation between sets T and R represents order data that did not previously exist and is newly added, and is marked as newly added. The data in the result set of the intersection operation between sets T and R represents order data that previously existed. If the key fields have changed, the change is marked as relevant to revenue settlement; otherwise, it is marked as unrelated to revenue settlement.

[0105] After the order status is marked, the order information parsing phase begins. When parsing order information, it follows the four-layer structure of the order. The first layer identifies and parses the global order information, including order ID, order sales, and payment information. The second layer identifies and parses all passenger information under the order, including each passenger's ID, passenger taxes, and other information. The third layer identifies and parses all air transport and ancillary service information under each passenger, including the ID of each air transport flight, the origin and destination information of the flight, each ancillary service, and the corresponding amount information. The fourth layer identifies and parses all flight segment information under each flight segment, including the ID of each flight segment, the specific flight and carrier status of the flight segment, and other information. Finally, the parsed order information is stored in the order database at different levels.

[0106] Order hierarchical analysis is mainly divided into four parts: order global information analysis, passenger information analysis, flight segment information analysis, and flight section information analysis. The key points of each level of analysis are as follows:

[0107] Global layer: Use JSONPath to extract key fields, including order ID, order sales, and payment.

[0108] Passenger layer: Loop through the array structure to establish a mapping between order ID and passenger ID;

[0109] Segment layer: Parse the nested JSON objects to build multi-level relationships between segment IDs and passenger IDs;

[0110] Node layer: time series data processing, recording the association between node ID and segment ID, etc.

[0111] In step 103, based on the order identifier, multiple orders with a parent-child relationship are searched in the order database to construct an order fission mapping relationship; the order fission mapping relationship is a mapping relationship of all fission orders under the original order.

[0112] In the embodiment of the present invention, it is considered that the orders of low-cost airline companies have the characteristics of order fission. Figure 5 , Figure 5 This is a schematic diagram of airline order fission in an embodiment of the present invention. Figure 5 In the example, Order 1 initially contains 9 passengers. After the first split into Order 2, Order 1 still retains 4 passengers. After the second split into Order 3, Order 1 still retains 3 passengers. And so on. If an order contains multiple passengers, this order can be subsequently split into several sub-orders, and each sub-order can be further split into several grand-orders... This provides full flexibility for different passengers in the original order in selecting various services and travel freedom.

[0113] An order of a low-cost airline can include multiple passengers. If some passengers in the same order need to change their service content or request to leave the original order, the airline can split these passengers in the original order into a new order in the order management system, and display the latest information of these passengers in the new order. The original order is called the parent order, and the new order split from the parent order is called the child order. The child order will create a new order ID in the order management system, and the child order will carry the order ID of the parent order; the child order can continue to split into several grandchild orders, and the grandchild order will also have its own order ID. Similarly, the grandchild order will carry the order ID of the previous level sub-order; the grandchild order can continue to split downward until there is only one passenger left in the order.

[0114] In one embodiment, based on the order identifier, multiple orders with a parent-child relationship are searched in the order database to construct an order fission mapping relationship, which may include: for any order, determining whether the parent order ID of the order is empty; if the parent order ID of the order is empty, taking the order as the original order; if the parent order ID of the order is not empty, determining that the order is a child order, and searching the order database for orders with the same parent order ID as the child order identifier until the parent order ID of the searched order is empty, and finally, constructing the order fission mapping relationship.

[0115] For example, when the order data of a low-cost airline is transmitted from the upstream order management system to the downstream revenue settlement system, the revenue settlement system needs to identify the fission orders in the order data and establish mapping relationships between parent orders and child orders, and child orders and grandchild orders.

[0116] Figure 6 This is a schematic diagram of airline order fission identification processing in an embodiment of the present invention, referring to Figure 6The method for identifying order fission is to judge the parent-child order ID information in each order, thereby determining the parent order and child order, and setting the "order fission" mark on the order that has undergone fission, and continue to trace it back to the original parent order of the order. The method for parsing order fission is to use the parent order ID on the child order to search the order database for the same order ID and if the parent order ID on the order is empty, it means that the order is a child order and the first fission of the parent order, and no subsequent search will be performed; if the same order ID can be found and the parent order ID on the order is not empty, it means that the previous level order of the order still has order fission, and such orders are marked with "order fission", and then continue to search upward according to the above method until an order with an empty parent order ID is found. After completing the parsing of the order fission data, a mapping relationship is established for all fission orders under an order in the order database for subsequent revenue settlement processing.

[0117] Step 104: Based on the order status, read the target order that has an impact on revenue settlement from the order database.

[0118] For example, orders that have not yet been allocated freight rates, services, and taxes are sequentially read from the order database.

[0119] In step 105, the parsed data of the target order and the order fission mapping relationship including the target order identifier are used to obtain the parsed data corresponding to each passenger in the target order.

[0120] Through the aforementioned preliminary preparation of order data, the analytical data corresponding to each passenger in the target order is obtained, including the full amount of flight-related information.

[0121] In step 106, the parsed data corresponding to each passenger in the target order is used to perform order fare allocation, order package service disassembly, and order tax splitting to obtain the order allocation and splitting results; the order allocation and splitting results include: air fares, auxiliary service prices allocated to each flight segment of the passenger's itinerary, prices of each detailed service in the auxiliary service, each detailed service split into each flight node, and taxes split into each flight segment and flight node.

[0122] In one embodiment, using the parsed data corresponding to each passenger in the target order to allocate the order fare may include:

[0123] Using the flight segment information of the same passenger, determining whether the passenger's flight is a direct flight or a connecting flight; a connecting flight means that the entire flight is carried by different flights;

[0124] When the passenger's flight is a direct flight, the fare of the direct flight will be used as the air fare allocation result;

[0125] When the passenger's flight is a connecting flight, all the segments in the passenger's flight information are spliced in order to form the entire flight, and the total fare of all segments is allocated according to the distance of each segment.

[0126] In one embodiment, the flight segment information includes auxiliary service information for each flight segment; order packaging services are decomposed using the parsed data corresponding to each passenger in the target order, which may include:

[0127] Matching the ancillary service information for each flight segment with a second preset reference file to determine the price of each detailed service in the ancillary service for each flight segment and whether it is within the validity period; the second preset reference file includes reference information on various ancillary service items;

[0128] The price of each detailed service is allocated to the flight node level according to the distance of each flight node under the flight segment.

[0129] Figure 7 This is a schematic diagram of the airline order rate allocation and packaging service disassembly in an embodiment of the present invention, refer to Figure 7 Orders that haven't yet been allocated and service decomposition are sequentially read from the order database. Each passenger's itinerary information for eligible orders is retrieved, and the itinerary type is determined. If the route is a direct flight (a direct flight is a flight from point A to point B, with multiple stops, but the flight number remains the same), the fare for that segment is used as the allocation result. If the route is a connecting flight (a connecting flight is an entire flight operated by different flight numbers or by different airlines), the segments associated with the connecting flights are combined to form the entire itinerary. The fares for each segment are then aggregated and allocated to each segment based on their distance (the distance of each segment is obtained from the "segment distance reference information" pre-maintained in the revenue settlement system). Once the fare allocation is complete, each segment receives the packaged service price for its air transportation and non-air transportation ancillary services. The packaged services are then broken down into their individual services, and the value of each service is determined. When unpacking packaged services, the packaged service information is compared with the detailed service characteristics in a predefined second reference file within the revenue settlement system, identifying each detailed service and its corresponding value. After completing the segment-level service unpacking, the value of each service is further allocated to the segment level based on the distance between each flight knot within that segment. This way, the value of each service provided within the flight knot, the smallest unit of service provided, is captured. Subsequent service consumption allows for revenue recognition.

[0130] The basic concept behind order rate allocation is to allocate the packaged service amount to the flight segments based on the different types of low-cost airline order data. This yields an allocated amount for each segment, which serves as the basis for subsequent packaged service decomposition, airline revenue recognition, and accounting. In this embodiment of the present invention, the distance between the origin and destination is used as the basis for allocating the amount. Using distance as the basis requires access to external data recording the distances of each flight segment / knot as a reference.

[0131] The order freight rate allocation logic is as follows:

[0132] 1. Target data: all order data for which freight rate allocation has not been successfully completed;

[0133] 2. Target search and flight path splicing:

[0134] (1) Find the corresponding data in the passenger information table according to the order ID in the order database and obtain the corresponding passenger ID.

[0135] (2) Use the passenger ID to find the corresponding flight segment data in the flight segment information table.

[0136] (3) Find the flight segment data of the same passenger ID, check the value of its "flight type", and determine whether it is a "connecting flight" or a "direct flight"; Figure 3 The basic structure of order data is only shown in the figure. Each layer of order data contains a lot of data, which cannot be displayed in the figure. Figure 3 For example, the third-level flight segment layer may include flight type, aircraft type, departure station, departure date, booking status, etc. When the flight type value is 4, it is a "connecting flight", and the rest of the values are "non-stop flights".

[0137] (4) For the flight segment records under the same passenger ID, find all the flight segments that need to be apportioned, and then find the flight segments with the same "connecting flight" ID. Such flight segments belong to the same flight and are spliced into a group to wait for apportionment. At the same time, write the value of the order ID + passenger ID + flight ID of such a group of flight segments under the apportionment ID field.

[0138] (5) For data with the same allocation ID and allocation status of "not yet successfully allocated", write the "origin" and "destination" into the "voyage to be allocated" field in the order of the flight segments to splice out the entire flight.

[0139] (6) Obtain the distance of the entire voyage by reading the “Velocity / Knot Distance Reference Information”.

[0140] For example, for flight segment records under the same passenger ID, all segments requiring apportionment are identified. Then, segments with the same "Flight Number" value are searched for. These segments belong to the same journey and are grouped together for apportionment. After successful apportionment, the system sets the "Needs Apportionment" flag to "Y." This allows subsequent apportionment to be performed only on segments with a non-Y "Needs Apportionment" flag. For all segments found, the departure and arrival station fields (both 3-character STATION fields) are written to the "Flight" field in segment order, removing any adjacent duplicate STATIONs.

[0141] 3. Apportionment calculation.

[0142] (1) According to the passenger ID + flight segment ID, find the amount information corresponding to each flight segment in the order, add up the total amount of the entire journey, and use it as the apportionment amount; then use the distance of each flight segment as the apportionment basis, multiply the distance of this flight segment by the distance of the entire journey, and get the apportionment value of this flight segment.

[0143] (2) If the allocation is successful, the allocation status of the order will be set to "Allocation Successful";

[0144] (3) If the information of the amount to be allocated is missing or the information of the flight segment distance is missing, the allocation status is set to "Allocation Error" and the reason for the allocation error is recorded in the Allocation Error field;

[0145] (4) For orders with allocation errors, an error correction function is provided for front-end users to modify them. The modified order information will continue to be allocated until the allocation is successful.

[0146] The basic idea behind packaged service decomposition is as follows: 1) Packaged service decomposition is performed after the freight rates of the order data are allocated; 2) When decomposing packaged services, it is necessary to obtain the pricing of various services by comparing the external data of the "service characteristic reference information" recorded in the second preset reference file; 3) The scope of packaged service decomposition is carried out in each flight segment, decomposing the value of the air transport services and the value of various non-air transport services in each flight segment.

[0147] Packaging service disassembly logic:

[0148] 1. For the flight segments that have completed the apportionment process, match the "Service Product Code" information in the flight segment with the "Service Characteristics Reference Information" recorded in the second preset reference file to preliminarily find the target range;

[0149] 2. Use the target range found in step 1 to find the corresponding "aircraft type" information for the flight segment and compare it with the "service characteristics reference information" to further narrow the target range;

[0150] 3. Use the narrowed target range found in step 2 to continue checking whether it is within the "Validity Period" range of the "Service Feature Reference Information" so as to eliminate invalid values and continue to narrow the target range;

[0151] 4. Using the results obtained in the first three steps, continue matching the "flight direction", "trip type", and "knot restriction" information. The flight direction reference information maintains directional restrictions on the trip. A value of A indicates "trip information and flight direction are both met", and a value of B indicates "as long as the trip information is met, the flight direction is not required". For example, if the information maintained in the second preset reference file is city 1-city 2, and the flight direction is required to be from city 1 to city 2, then if the trip is "city 1-city 2" but the flight direction is "city 2-city 1", it does not meet the requirement. Conversely, if the information maintained in the second preset reference file is city 1-city 2, and there is no restriction on the flight direction, then the trip can be "city 1-city 2" or "city 2-city 1", both of which meet the requirement. The knot restriction indicates whether more than one knot is allowed in the trip. "Allow" or "Not Allowed" can be maintained in the second preset reference file. The system compares the actual data with the second preset reference file to determine whether there is a match.

[0152] Complete the above four steps to locate the detailed service information. Then, extract the value of the service from the "Service Characteristics Reference Information." When extracting the packaged services, consider the priority order of each service defined in the "Service Characteristics Reference Information" external data. The allocated amount for the flight segments needs to be broken down according to the priority order of each service.

[0153] For example, for the flight segment "City 1-City 2," the "Packaged Service Price to be Split" is 120, and the "Service Product Code" is AA. Based on the data maintained in the second preset reference file, n pieces of auxiliary service data with "Service Product Code" = AA are matched. Using aircraft model information, sale date, flight direction, and flight type, the x pieces of auxiliary service data that meet the criteria are filtered out and the amount splitting begins:

[0154] Priority 1, the corresponding auxiliary service type is food type 1, and the price is 34. 34 is allocated to food type 1, and the remaining package service price is 120-34=86;

[0155] Next, find the next priority 3 auxiliary service type, which is Comfort Package 1 and has a price of 18. Then, allocate 18 to the Comfort Package, and the remaining package service price is 86-18=68.

[0156] And so on, complete the packaged service disassembly.

[0157] In one embodiment, using the parsed data corresponding to each passenger in the target order to perform order tax splitting may include:

[0158] Obtain tax information for each passenger from the parsed data corresponding to each passenger in the target order;

[0159] Determining the tax type of each passenger based on the comparison of each passenger's tax information with a third preset reference file; the tax type includes general taxes and penalty taxes;

[0160] For general taxes and fees, the taxes and fees are allocated to each leg of the voyage based on the voyage corresponding to the taxes and fees in the order data.

[0161] For penalty taxes and fees, allocate the penalty taxes and fees to the passenger's cancelled flight segments;

[0162] The amount of each tax is allocated to the flight knot level according to the distance of each flight knot under the flight segment.

[0163] In one embodiment, the parsed data corresponding to each passenger in the target order is used to perform order freight allocation, order packaging service disassembly, and order tax splitting. After obtaining the order parsing and splitting results, the method may further include: marking a parsing status identifier for the target order based on the order parsing and splitting results; the parsing status identifier includes allocation success, allocation error and reason, tax splitting success, tax splitting error and reason.

[0164] Figure 8 This is a schematic diagram of the tax information splitting of airline orders in an embodiment of the present invention, refer to Figure 8 Orders that haven't yet been tax-split are sequentially read from the order database. The tax information for each passenger in the eligible order is then retrieved. This tax information is compared with the external data ("Industry Tax Reference Information") stored in the third preset reference file in the revenue settlement system to determine the tax type. If it's a general tax, the tax is allocated to the corresponding flight segment based on the flight distance information in the order. If it's a penalty tax (low-cost airlines often charge a penalty fee when a passenger cancels all or part of an already-sold order), the penalty is allocated to the canceled flight segment to ensure complete input recognition (the penalty fee is also considered input). After completing the segment-level tax split, the tax amount is further apportioned to the flight segment level based on the distance between each flight segment. This way, the flight segment, as the smallest unit of service provided, provides the tax amount for that flight segment, facilitating subsequent revenue settlement processing.

[0165] The logic for splitting order taxes and fees is as follows:

[0166] 1. Target data: all order data for which tax splitting has not been successfully completed;

[0167] 2. Target search method:

[0168] (1) Find the corresponding data in the passenger information table according to the order ID in the order database and obtain the corresponding passenger ID;

[0169] (2) Use the passenger ID to find all the tax IDs of the passenger;

[0170] (3) By comparing each tax item in the order with the external data of "Tax Reference Information", the tax type information is obtained to determine whether the tax item belongs to "General Tax" or "Penalty Tax";

[0171] (4) For “general taxes and fees”, the tax and fee information shall be allocated to the corresponding flight segments according to the flight segment information recorded in the tax and fee ID information;

[0172] (5) For "penalty taxes and fees", you need to associate the taxes and fees with the old (deleted) records. Based on the origin and destination recorded in the tax and fee ID information, as well as the old flight segment information, find the old "segments with the same origin and destination" and place the taxes and fees on the old flight segments;

[0173] (6) After the above two types of tax and fee amounts are divided into flight segments, they are further divided into flight nodes according to the distance between each flight node.

[0174] After the tax split is complete, different status indicators (successful or failed) are set based on the split results. For orders where tax splitting fails, a modification function is provided. After modification, the tax split process will continue until it succeeds.

[0175] In summary, the airline order data processing method according to the embodiments of the present invention is particularly suitable for low-cost airlines. It improves the efficiency of revenue settlement processing for low-cost airlines, enhances the accuracy of order data parsing, supports real-time accounting, and enables rapid response to business needs. The order parsing and splitting solution of the present invention can process orders widely used by low-cost airlines, has strong adaptability, and has broad application prospects.

[0176] The present invention also provides an airline order data processing device, as described in the following embodiments. Since the principle of solving the problem of the device is similar to that of the airline order data processing method, the implementation of the device can refer to the implementation of the airline order data processing method, and the repeated parts will not be repeated.

[0177] Figure 9 FIG. 1 is a schematic diagram of an airline order data processing device according to an embodiment of the present invention. Figure 9 As shown, the apparatus 900 includes:

[0178] The data acquisition module 901 is used to receive order data; the order data has an order identifier, and the order identifier includes a parent order identifier and a child order identifier;

[0179] The order information parsing module 902 is used to parse order data, obtain parsed data, and store the parsed data in the order database. The parsing includes marking the order status and performing hierarchical parsing. The hierarchical parsing includes parsing global order information, passenger information, flight segment information, and flight segment information. The parsed data includes order status, global order information, passenger information, flight segment information, and flight segment information. The order status indicates whether the order data has an impact on revenue settlement.

[0180] The fission order identification processing module 903 is used to search the order database for multiple orders with a parent-child relationship based on the order identifier and construct an order fission mapping relationship; the order fission mapping relationship is the mapping relationship of all fission orders under the original order;

[0181] The allocation and splitting processing module 904 is used to read the target order that has an impact on the revenue settlement from the order database in combination with the order status; use the parsed data of the target order and the order fission mapping relationship including the target order identifier to obtain the parsed data corresponding to each passenger in the target order; use the parsed data corresponding to each passenger in the target order to allocate the order fare, disassemble the order packaging service and split the order taxes and fees to obtain the order allocation and splitting results; the order allocation and splitting results include: the air fare, the auxiliary service price allocated to each flight segment of the passenger's itinerary, the price of each detailed service in the auxiliary service, each detailed service split into each flight node, and the taxes and fees split into each flight segment and flight node.

[0182] In one embodiment, the order data further includes an order version number and a history code. The order version number reflects the number of times the information in the order has been changed, and the history code reflects the specific content of a single change in the order.

[0183] The order information parsing module 902 is specifically used to mark the order status of the order data using the order version number and the history record code.

[0184] In one embodiment, the order information parsing module 902 is specifically configured to:

[0185] When the order version number reflects that the number of times the order information has been changed is 0, the order status of the order data is marked as a new order and is related to revenue settlement;

[0186] When the order version number reflects that the number of times the information in the order has been changed is greater than 0, the historical record code in the order data is obtained, and the historical record code in the order data is matched with the first preset reference file. When the match is successful, the order status of the order data is marked as a changed order but related to revenue settlement, or a changed order but not related to revenue settlement according to the matching result; the first preset reference file stores a historical record code field that affects revenue settlement.

[0187] In one embodiment, the apparatus 900 further includes:

[0188] an order tag backup processing module, configured to compare the order identifier of the received order data with the order identifier in the order database when the order version number indicates that the number of times the order information has been changed is greater than 0 and when the historical record code in the order data cannot be obtained or the historical record code in the order data fails to match the first preset reference file;

[0189] When there is no order with the same order ID in the order database, the order status of the order data is marked as a new order and is related to revenue settlement;

[0190] When an order with the same order ID exists in the order database, the set key fields of the received order data are compared with the order data with the same order ID in the order database. Based on the comparison result, the order status of the order data is marked as a changed order but related to revenue settlement, or a changed order but not related to revenue settlement.

[0191] In one embodiment, the fission order identification processing module 903 is specifically configured to:

[0192] For any order, determine whether the parent order ID of the order is empty;

[0193] If the parent order ID of the order is empty, the order will be treated as the original order;

[0194] If the parent order ID of the order is not empty, the order is determined to be a child order, and the order database is searched for orders with the same parent order ID as the child order identifier until the parent order ID of the searched order is empty, and the order fission mapping relationship is constructed.

[0195] In one embodiment, the allocation and splitting processing module 904 is specifically configured to:

[0196] Using the flight segment information of the same passenger, determining whether the passenger's flight is a direct flight or a connecting flight; a connecting flight means that the entire flight is carried by different flights;

[0197] When the passenger's flight is a direct flight, the fare of the direct flight will be used as the air fare allocation result;

[0198] When the passenger's flight is a connecting flight, all the segments in the passenger's flight information are spliced in order to form the entire flight, and the total fare of all segments is allocated according to the distance of each segment.

[0199] In one embodiment, the flight segment information includes auxiliary service information of each flight segment;

[0200] The allocation and splitting processing module 904 is specifically used to:

[0201] Matching the ancillary service information for each flight segment with a second preset reference file to determine the price of each detailed service in the ancillary service for each flight segment and whether it is within the validity period; the second preset reference file includes reference information on various ancillary service items;

[0202] The price of each detailed service is allocated to the flight node level according to the distance of each flight node under the flight segment.

[0203] In one embodiment, the allocation and splitting processing module 904 is specifically configured to:

[0204] Obtain tax information for each passenger from the parsed data corresponding to each passenger in the target order;

[0205] Determining the tax type of each passenger based on the comparison of each passenger's tax information with a third preset reference file; the tax type includes general taxes and penalty taxes;

[0206] For general taxes and fees, the taxes and fees are allocated to each leg of the voyage based on the voyage corresponding to the taxes and fees in the order data.

[0207] For penalty taxes and fees, allocate the penalty taxes and fees to the passenger's cancelled flight segments;

[0208] The tax amount is allocated to the flight node level based on the distance of each flight node under the flight segment.

[0209] In one embodiment, the apparatus 900 may further include:

[0210] The parsing status identification processing module is used for the allocation and splitting processing module 904 to use the parsing data corresponding to each passenger in the target order to allocate the order freight, split the order packaging service and split the order taxes and fees. After obtaining the order allocation and splitting results, the parsing status identification is marked for the target order according to the order allocation and splitting results; the parsing status identification includes allocation success, allocation error and reason, tax splitting success, tax splitting error and reason.

[0211] An embodiment of the present invention further provides a computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned airline order data processing method when executing the computer program.

[0212] An embodiment of the present invention further provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the computer program implements the above-mentioned airline order data processing method.

[0213] An embodiment of the present invention further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the above-mentioned airline order data processing method.

[0214] In the embodiment of the present invention, after receiving the order data, a mark indicating whether it has an impact on revenue settlement is printed on it, and the order global information, passenger information, flight segment information and flight section information are fully parsed and stored in the order database. An order fission mapping relationship is also constructed so that data will not be missed during subsequent allocation and splitting. Finally, the target order that has an impact on revenue settlement is read from the order database, and the parsed data corresponding to each passenger in the target order is used to perform order fare allocation, order package service disassembly and order tax splitting to obtain the order allocation and splitting result. Compared with the manual processing method in the prior art, the processing of order data parsing, order fission mapping relationship construction and order fare allocation, order package service disassembly and order tax splitting improves the revenue settlement business processing efficiency of low-cost airlines, improves the accuracy of order data allocation and splitting processing, and can also support real-time accounting, so as to quickly respond to business needs.

[0215] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

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

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

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

[0219] The specific embodiments described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for processing airline order data, characterized in that: include: Receive order data; The order data has an order ID, which includes a parent order ID and a child order ID; An order includes all air transport and non-air transport services for multiple passengers. The order data consists of a four-layer structure: (i) the order, (ii) all passengers in the order, (iii) the flight segments corresponding to each passenger, and (iv) the flight segment information corresponding to each flight segment. The amount, taxes, fees, and ancillary services information are supplemented in the corresponding layers. The order data has an order number, which is the unique identifier of the order and remains unchanged. The order data also has an order version number and a history code. The order version number reflects the number of times the information in the order has been changed, and the history code reflects the specific content of a single change to the order. Parse the order data to obtain parsed data, and store the parsed data in the order database; The analysis includes marking order status and hierarchical analysis; the hierarchical analysis includes order global information analysis, passenger information analysis, flight segment information analysis, and flight segment information analysis; the analysis data includes order status, order global information, passenger information, flight segment information, and flight segment information; the order status reflects whether the order data has an impact on revenue settlement; the order status includes newly added order and related to revenue settlement, changed order but related to revenue settlement, or changed order but not related to revenue settlement; According to the order ID, multiple orders with parent-child relationships are searched in the order database to build an order fission mapping relationship; The order fission mapping relationship is the mapping relationship of all fission orders under the original order; Combined with the order status, read the target orders that affect revenue settlement from the order database; Obtain the parsed data corresponding to each passenger in the target order using the parsed data of the target order and the order fission mapping relationship including the target order identifier; Use the parsed data corresponding to each passenger in the target order to allocate the order freight, split the order packaging services, and split the order taxes and fees to obtain the order allocation and split results; The order allocation and splitting results include: air fares and ancillary service prices allocated to each flight segment of the passenger's itinerary, the prices of each detailed service in the ancillary services, each detailed service split into each flight node, and taxes split into each flight segment and flight node.

2. The method according to claim 1, wherein Parse the order data to obtain parsed data, including: Use the order version number and history code to mark the order status of the order data.

3. The method according to claim 2, wherein Use the order version number and history code to mark the order status of the order data, including: When the order version number reflects that the number of times the order information has been changed is 0, the order status of the order data is marked as a new order and is related to revenue settlement; When the order version number reflects that the number of times the information in the order has been changed is greater than 0, the historical record code in the order data is obtained, and the historical record code in the order data is matched with the first preset reference file. When the match is successful, the order status of the order data is marked as a changed order but related to revenue settlement, or a changed order but not related to revenue settlement according to the matching result; the first preset reference file stores a historical record code field that affects revenue settlement.

4. The method according to claim 3, wherein When the order version number reflects that the number of times the order information has been changed is greater than 0, it also includes: When the historical record code in the order data cannot be obtained, or the historical record code in the order data fails to match the first preset reference file, comparing the order identifier in the received order data with the order identifier in the order database; When there is no order with the same order ID in the order database, the order status of the order data is marked as a new order and is related to revenue settlement; When an order with the same order ID exists in the order database, the set key fields of the received order data are compared with the order data with the same order ID in the order database. Based on the comparison result, the order status of the order data is marked as a changed order but related to revenue settlement, or a changed order but not related to revenue settlement.

5. The method according to claim 1, wherein Based on the order ID, multiple orders with parent-child relationships are searched in the order database to build an order fission mapping relationship, including: For any order, determine whether the parent order ID of the order is empty; If the parent order ID of the order is empty, the order will be treated as the original order; If the parent order ID of the order is not empty, the order is determined to be a child order, and the order database is searched for orders with the same parent order ID as the child order identifier until the parent order ID of the searched order is empty, and the order fission mapping relationship is constructed.

6. The method according to claim 1, wherein Use the parsed data corresponding to each passenger in the target order to allocate the order freight, including: Using the flight segment information of the same passenger, determining whether the passenger's flight is a direct flight or a connecting flight; a connecting flight means that the entire flight is carried by different flights; When the passenger's flight is a direct flight, the fare of the direct flight will be used as the air fare allocation result; When the passenger's flight is a connecting flight, all the segments in the passenger's flight information are spliced in order to form the entire flight, and the total fare of all segments is allocated according to the distance of each segment.

7. The method according to claim 6, wherein The flight segment information includes auxiliary service information of each flight segment; Use the parsed data corresponding to each passenger in the target order to perform order packaging service disassembly, including: Match the ancillary service information of each flight segment with the second preset reference file to determine the price of each detailed service in the ancillary service of each flight segment and whether it is within the validity period; The second preset reference file includes reference information of various auxiliary service items; The price of each detailed service is allocated to the flight node level according to the distance of each flight node under the flight segment.

8. The method according to claim 1, wherein Use the parsed data corresponding to each passenger in the target order to split the order tax, including: Obtain tax information for each passenger from the parsed data corresponding to each passenger in the target order; Determining the tax type of each passenger based on the comparison of each passenger's tax information with a third preset reference file; the tax type includes general taxes and penalty taxes; For general taxes and fees, the taxes and fees are allocated to each leg of the voyage based on the voyage corresponding to the taxes and fees in the order data. For penalty taxes and fees, allocate the penalty taxes and fees to the passenger's cancelled flight segments; The tax amount is allocated to the flight node level based on the distance of each flight node under the flight segment.

9. The method according to claim 8, wherein Use the parsed data corresponding to each passenger in the target order to allocate the order price, split the order package service, and split the order tax. After obtaining the order allocation and split results, it also includes: Based on the order allocation and splitting results, the target order is marked with a resolution status indicator; the resolution status indicators include allocation success, allocation error and reason, tax splitting success, tax splitting error and reason.

10. An airline order data processing device, characterized in that: include: Data acquisition module, used to receive order data; The order data has an order ID, which includes a parent order ID and a child order ID; An order includes all air transport and non-air transport services for multiple passengers. The order data consists of a four-layer structure: (i) the order, (ii) all passengers in the order, (iii) the flight segments corresponding to each passenger, and (iv) the flight segment information corresponding to each flight segment. The amount, taxes, fees, and ancillary services information are supplemented in the corresponding layers. The order data has an order number, which is the unique identifier of the order and remains unchanged. The order data also has an order version number and a history code. The order version number reflects the number of times the information in the order has been changed, and the history code reflects the specific content of a single change to the order. An order information parsing module is used to parse order data, obtain parsed data, and store the parsed data in an order database; The analysis includes marking order status and hierarchical analysis; the hierarchical analysis includes order global information analysis, passenger information analysis, flight segment information analysis, and flight segment information analysis; the analysis data includes order status, order global information, passenger information, flight segment information, and flight segment information; the order status reflects whether the order data has an impact on revenue settlement; the order status includes newly added order and related to revenue settlement, changed order but related to revenue settlement, or changed order but not related to revenue settlement; The fission order identification and processing module is used to search for multiple orders with parent-child relationships in the order database based on the order identifier and build an order fission mapping relationship; the order fission mapping relationship is the mapping relationship of all fission orders under the original order; The allocation and splitting processing module is used to read the target order that affects revenue settlement from the order database based on the order status; and obtain the corresponding parsed data for each passenger in the target order using the parsed data of the target order and the order fission mapping relationship including the target order identifier; Use the parsed data corresponding to each passenger in the target order to allocate the order freight, split the order packaging services, and split the order taxes and fees to obtain the order allocation and split results; The order allocation and splitting results include: air fares and ancillary service prices allocated to each flight segment of the passenger's itinerary, the prices of each detailed service in the ancillary services, each detailed service split into each flight node, and taxes split into each flight segment and flight node.

11. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the method according to any one of claims 1 to 9 is implemented.

12. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

13. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images