Stroke search method, device, electronic device, and storage medium

Abstract

The present application provides a stroke search method, device, electronic device, and storage medium, which first generate rules for calculating strokes and fares; and then, upon receiving a user request, determine a target rule from the rules that matches the user request, calculate strokes and fares using the target rule, and output corresponding results. The present application realizes a personalized configuration for stroke and fare calculation for a route in a specific market or channel, and realizes personalized stroke search for airlines by matching and calculating the rules of the personalized configuration with the user request. This application can help airlines achieve more precise control over stroke search results, allowing them to make a series of dynamic adjustments, particularly when airlines are conducting online sales promotions, thereby maximizing revenue.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to a Chinese patent application bearing application number 202310032141.0 and title "Stroke Search Method, Apparatus, Electronic Device and Storage Medium" filed with the China Patent Office on January 10, 2023, the entire contents of which are incorporated herein by reference.

[0002] Technical Field The present application relates to the field of software technology, and more particularly to a stroke search method, device, electronic device, and storage medium. [Background technology]

[0003] Currently, most of the stroke search products on the market provide neutral results, meaning that the search engine calculates strokes and fares according to its own predefined rules, and returns the results to the user according to a predefined sorting method, which is not necessarily what the airline expects. Summary of the Invention [Problem to be solved by the invention]

[0004] In contrast, how airlines can provide personalized stroke calculations for users' search requests across different channels according to their market needs is an issue that needs to be resolved urgently at this stage. [Means for solving the problem]

[0005] In view of this, in order to solve the above problems, the present application provides a stroke search method, device, electronic device and storage medium, and the technical solutions are as follows:

[0006] 1. A stroke search method, the method comprising: generating rules for calculating strokes and fares; When receiving a user request, determining a target rule that matches the user request from the rules, calculating strokes and freight charges according to the target rule, and outputting corresponding results.

[0007] Preferably, said step of generating rules for calculating strokes and fares comprises: In response to a rule configuration command, obtaining sales destination information, route information, stroke conditions and freight parameters, filtering parameters, and sorting parameters corresponding to each rule to be configured; and performing a simulation according to the sales destination information, route information, stroke conditions and freight parameters, filtering parameters, and sorting parameters corresponding to each rule to determine the state of each rule, including an active or inactive state.

[0008] Preferably, the step of determining a target rule that matches the user's request from the rules, calculating strokes and fares according to the target rule, and outputting corresponding results comprises: extracting rules whose status is enabled from the rules, and determining a matching order according to the priority of the extracted rules; Sequentially matching the sales destination information and the route information between the user's request and the extracted rules in the matching order, and determining the target rule that matches the user's request from among the extracted rules; If the target rule is not empty, determining a calculation order according to the priority of stroke conditions in the target rule; The method includes a step of sequentially calculating stroke conditions and fare parameters corresponding to the target rule in the calculation order, filtering the calculation results according to filtering parameters corresponding to the target rule, sorting the filtering results according to sorting parameters corresponding to the target rule, and outputting the sorted results.

[0009] Preferably, the step of determining a target rule that matches the user's request from the rules, calculating strokes and fares according to the target rule, and outputting corresponding results comprises: The method further includes returning a neutral result if the target rule is empty.

[0010] 1. A stroke search device, comprising: A personalized configuration front end for generating rules for calculating strokes and fares; and a search engine for, when receiving a user request, determining a target rule that matches the user request from the rules, calculating strokes and fares according to the target rule, and outputting corresponding results.

[0011] Preferably, said personalization configuration front end specifically comprises: It is used in response to a rule configuration command to obtain the seller information, route information, stroke conditions and freight parameters, filtering parameters, and sorting parameters corresponding to each rule to be configured.

[0012] The search engine Simulations are also performed according to the sales destination information, route information, stroke conditions and freight parameters, filtering parameters, and sorting parameters corresponding to each rule, and are used to determine the state of each rule, including its enabled or disabled state.

[0013] Preferably, the search engine for determining a target rule that matches the user's request from the rules, calculating strokes and fares according to the target rule, and outputting corresponding results specifically comprises: The method is used to extract rules whose status is enabled from the rules, and determine a matching order according to the priority of the extracted rules; sequentially match sales destination information and route information between the user's request and the extracted rules in the matching order, and determine a target rule among the extracted rules that matches the user's request; if the target rule is not empty, determine a calculation order according to the priority of stroke conditions in the target rule; sequentially calculate the stroke conditions and freight parameters corresponding to the target rule in the calculation order, and filter the calculation results according to filtering parameters corresponding to the target rule, sort the filtered results according to sorting parameters corresponding to the target rule, and output the sorted results.

[0014] Preferably, the search engine for determining a target rule matching the user's request from the rules, calculating strokes and fares according to the target rule, and outputting corresponding results comprises: It is also used to return neutral results if the target rule is empty.

[0015] An electronic device comprising: at least one memory in which an application program for implementing the stroke search method is stored; and at least one processor that invokes the application program stored in the memory.

[0016] A storage medium having stored thereon computer program code that, when executed, implements the stroke search method. [Effects of the Invention]

[0017] Compared with the prior art, the beneficial effects achieved by the present invention are as follows: The present application provides a stroke search method, device, electronic device, and storage medium, which first generate rules for calculating strokes and fares; and then, upon receiving a user request, determine a target rule from the rules that matches the user request, calculate strokes and fares using the target rule, and output corresponding results. The present application realizes a personalized configuration for stroke and fare calculation for a route in a specific market or channel, and realizes personalized stroke search for airlines by matching and calculating the rules of the personalized configuration with the user request. This application can help airlines achieve more precise control over stroke search results, allowing them to make a series of dynamic adjustments, particularly when airlines are conducting online sales promotions, thereby maximizing revenue. [Brief explanation of the drawings]

[0018] In order to more clearly describe the technical solutions in the embodiments of the present application or the existing technology, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the existing technology. It is obvious that the accompanying drawings in the following description are only some embodiments of the present application, and those skilled in the art can also obtain other accompanying drawings based on these accompanying drawings without any creative efforts. [Figure 1] 1 is a method flowchart of a stroke search method according to an embodiment of the present application; [Figure 2] 1 is a structural schematic diagram of a stroke search device according to an embodiment of the present application; [Figure 3] FIG. 1 is an interaction diagram of a stroke search device according to an embodiment of the present application. [Figure 4] 1 is a signaling flowchart of a stroke search method according to an embodiment of the present application; [Figure 5] FIG. 2 is a schematic diagram of setting airline rules according to an embodiment of the present application. [Figure 6] 1 is a structural schematic diagram of an electronic device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0019]

[0023] Hereinafter, embodiments of the present application will be described in detail with reference to the accompanying drawings. Although the drawings show several embodiments of the present application, it should be understood that the present application can be realized in various forms and should not be construed as being limited to the embodiments described herein, but rather provided for a more transparent and complete understanding of the present application. It should be understood that the drawings and embodiments of the present application are used only for illustrative purposes and are not used to limit the scope of protection of the present application.

[0020] As used herein, the term "comprises" and variations thereof are intended to be open inclusive, i.e., "including, but not limited to." The term "based on" means "based at least in part on." The term "in one embodiment" means "at least one embodiment," the term "in another embodiment" means "at least one other embodiment," and the term "in some embodiments" means "at least some embodiments." Relevant definitions of other terms are provided below.

[0021] It should be noted that the concepts of "first", "second", etc. referred to in this application are used only to distinguish between different devices, modules, or units, and do not limit the order or interdependence of functions performed by these devices, modules, or units.

[0022] It should be noted that the modifications "a" and "a plurality" referred to in this application are intended to be general rather than limiting and should be understood as "one or more" unless the context clearly indicates otherwise.

[0023] In recent years, 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 been increasing year by year. Online reservations and ticket purchases have become the first choice for many travelers. Passengers are demanding updates in terms of the timeliness and accuracy of travel information, the convenience and richness of ticket purchasing services, the innovativeness and diversity of models, and the breadth and depth of travel products. Meanwhile, competition in the passenger travel market is becoming increasingly fierce, with airlines in the industry reducing their international routes and creating an oversupply of production means such as flights, resulting in airlines' routes, products, and services becoming more and more similar. External transportation options such as high-speed rail continue to put pressure on airlines, and internet giants that control traffic through channels are continuing to squeeze airlines' profit space. Airline ticket sales, the airline's primary source of revenue, require more personalized service.

[0024] Under these circumstances, airlines need to maximize revenue by providing different search results for different users and channels for the same route or market based on their own unique market strategies. In particular, as airlines have focused on improving direct sales in recent years, they want to strengthen the sales ratio of their direct sales channels while maintaining the sales competitiveness of their proxy channels. Therefore, when users perform stroke searches or fare searches, airlines need to be able to provide different personalized plans and different search results for different users based on their own unique market strategies.

[0025] Currently, most of the stroke search products on the market provide neutral results, meaning that the search engine calculates strokes and fares according to its own predefined rules, and returns the results to the user according to a predefined sorting method, which is not necessarily what the airline expects.

[0026] Therefore, this application provides a holistic solution that allows airlines to perform personalized stroke calculations for user search requests across different channels according to their market needs, adjust the results appropriately, and return them to users in a way that the airline deems optimal.

[0027] Please refer to FIG. 1, which is a method flowchart of a stroke searching method according to an embodiment of the present application, which includes the following steps:

[0028] S10, generating rules for calculating strokes and fares;

[0029] S20, when receiving a user request, determine a target rule that matches the user request from the rules, calculate strokes and freight charges according to the target rule, and output the corresponding results.

[0030] To solve the above problem that many of the stroke search products currently on the market give neutral results and ensure richness and accuracy of search results, this application integrates existing systems and modules and proposes the following solution from the perspective of overall solution design.

[0031] Personalized management of strokes is performed through the configuration front end and synchronized in real time with the calculation engine, which receives the user's requests and returns the results to the user in a personalized configuration.

[0032] Referring to FIG. 2, FIG. 2 is a structural diagram of a stroke search device according to an embodiment of the present application. The stroke search method according to the embodiment of the present application may be realized by the stroke search device, which includes two parts: a personalized configuration front end 10 (i.e., GUI) and a search engine 20 (i.e., search engine). Referring to FIG. 3, FIG. 3 is a diagram of interaction between the stroke search device according to the embodiment of the present application. In practical application, data synchronization between the personalized configuration front end 10 and the search engine 20 can be performed through REDIS (memory database), where one personalized configuration front end 10 can synchronize data with multiple search engines 20 simultaneously. The personalized configuration front end 10 can create, delete, and modify rules for calculating strokes and fares in REDIS, and the search engine 20 can read the rules in REDIS.

[0033] Specifically, in this embodiment, the personalization configuration front end 10 allows a user to configure the sales destination information, route information, stroke conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule in REDIS, thereby completing the creation of the rule. The personalization configuration front end 10 also allows a user to modify any one or more of the sales destination information, route information, stroke conditions and fare parameters, filtering parameters, and sorting parameters of the rule created in REDIS, thereby completing the rule modification. Of course, the user can also delete a rule created in REDIS. In this way, the personalization configuration front end 10 can generate rules for calculating strokes and fares.

[0034] After obtaining the user's request, the search engine 20 reads the rules in REDIS, matches the user's request with the read rules, including matching sales location information and route information, and for the rule that matches the user's request, i.e., the target rule, calculates according to the stroke conditions and fare parameters corresponding to the target rule, further filters the calculation result according to the filtering parameters corresponding to the target rule, and finally sorts the filtering result according to the sorting parameters corresponding to the target rule, and outputs the final result.

[0035] In the specific implementation process, step S10 of "generating rules for calculating strokes and fares" is In response to a rule configuration command, obtaining sales destination information, route information, stroke conditions and freight parameters, filtering parameters, and sorting parameters corresponding to each rule to be configured; and performing a simulation according to the sales destination information, route information, stroke conditions and freight parameters, filtering parameters, and sorting parameters corresponding to each rule to determine the state of each rule, including an active or inactive state.

[0036] 4, which is a signaling flowchart of a stroke search method according to an embodiment of the present application. Continuing to refer to FIG. 4, an airline can use the personalization configuration front end 10 (i.e., the GUI in FIG. 4) to configure stroke calculation and fare calculation personalization (i.e., set related rules) for a route in a specific market or channel, including setting the identity (POS, i.e., Point of Sale, point of sale information) to which the rule applies, the route (Market, i.e., route information) to which the rule applies, stroke conditions and fare parameters, filter parameters (setting the result screening conditions), and sort parameters (setting the expected sorting method of the results). Furthermore, if an airline configures multiple rules, the rules can be sorted by priority, and rules with higher priorities will be given priority in matching during calculation.

[0037] In response to the rule configuration command input by the airline, the personalized configuration front end 10 obtains the sales location information, route information, stroke conditions and fare parameters, filtering parameters, and sorting parameters corresponding to each rule, saves the rules, and then synchronizes them with the search engine 20 (i.e., the Search Engine, specifically the Shop Engine in FIG. 4) in real time. For rules that are not enabled, the page's simulation function can be used to perform a simulation search to check whether the results are as expected, and if so, the rules can be enabled. Once a rule is enabled, it is matched in real time during calculation by the search engine 20 and acts on the corresponding user request.

[0038] In an embodiment of the present application, an airline can set personalization rules through the personalization configuration front end 10 and perform a simulation through the simulation page after setting the rules. Referring to FIG. 5, FIG. 5 is a schematic diagram of setting airline rules according to an embodiment of the present application. Still referring to FIG. 5, an airline can set the rule name, the origin market and destination market to which the rule applies (i.e., route information), the sales destination to which the rule applies (i.e., sales destination information), the product to which the rule applies, the effective date range of the rule, the serial number of the rule (i.e., priority), whether the rule is enabled, and the sorting rules (i.e., sorting parameters) and filtering rules (i.e., filtering parameters). Then, the airline can set the stroke conditions or fare conditions (i.e., stroke conditions and fare parameters).

[0039] If an airline configures multiple rules, the personalized configuration front end 10 assigns a default serial number to each rule according to a default algorithm, where the lower the serial number, the higher the priority. The airline adjusts the serial numbers of the rules in the rule list on the page.

[0040] After setting the rules, the airline can temporarily save the rules and proceed to the simulation page to perform a simulation without enabling the rules to verify that the rule settings are as expected. On the simulation page, the airline can enter the identity information of the inquirer and the query conditions as necessary, then perform a simulation, examine the results returned from the simulation, and verify whether the results are as expected. When the user performs a simulation, a corresponding query request is submitted to the search engine 20. The search engine 20 loads all the rules set by the airline (including enabled and disabled rules), sorts them by rule serial number, and matches them one by one. The matching process is the same as the matching process requested by the user (see the following "Rule Matching" for details). The calculation process after matching is also the same as the calculation process requested by the user (see the following "Rule Calculation" for details).

[0041] In addition, in the present embodiment, when the search engine 20 receives a request, it performs the following steps.

[0042] Step 1): Applicability Determination. Continuing to refer to Figure 4, the search engine 20 presets the applicability conditions according to the user's needs, and for the user's request that satisfies the applicability conditions (i.e., the SHOP request initiated by the agent / airline in Figure 4), it continues the processing flow of the next step, and for the user's request that does not satisfy the applicability conditions, it directly returns neutral results.

[0043] Step 2) Continuing to refer to FIG. 4, the search engine 20 determines whether the request is a simulation request, and if so, extracts all valid and invalid rules set by the airline; if not, extracts all valid rules.

[0044] Furthermore, the extracted rules are sorted in descending order of priority and the rules are read; furthermore, the POS is sequentially matched (i.e., matching sales location information) and the route is matched (i.e., matching route information) for the user's request and the read rules, that is, using the route information in the user's request and the POS information in the user's request, matching is performed for each rule in priority from these two dimensions, and for the matched rules, the processing flow of the next step is executed; furthermore, if none of the rules are matched, a neutral result is directly returned.

[0045] Step 3): Calculate based on the stroke settings and fare settings (i.e., stroke conditions and fare parameters) in the matched rules, and return the results that satisfy the stroke conditions and fare conditions.

[0046] The fare options set in the rules include, but are not limited to, whether EOE (i.e., End On End, single-stage fare addition) is supported, etc. The stroke conditions set in the rules include, but are not limited to, flight type, connection information (connection time and connection point information), airline restrictions, flight number restrictions, CODE SHARE restrictions, etc.

[0047] It is possible to set multiple stroke conditions, and if there are multiple stroke conditions, it is also possible to set a rank (RANK) corresponding to each stroke condition.The smaller the RANK, the higher the rank; in other words, since this is the result that the airline is most interested in selling, it should appear higher in the final results.

[0048] Step 4): The calculated result set is filtered based on the screening conditions (i.e., filtering parameters) corresponding to the rules, and sorted according to the sort options (i.e., sort parameters), and then returned to the agent / airline.

[0049] In the specific implementation process, the step S20 of "determining a target rule that matches the user's request from the rules, calculating strokes and freight charges according to the target rule, and outputting the corresponding results" is as follows: extracting rules whose status is enabled from the rules, and determining a matching order according to the priority of the extracted rules; Sequentially matching the sales destination information and the route information between the user's request and the extracted rules in a matching order, and determining a target rule that matches the user's request among the extracted rules; If the target rule is not empty, determining the calculation order according to the priority of the stroke conditions in the target rule; The method may adopt the steps of sequentially calculating the stroke conditions and fare parameters corresponding to the target rule in a calculation order, filtering the calculation results according to the filtering parameters corresponding to the target rule, sorting the filtering results according to the sorting parameters corresponding to the target rule, and outputting the sorted results.

[0050] In the embodiment of the present application, after a user requests access to the search engine 20, the search engine 20 first performs applicability judgment based on the airline's preset conditions, that is, determines whether the airline allows the user to request personalized calculation; if the user is not allowed to request personalized calculation, the search engine 20 directly returns neutral results; if the user is allowed to request personalized calculation, for the user's request, the search engine 20 determines the matching order by sorting the valid rules in ascending order of serial numbers, and then performs rule matching according to the information in the user's request (including matching sales destination information and route information), and if there is a matched rule (i.e., a target rule), it performs calculation based on the target rule. Specifically, it is as follows:

[0051] 1. Rule matching:

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

[0053] 1. POS matching process: The following Table 1 shows the user identity information in the user request and the information configured into the POS data items in the corresponding rule. [Table 1]

[0054] Note that multiple POS data items can be defined for each rule, and the POS data items are sorted in ascending order of weight, which is automatically calculated by the system (the more minute the item, the lower the weight), and POS data items with lower weights are given priority in matching. The matching process is as follows: 1) extracting the user identity information requested by the user; 2) Read the corresponding sales location information (i.e., POS data items) in the rule and sort them in ascending order of weight; 3) Match the user identification information requested by the user with the POS data items one by one in ascending order of weight. If none of the POS data items match, it returns a match failure and continues matching with the next rule. If a rule with EXCLUDE set to TRUE is matched, it returns a match failure and continues matching the next rule. If a rule with EXCLUDE set to FALSE is matched, return a successful match and continue matching takeoff and arrival markets.

[0055] 2. Matching process between takeoff market and arrival market:

[0056] Based on the departure and arrival points in the user's request, the departure market and arrival market defined in the rule are matched, respectively, and if both are successfully matched, it is considered that the rule has been matched successfully and can be calculated using the rule. Table 2 below shows the regional levels related to market definition. [Table 2]

[0057] Each rule can define multiple takeoff and landing market data items, and each market data item has a weight that is automatically calculated by the system (the more detailed the weight, the lower the weight). The matching process is as follows: 1) Based on the departure point requested by the user, retrieve the relevant geographic information of the departure point, including Airport, City, State, Country, ATPCO Zone, TC Area, etc.; 2) Reading the list of market data items based on the take-off market in the rule, and matching the take-off location requested by the user with the market data items one by one from low to high weight; 3) If the market data item in the rule is matched, go to step 4) If none of the market data items match, it returns a match failure directly and continues matching the next rule. 4) Based on the destination requested by the user, retrieve the destination's related geographic information, including Airport, City, State, Country, ATPCO Zone, TC Area, etc.; 5) Reading the list of market data items based on the destination market in the rule, and matching the destination requested by the user with the market data items one by one in order of weight from low to high; 6) If the arrival market data item is matched, the rule matching is considered successful and the rule calculation can be directly entered; If none of the arrival market data items match, a match failure is returned directly and matching continues with the next rule.

[0058] Second, calculation rules:

[0059] The search engine 20 directly returns neutral results for user requests that do not match any of the rules, i.e., if the target rule is empty, the search engine 20 returns neutral results.

[0060] In the case of a user request that has been successfully matched with the target rule: The priority (rank) of the fare parameters and stroke conditions in the target rule is calculated in order, starting from priority 1 (rank1). 1) Generate sequential flights and corresponding fares based on rule stroke conditions and fare parameters; 2) Filter flights and if the filtering rules specify to return all direct flights, do not filter direct flights, 3) Sort the flights within the priority (rank) and filter from the first sorting condition according to the sorting rules. The sorting dimensions are as follows: if multi-dimensional sorting is defined, sort by the first sorting dimension; if the data is the same, sort by the second sorting dimension; thus, the specific sorting dimensions are as follows:

[0061] 3.1) Travel time, shortest first The travel times are the flight times of all flights in the SOLUTION (the flight combinations returned in the results, including prices) plus all intervening layover times, sorted from lowest to highest.

[0062] 3.2) Number of connections, lowest to highest Number of connecting points = total number of flights - 1, sorted in ascending order of number of connecting points.

[0063] 3.3) Lowest price, lowest total price Sort the SOLUTION total price from lowest to highest.

[0064] 3.4) Take-off time, from morning to night The takeoff times are sorted using the takeoff date and takeoff time of the starting flight of the starting flight segment in SOLUTION.

[0065] 3.5) Arrival time, morning to night Arrival times are sorted using the arrival date and time of the last flight segment in the SOLUTION.

[0066] 3.6) Online (same connecting flight on the same airline) results are ranked higher In the case of flights in a SOLUTION, if all flights belong to the same market airline then it is ONLINE, otherwise it is not ONLINE but intermodal, and the intermodal SOLUTION should be ranked after ONLINE.

[0067] 3.7) Non-Code Sharing Top For flights in a SOLUTION, if all flights belong to the same market carrier as the flight's actual carrier, they are considered non-code-shared; otherwise, they are considered code-shared. SOLUTIONS with code-sharing will be ranked after SOLUTIONS without code-sharing.

[0068] 3.8) Overall score, lowest to highest During the calculation process, each SOLUTION is assigned a score based on various factors and then sorted by its score.

[0069] 4) Return the results in descending order of RANK.

[0070] Through the above description, the solution proposed in this application can help airlines achieve more granular control over stroke search results, and can make a series of dynamic adjustments, especially when airlines conduct online sales promotions, thereby maximizing revenue.

[0071] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functions, and operations that may be implemented in accordance with systems, methods, and computer program products according to various embodiments of the present application. In this regard, each block in the flowcharts or block diagrams may represent a module, program segment, or portion of code, which includes one or more executable instructions for implementing a given logical function. In alternative implementations, the functions displayed in the blocks may occur in a different order than that displayed in the accompanying drawings. For example, two blocks shown in succession may actually be executed substantially in parallel or may be executed in the reverse order depending on the functionality involved. Each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented by a dedicated hardware-based system that performs a given function or operation, or by a combination of dedicated hardware and computer instructions.

[0072] The names of messages or information interacted between multiple devices in the embodiments of the present application are used for illustrative purposes only and are not used to limit the scope of these messages or information.

[0073] Although the operations are shown in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown, or sequentially. In some environments, multitasking or parallel processing may be advantageous.

[0074] It should be understood that the steps described in the method embodiments of the present application may be performed in different orders and / or in parallel, and that method embodiments may include additional steps and / or omit performing steps as shown, and the scope of the present application is not limited in this respect.

[0075] Computer program code for carrying out the operations of the present application 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, C++, and even conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may run entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the context of a remote computer, the remote computer may be connected to the user's computer by any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., connected by the Internet using an Internet Service Provider).

[0076] Based on the stroke search method according to the above embodiment, the present invention provides a corresponding apparatus for implementing the stroke search method, the structural diagram of which is shown in FIG. 2, and the apparatus comprises: a personalized configuration front end 10 for generating rules for calculating strokes and fares; and a search engine 20 for, when receiving a user request, determining a target rule that matches the user request from the rules, calculating strokes and fares according to the target rule, and outputting corresponding results.

[0077] Optionally, the personalization configuration front end 10 may specifically: It is used in response to a rule configuration command to obtain the seller information, route information, stroke conditions and freight parameters, filtering parameters, and sorting parameters corresponding to each rule to be configured.

[0078] Search Engine 20 Simulations are also performed according to the sales destination information, route information, stroke conditions and freight parameters, filtering parameters, and sorting parameters corresponding to each rule, and are used to determine the state of each rule, including its enabled or disabled state.

[0079] The search engine 20 for selectively determining a target rule matching the user's request from the rules, calculating strokes and fares according to the target rule, and outputting corresponding results, specifically includes: It is used for: extracting rules whose status is enabled from the rules, and determining a matching order according to the priority of the extracted rules; sequentially matching the sales destination information and route information between the user's request and the extracted rules in the matching order, and determining a target rule among the extracted rules that matches the user's request; if the target rule is not empty, determining a calculation order according to the priority of the stroke conditions in the target rule; sequentially calculating the stroke conditions and freight parameters corresponding to the target rule in the calculation order, and filtering the calculation results according to the filtering parameters corresponding to the target rule, sorting the filtering results according to the sorting parameters corresponding to the target rule, and outputting the sorted results.

[0080] Optionally, a search engine 20 for determining a target rule matching the user's request from the rules, calculating strokes and fares according to the target rule, and outputting corresponding results, It is also used to return a neutral result if the target rule is empty.

[0081] It should be noted that in the embodiment of the present application, the segmentation functions of the personalized configuration front end 10 and the search engine 20 may refer to the disclosure parts corresponding to the embodiment of the configuration file verification method described above, and will not be further described.

[0082] The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), etc.

[0083] Based on the stroke search method according to the above embodiment, an embodiment of the present application further provides an electronic device including at least one memory in which an application program for implementing the stroke search method is stored, and at least one processor that invokes the application program stored in the memory.

[0084] Reference will now be made to Figure 6, which is a structural schematic diagram suitable for realizing an electronic device 600 according to an embodiment of the present application. The terminal devices according to the embodiment of the present application may include, but are not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet personal computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. The electronic device shown in Figure 6 is merely an example and does not limit the functions and scope of use of the embodiment of the present application.

[0085] 6, electronic device 600 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate operations and processes based on programs stored in read-only memory (ROM) 602 or programs loaded from storage device 608 into random access memory (RAM) 603. Various programs and data necessary for operating electronic device 600 are also stored in RAM 603. Processing unit 601, ROM 602, and RAM 603 are connected to each other by bus 604. Input / output (I / O) interface 605 is also connected to bus 604.

[0086] Typically, the following devices can be connected to the I / O interface 605: input devices 606 including, for example, a touchscreen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a liquid crystal display (LCD), speakers, vibrators, etc.; storage devices 608 including, for example, a magnetic tape, hard disk, etc.; and communication devices 609. The communication devices 609 can allow the electronic device 600 to communicate wirelessly or via wires with other devices to exchange data. While FIG. 6 illustrates the electronic device 600 with various devices, it should be understood that it is not required to implement or include all of the devices shown. Alternatively, more or fewer devices can be implemented or included.

[0087] Based on the stroke search method according to the above embodiment, an embodiment of the present application further provides a storage medium having stored thereon a computer program code that, when executed, realizes the stroke search method.

[0088] In the context of this application, a storage medium may be a tangible medium, and may include or store a program for use in or in conjunction with an instruction execution system, device, or appliance. A storage medium may be a machine-readable signal medium or a machine-readable storage medium. A storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or appliance, or any suitable combination of the above. More specific examples of machine-readable storage media include an electrical connection with one or more leads, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0089] It should be noted that the storage medium referred to herein may be a computer-readable signal medium, a computer-readable storage medium, or any combination of the above. The computer-readable storage medium may be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of the computer-readable storage medium may include, but are not limited to, an electrical connection having one or more leads, a portable computer magnetic disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact magnetic disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this application, the computer-readable storage medium may be any tangible medium that contains or stores a program, which can be used by or in combination with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium may include a propagated data signal, either in baseband or as part of a carrier, bearing computer-readable program code. Such a propagated data signal may take multiple forms, including, but not limited to, an electromagnetic signal, an optical signal, or any suitable combination of the above. A computer-readable signal medium may also be any storage medium other than a computer-readable storage medium, which is capable of transmitting, propagating, or transmitting a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained in the storage medium may be transmitted over any suitable medium, including, but not limited to, electrical wire, optical cable, RF (radio frequency), etc., or any suitable combination of the above.

[0090] The storage medium may be included in the electronic device, or may exist independently and not be incorporated into the electronic device.

[0091] According to one or more embodiments of the present application, generating rules for calculating strokes and fares; When receiving a user request, determining a target rule that matches the user request from the rules, calculating strokes and freight charges according to the target rule, and outputting corresponding results.

[0092] According to one or more embodiments of the present application, there is provided a stroke search method, wherein the step of generating rules for calculating strokes and fares includes: In response to a rule configuration command, obtaining sales destination information, route information, stroke conditions and freight parameters, filtering parameters, and sorting parameters corresponding to each rule to be configured; and performing a simulation according to the sales destination information, route information, stroke conditions and freight parameters, filtering parameters, and sorting parameters corresponding to each rule to determine the state of each rule, including an active or inactive state.

[0093] According to one or more embodiments of the present application, a stroke search method is provided, wherein the steps of determining a target rule that matches the user's request from the rules, calculating strokes and fares according to the target rule, and outputting corresponding results include: extracting rules whose status is enabled from the rules, and determining a matching order according to the priority of the extracted rules; Sequentially matching the sales destination information and the route information between the user's request and the extracted rules in the matching order, and determining the target rule that matches the user's request from among the extracted rules; If the target rule is not empty, determining a calculation order according to the priority of stroke conditions in the target rule; The method includes a step of sequentially calculating stroke conditions and fare parameters corresponding to the target rule in the calculation order, filtering the calculation results according to filtering parameters corresponding to the target rule, sorting the filtering results according to sorting parameters corresponding to the target rule, and outputting the sorted results.

[0094] According to one or more embodiments of the present application, a stroke search method is provided, wherein the steps of determining a target rule that matches the user's request from the rules, calculating strokes and fares according to the target rule, and outputting corresponding results include: The method further includes returning a neutral result if the target rule is empty.

[0095] According to one or more embodiments of the present application, A personalized configuration front end for generating rules for calculating strokes and fares; A stroke search device is provided, which includes: a search engine for, when receiving a user request, determining a target rule that matches the user request from the rules, calculating strokes and fares using the target rule, and outputting corresponding results.

[0096] According to one or more embodiments of the present application, there is provided a stroke search device, wherein the personalization configuration front end specifically comprises: It is used in response to a rule configuration command to obtain the seller information, route information, stroke conditions and freight parameters, filtering parameters, and sorting parameters corresponding to each rule to be configured.

[0097] The search engine Simulations are also performed according to the sales destination information, route information, stroke conditions and freight parameters, filtering parameters, and sorting parameters corresponding to each rule, and are used to determine the state of each rule, including its enabled or disabled state.

[0098] According to one or more embodiments of the present application, a stroke search device is provided, wherein the search engine for determining a target rule matching the user's request from the rules, calculating strokes and fares according to the target rule, and outputting corresponding results specifically includes: The method is used to extract rules whose status is enabled from the rules, and determine a matching order according to the priority of the extracted rules; sequentially match sales destination information and route information between the user's request and the extracted rules in the matching order, and determine a target rule among the extracted rules that matches the user's request; if the target rule is not empty, determine a calculation order according to the priority of stroke conditions in the target rule; sequentially calculate the stroke conditions and freight parameters corresponding to the target rule in the calculation order, and filter the calculation results according to filtering parameters corresponding to the target rule, sort the filtered results according to sorting parameters corresponding to the target rule, and output the sorted results.

[0099] According to one or more embodiments of the present application, a stroke search device is provided, wherein the search engine for determining a target rule matching the user's request from the rules, calculating strokes and fares according to the target rule, and outputting corresponding results includes: It is also used to return neutral results if the target rule is empty.

[0100] According to one or more embodiments of the present application, there is provided an electronic device including at least one memory in which an application program for implementing a stroke search method is stored, and at least one processor that invokes the application program stored in the memory.

[0101] According to one or more embodiments of the present application, a storage medium is provided having stored thereon computer program code that, when executed, implements a stroke search method.

[0102] Although the present subject matter has been described in language specific to structural features and / or methodological logic operations, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or operations described above. On the contrary, the specific features and operations described above are merely example forms of implementing the claims.

[0103] Although several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present application. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable subcombination.

[0104] The above description merely describes the preferred embodiments and the operating technical principles of the present application. Those skilled in the art should understand that the scope of the present application is not limited to the technical solution consisting of a specific combination of the above technical features, but should also cover other technical solutions consisting of any combination of the above technical features or their equivalent features without departing from the idea of ​​the present application, such as technical solutions formed by mutually substituting the above features with technical features having similar functions (but not limited to those disclosed in the present application).

Claims

1. generating rules for calculating strokes and fares; When a user request is received, determining a target rule that matches the user request from the rules, calculating strokes and freight using the target rule, and outputting the corresponding result.

2. The step of generating rules for calculating strokes and fares comprises: In response to a rule configuration command, obtaining sales destination information, route information, stroke conditions and freight parameters, filtering parameters, and sorting parameters corresponding to each rule to be configured; and performing a simulation according to the sales destination information, route information, stroke conditions and freight parameters, filtering parameters, and sorting parameters corresponding to each rule to determine the state of each rule, including an active state or an inactive state.

3. The step of determining a target rule that matches the user's request from the rules, calculating strokes and freight charges according to the target rule, and outputting the corresponding results, extracting rules whose status is enabled from the rules, and determining a matching order according to the priority of the extracted rules; Sequentially matching the sales destination information and the route information between the user's request and the extracted rules in the matching order, and determining the target rule that matches the user's request among the extracted rules; If the target rule is not empty, determining a calculation order according to the priority of stroke conditions in the target rule; 3. The stroke search method according to claim 2, further comprising the steps of: sequentially calculating stroke conditions and fare parameters corresponding to the target rule in the calculation order; filtering the calculation results according to filtering parameters corresponding to the target rule; sorting the filtered results according to sorting parameters corresponding to the target rule; and outputting the sorted results.

4. The step of determining a target rule that matches the user's request from the rules, calculating strokes and freight charges according to the target rule, and outputting the corresponding results, 4. The stroke search method of claim 3, further comprising the step of returning a neutral result if the target rule is empty.

5. A personalized configuration front end for generating rules for calculating strokes and fares; a search engine for, when receiving a user's request, determining a target rule that matches the user's request from the rules, calculating strokes and fares using the target rule, and outputting corresponding results.

6. The personalized configuration front end specifically comprises: In response to a rule configuration command, the system is used to obtain sales destination information, route information, stroke conditions and freight parameters, filtering parameters, and sorting parameters corresponding to each configured rule; The search engine The device of claim 5, further comprising: a simulation according to the seller information, route information, stroke conditions and freight parameters, filtering parameters, and sorting parameters corresponding to each rule, which is also used to determine the state of each rule, including an active or inactive state.

7. The search engine for determining a target rule that matches the user's request from the rules, calculating strokes and fares according to the target rule, and outputting corresponding results specifically includes:

7. The device according to claim 6, wherein the device is used for: extracting rules whose status is enabled from the rules, and determining a matching order according to the priority of the extracted rules; sequentially matching sales destination information and route information between the user's request and the extracted rules in the matching order, and determining a target rule among the extracted rules that matches the user's request; if the target rule is not empty, determining a calculation order according to the priority of stroke conditions in the target rule; sequentially calculating stroke conditions and freight parameters corresponding to the target rule in the calculation order, and filtering the calculation results according to filtering parameters corresponding to the target rule, sorting the filtering results according to sorting parameters corresponding to the target rule, and outputting the sorted results.

8. The search engine for determining a target rule that matches the user's request from the rules, calculating strokes and fares according to the target rule, and outputting corresponding results, 8. The apparatus of claim 7, further comprising a step of: returning a neutral result if the target rule is empty.

9. 5. An electronic device comprising: at least one memory for storing an application program for implementing the stroke search method according to claim 1; and at least one processor for calling the application program stored in the memory.

10. A storage medium storing computer program code that, when executed, implements the stroke search method according to any one of claims 1 to 4.

Images