Civil Aviation Passenger Revenue Management System and Method

Abstract

The present invention discloses a civil aviation passenger revenue management system and method, which relates to the technical field of aviation data processing. The system includes: an order recognition module, an order database, an accounting module, a balance check module, and an archiving module; the order recognition module is used for: receiving order data; marking the revenue impact status for the order data; performing hierarchical parsing on the order data to obtain parsing information; the order database is used for: storing the order data processed by the order recognition module; the accounting module is used for: performing addition and subtraction processing on the amount to be settled and using revenue confirmation or deletion for the order data that has an impact on revenue management; the balance check module is used for checking whether the amount to be settled and the used revenue of the order with the order status of closed are balanced; the archiving module is used for archiving the orders with the order status of closed and passing the balance check. The present invention can solve the problem that the current airline revenue management system for processing air ticket / miscellaneous fee bills cannot handle the revenue management of unified orders.

Description

Technical Field

[0001] The present invention relates to the technical field of air data processing, and particularly to a civil aviation passenger revenue management system and method. Background Art

[0002] This section aims to provide background or context for the embodiments of the present invention described in the claims. The description herein is not admitted to be prior art merely by virtue of being included in this section.

[0003] At present, most airlines in the world mainly provide air transportation services and various non-air transportation services (such as hotels, car rentals, etc.) to passengers based on the ticket and miscellaneous fee bill system. In recent years, the International Air Transport Association (IATA) has proposed the concept of ONE Order, aiming to simplify the existing complex business processes of airlines, thereby reducing the operating costs of airlines and promoting the progress of the industry. Major airlines in the world have responded to the IATA's advocacy and begun to transform to ONE Order.

[0004] In the ONE Order environment, various air transportation and non-air transportation services currently provided by airlines will be carried by orders, and an order management system (OMS) will be used to complete all-round information management of order sales, order payment, order use, revenue management, data analysis, etc. The order management system will centralize the management missions currently distributed in multiple application systems of airlines in one system for unified management, so as to achieve the purpose of simplifying business processes and reducing costs.

[0005] The civil aviation revenue management system established for the ticket / miscellaneous fee bill system cannot fulfill the mission of revenue management for International Air Transport Association (IATA) ONE Order data. Therefore, it is necessary to design a revenue management method based on the new system.

[0006] Currently, ticket / miscellaneous fee bill data adopts a two-layer structure according to industry standards: ticket and flight coupon. The ticket information contains the overall information of the entire ticket, such as fare and itinerary information, etc.; several flight coupons can be included under one ticket, and the flight coupon information includes the information of a specific flight segment in the ticket (flight number, cabin class, flight date, etc.). Since the information contained in this two-layer structure data is limited, air transportation services and non-air transportation services can only be carried by tickets and miscellaneous fee bills respectively.

[0007] According to the industry standards issued by the International Air Transport Association (IATA), ONE Order includes a three-layer structure: order, sub-order, and service. Several sub-orders are included under one order, and several services are included under each sub-order.

[0008] Due to the significant differences between the industry standards for the air ticket / miscellaneous charge bill system and the industry standards for the unified order (ONE Order), the current airline revenue management system that processes air ticket / miscellaneous charge bills is unable to meet the revenue management requirements of the unified order (ONE Order) environment. Summary of the Invention

[0009] An embodiment of the present invention provides a civil aviation passenger revenue management system to address the problem that current airline revenue management systems that process air tickets / miscellaneous charges are unable to handle revenue management of unified orders. The method includes: an order identification module, an order database, a calculation module, a balance check module, and an archiving module.

[0010] The order identification module is used to: receive order data; mark the order data with revenue impact status; and perform hierarchical analysis of the order data to obtain analysis information; the analysis information includes global order information, sub-order information, and sub-order service information; global order information includes order status, which can be open or closed. Open indicates that the services in the order are not used, and closed indicates that the services in the order are invalid; the revenue impact status indicates whether there is an impact on revenue management;

[0011] The order database is used to: store the order data processed by the order identification module;

[0012] The accounting module is used to increase or decrease pending payments and adjust revenue usage for order data in the order database that impacts revenue management. This module uses service information under sub-orders to increase or decrease pending payments and order status to confirm or delete revenue usage.

[0013] The balance check module is used to check whether the pending settlement amount and used income of orders with closed status are balanced;

[0014] The Archiving module is used to archive orders that have a status of Closed and have passed the balance check.

[0015] The embodiment of the present invention further provides a civil aviation passenger revenue management method to solve the problem that the current airline revenue management system for processing air tickets / miscellaneous charges is unable to handle revenue management of unified orders. The method includes:

[0016] Receive order data, mark the order data with revenue impact status, perform layered analysis on the order data, obtain analysis information, and store it in the order database; the revenue impact status reflects whether it has an impact on revenue management; the analysis information includes global order information, sub-order information, and sub-order service information; the global order information includes the order status, which can be open or closed. Open indicates that the services in the order are not used, and closed indicates that the services in the order are invalid;

[0017] Read order data sequentially from the order database to determine the order status and revenue impact status;

[0018] When the order status is open and the revenue impact status has an impact on revenue management, perform the processing of increasing or decreasing the amount to be settled and use revenue adjustment on the order data; among them, use the service information under the sub-order to increase or decrease the amount to be settled, and use the order status to confirm or delete the use of revenue;

[0019] When the order status is closed, check whether the amount to be settled and the use of revenue of the order are balanced. When the amount to be settled and the use of revenue of the order are balanced, archive the order.

[0020] An embodiment of the present invention also 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 civil aviation passenger transportation revenue management method is implemented.

[0021] An embodiment of the present invention also 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 civil aviation passenger transportation revenue management method is implemented.

[0022] An embodiment of the present invention also 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 civil aviation passenger transportation revenue management method is implemented.

[0023] In the embodiment of the present invention, the civil aviation passenger transportation revenue management system can, in a unified order environment, realize order data identification, parsing, calculation and confirmation of the amount to be settled for sales and service use revenue, check the balance of the amount to be settled for sales and service use information until the order revenue information is archived, and solve the problem that the current airline revenue management system for processing air ticket / miscellaneous fee bills cannot handle the revenue management of unified orders. After airlines replace the current air ticket / miscellaneous fee bill system with a unified order form in the future, the civil aviation passenger transportation revenue management system based on the method of the embodiment of the present invention can be widely applied to airlines. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order 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 following drawings 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 diagram of the civil aviation passenger transportation revenue management system in the embodiment of the present invention;

[0026] Figure 2 Schematic diagram of the order data structure in the embodiment of the present invention;

[0027] Figure 3 Schematic diagram of the order change information record table in the embodiment of the present invention;

[0028] Figure 4 Schematic diagram of the process of data identification and parsing in the embodiment of the present invention;

[0029] Figure 5 Schematic diagram of the order data parsing in the embodiment of the present invention;

[0030] Figure 6 Schematic diagram of the order data storage in the embodiment of the present invention;

[0031] Figure 7 Schematic diagram of the processing flow of the accounting module in the embodiment of the present invention;

[0032] Figure 8 Schematic diagram of the processing flow of the balance check module in the embodiment of the present invention;

[0033] Figure 9 Schematic diagram of the process of the civil aviation passenger transportation revenue management method in the embodiment of the present invention;

[0034] Figure 10 A specific example diagram of the civil aviation passenger transportation revenue management method in the embodiment of the present invention. Detailed implementation manners

[0035] To make the objectives, technical solutions and advantages of the embodiments of the present invention clearer and more understandable, the following further elaborates on the embodiments of the present invention with reference to the accompanying drawings. Herein, the illustrative embodiments of the present invention and their descriptions are used to explain the present invention, but not to limit the present invention.

[0036] In order to facilitate a clear description of the technical solutions of 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 effects. Those skilled in the art can understand that the terms "first" and "second" do not limit the quantity and execution order.

[0037] In the technical solutions of the present application, the acquisition, transmission, storage, use, processing, etc. of data all comply with the relevant provisions of national laws and regulations.

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

[0039] 1. The International Air Transport Association (IATA) is a large international organization composed of airlines from all over the world.

[0040] 2. IATA ONE Order: It is an industry standard initiated by IATA to simplify business operations such as airline sales, delivery, and revenue management. Its core is to use a single order to cover all air transportation services and non-air transportation services, replacing the existing ticket / miscellaneous fee list system.

[0041] 3. Airline Order Management System (OMS): In the ONE Order environment, the order management system is responsible for comprehensive information management in aspects such as order sales, order payment, order usage, revenue management, and data analysis. It centralizes the management missions currently distributed in multiple airline information systems into one system, achieving unified management of the upstream and downstream businesses by the airline.

[0042] 4. Ticket, miscellaneous fee list: An airline's services are mainly divided into air transportation services and non-airline auxiliary services. Usually, tickets and miscellaneous fee lists are used as vouchers to carry air transportation and various auxiliary services respectively.

[0043] 5. Airline's "amount due for settlement": The funds received when an airline sells service products are of a prepaid nature and belong to the liability category. After the sale of service products is completed, the airline's accounting treatment is to credit the "amount due for settlement in sales" account, indicating an increase in liabilities (the obligation to provide unfulfilled services). Usually, this type of sales revenue is referred to as the airline's "amount due for settlement". After the corresponding services provided by the airline are completed, the liability can be transferred to the revenue account.

[0044] Figure 1 It is a schematic diagram of the civil aviation passenger transport revenue management system in the embodiment of the present invention. As Figure 1 shown, the system 100 includes an order identification module 101, an order database 102, an accounting module 103, a balance check module 104, and an archiving module 105. Among them:

[0045] The order identification module 101 is used to: receive order data; mark the revenue impact status for the order data; perform hierarchical parsing on the order data to obtain parsing information; the parsing information includes order global information, sub-order information, and service information under the sub-order; the order global information includes the order status, and the order status includes open or closed. Open reflects the unused situation of various services in the order, and closed reflects that various services in the order have expired; the revenue impact status reflects whether there is an impact on revenue management.

[0046] The order database 102 is used for: storing the order data processed by the order recognition module;

[0047] The accounting module 103 is used for: performing the processing of increasing or decreasing the amount of money to be settled and using revenue adjustment on the order data in the order database that has an impact on revenue management; among them, the amount of money to be settled is increased or decreased by using the service information under the sub-order, and the use of revenue is confirmed or deleted by using the order status;

[0048] The balance check module 104 is used for checking whether the amount of money to be settled and the used revenue of the order with the order status of closed are balanced;

[0049] The archiving module 105 is used for archiving the orders with the order status of closed and passing the balance check.

[0050] The following specifically explains the civil aviation passenger revenue management system and method in the embodiments of the present invention.

[0051] The unified order in the embodiments of the present invention includes a three-layer structure: order, sub-order, and service. A single order contains several sub-orders, and each sub-order contains several services. Figure 2 For the schematic diagram of the order data structure in the embodiments of the present invention, refer to Figure 2 , the unified order structure. The first layer is the order, including all aviation and non-aviation services under the order. The second layer is the sub-order, including the services and prices of multiple sub-orders. The third layer is the detailed service, which is the detailed information of the services under each sub-order.

[0052] The unified order in the embodiments of the present invention has the following characteristics:

[0053] (1) Order identifier and order version number.

[0054] After the unified order is created, an order identifier is generated, such as the order ID. The order ID will remain unchanged as the unique identifier of this order. Subsequently, no matter how the information in the order changes, the order identifier will not change accordingly. After the order is created, various subsequent changes in the information in the order, such as the addition, modification, and deletion of services, are recorded as order changes. There is a version number information in the unified order. The initial version serial number of each order is 1, and each time a change occurs thereafter, the version number is incremented by 1, which is recorded as the order version number.

[0055] (2) Order status.

[0056] The order status includes open or closed. Open reflects the unused situation of the services in the order, and closed reflects that the services in the order have expired; the revenue impact status reflects whether there is an impact on revenue management.

[0057] The order is in an open state after it is created; when all services in the order are fully used or although the services are not used but exceed the specified validity period, the order is set to a closed state in the upstream order management system. The order information in the closed state will no longer change.

[0058] (3) Order change.

[0059] In the upstream order management system, there are records of order changes, which record the change information and the corresponding order version number for each order each time a change occurs. Whenever there is an information change in an order, the order management system will compare the information of the current version of the order with the information of the previous version, and record the specific change information in the order change record table and send it to the downstream civil aviation passenger revenue management system.

[0060] The changes that occur to an order are divided into three types: addition, deletion, and modification, which are saved in the order change record respectively. Refer to Figure 3 , Figure 3 This is a schematic diagram of the order change information record table in the embodiment of the present invention.

[0061] a. Order information addition: Save the details of the newly added information in the "Add new information" area;

[0062] b. Order information deletion: Save the details of the deleted information in the "Delete old information" area;

[0063] c. Order information modification: Save the details of the information before modification in the "Delete old information" area, and save the details of the information after modification in the "Add new information" area.

[0064] d. Record the change occurrence time, change type, and change reason.

[0065] In one embodiment, the order data received by the system carries order change record information, Figure 4 This is a schematic diagram of the data identification and parsing process in the embodiment of the present invention. Refer to Figure 4 , the order identification module 101 is specifically used for:

[0066] 1) Receive order data and store the order data in a temporary database; the temporary database is used for order identification and parsing processing;

[0067] 2) Sequentially read the target order data from the temporary database, and determine whether a new order is added according to the order version number of the target order data;

[0068] 3) Judge whether this target order is a newly added order or an order that has been established previously and has had information changes this time according to the order version number. Specifically:

[0069] 3.1) When the order version number reflects that the number of order changes is zero, mark the revenue impact status of the target order data as a new order;

[0070] That is, when the order version number is 1, it indicates a new order. All new orders need to undergo revenue management processing, and mark the revenue impact status of the target order data as a new order;

[0071] 3.2) When the order version number reflects that the number of order changes is greater than zero, that is, the order version number is greater than 1, it indicates that this is an order with information changes. Continue to determine whether the order version number of the order data with the same order identifier in the order database is 1 less than the order version number of the target order data (the difference is equal to 1), that is, determine whether it is a consecutive order:

[0072] 3.2.1) If it is 1 less, it means that the version information of the target order is correct, and continue with the marking process. Specifically, use the order change record information carried by the order data and the first preset file to mark the revenue impact status of the target order data as an order with changes and irrelevant to revenue management, or an order with changes and relevant to revenue management; the first preset file stores the mapping relationship between order change record information and revenue impact status;

[0073] 3.2.2) If it is not 1 less, it means that the version information of the target order is incorrect. Re-obtain the order data, obtain the correct order data from the upstream order management system, and then mark the revenue impact status of the re-obtained order data;

[0074] 4) When the revenue impact status of the order data is marked, hierarchically parse the order data in the temporary database to obtain parsing information and store it in the order database.

[0075] Among them, when processing the order version number of the target order, in order to improve the comparison efficiency, an order version number table is established and updated in real time in advance. The order version number table records the order ID and the latest version number of the order ID. Before starting to process the order version number of the target order, load the content of this table into the memory of the system server. For an order with a version number of 1, directly insert a new record into the order version number table; for an order with a version number greater than 1, compare the obtained version number with the order version number of the same order ID stored in the order version number table. If the version number of the target order is 1 greater than the version number stored in the table, it proves that the version information of this order is correct, and then update the latest version number to the table; if the version number of the target order is not 1 greater than the version number stored in the table, it indicates that the version information of this order is incorrect and it is necessary to request the order management system to re-transmit, and the order version number already stored in the table remains unchanged.

[0076] When marking the revenue impact status of target order data as a changed order and unrelated to revenue management, or a changed order and related to revenue management, using the order change record information carried in the order data and the first preset file, in the embodiments of the present invention, "change type" and "change reason" codes are defined. By reading these two types of codes, the specific type of order change can be known. During the entire life cycle of an order from creation to the use of all services, usually dozens or even hundreds of information changes occur, and quite a number of these change types are not relevant to subsequent revenue management. To improve the processing efficiency of the revenue management system, it is necessary to identify whether each change type that occurs will affect revenue management, and only screen out those "changes" that affect revenue management for processing. For this purpose, in the embodiments of the present invention, a first preset file is created to maintain whether the "change type" affects revenue calculation and store the mapping relationship between order change record information and revenue impact status, so as to screen out the changed orders that need to be processed. An example of the information maintained in the first preset file is shown in Table 1 below:

[0077] Table 1

[0078]

[0079] When hierarchically parsing order data, it is parsed in three layers: order, sub-order, and service. The parsed order information is saved to the order database at different levels.

[0080] Figure 5 For the schematic diagram of order data parsing in the embodiments of the present invention, refer to Figure 5 , when parsing order information, it is carried out according to the three-layer structure of the unified order and stored in the corresponding tables respectively. Through Figure 5 the multi-level grayscale, it can be seen that the first level is the order global information, including information such as order ID, order version number, and order status; the second level is all sub-order information under the order, including information such as sub-order ID, sub-order price, and sub-order status; the third level is the detailed service, specifically all service information under the sub-order, including the ID of each service, service status, and specific service information (such as flight, voyage), etc.

[0081] In one embodiment, the order database 102 is specifically used for: storing the order data with the same order identifier in layers; the first layer stores the order global information, the second layer stores all sub-order information under the order, and the third layer stores all service information under the sub-order.

[0082] Figure 6 For the schematic diagram of order data storage in the embodiments of the present invention, refer to Figure 6, after the information of the initial order (version number equal to 1) is stored in the order database, according to the characteristics of the unified order, for subsequent order changes (version number greater than 1), only the change information that occurs each time in the order change record needs to be parsed according to this three-layer structure and the specific content of each change is stored in the corresponding table. In this way, for the same order, its initial information and the information of subsequent changes can be linked together through the order ID. For multiple changes that occur to the same order, they can be distinguished by different version numbers corresponding to different changes. To quickly identify the content of each order change, the order version number of each change, the "change type", "change reason", and "change time" of addition, deletion, and modification can be defined as key information.

[0083] Figure 6 For the first-layer order information in order storage, key information such as order ID and version number exists. For the second-layer sub-order information, key information such as sub-order ID and version number exists. For the third-layer order information, key information such as service ID and version number exists.

[0084] The revenue management of the unified order is based on the order service information, and uses the unified order revenue management system to complete the confirmation of the amount to be settled for the services in the order, the calculation of revenue after the services are used, and the recalculation of the amount to be settled and the used revenue of each service after the order changes.

[0085] In one embodiment, the accounting module 103 is specifically used for:

[0086] When the revenue impact status of the order data is a new order, determine the increment of the amount to be settled using all the new service information of the order data, and determine the service usage revenue using the order status of the order data;

[0087] When the revenue impact status of the order data is a changed order and is related to revenue management, determine whether the order data of the previous version of the order data has been adjusted for usage revenue;

[0088] After the order data of the previous version of the order data has been adjusted for usage revenue, determine the addition, reduction, and change information of the services in the parsed information of the order data, use the addition, reduction, and change information of the services to adjust the amount to be settled, and adjust the usage revenue according to the usage situation of each service in the order status of the order data.

[0089] In specific implementation, for the order data that has been parsed, the corresponding revenue calculation process will be completed according to the different status identifiers assigned during order parsing, with the goal of completing the calculation and confirmation of the amount to be settled and the usage revenue of each service in the order.

[0090] Revenue calculation will be processed differently according to the order status. If the order is in the "open" state, it means that not all service items in the order have been used up. Different processing methods will be adopted by reading a series of identifiers assigned to the order during the parsing process.

[0091] Figure 7 This is a schematic diagram of the processing flow of the accounting module in the embodiment of the present invention. Refer to Figure 7 :

[0092] 1) If the order identifier is a new order, it means that this order is entering the revenue management system for the first time and needs to confirm the initial amount to be settled. Calculate the amount to be settled for this new order.

[0093] 2) If the order identifier is a changed order and has nothing to do with revenue management, no subsequent revenue calculation processing will be performed.

[0094] 3) If the order identifier is a changed order and is related to revenue management, it means that the order has changed after being created, and the changed information will affect the amount to be settled for the order. First, judge whether the previous version of this order has been subject to revenue calculation. If the previous version has not been subject to revenue calculation, calculate the amount to be settled for the previous version of the order first; if the previous version of the order has been subject to revenue calculation, it is necessary to further judge by combining the parsing change information of the new and old orders:

[0095] (3.1) If the order change parsing information shows that there are new services in this order, calculate the incremental amount to be settled for the new service items of this order; if the service status of these new service items is "used", confirm the usage revenue for these service items.

[0096] (3.2) If the order change parsing information shows that there are reduced services in this order, calculate the decremental amount to be settled for the reduced service items of this order; if the service status of these reduced service items is "used", delete the usage revenue for the reduced service items.

[0097] (3.3) If the order change parsing information shows that there are other order change situations in this order besides new services and reduced services, such as order amount changes, passenger cabin upgrades and downgrades and other changed service items, calculate the difference value for each part of the order change, and then calculate the incremental or decremental amount to be settled; if the service status of these changed service items is "used", it is necessary to adjust the usage revenue of the service according to the difference value.

[0098] When all services in a unified order have been used up, or after the usage period has expired, the order management system will set such orders to the closed state. For orders in the closed state, it is necessary to check the balance of the amount to be settled.

[0099] In one embodiment, the balance check module 104 is specifically configured to:

[0100] Perform balance checks on orders with a closed order status in the following three dimensions:

[0101] (1) Balance check of the amount due for settlement at the service level: Subtract the usage revenue of the service from the amount due for settlement of the service. When the result is zero, mark the order service level as balanced (a zero value represents balance; a non-zero value represents imbalance);

[0102] (2) Balance check of the amount due for settlement at the sub-order level: Subtract the total usage revenue of the sub-orders from the amount due for settlement of the sub-orders. When the result is zero, mark the order sub-order level as balanced;

[0103] (3) Balance check of the amount due for settlement at the order level: Subtract the total usage revenue summary of all sub-orders from the amount due for settlement of the order. When the result is zero, mark the order level as balanced;

[0104] If through the above three-dimensional checks, the differences between the amounts due for settlement and the usage revenues of the orders are all zero, it means that the order has been fully used and there is no balance of the amount due for settlement. That is, when the order with a closed order status is simultaneously marked as balanced at the order service level, the order sub-order level, and the order level, it is determined that the order with a closed order status passes the balance check, and this order can pass the balance check of the amount due for settlement. The revenue management system will record the time when this order is fully used.

[0105] If there is any dimension where the difference between the amount due for settlement and the usage revenue is not zero, it means that there is still unused service for this closed order, that is, there is still a balance of the amount due for settlement.

[0106] In one embodiment, the balance check module 104 is specifically configured to: When the balance check in any dimension fails, determine that the order with a closed order status fails the balance check and output imbalance reason information.

[0107] Figure 8 This is a schematic diagram of the processing flow of the balance check module in the embodiments of the present invention. Refer to Figure 8 , perform a balance check on the order with a closed order. When the balance check fails, the revenue management system will report an exception for the order that fails the balance check and prompt the airline to conduct an investigation. Specifically, conduct an investigation on the reason for the imbalance. After completing the investigation on the reason for the imbalance of the amount due for settlement, adjusting according to the investigation results and entering the reason code, the revenue management system will decide whether the order needs to be subjected to another balance check of the amount due for settlement or can ignore the balance check and continue processing based on the investigated reason code.

[0108] Finally, perform archiving processing on the order. If the order is in a closed state and passes the balance check of the amount due for settlement, the revenue management system will perform archiving processing on the order.

[0109] In one embodiment, the archiving module 105 is specifically configured to:

[0110] Use the preset order archiving configuration information to archive orders with a closed order status and passing the balance check; the preset order archiving configuration information includes the time information for moving from the order database to the order archive library corresponding to different archiving scenarios; the archiving scenarios include information on whether the revenue used in the order has been fully processed and information on whether there is a third-party service provided in the order.

[0111] During implementation, the corresponding order archiving time can be set according to different archiving scenarios, and order archiving can be flexibly performed by reading the order archiving settings. Refer to Table 2 below.

[0112] Table 2

[0113]

[0114] During the order archiving process, the following operations are performed according to the archiving scenario to which the closed order belongs:

[0115] 1) If the closed order meets the archiving scenario "the order has been fully used and there is no third-party service provided in the order", then according to the time when the order was fully used, after the Xth month from the time the order was used, move the order from the order database to the order archive library;

[0116] 2) If the closed order meets the archiving scenario "the order has been fully used and there is a third-party service provided in the order", which means there is still a business settlement between the airline and the third-party service provider in the order (usually taking a long time), it is necessary to move the order from the order database to the order archive library after the Yth month from the time the order was fully used;

[0117] 3) If the closed order meets the archiving scenario "the order has been partially used and there is still a balance of unsettled payments", which means there are still services with unconfirmed revenue in the order (such as services that have not been used beyond the expiration date in the order), then read the last usage time of each service in the order, and move the order from the order database to the order archive library after the Zth month from the last usage time of the order service. During the archiving process, confirm the revenue of the unused services and record it in the archive account.

[0118] In the embodiments of the present invention, a civil aviation passenger transportation revenue management method is also provided, as described in the following embodiments. Since the principle of solving problems by this method is similar to that of the civil aviation passenger transportation revenue management system, the implementation of this method can refer to the implementation of the civil aviation passenger transportation revenue management system, and the repeated parts will not be described again.

[0119] Figure 9 It is a schematic flowchart of the civil aviation passenger transportation revenue management method in the embodiments of the present invention, asFigure 9 As shown, the method includes:

[0120] Step 901: Receive order data, mark the revenue impact status for the order data, perform hierarchical parsing on the order data to obtain parsing information, and store it in the order database; the revenue impact status reflects whether there is an impact on revenue management; the parsing information includes order global information, sub-order information, and service information under the sub-order; the order global information includes the order status, and the order status includes open or closed. Open reflects the unused situation of each service in the order, and closed reflects that each service in the order has expired;

[0121] Step 902: Sequentially read the order data from the order database, and determine the order status and revenue impact status;

[0122] Step 903: When the order status is open and the revenue impact status is that there is an impact on revenue management, perform processing on increasing or decreasing the amount to be settled and adjust the revenue used for the order data; among them, use the service information under the sub-order to increase or decrease the amount to be settled, and use the order status to confirm or delete the revenue used;

[0123] Step 904: When the order status is closed, check whether the amount to be settled and the revenue used of the order are balanced. When the amount to be settled and the revenue used of the order are balanced, archive the order.

[0124] In an embodiment, the order data carries order change record information; after the order is created, it has a unique order identifier, and an order version number is generated every time the order changes; the order version number reflects the number of times the order has changed;

[0125] Receive order data, mark the revenue impact status for the order data, perform hierarchical parsing on the order data to obtain parsing information, including:

[0126] Receive order data and store the order data in the temporary database;

[0127] Sequentially read the target order data from the temporary database, and query the order data with the same order identifier from the order database according to the order identifier of the target order data;

[0128] When no order data with the same order identifier is queried from the order database, mark the revenue impact status of the target order data as a new order;

[0129] When order data with the same order identifier is queried from the order database, determine whether the order version number of the order data with the same order identifier in the order database is 1 less than the order version number of the target order data:

[0130] If it is less than 1, use the order change record information carried in the order data and the first preset file to mark the revenue impact status of the target order data as a changed order and irrelevant to revenue management, or a changed order and relevant to revenue management; the first preset file stores the mapping relationship between the order change record information and the revenue impact status.

[0131] If it is not less than 1, re-obtain the order data and mark the revenue impact status of the re-obtained order data.

[0132] When the revenue impact status of the order data is marked, hierarchically parse the order data in the temporary database to obtain parsing information and store it in the order database.

[0133] In one embodiment, the order data with the same order identifier is hierarchically stored in the order database; the first layer stores the order global information, the second layer stores all sub-order information under the order, and the third layer stores all service information under the sub-order.

[0134] In one embodiment, performing an increase or decrease process on the amount to be settled and using revenue adjustment for the order data includes:

[0135] When the revenue impact status of the order data is a new order, determine the increment of the amount to be settled using all the new service information of the order data, and determine the service usage revenue using the order status of the order data.

[0136] When the revenue impact status of the order data is a changed order and relevant to revenue management, determine whether the previous version of the order data of the order data has been subject to usage revenue adjustment.

[0137] After the previous version of the order data of the order data has been subject to usage revenue adjustment, determine the increase, decrease, and change information of the services in the parsing information of the order data, use the increase, decrease, and change information of the services to adjust the amount to be settled, and adjust the usage revenue according to the usage situation of each service in the order status of the order data.

[0138] In one embodiment, checking whether the amount to be settled and the usage revenue of the order are balanced includes:

[0139] Perform the following three-dimensional balance checks on the orders with the order status of closed:

[0140] Subtract the usage revenue of the service from the amount to be settled of the service. When the result is zero, mark the order service layer as balanced.

[0141] Subtract the total usage revenue of the sub-orders from the amount to be settled of the sub-order. When the result is zero, mark the order sub-order layer as balanced.

[0142] Subtract the total usage revenue summary of all sub-orders from the amount to be settled of the order. When the result is zero, mark the order layer as balanced;

[0143] When an order with a closed order status is simultaneously marked with order service layer balance, order sub - order layer balance, and order layer balance, it is determined that the order with a closed order status passes the balance check.

[0144] In one embodiment, the following three - dimensional balance checks are performed on an order with a closed order status, including:

[0145] When the balance check for any dimension fails, it is determined that the order with a closed order status fails the balance check, and the imbalance reason information is output.

[0146] In one embodiment, archiving an order includes:

[0147] Using preset order archiving configuration information, archiving an order with a closed order status that passes the balance check; the preset order archiving configuration information includes time information for moving from the order database to the order archive library corresponding to different archiving scenarios; the archiving scenarios include information on whether the income used in the order has been fully processed and information on whether there is third - party provided service in the order.

[0148] Figure 10 This is a specific example diagram of the civil aviation passenger revenue management method in the embodiments of the present invention. As Figure 10 shown, it shows an overview of the overall processing flow of order revenue management, mainly including order information identification and parsing of order data, storage in the order database, unified order sales, calculation of used income; balance checks on order sales and use information, and data archiving.

[0149] The embodiments of the present invention also provide 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 civil aviation passenger revenue management method is implemented.

[0150] The embodiments of the present invention also provide a computer - readable storage medium. The computer - readable storage medium stores a computer program, and when the computer program is executed by a processor, the above - mentioned civil aviation passenger revenue management method is implemented.

[0151] The embodiments of the present invention also provide a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the above - mentioned civil aviation passenger revenue management method is implemented.

[0152] In the embodiments of the present invention, the civil aviation passenger revenue management system can, in a unified order environment, realize order data recognition, parsing, calculation and confirmation of sales pending settlement and service usage revenue, balance check of sales and service usage information for pending settlement until the order revenue information is archived, solving the problem that the current airline revenue management system for processing air tickets / miscellaneous fee bills cannot handle the revenue management of unified orders. After airlines replace the current air ticket / miscellaneous fee bill system with a unified order form in the future, the civil aviation passenger revenue management system based on the method of the embodiments of the present invention can be widely applied to airlines.

[0153] 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.

[0154] The present invention is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to the embodiments of the present invention. It should be understood that each flow and / or block in the flowchart and / or block diagram, and the combination of flows and / or blocks in the flowchart and / or block diagram, can be realized 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 realizing the specified functions in Figure 1 one or more flows Figure 1 or blocks or a combination of multiple flows and / or blocks.

[0155] These computer program instructions can 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 generate a manufactured article including instruction means, and the instruction means realizes the specified functions in Figure 1 one or more flows Figure 1 or blocks or a combination of multiple flows and / or blocks.

[0156] These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process. Thus, the instructions executed on the computer or other programmable device provide means for realizing the specified functions in Figure 1 one or more flows Figure 1Steps of the functions specified in one or more boxes.

[0157] In the above-described specific embodiments, the object, technical solution, and beneficial effects of the present invention have been further described in detail. It should be understood that the above are only 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 principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. An airline passenger revenue management system, characterized in that, Including: An order identification module, an order database, an accounting module, a balance check module, and an archiving module; The order identification module is used to: receive order data; Mark the revenue impact status for the order data; perform hierarchical parsing on the order data to obtain parsing information; the parsing information includes order global information, sub-order information, and service information under the sub-order; The order global information includes the order status, and the order status includes open or closed. Open reflects the unused situation of each service in the order, and closed reflects that each service in the order has expired; the revenue impact status reflects whether there is an impact on revenue management; the order has a three-layer structure: order, sub-order, and service. After the order is created, it has a unique order identifier, and each time the order changes, an order version number is generated; The order version number reflects the number of times the order has changed; The order data carries order change record information; Using the order change record information carried by the order data and the first preset file, mark the revenue impact status of the target order data as a changed order and irrelevant to revenue management, or a changed order and relevant to revenue management; the first preset file stores the mapping relationship between the order change record information and the revenue impact status; The order database is used to: store the order data processed by the order identification module; The accounting module is used to: perform addition and subtraction processing on the payable amount to be settled and use revenue adjustment for the order data in the order database that has an impact on revenue management; among them, use the service information under the sub-order to increase or decrease the payable amount to be settled, and use the order status to confirm or delete the used revenue; The balance check module is used to check whether the payable amount to be settled and the used revenue of the order with the order status of closed are balanced; The archiving module is used to archive the order with the order status of closed and passing the balance check.

2. The civil aviation passenger revenue management system according to claim 1, wherein Specifically, the order identification module is used to: Receive order data and store the order data in the temporary database; Read the target order data sequentially from the temporary database, and determine whether a new order is added according to the order version number of the target order data; When the number of times the order version number reflects the order has changed is zero, mark the revenue impact status of the target order data as a new order; When the number of times the order version number reflects the order has changed is greater than zero, judge whether the order version number of the order data with the same order identifier in the order database is 1 less than the order version number of the target order data: If it is 1 less, use the order change record information carried by the order data and the first preset file to mark the revenue impact status of the target order data as a changed order and irrelevant to revenue management, or a changed order and relevant to revenue management; If it is not 1 less, re-obtain the order data and mark the revenue impact status for the re-obtained order data; When the revenue impact status of the order data is marked, perform hierarchical parsing on the order data in the temporary database to obtain parsing information and store it in the order database.

3. The civil aviation passenger revenue management system according to claim 2, wherein Specifically, the order database is used to: store the order data with the same order identifier in layers; the first layer stores the order global information, the second layer stores all sub-order information under the order, and the third layer stores all service information under the sub-order.

4. The civil aviation passenger revenue management system according to claim 2, wherein Specifically, the accounting module is used to: When the revenue impact status of the order data is a new order, determine the increment of the amount to be settled using all the new service information of the order data, and determine the service usage revenue based on the order status of the order data. When the revenue impact status of the order data is a changed order and is related to revenue management, determine whether the usage revenue of the previous version of the order data has been adjusted. After the usage revenue of the previous version of the order data has been adjusted, determine the increase, decrease, and change information of the services in the parsed information of the order data. Use the increase, decrease, and change information of the services to adjust the amount to be settled, and adjust the usage revenue according to the usage status of each service in the order status of the order data.

5. The civil aviation passenger revenue management system according to claim 1, characterized in that, The balance check module is specifically used for: Perform balance checks on orders with the order status of closed in the following three dimensions: Subtract the service usage revenue from the amount to be settled for the service. When the result is zero, mark the order service layer as balanced. Subtract the total usage revenue of the sub-orders from the amount to be settled for the sub-orders. When the result is zero, mark the order sub-order layer as balanced. Subtract the total usage revenue summary of all sub-orders from the amount to be settled for the order. When the result is zero, mark the order layer as balanced. When an order with the order status of closed is simultaneously marked as balanced in the order service layer, the order sub-order layer, and the order layer, determine that the order with the order status of closed passes the balance check.

6. The civil aviation passenger revenue management system according to claim 5, characterized in that, The balance check module is specifically used for: When the balance check in any dimension fails, determine that the order with the order status of closed fails the balance check and output the imbalance reason information.

7. The civil aviation passenger transport revenue management system according to claim 1, characterized in that, The archiving module is specifically used for: Archive the orders with the order status of closed and passing the balance check using the preset order archiving configuration information; the preset order archiving configuration information includes the time information for moving from the order database to the order archive library corresponding to different archiving scenarios; the archiving scenarios include information on whether the usage revenue in the order has been fully processed and information on whether there are services provided by a third party in the order.

8. A civil aviation passenger revenue management method, characterized in that Include: Receive order data, mark the revenue impact status for the order data, perform hierarchical parsing on the order data to obtain parsed information, and store it in the order database. The revenue impact status reflects whether there is an impact on revenue management; the parsed information includes order global information, sub-order information, and service information under the sub-orders. The order global information includes the order status, and the order status includes open or closed. Open reflects the unused situation of each service in the order, and closed reflects that each service in the order has expired; the order contains a three-layer structure: order, sub-order, and service. After the order is created, it has a unique order identifier, and each time the order changes, an order version number is generated. The order version number reflects the number of times the order has changed. The order data carries order change record information. Use the order change record information carried by the order data and the first preset file to mark the revenue impact status of the target order data as a changed order and not related to revenue management, or a changed order and related to revenue management. The first preset file stores the mapping relationship between the order change record information and the revenue impact status. Read the order data from the order database in sequence to determine the order status and revenue impact status. When the order status is open and the revenue impact status is having an impact on revenue management, perform the processing of increasing or decreasing the amount to be settled for the order data and use revenue adjustment; among them, use the service information under the sub - order to increase or decrease the amount to be settled, and use the order status to confirm or delete the used revenue; When the order status is closed, check whether the amount to be settled and the used revenue of the order are balanced. When the amount to be settled and the used revenue of the order are balanced, archive the order.

9. The civil aviation passenger transportation revenue management method according to claim 8, wherein, Receive the order data, mark the revenue impact status for the order data, and perform hierarchical parsing on the order data to obtain parsing information, including: Receive the order data and store the order data in the temporary database; Read the target order data sequentially from the temporary database, and query the order data with the same order identifier from the order database according to the order identifier of the target order data; When no order data with the same order identifier is queried from the order database, mark the revenue impact status of the target order data as a new order; When order data with the same order identifier is queried from the order database, determine whether the order version number of the order data with the same order identifier in the order database is 1 less than the order version number of the target order data: If it is 1 less, use the order change record information carried by the order data and the first preset file to mark the revenue impact status of the target order data as a changed order and irrelevant to revenue management, or a changed order and relevant to revenue management; If it is not 1 less, re - obtain the order data and mark the revenue impact status for the re - obtained order data; When the marking of the revenue impact status of the order data is completed, perform hierarchical parsing on the order data in the temporary database to obtain parsing information and store it in the order database.

10. The civil aviation passenger revenue management method according to claim 9, characterized in that, In the order database, the order data with the same order identifier is stored hierarchically; The first layer stores the order global information, the second layer stores all sub - order information under the order, and the third layer stores all service information under the sub - order.

11. The civil aviation passenger revenue management method according to claim 9, characterized in that, Perform the processing of increasing or decreasing the amount to be settled for the order data and use revenue adjustment, including: When the revenue impact status of the order data is a new order, determine the increment of the amount to be settled using all the new service information of the order data, and determine the service used revenue using the order status of the order data; When the revenue impact status of the order data is a changed order and relevant to revenue management, judge whether the order data of the previous version of the order data has been subjected to used revenue adjustment; After the order data of the previous version of the order data has been subjected to used revenue adjustment, determine the increase, decrease, and change information of the services in the parsing information of the order data, use the increase, decrease, and change information of the services to adjust the amount to be settled, and adjust the used revenue according to the usage situation of each service in the order status of the order data.

12. The civil aviation passenger revenue management method according to claim 8, characterized in that, Check whether the amount to be settled and the used revenue of the order are balanced, including: Perform the following three - dimensional balance checks on the order with the order status of closed: Subtract the used revenue of the service from the amount to be settled of the service. When the result is zero, mark the service layer of the order as balanced; Subtract the total used revenue of the sub - order from the amount to be settled of the sub - order. When the result is zero, mark the sub - order layer of the order as balanced; Subtract the total used revenue summary of all sub - orders from the amount to be settled of the order. When the result is zero, mark the order layer as balanced; When an order with the order status of "closed" is simultaneously marked as balanced at the order service layer, sub-order layer, and order layer, it is determined that the order with the order status of "closed" passes the balance check.

13. The civil aviation passenger revenue management method according to claim 12, wherein Perform balance checks on orders with the order status of "closed" in the following three dimensions, including: When the balance check in any dimension fails, it is determined that the order with the order status of "closed" fails the balance check, and the imbalance reason information is output.

14. The civil aviation passenger revenue management method according to claim 8, wherein, Archive the order, including: Using the preset order archiving configuration information, archive the orders with the order status of "closed" and passing the balance check; the preset order archiving configuration information includes the time information for moving from the order database to the order archive library corresponding to different archiving scenarios; the archiving scenarios include information on whether the revenues used in the order have been fully processed and information on whether there is a third-party service provided in the order.

15. A computer device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method according to any one of claims 8 to 14.

16. 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, it implements the method according to any one of claims 8 to 14.

17. A computer program product, characterized in that, The computer program product includes a computer program, and when the computer program is executed by a processor, it implements the method according to any one of claims 8 to 14.

Images