A processing method for large customer's freight rate of civil aviation open passenger reservation system agent

Abstract

This application relates to a method and apparatus for processing fare requests from large clients of civil aviation open passenger reservation systems. The method includes: verifying the fare request submitted by the agent using both the large client code and the passenger type code; reading the verification switch table and verification capability table to confirm the airline group code and whether it supports large client fare codes; extracting the passenger name record number to obtain the order details message; verifying the fare item in the order details message; verifying whether the order details message contains the fare Q identifier and constructing a list of flight segments to be sent; constructing a request message to be sent; performing large client verification on the request message and constructing relevant remarks and service items for successfully verified request messages; setting corresponding return message parameters for different processing types and returning a return message. This method can improve the targeting and effectiveness of system services, achieve efficient processing of agent large client fare requests, and improve processing efficiency and accuracy.

Description

Technical Field

[0001] This application belongs to the field of data processing technology, and specifically relates to a method, apparatus, computer-readable storage medium, and electronic device for processing the fare of large clients of agents in a civil aviation open passenger reservation system. Background Technology

[0002] The Unified Order (Customer Travel Record, CTR) based on open platform storage technology is the core data of the Civil Aviation Open Passenger Reservation System, recording data throughout the entire passenger travel process from booking and sales to passenger service and travel delivery. The Civil Aviation Open Passenger Reservation System is responsible for synchronizing and managing CTR order data. Based on CTR order data, it realizes the reservation transaction process, provides airline and agent clients with reservations for flights and ancillary service products, and offers differentiated reservation services based on passenger value. It supports the reservation and retail needs of airlines and agents and tracks changes in passenger reservation status.

[0003] When the agent booking front-end system sends an agent fare request to the civil aviation open passenger booking system, the civil aviation open passenger booking system receives and processes the agent fare request and returns the processing result to the civil aviation agent booking front-end system.

[0004] In particular, when the civil aviation open passenger reservation system processes agent fare requests that include bulk customer fares, the reservation system needs to handle these requests specially. However, the current civil aviation open passenger reservation system does not have a corresponding design for this requirement, which leads to many inconveniences in processing agent fare requests that include bulk customer fares. Therefore, a new solution is needed to solve the problem of inconvenience in the current civil aviation open passenger reservation system when agent fare requests include bulk customer fares. Summary of the Invention

[0005] To address the aforementioned issues, this application proposes a new method and apparatus for processing fare rates for large clients of agents in a civil aviation open passenger reservation system.

[0006] This application aims to address the inconvenience caused by the current civil aviation open passenger reservation system's inability to differentiate between fare requests from large customers, resulting in difficulties in receiving and processing agent fare requests that include large customer fares. The proposed method, through modular design, enables the civil aviation open passenger reservation system to provide corresponding and effective processing methods for both regular customer fares and large customer fares when handling agent fare requests containing large customer fares. This improves the system's service targeting and effectiveness, achieves efficient processing of agent large customer fare requests, enhances processing efficiency and accuracy, and reduces the number of problem tickets required from system users.

[0007] To achieve the above objectives, this application provides the following technical solution:

[0008] The first aspect of this application provides a method for processing fare rates for large clients of agents in a civil aviation open passenger reservation system, including:

[0009] Receive the freight rate request submitted by the agent, extract the value of the major customer code field from the agent's freight rate request, and perform major customer code verification;

[0010] Extract the value of the passenger type code field from the agent's fare request and perform passenger type code verification;

[0011] Read the verification switch table and verification capability table to determine whether further verification of the major customer code is required, and confirm the airline group code and whether the major customer code fare is supported;

[0012] Extract the passenger name record number from the agent's fare request, send the number to the order details query interface, and obtain the order details message returned by the interface;

[0013] Perform freight rate verification on the order details message;

[0014] Verify whether the order details message contains the fare Q identifier, and construct a list of flight segments to be sent based on the verification result;

[0015] Construct a request message to be sent based on the list of flight segments to be sent;

[0016] Send the request message to the customer management system for large customer verification, and construct relevant remarks and service items for the request message that has been successfully verified.

[0017] Set the corresponding reward message parameters for different processing types and return the reward message.

[0018] Optionally, in the method of this application, the step of performing large customer code verification includes:

[0019] If the large customer code field in the agent's freight rate request is empty, the response result will be returned indicating that the large customer code is empty, and no further processing will be performed;

[0020] If the value of the large customer code field in the agent's freight rate request is not compliant, the response result will be returned indicating that the large customer code is not compliant, and no further processing will be performed;

[0021] If the Large Customer Code field in the agent's freight rate request is GP, then the process will proceed to the GP type reward processing module.

[0022] Optionally, in the method of this application, the passenger type code verification includes: if the passenger type code field in the agent fare request is INF, then proceed to the NOCHECK type report processing module;

[0023] Read the verification switch table and verification capability table. If it is determined that no further verification of the major customer code is required or the confirmed airline group code does not support the major customer code fare, then proceed to the NOCHECK type report processing module.

[0024] Optionally, in the method of this application, the step of verifying the freight rate item in the order details message includes: looping through the FareBoxes node under the Passengers node in the order details message; if the FareBoxes node is not empty, returning a response result and prompting that the net freight rate content needs to be deleted.

[0025] The verification of whether the order details message contains the fare Q identifier includes: looping through the Segment nodes under the Passengers node in the order details message; if the Segment node is empty, return a response indicating no flight segment; if the Segment node is not empty, extract the content of each Segment node under that node; if the content of the Segment node contains the fare Q identifier, add the Segment node to the list of flight segments to be sent; if the content of all Segment nodes does not contain the fare Q identifier, add all Segment nodes to the list of flight segments to be sent.

[0026] The step of constructing a request message to be sent based on the list of flight segments to be sent includes: looping through the list of flight segments to be sent; if the list of flight segments to be sent is empty, then entering the NOCHECK type report processing module; if the list of flight segments to be sent is not empty, then looping to extract the content of each Segment node under the list and adding it to the request message to be sent.

[0027] Optionally, in the method of this application, the step of sending the request message to the customer management system for large customer verification includes: sending the request message to the customer management system; if no response is received within the timeout period, returning a response result indicating timeout; if the received response contains an identifier indicating that the verification failed, returning a response result indicating that the verification failed; if the received response contains an identifier indicating that the verification succeeded, constructing relevant remarks and service items for the request message, and then entering the OK type response processing module;

[0028] The remarks items include ACC remarks items and FARECODE remarks items, and the service items include CKIN VICO service items; wherein:

[0029] Add the airline's two-letter code, major customer code, amount of credit used this time, amount of credit remaining, and passenger identifier for the credit used to the ACC remarks section.

[0030] Add the following information to the FARECODE remarks section: Customer Code, Airline Code, Flight Number, Departure and Arrival Cities, Flight Segment Dates, and Price;

[0031] Add the airline's two-letter code, action code, number of seats, and corporate customer code to the CKIN VICO service item.

[0032] Optionally, in the method of this application, setting corresponding reward message parameters for different processing types includes:

[0033] For OK processing types, the relevant remarks and service items are placed in the report message, and then the government flag is set to 0, the keyAccount flag is set to 1, and the vipAccount flag is set to 1 in the report message;

[0034] For GP processing types, set the government flag to 1, the keyAccount flag to 0, and the vipAccount flag to 0 in the response message;

[0035] For the NOCHECK processing type, the government flag, keyAccount flag, and vipAccount flag are set to 0 in the response message.

[0036] A second aspect of this application provides a processing apparatus for fare rates for large clients of an agent in a civil aviation open passenger reservation system, the apparatus comprising:

[0037] Large Customer Code Verification Module: Used to extract the value of the large customer code field from the agent's freight rate request and determine the value type;

[0038] Passenger type check module: used to extract the value of the passenger type code field in the agent's fare request and determine the type of the value;

[0039] Verification switch and capability check module: used to read the verification switch table and verification capability table, determine whether further verification of the major customer code is required, and confirm the airline group code and whether the major customer code fare is supported;

[0040] Order details retrieval module: used to extract the passenger name record number from the agent's fare request and obtain the order details message through the order details query interface;

[0041] Freight Rate Validation Module: Used to validate the freight rate item in the order details message;

[0042] Segment Group Q Label Verification Module: Used to verify whether the order details message contains the fare Q label, and to construct a list of segments to be sent based on the verification results;

[0043] The pending flight segment verification and construction module is used to construct a pending request message based on the pending flight segment list.

[0044] Large Customer Verification and Construction Module: Used to send request messages to the customer management system for large customer verification, and to construct relevant remarks and service items for successfully verified request messages;

[0045] The feedback processing module is used to set the corresponding feedback message parameters for different processing types and return feedback messages.

[0046] When the device is in operation, it implements the steps of the aforementioned method for processing fare rates for large clients of the civil aviation open passenger reservation system.

[0047] Optionally, in the device of this application, the remarks include ACC remarks and FARECODE remarks, and the service items include CKIN VICO service items.

[0048] A third aspect of this application provides an electronic device, including: a memory and a processor;

[0049] Memory: Used to store computer programs;

[0050] Processor: Used to execute the computer program to implement the steps of the aforementioned method for processing fare rates for large clients of the civil aviation open passenger reservation system.

[0051] A fourth aspect of this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the aforementioned method for processing fare rates for large clients of an agent in a civil aviation open passenger reservation system.

[0052] In summary, this application proposes a novel method for processing fare requests from large clients of civil aviation open passenger reservation systems. This method addresses the inconvenience currently present in receiving and processing fare requests from agents that include large client fares. Through modular design, this method enables the civil aviation open passenger reservation system to provide corresponding and effective processing methods for both regular customer fares and large client fares when handling agent fare requests containing large client fares. This improves the targeting and effectiveness of system services, achieves efficient processing of agent large client fare requests, enhances processing efficiency and accuracy, and reduces the number of problem tickets required from system users.

[0053] Other features and advantages of this application will be set forth in the following description and will be apparent in part from the description or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the techniques pointed out in the description, claims and drawings. Attached Figure Description

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

[0055] Figure 1 This is a structural diagram of a device for processing fare rates for large clients of an open passenger reservation system for civil aviation, provided in one embodiment of this application.

[0056] Figure 2 This is a schematic diagram of the operational architecture of a method for processing fare rates for large clients of an agent in a civil aviation open passenger reservation system, provided in one embodiment of this application.

[0057] Figure 3 This is an overall implementation flowchart of a method for processing fare rates for large clients of an agent in a civil aviation open passenger reservation system, as provided in one embodiment of this application.

[0058] Figure 4 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this application. Detailed Implementation

[0059] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0060] The term “comprising” and its variations as used herein are open-ended inclusions, meaning “including but not limited to”; the term “based on” means “at least partially based on”; and the term “one embodiment” means “at least one embodiment”.

[0061] It should be noted that the terms "a" and "a plurality of" used in this application are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0062] Figure 1The diagram shows the structural composition of a processing device for large customer fares in a civil aviation open passenger reservation system provided in this application. The device includes:

[0063] Large Customer Code Verification Module: Used to extract the value of the large customer code field from the agent's freight rate request and determine the value type;

[0064] Passenger type check module: used to extract the value of the passenger type code field in the agent's fare request and determine the type of the value;

[0065] Verification switch and capability check module: used to read the SK table (verification switch table) and WS table (verification capability table), determine whether further verification of the major customer code is required, and confirm the airline group code and whether it supports the major customer code fare.

[0066] Order details retrieval module: used to extract the passenger name record number from the agent's fare request and obtain the order details message through the order details query interface;

[0067] Freight Rate Validation Module: Used to validate the freight rate item in the order details message;

[0068] Segment group Q identifier verification module: used to verify whether the Segment node in the order details message contains the fare Q identifier (surcharge identifier), and add the Segment node containing the fare Q identifier to the list of segments to be sent;

[0069] The segment verification and construction module is used to extract the content of the Segment node under the segment list to be sent and add it to the request message to be sent.

[0070] Large Customer Verification and Construction Module: This module sends request messages to the customer management system for large customer verification and constructs ACC (Large Customer Code) remarks, FARECODE (Price Code) remarks, and CKIN VICO (Large Customer Code) service items for successfully verified request messages.

[0071] The feedback processing module is used to set the corresponding feedback message parameters for different processing types and return feedback messages.

[0072] When the above-mentioned device is in operation, it implements the steps of the method for processing the fare of large customers of the civil aviation open passenger reservation system disclosed in this application.

[0073] Figure 2 The diagram shows the operational architecture of a method for processing fare rates for large clients of an agent in a civil aviation open passenger reservation system, as proposed in this application. Figure 3 The diagram shows the overall implementation flow of this method, which includes the following steps:

[0074] Step 1: Enter the Large Customer Code Verification Module, receive the freight rate request submitted by the agent, extract the value of the Large Customer Code field from the agent's freight rate request. If the value is empty, return a response result indicating that the Large Customer Code is empty and do not proceed with further processing; if the value is non-compliant, return a response result indicating that the Large Customer Code is non-compliant and do not proceed with further processing; if the Large Customer Code is GP (Important Purchase), then enter the GP type report processing module.

[0075] Step 2: Enter the passenger type check module to verify the passenger type code in the agent's fare request, extract the value of the passenger type code field in the request, and if the value is INF (infant), then enter the NOCHECK (no verification required) type of report processing module to simplify the processing flow.

[0076] Step 3: Enter the verification switch and capability check module, read the SK table (verification switch table), and obtain the value of whether to verify the large customer code. If the value is 0, enter the NOCHECK type report processing module; if the value is 1, read the WS table (verification capability table), obtain the airline group code and the value of whether to support the large customer code fare. If the value is 0, enter the NOCHECK type report processing module.

[0077] Step 4: After confirming that large customer fare verification is required, proceed to the order details acquisition module, extract the passenger name record number from the agent fare request, send the number to the order details query interface, and obtain the order details message returned by the interface.

[0078] Step 5: Enter the fare item verification module, and iterate through the FareBoxes node under the Passengers node in the order details message. If the FareBoxes node is not empty, it means that there is an additional fare item. Then return the response result and prompt that the FN (Fare Net Value) content needs to be deleted.

[0079] Step 6: Enter the segment group Q mark verification module, and iterate through the Segment nodes under the Passengers node in the order details message. If the Segment node is empty, return the response result, indicating that there is no segment; if the Segment node is not empty, extract the content of each Segment node under that node. If the content of the Segment node contains the fare Q mark, add the Segment node to the list of segments to be sent; if the content of all Segment nodes does not contain the fare Q mark, add all Segment nodes to the list of segments to be sent.

[0080] Step 7: Enter the segment verification and construction module, and iterate through the content of each segment node in the segment list to be sent. If the segment list to be sent is empty, enter the NOCHECK type report processing module; if the segment list to be sent is not empty, extract the content of each segment node under the list and add it to the request message to be sent.

[0081] Step 8: Enter the large customer verification and construction module, send the request message to the customer management system. If no response is received within the timeout period, return a response result indicating timeout. If the received response contains an identifier indicating that the verification failed, return a response result indicating that the verification failed. If the received response contains an identifier indicating that the verification succeeded, construct the ACC memo item, FARECODE memo item, and CKIN VICO service item respectively. Add the airline two-letter code, large customer code, amount of credit used this time, amount of remaining credit, and passenger identifier of the credit used to the ACC memo item. Add the large customer code, airline two-letter code, flight number, departure and arrival cities, flight segment date, and price to the FARECODE memo item. Add the airline two-letter code of the ticketing airline, action code, number of seats, and large customer code to the CKIN VICO service item. Enter the OK (verification successful) type response processing module.

[0082] Step 9: Based on the processing type (OK, GP, or NOCHECK), proceed to the appropriate response processing module. If it is an OK response, include the ACC memo, FARECODE memo, and CKIN VICO service items constructed in the previous steps into the response message. Then, set the government flag to 0, the keyAccount flag to 1, and the vipAccount flag to 1 in the response message and return the response message. If it is a GP response, set the government flag to 1, the keyAccount flag to 0, and the vipAccount flag to 0 in the response message and return the response message. If it is a NOCHECK response, set the government flag to 0, the keyAccount flag to 0, and the vipAccount flag to 0 in the response message and return the response message.

[0083] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0084] like Figure 4 As shown in the illustration, an embodiment of this application also discloses an electronic device, including: a processor 310, a communication interface 320, a memory 330 for storing a processor-executable computer program, and a communication bus 340. The processor 310, communication interface 320, and memory 330 communicate with each other via the communication bus 340. The processor 310 executes the executable computer program to implement the steps of the above-described method for processing fare rates for large clients of an agent in a civil aviation open passenger reservation system.

[0085] It is understandable that, in addition to memory and a processor, this electronic device may also include input devices such as a keyboard, output devices such as a display, and other communication modules. The input devices, output devices, and other communication modules communicate with the processor through I / O interfaces (i.e., input / output interfaces).

[0086] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof. These programming languages ​​include, but are not limited to, object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0087] Furthermore, this application also discloses a computer-readable storage medium, wherein when the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is able to perform the various steps of the processing method for agent large customer fares of the civil aviation open passenger reservation system disclosed in this application.

[0088] In the context of this application, a computer-readable storage medium can be a tangible medium, and more specific examples include portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0089] Specifically, according to embodiments of this application, the processes described in the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for executing the processing method for large customer fare information of the civil aviation open passenger reservation system disclosed in this application. When the computer program is executed by a processing device, it performs the functions defined in the methods of the embodiments of this application.

[0090] While the foregoing discussion includes several specific implementation details, these should not be construed as limiting the scope of this application. The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept.

[0091] Those skilled in the art should also understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for processing fare rates for large clients of agents in a civil aviation open passenger reservation system, characterized in that, The method includes: Receive the freight rate request submitted by the agent, extract the value of the major customer code field from the agent's freight rate request, and perform major customer code verification; Extract the value of the passenger type code field from the agent's fare request and perform passenger type code verification; Read the verification switch table and verification capability table to determine whether further verification of the major customer code is required, and confirm the airline group code and whether the major customer code fare is supported; Extract the passenger name record number from the agent's fare request, send the number to the order details query interface, and obtain the order details message returned by the interface; Perform freight rate verification on the order details message; Verify whether the order details message contains the fare Q identifier, and construct a list of flight segments to be sent based on the verification result; Construct a request message to be sent based on the list of flight segments to be sent; Send the request message to the customer management system for large customer verification, and construct relevant remarks and service items for the request message that has been successfully verified. Set the corresponding reward message parameters for different processing types and return the reward message; The large customer code verification includes: If the large customer code field in the agent's freight rate request is empty, the response result will be returned indicating that the large customer code is empty, and no further processing will be performed; If the value of the large customer code field in the agent's freight rate request is not compliant, the response result will be returned indicating that the large customer code is not compliant, and no further processing will be performed; If the Large Customer Code field in the agent's freight rate request is GP, then the process will proceed to the GP type reward processing module. The passenger type code verification includes: if the passenger type code field in the agent's fare request is INF, then proceed to the NOCHECK type report processing module; Read the verification switch table and verification capability table. If it is determined that no further verification of the major customer code is required or the confirmed airline group code does not support the major customer code fare, then proceed to the NOCHECK type report processing module. The step of sending the request message to the customer management system for large customer verification includes: sending the request message to the customer management system; if no response is received within the timeout period, returning a response result indicating timeout; if the received response contains an identifier indicating that the verification failed, returning a response result indicating that the verification failed; if the received response contains an identifier indicating that the verification succeeded, constructing relevant remarks and service items for the request message, and then entering the OK type response processing module. The remarks items include ACC remarks items and FARECODE remarks items, and the service items include CKIN VICO service items; wherein: Add the airline's two-letter code, major customer code, amount of credit used this time, amount of credit remaining, and passenger identifier for the credit used to the ACC remarks section. Add the following information to the FARECODE remarks section: Customer Code, Airline Code, Flight Number, Departure and Arrival Cities, Flight Segment Dates, and Price; Add the airline's two-letter code, movement code, number of seats, and corporate customer code to the CKIN VICO service item; The setting of corresponding reward message parameters for different processing types includes: For OK processing types, the relevant remarks and service items are placed in the report message, and then the government flag is set to 0, the keyAccount flag is set to 1, and the vipAccount flag is set to 1 in the report message; For GP processing types, set the government flag to 1, the keyAccount flag to 0, and the vipAccount flag to 0 in the response message; For the NOCHECK processing type, the government flag, keyAccount flag, and vipAccount flag are set to 0 in the response message.

2. The method according to claim 1, characterized in that, The procedure for verifying the freight rate item in the order details message includes: looping through the FareBoxes node under the Passengers node in the order details message; if the FareBoxes node is not empty, returning a response result and prompting that the net freight rate content needs to be deleted. The verification of whether the order details message contains the fare Q identifier includes: looping through the Segment nodes under the Passengers node in the order details message; if the Segment node is empty, return a response indicating no flight segment; if the Segment node is not empty, extract the content of each Segment node under that node; if the content of the Segment node contains the fare Q identifier, add the Segment node to the list of flight segments to be sent; if the content of all Segment nodes does not contain the fare Q identifier, add all Segment nodes to the list of flight segments to be sent. The step of constructing a request message to be sent based on the list of flight segments to be sent includes: looping through the list of flight segments to be sent; if the list of flight segments to be sent is empty, then entering the NOCHECK type report processing module; if the list of flight segments to be sent is not empty, then looping to extract the content of each Segment node under the list and adding it to the request message to be sent.

3. A device for processing fare rates for large clients of agents in a civil aviation open passenger reservation system, characterized in that, The device includes: Large Customer Code Verification Module: Used to extract the value of the large customer code field from the agent's freight rate request and determine the value type; it includes: If the Large Customer Code field in the agent's freight rate request is empty, a response will be returned indicating that the Large Customer Code is empty, and no further processing will be performed; if the Large Customer Code field in the agent's freight rate request is non-compliant, a response will be returned indicating that the Large Customer Code is non-compliant, and no further processing will be performed; if the Large Customer Code field in the agent's freight rate request is GP, the process will proceed to the GP type reward processing module. Passenger Type Check Module: Used to extract the values ​​of the passenger type code field from the agent's fare request and determine the type of the value; it includes: If the passenger type code field in the agent's fare request is INF, then the report processing module of type NOCHECK is entered; the verification switch table and verification capability table are read. If it is determined that no further verification of the major customer code is required or the confirmed airline group code does not support the major customer code fare, then the report processing module of type NOCHECK is entered. Verification switch and capability check module: used to read the verification switch table and verification capability table, determine whether further verification of the major customer code is required, and confirm the airline group code and whether the major customer code fare is supported; Order details retrieval module: used to extract the passenger name record number from the agent's fare request and obtain the order details message through the order details query interface; Freight Rate Validation Module: Used to validate the freight rate item in the order details message; Segment Group Q Label Verification Module: Used to verify whether the order details message contains the fare Q label, and to construct a list of segments to be sent based on the verification results; The pending flight segment verification and construction module is used to construct a pending request message based on the pending flight segment list. Large Customer Verification and Construction Module: Used to send request messages to the customer management system for large customer verification, and to construct relevant remarks and service items for successfully verified request messages; The feedback processing module is used to set the corresponding feedback message parameters for different processing types and return feedback messages. The step of sending the request message to the customer management system for large customer verification includes: sending the request message to the customer management system; if no response is received within the timeout period, returning a response result indicating timeout; if the received response contains an identifier indicating that the verification failed, returning a response result indicating that the verification failed; if the received response contains an identifier indicating that the verification succeeded, constructing relevant remarks and service items for the request message, and then entering the OK type response processing module. The remarks items include ACC remarks items and FARECODE remarks items, and the service items include CKIN VICO service items; wherein: Add the airline's two-letter code, major customer code, amount of credit used this time, amount of credit remaining, and passenger identifier for the credit used to the ACC remarks section. Add the following information to the FARECODE remarks section: Customer Code, Airline Code, Flight Number, Departure and Arrival Cities, Flight Segment Dates, and Price; Add the airline's two-letter code, movement code, number of seats, and corporate customer code to the CKIN VICO service item; The corresponding reward message parameter settings for different processing types include: For OK processing types, the relevant remarks and service items are placed in the report message, and then the government flag is set to 0, the keyAccount flag is set to 1, and the vipAccount flag is set to 1 in the report message; For GP processing types, set the government flag to 1, the keyAccount flag to 0, and the vipAccount flag to 0 in the response message; For the NOCHECK processing type, the government flag, keyAccount flag, and vipAccount flag are set to 0 in the response message.

4. The apparatus according to claim 3, characterized in that, The remarks include ACC remarks and FARECODE remarks, and the service items include CKIN VICO service items.

5. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the method for processing the fare of large customers of the civil aviation open passenger reservation system as described in any one of claims 1-2.

6. An electronic device, characterized in that, include: Memory and processor; Memory: Used to store computer programs; Processor: Used to execute the computer program to implement the steps of the method for processing the fare of large customers of the civil aviation open passenger reservation system as described in any one of claims 1-2.

Images