Settlement and reconciliation method, device and system suitable for air ticket distribution

Abstract

The invention discloses a settlement and reconciliation method, device and system suitable for distribution airline tickets. The method comprises the following steps: acquiring airline ticket sales data of an agent based on a BOP platform; acquiring an account checking file from a ticket business data overall planning center; the ticket business data overall planning center is used for summarizing full-amount air ticket sales data of an airline company and each distribution platform; comparing the air ticket sales data with the reconciliation file, and generating an adjustment list according to a comparison result; the comparison result comprises difference ticket information; the adjustment sheet comprises the amount payable and the amount receivable of the agent corresponding to the difference ticket information; and pushing the adjustment list to the agent. According to the invention, full-process automatic account checking and settlement can be carried out, and the efficiency, accuracy and compliance of airline ticket sales and settlement are improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of civil aviation ticket distribution, and in particular to a settlement and reconciliation method, device and system suitable for distributing tickets. BACKGROUND

[0002] In the traditional BSP (Billing and Settlement Plan) field, after selling tickets based on a distribution platform, the agent user needs to reconcile and settle with the corresponding airline according to the different distribution records of each airline. At the same time, the methods and ways of reconciliation and settlement of each airline are quite different, and the interaction between systems is very complicated. For the agent user, the reconciliation and settlement is relatively complicated, for the airline, the settlement period is long, easy to make mistakes, and the cost is high. In the prior art, there are the following settlement and reconciliation methods for the BSP distribution field:

[0003] (1) Manual reconciliation + bank bulk transfer mode.

[0004] Small and medium-sized airlines or low-cost airlines have long relied on the traditional process of "agent submitting paper bills → airline finance manual checking → bank bulk transfer". This mode completely relies on manual operation, not only is inefficient (a single batch of reconciliation can take up to 5-10 working days), but also has a high error rate. At the same time, there are risks such as data tampering and operation errors in the manual processing process, and the safety of funds is difficult to guarantee. This mode has been gradually eliminated because it cannot bear the business scale.

[0005] (2) Airline self-built closed settlement system.

[0006] Some large airlines have tried to build independent settlement systems to achieve reconciliation and fund transfer through direct connection with agent terminals. However, such systems have inherent limitations: first, the coverage is limited, only a few agents with close cooperation can be connected, and it cannot adapt to the entire industry distribution network; second, the maintenance cost is high, a large amount of resources need to be invested to develop interfaces, update rules (such as agent fee adjustment, change of refund and change rules), and it is difficult to compatible with emerging distribution channels (such as OTA platform, NDC channel); third, the data island problem is prominent, it cannot realize cross-subject data collaboration with other airlines and payment institutions, and the accuracy is difficult to guarantee (according to industry statistics, the reconciliation error rate of such systems is about 0.3%-0.5%).

[0007] (3) Third-party payment platform dominated clearing mode.

[0008] Some payment institutions have attempted to enter the airline ticket settlement scenario with a "aggregated payment + simple reconciliation" model, aggregating funds through a unified acquiring interface and then distributing revenue proportionally. However, this model lacks deep adaptation to the airline's business logic: on the one hand, it cannot handle the complex rules in ticket sales (such as group ticket revenue sharing and cabin class-based pricing); on the other hand, the separation of fund flow and ticket information flow requires manual linking of payment transactions and sales records during reconciliation, which can easily lead to problems such as "overpayment and underpayment" and "missed or incorrect orders." In addition, the data storage and management of payment institutions are difficult to meet the regulatory requirements of the civil aviation industry (such as data retention within China and audit traceability timeliness), posing compliance risks.

[0009] (4) General-purpose enterprise financial shared system.

[0010] Some airlines have attempted to integrate ticket settlement into their corporate shared service centers, relying on general financial software (such as SAP and Oracle) to streamline the process. However, these systems are not specifically designed for airline ticketing scenarios and suffer from functional gaps: for example, they cannot automatically identify industry-specific data segments such as ticket validity periods and cabin class, requiring manual input of key information; their reconciliation rules are rigid (e.g., only supporting simple amount comparisons), making it difficult to adapt to complex scenarios such as "tiered calculation of agency fees" and "cross-airline intermodal revenue sharing." According to actual test data, the efficiency of general financial systems in processing airline ticket reconciliation is only 30%-40% of that of the BOP (BSP Online Payment) platform, and a large number of customized plugins need to be developed, resulting in higher overall costs.

[0011] (5) Emerging blockchain-based distributed settlement solutions.

[0012] Blockchain technology, due to its immutability, is considered a potential alternative. However, it faces significant bottlenecks in airline ticketing scenarios: First, performance limitations—public blockchains typically process fewer than 1,000 transactions per second (TPS), making it difficult to support the concurrent demands of airlines during peak periods; second, poor rule flexibility—modification of smart contracts after deployment is costly, hindering rapid responses to high-frequency business changes such as adjustments to airline agency fees and changes in refund and change rules; and third, weak ecosystem compatibility—all participants (airlines, agents, banks, and regulatory agencies) must connect to the same blockchain network, resulting in high collaboration costs.

[0013] In summary, there is an urgent need for an efficient, accurate, and cost-effective reconciliation and settlement method for individual invoice sales. Summary of the Invention

[0014] This invention provides a settlement and reconciliation method suitable for airline ticket distribution. Relying on a mainstream distribution platform such as the BOP platform, it automates the entire reconciliation and settlement process, improving the efficiency, accuracy, and compliance of airline ticket sales settlement. The method includes:

[0015] Obtain ticket sales data from agents based on the BOP platform;

[0016] Obtain reconciliation files from the ticketing data coordination center; the ticketing data coordination center is used to aggregate all ticket sales data from airlines and various distribution platforms;

[0017] The airline ticket sales data is compared with the reconciliation documents, and an adjustment order is generated based on the comparison results. The comparison results include discrepancy ticket information. The adjustment order includes the agent's payable amount and receivable amount corresponding to the discrepancy ticket information.

[0018] The adjustment order will be sent to the agent.

[0019] This invention also provides a settlement and reconciliation device suitable for airline ticket distribution. Relying on a mainstream general distribution platform such as the BOP platform, it performs fully automated reconciliation and settlement, improving the efficiency, accuracy, and compliance of airline ticket sales settlement. The device includes:

[0020] The multi-source data access module is used to obtain ticket sales data from agents based on the BOP platform; and to obtain reconciliation files from the ticketing data coordination center; the ticketing data coordination center is used to aggregate all ticket sales data from airlines and various distribution platforms;

[0021] The intelligent reconciliation processing module is used to compare ticket sales data with reconciliation files and generate adjustment orders based on the comparison results; the comparison results include discrepancy ticket information; the adjustment order includes the agent's payable amount and receivable amount corresponding to the discrepancy ticket information;

[0022] The adjustment module is used to push adjustment orders to agents.

[0023] This invention also provides a settlement and reconciliation system suitable for airline ticket distribution. Relying on a mainstream distribution platform such as the BOP platform, it automates the entire reconciliation and settlement process, improving the efficiency, accuracy, and compliance of airline ticket sales settlement. The system includes: a transaction processing server, a data storage array, and a ticketing data coordination center. The transaction processing server implements the settlement and reconciliation method for airline ticket distribution, the data storage array stores real-time ticket sales data, and the ticketing data coordination center aggregates all ticket sales data from airlines and various distribution platforms.

[0024] This invention also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the above-described settlement and reconciliation method applicable to airline ticket distribution.

[0025] This invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described settlement and reconciliation method applicable to airline ticket distribution.

[0026] This invention also provides a computer program product, which includes a computer program that, when executed by a processor, implements the above-described settlement and reconciliation method applicable to airline ticket distribution.

[0027] This invention, in its embodiment, acquires ticket sales data from agents using the BOP platform; obtains reconciliation files from the ticketing data coordination center; compares the ticket sales data with the reconciliation files, generates adjustment orders based on the comparison results, and pushes the adjustment orders to agents. This invention, based on the BOP platform, achieves unified reconciliation in the civil aviation ticketing distribution field, avoiding the cumbersome process of agents separately contacting different airlines in the traditional model. It reduces the workload of manual data entry and verification, achieves standardized management of ticket reconciliation and settlement, significantly improves reconciliation efficiency, and reduces connection problems caused by differences in airline systems. Through centralized data comparison, discrepancies between sales data and settlement amounts can be detected promptly, reducing issues such as missed orders and incorrect accounts, improving the accuracy of financial settlement, avoiding the fund management risks caused by decentralized reconciliation in the traditional model, and improving the accuracy and compliance of airline ticket sales settlement. Attached Figure Description

[0028] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0029] Figure 1 This is a flowchart illustrating the settlement and reconciliation method applicable to airline ticket distribution in an embodiment of the present invention;

[0030] Figure 2 This is a specific example diagram of a settlement and reconciliation method applicable to the distribution of airline tickets in this embodiment of the invention;

[0031] Figure 3 This is another specific example diagram of a settlement and reconciliation method applicable to the distribution of airline tickets in this invention.

[0032] Figure 4 This is a schematic diagram of a settlement and reconciliation device applicable to the distribution of airline tickets in an embodiment of the present invention;

[0033] Figure 5 This is a schematic diagram of a computer device in an embodiment of the present invention. Detailed Implementation

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

[0035] First, the technical terms involved in the embodiments of the present invention will be explained.

[0036] IATA: International Air Transport Association.

[0037] Dovepay: An independent third-party payment platform.

[0038] China BSP Online Payment Platform (BOP): This is a brand-new payment and settlement business model for BSP tickets launched for BSP agents. The BOP platform is a technical platform that provides BSP agents with online ticketing, payment and settlement services. BSP tickets issued through this platform are collectively referred to as BOP tickets.

[0039] Agent: A person who opens a BOP business account with Depay and pre-deposits funds in the BOP account for subsequent payment and ticketing for airline NDC channel business operations.

[0040] The acquisition, storage, use, and processing of data in this application all comply with the relevant provisions of national laws and regulations.

[0041] Currently, most known ticket reconciliation and settlement methods in the civil aviation sector are applied to airlines' own platforms. Based on the sale of airline tickets, reconciliation and settlement are primarily handled by resolving discrepancies in ticket amounts and settling payments between passengers and airlines. In the traditional airline BSP (Bill of Services) ticket distribution sector, reconciliation and settlement also occur between corporate users (agents) and each individual airline. There is no dedicated, integrated, unified reconciliation and settlement method specifically for the BSP ticket distribution sector.

[0042] This invention builds an efficient and accurate settlement and reconciliation system based on the BOP platform, and proposes a settlement and reconciliation method and device suitable for airline ticket sales, providing strong technical support for the full-process fund management of airline ticket sales.

[0043] Figure 1 This is a flowchart illustrating the settlement and reconciliation method applicable to airline ticket distribution in an embodiment of the present invention, such as... Figure 1 As shown, the method includes:

[0044] Step 101: Obtain the agent's ticket sales data based on the BOP platform;

[0045] Step 102: Obtain the reconciliation file from the ticketing data coordination center; the ticketing data coordination center is used to aggregate all ticket sales data from airlines and various distribution platforms;

[0046] Step 103: Compare the ticket sales data with the reconciliation file, and generate an adjustment order based on the comparison results; the comparison results include discrepancy ticket information; the adjustment order includes the agent's payable amount and receivable amount corresponding to the discrepancy ticket information;

[0047] Step 104: Push the adjustment order to the agent.

[0048] After an agent successfully sells airline BOP tickets through the BOP platform, the reconciliation and settlement process is initiated in an orderly manner according to the method described in this embodiment of the invention, so as to achieve seamless connection and precise control of each link.

[0049] In practice, the process begins by acquiring real-time ticket sales data from agents through the BOP platform. This data includes, but is not limited to, one or any combination of, the following: ticket number, airline identifier, agent identifier, sales time, ticket price, and payment method. Then, reconciliation files are obtained from the ticketing data coordination center, which aggregates all ticket sales data from airlines and various distribution platforms.

[0050] In this embodiment, the ticketing data coordination center is, for example, the International Air Transport Association (IATA) data processing center (DPC). The IATA data processing center centrally collects ticket sales data from airlines, GDS (Global Distribution System), BOP platforms, and other organizations certified by IATA.

[0051] In this embodiment, the reconciliation document is used as a reference benchmark to compare the ticket sales data with the reconciliation document.

[0052] In one embodiment, comparing ticket sales data with reconciliation documents and generating adjustment orders based on the comparison results includes: periodically comparing ticket sales data with reconciliation documents and generating adjustment orders based on the comparison results; the periodicity includes daily and set settlement cycles.

[0053] The settlement cycle can be set by DPC and / or the airline.

[0054] For example, on the set settlement date, reconciliation with DPC is initiated. Thanks to optimized program processing time, massive amounts of cross-border transaction data can be processed quickly, completing data comparison, discrepancy analysis, and confirmation in a short time, significantly reducing the cycle and saving time for subsequent fund settlement.

[0055] In one embodiment, before comparing the ticket sales data with the reconciliation file, the method further includes:

[0056] Every day, the full daily flight ticket sales data is obtained from GDS. Based on the full daily flight ticket sales data, the sales records or payment records of the full daily flight ticket sales data are aligned with the agent flight ticket sales data of the BOP platform for the same day, and the agent flight ticket sales data with supplementary payment records is obtained.

[0057] The process of periodically comparing ticket sales data with reconciliation documents and generating adjustment orders based on the comparison results includes:

[0058] Upon reaching the set settlement date, the agent's ticket sales data, which are supplementary payment records summarized within the BOP platform's settlement cycle, are compared with the reconciliation files from the ticketing data coordination center. An adjustment order is then generated based on the comparison results.

[0059] In one embodiment, obtaining the reconciliation file from the ticketing data coordination center may include: using a secure file transfer service based on the SSH protocol to obtain the reconciliation file from the ticketing data coordination center.

[0060] For example, DPC uses a dedicated SFTP server cluster equipped with a dedicated encryption chip to enhance the encryption processing capabilities of data file transmission with airlines and agents, and to cope with scenarios where multiple entities upload sales data at the same time.

[0061] In this embodiment, GDS may also use a dedicated SFTP server cluster to store its online and offline ticket sales data.

[0062] In one embodiment, the comparison result includes overage / underage information; comparing ticket sales data with reconciliation documents may include:

[0063] Based on the reconciliation file, the ticket sales data is subjected to a first-level verification. Ticket sales data that fails the first-level verification is marked as abnormal. The first-level verification means comparing the ticket sales data with the specified core fields of the reconciliation file using the ticket number as an index.

[0064] A second-level verification is performed on the ticket sales data that passed the first-level verification and the reconciliation file. The second-level verification means: using the ticket number as an index, generating over / under payment information based on the amount difference; the over / under payment information includes payment record differences and amount differences.

[0065] An adjustment order is generated based on the comparison results. This can include generating an adjustment order after the overage / underage information has been approved.

[0066] In this embodiment, the comparison process is automatically executed according to the three-level reconciliation logic to ensure data consistency.

[0067] The first-level verification is based on basic information matching, using the ticket number as a unique index to compare the sales data with the specified core fields in the reconciliation file. These specified core fields include, for example, the airline code (airline identifier), the sales date, and the IATA class. The airline code, sales date, and IATA class must be completely consistent.

[0068] The second-level verification is for fund flow matching. For records that pass the first-level verification, the payment data is linked to verify the consistency of funds between the two parties. The relationship between the reconciliation file data and the BOP ticket sales data is bound by the unique ticket number. If the amount in the reconciliation file and the BOP sales amount are inconsistent, the payment record difference and the amount difference are marked, the reconciliation record is marked as abnormal, and the data is uniformly summarized and sent to the business operations personnel for verification.

[0069] The three-level verification involves a rule engine and manual review. For abnormal data with inconsistent amounts, after review by the rule engine and manual review, a reconciliation result is obtained, and an adjustment order is generated. The adjustment order must include at least the amount payable and the amount receivable by the agent corresponding to the discrepancy in the invoice information.

[0070] The adjustment order will be sent to the agent, showing the agent the reconciliation results.

[0071] In one embodiment, after the adjustment order is pushed to the agent, the method may further include:

[0072] Receive confirmation or modification suggestions from the agent regarding the adjustment order;

[0073] Modify the adjustment order according to the modification suggestions, push the modified adjustment order to the agent, and receive the agent's confirmation of the adjustment order;

[0074] Based on the agent's confirmation of the adjustment order, the funds are transferred to the airline's or agent's account; the airline's or agent's account has pre-deposited funds.

[0075] The adjustment order must include at least the agent information, adjustment amount, and payment period, and send the transfer instruction to the partner bank through an encrypted interface (using HTTPS + national cryptographic SM4 algorithm).

[0076] The adjustment order will be sent to the agent. After the agent approves it, the funds will be automatically transferred from the agent's account to the airline's account. If a refund is required from the airline to the agent, the adjustment order will be sent to the airline. After the airline approves it, the funds will be transferred from the airline's account to the agent's account.

[0077] In one embodiment, before comparing the ticket sales data with the reconciliation file, the method may further include:

[0078] The ticket sales data and reconciliation files are preprocessed separately to obtain preprocessed ticket sales data and reconciliation files; the preprocessing includes format standardization, abnormal field repair, and fingerprinting.

[0079] Furthermore, the ticket sales data was compared with the reconciliation documents, including:

[0080] The pre-processed ticket sales data is compared with the reconciliation documents.

[0081] Figure 2 This is a specific example diagram of a settlement and reconciliation method applicable to the distribution of airline tickets in an embodiment of the present invention, as shown below. Figure 2 The diagram illustrates the reconciliation process. Based on "data-driven, rule-based, and automated execution," the entire reconciliation process after ticket sales is automated. The specific implementation method is as follows:

[0082] Step 201: Data collection and analysis for reconciliation.

[0083] The data obtained from the BOP platform data center includes at least the ticket number, airline code, agent ID, sales time, ticket price, and payment method.

[0084] Daily reconciliation data: The system automatically retrieves the daily reconciliation TI file from the GDS's dedicated SFTP server cluster.

[0085] Reconciliation data for the period: The system automatically retrieves the settlement period reconciliation RET file from the IATA's dedicated SFTP server cluster.

[0086] TI and RET are file extensions, indicating the file format. Daily reconciliation data is obtained by BOP from TravelSky and is used to reconcile BOP's daily sales data with TravelSky's sales data. Daily reconciliation only aligns payment records, not specific amounts. Periodic reconciliation data is obtained by BOP from IATA and is used for final verification with standard data issued by IATA. Periodic reconciliation includes comprehensive alignment of payment records, amounts, etc.

[0087] The system analyzes ticket sales data and reconciliation documents, using agents and IATA numbers as dimensions to collect statistics on ticketing information, ticket numbers, amounts, and statuses. This data is then entered into the system, and the status is updated to "analyzed".

[0088] Step 202: Data standardization and cleaning.

[0089] Unified format: Based on preset mapping rules (stored in the rule base), heterogeneous data is converted into a unified format. For example, the date format is unified as "yyyy-MM-dd HH:mm:ss", and the amount is retained to two decimal places (rounding rules).

[0090] Abnormal field repair: Perform automatic repair (such as completing default values) or mark abnormal fields (such as null values ​​or incorrect formats) for manual verification.

[0091] Fingerprinting: A unique checksum is generated for each piece of data using the SHA-256 hash algorithm, which is used for subsequent data integrity verification.

[0092] Step 203: Intelligent reconciliation processing.

[0093] The comparison process is automatically executed according to the three-level reconciliation logic to ensure data consistency.

[0094] a. Level 1 verification: Basic information matching.

[0095] Using the ticket number as a unique index, we compare the core fields of sales data with airline benchmark data:

[0096] The airline code, sales date, and IATA class must be exactly the same;

[0097] The deviation between the sales amount on Depay and the sales amount in the reconciliation document must be less than or equal to 0.1% (rounding error is allowed);

[0098] Records that fail the verification are marked as "basic anomalies," triggering an alert and pushing it to business operations personnel, who must correct the data before 3 PM that day.

[0099] b. Secondary verification: fund flow matching.

[0100] For records that pass the first-level verification, the payment data is linked to verify the consistency of funds between the two parties:

[0101] Payment amount for invoices = face value of invoices + taxes and fees + face value of invoices × agency fee rate (or fixed agency fee) (automatically calculated by the formula engine);

[0102] When an agent and an airline disagree on liability or financial settlement for a particular ticket, the agent can propose an agreement on the ticket payment amount. In subsequent processing of these discrepancies, this embodiment of the invention automatically calculates the ticket payment amount, adjusts it in an adjustment form, and presents it to the agent for review.

[0103] During implementation, the relationship between reconciliation data and BOP sales center data is linked through a unique ticket number;

[0104] Mark payment record differences:

[0105] If there is no payment record in the reconciliation file but there is a payment record in the BOP sales data, issue a refund order and deduct the payment from the account; if there is a record in the reconciliation file but no record in the BOP sales data, issue a payment order and deduct the payment from the account.

[0106] Differences in marked amounts:

[0107] If the reconciliation file contains payment records and the BOP contains canceled payment records, these will be displayed as a shortfall on the long / shortfall management page. In this embodiment, a long / shortfall management page is provided to display long / shortfall information.

[0108] The system uses the ticket number as an index and marks the difference in amount as either an overage or a shortage; an overage indicates that the BOP ticket sales data amount is greater than the amount in the reconciliation file; a shortage indicates that the BOP ticket sales data amount is less than the amount in the reconciliation file.

[0109] Ticket refunds are processed automatically and displayed as long-term / short-term refunds on the long / short-term refund management page.

[0110] For discrepancies in total amount or total amount, the difference amount needs to be recorded, the reconciliation record needs to be marked as abnormal, and then the data should be summarized and sent to the business operations system backend for further adjustment and processing by the system.

[0111] The processing of overpayment, underpayment, summary, and balance are all updated on the overpayment / underpayment management page. For details, you can view the overpayment / underpayment information for each transaction.

[0112] c. Three-level verification: rule engine plus manual review

[0113] For abnormal data with inconsistent amounts, after review by the rule engine in the secondary verification, manual review by the agent may be introduced if necessary. After the agent has completed the verification of all tickets, the difference in the marked overpayment / shortpayment amounts is netted to form the overpayment amount / shortpayment amount, and the reconciliation result is obtained.

[0114] The reconciliation results include, for example, fewer BOP platforms, more BOP platforms, balanced accounts, information differences, and amount differences. The reconciliation status of each transaction is updated to "reconciled".

[0115] Step 204: Automated settlement execution processing.

[0116] Once the reconciliation is successful, the fund transfer process will be automatically initiated according to the tiered settlement strategy.

[0117] a. Automatically generate adjustment orders.

[0118] During implementation, an adjustment order is automatically generated based on the reconciliation structure, which includes fields such as agent information, adjustment amount, and payment period, and a unique adjustment order number is automatically generated.

[0119] b. Issue fund settlement instructions.

[0120] Based on the DPC settlement amount in the reconciliation document, a transfer instruction is sent to the partner bank through an encrypted interface (using HTTPS + national cryptographic SM4 algorithm).

[0121] Based on the shortfall adjustment order, the agent will be sent a shortfall repayment adjustment statement, and the agent must complete the repayment within the specified time.

[0122] The system automatically completes the refund of overdue funds to the agent based on the instruction issued in the overdue adjustment order.

[0123] During implementation, a batch processing function is provided. Overpayments are automatically refunded to the agent's funds account, while underpayments are automatically generated and sent to the agent. The agent needs to complete the repayment operation according to the bill amount.

[0124] When the bank interface response times out (more than 30 seconds), it will automatically retries 3 times. If it still fails, it will trigger a manual intervention process.

[0125] Figure 3 This is another specific example diagram of the settlement and reconciliation method applicable to the distribution of airline tickets in this embodiment of the invention, as shown in the figure. Figure 3 As shown, the settlement process is illustrated, including: DPC data is loaded and parsed through AP2 (sales data summary sales file), and then verified in the BOP settlement system. The transaction data quantity, amount, status, agent, and airline data are compared with the AP2 file data to obtain the reconciliation results, and automatic settlement and payment processing is executed.

[0126] Step 205: Closed-loop feedback of reconciliation and settlement results.

[0127] Receive bank transfer result notification for settlement amount (synchronous interface + asynchronous callback double confirmation):

[0128] After the agent successfully repays the short-term loan, the system will automatically update the short-term loan status to "repaid".

[0129] After the long-term payment was refunded, the status of the long-term payment on the billing statement changed to "Long-term payment processed".

[0130] All settlement records are written to an immutable log to meet audit traceability requirements.

[0131] This invention provides two forms of periodic reconciliation: fully automatic daily reconciliation and fully automatic settlement period reconciliation.

[0132] (1) Fully automatic daily reconciliation.

[0133] In a BOP-based settlement and reconciliation system, the scientific and efficient nature of the reconciliation method is crucial for ensuring the smooth operation of the entire process. The reconciliation method uses SFTP (File Transfer Protocol) as the data receiving hub, and through systematic data processing and verification logic, it achieves accurate matching and anomaly handling of airline and agent sales data.

[0134] (2) Fully automated settlement period reconciliation

[0135] The fully automated settlement period reconciliation is another important innovation based on the BOP platform settlement reconciliation system. It strictly follows the IATA's settlement period rules and achieves efficient and accurate processing of period reconciliation with DPC through fully automated operation.

[0136] During the data acquisition phase, the system automatically downloads the DPC settlement period reconciliation file from the IATA SFTP server, based on the settlement period stipulated by IATA. This file contains crucial information, and the system performs a comprehensive and detailed comparison between the records in the reconciliation file and the data stored in the BOP data center. This process no longer relies on manual operation but automatically matches and verifies various pieces of information through a built-in intelligent comparison algorithm.

[0137] This invention automatically generates corresponding adjustment orders based on the resulting over / under balance data. The adjustment order details the relevant information of the discrepancies, the amounts of the over / under balance, and the reasons for the adjustment. Subsequently, the adjustment order is automatically pushed to the corresponding agent for confirmation. After the agent views the adjustment order and completes the confirmation process through the BOP platform, the adjustment is automatically executed based on the confirmation result, without requiring manual intervention in fund transfers or account modifications. This automated adjustment mechanism not only significantly shortens the adjustment cycle and avoids the delays and errors that may occur in traditional manual adjustments, but also fully ensures the accuracy and compliance of the adjustment process.

[0138] This invention utilizes SFTP data file interaction to automatically process BSP sales data from various airlines and agents, achieving unified reconciliation and settlement, and changing the situation of decentralized processing.

[0139] In terms of data exchange, relying on SFTP, BSP sales data from various airlines and agents are centralized on the BOP platform, avoiding data format differences and transmission barriers. During the reconciliation process, the platform processes all data according to a unified standard, ensuring standardization and consistency. In the clearing and settlement phase, the platform automatically completes fund clearing and settlement based on the reconciliation results, eliminating the need for separate communication with agents.

[0140] This method precisely addresses pain points in the BSP (Bill of Services) field: it integrates reconciliation processes across multiple airlines, avoiding multiple intermediaries for agents; it standardizes settlement processes; and it reduces manual operations, lowering the risk of errors. It provides the industry with a standardized, integrated technical solution, promoting more efficient and standardized reconciliation and settlement.

[0141] Furthermore, in one embodiment, the method further includes: full-process anomaly monitoring, displaying anomaly events; the anomaly events include payment failure and processing failure exceeding the time limit.

[0142] Real-time monitoring of any abnormal statuses in data collection, reconciliation, and settlement processes, displayed on a dashboard:

[0143] Abnormal events include basic anomalies, fund anomalies, and payment failures. Basic anomalies include: inconsistent IATA numbers (from II to I), inconsistent sales status, and inconsistent sales records (sales records in the reconciliation file are more / less than those in the BOP sales record). Fund anomalies include: inconsistencies between the settlement amount recorded in the reconciliation file and the payment amount on the BOP ticket. Payment failures include: insufficient balance in the agent's account or abnormal status of the agent's account (frozen, etc.).

[0144] Timeliness warnings (such as abnormal records that have not been processed within 24 hours);

[0145] It supports filtering, exporting, and batch processing of abnormal records (such as batch reconciliation and manual settlement triggering).

[0146] For anomalies that can be automatically repaired (such as payment data delays caused by network fluctuations), this embodiment of the invention periodically (every 10 minutes) retrieves data again and retryes.

[0147] For anomalies requiring manual handling (such as excessive amount discrepancies or invalid qualifications), the work order system is used to assign them to the corresponding responsible persons (airline finance / agent customer service) and set a processing time limit (automatic escalation reminders when the time limit is exceeded).

[0148] In one embodiment, the method further includes recording full-process log information.

[0149] All operations (data access, reconciliation results, settlement instructions, and exception handling) generate detailed logs, including information such as the operator, time, content, and IP address.

[0150] Offers multi-dimensional query functions: search by ticket number, adjustment order number, time range, exception type, etc., and supports log export and printing;

[0151] Logs are retained for at least 7 years to meet financial audit and industry regulatory requirements.

[0152] In this embodiment of the invention, after an agent successfully sells airline BOP tickets through the BOP platform, the reconciliation and settlement process is initiated in an orderly manner according to a predetermined logic. On the settlement date stipulated by IATA, reconciliation with DPC is initiated. Thanks to optimized program processing time, massive amounts of cross-border transaction data can be processed quickly, completing data comparison, discrepancy analysis, and confirmation in a short time, significantly reducing the cycle and saving time for subsequent fund settlement.

[0153] Once the reconciliation with DPC is completed and verified to be accurate, the system automatically triggers ticket payment settlement with IATA and adjustments for agent cash shortages. Due to improved interface decoupling, related modules can operate independently and efficiently, with no interference between interfaces. The process requires no manual intervention, ensuring accuracy and improving efficiency.

[0154] Based on the BOP platform, this invention leverages the technical advantages of interface standardization, optimized program processing time, and improved interface decoupling to construct a fully automated reconciliation and settlement system, significantly improving the efficiency, accuracy, and compliance of airline ticket sales and settlement.

[0155] This invention also provides a settlement and reconciliation system suitable for airline ticket distribution, comprising: a transaction processing server, a data storage array, and a ticketing data coordination center; the transaction processing server is used to implement the aforementioned settlement and reconciliation method suitable for airline ticket distribution, the data storage array is used to store real-time ticket sales data, and the ticketing data coordination center is used to aggregate all ticket sales data from airlines and various distribution platforms.

[0156] The system's hardware modules must meet the requirements of efficient data processing, accurate transaction record storage, secure information exchange, and stable operation. These modules work together to support the orderly progress of the entire reconciliation and settlement process. The core modules are described in detail below from a hardware perspective.

[0157] (1) Core processing module - transaction processing server: the computing center for reconciliation and settlement.

[0158] The transaction processing server is the core of the BOP platform's reconciliation and settlement logic. It is responsible for processing ticket sales data, executing reconciliation algorithms, and triggering settlement instructions. It needs to have high computing efficiency and multi-tasking capabilities.

[0159] (2) Storage module: a reliable carrier of transaction data.

[0160] The storage module needs to implement hierarchical storage of data such as sales records, reconciliation results, and settlement vouchers, while balancing real-time access speed and long-term archiving security.

[0161] (3) Input / output module: a bridge node for information interaction.

[0162] The input module is responsible for collecting raw data from sales terminals and payment channels, while the output module implements functions such as settlement result push and voucher printing to ensure the integrity of data interaction.

[0163] (4) Power supply module: the cornerstone of system stability.

[0164] The power module needs to provide continuous and stable power support for all hardware components, especially for critical processes such as reconciliation and settlement, and must have redundancy backup and abnormal power failure protection capabilities.

[0165] (5) Communication module: Transmission channel for cross-node data.

[0166] The communication module needs to enable cross-network data interaction between the BOP platform and airline databases, agent terminals, and bank payment systems, while balancing transmission speed and information security.

[0167] (6) Security authentication module: a protective barrier for transaction compliance.

[0168] Given the high security requirements of airline financial management, hardware-level authentication modules are needed to prevent data tampering and unauthorized access.

[0169] (7) Example of collaborative process.

[0170] After the agent completes the ticket sale through the BOP platform:

[0171] The input module collects sales data (ticket number, amount, payment channel) and transmits it to the transaction processing server via the communication module in an encrypted manner.

[0172] The transaction processing server calls the CPU to read the airline's original ticket information from the storage module and executes the reconciliation algorithm (comparing the amount, passenger information, and payment status).

[0173] If the accounts match, a settlement instruction is generated, encrypted by the security authentication module, and sent to the bank system via the communication module.

[0174] The entire data processing is ensured by a stable power supply module, which triggers an emergency mechanism in case of an anomaly to ensure uninterrupted operation. Through the collaboration of the aforementioned hardware modules, the system can achieve a reconciliation processing capacity of ≥500 transactions per second, with a settlement accuracy rate of 100%, providing reliable hardware support for the entire process of airline ticket sales fund management.

[0175] The system underwent targeted preparation before implementation: This included: assessing the scale of data interaction among cross-border airlines, agents, DPCs, and international travel information providers involved in the BOP platform; clarifying the average daily transaction data volume, peak processing demands (such as data surges on settlement days), and latency thresholds for cross-border data transmission; surveying data center infrastructure in multiple regions, focusing on evaluating network link stability and verifying whether the hardware meets compliance standards for encrypted cross-border data transmission; and designing high-performance computing and storage clusters, cross-border network and security hardware architecture, interface hardware coordination, system integration testing, and cross-border scenario verification.

[0176] (1) High-performance computing and storage clusters.

[0177] Transaction processing servers: Employing a distributed server cluster architecture, nodes are configured with multi-core processors (e.g., 40 cores or more) and large-capacity DDR4 memory (starting from 256GB) to meet the demands of parallel comparison of massive amounts of data during DPC reconciliation. A load balancer dynamically distributes tasks across nodes to prevent single-node overload.

[0178] Data storage array: A multi-protocol Storage Area Network (SAN) is selected, equipped with a hybrid storage architecture of high-speed SSDs and large-capacity HDDs. SSDs are used to store real-time reconciliation data, while HDDs are used to archive historical settlement data. Storage-level encryption is also enabled to ensure the security of data during cross-border transmissions at the storage stage.

[0179] SFTP Dedicated Server: The ticketing data coordination center deploys an independent SFTP server cluster equipped with a dedicated encryption chip to enhance the encryption processing capabilities of data file transfers with airlines and agents, and to cope with scenarios where multiple entities upload sales data simultaneously.

[0180] (2) Cross-border network and security hardware architecture.

[0181] International leased lines and redundant links: Deploy multiple international leased lines to connect to overseas nodes (IATA servers), and with intelligent routing switching equipment, automatically switch to the backup link within 10 seconds when the main link fails, ensuring uninterrupted data transmission for reconciliation during the guarantee period.

[0182] A comprehensive security protection system: Deploy a next-generation firewall (NGFW) at the network boundary, enable application layer detection, and accurately identify abnormal traffic in cross-border data exchanges; configure intrusion prevention system (IPS) and data loss prevention (DLP) hardware devices; and for inter-module communication after interface decoupling, perform micro-segmentation through the internal firewall to restrict access permissions between modules.

[0183] (3) Co-design of interface hardware.

[0184] Data Interaction Gateway: Deploy a hardware gateway that supports multi-protocol conversion (such as supporting SNA and TCP / IP protocol adaptation) to solve the interface compatibility issues between the BOP platform and other systems. The gateway needs to have a built-in hardware encryption engine to reduce encryption latency during the data conversion process.

[0185] (4) System integration and cross-border scenario verification.

[0186] End-to-end stress testing: Simulate peak scenarios on settlement days, test the CPU load, memory usage, and storage IOPS (input / output operations per second) of the server cluster, test the automatic switching capability when the international link is interrupted, and verify whether the backup link can seamlessly take over the data transmission task.

[0187] This invention also provides a settlement and reconciliation device suitable for airline ticket distribution, as described in the following embodiments. Since the principle by which this device solves the problem is similar to the settlement and reconciliation method suitable for airline ticket distribution, the implementation of this device can refer to the implementation of the settlement and reconciliation method suitable for airline ticket distribution; repeated details will not be elaborated further.

[0188] Figure 4 This is a schematic diagram of a settlement and reconciliation device applicable to the distribution of airline tickets in an embodiment of the present invention, as shown below. Figure 4 As shown, the device 400 includes:

[0189] The multi-source data access module 401 is used to obtain the agent's ticket sales data based on the BOP platform; and to obtain reconciliation files from the ticketing data coordination center; the ticketing data coordination center is used to aggregate the full ticket sales data of airlines and various distribution platforms;

[0190] The intelligent reconciliation processing module 402 is used to compare the ticket sales data with the reconciliation file and generate an adjustment order based on the comparison results; the comparison results include discrepancy ticket information; the adjustment order includes the agent's payable amount and receivable amount corresponding to the discrepancy ticket information;

[0191] Adjustment module 403 is used to push the adjustment order to the agent.

[0192] In one embodiment, the device 400 further includes a preprocessing module for:

[0193] Before the intelligent reconciliation processing module 402 compares the ticket sales data with the reconciliation file, it preprocesses the ticket sales data and the reconciliation file to obtain preprocessed ticket sales data and reconciliation file; the preprocessing includes format unification, abnormal field repair, and fingerprinting.

[0194] The intelligent reconciliation processing module 402 is specifically used for:

[0195] The pre-processed ticket sales data is compared with the reconciliation documents.

[0196] In one embodiment, the comparison result includes length and width information;

[0197] The intelligent reconciliation processing module 402 is specifically used for:

[0198] Based on the reconciliation file, the ticket sales data is subjected to a first-level verification. Ticket sales data that fails the first-level verification is marked as abnormal. The first-level verification means comparing the ticket sales data with the specified core fields of the reconciliation file using the ticket number as an index.

[0199] A second-level verification is performed on the ticket sales data that passed the first-level verification and the reconciliation file. The second-level verification means: using the ticket number as an index, generating over / under payment information based on the amount difference; the over / under payment information includes payment record differences and amount differences.

[0200] Once the length and quantity information is approved, an adjustment order will be generated.

[0201] In one embodiment, the device 400 further includes a settlement processing module for:

[0202] After the adjustment module 403 pushes the adjustment order to the agent, it receives the agent's confirmation of the adjustment order or modification suggestions.

[0203] Modify the adjustment order according to the modification suggestions, push the modified adjustment order to the agent, and receive the agent's confirmation of the adjustment order;

[0204] Based on the agent's confirmation of the adjustment order, the funds are transferred to the airline's or agent's account; the airline's or agent's account has pre-deposited funds.

[0205] In one embodiment, the intelligent reconciliation processing module 402 is specifically used for:

[0206] Regularly compare ticket sales data with reconciliation documents and generate adjustment orders based on the comparison results; the regularity includes daily and set settlement cycles.

[0207] In one embodiment, the multi-source data access module 401 is specifically used for:

[0208] A secure file transfer service based on the SSH protocol retrieves reconciliation files from the ticketing data coordination center.

[0209] In one embodiment, the ticket sales data includes one or any combination of the following:

[0210] Ticket number, airline logo, agent logo, sales date, ticket price, and payment method.

[0211] In one embodiment, the device 400 further includes a risk monitoring module for: full-process anomaly monitoring and displaying abnormal events; the abnormal events include payment failure and processing failure exceeding the time limit.

[0212] In one embodiment, the device 400 further includes a log tracing module for recording full-process log information.

[0213] Figure 5 This is a schematic diagram of a computer device in an embodiment of the present invention, such as... Figure 5 As shown, this embodiment of the invention also provides a computer device 500, including a processor 501, a memory 502, and a computer program 503 stored in the memory 502 and executable on the processor 501. When the processor 501 executes the computer program 503, it implements the above-described settlement and reconciliation method applicable to the distribution of airline tickets.

[0214] This invention also provides a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the aforementioned settlement and reconciliation program product applicable to airline ticket distribution.

[0215] The unified reconciliation and settlement method for civil aviation BSP ticket distribution based on the BOP platform proposed in this invention embodiment has the following significant advantages compared with the traditional decentralized settlement model:

[0216] (1) Settlement efficiency has been greatly improved.

[0217] The BOP platform's unified reconciliation and settlement methods enable ultra-fast settlement, and airlines can customize the settlement frequency, greatly improving capital turnover efficiency.

[0218] (2) Standardization and integration.

[0219] This avoids the cumbersome process of agents having to deal with different airlines separately in the traditional model, and achieves standardized management of ticket reconciliation and settlement, reducing connection problems caused by differences in airline systems.

[0220] (3) Automation and efficiency.

[0221] By using SFTP to automatically receive and summarize sales and settlement data, the workload of manual data entry and verification is reduced, significantly improving reconciliation efficiency and reducing the risk of errors caused by manual intervention.

[0222] (4) Improved settlement accuracy.

[0223] Centralized data comparison can promptly identify discrepancies between sales data and settlement amounts, reducing issues such as missed orders and incorrect accounts, improving the accuracy of financial settlements, and avoiding the financial management risks caused by decentralized reconciliation in the traditional model. This standardized and refined process can effectively avoid errors caused by manual operation, providing reliable financial data support for airlines and agents.

[0224] (5) Optimize fund clearing efficiency.

[0225] After the settlement data is automatically matched, the system can directly trigger the payment process, shorten the settlement cycle, speed up the return of funds, and improve the efficiency of fund transfer between airlines and agents.

[0226] (6) Adapt to industry needs and reduce operating costs.

[0227] Designed to address pain points in the BSP distribution sector, this system reduces the cost for agents to maintain multiple settlement systems, while also lowering the settlement management burden on airlines and promoting the standardization and intelligentization of industry settlement processes.

[0228] Compared to existing technologies, the BOP platform-based system of this invention possesses three core barriers: "deep scenario adaptation + full-link collaboration + dynamic evolution."

[0229] In terms of scenario adaptation, by pre-setting the airline ticketing industry rule base (such as cabin pricing, refund and change difference rules, etc.), the entire process from sales data collection to fund transfer is automated without manual intervention.

[0230] At the collaboration level, leveraging the BOP platform's industry hub status, data interfaces between airlines, agents, payment institutions, and regulatory authorities are connected to form a closed-loop ecosystem and avoid data silos.

[0231] At the evolutionary level, modular architecture supports dynamic rule updates and responds faster than alternatives.

[0232] In the context of full-process fund management for airline ticket sales, the overall performance of the solution in this embodiment of the invention is currently unmatched by any other solution.

[0233] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. 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. Furthermore, the present invention can take the form of a computer program product embodied 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.

[0234] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0235] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0236] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0237] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A settlement and reconciliation method applicable to airline ticket distribution, characterized in that, include: Obtain ticket sales data from agents based on the BOP platform; Obtain reconciliation documents from the ticketing data coordination center; The ticketing data coordination center is used to aggregate all ticket sales data from airlines and various distribution platforms; The airline ticket sales data is compared with the reconciliation documents, and an adjustment order is generated based on the comparison results. The comparison results include discrepancy ticket information. The adjustment order includes the agent's payable amount and receivable amount corresponding to the discrepancy ticket information. The adjustment order will be sent to the agent.

2. The method as described in claim 1, characterized in that, Before comparing ticket sales data with reconciliation documents, the process also includes: The ticket sales data and reconciliation files are preprocessed separately to obtain preprocessed ticket sales data and reconciliation files; the preprocessing includes format standardization, abnormal field repair, and fingerprinting. Compare the ticket sales data with the reconciliation documents, including: The pre-processed ticket sales data is compared with the reconciliation documents.

3. The method as described in claim 1, characterized in that, The comparison results include length and width information; Compare the ticket sales data with the reconciliation documents, including: Based on the reconciliation file, the ticket sales data is subjected to a first-level verification. Ticket sales data that fails the first-level verification is marked as abnormal. The first-level verification means comparing the ticket sales data with the specified core fields of the reconciliation file using the ticket number as an index. A second-level verification is performed on the ticket sales data that passed the first-level verification and the reconciliation file. The second-level verification means: using the ticket number as an index, generating over / under payment information based on the amount difference; the over / under payment information includes payment record differences and amount differences. An adjustment order is generated based on the comparison results, including: Once the length and quantity information is approved, an adjustment order will be generated.

4. The method as described in claim 1, characterized in that, After the adjustment order is sent to the agent, it also includes: Receive confirmation or modification suggestions from the agent regarding the adjustment order; Modify the adjustment order according to the modification suggestions, push the modified adjustment order to the agent, and receive the agent's confirmation of the adjustment order; Based on the agent's confirmation of the adjustment order, the funds are transferred to the airline's or agent's account; the airline's or agent's account has pre-deposited funds.

5. The method as described in claim 1, characterized in that, Compare ticket sales data with reconciliation documents, and generate adjustment orders based on the comparison results, including: Regularly compare ticket sales data with reconciliation documents and generate adjustment orders based on the comparison results; the regularity includes daily and set settlement cycles.

6. The method as described in claim 1, characterized in that, Obtain reconciliation documents from the ticketing data coordination center, including: A secure file transfer service based on the SSH protocol retrieves reconciliation files from the ticketing data coordination center.

7. The method as described in claim 1, characterized in that, The ticket sales data includes one or any combination of the following: Ticket number, airline logo, agent logo, sales date, ticket price, and payment method.

8. The method according to any one of claims 1 to 7, characterized in that, Also includes: Full-process anomaly monitoring displays abnormal events; these abnormal events include payment failures and processing failures exceeding the time limit.

9. The method according to any one of claims 1 to 7, characterized in that, Also includes: Record all process log information.

10. A settlement and reconciliation device suitable for distributing airline tickets, characterized in that, include: The multi-source data access module is used to obtain ticket sales data from agents based on the BOP platform and to obtain reconciliation files from the ticketing data coordination center. The ticketing data coordination center is used to aggregate all ticket sales data from airlines and various distribution platforms; The intelligent reconciliation processing module is used to compare ticket sales data with reconciliation files and generate adjustment orders based on the comparison results; the comparison results include discrepancy ticket information; the adjustment order includes the agent's payable amount and receivable amount corresponding to the discrepancy ticket information; The adjustment module is used to push adjustment orders to agents.

11. A settlement and reconciliation system suitable for airline ticket distribution, characterized in that, include: The system comprises a transaction processing server, a data storage array, and a ticketing data coordination center; the transaction processing server is used to implement the method described in any one of claims 1 to 9, the data storage array is used to store real-time ticket sales data, and the ticketing data coordination center is used to aggregate all ticket sales data from airlines and various distribution platforms.

12. 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, it implements the method of any one of claims 1 to 9.

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

14. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 9.

Images