Itinerary search method and device, electronic equipment and storage medium

CN116150216BActive Publication Date: 2026-10-09TRAVELSKY TECHNOLOGY LIMITED
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202310032141.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-01-10
Publication Date
2026-10-09
Estimated Expiration
2043-01-10

AI Technical Summary

Benefits of technology

[0032] This disclosure provides a method, apparatus, electronic device, and storage medium for itinerary search. First, rules for itinerary and fare calculation are generated. Then, upon receiving a user request, a target rule matching the user request is determined from the aforementioned rules. The itinerary and fare are calculated using this target rule, and the corresponding results are output. This disclosure enables personalized configuration of itinerary and operational calculations for certain routes in specific markets and channels, and uses the personalized rules to match and calculate with user requests to achieve personalized itinerary search for airlines. Based on this disclosure, airlines can achieve more refined control over itinerary search results, especially during online promotions, allowing for a series of dynamic adjustments to maximize revenue.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116150216B_ABST
    Figure CN116150216B_ABST
Patent Text Reader

Abstract

The present disclosure provides a trip search method, device, electronic equipment and storage medium. Firstly, rules for trip and fare calculation are generated. Then, in the case of receiving a user request, the target rule matched with the user request is determined from the above rules, the trip and fare are calculated based on the target rule, and the corresponding result is output. The present disclosure can realize the personalized configuration of trip and operation calculation for certain routes of specific markets and channels, and realize the personalized trip search of airlines by matching and calculating the personalized configured rules with the user request. Based on the present disclosure, airlines can realize more precise trip search result control, especially when the airlines carry out network promotion, a series of dynamic adjustments can be made to maximize revenue.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of software technology, and more specifically, to a route search method, apparatus, electronic device, and storage medium. Background Technology

[0002] Most travel search products on the market currently provide neutral results. In other words, the search engine calculates the travel itinerary and fares according to its own established rules and returns the results to the user in a predetermined sorting manner. The results returned in this way may not be the results that the airlines expect.

[0003] Therefore, how to enable airlines to personalize itinerary calculations based on their market demands and the search requests of users from different channels has become an urgent problem to be solved at this stage. Summary of the Invention

[0004] In view of this, to solve the above problems, this disclosure provides a route search method, apparatus, electronic device, and storage medium, the technical solution of which is as follows:

[0005] A trip search method, the method comprising:

[0006] Generate rules for trip and fare calculation;

[0007] Upon receiving a user request, a target rule matching the user request is determined from the rules, the trip and fare are calculated using the target rule, and the corresponding result is output.

[0008] Preferably, the rules for generating trip and fare calculations include:

[0009] Responding to rule configuration commands, obtain the sales location information, route information, itinerary conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule to be configured;

[0010] Simulations are performed based on the sales location information, route information, travel conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule to determine the status of each rule, which includes whether it is effective or ineffective.

[0011] Preferably, the step of determining the target rule matching the user request from the rules, calculating the trip and fare using the target rule, and outputting the corresponding result includes:

[0012] Extract the rules that are in an active state from the rules, and determine the matching order according to the priority of the extracted rules;

[0013] The sales location information and flight route information between the user request and the extracted rules are matched sequentially according to the matching order to determine the target rule among the extracted rules that matches the user request;

[0014] If the target rule is not empty, the calculation order is determined according to the priority of the travel conditions in the target rule;

[0015] The trip conditions and fare parameters corresponding to the target rule are calculated sequentially according to the calculation order. The calculation results are then filtered according to the filtering parameters corresponding to the target rule and sorted according to the sorting parameters corresponding to the target rule to output the sorted results.

[0016] Preferably, the step of determining the target rule matching the user request from the rules, calculating the trip and fare using the target rule, and outputting the corresponding result further includes:

[0017] If the target rule is empty, a neutral result is returned.

[0018] A trip search device, the device comprising:

[0019] A personalized configuration frontend is used to generate rules for trip and fare calculations;

[0020] A search engine, upon receiving a user request, determines a target rule from the rules that matches the user request, calculates the trip and fare using the target rule, and outputs the corresponding results.

[0021] Preferably, the personalized configuration front-end is specifically used for:

[0022] Responding to rule configuration commands, obtain the sales location information, route information, itinerary conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule to be configured;

[0023] The search engine is also used for:

[0024] Simulations are performed based on the sales location information, route information, travel conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule to determine the status of each rule, which includes whether it is effective or ineffective.

[0025] Preferably, the search engine used to determine target rules matching the user request from the rules, calculate the trip and fare using the target rules, and output the corresponding results is specifically used for:

[0026] Rules in an active state are extracted from the rules, and the matching order is determined according to the priority of the extracted rules. The sales location information and route information between the user request and the extracted rules are matched sequentially according to the matching order to determine the target rule that matches the user request among the extracted rules. If the target rule is not empty, the calculation order is determined according to the priority of the travel conditions in the target rule. The travel conditions and fare parameters corresponding to the target rule are calculated sequentially according to the calculation order. The calculation results are filtered according to the filtering parameters corresponding to the target rule, and the filtered results are sorted according to the sorting parameters corresponding to the target rule to output the sorted result.

[0027] Preferably, the search engine, used to determine target rules matching the user request from the rules, calculate the trip and fare using the target rules, and output the corresponding results, is further used to:

[0028] If the target rule is empty, a neutral result is returned.

[0029] An electronic device includes: at least one memory and at least one processor; the memory stores an application program, and the processor invokes the application program stored in the memory, the application program being used to implement the trip search method.

[0030] A storage medium storing computer program code, which, when executed, implements the aforementioned route search method.

[0031] Compared to existing technologies, the beneficial effects achieved by this disclosure are as follows:

[0032] This disclosure provides a method, apparatus, electronic device, and storage medium for itinerary search. First, rules for itinerary and fare calculation are generated. Then, upon receiving a user request, a target rule matching the user request is determined from the aforementioned rules. The itinerary and fare are calculated using this target rule, and the corresponding results are output. This disclosure enables personalized configuration of itinerary and operational calculations for certain routes in specific markets and channels, and uses the personalized rules to match and calculate with user requests to achieve personalized itinerary search for airlines. Based on this disclosure, airlines can achieve more refined control over itinerary search results, especially during online promotions, allowing for a series of dynamic adjustments to maximize revenue. Attached Figure Description

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

[0034] Figure 1 A flowchart of the itinerary search method provided in this embodiment of the disclosure;

[0035] Figure 2 A schematic diagram of the structure of the trip search device provided in the embodiments of this disclosure;

[0036] Figure 3 This is a schematic diagram of the interaction of the trip search device provided in the embodiments of this disclosure;

[0037] Figure 4 Signaling flowchart of the trip search method provided in the embodiments of this disclosure;

[0038] Figure 5 A schematic diagram of airline rule settings provided in this embodiment of the disclosure;

[0039] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Detailed Implementation

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

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

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

[0043] 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".

[0044] In recent years, on the one hand, with the rapid development of the online travel market, airlines and agents have gradually established their own online sales systems, and the proportion of online sales has increased year by year. Online booking and ticket purchase have become the first choice for many travelers. Travelers are placing new demands on the timeliness and accuracy of travel information, the convenience and variety of ticketing services, the innovation and diversity of models, and the breadth and depth of travel products. On the other hand, competition in the travel market is becoming increasingly fierce. Airlines within the industry are reducing international routes, resulting in a surplus of production resources such as flights. Airlines are also converging on routes, products, and services. Externally, high-speed rail and other modes of transportation continue to put pressure on airlines, and internet giants that control traffic at the distribution level are constantly squeezing airlines' profit margins. As ticket sales are the most important source of revenue for airlines, they need to provide more refined services.

[0045] Against this backdrop, airlines need to maximize revenue by providing different search results for the same route or market to different users or channels, according to their own market strategies. Especially in recent years, with airlines heavily promoting direct sales, they hope to maintain competitiveness through agency channels while increasing the sales ratio of direct sales channels. This requires airlines to set up different personalized solutions for different users when they search for itineraries or fares, based on their own market strategies.

[0046] Most travel search products on the market currently provide neutral results. In other words, the search engine calculates the travel itinerary and fares according to its own established rules and returns the results to the user in a predetermined sorting manner. The results returned in this way may not be the results that the airlines expect.

[0047] In response, this invention provides airlines with a holistic solution that enables them to perform personalized itinerary calculations based on their market demands and search requests from users across different channels, and to adjust the results appropriately to return them to users in the manner that the airline deems optimal.

[0048] See Figure 1 , Figure 1 This is a flowchart of a trip search method provided in an embodiment of the present disclosure. The trip search method includes the following steps:

[0049] S10 generates rules for trip and fare calculation.

[0050] S20: Upon receiving a user request, determine the target rule that matches the user request from the rules, calculate the trip and fare using the target rule, and output the corresponding results.

[0051] To address the issue that most current itinerary search products on the market provide only neutral results, and to ensure the richness and accuracy of search results, this disclosure integrates existing systems and modules, and proposes the following solution from the perspective of overall solution design:

[0052] Personalized trip management is achieved through front-end configuration, and the data is synchronized to the computing engine in real time. The computing engine receives user requests and returns results to the user according to the personalized configuration.

[0053] See Figure 2 , Figure 2 This is a schematic diagram of the structure of a trip search device provided in an embodiment of this disclosure. The trip search method of this embodiment can be implemented by this trip search device, which includes two parts: a personalized configuration front-end 10 (i.e., a GUI) and a search engine 20 (i.e., a Search Engine). See also Figure 3 , Figure 3 This is an interactive schematic diagram of the trip search device provided in this embodiment of the present disclosure. In practical applications, the two modules, personalized configuration front-end 10 and search engine 20, can synchronize data through REDIS (a kind of in-memory database). One personalized configuration front-end 10 can synchronize data to multiple search engines 20 at the same time. The personalized configuration front-end 10 can create, delete and modify rules for trip and fare calculation in REDIS, while the search engine 20 can read the rules in REDIS.

[0054] Specifically, in this embodiment, through the personalized configuration front-end 10, users can configure the sales location information, route information, itinerary conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule within REDIS, thereby completing the rule creation. Furthermore, through the personalized configuration front-end 10, users can also modify any one or more of the corresponding sales location information, route information, itinerary conditions and fare parameters, filtering parameters, and sorting parameters of a rule already created within REDIS, thereby completing the rule modification. Of course, users can also delete rules already created within REDIS. Thus, the personalized configuration front-end 10 can generate rules for itinerary and fare calculation.

[0055] After obtaining a user request, the search engine 20 can read the rules in REDIS and match the user request with the read rules, including matching sales location information and route information. For the rules that match the user request, i.e. the target rules, it can calculate according to the corresponding itinerary conditions and fare parameters, and then further filter the calculation results according to the corresponding filtering parameters of the target rules. Finally, it sorts the filtered results according to the corresponding sorting parameters of the target rules and outputs the final result.

[0056] In the specific implementation process, step S10, "generating rules for trip and fare calculation," can be performed using the following steps:

[0057] Responding to rule configuration commands, obtain the sales location information, route information, itinerary conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule to be configured;

[0058] Simulations are performed based on the sales location information, route information, travel conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule to determine the status of each rule, including whether it is effective or ineffective.

[0059] See Figure 4 , Figure 4 A signaling flowchart of the trip search method provided in this embodiment of the disclosure. See also: Figure 4 Airlines can personalize the front end 10 (i.e. Figure 4 The GUI allows for personalized configuration of itinerary and fare calculations for specific markets and channels (i.e., setting relevant rules). This includes setting the applicable identity (POS, Point of Sale, sales location information), the applicable route (Market, route information), itinerary conditions and fare parameters, filtering parameters (i.e., setting filtering conditions for results), and sorting parameters (i.e., setting the expected sorting method for results). In addition, when an airline sets multiple rules, the rules can be sorted by priority, and rules with higher priority will be matched first during calculation.

[0060] In response, the personalized configuration front-end 10 obtains the sales location information, route information, itinerary conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule by obtaining the rule's corresponding sales location information, route information, itinerary conditions and fare parameters, filtering parameters, and sorting parameters. After the rules are saved, they are synchronized in real time to the search engine 20 (i.e., the Search Engine, which can be specifically...). Figure 4In Shop Engine, for rules that are not yet enabled, you can use the page's simulation function to perform a mock search and check if the results meet expectations. If they do, you can enable the rule. Once enabled, the search engine will match and apply the rules to the corresponding user requests in real time during its calculations.

[0061] In this embodiment of the disclosure, airlines can set personalized rules through the personalized configuration front-end 10, and after setting the rules, they can perform simulations through the simulation page. See also Figure 5 , Figure 5 This is a schematic diagram illustrating airline rule settings as provided in an embodiment of this disclosure. See also: Figure 5 Airlines can set rule names, applicable origin and destination markets (i.e., route information), applicable sales locations (i.e., sales location information), applicable products, effective date range, rule sequence number (i.e., priority), rule validity, sorting rules (i.e., sorting parameters), and filtering rules (i.e., filtering parameters). Based on this, they can then set itinerary conditions or fare conditions (i.e., itinerary conditions and fare parameters).

[0062] If an airline sets multiple rules, the personalized configuration front-end 10 will assign a default sequence number to each rule based on a default algorithm. The smaller the sequence number, the higher the priority. Airlines can also adjust the sequence numbers of rules in the rule list on the page.

[0063] After setting up the rules, airlines can temporarily save the rules without activating them to confirm that the rules meet expectations, and then proceed to the simulation page to perform a simulation. On the simulation page, airlines fill in the queryer's identity information and query conditions as required, perform the simulation, and then verify the results returned by the simulation to check whether the results meet expectations. When a user performs a simulation, the corresponding query request enters search engine 20. Search engine 20 will load all the rules set by the airline (including effective and ineffective rules), sort them by their sequence number from smallest to largest, and match them one by one. The matching process is the same as the user's request matching process (see "Rule Matching" later), and the calculation process after matching is also the same as the user's request calculation process (see "Rule Calculation" later).

[0064] In addition, in this embodiment of the disclosure, when the search engine 20 receives a request, it processes it according to the following steps:

[0065] Step 1): Applicability assessment. See also... Figure 4 The search engine 20 will preset applicable conditions based on user needs, and for user requests that meet the applicable conditions (i.e., Figure 4For SHOP requests initiated by agents / airlines, the processing flow will continue. For user requests that do not meet the applicable conditions, a neutral result will be returned directly.

[0066] Step 2) Continue to see Figure 4 The search engine determines whether it is a simulation request; if it is a simulation request, it extracts all the rules that have been set by the airline and those that have not been set; if it is not a simulation request, it extracts all the rules that have been set.

[0067] Then, the extracted rules are sorted from high to low priority and read. Further, the user request and the read rules are matched against POS (i.e., matching sales location information) and flight route (i.e., matching flight route information) in sequence. That is, using the flight route information and POS information in the user request, the rules are matched one by one in priority from these two dimensions. For the matched rules, the subsequent processing steps are executed. Otherwise, if no rule is matched, a neutral result is returned directly.

[0068] Step 3): Calculate according to the itinerary settings and fare settings (i.e., itinerary conditions and fare parameters) in the matched rules, and return the results that meet the itinerary conditions and fare conditions.

[0069] It should be noted that the fare options set in the rules include, but are not limited to, whether EOE (End On End, single-segment sum fare) is supported; the itinerary conditions set in the rules include, but are not limited to, flight type, transit information (transit duration and transit point information), airline restrictions, flight number restrictions, CODE SHARE (code-sharing) restrictions, etc.

[0070] It should also be noted that multiple travel conditions can be set. If there are multiple travel conditions, a corresponding rank can be set for each travel condition. The lower the rank, the higher the level, which is the result that the airline most wants to sell. Therefore, it should appear earlier in the final result.

[0071] Step 4): For the calculated result set, filter it according to the filtering conditions (i.e., filtering parameters) corresponding to the rules, sort it according to the sorting options (i.e. sorting parameters), and then return it to the agent / airline.

[0072] In the specific implementation process, step S20, "determine the target rule that matches the user request from the rules, calculate the trip and fare using the target rule, and output the corresponding results," can be implemented using the following steps:

[0073] Extract the rules that are in an active state from the rules, and determine the matching order according to the priority of the extracted rules;

[0074] The sales location information and flight route information between the user request and the extracted rules are matched sequentially in the matching order to determine the target rule among the extracted rules that matches the user request;

[0075] If the target rule is not empty, the calculation order is determined according to the priority of the travel conditions in the target rule;

[0076] The calculations are performed sequentially on the trip conditions and fare parameters corresponding to the target rules. The calculation results are then filtered according to the filtering parameters corresponding to the target rules and sorted according to the sorting parameters corresponding to the target rules, and the sorted results are output.

[0077] In this embodiment, after a user requests access to search engine 20, search engine 20 first performs an applicability judgment based on the airline's preset conditions, i.e., whether the airline allows the user to request personalized calculations. If the user is not allowed to request personalized calculations, search engine 20 directly returns a neutral result. If the user is allowed to request personalized calculations, search engine 20 sorts the effective rules in ascending order of sequence number to determine the matching order. Then, it performs rule matching according to the information in the user request (including matching sales location information and route information). If a matching rule (i.e., the target rule) is found, calculations are performed according to the target rule. Specifically:

[0078] I. Rule Matching:

[0079] The rule matching process is the process of matching the conditions in the user's request with the rules in the system. First, the POS data item of the rule (i.e., matching the sales location information) is matched with the user's identity information in the user's request. If the match is successful, the departure location and arrival location in the user's request are then matched with the departure market (i.e., the origin market) and arrival market (i.e., the destination market) in the rule (i.e., matching the route information).

[0080] 1. POS Matching Process: Table 1 below lists the user identity information in the user request, corresponding to the information configured in the POS data item of the rule:

[0081] Table 1

[0082]

[0083] It should be noted that each rule can define multiple POS data items. These POS data items are arranged in ascending order of weight, which is automatically calculated by the system (the more granular the weight, the lower the weight). POS data items with lower weights are matched first. The matching process is as follows:

[0084] 1) Extract the user's identity information from the user's request;

[0085] 2) Read out the corresponding sales location information (i.e., POS data items) in the rules and sort them by weight from smallest to largest;

[0086] 3) Match the user's requested identity information with the POS data items one by one, according to their weight from smallest to largest:

[0087] If no POS data item is matched, a match failure is returned, and the process continues to match the next rule.

[0088] If a rule with EXCLUDE set to TRUE is matched, the match fails, and the process continues to match the next rule.

[0089] If a rule with EXCLUDE set to FALSE is matched, a successful match is returned, and the matching process continues until the aircraft takes off and reaches the market.

[0090] 2. The process of matching the takeoff market and the arrival market:

[0091] Based on the origin and destination locations in the user's request, the rules are matched against the departure and arrival markets defined in the rules. If both matches are successful, the rule is considered successful and can be used for calculation. Table 2 below lists the regional levels involved in the market definitions:

[0092] Table 2

[0093]

[0094] It should be noted that each rule can define multiple market data items for takeoff and arrival, and each market data item has a weight, which is automatically calculated by the system (the more granular the weight, the lower the weight). The matching process is as follows:

[0095] 1) Based on the user's requested origin, retrieve the associated geographic information of the origin, including Airport, City, State, Country, ATPCO Zone, TC Area, etc.

[0096] 2) According to the rules, read the list of market data items for the departure market, and match the user's requested departure location with the market data items one by one according to the weight from low to high.

[0097] 3) If a market data item in the rule is matched, proceed to step 4);

[0098] If no market data item is matched, the system will return a "match failed" message and continue matching the next rule.

[0099] 4) Based on the destination requested by the user, retrieve the associated geographic information of the destination, including Airport, City, State, Country, ATPCO Zone, TC Area, etc.

[0100] 5) Based on the rules, read the list of market data items for arrival in the market, and match the arrival location in the user request with the market data items one by one according to the weight from low to high;

[0101] 6) If a matching market data item is found, the rule is considered to be successfully matched, and the rule calculation can proceed directly.

[0102] If no matching occurs for any arriving market data item, a matching failure is returned, and the process continues to match the next rule.

[0103] II. Rule Calculation:

[0104] For user requests that do not match any rules, search engine 20 returns a neutral result. In other words, if the target rule is empty, search engine 20 returns a neutral result.

[0105] For user requests that successfully match the target rule: calculations are performed sequentially based on the priority (rank) of the fare parameters and travel conditions in the target rule, starting from priority 1 (rank1):

[0106] 1) Generate flights and corresponding fares sequentially according to the rules, itinerary conditions, and fare parameters;

[0107] 2) Filter flights. If the filtering rule specifies that all direct flights should be returned, then direct flights will not be filtered.

[0108] 3) Within the priority (rank) range, sort the flights according to the sorting rules, starting with the first sorting condition. The sorting dimensions are as follows: If multi-dimensional sorting is defined, sort by the first sorting dimension first; if the data is the same, then sort by the second sorting dimension, and so on. Specific sorting dimensions:

[0109] 3.1) Travel time, from shortest to longest

[0110] Travel time is calculated as the total flight duration of all flights in the SOLUTION (i.e., the flight combinations returned in the results, including prices) plus the total duration of all layovers, sorted from lowest to highest.

[0111] 3.2) Number of transit points, from low to high

[0112] Number of transit points = Total number of flights - 1, sorted from lowest to highest number of transit points.

[0113] 3.3) Price, total price from low to high

[0114] Sort by total solution price, from lowest to highest.

[0115] 3.4) Departure time, from morning to evening

[0116] Departure times are sorted using the departure date and time of the initial flight of the originating segment in the SOLUTION.

[0117] 3.5) Arrival time, from morning to night

[0118] Arrival times are sorted using the arrival date and time of the last segment in the SOLUTION.

[0119] 3.6) ONLINE (connecting flights with the same airline) results are ranked higher.

[0120] For flights in a SOLUTION, if all flights belong to the same market airline, it is considered ONLINE; otherwise, it is considered non-ONLINE, i.e., connecting flights. Connecting flights SOLUTIONs should be listed after ONLINE.

[0121] 3.7) Non-code-sharing should be prioritized.

[0122] For flights in a solution, if all flights belong to the same market carrier and the same airline operating the flights, it is considered a non-codeshare solution; otherwise, it is a codeshare solution. Solutions with codeshare are listed after those without codeshare.

[0123] 3.8) Overall score, from low to high

[0124] During the calculation process, each solution is scored based on various factors and sorted from smallest to largest according to these scores.

[0125] 4) Return the results in ascending order of RANK.

[0126] Based on the above description, the solution proposed in this disclosure can help airlines achieve more refined control over itinerary search results, especially when airlines conduct online promotions, allowing for a series of dynamic adjustments to maximize revenue.

[0127] 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 disclosure. 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.

[0128] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

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

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

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

[0132] Based on the trip search method provided in the above embodiments, this disclosure provides an apparatus for executing the above trip search method, the structural schematic diagram of which is shown below. Figure 2 As shown, it includes:

[0133] The personalized configuration front-end 10 is used to generate rules for trip and fare calculation;

[0134] Search engine 20 is used to determine the target rule that matches the user request from the rules when a user request is received, calculate the trip and fare according to the target rule, and output the corresponding results.

[0135] Optional, personalized configuration of front-end 10, specifically used for:

[0136] Responding to rule configuration commands, obtain the sales location information, route information, itinerary conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule to be configured;

[0137] Search engine 20 is also used for:

[0138] Simulations are performed based on the sales location information, route information, travel conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule to determine the status of each rule, including whether it is effective or ineffective.

[0139] Optionally, a search engine 20 is used to determine target rules from the rules that match the user request, calculate the trip and fare based on the target rules, and output the corresponding results. Specifically, it is used for:

[0140] Extract rules that are in an active state from the rules, and determine the matching order according to the priority of the extracted rules; match the sales location information and route information between the user request and the extracted rules in the order of matching to determine the target rule that matches the user request among the extracted rules; if the target rule is not empty, determine the calculation order according to the priority of the travel conditions in the target rule; calculate the travel conditions and fare parameters corresponding to the target rule in the order of calculation, and filter the calculation results according to the filtering parameters corresponding to the target rule, and sort the filtering results according to the sorting parameters corresponding to the target rule to output the sorted result.

[0141] Optionally, the search engine 20, used to determine target rules from the rules that match the user request, calculate the trip and fare based on the target rules, and output the corresponding results, is also used for:

[0142] If the target rule is empty, a neutral result is returned.

[0143] It should be noted that the detailed configuration functions of the personalized configuration front-end 10 and the search engine 20 in this embodiment can be found in the corresponding disclosure section of the above configuration file verification method embodiment, and will not be repeated here.

[0144] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0145] Based on the trip search method provided in the above embodiments, this disclosure also provides an electronic device, characterized in that the electronic device includes: at least one memory and at least one processor; the memory stores an application program, and the processor calls the application program stored in the memory, the application program being used to implement the trip search method.

[0146] The following is for reference. Figure 6 This diagram illustrates a structural schematic of an electronic device 600 suitable for implementing embodiments of the present disclosure. The terminal devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 6 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0147] like Figure 6 As shown, electronic device 600 may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 601, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 602 or a program loaded from storage device 609 into random access memory (RAM) 603. RAM 603 also stores various programs and data required for the operation of electronic device 600. Processing device 601, ROM 602, and RAM 603 are interconnected via bus 604. Input / output (I / O) interface 605 is also connected to bus 604.

[0148] Typically, the following devices can be connected to I / O interface 605: input devices 606 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 607 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 608 including, for example, magnetic tapes, hard disks, etc.; and communication devices 609. Communication device 609 allows electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 6 An electronic device 600 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.

[0149] Based on the trip search method provided in the above embodiments, this disclosure also provides a storage medium, characterized in that the storage medium stores computer program code, and the computer program code implements the trip search method when executed.

[0150] In the context of this disclosure, a storage medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A storage medium can be a machine-readable signal medium or a machine-readable storage medium. Storage media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0151] It should be noted that the storage medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any storage medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the storage medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0152] The aforementioned storage medium may be included in the aforementioned electronic device; or it may exist independently and not be assembled into the electronic device.

[0153] According to one or more embodiments of this disclosure, a trip search method is provided, comprising:

[0154] Generate rules for trip and fare calculation;

[0155] Upon receiving a user request, a target rule matching the user request is determined from the rules, the trip and fare are calculated using the target rule, and the corresponding result is output.

[0156] According to one or more embodiments of this disclosure, a trip search method is provided to generate rules for trip and fare calculation, including:

[0157] Responding to rule configuration commands, obtain the sales location information, route information, itinerary conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule to be configured;

[0158] Simulations are performed based on the sales location information, route information, travel conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule to determine the status of each rule, which includes whether it is effective or ineffective.

[0159] According to one or more embodiments of this disclosure, a trip search method is provided, which determines target rules matching the user request from the rules, calculates the trip and fare using the target rules, and outputs the corresponding results, including:

[0160] Extract the rules that are in an active state from the rules, and determine the matching order according to the priority of the extracted rules;

[0161] The sales location information and flight route information between the user request and the extracted rules are matched sequentially according to the matching order to determine the target rule among the extracted rules that matches the user request;

[0162] If the target rule is not empty, the calculation order is determined according to the priority of the travel conditions in the target rule;

[0163] The trip conditions and fare parameters corresponding to the target rule are calculated sequentially according to the calculation order. The calculation results are then filtered according to the filtering parameters corresponding to the target rule and sorted according to the sorting parameters corresponding to the target rule to output the sorted results.

[0164] According to one or more embodiments of this disclosure, a trip search method is provided, which determines target rules matching the user request from the rules, calculates the trip and fare using the target rules, and outputs the corresponding results, and further includes:

[0165] If the target rule is empty, a neutral result is returned.

[0166] According to one or more embodiments of this disclosure, a trip search device is provided, comprising:

[0167] A personalized configuration frontend is used to generate rules for trip and fare calculations;

[0168] A search engine, upon receiving a user request, determines a target rule from the rules that matches the user request, calculates the trip and fare using the target rule, and outputs the corresponding results.

[0169] According to one or more embodiments of this disclosure, a trip search device is provided, with a personalized configuration front end, specifically used for:

[0170] Responding to rule configuration commands, obtain the sales location information, route information, itinerary conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule to be configured;

[0171] The search engine is also used for:

[0172] Simulations are performed based on the sales location information, route information, travel conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule to determine the status of each rule, which includes whether it is effective or ineffective.

[0173] According to one or more embodiments of this disclosure, a trip search device is provided, configured to determine target rules matching a user request from the rules, calculate trips and fares using the target rules, and output corresponding results; specifically, the search engine is used for:

[0174] Rules in an active state are extracted from the rules, and the matching order is determined according to the priority of the extracted rules. The sales location information and route information between the user request and the extracted rules are matched sequentially according to the matching order to determine the target rule that matches the user request among the extracted rules. If the target rule is not empty, the calculation order is determined according to the priority of the travel conditions in the target rule. The travel conditions and fare parameters corresponding to the target rule are calculated sequentially according to the calculation order. The calculation results are filtered according to the filtering parameters corresponding to the target rule, and the filtered results are sorted according to the sorting parameters corresponding to the target rule to output the sorted result.

[0175] According to one or more embodiments of this disclosure, a trip search apparatus is provided, configured to determine target rules matching a user request from the rules, calculate trips and fares using the target rules, and output corresponding results from the search engine, further configured to:

[0176] If the target rule is empty, a neutral result is returned.

[0177] According to one or more embodiments of the present disclosure, an electronic device is provided, the electronic device including: at least one memory and at least one processor; the memory stores an application program, and the processor calls the application program stored in the memory, the application program being used to implement a trip search method.

[0178] According to one or more embodiments of the present disclosure, a storage medium is provided that stores computer program code, which, when executed, implements a route search method.

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

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

[0181] 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 route search method, characterized in that, The method includes: Generate rules for trip and fare calculation, and determine the status of each rule, including an effective status or an ineffective status; Upon receiving a user request, determine whether the user request is a simulation request. If so, extract all rules that are in effect and those that are not. Otherwise, extract all rules that are in effect. Sort the extracted rules from highest to lowest priority and read the rules; The user request and the read rules are matched sequentially. This matching includes sales location information matching and route information matching. In the sales location information matching, the corresponding sales location information in the rules is read and sorted by weight from smallest to largest. The weights are automatically calculated by the system, and the more granular the level of the sales location data item, the lower its weight. The user identity information in the user request is matched with the sales location information one by one, from smallest to largest weight. If a match fails, the next rule is matched; if a match succeeds, the departure market and arrival market are matched. The departure market and arrival market matching includes: reading the associated geographical information of the origin based on the user request's origin; reading the market data item list based on the departure market in the rules; and sorting the data by weight. From low to high, the system matches the user's requested departure location with market data items one by one. If no market data item is matched, a matching failure is returned, and the system continues to match the next rule. If a match is successful, the system reads the associated geographic information of the destination based on the user's requested arrival location, reads the list of market data items according to the arrival market in the rule, and matches the user's requested arrival location with market data items one by one according to the weight from low to high. If no arrival market data item is matched, a matching failure is returned, and the system continues to match the next rule. If a match is successful, the rule is considered to be matched successfully, and rule calculation is performed. The associated geographic information includes the airport's three-letter code, the city's three-letter code, the state to which the airport belongs, the country to which the airport belongs, the sub-region to which the airport belongs, the region to which the airport belongs, and the whole world. The system determines the target rule that matches the user request from the rules, calculates the trip and fare based on the target rule, and outputs the corresponding result.

2. The method according to claim 1, characterized in that, The rules for generating trip and fare calculations are then determined, and the status of each rule is determined, including an active or inactive status, including: Responding to rule configuration commands, obtain the sales location information, route information, itinerary conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule to be configured; Simulations are performed based on the sales location information, route information, travel conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule to determine the status of each rule, which includes whether it is effective or ineffective.

3. The method according to claim 2, characterized in that, The step of determining a target rule from the rules that matches the user request, calculating the trip and fare using the target rule, and outputting the corresponding result includes: Extract the rules that are in an active state from the rules, and determine the matching order according to the priority of the extracted rules; The sales location information and flight route information between the user request and the extracted rules are matched sequentially according to the matching order to determine the target rule among the extracted rules that matches the user request; If the target rule is not empty, the calculation order is determined according to the priority of the travel conditions in the target rule; The trip conditions and fare parameters corresponding to the target rule are calculated sequentially according to the calculation order. The calculation results are then filtered according to the filtering parameters corresponding to the target rule and sorted according to the sorting parameters corresponding to the target rule to output the sorted results.

4. The method according to claim 3, characterized in that, The step of determining a target rule matching the user request from the rules, calculating the trip and fare using the target rule, and outputting the corresponding result further includes: If the target rule is empty, a neutral result is returned.

5. A route search device, characterized in that, The device includes: A personalized configuration frontend is used to generate rules for trip and fare calculations; A search engine is used to determine the status of each rule, including whether it is active or inactive. Upon receiving a user request, it determines whether the user request is a simulation request. If so, it extracts all active and inactive rules; otherwise, it extracts all active rules. The extracted rules are sorted from high to low priority, and the rules are read. The user request and the read rules are matched sequentially. The matching includes sales location information matching and route information matching. In the sales location information matching, the corresponding sales location information in the rules is read and sorted from low to high weight. The weight is automatically calculated by the system, and the more granular the level of the sales location data item, the lower its weight. The user identity information in the user request is matched with the sales location information one by one from low to high weight. If the match fails, the next rule is matched. If the match succeeds, the departure market and arrival market are matched. The departure market and arrival market matching includes: reading the origin and destination of the user request. The associated geographic information of the origin is used to read the list of market data items according to the departure market in the rules. The requested departure location is matched one by one with the market data items, ranked from low to high weight. If no market data item is matched, a matching failure is returned, and the process continues to the next rule. If a match is successful, the associated geographic information of the destination is read according to the arrival market in the rules. The requested arrival location is matched one by one with the market data items, ranked from low to high weight. If no arrival market data item is matched, a matching failure is returned, and the process continues to the next rule. If a match is successful, the rule is considered successfully matched, and rule calculation is performed. The associated geographic information includes the airport's three-letter code, city's three-letter code, the state to which the airport belongs, the country to which the airport belongs, the sub-region to which the airport belongs, the major region to which the airport belongs, and the entire world. A target rule matching the user's request is determined from the rules, and the itinerary and fare are calculated using the target rule, with the corresponding results output.

6. The apparatus according to claim 5, characterized in that, The personalized configuration front-end is specifically used for: Responding to rule configuration commands, obtain the sales location information, route information, itinerary conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule to be configured; The search engine is also used for: Simulations are performed based on the sales location information, route information, travel conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule to determine the status of each rule, which includes whether it is effective or ineffective.

7. The apparatus according to claim 6, characterized in that, The search engine, used to determine target rules matching the user request from the rules, calculate the trip and fare using the target rules, and output the corresponding results, is specifically used for: Rules in an active state are extracted from the rules, and the matching order is determined according to the priority of the extracted rules. The sales location information and route information between the user request and the extracted rules are matched sequentially according to the matching order to determine the target rule that matches the user request among the extracted rules. If the target rule is not empty, the calculation order is determined according to the priority of the travel conditions in the target rule. The travel conditions and fare parameters corresponding to the target rule are calculated sequentially according to the calculation order. The calculation results are filtered according to the filtering parameters corresponding to the target rule, and the filtered results are sorted according to the sorting parameters corresponding to the target rule to output the sorted result.

8. The apparatus according to claim 7, characterized in that, The search engine, configured to determine target rules from the rules that match the user request, calculate the trip and fare using the target rules, and output the corresponding results, is further configured to: If the target rule is empty, a neutral result is returned.

9. An electronic device, characterized in that, The electronic device includes: at least one memory and at least one processor; the memory stores an application program, and the processor calls the application program stored in the memory, the application program being used to implement the trip search method according to any one of claims 1-4.

10. A storage medium, characterized in that, The storage medium stores computer program code, which, when executed, implements the route search method according to any one of claims 1-4.

Citation Information

Patent Citations

  • Fare by rule calculation method, device and system

    CN105654338A

  • Information request method and device, server and storage medium

    CN110727699A

  • Data processing method, device and system

    CN115099856A