A method and device for determining a charter flight fare, an electronic device, and a storage medium

By receiving airfare calculation requests, matching and filtering charter flight fares, the problem of low efficiency and numerous errors in charter flight fare determination in existing technologies is solved, and automated and accurate fare calculation is achieved.

CN115345679BActive Publication Date: 2026-07-24TRAVELSKY TECHNOLOGY LIMITED
View PDF 4 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
TRAVELSKY TECHNOLOGY LIMITED
Filing Date
2022-08-23
Publication Date
2026-07-24

Smart Images

  • Figure CN115345679B_ABST
    Figure CN115345679B_ABST
Patent Text Reader

Abstract

The application discloses a method and device for determining a charter flight ticket price, electronic equipment and a storage medium. The method comprises the following steps: receiving a ticket price calculation request sent by a front end; wherein the ticket price calculation request comprises at least personal information, itinerary information of a current passenger and flight information of a target flight; based on the personal information, itinerary information of the current passenger and the flight information of the target flight, matching each initial available price from each pre-configured price information of the target flight; judging whether the target flight belongs to a charter flight based on a pre-configured charter flight data cluster; if the target flight belongs to a charter flight, searching for charter flight applicable rules bound by each initial available price from a pre-configured rule data cluster; based on the charter flight applicable rules bound by each initial available price, eliminating the initial available price not applicable to the charter flight to obtain a final available price; and feeding back each final available price to the front end.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of fare calculation, and in particular to a method and apparatus for determining charter flight fares, electronic equipment, and storage medium. Background Technology

[0002] In recent years, with continuous economic development and the gradual improvement of people's living standards, the economic capacity of the general public has also increased. As the most convenient and comfortable mode of travel, civil aviation is increasingly accepted by passengers and has gradually become the preferred mode of transportation for business, family visits, and leisure travel. Furthermore, in certain special circumstances, charter flights are often necessary.

[0003] When chartering a flight is needed, passengers need to contact the relevant carrier to understand the corresponding costs. The carrier will then prepare a quotation based on the passenger's specific travel situation and the airline's pricing policy, and provide it to the passenger.

[0004] However, the existing method is relatively slow because it requires contacting the relevant carrier and having the carrier manually provide a quote, and it is also prone to errors. Summary of the Invention

[0005] In view of the shortcomings of the prior art, this application provides a method and apparatus, electronic device and storage medium for determining charter flight fares, so as to solve the problems that the existing methods are not convenient enough and are prone to errors.

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

[0007] The first aspect of this application provides a method for determining charter flight fares, including:

[0008] Receive a ticket fare calculation request sent from the front end; wherein the ticket fare calculation request includes at least the current passenger's personal information, itinerary information, and flight information of the target flight;

[0009] Based on the current passenger's personal information, the itinerary information, and the flight information of the target flight, each initial available fare is matched from the pre-configured fare information of the target flight;

[0010] Based on a pre-configured charter flight data cluster, determine whether the target flight is a charter flight;

[0011] If it is determined that the target flight is a charter flight, then the applicable rules for each charter flight bound to the initial available fare are found from the pre-configured rule data cluster.

[0012] Based on the applicable rules for charter flights bound to each of the initial available fares, filter out the initial available fares that are not applicable to charter flights;

[0013] Each of the initial available fares that are not applicable to charter flights is removed to obtain the final available fares;

[0014] The final available freight rates are fed back to the front end.

[0015] Optionally, the above-mentioned method for determining charter flight fares may also include:

[0016] In response to the user's charter flight information creation operation, the charter flight information set by the user is obtained;

[0017] The legality of the charter flight information is verified.

[0018] If the charter flight information passes the legality verification, the charter flight information will be saved to the charter flight data cluster.

[0019] Optionally, the above-mentioned method for determining charter flight fares may also include:

[0020] In response to a user's charter flight rule creation operation, the system obtains the rule application scope information and rule type set by the user; wherein, the rule type includes applicable to charter flights, applicable only to charter flights, and not applicable to charter flights;

[0021] Based on the user-defined rule scope and rule type, create a rule applicable to charter flights;

[0022] The legality of the rules applicable to the created charter flights shall be verified.

[0023] If the created charter flight applicable rules pass the legality verification, the charter flight applicable rules will be stored in the rule data cluster.

[0024] Optionally, in the above-described method for determining charter flight fares, before receiving the ticket fare calculation request sent by the front end, the method further includes:

[0025] In response to the user's flight fare creation operation, obtain the fare and fare usage scope information of the target flight set by the user;

[0026] Based on the fare of the target flight and the fare application scope information, create a fare information entry for the target flight;

[0027] Bind the fare information of the target flight to the applicable rules of the selected charter flight;

[0028] The legality of the fare information for the target flight is verified;

[0029] If the fare information of the target flight passes the validity verification, the fare information of the target flight will be saved.

[0030] Optionally, the above-mentioned method for determining charter flight fares may also include:

[0031] If it is determined that the target flight is not a charter flight, then the initial available fares that are only applicable to charter flights are filtered out, and the remaining initial available fares are fed back to the front end.

[0032] A second aspect of this application provides a charter flight fare determination apparatus, comprising:

[0033] A receiving unit is used to receive a ticket fare calculation request sent by the front end; wherein the ticket fare calculation request includes at least the current passenger's personal information, itinerary information, and flight information of the target flight;

[0034] The initial fare determination unit is used to match each initial available fare from the pre-configured fare information of the target flight based on the current passenger's personal information, the itinerary information, and the flight information of the target flight.

[0035] The judgment unit is used to determine whether the target flight belongs to a charter flight based on a pre-configured charter flight data cluster.

[0036] The rule lookup unit is used to find the applicable rules for each charter flight bound to the initial available fare from the pre-configured rule data cluster when it is determined that the target flight belongs to a charter flight.

[0037] The filtering unit is used to filter out each of the initial available fares that are not applicable to charter flights based on the applicable rules for each of the initial available fares.

[0038] The elimination unit is used to eliminate each of the initial available fares that are not applicable to charter flights, thereby obtaining each final available fare;

[0039] The first feedback unit is used to feed back each of the final available fares to the front end.

[0040] Optionally, the charter flight fare determination device described above further includes:

[0041] The first response unit is used to respond to the user's charter flight information creation operation and obtain the charter flight information set by the user;

[0042] The first verification unit is used to verify the legality of the charter flight information;

[0043] The first storage unit is used to save the charter flight information to the charter flight data cluster when the charter flight information passes the legality verification.

[0044] Optionally, the charter flight fare determination device described above further includes:

[0045] The second response unit is used to respond to the user's charter flight rule creation operation, and to obtain the rule application scope information and rule type set by the user; wherein, the rule type includes applicable to charter flights, applicable only to charter flights, and not applicable to charter flights;

[0046] The rule creation unit is used to create a rule applicable to a charter flight based on the rule application scope and rule type set by the user.

[0047] The second verification unit is used to verify the legality of the rules applicable to the charter flight that have been created;

[0048] The second storage unit is used to store the charter flight applicable rules into the rule data cluster when the created charter flight applicable rules pass the legality verification.

[0049] Optionally, the charter flight fare determination device described above further includes:

[0050] The third response unit is used to respond to the user's flight fare creation operation and obtain the fare and fare usage scope information of the target flight set by the user;

[0051] The fare creation unit is used to create a fare information for the target flight based on the fare of the target flight and the fare application scope information;

[0052] A binding unit is used to bind the fare information of the target flight with the applicable rules of the selected charter flight;

[0053] The third verification unit is used to verify the legality of the fare information of the target flight.

[0054] The third storage unit is used to save the fare information of the target flight when the fare information of the target flight passes the legality verification.

[0055] Optionally, the charter flight fare determination device described above further includes:

[0056] The second feedback unit is used to filter out the initial available fares that are only applicable to charter flights when it is determined that the target flight is not a charter flight, and to feed back the remaining initial available fares to the front end.

[0057] A third aspect of this application provides an electronic device, comprising:

[0058] One or more processing devices;

[0059] A memory on which one or more programs are stored;

[0060] When the one or more programs are executed by the one or more processing devices, the one or more processing devices implement the charter flight fare determination method as described in any of the preceding claims.

[0061] The fourth aspect of this application provides a computer storage medium for storing a program, which, when executed, is used to implement the charter flight fare determination method as described in any of the preceding claims.

[0062] This application provides a method for determining charter flight fares, which receives a ticket fare calculation request sent from a front-end. The ticket fare calculation request includes at least the current passenger's personal information, itinerary information, and the target flight's flight information. Then, based on the current passenger's personal information, itinerary information, and target flight information, initial available fares are matched from pre-configured fare information for the target flight. Based on a pre-configured charter flight data cluster, it is determined whether the target flight belongs to a charter flight. If the target flight is determined to be a charter flight, the applicable rules for charter flights bound to each initial available fare are found from a pre-configured rule data cluster. Based on these applicable rules, initial available fares that are not applicable to charter flights are filtered out. These inapplicable initial available fares are then removed, resulting in final available fares, which are then fed back to the front-end. This achieves automatic calculation of fares for charter flights that meet passenger travel needs, making the acquisition of charter flight fares more convenient and effectively avoiding errors. Attached Figure Description

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

[0064] Figure 1This application provides a schematic diagram of the architecture of a charter flight fare determination system.

[0065] Figure 2 A flowchart illustrating a method for determining charter flight fares provided in this application embodiment;

[0066] Figure 3 A flowchart illustrating a method for configuring charter flight data provided in this application embodiment;

[0067] Figure 4 A flowchart illustrating a method for configuring rule data provided in an embodiment of this application;

[0068] Figure 5 A flowchart illustrating a method for configuring freight rate data provided in an embodiment of this application;

[0069] Figure 6 This is a schematic diagram of a charter flight fare determination device provided in an embodiment of this application;

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

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

[0072] In this application, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0073] This application provides a method for determining charter flight fares to address the problems that existing methods are not convenient enough and are prone to errors.

[0074] Optionally, to implement the charter flight fare determination method provided in this application embodiment, this application embodiment also provides a charter flight fare determination system, such as... Figure 1 As shown, it includes:

[0075] The components include: airfare management components, charter flight data clusters, rule data clusters, fare data clusters, airfare calculation components, and sales front-end components.

[0076] The airfare management component is primarily used to maintain information such as charter flight number ranges, airfare information, airfare rules, agency fees, and taxes. Specifically, it includes modules for publishing charter flight numbers, charter flight rules, and airfares.

[0077] The charter flight data cluster includes a charter flight number database, which stores information about published charter flight numbers.

[0078] The rules data cluster includes a rules database, which stores the rule restrictions on airfares published by various airlines.

[0079] The fare data cluster includes a fare database that stores fare information for each published flight.

[0080] The airfare calculation component includes an airfare calculation and processing module, which, upon receiving a calculation request, searches for fare data clusters, rule data clusters, and charter flight data clusters, and filters and calculates available airfares based on conditions such as itinerary information and passenger information, and returns them to the sales front-end component.

[0081] The sales front-end components include a ticket sales trigger module, which is mainly used to interact with passengers and trigger ticket calculation requests.

[0082] Based on the charter flight fare determination system described above, this application provides a method for determining charter flight fares, such as... Figure 2 As shown, it includes the following steps:

[0083] S201. Receive the airfare calculation request sent by the front end.

[0084] The ticket fare calculation request must include at least the current passenger's personal information, itinerary information, and the flight information of the target flight.

[0085] Optionally, the passenger's personal information may include basic customer identity information, as well as passenger class information. Itinerary information may include itinerary type, origin, destination, and travel time. Flight information may include flight number and cabin class.

[0086] S202. Based on the current passenger's personal information, itinerary information, and the target flight's flight information, match each initial available fare from the pre-configured fare information of the target flight.

[0087] It should be noted that in this embodiment, flight information for each flight is pre-configured. Therefore, based on the current passenger's personal information, itinerary information, and the target flight's flight information, the fare that matches the current passenger's travel requirements and identity can be selected from the various fare information of the target flight as the initial available fare.

[0088] For example, if the itinerary is CTU-HAK and flight number is 2348, the initial available fares could include: 01. Base fare YOW, price 2800 CNY; 02. Base fare Y / CCNOW97, price 2500 CNY; 03. Base fare Y / NRT95, price 2400 CNY; 04. Base fare Y / NNW98, price 2600 CNY; 05. Base fare Y / NCCT99, price 2700 CNY; 06. Base fare Y / NORMAL97, price 2550 CNY.

[0089] S203. Based on the pre-configured charter flight data cluster, determine whether the target flight is a charter flight.

[0090] It should be noted that, in this embodiment of the application, the charter flight fare determination service can be added to the existing fare service system, thereby eliminating the need to build a separate system, saving costs, improving efficiency, and making it easier for users to use.

[0091] Therefore, if the target flight is a regular flight, it is necessary to first determine whether the target flight is a charter flight based on the pre-configured charter flight data cluster.

[0092] The pre-configured charter flight data cluster includes relevant information for each pre-configured charter flight.

[0093] Optionally, another embodiment of this application provides a method for configuring charter flight data, such as... Figure 3 As shown, it includes:

[0094] S301: Respond to the user's charter flight information creation operation and obtain the charter flight information set by the user.

[0095] Alternatively, users can access the creation interface by clicking the "Create" button on the maintenance query interface. Then, in the parameter type drop-down menu, they can select the charter flight parameters and set the corresponding charter flight information.

[0096] Charter flight information must include at least the charter flight number, which can be a specific flight number or a range of flight numbers, and may also include the effective time, end time, flight start time, and flight end time.

[0097] S302. Verify the legality of charter flight information.

[0098] To ensure the accuracy of charter flight information and avoid conflicts, it is necessary to verify the legality of charter flight information.

[0099] Optionally, this could involve verifying whether the effective date is later than the current date; verifying whether the flight start time is later than the current date; verifying whether the effective date is empty; or verifying whether the charter flight number is empty.

[0100] S303. Determine whether the charter flight information has passed the legality verification.

[0101] If the charter flight information passes the legality verification, then step S304 is executed.

[0102] S304. Save the charter flight information to the charter flight data cluster.

[0103] Specifically, since the charter flight information includes corresponding times, it is necessary not only to determine whether the target flight number is among the set flight numbers, but also to determine whether the current time is within the range of the corresponding effective time and end time. When both conditions are met, the target flight data field is confirmed as a charter flight. If it is determined that the target flight is a charter flight, step S204 can be executed.

[0104] Optionally, in another embodiment of this application, it may further include:

[0105] If it is determined that the target flight is not a charter flight, then the initial available fares that are only applicable to charter flights are filtered out, and the remaining initial available fares are fed back to the front end.

[0106] Specifically, if the initial available fare is not tied to any charter flight rules, it means that it can be applied to regular flights. Alternatively, if the charter flight rules it is tied to are not limited to charter flights only, it means that it can also be applied to regular flights.

[0107] S204. From the pre-configured rule data cluster, find the applicable rules for each charter flight bound to the initial available fare.

[0108] It should be noted that in this embodiment, multiple applicable rules for charter flights are pre-set and stored in a rule data cluster. Furthermore, when setting the fare for a charter flight, it is necessary to bind an applicable rule for that charter flight based on specific needs. Therefore, the applicable rules for each initially available fare can be retrieved from the pre-configured rule data cluster.

[0109] Optionally, in another embodiment of this application, the method for configuring rule data is as follows: Figure 4 As shown, it includes:

[0110] S401: Respond to the user's charter flight rule creation operation, and obtain the rule application scope information and rule type set by the user.

[0111] The rule types include those applicable to charter flights, applicable only to charter flights, and not applicable to charter flights.

[0112] "Applicable to charter flights" means the fare applies regardless of whether the requested flight number is a charter flight. "Applicable only to charter flights" means it does not apply to regular flights. If the flight is a regular flight at the time of sale, the fare associated with this rule will not apply; it will be filtered out during automatic calculation and cannot be used for subsequent ticketing. This fare is only available when the request is for a charter flight. "Not applicable to charter flights" means it only applies to regular flights. If the flight is a charter flight at the time of sale, the fare associated with this rule will not apply. This fare is only available when the request is for a regular flight.

[0113] Optionally, the rule's scope information may include rule number, effective date, expiry date, advance booking time limit, group size limit, sales time, applicable weekday, code-share airline restrictions, flight number applicable scope, flight number exception scope, flight date applicable scope, flight date exception scope, refund rule number, change rule number, whether it can be sold individually, whether it can be sold in combination, and combination fare restrictions. Furthermore, it can also set restrictions on charter flights, and save configuration information such as airline, creator, creator location, creation time, last updater, last update location, and last update time for easy accountability.

[0114] S402. Based on the user-defined rule scope and rule type, create a rule applicable to charter flights.

[0115] S403. Verify the legality of the rules applicable to the created charter flights.

[0116] It should be noted that the verification of the legality of the applicable rules for charter flights is the same as the verification of the legality of charter flight information, so it will not be elaborated further.

[0117] S404. Determine whether the rules applicable to the created charter flight have passed the legality verification.

[0118] If the rules applicable to the created charter flight pass the legality verification, then step S405 is executed.

[0119] S405. Store the applicable rules for charter flights in the rules data cluster.

[0120] Optionally, in another embodiment of this application, the method for configuring freight rate data is as follows: Figure 5 As shown, it includes:

[0121] S501. Respond to the user's flight fare creation operation and obtain the fare and fare usage scope information of the target flight set by the user.

[0122] Optionally, the fare application information may include route type, cabin class code, fare base, sales effective date, sales end date, travel effective date, travel end date, ticketing effective date, ticketing end date, discount code, origin, destination, sales week, flight number, etc.

[0123] S502. Based on the fare of the target flight and the fare application scope information, create a fare information for the target flight.

[0124] S503. Bind the fare information of the target flight with the applicable rules for the selected charter flight.

[0125] It should be noted that when setting fare information, users also need to select the charter flight usage rules to be bound, so as to bind the fare information of the target flight with the selected charter flight applicable rules. Specifically, it can be bound with the rule number of the charter flight applicable rules.

[0126] S504. Verify the legality of the fare information for the target flight.

[0127] It should be noted that the same principle applies to verifying the legality of fare information for the target flight, so it will not be elaborated here.

[0128] S505. Determine whether the fare information of the target flight has passed the legality verification.

[0129] If the fare information for the target flight passes the validity verification, then step S506 is executed.

[0130] S506. Save the fare information for the target flight.

[0131] S205. Based on the applicable rules for charter flights bound to each initial available fare, filter out each initial available fare that is not applicable to charter flights.

[0132] For example, based on the above example, we obtain 6 initial available fares, and the applicable rules for the charter flights they are bound to are as follows: 01, Charter flight applicable rule: Applicable to charter flights; 02, Charter flight applicable rule: Not applicable to charter flights; 03, Charter flight applicable rule: Applicable only to charter flights; 04, Charter flight applicable rule: Applicable to charter flights; 05, Charter flight applicable rule: Not applicable to charter flights; 06, Charter flight applicable rule: Applicable only to charter flights. Therefore, it is clear that 02 and 05 are not applicable to charter flights among the initial available fares, so they need to be filtered out, and then step S206 should be executed.

[0133] S206. Remove the initial available fares that are not applicable to charter flights to obtain the final available fares.

[0134] Specifically, each initial available fare that is not applicable to charter flights is removed, and the remaining initial available fares are determined as the final available fares, in order to execute step S207.

[0135] S207. Feed back the final available freight rates to the front end.

[0136] This application provides a method for determining charter flight fares, which involves receiving a ticket fare calculation request from a front-end. The ticket fare calculation request includes at least the current passenger's personal information, itinerary information, and the target flight's flight information. Then, based on the current passenger's personal information, itinerary information, and target flight information, initial available fares are matched from pre-configured fare information for the target flight. Based on a pre-configured charter flight data cluster, it is determined whether the target flight is a charter flight. If the target flight is determined to be a charter flight, the applicable rules for charter flights bound to each initial available fare are found from a pre-configured rule data cluster. Based on these applicable rules, initial available fares that are not applicable to charter flights are filtered out. These inapplicable initial available fares are then removed, resulting in final available fares, which are then fed back to the front-end. This method automatically calculates the fares for charter flights that meet passenger travel needs, making the acquisition of charter flight fares more convenient and effectively avoiding errors.

[0137] It should be noted that the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, 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 the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. 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, can 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.

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

[0139] Another embodiment of this application provides a charter flight fare determination device, such as... Figure 6 As shown, it includes:

[0140] The receiving unit 601 is used to receive the airfare calculation request sent by the front end.

[0141] The ticket fare calculation request must include at least the current passenger's personal information, itinerary information, and the flight information of the target flight.

[0142] The initial fare determination unit 602 is used to match each initial available fare from the pre-configured fare information of the target flight based on the current passenger's personal information, itinerary information and the target flight's flight information.

[0143] The judgment unit 603 is used to determine whether the target flight is a charter flight based on a pre-configured charter flight data cluster.

[0144] The rule lookup unit 604 is used to find the applicable rules for each charter flight bound to the initial available fare from the pre-configured rule data cluster when it is determined that the target flight is a charter flight.

[0145] The filtering unit 605 is used to filter out the initial available fares that are not applicable to charter flights based on the applicable rules for each initial available fare.

[0146] Elimination unit 606 is used to eliminate each initial available fare that is not applicable to charter flights to obtain each final available fare.

[0147] The first feedback unit 607 is used to feed back each final available freight rate to the front end.

[0148] Optionally, in another embodiment of this application, the charter flight fare determination device further includes:

[0149] The first response unit is used to respond to the user's charter flight information creation operation and obtain the charter flight information set by the user.

[0150] The first verification unit is used to verify the legality of charter flight information.

[0151] The first storage unit is used to save the charter flight information to the charter flight data cluster when the charter flight information passes the legality verification.

[0152] Optionally, in another embodiment of this application, the charter flight fare determination device further includes:

[0153] The second response unit is used to respond to the user's charter flight rule creation operation and obtain the rule scope information and rule type set by the user. The rule type includes applicable to charter flights, applicable only to charter flights, and not applicable to charter flights.

[0154] The rule creation unit is used to create a rule applicable to a charter flight based on the rule's scope and type set by the user.

[0155] The second verification unit is used to verify the legality of the rules applicable to the created charter flights.

[0156] The second storage unit is used to store the charter flight applicable rules into the rule data cluster when the created charter flight applicable rules pass the legality verification.

[0157] Optionally, in another embodiment of this application, the charter flight fare determination device further includes:

[0158] The third response unit is used to respond to the user's flight fare creation operation and obtain the fare and fare application range information of the target flight set by the user.

[0159] The fare creation unit is used to create fare information for a target flight based on the fare and fare application scope information of the target flight.

[0160] The binding unit is used to bind the fare information of the target flight with the applicable rules of the selected charter flight.

[0161] The third verification unit is used to verify the legality of the fare information for the target flight.

[0162] The third storage unit is used to save the fare information of the target flight when the fare information of the target flight passes the legality verification.

[0163] Optionally, in another embodiment of this application, the charter flight fare determination device further includes:

[0164] The second feedback unit is used to filter out the initial available fares that are only applicable to charter flights when it is determined that the target flight is not a charter flight, and to feed back the remaining initial available fares to the front end.

[0165] It should be noted that the various units provided in the above embodiments of this application may specifically be... Figure 1 The components of the system shown, and the specific working process of each unit, can be referred to the corresponding steps in the above method embodiments, which will not be repeated here.

[0166] Furthermore, the functions of each unit described in the above embodiments can be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that can be used include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SOCs), Complex Programmable Logic Devices (CPLDs), etc.

[0167] Another embodiment of this application provides an electronic device, such as... Figure 7 The diagram illustrates a structural schematic of an electronic device 700 suitable for implementing embodiments of the present disclosure. The electronic device in these embodiments may include, but is not limited to, electronic devices such as desktop computers, laptops, tablets, and vehicle terminals.

[0168] like Figure 7 As shown, the electronic device 700 includes one or more processing devices 701, such as a central processing unit, a graphics processing unit, etc., and a memory 702 on which one or more programs are stored. When one or more programs are executed by one or more processing devices 701, the one or more processing devices 701 implement the charter flight fare determination method provided in any of the above embodiments.

[0169] Alternatively, the electronic device may also include other components, see also [reference needed]. Figure 7The processing device 701, read-only memory 702, and random access memory 703 are interconnected via bus 704. Input / output (I / O) interface 705 is also connected to bus 704. Typically, the following devices can be connected to I / O interface 705: input devices 706 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 707 including, for example, liquid crystal displays, speakers, vibrators, etc.; storage devices 708 including, for example, magnetic tape, hard disks, etc.; and communication devices 709. Communication device 709 allows electronic device 700 to communicate wirelessly or wiredly with other devices to exchange data. Although... Figure 7 An electronic device 700 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.

[0170] Another embodiment of this application provides a computer storage medium for storing a program, which, when executed, implements the charter flight fare determination method as described in any of the preceding claims.

[0171] Computer storage media, including both permanent and non-permanent, removable and non-removable media, can store information using any method or technology. Information can be computer-readable instructions, data structures, program modules, 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.

[0172] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0173] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for determining the fare for charter flights, characterized in that, include: Receive a ticket fare calculation request sent from the front end; wherein the ticket fare calculation request includes at least the current passenger's personal information, itinerary information, and flight information of the target flight; Based on the current passenger's personal information, the itinerary information, and the flight information of the target flight, each initial available fare is matched from the pre-configured fare information of the target flight; Based on a pre-configured charter flight data cluster, determine whether the target flight is a charter flight; If it is determined that the target flight is a charter flight, then the applicable rules for each charter flight bound to the initial available fare are found from the pre-configured rule data cluster. Based on the applicable rules for charter flights bound to each of the initial available fares, filter out the initial available fares that are not applicable to charter flights; Each of the initial available fares that are not applicable to charter flights is removed to obtain the final available fares; The final available freight rates are fed back to the front end; The method further includes: In response to a user's charter flight rule creation operation, the system obtains the rule application scope information and rule type set by the user; wherein, the rule type includes applicable to charter flights, applicable only to charter flights, and not applicable to charter flights; Based on the user-defined rule scope and rule type, create a rule applicable to charter flights; The legality of the rules applicable to the created charter flights shall be verified. If the created charter flight applicable rules pass the legality verification, the charter flight applicable rules will be stored in the rule data cluster.

2. The method according to claim 1, characterized in that, Also includes: In response to the user's charter flight information creation operation, the charter flight information set by the user is obtained; The legality of the charter flight information is verified. If the charter flight information passes the legality verification, the charter flight information will be saved to the charter flight data cluster.

3. The method according to claim 1, characterized in that, Before receiving the airfare calculation request sent by the front end, the process also includes: In response to the user's flight fare creation operation, obtain the fare and fare usage scope information of the target flight set by the user; Based on the fare of the target flight and the fare application scope information, create a fare information entry for the target flight; The fare information of the target flight is linked to the applicable rules for the selected charter flight; The legality of the fare information for the target flight is verified; If the fare information of the target flight passes the validity verification, the fare information of the target flight will be saved.

4. The method according to claim 1, characterized in that, Also includes: If it is determined that the target flight is not a charter flight, then the initial available fares that are only applicable to charter flights are filtered out, and the remaining initial available fares are fed back to the front end.

5. A device for determining the fare of a charter flight, characterized in that, include: A receiving unit is used to receive a ticket fare calculation request sent by the front end; wherein the ticket fare calculation request includes at least the current passenger's personal information, itinerary information, and flight information of the target flight; The initial fare determination unit is used to match each initial available fare from the pre-configured fare information of the target flight based on the current passenger's personal information, the itinerary information, and the flight information of the target flight. The judgment unit is used to determine whether the target flight belongs to a charter flight based on a pre-configured charter flight data cluster. The rule lookup unit is used to find the applicable rules for each charter flight bound to the initial available fare from the pre-configured rule data cluster when it is determined that the target flight belongs to a charter flight. The filtering unit is used to filter out each of the initial available fares that are not applicable to charter flights based on the applicable rules for each of the initial available fares. The elimination unit is used to eliminate each of the initial available fares that are not applicable to charter flights, thereby obtaining each final available fare; The first feedback unit is used to feed back each of the final available fares to the front end; The device further includes: The second response unit is used to respond to the user's charter flight rule creation operation, and to obtain the rule application scope information and rule type set by the user; wherein, the rule type includes applicable to charter flights, applicable only to charter flights, and not applicable to charter flights; The rule creation unit is used to create a rule applicable to a charter flight based on the rule application scope and rule type set by the user. The second verification unit is used to verify the legality of the rules applicable to the charter flight that have been created; The second storage unit is used to store the charter flight applicable rules into the rule data cluster when the created charter flight applicable rules pass the legality verification.

6. The apparatus according to claim 5, characterized in that, Also includes: The first response unit is used to respond to the user's charter flight information creation operation and obtain the charter flight information set by the user; The first verification unit is used to verify the legality of the charter flight information; The first storage unit is used to save the charter flight information to the charter flight data cluster when the charter flight information passes the legality verification.

7. An electronic device, characterized in that, include: One or more processing devices; A memory on which one or more programs are stored; When the one or more programs are executed by the one or more processing devices, the one or more processing devices implement the charter flight fare determination method as described in any one of claims 1 to 4.

8. A computer storage medium, characterized in that, Used to store a program, which, when executed, is used to implement the charter flight fare determination method as described in any one of claims 1 to 4.