A method for obtaining freight rate data and related device

Abstract

The application provides a fare data obtaining method and related equipment. The method can obtain a cabin fare processing request, the cabin fare processing request including journey information of a user, the journey information including cabin information; it is detected whether the cabin information includes a first-class cabin code, and if so, a fare type corresponding to the first-class cabin code is determined; and at least one first fare data corresponding to the first-class cabin code is obtained by performing fare calculation on the journey information and the first-class cabin code according to a fare acquisition strategy corresponding to the fare type. The first fare data corresponding to the first-class cabin code is calculated based on the journey information and the first-class cabin code and the fare acquisition strategy corresponding to the fare type, so that the fare data of multi-class cabins can be obtained scientifically and effectively, and the airline can flexibly control and manage the fare data of multi-class cabins.

Description

Technical Field

[0001] This disclosure relates to the field of data processing technology, and in particular to a method for obtaining freight rate data and related equipment. Background Technology

[0002] In the airline industry's cabin class management system, product fares are typically defined using cabin class codes. However, with the increasing diversification of products in the civil aviation market and the refinement of airline services, the current cabin class code management model is increasingly unable to meet the demands of detailed revenue management and diversified fare products.

[0003] To reduce the reuse of cargo space in freight rate management, achieve flexible control over revenue management, and effectively support multiple pricing for a single cargo space, multi-level cargo space control and management are required. However, there are currently no corresponding freight rate data management methods for multi-level cargo spaces, resulting in the inability to obtain freight rate data for multiple levels of cargo space.

[0004] Therefore, how to effectively obtain freight rate data across multiple cabin classes has become a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0005] In view of the above problems, this disclosure provides a method and related equipment for obtaining freight rate data to overcome or at least partially solve the above problems. The technical solution is as follows:

[0006] A method for obtaining freight rate data includes:

[0007] A cabin fare processing request is obtained, wherein the cabin fare processing request includes the user's travel information, and the travel information includes cabin information;

[0008] Detect whether the cabin information includes a primary cabin code; if it does, determine the fare type corresponding to the primary cabin code.

[0009] Using the itinerary information and the first-class cabin code, the fare is calculated according to the fare acquisition strategy corresponding to the fare type to obtain at least one first fare data corresponding to the first-class cabin code.

[0010] A freight rate data acquisition device includes: a space freight rate processing request acquisition unit, a primary space code detection unit, a type determination unit, and a first freight rate data acquisition unit.

[0011] The cabin fare processing request obtaining unit is used to obtain a cabin fare processing request, wherein the cabin fare processing request includes the user's travel information, and the travel information includes cabin information;

[0012] The first-level cabin code detection unit is used to detect whether the cabin information includes a first-level cabin code. If it does, the type determination unit is triggered.

[0013] The type determination unit is used to determine the fare type corresponding to the first-level cabin code;

[0014] The first fare data acquisition unit is used to calculate the fare using the itinerary information and the first-level cabin code, according to the fare acquisition strategy corresponding to the fare type, to obtain at least one first fare data corresponding to the first-level cabin code.

[0015] An electronic device includes at least one processor, at least one memory connected to the processor, and a bus; wherein the processor and the memory communicate with each other via the bus; the processor is used to call program instructions in the memory to execute the freight rate data acquisition method described above.

[0016] By employing the above technical solution, this disclosure provides a method and related equipment for obtaining fare data. This method can obtain a cabin fare processing request, which includes the user's itinerary information, including cabin class information. It detects whether the cabin class information includes a primary cabin class code; if so, it determines the fare type corresponding to the primary cabin class code. Using the itinerary information and the primary cabin class code, it calculates the fare according to a fare acquisition strategy corresponding to the fare type, obtaining at least one first fare data corresponding to the primary cabin class code. Based on the user's itinerary information and the primary cabin class code, this disclosure calculates the first fare data corresponding to the primary cabin class code using a fare acquisition strategy corresponding to the fare type. This enables the scientific and effective acquisition of fare data for multiple cabin classes, facilitating airlines' flexible control and management of fare data across multiple cabin classes.

[0017] The above description is merely an overview of the technical solution disclosed herein. In order to better understand the technical means of this disclosure and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this disclosure more apparent and understandable, specific embodiments of this disclosure are described below. Attached Figure Description

[0018] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0019] Figure 1 A flowchart illustrating one embodiment of the freight rate data acquisition method provided in this disclosure is shown.

[0020] Figure 2 A flowchart illustrating another implementation of the freight rate data acquisition method provided in this disclosure is shown.

[0021] Figure 3 A schematic diagram of the structure of the fare data acquisition device provided in an embodiment of this disclosure is shown;

[0022] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure is shown. Detailed Implementation

[0023] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0024] 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". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0025] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0026] It should be noted that the terms "a" and "a plurality of" used in this disclosure 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".

[0027] like Figure 1 The diagram shown illustrates a flowchart of one embodiment of the freight rate data acquisition method provided in this disclosure. The freight rate data acquisition method may include:

[0028] S100: Obtain a cabin fare processing request, wherein the cabin fare processing request includes the user's itinerary information, and the itinerary information includes cabin information.

[0029] The fare processing request can be standardized information generated from basic information entered by the user. This basic information may include the origin, destination, stopover points, passenger's ID number, and the passenger's selected cabin class. Optionally, itinerary information may include the origin, destination, flight type, and cabin class information. Cabin class information may include cabin class codes. Cabin class codes are used to indicate the seat class on a flight. For example, the cabin class code for first class is "F", for business class it is "C", and for economy class it is "Y".

[0030] S200: Check if the cabin information includes a Class 1 cabin code. If it does, proceed to step S300.

[0031] The first-level cabin class code is also called the sub-cabin code. Optionally, the first-level cabin class code is a code consisting of two or more characters and / or a one-character pre-identified as first-level. In this embodiment of the disclosure, corresponding first-level cabin class codes can be pre-assigned to each seat on the flight. For example, in this embodiment of the disclosure, the first-level cabin class code assigned to seat 1 on the flight can be "B1", and the first-level cabin class code assigned to seat 2 on the flight can be "B2".

[0032] Specifically, this embodiment of the disclosure can detect whether the cabin code in the cabin information consists of two or more characters, or whether the cabin code has been pre-identified as a level one, and determine whether the cabin code in the cabin information is a level one cabin code.

[0033] Understandably, if the cabin class code is not detected in the cabin information, it will be processed according to other methods of obtaining fare data.

[0034] S300, Determine the fare type corresponding to the Class 1 cabin code.

[0035] This disclosure allows for the pre-setting of corresponding fare types for each primary cabin class code. After detecting a primary cabin class code, the fare type corresponding to that primary cabin class code can be queried and determined. Optionally, fare types include: Publish Fare, Net Fare, and Fare By Rule.

[0036] S400: Using itinerary information and first-class cabin code, calculate the fare according to the fare acquisition strategy corresponding to the fare type, and obtain at least one first fare data corresponding to the first-class cabin code.

[0037] The fare acquisition strategy includes a pre-configured fare verification process. It's understood that each fare type corresponds to a specific fare acquisition strategy. For example, published fares correspond to published fare acquisition strategies, private fares to private fare acquisition strategies, and rule-based fares to rule-based fare acquisition strategies. It's also understood that the fare types corresponding to different first-tier cabin class codes can be the same or different.

[0038] Optionally, the fare verification process for publishing the fare acquisition strategy may include: Step a1: Processing the user's booked itinerary information, decomposing the Solution into one or more FCs (Fare Components, fare calculation units); Step a2: Processing the decomposed FCs; if the entire trip consists of multiple FCs, process them one by one; Step a3: Determining whether the request meets the admission criteria; Step a3.1: If it does not meet the admission criteria, determining whether to repeat step a2 based on whether there are any unprocessed FCs; Step a3.2: If it meets the admission criteria, performing further information verification; Step a4: Determining the passenger type, such as whether it is an adult, child, or infant; Step a5: Verifying the origin information, such as the origin being Beijing; Step a6: Verifying the destination information, such as the destination being Shanghai; Step a7: Determining the flight type, such as one-way; Step a8: Verifying the airline code, such as whether the flight is Air China; Step a9: Verifying the cabin class, determining whether the cabin class code is a secondary cabin class code or a primary cabin class code. If the cabin class code is a single letter, it is a second-level cabin class code; if the cabin class code is two digits, it is a first-level cabin class code. Step a10: Verify the flight date, for example: the flight departure time is 15:00 on January 1, 2021, and the arrival time is 18:00 on January 1, 2021. Step a11: Verify the sales date, for example: the current date is 08:30 on January 1, 2021. Step a12: Verify the published fare identifier to confirm that the fare found above is the published fare. Step a13: Verify if there are any unprocessed FCs. Step a13.1: If there are, repeat step a2. Step a13.2: If not, determine if there are any unprocessed Solutions. Step a13.2.1: If there are, repeat step a1. Step a13.2.2: If not, proceed to the next step. Step a14: Organize and output the processing results.

[0039] Optionally, the fare verification process for the private fare acquisition strategy may include: Step b1: Processing information from the user's booked trip, decomposing the Solution into one or more Functional Charges (FCs); Step b2: Processing the decomposed FCs, processing each FC individually if the entire trip consists of multiple FCs; Step b3: Determining if the request meets the admission criteria; Step b3.1: If the admission criteria are not met, determining whether to repeat step b2 based on whether there are any unprocessed FCs; Step b3.2: If the admission criteria are met, proceeding further... Information verification; Step b4: Verify the origin information, for example: origin is Beijing; Step b5: Verify the destination information, for example: destination is Shanghai; Step b6: Determine the flight type, for example: one-way; Step b7: Verify the cabin class, determine whether the cabin class code is a secondary cabin class code or a primary cabin class code. If the cabin class code is a single letter, it is a secondary cabin class code; if the cabin class code is two digits, it is a primary cabin class code; Step b9: Verify the flight date, for example: flight departure time is January 1, 2021, 15:00 Arrival time is 18:00 on January 1, 2021; Step b10: Verify the sales date, for example: the current date is 08:30 on January 1, 2021; Step b11: Determine the transit stop sign to confirm whether the fare includes a flight route; Step b12: Determine the passenger type, for example: whether it is an adult, child, infant, etc.; Step b13: Determine the itinerary stay time, for example: stay within 24 hours; Step b14: Verify the travel completion time to confirm the end time of the last flight in the entire itinerary; Step b 15: Perform discount code verification, for example: the discount code is SD; Step b16: Verify the private fare identifier to confirm that the fare determined above is a private fare; Step b17: Check if there are any unprocessed FCs; Step b17.1: If there are, repeat step b2; Step b17.2: If not, check if there are any unprocessed Solutions; Step b17.2.1: If there are, repeat step b1; Step b17.2.2: If not, proceed to the next step; Step b18: Organize and output the processing results.

[0040] Optionally, the fare verification process corresponding to the rule-based fare acquisition strategy may include: Step c1: Processing the information in the user's booked trip, decomposing the Solution into one or more FCs (Fare). Component (fare calculation unit); Step c2: Process the decomposed FC. If there are multiple FCs in the whole process, process them one by one; Step c3: Determine if the request meets the admission criteria; Step c3.1: If it does not meet the admission criteria, determine whether to repeat step c2 based on whether there are any unprocessed FCs; Step c3.2: If it meets the admission criteria, perform further information verification; Step c4: Verify the origin information; Step c5: Verify the destination information; Step c6: Determine the flight type; Step c7: Verify the airline code; Step c8: Verify the cabin class, determine whether the cabin class code is a secondary cabin class code or a primary cabin class code. If the cabin class code is a single letter, it is a secondary cabin class code; if the cabin class code is two digits, it is a primary cabin class code; Step c9: Verify the flight date; Step c10: Verify the sales date; Step c11: Determine the applicable identifier for the small cabin class and confirm. Step c12: Verify the large customer code; Step c13: Determine the itinerary layover time; Step c14: Determine whether it is a connecting / direct itinerary; Step c15: Verify the discount code; Step c16: Determine if there is a matching rule-based fare; Step c16.1: If it exists, proceed to step c17; Step c16.2: If it does not exist, proceed to step c19; Step c17: Obtain the original fare as the condition for calculating the rule-based fare; Step c18: Obtain the minimum fare and determine if the rule-based fare result is compliant; Step c19: Check if there are any unprocessed FCs; Step c19.1: If there are, repeat step c2; Step c19.2: If not, determine if there are any unprocessed Solutions; Step c19.2.1: If there are, repeat step c1; Step c19.2.2: If not, proceed to the next step; Step c20: Organize and output the processing results.

[0041] This embodiment of the disclosure introduces sales rule restriction information for fare products through a fare acquisition strategy corresponding to the fare type. It binds sales conditions (season, passenger, flight, combination, and refund / change) and other rule conditions with the price, performs fare calculation, and verifies at least one first fare data corresponding to the itinerary information and first-class cabin code.

[0042] This disclosure provides a method for obtaining fare data. The method involves obtaining a fare processing request, which includes the user's itinerary information, including fare class information. The method detects whether the fare class information includes a primary fare class code; if so, it determines the fare type corresponding to the primary fare class code. Using the itinerary information and the primary fare class code, the method calculates the fare according to a fare acquisition strategy corresponding to the fare type, obtaining at least one first fare data corresponding to the primary fare class code. Based on the user's itinerary information and the primary fare class code, this disclosure calculates the first fare data corresponding to the primary fare class code using a fare acquisition strategy corresponding to the fare type. This method can scientifically and effectively obtain fare data for multiple fare classes, facilitating airlines' flexible control and management of fare data for multiple fare classes.

[0043] Optional, based on Figure 1 The method shown is as follows: Figure 2 The diagram shows a flowchart of another embodiment of the freight rate data acquisition method provided in this disclosure. The freight rate data acquisition method may further include:

[0044] A100. If the cabin class information includes a primary cabin class code, determine the secondary cabin class code to which the primary cabin class code belongs and the display type corresponding to the primary cabin class code.

[0045] The secondary cabin class code is also called the major cabin class code. A secondary cabin class code can be a single-character code. Typically, a secondary cabin class code is a single letter. In this embodiment, the hierarchical relationship between each primary cabin class code and the secondary cabin class code can be pre-defined. For example, primary cabin class codes "B1" and "B2" belong to the secondary cabin class code "B". It is understood that in this embodiment, upon detecting a primary cabin class code, the secondary cabin class code to which that primary cabin class code belongs can be queried and determined.

[0046] This disclosure embodiment allows for pre-setting corresponding display types for each primary cabin class code. Optionally, the display type may include displaying only the primary cabin class fare and displaying fares for all cabin classes. For example, the control information for setting cabin class codes in this disclosure embodiment may be shown in Table 1.

[0047] Table 1

[0048]

[0049] A200. When the display type is set to display fares for each class of cabin, the fare is calculated using the itinerary information and the secondary cabin code, according to the fare acquisition strategy corresponding to the fare type, to obtain at least one second fare data corresponding to the secondary cabin code.

[0050] This embodiment of the disclosure can simultaneously obtain the fare data of the second-level fare codes to which the first-level fare code belongs when the display type is set to display fares for each fare class. The process of obtaining the second fare data corresponding to the second-level fare code is similar to the process of obtaining the first fare data corresponding to the first-level fare code, and can be found in the description of step S400, which will not be repeated here.

[0051] This embodiment of the disclosure calculates the fare data corresponding to the primary and secondary fare codes separately, and adopts different processing mechanisms according to different fare types. It flexibly manages the fare data from the perspective of each level of fare code, realizes the function of one fare with multiple prices in the context of diversified fare products, effectively reduces the reuse of fare slots in fare management, and flexibly manages revenue.

[0052] Optionally, in embodiments of this disclosure, when the fare type corresponding to the primary cabin class code is a private fare or a rule-based fare, the first route configuration data corresponding to the primary cabin class code is determined using the itinerary information and the primary cabin class code. The first configured route corresponding to each first fare data is determined from the first route configuration data. The first itinerary route corresponding to the primary cabin class code is determined from the itinerary information. The first itinerary routes are verified against each first configured route, and the first fare data corresponding to the first configured route that passes the verification is determined as the third fare data.

[0053] This disclosure allows for the pre-configuration of one or more first route configuration data for primary cabin class codes under different itinerary information. The first route configuration data may include origin, destination, cabin class, fare, and the first configured route. The first configured route includes origin, stopover points, destination, and the cabin class code corresponding to each segment.

[0054] Specifically, in this embodiment of the disclosure, the origin and destination under the itinerary information can be combined with the Class 1 cabin code to query one or more corresponding first-line configuration data. For example, Table 2 shows the configuration data of three first-line routes with the origin in Beijing (PEK), the destination in Guangzhou (CAN), and the Class 1 cabin code "B1".

[0055] Table 2

[0056] Origin destination cabin Amount First configured route PEK CAN B1 1000.00 none PEK CAN B1 1100.00 PEK-(B1)-SHA-(B1)-CAN PEK CAN B1 1200.00 PEK-(B1)-SHA-(K1)-CAN

[0057] To facilitate understanding, an example is provided here: Based on Table 2, assuming the itinerary information includes "PEK-(B1)-SHA-(B1)-CAN", the first itinerary route corresponding to the Class 1 cabin code can include "PEK-(B1)-SHA" and "SHA-(B1)-CAN". If the first fare data with an amount of 1100 is obtained based on "PEK-(B1)-SHA" and the first fare data with an amount of 1200 is obtained based on "SHA-(B1)-CAN", it can be determined that the first configured route corresponding to the first fare data with an amount of 1100 is "PEK-( The first fare data with an amount of 1200 was determined to be “PEK-(B1)-SHA-(K1)-CAN”. The two first trip routes were verified with their respective first configuration routes. Since the first trip route “SHA-(B1)-CAN” was inconsistent with the first configuration route “PEK-(B1)-SHA-(K1)-CAN”, the first fare data with an amount of 1200 was filtered out, and the first fare data with an amount of 1100 was determined as the third fare data.

[0058] This embodiment of the disclosure verifies the route by comparing the first configured route with the first travel route, and can filter out the third fare data that meets the preset configuration requirements from each first fare data, thereby further meeting the requirements for fare data for multiple cabin classes.

[0059] Optionally, in this embodiment of the disclosure, after verifying the first itinerary route with each of the first configured routes, and determining the first fare data corresponding to the verified first configured routes as the third fare data, rule verification is performed on the third fare data based on the itinerary information to obtain a first rule verification result. Permission verification is then performed on the third fare data based on the itinerary information to obtain a first permission verification result. Third fare data for which both the first rule verification result and the first permission verification result are verified are then displayed.

[0060] The rule verification can include verification of any of the following restriction rules: blackout period restriction, seasonality restriction, week restriction, flight number restriction, combination restriction, advance purchase restriction, and group passenger restriction.

[0061] The permission verification can include verification of any permission among system, channel, sales agency code, city, and country.

[0062] This disclosure embodiment can provide third-party fare data that has passed both rule verification and permission verification to the sales terminal or passenger terminal for display, so that relevant users can select from the displayed third-party fare data.

[0063] Optionally, in embodiments of this disclosure, when the fare type corresponding to the primary cabin class code is a private fare or a rule-based fare, the second route configuration data corresponding to the secondary cabin class code can be determined using the itinerary information and the secondary cabin class code. The second configured route corresponding to each secondary fare data is determined from the second route configuration data. The second itinerary route corresponding to the secondary cabin class code is determined from the itinerary information. The second itinerary routes are verified against each secondary configured route, and the second fare data corresponding to the verified secondary configured routes is determined as the fourth fare data.

[0064] This disclosure allows for the pre-configuration of one or more second route configuration data for secondary cabin class codes under different itinerary information. The second route configuration data may include the origin, destination, cabin class, fare, and the second configured route. The second configured route includes the origin, stopover points, destination, and the cabin class code corresponding to each segment.

[0065] Specifically, in this embodiment of the disclosure, the origin and destination under the itinerary information, combined with the secondary cabin code, can be used to query one or more corresponding secondary route configuration data. For example, Table 3 shows the configuration data for two secondary routes with Beijing (PEK) as the origin, Guangzhou (CAN) as the destination, and the secondary cabin code "B".

[0066] Table 3

[0067] Origin destination cabin Amount Second configuration route PEK CAN B 1300.00 PEK-(B)-SHA-(B)-CAN PEK CAN B 1400.00 PEK-(B)-SHA-(K)-CAN

[0068] To facilitate understanding, an example is provided here: Based on Table 3, assuming the itinerary information includes "PEK-(B1)-SHA-(B1)-CAN", since the first-class cabin code "B1" belongs to the second-class cabin code "B", the second itinerary route corresponding to the second-class cabin code can include "PEK-(B)-SHA" and "SHA-(B)-CAN". If a second fare of 1300 is obtained based on "PEK-(B)-SHA" and a second fare of 1400 is obtained based on "SHA-(B)-CAN", it can be determined that the second fare of 1300 corresponds to... The second configured route is "PEK-(B)-SHA-(B)-CAN". The second configured route corresponding to the second fare data with an amount of 1400 is determined to be "PEK-(B)-SHA-(K)-CAN". The two second itinerary routes are verified with their respective second configured routes. Since the second itinerary route "SHA-(B)-CAN" is inconsistent with the route where the second class code is located in the second configured route "PEK-(B)-SHA-(K)-CAN", the second fare data with an amount of 1400 is filtered out, and the second fare data with an amount of 1300 is determined as the fourth fare data.

[0069] This embodiment of the disclosure verifies the route by comparing the second configured route with the second travel route, and can filter out the fourth fare data that meets the preset configuration requirements from each second fare data, thereby further meeting the requirements for fare data for multiple cabin classes.

[0070] Optionally, in this embodiment of the disclosure, after verifying the second itinerary route with each of the second configured routes, and determining the second fare data corresponding to the verified second configured routes as the fourth fare data, rule verification is performed on the fourth fare data based on the itinerary information to obtain a second rule verification result. Permission verification is then performed on the fourth fare data based on the itinerary information to obtain a second permission verification result. Fourth fare data for which both the second rule verification result and the second permission verification result are verified are then displayed.

[0071] This embodiment of the disclosure can provide fourth fare data that has passed both rule verification and permission verification to the sales terminal or passenger terminal for display, so that relevant users can select from the displayed fourth fare data.

[0072] This disclosure provides a fare management platform for inputting and maintaining control information such as fare types and display types corresponding to multiple cabin classes. Through a visual fare management interface, users can create, modify, delete, and query relevant control information. The platform also supports batch import of control information using Excel templates and provides an XML file interface for batch importing XML format files, facilitating data integration with other airline systems.

[0073] The fare data acquisition method provided in this disclosure addresses the problems faced by airlines, such as a severe shortage of cabin class codes, complex product management with multiple fares per cabin class, and difficulty in publishing fares. It provides flexible management of different fare data under multiple cabin classes, meets the different needs of different products, and can scientifically and effectively obtain fare data for multiple cabin classes in practical applications.

[0074] Although the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous.

[0075] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0076] Corresponding to the above method embodiments, this disclosure also provides a fare data acquisition device, the structure of which is as follows: Figure 3 As shown, it may include: a cabin fare processing request acquisition unit 100, a first-level cabin code detection unit 200, a type determination unit 300, and a first fare data acquisition unit 400.

[0077] The cabin fare processing request obtaining unit 100 is used to obtain a cabin fare processing request, wherein the cabin fare processing request includes the user's itinerary information, and the itinerary information includes cabin information.

[0078] The Level 1 Cabin Code Detection Unit 200 is used to detect whether the cabin information includes a Level 1 Cabin Code. If it does, the Type Determination Unit 300 is triggered.

[0079] Type determination unit 300 is used to determine the fare type corresponding to the first-class cabin code.

[0080] The first fare data acquisition unit 400 is used to calculate fares using itinerary information and first-class cabin codes, according to a fare acquisition strategy corresponding to the fare type, and to obtain at least one first fare data corresponding to the first-class cabin code.

[0081] Optionally, the freight rate data acquisition device may further include: a first determining unit and a first acquiring unit.

[0082] The first determining unit is used to determine the secondary cabin code to which the primary cabin code belongs and the display type corresponding to the primary cabin code, when the cabin information includes a primary cabin code.

[0083] The first obtaining unit is used to calculate the fare using the itinerary information and the secondary cabin code, according to the fare acquisition strategy corresponding to the fare type, when the display type is to display fares for each cabin class, and obtain at least one second fare data corresponding to the secondary cabin code.

[0084] Optional rate types include: published rates, private rates, and rule-based rates.

[0085] Optionally, the freight rate data acquisition device may further include: a second determining unit, a third determining unit, a fourth determining unit, and a fifth determining unit.

[0086] The second determining unit is used to determine the first route configuration data corresponding to the first-level cabin code by using the itinerary information and the first-level cabin code, when the fare type corresponding to the first-level cabin code is a private fare or a rule fare.

[0087] The third determining unit is used to determine the first configured routes corresponding to each first fare data in the first route configuration data.

[0088] The fourth determining unit is used to determine the first itinerary route corresponding to the first class cabin code in the itinerary information.

[0089] The fifth determining unit is used to verify the first trip route against each of the first configured routes, and to determine the first fare data corresponding to the first configured route that passes the verification as the third fare data.

[0090] Optionally, the freight rate data acquisition device may further include: a sixth determining unit, a seventh determining unit, an eighth determining unit, and a ninth determining unit.

[0091] The sixth determining unit is used to determine the second route configuration data corresponding to the second-level cabin code by using the itinerary information and the second-level cabin code, when the fare type corresponding to the first-level cabin code is a private fare or a rule fare.

[0092] The seventh determining unit is used to determine the second configured routes corresponding to each second fare data in the second route configuration data.

[0093] The eighth determining unit is used to determine the second itinerary route corresponding to the second class cabin code in the itinerary information.

[0094] The ninth determining unit is used to verify the second itinerary route against each of the second configured routes, and to determine the second fare data corresponding to the verified second configured route as the fourth fare data.

[0095] Optionally, the fare data acquisition device may further include: a second acquisition unit, a third acquisition unit, and a first display unit.

[0096] The second obtaining unit is used to verify the first trip route with each of the first configured routes in the fifth determining unit, and after determining the first fare data corresponding to the first configured route that has passed the verification as the third fare data, perform rule verification on the third fare data based on the trip information to obtain the first rule verification result.

[0097] The third obtaining unit is used to perform permission verification on the third fare data based on the trip information and obtain the first permission verification result.

[0098] The first display unit is used to display the third fare data where both the first rule verification result and the first permission verification result have passed.

[0099] Optionally, the fare data acquisition device may further include: a fourth acquisition unit, a fifth acquisition unit, and a second display unit.

[0100] The fourth obtaining unit is used to verify the second itinerary route against each of the second configured routes in the ninth determining unit, and after determining the second fare data corresponding to the verified second configured route as the fourth fare data, perform rule verification on the fourth fare data based on the itinerary information to obtain the second rule verification result.

[0101] The fifth obtaining unit is used to perform permission verification on the fourth fare data based on the trip information and obtain the second permission verification result.

[0102] The second display unit is used to display the fourth fare data where both the second rule verification result and the second permission verification result have passed the verification.

[0103] Optionally, the Class 1 cabin code is a code consisting of two or more characters and / or a single character pre-identified as Class 1.

[0104] This disclosure provides a fare data acquisition device that can receive a cabin class fare processing request, which includes the user's itinerary information, including cabin class information. The device detects whether the cabin class information includes a primary cabin class code; if so, it determines the fare type corresponding to the primary cabin class code. Using the itinerary information and the primary cabin class code, it calculates the fare according to a fare acquisition strategy corresponding to the fare type, obtaining at least one first fare data corresponding to the primary cabin class code. Based on the user's itinerary information and the primary cabin class code, this disclosure calculates the first fare data corresponding to the primary cabin class code using a fare acquisition strategy corresponding to the fare type. This enables the scientific and effective acquisition of fare data for multiple cabin classes, facilitating airlines to flexibly control and manage fare data for multiple cabin classes.

[0105] Regarding the apparatus in the above embodiments, the specific manner in which each unit performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0106] The fare data acquisition device includes a processor and a memory. The aforementioned cabin fare processing request acquisition unit 100, first-level cabin code detection unit 200, type determination unit 300, and first fare data acquisition unit 400 are all stored as program units in the memory. The processor executes the aforementioned program units stored in the memory to realize the corresponding functions.

[0107] The processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured. By adjusting kernel parameters, based on the user's itinerary information and first-class cabin code, and using a fare acquisition strategy corresponding to the fare type, the first fare data corresponding to that first-class cabin code can be calculated scientifically and effectively. This allows airlines to flexibly control and manage fare data across multiple cabin classes.

[0108] This disclosure provides a computer-readable storage medium having a program stored thereon that, when executed by a processor, implements the freight rate data acquisition method.

[0109] This disclosure provides a processor for running a program, wherein the program executes the freight rate data acquisition method during runtime.

[0110] like Figure 4As shown, the electronic device 500 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 506 into a random access memory (RAM) 503. The RAM 503 also stores various programs and data required for the operation of the electronic device 500. The processing unit 501, ROM 502, and RAM 503 are interconnected via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0111] Typically, the following devices can be connected to I / O interface 505: input devices 506 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 507 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 506 including, for example, magnetic tapes, hard disks, etc.; and communication devices 509. Communication device 509 allows electronic device 500 to communicate wirelessly or wiredly with other devices to exchange data. Although... Figure 4 An electronic device 500 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0112] This disclosure also provides a computer program product that, when executed on an electronic device, is adapted to execute a program that initializes a method for obtaining freight data.

[0113] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus, electronic devices (systems), and computer program products according to embodiments of this disclosure. 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 device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable device, generate instructions for implementing the flowchart. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0114] In a typical configuration, an electronic device includes one or more processors (CPUs), memory, and a bus. The electronic device may also include input / output interfaces, network interfaces, etc.

[0115] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, like read-only memory (ROM) or flash RAM, and memory includes at least one memory chip. Memory is an example of computer-readable media.

[0116] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0117] In the description of this disclosure, it should be understood that if the terms "upper", "lower", "front", "rear", "left" and "right" are used to indicate the orientation or positional relationship based on the orientation or positional relationship shown in the drawings, they are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the position or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of this disclosure.

[0118] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, systems, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure 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.

[0119] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

[0120] While several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0121] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure 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. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

Claims

1. A method for obtaining freight rate data, characterized in that, include: A cabin fare processing request is obtained, wherein the cabin fare processing request includes the user's travel information, and the travel information includes cabin information; The system detects whether the cabin class information includes a primary cabin class code. If it does, it determines the fare type corresponding to the primary cabin class code. The fare type includes: published fares, private fares, and rule-based fares. Using the itinerary information and the first-class cabin code, the fare is calculated according to the fare acquisition strategy corresponding to the fare type to obtain at least one first fare data corresponding to the first-class cabin code; When the fare type corresponding to the primary cabin class code is the private fare or the rule fare, the first route configuration data corresponding to the primary cabin class code is determined using the itinerary information and the primary cabin class code; In the first route configuration data, determine the first configured route corresponding to each of the first fare data; Determine the first itinerary route corresponding to the Class 1 cabin code from the itinerary information; The first itinerary route is verified against each of the first configured routes, and the first fare data corresponding to the first configured route that passes the verification is determined as the third fare data.

2. The method according to claim 1, characterized in that, Also includes: If it is determined that the cabin information includes the primary cabin code, then determine the secondary cabin code to which the primary cabin code belongs and the display type corresponding to the primary cabin code; When the display type is to display fares for each cabin class, the fare is calculated using the itinerary information and the secondary cabin class code, according to the fare acquisition strategy corresponding to the fare type, to obtain at least one second fare data corresponding to the secondary cabin class code.

3. The method according to claim 2, characterized in that, Also includes: When the fare type corresponding to the primary cabin class code is the private fare or the rule fare, the second route configuration data corresponding to the secondary cabin class code is determined using the itinerary information and the secondary cabin class code; In the second route configuration data, determine the second configured route corresponding to each of the second fare data; Determine the second itinerary route corresponding to the second-class cabin code from the itinerary information; The second itinerary route is verified against each of the second configured routes, and the second fare data corresponding to the second configured route that passes the verification is determined as the fourth fare data.

4. The method according to claim 1, characterized in that, After verifying the first itinerary route against each of the first configured routes, and determining the first fare data corresponding to the first configured route that passes the verification as the third fare data, the method further includes: Based on the itinerary information, the third fare data is subjected to rule verification to obtain the first rule verification result; the rule verification includes verification of any of the following restriction rules: exclusion date restriction, seasonal restriction, weekday restriction, flight number restriction, combination restriction, advance ticketing restriction, and group / individual traveler restriction; Based on the trip information, the third fare data is subjected to permission verification to obtain a first permission verification result; the permission verification includes verification of any one of the following permissions: system, channel, sales agency code, city, and country; The third fare data is displayed if both the first rule verification result and the first permission verification result are passed.

5. The method according to claim 3, characterized in that, After verifying the second itinerary route against each of the second configured routes, and determining the second fare data corresponding to the verified second configured routes as the fourth fare data, the method further includes: Based on the itinerary information, the fourth fare data is subjected to rule verification to obtain a second rule verification result; the rule verification includes verification of any of the following restriction rules: exclusion date restriction, seasonal restriction, weekday restriction, flight number restriction, combination restriction, advance ticketing restriction, and group / individual traveler restriction; Based on the trip information, the fourth fare data is subjected to permission verification to obtain a second permission verification result; the permission verification includes verification of any one of the following permissions: system, channel, sales agency code, city, and country; The fourth fare data is displayed if both the second rule verification result and the second permission verification result are passed.

6. The method according to claim 1, characterized in that, The Class 1 cabin code is a code consisting of two or more characters and / or a single character pre-identified as Class 1.

7. A freight rate data acquisition device, characterized in that, include: The system comprises a cabin class fare processing request acquisition unit, a first-level cabin class code detection unit, a type determination unit, a first fare data acquisition unit, a second determination unit, a third determination unit, a fourth determination unit, and a fifth determination unit. The cabin fare processing request obtaining unit is used to obtain a cabin fare processing request, wherein the cabin fare processing request includes the user's travel information, and the travel information includes cabin information; The first-level cabin code detection unit is used to detect whether the cabin information includes a first-level cabin code. If it does, the type determination unit is triggered. The type determination unit is used to determine the fare type corresponding to the primary cabin class code; the fare type includes: published fare, private fare, and rule-based fare. The first fare data acquisition unit is used to calculate the fare using the itinerary information and the first-level cabin code, according to the fare acquisition strategy corresponding to the fare type, to obtain at least one first fare data corresponding to the first-level cabin code. The second determining unit is used to determine the first route configuration data corresponding to the first-level cabin code by using the itinerary information and the first-level cabin code when the fare type corresponding to the first-level cabin code is the private fare or the rule fare; The third determining unit is used to determine the first configured routes corresponding to each of the first fare data in the first route configuration data; The fourth determining unit is used to determine the first itinerary route corresponding to the first-class cabin code in the itinerary information; The fifth determining unit is used to verify the first itinerary route against each of the first configured routes, and to determine the first fare data corresponding to the first configured route that passes the verification as the third fare data.

8. An electronic device, the electronic device comprising at least one processor, and at least one memory and a bus connected to the processor; wherein, The processor and the memory communicate with each other via the bus; The processor is used to invoke program instructions in the memory to execute the freight rate data acquisition method as described in any one of claims 1 to 6.

Images