Airline company order data processing method and device

Abstract

The invention discloses an airline order data processing method and device, and relates to the technical field of airline data processing, and the method comprises the steps: carrying out the order state marking and hierarchical analysis of order data; the hierarchical analysis comprises order global information analysis, passenger information analysis, flight segment information analysis and flight section information analysis; the order state reflects whether the order data has an influence on income settlement; searching a plurality of orders with a father-son association relationship in an order database according to the order identifiers, and constructing an order fission mapping relationship; in combination with the order state, reading a target order having an influence on income settlement from an order database, and obtaining analysis data corresponding to each passenger in the target order; and the analysis data corresponding to each passenger in the target order is used to carry out order freight rate allocation, order packaging service splitting and order tax splitting, and an order allocation splitting result is obtained. According to the method, the income settlement business processing efficiency, accuracy and real-time performance of the low-cost airline company can be improved.

Description

Technical Field

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

[0002] This section aims to provide background or context for the embodiments of the present invention described in the claims. The descriptions herein are not admitted to be prior art merely because they are included in this section.

[0003] Currently, the vast majority of full-service airlines mainly adopt the system based on electronic tickets and electronic miscellaneous charges invoices to provide air transportation services and various non-air transportation auxiliary services to passengers. The predecessor of this system, paper tickets and paper miscellaneous charges invoices, has been widely used in the world's civil aviation field since the 1920s. The International Air Transport Association (IATA) has formulated detailed rules for the entire process of ticket and miscellaneous charges invoice from sales, use to financial settlement. Since computers were introduced into the civil aviation revenue settlement field in the 1960s, three generations of management information systems for revenue settlement business management have been developed internationally, based on ticket carriage information (Uplift base), the first ticket information entered into the revenue settlement system (Primary base), and ticket sales information (Salesbase). To date, the revenue settlement system established based on industry rules and business processes covers all aspects of the revenue settlement business of full-service airlines.

[0004] However, low-cost airlines have replaced the ticket / miscellaneous charges invoice system with an order-based model that carries all air and non-air services. Under the order-based model of low-cost airlines, the Order Management System (OMS) completes the comprehensive information management of many links, from order sales, order payment to the use of air transportation and non-air auxiliary services in the order, and can centralize the information management missions currently distributed in multiple application systems in the full-service airline environment into one system, realizing the centralized management of upstream and downstream information by airlines. At the same time, the order model of low-cost airlines does not comply with the industry rules based on the ticket / miscellaneous charges invoice system formulated by IATA, resulting in significant differences in the processing processes of low-cost airlines from service product sales to revenue settlement compared with full-service airlines.

[0005] The ticket / miscellaneous fee bill adopted by full-service airlines consists of a two-layer structure: (i) Ticket; (ii) Coupon. Among them, the ticket information includes the sales price of the whole ticket and all voyage information; the coupon information includes the voyage information of a specific flight segment in the ticket (flight number, cabin class, flight date, etc.). Since the information contained in this two-layer structured data is limited, the air transportation service and the non-air transportation auxiliary services can only be carried by the ticket and the miscellaneous fee bill respectively.

[0006] The common practice of low-cost airlines is to provide order data sources by the order management system. The order data covers all services and includes the sales information of the order and the usage status information of each service, which is also the only data source required for revenue settlement processing.

[0007] Full-service airlines need to receive numerous sales data sources and usage data sources from many upstream systems. Since the data formats of the data sources are different and the information contents included are also different, the revenue settlement system based on the ticket / miscellaneous fee bill data as the revenue settlement processing data source cannot handle the revenue settlement business of international mainstream low-cost airlines based on orders. The existing revenue settlement business of low-cost airlines is mainly processed manually. This method is not only inefficient but also error-prone. At the same time, with the growth of business volume, the amount of data to be processed also increases accordingly, which will bring greater pressure to the manual system and may lead to processing backlogs, resulting in poor real-time performance of the revenue settlement of low-cost airlines and difficulty in quickly responding to market changes or adjustments of business requirements. Summary of the Invention

[0008] An embodiment of the present invention provides a method for processing airline order data, which is applicable to the processing of low-cost airline order data and is used to improve the processing efficiency, accuracy, and real-time performance of the revenue settlement business of low-cost airlines. The method includes:

[0009] Receiving order data; the order data has an order identifier, and the order identifier includes a parent order identifier and a sub-order identifier;

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

[0011] Search for multiple orders with parent-child association relationships in the order database according to 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.

[0012] Combined with the order status, read the target orders that have an impact on revenue settlement from the order database.

[0013] Utilize 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.

[0014] Perform order fare allocation, order package service disassembly, and order tax splitting using the parsed data corresponding to each passenger in the target order to obtain the order allocation and splitting result; the order allocation and splitting result includes: the airfare and the price of auxiliary services allocated to each flight segment of the passenger's itinerary, the price of each detailed service in the auxiliary services, the price of each detailed service split to each flight section, and the tax split to each flight segment and flight section.

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

[0016] A data acquisition module, configured to receive order data; the order data has an order identifier, and the order identifier includes a parent order identifier and a sub-order identifier.

[0017] An order information parsing module, configured to 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 order global information parsing, passenger information parsing, flight segment information parsing, and flight section information parsing; the parsed data includes order status, order global information, passenger information, flight segment information, and flight section information; the order status reflects whether the order data has an impact on revenue settlement.

[0018] A fission order identification and processing module, configured to search for multiple orders with parent-child association relationships in the order database according to 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.

[0019] The sharing and splitting processing module is used to read target orders that affect revenue settlement from the order database in combination with the order status; obtain the parsed data corresponding to each passenger in the target order by using the parsed data of the target order and the order fission mapping relationship including the target order identifier; perform order fare sharing, order package service disassembly, and order tax splitting by using the parsed data corresponding to each passenger in the target order to obtain the order sharing and splitting result; the order sharing and splitting result includes: the airfare and the price of supplementary services are allocated to each flight segment of the passenger's voyage, the prices of various detailed services in the supplementary services, the price of each detailed service is split to each flight section, and the taxes are split to each flight segment and flight section.

[0020] An embodiment of the present invention further provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, the above-mentioned airline order data processing method is implemented.

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

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

[0023] After receiving the order data in the embodiment of the present invention, a mark indicating whether it affects revenue settlement is printed on it, and the global order information, passenger information, flight segment information, and flight section information are comprehensively parsed and stored in the order database. An order fission mapping relationship is also constructed to prevent data from being missed during subsequent sharing and splitting. Finally, target orders that affect revenue settlement are read from the order database, and order fare sharing, order package service disassembly, and order tax splitting are performed by using the parsed data corresponding to each passenger in the target order to obtain the order sharing and splitting result. Compared with the manual processing method in the prior art, the embodiment of the present invention is particularly applicable to the revenue settlement business processing of low-cost airlines. By processing order data parsing, constructing an order fission mapping relationship, and performing order fare sharing, order package service disassembly, and order tax splitting, the processing efficiency of the revenue settlement business of low-cost airlines and the accuracy of order data sharing and splitting processing are improved. It can also support real-time accounting and can quickly respond to business requirements. Description of the Drawings

[0024] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings. In the drawings:

[0025] Figure 1 It is a schematic flowchart of the airline order data processing method in the embodiment of the present invention;

[0026] Figure 2 It is a specific example diagram of the airline order data processing method in the embodiment of the present invention;

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

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

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

[0030] Figure 6 It is a schematic diagram of the airline order fission identification and processing in the embodiment of the present invention;

[0031] Figure 7 It is a schematic diagram of the airline order freight rate sharing and packaging service disassembly in the embodiment of the present invention;

[0032] Figure 8 It is a schematic diagram of the airline order tax information splitting in the embodiment of the present invention;

[0033] Figure 9 It is a schematic diagram of the airline order data processing device in the embodiment of the present invention. Detailed implementation manners

[0034] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer and more understandable, the following will further elaborate on the embodiments of the present invention in conjunction with the drawings. Here, the illustrative embodiments of the present invention and their descriptions are used to explain the present invention, but not to limit the present invention.

[0035] To facilitate a clear description of the technical solutions in the embodiments of the present invention, in the embodiments of the present invention, terms such as "first" and "second" are used to distinguish the same items or similar items with basically the same functions and roles. Those skilled in the art can understand that the terms "first", "second", etc. 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): It refers to an airline that provides complete services, usually including multiple cabins (such as first class, business class, and economy class), various types of services, and full-chain services. Their market coverage is extensive, serving both high-end business travelers who pursue comfort and mass leisure travelers. The main characteristics of full-service airlines include:

[0038] Multiple cabin services: Provide first class, business class, and economy class to meet the needs of different passengers;

[0039] Free checked baggage allowance: Usually provide free checked baggage allowance for passengers;

[0040] In-flight free meals: Provide free in-flight meals.

[0041] 2. Low Cost Carrier (LCC): It refers to an airline that controls its operating costs lower than full-service airlines by canceling some traditional airline passenger services, so that it can provide cheap prices in large quantities for a long time. The main characteristics of low-cost airlines include:

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

[0043] Service simplification: In order to reduce operating costs, low-cost airlines usually do not provide free meals, checked baggage incurs additional charges, and seat selection may require payment. In addition, they usually do not have first class and business class, and only provide economy class services.

[0044] Direct sales model: Low-cost airlines mainly conduct direct sales through the Internet and call centers, reducing the fees of intermediate links. This model not only reduces costs but also provides more flexible service options.

[0045] 3. Electronic Ticket (ET), Electronic Miscellaneous Document (EMD): The services of full-service airlines are mainly divided into air transportation services and non-airline auxiliary services. Usually, electronic tickets and electronic miscellaneous documents are used as vouchers to carry air transportation and various auxiliary services respectively.

[0046] 4. Low-cost airline order (Order or Booking): In the international market, the transportation services and various additional services provided by most low-cost airlines are carried by orders as the sole vouchers, eliminating the concepts of tickets and miscellaneous fee bills used by full-service airlines. An order can include all services, both air transportation and non-air transportation, for multiple passengers.

[0047] 5. Packed Service: Full-service airlines usually include necessary free checked baggage allowance and in-flight meal service in the air transportation services they provide. For low-cost airlines, except for the most basic air transportation service, services such as checked baggage and in-flight meals belong to the category of ancillary services. Therefore, the proportion of ancillary service revenue in low-cost airlines is much larger than that in full-service airlines. When passengers purchase multiple ancillary services, low-cost airlines usually offer a packed service price that includes all the air transportation and various ancillary services selected by the passengers. The packed service price is also cheaper than the price of purchasing each service separately. In the low-cost airline order, it includes the service content provided to passengers and the total price of the packed service. In the revenue settlement and processing link, for refined management, the packed service needs to be disassembled to separately recognize the revenue for different services, so as to accurately obtain the profit contribution degree of various services to the airline.

[0048] 6. Itinerary: It refers to the whole process from a passenger's departure to arrival, including the departure place, destination, and intermediate stops. An itinerary includes one or more flight segments.

[0049] 7. Segment: It refers to the flight process of an aircraft from the departure airport to the destination airport. A segment is described from the perspective of passengers and represents a part of the passenger's journey. Each segment includes one or more legs.

[0050] 8. Leg: It refers to the flight operation of an aircraft from one scheduled departure station to the next scheduled arrival station. A leg is described from the perspective of flight operations and represents the actual flight part of the aircraft.

[0051] In the existing industry rules of the International Air Transport Association, it is stipulated that ticket / miscellaneous fee statement data adopts a two - layer structure, namely: ticket certificate and ticket coupon. Among them, the ticket certificate information includes the sales price of the entire ticket and all voyage information; the ticket coupon information includes the voyage information (flight number, cabin class, flight date, etc.) of a specific flight segment in the ticket certificate. Since the information contained in this two - layer structure data is limited, air transportation services and non - air transportation - related auxiliary services can only be carried by tickets and miscellaneous fee statements respectively. The orders of low - cost airlines are the data sources for all revenue settlement operations, including information such as orders, all passengers, flight segments, and flight legs in the orders. Their data formats and structures are different from those of ticket / miscellaneous fee statement data. Therefore, it is difficult for the revenue settlement system established based on the two - layer structure data of ticket certificates / miscellaneous fee statements to process the order data of low - cost airlines. The common practice of low - cost airlines is to handle it manually. This method is not only inefficient but also prone to errors. At the same time, with the growth of business volume, the amount of data to be processed also increases accordingly, which will bring greater pressure to the manual system and may lead to processing backlogs, resulting in poor real - time performance of revenue settlement for low - cost airlines and difficulty in quickly responding to market changes or adjustments in business requirements.

[0052] Therefore, the embodiments of the present invention design a brand - new method for parsing the data of the order management systems of international mainstream low - cost airlines, including parsing low - cost airline order data, disassembling various aviation and non - aviation service packaged products in the order, and allocating (splitting) the values of various services and taxes to each flight segment / flight leg, laying a foundation for subsequent completion of revenue settlement for low - cost airlines.

[0053] Figure 1 It is a schematic flowchart of the airline order data processing method in the embodiments of the present invention, as Figure 1 shown. This method includes:

[0054] Step 101: Receive order data; the order data has an order identifier, and the order identifier includes a parent order identifier and a sub - order identifier;

[0055] Step 102: 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 of order global information, passenger information, flight segment information, and flight leg information; the parsed data includes order status, order global information, passenger information, flight segment information, and flight leg information; the order status reflects whether the order data has an impact on revenue settlement;

[0056] Step 103: According to the order identifier, search for multiple orders with parent - child association relationships in the order database, and construct an order fission mapping relationship; the order fission mapping relationship is the mapping relationship of all fission orders under the original order;

[0057] Step 104: Read target orders that affect revenue settlement from the order database in combination with the order status;

[0058] Step 105: 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;

[0059] Step 106: Use 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 the order allocation and splitting result; the order allocation and splitting result includes: the air freight rate and the price of the auxiliary service are allocated to each flight segment of the passenger voyage, the price of each detailed service in the auxiliary service, the price of each detailed service is split to each flight section, and the tax is split to each flight segment and flight section.

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

[0061] (1) Order data parsing;

[0062] (2) Order fission identification;

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

[0064] (4) Allocation (splitting) of the value of various services and taxes to each flight segment / flight section.

[0065] The following specifically introduces the order data processing method of the low-cost airline in the embodiment of the present invention.

[0066] Figure 2 This is a specific example diagram of the airline order data processing method in the embodiment of the present invention. Refer to Figure 2 , according to the order data processing method of the low-cost airline in 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 new / change status;

[0068] (2) Order information parsing;

[0069] (3) Order fission identification, aviation and non-aviation service disassembly, freight rate / tax / auxiliary service value allocation;

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

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

[0072] The order data of low-cost airlines can include a four-layer structure: (i) orders; (ii) all passengers in the order; (iii) the flight segments corresponding to each passenger; (iv) the leg information corresponding to each flight segment, and information such as amount, taxes, and ancillary services is supplemented in the corresponding layer. This four-layer order structure provides a more flexible and broad space to cover all passengers in the order and the corresponding all services (including air transportation and various non-air services) as well as payment and tax information, without the need for other information outside the order.

[0073] Figure 3 This is a schematic diagram of the airline order data structure in the embodiment of the present invention. Refer to Figure 3 , obtaining order data may include: the first layer of orders, including all passengers under the order and their corresponding all services; the second layer of passengers includes the flight segments and all services of all passengers under the order; the third layer of flight segments includes the specific information, fare, taxes, and ancillary service information of each flight segment in the flight; the fourth layer of leg information includes the information of each leg in the flight segment.

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

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

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

[0077] By identifying the order status, it is determined whether the order data received this time has an impact on revenue settlement, so as to determine whether the order data will be processed for revenue settlement subsequently. Through hierarchical parsing, detailed information about order sales, payment, passengers, flights, flight segments, and legs in the order data is obtained.

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

[0079] The order history information records the complete information of the order changes that occur in sequence during the entire life cycle of the order since its initial creation. Each order change that occurs is marked with a unique version number in the order history record information. When the order is created, the version number of the order is 1, and thereafter, each time the order changes, its version number is incremented by 1 in sequence. In addition, the time (in the form of a timestamp) when each order change occurs is also saved in the order history record information. The history record is crucial for identifying the content of each order change and determining the method to be adopted during subsequent revenue settlement processing. As mentioned above, an order contains four levels of information to carry all the auxiliary service information of air transportation and non-air transportation. In the order history record information provided by the upstream order management system, a unique "history record code" is defined for each type of order change. By reading this history record code, the specific content of each order change can be known. During revenue settlement processing, it is necessary to identify the history record code that appears in the order and determine whether this change has an impact on revenue settlement based on this history record code. Through the order's history record code, the order changes that have an impact on revenue settlement can be filtered out to complete the corresponding 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] Marking the order status of the order data using the order version number and the history record code may further include:

[0082] When the number of times the information in the order has changed reflected by the order version number is 0, mark the order status of the order data as a new order and related to revenue settlement;

[0083] When the number of times the information in the order has changed reflected by the order version number is greater than 0, obtain the history record code in the order data, match the history record code in the order data with a first preset reference file. When the match is successful, mark the order status of the order data as a changed order related to revenue settlement or a changed order not related to revenue settlement according to the match result; the first preset reference file stores the history record code field that affects revenue settlement.

[0084] For example, after the revenue settlement system in the embodiment of the present invention receives the order data from the upstream order management system, it starts to verify the accuracy of the "order version number, historical record code, and timestamp" in the order. If the "order version number, historical record code, and timestamp" are accurate, it is determined whether this order is a new order (order version number is 1) or an order that has been previously established and has had information changes this time (order number is greater than 1) by the order version number; for a small number of orders with missing or inaccurate "order version number, historical record code, and timestamp", by comparing the received order data with the order information of the same order number stored in the order database, it is determined whether the newly received order is a new order or a changed order.

[0085] If it is a new order, it is marked as "new order" on the order. Since all new orders need to undergo revenue settlement processing, this type of order needs to be set with the identifier "new order and related to revenue settlement", and then saved to the order database;

[0086] If it is an order with information changes, it is necessary to determine whether the information changes that occurred this time have an impact on revenue settlement (it needs to be determined by comparing the "historical information code affecting revenue settlement" in the first preset reference file in the revenue settlement system). After determination, if the changed information of the order has no impact on revenue settlement, this type of order is set with the identifier "changed order but not related to revenue settlement", and then saved to the order database. This type of "order change" information is only used for information storage and query and does not participate in subsequent revenue settlement processing; if it is determined that the changed information of the order has an impact on revenue settlement after determination, this type of order is set with the identifier "changed order and related to revenue settlement", and then saved to the order database.

[0087] Through the above processing, the orders are classified according to the "new" and "changed" statuses, and different identifiers are set for the orders that need to undergo revenue settlement processing and those that do not need to undergo revenue settlement processing respectively, and then enter the subsequent "order information parsing" link.

[0088] Figure 4 This is a schematic diagram of the parsing and processing of airline order data in the embodiment of the present invention. As Figure 4 shown, the order information identification and parsing are 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 the temporary database for subsequent processing;

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

[0091] (3)Order status judgment: Determine whether it is a new order or a changed order, and analyze the historical record code in the order historical information to determine whether it affects revenue settlement;

[0092] (3)Identification processing: According to the Figure 4 process in, mark the order status according to the judgment result;

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

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

[0095] The following Table 1 illustrates the relationship between the historical record code in the first preset reference file and the "whether it affects revenue settlement" identifier.

[0096] Table 1

[0097]

[0098] In an embodiment, when the order version number reflects that the number of times the information in the order has 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, compare the order identifier of the received order data with the order identifier in the order database;

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

[0101] When there is an order with the same order identifier in the order database, compare the set key fields of the received order data with the order data of the order with the same order identifier in the order database, and according to the comparison result, mark the order status of the order data 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, compare the received order information with the order information of the order with the same order ID already stored in the order database. The comparison steps are as follows:

[0103] First step: Configure the key field information in the order, and load the set key field information into the memory of the revenue settlement system server.

[0104] Step 2: Perform operations on the accessed order data according to the set key fields to form set T. Then read the data in the order database to form set R, and convert the comparison of order data into set operations. The data in the result set of the difference set operation between set T and set R indicates that the order data did not exist before and is newly added order data, which is marked as new; the data in the result set of the intersection set operation between set T and set R indicates that the order data existed before. If the key fields change, it is marked as related to change and revenue settlement, otherwise it is marked as unrelated to change and revenue settlement.

[0105] After the order status is marked as completed, enter the order information parsing link. When parsing order information, it is carried out according to the four-layer structure of the order. At the first level, identify and parse the global order information, including order ID, order sales and payment, etc.; at the second level, identify and parse all passenger information under the order, including the ID of each passenger, passenger taxes and fees, etc.; at the third level, identify and parse all air transportation and auxiliary service information under each passenger, including the ID of each air transportation flight segment, origin and destination information of this flight segment, each type of auxiliary service and corresponding amount information; at the fourth level, identify and parse all flight leg information under each flight segment, including the ID of each flight leg, the specific flight and flight status of this flight leg, etc. Finally, store the parsed order information in the order database according to different levels.

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

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

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

[0109] Flight segment layer: Nest to parse the JSON object and construct multi-level relationships such as flight segment ID and passenger ID;

[0110] Flight leg layer: Process time-series data and record the association between flight leg ID and flight segment ID, etc.

[0111] In step 103, according to the order identifier, search for multiple orders with a parent-child association relationship in the order database and construct an order fission mapping relationship; the order fission mapping relationship is the 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 airlines have the characteristic of order fission. Refer to Figure 5 , Figure 5 is the schematic diagram of airline order fission in the embodiment of the present invention.Figure 5 In this case, Order 1 initially includes 9 passengers. After the first split to Order 2, Order 1 still retains 4 passengers. After the second split to Order 3, Order 1 still retains 3 passengers, and so on. If an order contains multiple passengers, this order can be split into several sub-orders in the follow-up, and each sub-order can continue to be split into several grand-orders... This provides sufficient flexibility for different passengers in the original order when selecting various services and travel freedom.

[0113] An order of a low-cost airline can contain 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 from the original order in the order management system to form a new order, and display the latest information of these passengers in the new order. Among them, the original order is called the parent order, and the new order split from the parent order is called the sub-order. The sub-order will create a new order ID in the order management system, and the sub-order will carry the order ID of the parent order; several grand-orders can continue to be split from the sub-order, and the grand-orders will also have their own order IDs. Similarly, the grand-order will carry the order ID of the upper-level sub-order; the grand-order can continue to split downwards until there is only one passenger left in the order.

[0114] In an embodiment, according to the order identifier, searching for multiple orders with a parent-child association relationship in the order database and constructing an order fission mapping relationship 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, regarding this order as the original order; if the parent order ID of the order is not empty, determining that this order is a sub-order, and searching for orders with the same parent order ID as the sub-order identifier in the order database until the parent order ID of the searched order is empty. Finally, construct 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 perform fission order identification on the order data and establish the mapping relationship between the parent order and the sub-order, and between the sub-order and the grand-order.

[0116] Figure 6 It is a schematic diagram of the airline order fission identification processing in the embodiment of the present invention. Refer to Figure 6, The method for identifying order fission is to judge the parent - child order ID information in each order, so as to determine the parent order and the child order, mark the order with fission as "order fission", and continue to trace back to the most 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 in the order database for the same order ID and the parent order ID on this order is empty, which means this order is a child order and is the first fission of the parent order, and no subsequent search is required; if the same order ID can be found and the parent order ID on this order is not empty, it means that there is still order fission in the upper - level order of this order. Mark this type of order 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 parsing the order fission data, establish a mapping relationship for all fission orders under an order in the order database for subsequent revenue settlement processing.

[0117] Step 104: Combine the order status and read the target orders that have an impact on revenue settlement from the order database.

[0118] For example, sequentially read orders from the order database that have not undergone freight rate sharing, service disassembly, and tax splitting.

[0119] In step 105, 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.

[0120] Through the above - mentioned preliminary preparation of order data, obtain the parsed data corresponding to each passenger in the target order, including all information related to the flight itinerary.

[0121] In step 106, use the parsed data corresponding to each passenger in the target order to perform order freight rate sharing, order packaged service disassembly, and order tax splitting to obtain the order sharing and splitting result; the order sharing and splitting result includes: the air freight rate and the price of auxiliary services are allocated to each flight segment of the passenger's itinerary, the price of each detailed service in the auxiliary services, the price of each detailed service is split to each flight section, and the tax is split to each flight segment and flight section.

[0122] In an embodiment, using the parsed data corresponding to each passenger in the target order to perform order freight rate sharing may include:

[0123] Use the flight segment information of the same passenger to determine whether the passenger's itinerary is a direct flight itinerary or a connecting flight; the connecting flight means that the entire itinerary is carried by different flights;

[0124] When the passenger's itinerary is a direct flight itinerary, use the freight rate of the direct flight itinerary as the air freight rate sharing result;

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

[0126] In one embodiment, the segment information includes the ancillary service information of each segment; using the parsed data corresponding to each passenger in the target order for order bundling service disassembly may include:

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

[0128] Apportion the price of each detailed service to the leg level according to the distance of each leg under the segment.

[0129] Figure 7 This is a schematic diagram of the airline order fare apportionment and bundling service disassembly in the embodiments of the present invention. Refer to Figure 7 , sequentially read the orders from the order database that have not undergone fare apportionment and service disassembly, read the itinerary information of each passenger in the qualified orders, and then judge the itinerary type: if it is a direct flight itinerary (a direct flight itinerary means a flight flies from point A to point B, and multiple intermediate stops are allowed, but the flight number does not change), then directly use the fare of this segment as the apportionment result; if it is a connecting flight (a connecting itinerary means the entire itinerary is carried by flights with different flight numbers or by different airlines), then it is necessary to piece together the segments related to the connecting flight to form the entire itinerary. At the same time, after adding up the fares of the relevant segments, the fare value is apportioned to each segment according to the distance of each segment (the distance of each segment is obtained through the "segment distance reference information" pre-maintained in the revenue settlement system). When the processing of apportioning the fare to each segment is completed, each segment obtains the bundled service price of the air transportation and non-air transportation ancillary services of this segment. Next, it is necessary to disassemble the bundled service into various detailed services and obtain the value of each service at the same time. When disassembling the bundled service, it is necessary to compare the bundled service information with the characteristics of each detailed service defined in the second preset reference file in the revenue settlement system in advance, and identify the detailed service and the corresponding value one by one. After completing the service disassembly at the segment level, apportion the value of each service to the leg level according to the distance of each leg under the segment. In this way, as the smallest unit providing services, each leg obtains the value of each service provided in this leg. After the subsequent use of this service, the revenue confirmation of the corresponding service can be carried out.

[0130] The basic idea of order freight rate allocation is as follows: for different types of low-cost airline order data, the amount of the bundled service is allocated to each flight segment, and the allocated amount for each flight segment is obtained. This is the basis for subsequent unpacking of the bundled service, airline transportation revenue recognition, and accounting treatment. In the embodiment of the present invention, the distance between the origin and the destination is used as the basis for allocating the amount. When using the distance as the basis, external data recording the distances of each flight segment / section needs to be accessed as reference data.

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

[0132] 1. Target data: All order data for which freight rate allocation has not been successfully carried out;

[0133] 2. Target search and voyage splicing:

[0134] (1) In the order database, find the corresponding data in the passenger information table according to the order ID to 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 with the same passenger ID, check the value of its "voyage type", and determine whether it is a "connecting voyage" or a "direct voyage"; Figure 3 Only shows the basic structure of the order data. Among them, each layer of the order data includes a large amount of data content, which cannot be listed one by one in Figure 3 For example, for the third-layer flight segment layer, it can include voyage type, aircraft type, departure station, departure date, reservation status, etc. When the value of the voyage type is 4, it is a "connecting voyage", and the rest of the values are "direct voyages".

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

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

[0139] (6) Obtain the distance of the entire voyage by reading the "voyage / section distance reference information".

[0140] For example, 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 value in the field "flight number". Such flight segments belong to the same flight itinerary and are grouped together for apportionment. After successful apportionment, the system sets the "whether to be apportioned" flag to "Y", so that next time only those with the "whether to be apportioned" flag not equal to Y need to be apportioned. For all the found flight segments, write the departure station and arrival station fields (both of the above two STATION fields are 3-character) into the "flight itinerary" field in the order of the flight segments, and at the same time remove 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, and after summing up, obtain the total amount of the entire flight itinerary as the amount to be apportioned; then use the distance of each flight segment as the apportionment basis, multiply it by the distance of this flight segment divided by the distance of the entire flight itinerary to obtain the apportionment value of this flight segment.

[0143] (2) If the apportionment is successful, set the apportionment status of the order to "apportionment successful";

[0144] (3) If there is a lack of information on the amount to be apportioned or a lack of information on the flight segment distance, the apportionment status is set to "apportionment error", and the reason for the apportionment error is recorded in the apportionment error field;

[0145] (4) For the order with apportionment error, provide an error modification function for the front-end user to modify. The modified order information will continue to perform the apportionment process until the apportionment is successful.

[0146] The basic idea of unpacking the package service is as follows: 1) The unpacking of the package service is carried out after the freight rate apportionment of the order data; 2) When unpacking the package service, 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 unpacking the package service is carried out in each flight segment, and the value of air transportation services and the values of various non-air transportation services in each flight segment are disassembled.

[0147] Unpacking logic of the package service:

[0148] 1. For the flight segments that have completed the apportionment process, match the "service product code" information in this flight segment with the "service characteristic reference information" recorded in the second preset reference file to initially find the target range;

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

[0150] 3. Using the narrowed target range found in step 2, continue to check if it is within the "valid period" of the "service feature reference information" to eliminate invalid values and further narrow the target range;

[0151] 4. Using the results obtained from the previous three steps, continue to match the information of "flight direction", "flight range type", and "flight segment limit". The flight direction reference information maintains the directional limit for the flight range. When the value is A, it means "the flight range information conforms and the flight direction conforms"; when the value is B, it means "as long as the flight range information conforms, 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 flight range is "city 1 - city 2" but the flight direction is "city 2 - city 1", it does not meet the requirements. On the contrary, if the information maintained in the second preset reference file is city 1 - city 2 and the flight direction is not restricted, then both "city 1 - city 2" and "city 2 - city 1" for the flight range meet the requirements. The flight segment limit indicates whether more than 1 flight segment is allowed during the flight range. The second preset reference file can maintain "allowed" or "not allowed", and the system determines whether there is a match by comparing the actual data with the second preset reference file.

[0152] Locate the detailed service information according to the above four steps, and then disassemble the value of this service from the "service feature reference information". When disassembling the packaged service, it is also necessary to consider the priority order of each service defined in the external data of the "service feature reference information", and the apportioned amount of the flight segment needs to be disassembled according to the priority order of each service.

[0153] For example, for the flight segment "city 1 - city 2", the "price of the packaged service to be disassembled" is 120, and the "service product code" = AA. According to the data maintained in the second preset reference file, n auxiliary service data with the "service product code" = AA are matched. Use aircraft type information, sales date, flight direction, flight range type, etc. to filter out x auxiliary service data that meet the conditions, and start the amount disassembly:

[0154] For priority 1, the corresponding auxiliary service type is food type 1, and the price is 34. Then allocate 34 to food type 1, and the remaining packaged service price is 120 - 34 = 86;

[0155] Then find the next one. For priority 3, the corresponding auxiliary service type is comfort supplies set 1, and the price is 18. Then allocate 18 to the comfort supplies set, and the remaining packaged service price is 86 - 18 = 68;

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

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

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

[0159] Compare the tax and fee information of each passenger with a third preset reference document to determine the tax and fee type of each passenger; the tax and fee type includes general taxes and fees, and penalty taxes and fees;

[0160] For general taxes and fees, allocate the taxes and fees to each flight segment of the flight according to the flight segments corresponding to the taxes and fees in the order data;

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

[0162] Allocate each tax and fee amount to the flight leg level according to the distance of each flight leg under the flight segment.

[0163] In one embodiment, after using the parsed data corresponding to each passenger in the target order for order fare allocation, order bundled service disassembly, and order tax and fee splitting to obtain the order parsing and splitting result, the method may further include: according to the order parsing and splitting result, mark the parsing status identifier for the target order; the parsing status identifier includes successful allocation, allocation error and reason, successful tax and fee splitting, tax and fee splitting error and reason.

[0164] Figure 8 This is a schematic diagram of the splitting of airline order tax and fee information in the embodiments of the present invention. Refer to Figure 8 , sequentially read the orders that have not been subject to tax and fee splitting from the order database, and then read the tax and fee information of each passenger in the eligible orders. By comparing the tax and fee information with the "industry tax and fee reference information" external data of the third preset reference document pre-maintained in the revenue settlement system, complete the judgment of the tax and fee type: if it is a general type of tax and fee, then allocate the tax and fee information to the corresponding flight segments according to the flight segment information corresponding to the tax and fee in the order information; if it is a penalty type of tax and fee (for low-cost airlines, when a passenger actively cancels all or part of the services of an order after purchase, a penalty fee is usually charged), then this type of penalty tax and fee needs to be allocated to the cancelled flight segments in order to form a complete input tax confirmation in the subsequent process (penalty fees also belong to input tax). After completing the tax and fee splitting at the flight segment level, allocate each tax and fee amount to the flight leg level according to the distance of each flight leg under the flight segment. In this way, as the smallest unit providing services, the flight leg obtains the amount of each tax and fee in this flight leg, preparing for the subsequent revenue settlement processing.

[0165] The order tax and fee splitting logic is as follows:

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

[0167] 2. Target search method:

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

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

[0170] (3) By comparing each tax in the order with the external data of "tax reference information", obtain the type information of the tax to determine whether the tax belongs to "general tax" or "penalty tax";

[0171] (4) For "general tax", according to the flight segment information recorded in the tax ID information, allocate the tax information to the corresponding flight segment;

[0172] (5) For "penalty tax", the tax needs to be associated with the old (deleted) record. According to the origin and destination recorded in the tax ID information and the old flight segment information, find the old "flight segment with the same origin and destination", and place the tax in the old flight segment;

[0173] (6) After splitting the amounts of the above two types of taxes into flight segments, further split them into flight legs according to the distance of each flight leg.

[0174] When the tax is split, different status flags (split successfully, split failed) need to be set according to the split situation. For orders with failed tax splitting, a modification function is provided. After modification, the tax splitting process will continue until it is successful.

[0175] In summary, the method for processing airline order data in the embodiments of the present invention is particularly applicable to low-cost airlines, improving the processing efficiency of revenue settlement operations of low-cost airlines, enhancing the accuracy of order data parsing, and also being able to support real-time accounting, enabling quick response to business requirements. The order parsing and splitting solution of the present invention can process orders widely adopted by low-cost airlines, has strong adaptability, and broad application prospects.

[0176] In the embodiments of the present invention, an airline order data processing device is also provided, as described in the following embodiments. Since the principle of the device for solving problems 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 elaborated.

[0177] Figure 9 is a schematic diagram of the airline order data processing device in the embodiments of the present invention, as Figure 9 shown. The device 900 includes:

[0178] A data acquisition module 901, configured to receive order data; the order data has an order identifier, and the order identifier includes a parent order identifier and a sub-order identifier;

[0179] An order information parsing module 902, configured to 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 order global information parsing, passenger information parsing, flight segment information parsing, and flight section information parsing; the parsed data includes order status, order global information, passenger information, flight segment information, and flight section information; the order status reflects whether the order data has an impact on revenue settlement;

[0180] A fission order identification and processing module 903, configured to search for multiple orders with a parent-child association relationship in the order database according to 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] An apportionment and splitting processing module 904, configured to combine the order status, read a target order that has an impact on revenue settlement from the order database; 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 perform order fare apportionment, order package service disassembly, and order tax splitting, and obtain an order apportionment and splitting result; the order apportionment and splitting result includes: the airfare and the price of auxiliary services are apportioned to each flight segment of the passenger voyage, the price of each detailed service in the auxiliary services, the price of each detailed service is split to each flight section, and the tax is split to each flight segment and flight section.

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

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

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

[0185] When the number of times the information in the order has changed reflected by the order version number is 0, mark the order status of the order data as a new order and related to revenue settlement;

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

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

[0188] An order marking standby processing module, configured to, after the number of times the order version number reflects that the information in the order has changed is greater than 0, compare the order identifier of the received order data with the order identifiers in the order database 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 identifier in the order database, mark the order status of the order data as a new order related to revenue settlement;

[0190] When there is an order with the same order identifier in the order database, compare the set key fields of the received order data with the order data of the order with the same order identifier in the order database, and mark the order status of the order data as a changed order related to revenue settlement or a changed order unrelated to revenue settlement according to the comparison result.

[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, regard the order as an original order;

[0194] If the parent order ID of the order is not empty, determine that the order is a sub - order, search for orders with the same parent order ID as the sub - order identifier in the order database until the parent order ID of the searched order is empty, and construct an order fission mapping relationship.

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

[0196] Use the flight segment information of the same passenger to determine whether the passenger's flight itinerary is a direct flight or a connecting flight; the connecting flight means that the entire itinerary is carried by different flights;

[0197] When the passenger's flight itinerary is a direct flight, use the fare of the direct flight as the air fare sharing result;

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

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

[0200] The apportionment and splitting processing module 904 is specifically configured to:

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

[0202] Apportion the price of each detailed service to the leg level according to the distance of each leg under the segment.

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

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

[0205] Compare the tax and fee information of each passenger with a third preset reference file to determine the tax and fee type of each passenger; the tax and fee type includes general taxes and fees, and penalty taxes and fees;

[0206] For general taxes and fees, allocate the taxes and fees to each segment of the voyage through 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 segments that the passenger has cancelled;

[0208] Apportion the tax and fee amount to the leg level according to the distance of each leg under the segment.

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

[0210] An analysis status identification processing module, configured to, after the apportionment and splitting processing module 904 uses the parsed data corresponding to each passenger in the target order to perform order fare apportionment, order package service disassembly, and order tax and fee splitting, and obtains the order apportionment and splitting result, mark an analysis status identification for the target order according to the order apportionment and splitting result; the analysis status identification includes apportionment success, apportionment error and reason, tax and fee splitting success, tax and fee splitting error and reason.

[0211] An embodiment of the present invention further provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where when the processor executes the computer program, the above-mentioned airline order data processing method is implemented.

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

[0213] An embodiment of the present invention also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the above-mentioned airline order data processing method is implemented.

[0214] After receiving the order data in the embodiment of the present invention, a mark indicating whether it has an impact on revenue settlement is printed, and the global order information, passenger information, flight segment information, and flight section information are comprehensively analyzed and stored in the order database. An order fission mapping relationship is also constructed to prevent data loss during the subsequent allocation and splitting. Finally, the target orders that have an impact on revenue settlement are read from the order database, and order fare allocation, order package service disassembly, and order tax splitting are performed using the parsed data corresponding to each passenger in the target orders to obtain the order allocation and splitting results. Compared with the manual processing method in the prior art, through the processing of order data parsing, order fission mapping relationship construction, order fare allocation, order package service disassembly, and order tax splitting, the processing efficiency of the revenue settlement business of low-cost airlines is improved, the accuracy of order data allocation and splitting processing is improved, and real-time accounting can be supported, and business requirements can be quickly responded to.

[0215] Those skilled in the art should understand that the embodiments of the present invention can be provided as a method, a system, or a computer program product. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present invention can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0216] The present invention is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (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, and the combination 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 the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate means for implementing the specified functions in one process Figure 1 one process or multiple processes and / or blocks Figure 1 or multiple blocks.

[0217] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to work in a particular manner, such that the instructions stored in the computer-readable memory produce a manufacture including an instruction means that implements the functions specified in one process Figure 1 or a plurality of processes and / or blocks Figure 1 or a plurality of blocks.

[0218] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus, such that a series of operational steps are performed on the computer or other programmable apparatus to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable apparatus provide steps for implementing the functions specified in one process Figure 1 or a plurality of processes and / or blocks Figure 1 or a plurality of blocks.

[0219] The specific embodiments described above further elaborate on the objectives, technical solutions, and beneficial effects of the present invention. It should be understood that the above are merely specific embodiments of the present invention and are not used to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope 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; 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 section information analysis; the analysis data includes order status, order global information, passenger information, flight segment information and flight section information; the order status reflects whether the order data has an impact on revenue settlement; According to the order ID, multiple orders with parent-child relationship are searched in the order database to build 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 order that has an impact on revenue settlement from the order database; Obtain the parsed data corresponding to each passenger in the target order by 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, 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: 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, characterized in that The order data also 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. 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, characterized in that 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 information in the order 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, characterized in that 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 of 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 newly added order and related to revenue settlement; When there are orders with the same order ID 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, characterized in that According to the order ID, multiple orders with parent-child relationship are searched in the order database to build 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 is taken 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 an order fission mapping relationship is constructed.

6. The method according to claim 1, characterized in that Use the parsed data corresponding to each passenger in the target order to allocate the order freight rate, including: Using the flight segment information of the same passenger, determining whether the passenger's flight is a direct flight or a connecting flight; the 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 result of the air fare allocation; When the passenger's flight is a connecting flight, all the flight segments in the passenger's flight segment information will be spliced ​​in order to form the entire flight, and the total fare of all the flight segments will be allocated according to the distance of each flight segment.

7. The method according to claim 6, characterized in that 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: Matching the auxiliary service information of each flight segment with the second preset reference file to determine the price of each detailed service in the auxiliary 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 knot level according to the distance of each flight knot under the flight segment.

8. The method according to claim 1, characterized in that 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; Determine the tax type of each passenger by comparing the tax information of each passenger with the third preset reference file; the tax type includes general taxes and penalty taxes; For general taxes, the taxes are allocated to each flight segment according to the flight segment corresponding to the taxes in the order data. For penalty taxes and fees, the penalty taxes and fees will be allocated to the passenger's cancelled flight segments; The tax amount is allocated to the flight knot level according to the distance of each flight knot under the flight segment.

9. The method according to claim 8, characterized in that Use the parsed data corresponding to each passenger in the target order to allocate the order freight, disassemble the order packaging service, and split the order tax. After obtaining the order allocation and splitting results, it also includes: According to the order allocation and splitting results, the target order is marked with a parsing status identifier; the parsing status identifiers 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: A data acquisition module, used for receiving order data; The order data has an order ID, which includes a parent order ID and a child order ID; An order information parsing module is used to parse the order data, 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 section information analysis; the analysis data includes order status, order global information, passenger information, flight segment information and flight section information; the order status reflects whether the order data has an impact on revenue settlement; The fission order identification processing module is used to search for multiple orders with a parent-child relationship in the order database according to 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; The allocation and splitting processing module is used to read the target order that affects the revenue settlement from the order database in combination with the order status; obtain the corresponding parsed data of each passenger in the target order by 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, 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: 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, characterized in that: 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