Freight rate rule generation method and device, medium and product
By employing a multi-level parallel rule engine and verification credentials in the generation of airfare rules, the problem of low efficiency of a single rule engine is solved, and the effect of quickly generating multi-level fare rules is achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CHINA SOUTHERN AIRLINES DIGITAL TECHNOLOGY (GUANGDONG) CO LTD
- Filing Date
- 2026-02-04
- Publication Date
- 2026-05-15
AI Technical Summary
In existing technologies, single rule engines are inefficient in generating and updating airfare rules, and cannot effectively handle the complexity caused by multiple influencing factors and increased data volume, thus affecting the efficiency and timeliness of fare rule generation.
By determining the target propagation path, using a parallel rule engine with multiple rule levels, sub-rules for each rule level are generated based on basic business information. These sub-rules are then combined with target verification credentials to perform hierarchical verification and generate target fare rules.
It improves the efficiency of generating freight rate rules, enabling rapid processing of sub-rules at multiple rule levels, and meeting the timeliness requirements of tiered freight rate deployment.
Smart Images
Figure CN122048431A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of aviation information technology, and in particular to a method, device, medium and product for generating fare rules. Background Technology
[0002] In civil aviation transportation, the determination of airfares has a significant impact on the development of air transport companies. The rules for setting airfares are typically influenced by various factors such as travel date and flight distance, thus necessitating updates to these rules.
[0003] In existing solutions, air transport companies typically use a single rule engine to generate new fare rules when creating and updating them. However, as the types and volume of factors influencing fares continue to increase, solutions using a single rule engine to generate fare rules suffer from low generation efficiency. Summary of the Invention
[0004] This application provides a method, apparatus, medium, and product for generating fare rules, which can improve the efficiency of fare rule generation for air transport companies when generating and updating fare rules.
[0005] Firstly, this application provides a method for generating freight rate rules, including: Obtain basic business information, which is used to indicate data regarding freight rates; Based on basic business information, a target propagation path is determined, which includes at least one rule level. Each rule level is equipped with a corresponding rule engine, which generates sub-rules for the corresponding rule level based on the basic business information. By using the rule engine corresponding to each rule level in the target propagation path, sub-rules about freight rates are obtained for each rule level; Based on the sub-rules concerning freight rates, a target freight rate rule is generated.
[0006] The technical solution provided in this application offers at least the following advantages: By using basic business information to indicate fare rates, a target propagation path including at least one rule level is determined. A target verification credential is generated based on the basic business information. Based on the basic business information and the target verification credential, sub-rules regarding fare rates are generated for each rule level using the rule engine corresponding to each rule level in the target propagation path. Finally, a target fare rate rule is generated based on each sub-rule regarding fare rates. Thus, by using parallel rule engines corresponding to each rule level, multiple sub-rules corresponding to each level can be quickly generated, and a target fare rate rule for determining the fare rate can be generated based on each sub-rule, thereby improving the efficiency of fare rate rule generation.
[0007] One possible implementation involves determining the target propagation path based on fundamental business information, including: Based on the basic business information, target type information is determined. Target type information is used to indicate the data types in the basic business information that affect freight rates. In the path database, retrieve the path type identifier that is the same data type as indicated by the target type information; the path database pre-stores multiple sets of path type identifiers and corresponding path information, and the path information is used to indicate the corresponding propagation path; The target propagation path is determined based on the path type identifier corresponding to the same data type indicated by the target type information.
[0008] Another possible implementation is to obtain the sub-rules about the fare at each rule level through the rule engine corresponding to each rule level in the target propagation path, including: sending the basic business information to the first rule level in the target propagation path, generating the first sub-rule through the rule engine corresponding to the first rule level, and the first sub-rule is used to indicate the fare constraints and sales plan overview; Perform hierarchical validation on the first sub-rule; In response to the successful hierarchical verification, the sub-rules generated by the remaining rule levels in the target propagation path are obtained based on the basic business information and the first sub-rule.
[0009] Another possible implementation is to perform hierarchical verification on the first sub-rule, including: generating a target verification credential based on the basic business information, whereby the target verification credential is used to refer to a globally unique identifier of the basic business information; Based on the target verification credential, hierarchical verification is performed on the first sub-rule.
[0010] Another possible implementation involves obtaining the sub-rules generated from the remaining rule levels in the target propagation path, based on the basic business information and the first sub-rule, including: The basic business information and the first sub-rule are sent to the second rule level in the target propagation path. The rule engine corresponding to the second rule level parses the basic business information and the first sub-rule to generate the second sub-rule. The second sub-rule is used to indicate the fare calculation formula for different dates and flight segments. The basic business information and the second sub-rule are sent to the third rule level in the target propagation path. The rule engine corresponding to the third rule level parses the basic business information and the second sub-rule to generate the third sub-rule. The third sub-rule is used to indicate the flight path filtering rules. The basic business information and the third sub-rule are sent to the fourth rule level in the target propagation path. The rule engine corresponding to the fourth rule level parses the basic business information and the third sub-rule to generate the fourth sub-rule. The fourth sub-rule is used to indicate the agency information of each ticket agent. The basic business information and the fourth sub-rule are sent to the fifth rule level in the target propagation path. The rule engine corresponding to the fifth rule level parses the basic business information and the fourth sub-rule to generate the fifth sub-rule. The fifth sub-rule is used to indicate the supplementary document information about freight rates that needs to be added.
[0011] Another possible implementation involves performing hierarchical verification on the first sub-rule based on the target verification credential, including: determining the existing rule database corresponding to the first rule level based on the target verification credential; wherein the existing rule database pre-stores multiple already generated existing rule instances; In the existing rule database, check if there is an existing rule instance that is the same as the first sub-rule; if no identical existing rule instance is found, confirm that the hierarchical verification passes. If an identical existing rule instance exists, the hierarchical verification fails.
[0012] Secondly, this application provides a fare rule generation apparatus, comprising: The acquisition module is used to acquire basic business information, which is used to indicate data about freight rates. The generation module is used to determine the target propagation path based on basic business information. The target propagation path includes at least one rule level. Each rule level is equipped with a corresponding rule engine, which generates sub-rules for the corresponding rule level based on the basic business information. The generation module is also used to obtain sub-rules about freight rates at each rule level through the rule engine corresponding to each rule level in the target propagation path; The generation module is also used to generate target freight rate rules based on the various sub-rules regarding freight rates.
[0013] Thirdly, this application provides an electronic device comprising: a processor and a memory; the memory storing processor-executable instructions; when the processor is configured to execute the instructions, causing the electronic device to implement the method of the first aspect described above.
[0014] Fourthly, this application provides a computer-readable storage medium comprising: computer software instructions; which, when executed in an electronic device, cause the electronic device to implement the method described in the first aspect.
[0015] Fifthly, this application provides a computer program product comprising a computer program; when the computer program is run in an electronic device, the electronic device performs the method described in the first aspect.
[0016] The beneficial effects of the second to fifth aspects mentioned above are described in the corresponding description of the first aspect and will not be repeated here. Attached Figure Description
[0017] Figure 1 A flowchart illustrating a method for generating freight rate rules provided in an embodiment of this application; Figure 2 A flowchart illustrating another method for generating freight rate rules provided in this application embodiment; Figure 3 A schematic diagram of a system architecture provided for an embodiment of this application; Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application; Figure 5 This is a schematic diagram of the composition of a fare rule generation device provided in an embodiment of this application. Detailed Implementation
[0018] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.
[0019] To facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish the same or similar items with essentially the same function and effect. Those skilled in the art can understand that the terms "first" and "second" are not intended to limit the quantity or execution order.
[0020] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.
[0021] It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.
[0022] In the description of this application, unless otherwise stated, "a plurality of" means two or more.
[0023] With the development of the international civil aviation passenger transport industry, the formulation of tiered fares has affected the operation and development of air transport companies.
[0024] Tiered pricing refers to the refined product design and dynamic pricing of airfares based on anticipated passenger willingness to pay, service levels, and market demand, thereby maximizing total flight revenue.
[0025] The rules for setting tiered fares are usually divided into sub-rules at different rule levels based on different market dimensions such as travel date and flight distance. The sub-rules at different rule levels correspond to different market dimensions regarding fares. These sub-rules at different dimensions together constitute the rules for setting fares that need to be deployed.
[0026] In freight rate management schemes, sub-rules corresponding to each rule level are typically generated based on a single rule engine. However, as the types and volume of factors affecting freight rates continue to increase, the scale of business data that the rule engine needs to process expands, and the number of rule levels increases, making the dependencies and propagation paths between sub-rules more complex.
[0027] As a data processing system, the rule engine takes multi-dimensional real-time market business data as input and outputs specific, executable pricing sub-rules.
[0028] If a single rule engine is still used to generate sub-rules at each rule level, when the market environment in which airlines operate changes, causing multiple factors affecting fares, such as fuel prices or airspace routes, to change simultaneously, and market personnel need to update sub-rules at multiple rule levels, a single rule engine can only process the sub-rules corresponding to the current rule level and cannot process multiple rule levels that have changed at the same time. This reduces the efficiency of generating fare rules and extends the time for fare deployment, failing to meet the timeliness requirements of tiered fare deployment.
[0029] To address the aforementioned technical problems, this application provides a method, apparatus, medium, and product for generating fare rules. It determines a target propagation path including at least one rule level by using basic business information indicating fare details. A target verification credential is generated based on the basic business information. Based on the basic business information and the target verification credential, sub-rules related to fare are generated for each rule level using rule engines corresponding to those rule levels within the target propagation path. Finally, a target fare rule is generated based on these sub-rules. Thus, by using parallel rule engines corresponding to each rule level, multiple sub-rules corresponding to each level can be quickly generated, and a target fare rule for determining the fare allocation can be generated based on these sub-rules, thereby improving the efficiency of fare rule generation.
[0030] The embodiments provided in this application will now be described in detail with reference to the accompanying drawings.
[0031] Figure 1 This is a flowchart illustrating a method for generating freight rate rules, provided as an embodiment of this application. (Combined with...) Figure 1 The present application provides an example of a method for generating freight rate rules.
[0032] S101. Obtain basic business information.
[0033] In some embodiments, basic business information input by back-end personnel is obtained. This basic business information includes data such as the rule-applying unit, the tiered fare calculation framework, fare type, sales date, travel date, and itinerary category.
[0034] S102. Determine the target propagation path based on basic business information.
[0035] In some embodiments, target type information is determined based on business foundation information. This target type information indicates the data type (such as the tiered fare calculation framework and sales date) that affects fares within the business foundation information. The target propagation path is then determined based on the target type information.
[0036] The target propagation path includes at least one rule level, and each rule level is equipped with a corresponding rule engine. The rule engine generates sub-rules for the corresponding rule level based on basic business information.
[0037] For example, in the path database, a path type identifier that is the same as the data type indicated by the target type information is retrieved; wherein, the path database pre-associates and stores multiple sets of path type identifiers and corresponding path information, the path information being used to indicate the corresponding propagation path.
[0038] For example, the target propagation path is determined based on the path information corresponding to the path type identifier that has the same data type as the target type information.
[0039] S103. Obtain the sub-rules about freight rates for each rule level through the rule engine corresponding to each rule level in the target propagation path.
[0040] In some embodiments, after obtaining the target propagation path, the basic business information is propagated along the target propagation path. While the basic business information is propagating along the target propagation path, the rule engine corresponding to each level of rules in the target propagation path generates sub-rules regarding fares for each rule level based on the basic business information.
[0041] For example, in the second rule level used to formulate the price calculation formula, the rule engine corresponding to the second rule level formulates a formula to generate a price calculation framework for a specified date range or flight segment based on the hierarchical fare calculation framework and sales date in the business basic information.
[0042] S104. Generate the target freight rate rule based on each sub-rule concerning freight rate.
[0043] In some embodiments, after obtaining the sub-rules generated by the rule engine corresponding to each rule level, the data format of each sub-rule is uniformly converted into the same preset format. Sub-rules with the same data format are combined to obtain the target fare rule. The target fare rule indicates the fare setting rule corresponding to different dimensional conditions.
[0044] In this embodiment, a target propagation path, including at least one rule level, is determined using basic business information indicating fare details. A target verification credential is generated based on the basic business information. Then, based on the basic business information and the target verification credential, sub-rules related to fare details are generated for each rule level using the rule engine corresponding to each rule level in the target propagation path. Finally, a target fare rule is generated based on these sub-rules. Thus, by using parallel rule engines corresponding to each rule level, multiple sub-rules corresponding to each level can be generated simultaneously, thereby improving the efficiency of fare rule generation.
[0045] Figure 2 This is a flowchart illustrating another method for generating freight rate rules provided in an embodiment of this application. (In conjunction with...) Figure 2 As shown, in step S103 above, obtaining the sub-rules regarding freight rates at each rule level through the rule engine corresponding to each rule level in the target propagation path can be achieved through the following steps: S1031. Distribute basic business information to the first rule level in the target propagation path, and generate the first sub-rule through the rule engine corresponding to the first rule level.
[0046] For example, the first sub-rule serves as the baseline for subsequently generated sub-rules. The first sub-rule indicates the fare constraints and sales program overview. The fare constraints refer to a series of specific rules, such as volume restrictions or route restrictions, that must be met to achieve the target fare set by the marketing personnel. The sales program overview refers to the flight strategy and execution framework developed by the marketing personnel for a specific market or customer group to maximize flight seat revenue, such as the route network, flight schedules, and seat classes offered by low-cost carriers.
[0047] S1032. Perform hierarchical validation on the first sub-rule.
[0048] In some embodiments, after obtaining the first sub-rule, a target verification credential is generated based on the business foundation information. The target verification credential is used to indicate a globally unique identifier of the business foundation information. Based on the target verification credential, hierarchical verification is performed on the first sub-rule.
[0049] For example, based on the target verification credential, a current rule database corresponding to the first rule level is determined; wherein the current rule database pre-stores multiple already generated existing rule instances. In the current rule database, it is searched to see if an existing rule instance identical to the first sub-rule exists.
[0050] For example, in response to the absence of an identical existing rule instance in the existing rule database corresponding to the first rule level, the level verification is confirmed to be successful, and the first sub-rule at this time is stored in the existing rule database corresponding to the first rule level, so as to realize the data update of the existing rule database corresponding to the first rule level.
[0051] For example, in response to the existence of an existing rule instance identical to the one in the existing rule database corresponding to the first rule level, the level verification is confirmed to have failed. When the first sub-rule level verification is confirmed to have failed, an alarm message is generated based on the first sub-rule and pushed to the client corresponding to the backend personnel to remind them to take action.
[0052] For example, during each level of verification, the business basic information will check for uniqueness of information such as sales date / travel date / fare type / tiered fare framework selection, and check for the existence of duplicate existing rule instances. If so, an alert will be issued and the process will be transferred back to the basic information level for adjustment. Because the basic information level will be adjusted during the tiered rule transfer process, it is necessary to check for the existence of duplicate existing rule instances in each level transfer.
[0053] S1033. In response to the successful hierarchical verification, based on the basic business information and the first sub-rule, the remaining rule levels in the target propagation path are generated into sub-rules.
[0054] In some embodiments, after obtaining the first sub-rule and passing the level verification corresponding to the first sub-rule, sub-rules corresponding to the remaining rule levels in the target propagation path are generated based on the first sub-rule and the business basic information.
[0055] For example, the basic business information and the first sub-rule are sent to the second rule level in the target propagation path. The rule engine corresponding to the second rule level parses the basic business information and the first sub-rule to generate the second sub-rule. The second sub-rule is used to indicate the fare calculation formula for different dates and flight segments.
[0056] As one possible implementation, after obtaining the second sub-rule, the existing rule database corresponding to the second rule level is searched to see if there is an existing rule instance that is the same as the second sub-rule, so as to realize the hierarchical verification of the second sub-rule.
[0057] In response to the absence of an identical existing rule instance in the existing rule database corresponding to the second rule level, the corresponding level verification is confirmed to be successful, and the second sub-rule at this time is stored in the existing rule database corresponding to the second rule level, so as to realize the data update of the existing rule database corresponding to the second rule level.
[0058] Specifically, if an existing rule instance with the same name exists in the existing rule database corresponding to the second rule level, the corresponding level verification is confirmed to have failed. Upon confirming that the second sub-rule level verification has failed, an alarm message is generated based on the second sub-rule and pushed to the corresponding client of the backend personnel to remind them to take action.
[0059] For example, the basic business information and the second sub-rule that has passed the hierarchical verification are sent to the third rule level in the target propagation path. The rule engine corresponding to the third rule level parses the basic business information and the second sub-rule to generate the third sub-rule, which is used to indicate the flight path filtering rules.
[0060] In some other embodiments, the third sub-rule may not be related to the second sub-rule in terms of specific content, and each sub-rule may only parse the corresponding basic business information.
[0061] As one possible implementation, the existing rule database corresponding to the third rule level is searched to see if there is an existing rule instance that is the same as the third sub-rule, so as to realize the hierarchical verification of the third sub-rule.
[0062] In response to the absence of an identical existing rule instance in the existing rule database corresponding to the third rule level, the corresponding level verification is confirmed to be successful, and the third sub-rule at this time is stored in the existing rule database corresponding to the third rule level, so as to realize the data update of the existing rule database corresponding to the third rule level.
[0063] Specifically, if an existing rule instance with the same name exists in the existing rule database corresponding to the third rule level, the corresponding level verification is confirmed to have failed. Upon confirming that the third sub-rule level verification has failed, an alarm message is generated based on the third sub-rule and pushed to the corresponding client of the backend personnel to remind them to take action.
[0064] For example, the basic business information and the third sub-rule that has passed the hierarchical verification are sent to the fourth rule level in the target propagation path. The rule engine corresponding to the fourth rule level parses the basic business information and the third sub-rule to generate the fourth sub-rule. The fourth sub-rule is used to indicate the agency information of each ticket agent.
[0065] In some other embodiments, the third and fourth sub-rules may not be related in terms of specific content, and each sub-rule may only parse the corresponding basic business information.
[0066] As one possible implementation, the existing rule database corresponding to the fourth rule level is searched to see if there is an existing rule instance that is the same as the fourth sub-rule, so as to realize the level verification of the fourth sub-rule.
[0067] In response to the absence of an identical existing rule instance in the existing rule database corresponding to the fourth rule level, the corresponding level verification is confirmed to be successful, and the fourth sub-rule at this time is stored in the existing rule database corresponding to the fourth rule level, so as to realize the data update of the existing rule database corresponding to the fourth rule level.
[0068] Specifically, if an existing rule instance with the same name exists in the existing rule database corresponding to the fourth rule level, the corresponding level verification is confirmed to have failed. Upon confirming that the fourth sub-rule level verification has failed, an alarm message is generated based on the fourth sub-rule and pushed to the corresponding client of the backend personnel to remind them to take action.
[0069] For example, the basic business information and the fourth sub-rule that has passed the hierarchical verification are sent to the fifth rule level in the target propagation path. The rule engine corresponding to the fifth rule level parses the basic business information and the fourth sub-rule to generate the fifth sub-rule. The fifth sub-rule is used to indicate the supplementary document information about freight rates that needs to be added.
[0070] In some other embodiments, the fourth and fifth sub-rules may not be related in terms of specific content, and each sub-rule may only parse the corresponding basic business information.
[0071] As one possible implementation, the existing rule database corresponding to the fifth rule level is searched to see if there is an existing rule instance that is the same as the fifth sub-rule, so as to realize the level verification of the fifth sub-rule.
[0072] In response to the absence of an identical existing rule instance in the existing rule database corresponding to the fifth rule level, the corresponding level verification is confirmed to be successful, and the fifth sub-rule at this time is stored in the existing rule database corresponding to the fifth rule level, so as to realize the data update of the existing rule database corresponding to the fifth rule level.
[0073] Specifically, if an existing rule instance with the same name exists in the existing rule database corresponding to the fifth rule level, the corresponding level verification is confirmed to have failed. Upon confirming that the fifth sub-rule level verification has failed, an alarm message is generated based on the fifth sub-rule and pushed to the corresponding client of the backend personnel to remind them to take action.
[0074] In this embodiment of the application, when the rule engine generates sub-rules corresponding to each rule level along the target propagation path, it avoids logical confusion or abnormal behavior caused by rule duplication or version inconsistency by combining the corresponding level verification.
[0075] Figure 3 A schematic diagram of a system architecture provided in this application embodiment includes: a control decision unit 301, an execution unit 302, and a detection and parsing unit 303.
[0076] The control decision unit 301 includes a rule engine corresponding to the first rule level and an existing rule database.
[0077] In some embodiments, the control decision unit 301 generates a first sub-rule by using the rule engine corresponding to the first rule level, based on the business basic information about freight rates input by the back-end personnel, to indicate the constraints on freight rates and an overview of the sales plan. After the first sub-rule level is verified, the business basic information and the first sub-rule are sent to each rule level in the execution unit 102.
[0078] The execution unit 302 includes rule engines and existing rule databases corresponding to the second, third, fourth, and fifth rule levels.
[0079] In some embodiments, based on the business basic information and the first sub-rule issued by the control decision unit 301, the rule engine corresponding to each rule level in the execution unit 302 is used to generate sub-rules for each rule level, such as the second sub-rule for indicating the fare calculation rule, the third sub-rule for defining the flight route screening rule, and the fourth sub-rule for indicating the agency rule of each ticket agent.
[0080] The detection and parsing unit 303 includes a verification engine, which is used to perform hierarchical verification on each sub-rule generated by the rules at each level in the control decision unit 301 or the execution unit 302 before it reaches another rule level. This is done through the verification engine and the existing rule database corresponding to each rule level, thereby preventing the generation of freight rate setting rules from being logically chaotic or abnormal due to repeated contradictions in factor rules.
[0081] It should be noted that the system architecture described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of system architecture, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.
[0082] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device includes: a processor 401, a communication interface 403, and a bus 404. Optionally, the electronic device may further include a memory 402. In specific implementation, Figure 3 The rule engine corresponding to the rule hierarchy of each unit can be used Figure 4 The processor 401 shown is implemented as follows: Figure 3 The existing rule database corresponding to the rule hierarchy of each unit can be centrally stored in Figure 4 In the memory 402 shown.
[0083] Processor 401 may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 401 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 401 may also be a combination implementing computational functions, such as including CPU0 and CPU1.
[0084] The communication interface 403 includes a receiving unit and a transmitting unit, used for connecting with other devices via a communication network. This communication network can be Ethernet, a wireless access network, a wireless local area network (WLAN), etc.
[0085] Memory 402 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage medium or other magnetic storage device, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.
[0086] As one possible implementation, the memory 402 can exist independently of the processor 401. The memory 402 can be connected to the processor 401 via a bus 404 for storage. Figure 3 The existing rule database corresponding to the rule hierarchy of each unit.
[0087] In another possible implementation, the memory 402 can also be integrated with the processor 401.
[0088] Bus 404 is an extended industry standard architecture (EISA) bus, etc. Bus 404 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 4 It is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.
[0089] As can be seen, the above mainly describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, the embodiments of this application provide corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the modules and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this invention.
[0090] This application embodiment can divide the fare rule generation device into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. Optionally, the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.
[0091] In some embodiments, this application also provides a fare rule generation apparatus. The fare rule generation apparatus may include one or more functional modules for implementing the fare rule generation method of the above method embodiments.
[0092] Figure 5 This is a schematic diagram illustrating the composition of a fare rule generation device provided in an embodiment of this application. Figure 5 As shown, the fare rule generation device includes: an acquisition module 501 and a generation module 502.
[0093] The acquisition module 501 is used to acquire basic business information, which is used to indicate data about freight rates.
[0094] The generation module 502 is used to determine the target propagation path based on the basic business information. The target propagation path includes at least one rule level. Each rule level is equipped with a corresponding rule engine, and the rule engine generates sub-rules for the corresponding rule level based on the basic business information.
[0095] The generation module 502 is also used to obtain sub-rules about freight rates at each rule level through the rule engine corresponding to each rule level in the target propagation path.
[0096] The generation module 502 is also used to generate target freight rate rules based on the various sub-rules about freight rates.
[0097] In some embodiments, the generation module 502 is specifically used to determine target type information based on business basic information, wherein the target type information is used to indicate the data type that affects the freight rate in the business basic information; In the path database, retrieve the path type identifier that is the same data type as indicated by the target type information; the path database pre-stores multiple sets of path type identifiers and corresponding path information, and the path information is used to indicate the corresponding propagation path; The target propagation path is determined based on the path type identifier corresponding to the same data type indicated by the target type information.
[0098] In other embodiments, the generation module 502 is specifically used to send basic business information to the first rule level in the target propagation path, and generate a first sub-rule through the rule engine corresponding to the first rule level. The first sub-rule is used to indicate the restrictions on freight rates and an overview of the sales plan. Perform hierarchical validation on the first sub-rule; In response to the successful hierarchical verification, based on the basic business information and the first sub-rule, the remaining rule levels in the target propagation path are generated into sub-rules.
[0099] In some other embodiments, a target verification credential is generated based on the business foundation information. The target verification credential is used to indicate a globally unique identifier of the business foundation information. Based on the target verification credential, hierarchical verification is performed on the first sub-rule.
[0100] In some other embodiments, the generation module 502 is specifically used to send the basic business information and the first sub-rule to the second rule level in the target propagation path, and to parse the basic business information and the first sub-rule through the rule engine corresponding to the second rule level to generate the second sub-rule. The second sub-rule is used to indicate the fare calculation formula for different dates and flight segments. The basic business information and the second sub-rule are sent to the third rule level in the target propagation path. The rule engine corresponding to the third rule level parses the basic business information and the second sub-rule to generate the third sub-rule. The third sub-rule is used to indicate the flight path filtering rules. The basic business information and the third sub-rule are sent to the fourth rule level in the target propagation path. The rule engine corresponding to the fourth rule level parses the basic business information and the third sub-rule to generate the fourth sub-rule. The fourth sub-rule is used to indicate the agency information of each ticket agent. The basic business information and the fourth sub-rule are sent to the fifth rule level in the target propagation path. The rule engine corresponding to the fifth rule level parses the basic business information and the fourth sub-rule to generate the fifth sub-rule. The fifth sub-rule is used to indicate the supplementary document information about freight rates that needs to be added.
[0101] In some other embodiments, the generation module 502 is specifically used to determine the existing rule database corresponding to the first rule level based on the target verification credential; wherein the existing rule database pre-stores multiple already generated existing rule instances; In the existing rule database, search for whether there is an existing rule instance that is the same as the first sub-rule; If no identical existing rule instance exists, the hierarchical validation is confirmed to have passed. If an identical existing rule instance exists, the hierarchical verification fails.
[0102] Through the above description of the implementation methods, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the service calling device can be divided into different functional modules to complete all or part of the functions described above.
[0103] This application also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be executed by computer instructions instructing related hardware. The program can be stored in the aforementioned computer-readable storage medium, and when executed, it can include the processes of the above method embodiments. The computer-readable storage medium can be any of the foregoing embodiments or memory. The aforementioned computer-readable storage medium can also be an external storage device of the aforementioned service invocation device, such as a plug-in hard drive, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the aforementioned service invocation device. Further, the aforementioned computer-readable storage medium can include both internal storage units of the aforementioned service invocation device and external storage devices. The aforementioned computer-readable storage medium is used to store the aforementioned computer program and other programs and data required by the aforementioned service invocation device. The aforementioned computer-readable storage medium can also be used to temporarily store data that has been output or will be output.
[0104] This application also provides a computer program product, which includes a computer program that, when run on a computer, causes the computer to execute any of the fare rule generation methods provided in the above embodiments.
[0105] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A method for generating freight rate rules, characterized in that, include: Obtain basic business information, which is used to indicate data regarding freight rates; Based on the aforementioned business information, a target propagation path is determined, which includes at least one rule level; wherein each rule level is equipped with a corresponding rule engine, and the rule engine generates sub-rules corresponding to the rule level based on the aforementioned business information. By using the rule engine corresponding to each rule level in the target propagation path, sub-rules regarding freight rates are obtained for each rule level; Based on the aforementioned sub-rules regarding freight rates, a target freight rate rule is generated.
2. The method according to claim 1, characterized in that, The determination of the target propagation path based on the aforementioned business information includes: Based on the aforementioned business basic information, target type information is determined, which indicates the data type in the business basic information that affects freight rates; In the path database, a path type identifier that is the same as the data type indicated by the target type information is retrieved; wherein, the path database is pre-associated and stored multiple sets of path type identifiers and corresponding path information, and the path information is used to indicate the corresponding propagation path; The target propagation path is determined based on the path information corresponding to the path type identifier that has the same data type as the target type information.
3. The method according to claim 1, characterized in that, The step of obtaining sub-rules regarding fares for each rule level through the rule engine corresponding to each rule level in the target propagation path includes: The basic business information is sent to the first rule level in the target propagation path. A first sub-rule is generated through the rule engine corresponding to the first rule level. The first sub-rule is used to indicate the restrictions on freight rates and an overview of the sales plan. Perform hierarchical validation on the first sub-rule; In response to the successful hierarchical verification, the sub-rules generated by the remaining rule levels in the target propagation path are obtained based on the basic business information and the first sub-rule.
4. The method according to claim 3, characterized in that, The hierarchical validation of the first sub-rule includes: Based on the aforementioned business basic information, a target verification credential is generated, which is used to indicate a globally unique identifier of the aforementioned business basic information. Based on the target verification credential, the first sub-rule is subjected to hierarchical verification.
5. The method according to claim 3, characterized in that, The sub-rules generated based on the business foundation information and the first sub-rule, to obtain the remaining rule levels in the target propagation path, include: The basic business information and the first sub-rule are sent to the second rule level in the target propagation path. The rule engine corresponding to the second rule level parses the basic business information and the first sub-rule to generate the second sub-rule. The second sub-rule is used to indicate the fare calculation formula for different dates and flight segments. The basic business information and the second sub-rule are sent to the third rule level in the target propagation path. The rule engine corresponding to the third rule level parses the basic business information and the second sub-rule to generate the third sub-rule, which is used to indicate the flight path filtering rule. The basic business information and the third sub-rule are sent to the fourth rule level in the target propagation path. The rule engine corresponding to the fourth rule level parses the basic business information and the third sub-rule to generate the fourth sub-rule. The fourth sub-rule is used to indicate the agency information of each ticket agent. The basic business information and the fourth sub-rule are sent to the fifth rule level in the target propagation path. The rule engine corresponding to the fifth rule level parses the basic business information and the fourth sub-rule to generate the fifth sub-rule. The fifth sub-rule is used to indicate the supplementary document information about freight rates that needs to be added.
6. The method according to claim 4, characterized in that, The step of performing hierarchical verification on the first sub-rule based on the target verification credential includes: Based on the target verification credential, a current rule database corresponding to the first rule level is determined; wherein the current rule database pre-stores multiple instances of existing rules that have already been generated. In the existing rule database, search for whether there is an existing rule instance that is the same as the first sub-rule; If no identical existing rule instance is found, the hierarchical verification is confirmed to be successful. In response to the existence of the same existing rule instance, the hierarchical verification is confirmed to fail.
7. A freight rate rule generation device, characterized in that, include: The acquisition module is used to acquire basic business information, which is used to indicate data about freight rates; A generation module is used to determine a target propagation path based on the business basic information, wherein the target propagation path includes at least one rule level; wherein each rule level is provided with a corresponding rule engine, and the rule engine generates sub-rules corresponding to the rule level based on the business basic information; The generation module is further configured to obtain sub-rules regarding freight rates for each rule level through the rule engine corresponding to each rule level in the target propagation path; The generation module is also used to generate target freight rate rules based on each of the sub-rules regarding freight rates.
8. An electronic device, characterized in that, The device includes a processor and a memory, the processor being coupled to the memory; the memory is used to store computer instructions, which are loaded and executed by the processor to enable the computer device to implement the freight rule generation method as described in any one of claims 1 to 6.
9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer-executable instructions that, when executed on a computer, cause the computer to perform the fare rule generation method as described in any one of claims 1 to 6.
10. A computer program product, characterized in that, The computer program product includes a computer program that, when run on an electronic device, causes the electronic device to perform the fare rule generation method as described in any one of claims 1 to 6.