Effective method and device of aviation product rule, electronic equipment and storage medium

Abstract

The invention discloses an aviation product rule effective method and device, electronic equipment and a storage medium, and relates to the field of aviation information processing, and the method comprises the steps: receiving an aviation product rule creation request of a business end, and obtaining aviation product rule information corresponding to a to-be-created target aviation product rule; checking the target aviation product rule on the basis of the aviation product rule information, querying a rule database on the basis of the aviation product code under the condition that the checking is passed, obtaining a historical version of the target aviation product rule, marking version information for the target aviation product rule, and obtaining the target aviation product rule of the current version; and releasing the target aviation product rule of the current version based on the version information of the target aviation product rule. According to the method and the device, the technical problem that in related technologies, when new aviation product rules are published, business personnel need to manually query and excavate old rules in the published state and remove the old rules, and the efficiency is relatively low is solved.

Description

Technical Field

[0001] The present invention relates to the field of aviation information processing or other related technical fields, and in particular to a method for implementing aviation product rules and a device, electronic equipment and storage medium thereof. Background Art

[0002] In the field of civil aviation e-commerce and passenger services, the dynamic adjustment of aviation product rules is the key to responding to market changes, policy updates and emergencies, so as to provide aviation products and services that better meet the needs of passengers. These rules cover multiple dimensions such as the applicable dates of aviation products, passenger types, operating routes, sales channels, price discounts, etc., involving multiple needs of sales strategies, service optimization and compliance management. However, the implementation mechanism of aviation product rules in traditional systems often has certain limitations and risks, which are specifically manifested as follows:

[0003] Limitations of the way aviation product rules come into effect. In the existing civil aviation e-commerce system, the way rules come into effect can be roughly divided into two categories: one is rules that do not require approval, which take effect as soon as they are released after configuration. Although this method is fast and convenient, it lacks an effective control mechanism. Once the rules need to be changed, they must be reconfigured and prioritized. This not only increases the complexity of management, but also during the replacement of old and new rules, there may be multiple conflicting rules in the production environment, resulting in lengthy response messages, increasing the burden on network transmission, and reducing the response speed and efficiency of the system.

[0004] Secondly, rules that require approval can only be published and take effect after approval. During the waiting period for rule approval, the production environment may face a situation where no effective rules are available, which will affect the normal sales of products and may even cause serious sales accidents, damaging passenger experience and airline profits.

[0005] Risks of rule changes and effectiveness. Regardless of the effectiveness method, there is a time difference risk in the process of rule changes and release. The time window between the approval of the new rule and the expiration of the old rule may cause confusion in the effectiveness of the rules in the production environment, affecting the stability and accuracy of the sales process. For example, when the approval process for new rules is long, if the switch between the new and old rules is not smooth, there may be a gap in the sales rules, resulting in the inability to sell the product normally, or a conflict in sales rules, making it difficult for the system to determine which rule should be used for matching and calculation, thereby affecting flight booking, payment and subsequent service provision.

[0006] Due to the limitations in the implementation process of the above rules, when issuing new aviation product rules, business personnel are often required to manually query and mine conflicting old rules and eliminate them, which results in low efficiency.

[0007] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0008] The embodiments of the present invention provide a method for validating aviation product rules and its device, electronic device and storage medium, so as to at least solve the technical problem in the related technology that when new aviation product rules are released, business personnel need to manually query and mine old rules in the released state and eliminate them, which is inefficient.

[0009] According to one aspect of an embodiment of the present invention, a method for validating aviation product rules is provided, comprising: receiving an aviation product rule creation request from a business end, and obtaining aviation product rule information corresponding to a target aviation product rule to be created based on the aviation product rule creation request, wherein the aviation product rule information includes at least: an aviation product name, an aviation product code, a rule code, and rule applicability information; verifying the target aviation product rule based on the aviation product rule information to obtain a verification result; when the verification result indicates that the target aviation product rule has passed the verification, querying a rule database based on the aviation product code in the target aviation product rule information to obtain a historical version of the target aviation product rule, marking version information for the target aviation product rule based on the historical version, and obtaining a current version of the target aviation product rule; publishing the current version of the target aviation product rule based on the version information of the target aviation product rule, so that the current version of the target aviation product rule takes effect, and configuring the rule status of the current version of the target aviation product rule to a published status.

[0010] Optionally, the current version of the target aviation product rules is published based on the version information of the target aviation product rules, and the step of making the current version of the target aviation product rules effective includes: when the version information of the target aviation product rules indicates that the current version of the target aviation product rules is a non-initial version of the target aviation product rules, extracting the target historical version of the target aviation product rules from the historical version, wherein the target historical version is a historical version in a published state; publishing the current version of the target aviation product rules to make the current version of the target aviation product rules effective, and invalidating the target historical version of the target aviation product rules at the time point when the current version of the target aviation product rules takes effect, wherein invalidating the target historical version ensures that there is only one published version of the target aviation product rules at the same time point.

[0011] Optionally, the target aviation product rules are published based on the version information of the target aviation product rules, and the step of making the target aviation product rules effective includes: when the version information of the target aviation product rules indicates that the version of the target aviation product rules is the initial version under the target aviation product, the target aviation product rules are published to make the target aviation product rules effective.

[0012] Optionally, the aviation product rule information also includes rule review requirements. After obtaining the current version of the target aviation product rules, it also includes: generating the current version of the target aviation product rules, and obtaining the rule review requirements of the target aviation product rules; when the rule review requirements indicate that the target aviation product rules need to be reviewed, sending the current version of the target aviation product rules to the review end, and receiving the review results returned by the review end.

[0013] Optionally, after receiving the audit result returned by the audit end, it also includes: when the audit result indicates that the current version of the target aviation product has passed the audit, configuring the rule status of the current version of the target aviation product rules to a saved state and waiting for the target aviation product rules to take effect; when the audit result indicates that the current version of the target aviation product has not passed the audit, configuring the rule status of the current version of the target aviation product rules to a saved state, and returning the current version of the target aviation product rules to the business end for modification by the business end.

[0014] Optionally, after making the current version of the target aviation product rules effective, it also includes: receiving an aviation product rule query request from a user terminal, and obtaining a query field based on the aviation product rule query request; querying the rule database based on the query field to obtain M aviation product rules, where M is a positive integer; screening the M aviation product rules based on the rule status of the M aviation product rules to obtain the aviation product rules that meet the user's needs, and pushing the aviation product rules that meet the user's needs to the user terminal.

[0015] Optionally, the step of verifying the target aviation product rules based on the aviation product rule information includes: verifying the required fields of the aviation product rule information based on the required field rule to obtain the required field verification result; verifying the compliance of the aviation product rule information based on the field compliance rule to obtain the compliance verification result; and obtaining the verification result of the target aviation product rules based on the required field verification result and the compliance verification result.

[0016] According to another aspect of an embodiment of the present invention, there is also provided an apparatus for validating aviation product rules, comprising: a receiving unit, configured to receive an aviation product rule creation request from a business end, and to obtain aviation product rule information corresponding to a target aviation product rule to be created based on the aviation product rule creation request, wherein the aviation product rule information includes at least: an aviation product name, an aviation product code, a rule code, and rule applicability information; a verification unit, configured to verify the target aviation product rule based on the aviation product rule information to obtain a verification result; an acquisition unit, configured to query a rule database based on the aviation product code in the target aviation product rule information when the verification result indicates that the target aviation product rule has passed the verification, obtain a historical version of the target aviation product rule, mark version information for the target aviation product rule based on the historical version, and obtain a current version of the target aviation product rule; and an effectiveness unit, configured to publish the current version of the target aviation product rule based on the version information of the target aviation product rule, so that the current version of the target aviation product rule takes effect, and configure the rule status of the current version of the target aviation product rule to a published status.

[0017] Optionally, the effectiveness unit includes: a first extraction module, used to extract a target historical version of the target aviation product rule from the historical version when the version information of the target aviation product rule indicates that the current version of the target aviation product rule is a non-initial version of the target aviation product rule, wherein the target historical version is a historical version in a published state; a first publishing module, used to publish the current version of the target aviation product rule to make the current version of the target aviation product rule effective, and invalidate the target historical version of the target aviation product rule at the time point when the current version of the target aviation product rule takes effect, wherein invalidating the target historical version ensures that there is only one published version of the target aviation product rule at the same time point.

[0018] Optionally, the effectiveness unit includes: a second publishing module, used to publish the target aviation product rule to make the target aviation product rule effective when the version information of the target aviation product rule indicates that the version of the target aviation product rule is an initial version under the target aviation product.

[0019] Optionally, the device for making the aviation product rules effective further includes: a first generating module, used to generate the current version of the target aviation product rules and obtain the rule review requirements of the target aviation product rules; a first sending module, used to send the current version of the target aviation product rules to the review end when the rule review requirements indicate that the target aviation product rules need to be reviewed, and receive the review results returned by the review end.

[0020] Optionally, the device for making the aviation product rules effective further includes: a first configuration module, for configuring the rule status of the current version of the target aviation product rules to a saved state and waiting for the target aviation product rules to take effect when the audit result indicates that the current version of the target aviation product has passed the audit; and a second configuration module, for configuring the rule status of the current version of the target aviation product rules to a saved state and returning the current version of the target aviation product rules to the business end for modification by the business end when the audit result indicates that the current version of the target aviation product has not passed the audit.

[0021] Optionally, the aviation product rule validation device also includes: a first receiving module, used to receive an aviation product rule query request from a user terminal, and obtain a query field based on the aviation product rule query request; a first query module, used to query the rule database based on the query field to obtain M aviation product rules, where M is a positive integer; a first screening module, used to screen the M aviation product rules based on the rule status of the M aviation product rules to obtain the aviation product rules that meet the user's needs, and push the aviation product rules that meet the user's needs to the user terminal.

[0022] Optionally, the verification unit includes: a first verification module, used to verify the required fields of the aviation product rule information based on the required field rules to obtain the required field verification results; a second verification module, used to verify the compliance of the aviation product rule information based on the field compliance rules to obtain the compliance verification results; a second acquisition module, used to obtain the verification results of the target aviation product rules based on the required field verification results and the compliance verification results.

[0023] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium includes a stored computer program, wherein when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute any one of the above-mentioned methods for implementing aviation product rules.

[0024] According to another aspect of an embodiment of the present invention, an electronic device is further provided, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method for implementing any one of the above-mentioned aviation product rules.

[0025] In the present application, the following steps are performed: receiving an aviation product rule creation request from a business end, and obtaining aviation product rule information corresponding to a target aviation product rule to be created based on the aviation product rule creation request, wherein the aviation product rule information includes at least: aviation product name, aviation product code, rule code, and rule applicability information; and verifying the target aviation product rule based on the aviation product rule information to obtain a verification result; when the verification result indicates that the target aviation product rule has passed the verification, querying a rule database based on the aviation product code in the target aviation product rule information to obtain a historical version of the target aviation product rule, marking version information for the target aviation product rule based on the historical version, and obtaining the current version of the target aviation product rule; publishing the current version of the target aviation product rule based on the version information of the target aviation product rule, making the current version of the target aviation product rule effective, and configuring the rule status of the current version of the target aviation product rule to be a published status.

[0026] In the present application, multiple product rules for aviation products are marked by version information. When the business end creates the target aviation product rule, the database is queried by the aviation product code to obtain the historical version of the target aviation product rule. Based on the historical version, the historical version is invalidated while the target aviation product rule is taking effect, so that only one version of the aviation product rule is valid at the same time, thereby achieving the purpose of automatically switching between old and new rules and eliminating the time difference in the effectiveness of the rules. The technical effect of seamless switching between old and new rules and improving the processing efficiency of old rules is achieved, avoiding the abnormal sales of aviation products caused by the time difference in the effectiveness of the rules, and thus solving the technical problem in the related technology that when publishing new aviation product rules, business personnel need to manually query and mine the old rules in the published state and eliminate them, which is inefficient. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0028] Figure 1 is a flow chart of an optional method for validating aviation product rules according to an embodiment of the present invention;

[0029] Figure 2is a schematic diagram of an optional process for taking effect of aviation product rules according to an embodiment of the present invention;

[0030] Figure 3 is a schematic diagram of an optional aviation product rule validation device according to an embodiment of the present invention;

[0031] Figure 4 The present invention is a hardware structure block diagram of an electronic device (or mobile device) for executing a method for validating aviation product rules according to an embodiment of the present invention. DETAILED DESCRIPTION

[0032] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0033] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0034] It should be noted that the method and device for validating aviation product rules in the present application can be used in the field of aviation information processing when the aviation product rules are validated based on version data, and can also be used in any field other than the field of aviation information processing when the aviation product rules are validated based on version data. The present application does not limit the application field of the method and device for validating aviation product rules.

[0035] It should be noted that the relevant information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with the relevant laws, regulations and standards of the relevant regions, take necessary confidentiality measures, do not violate public order and good customs, and provide corresponding operation entrances for users to choose to authorize or refuse. For example, an interface is set up between this system and relevant users or organizations. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or organization through the interface, and obtain relevant information after receiving the consent information fed back by the aforementioned user or organization.

[0036] It should be noted that in this application, when collecting and analyzing customer information, corresponding operation entrances are provided for users to choose to agree or reject the automated decision-making results; if the user chooses to reject, the expert decision-making process will be entered.

[0037] The following embodiments of the present invention can be applied to various aviation product rule effectiveness systems / applications / devices. The present invention proposes a strategy to eliminate the time difference in the effectiveness of aviation product rules through multiple versions. The rules that are effective in production will not be affected by the approval process of new rules. When the new rules that have been approved are released and take effect, the old rules are automatically terminated, so as to achieve seamless switching between the new and old rules in production, improve the processing efficiency of the new and old rules, and avoid the confusion in aviation product sales caused by the time difference between the effectiveness and expiration of the new and old rules.

[0038] The present invention is described in detail below in conjunction with various embodiments.

[0039] Embodiment 1

[0040] According to an embodiment of the present invention, an embodiment of a method for implementing aviation product rules is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0041] Figure 1 1 is a flowchart of an optional method for validating aviation product rules according to an embodiment of the present invention. The implementation subject of the method for validating aviation product rules is an effective system for aviation product rules. Figure 1 As shown, the method for the effectiveness of the aviation product rules includes the following steps:

[0042] Step S101, receiving an aviation product rule creation request from a business end, and acquiring aviation product rule information corresponding to a target aviation product rule to be created based on the aviation product rule creation request.

[0043] With the rise of aviation e-commerce technology, the innovation and optimization of aviation products have become the core elements to enhance passenger experience and airline competitiveness. With the in-depth application of the Internet and big data technology, aviation e-commerce is not limited to online ticket purchases, but has expanded to a full range of passenger services such as personalized additional services, flight dynamic tracking, and intelligent recommendations. However, as aviation product rules become increasingly complex and changeable, how to efficiently manage these rules and ensure that the rules can respond quickly and be accurately implemented in the ever-changing market and policy environment has become a major challenge in the development of aviation e-commerce technology.

[0044] Aviation product rules are the bridge between airlines' operating strategies and passenger service experience. Aviation product rules include various restrictions and preferential terms in the sales process of aviation products, such as flight schedules, fares, baggage policies, refund and change rules, etc. As airlines pursue more refined operational management and passengers' personalized needs grow, the frequency of product rule adjustments has increased significantly. From responding to holiday promotions to flight adjustments due to sudden weather events, the real-time and accuracy of the rules have become the key. However, traditional product rule management methods often have delays or conflicts when rules are changed and take effect, which not only affects passengers' booking experience, but may also cause economic losses to airlines.

[0045] By introducing a multi-version rule management mechanism, the embodiment of the present invention enables the aviation e-commerce system to achieve rapid approval, seamless update and immediate effectiveness of rules, effectively solving the problem of time difference in rule effectiveness. This technology not only improves the efficiency of rule management, but also enhances system stability and the response speed of passenger services. For example, when an airline's operating strategy needs to be adjusted, business personnel can quickly create a new version of the rules. After approval, the system automatically invalidates the old rules and publishes new rules to ensure that passengers can obtain the latest rule information in a timely manner when inquiring about products, avoiding sales accidents caused by delayed rule updates.

[0046] When the business end needs to create a new aviation product rule, the configuration information of the aviation product rule is pre-configured and an aviation product rule creation request is generated, which is then sent to the aviation product rule effectiveness system to the rule verification module. The system can obtain the target aviation product rule to be created and the corresponding aviation product rule-related information by parsing the aviation product rule creation request, which may include: aviation product name, aviation product code, rule code, and rule applicability information. The aviation product name and aviation product code are identifiers used to distinguish different rules. Different versions of the same aviation product rule correspond to different rule codes. The rule applicability information is used to limit the use conditions of the aviation product rule, such as the airports to which the rule applies, the routes to which the rule applies, the rule type, etc.

[0047] Step S102: verify the target aviation product rules based on the aviation product rule information to obtain a verification result.

[0048] It should be noted that the rule verification module can perform preliminary verification on the newly created target aviation product rules to ensure rule compliance, logical consistency and data accuracy. It involves checking the rule content and also covers the verification of rule structure and field integrity. If the verification fails, the target aviation product rules will be returned to the business end for modification to improve the efficiency of aviation product rule creation.

[0049] Optionally, the step of verifying the target aviation product rules based on the aviation product rule information includes: verifying the required fields of the aviation product rule information based on the required field rule to obtain the required field verification result; verifying the compliance of the aviation product rule information based on the field compliance rule to obtain the compliance verification result; and obtaining the verification result of the target aviation product rules based on the required field verification result and the compliance verification result.

[0050] It should be noted that when verifying the target aviation product rules, it mainly includes two parts of content verification: mandatory fields and field compliance. The mandatory field verification is intended to verify whether all required fields in the aviation product rule information have been completed to ensure the integrity and operability of the rules. The system will check the mandatory fields in the aviation product rule information one by one, including but not limited to the aviation product name, aviation product code, rule code, rule applicability information, etc., to ensure that all key information is not missing; when the mandatory fields are completed, the compliance of the aviation product rule information also needs to be verified, including: each field assignment must comply with the predefined format and range, for example, the date field should use the correct date format, and the provided date range should not have logical errors, such as the start date is later than the end date. When the mandatory field verification results and compliance verification results of the target aviation product rules are both verified, the target aviation product rules pass the verification.

[0051] Step S103, when the verification result indicates that the target aviation product rule has passed the verification, query the rule database based on the aviation product code in the target aviation product rule information, obtain the historical version of the target aviation product rule, mark the version information of the target aviation product rule based on the historical version, and obtain the current version of the target aviation product rule.

[0052] For target aviation product rules that have passed verification, the system will update their rule status to "saved status" and wait for subsequent approval or direct release (for rules that do not require approval); for rules that have not passed verification, they will be returned to the business end for modification, and the business end will be prompted to modify the information to prevent non-compliant rules from entering the production environment.

[0053] It should be noted that the rule status can represent the current status of the aviation product rules, which is specifically divided into "saved status", "pending approval status", "approved status" and "published status". Only the "published status" will enter the production environment and be queried and purchased by users for related aviation products.

[0054] Optionally, the aviation product rule information also includes rule review requirements. After obtaining the current version of the target aviation product rules, it also includes: generating the current version of the target aviation product rules, and obtaining the rule review requirements of the target aviation product rules; when the rule review requirements indicate that the target aviation product rules need to be reviewed, sending the current version of the target aviation product rules to the review end, and receiving the review results returned by the review end.

[0055] It should be noted that for the newly created target aviation product rules, the rule review requirements carried in the aviation product rule information are used to determine whether the rule needs to be reviewed. The review process is a stricter business review based on the initial verification, which is related to the airline's rule management strategy, etc. It focuses on whether the field values ​​in the aviation product rule information meet specific business logic and compliance requirements, and checks whether the rule application information is consistent with the airline's business strategy and operation process. For example, for specific passenger types (such as children and the elderly), the preferential policies in the rules should match the existing policies of the airline to avoid compliance conflicts and ensure that the various provisions in the aviation product rule information comply with industry standards and internal policies of the airline. For example, the fare setting should comply with the airline's pricing strategy and should not violate the Consumer Rights Protection Law, etc. Business review can be performed on the review end. Therefore, for aviation product rules that need to be reviewed, the target aviation product rules need to be sent to the review end, and the review results returned by the review end are received. Only after the review is passed can they be released.

[0056] Optionally, after receiving the audit result returned by the audit end, it also includes: when the audit result indicates that the current version of the target aviation product has passed the audit, configuring the rule status of the current version of the target aviation product rules to a saved state and waiting for the target aviation product rules to take effect; when the audit result indicates that the current version of the target aviation product has not passed the audit, configuring the rule status of the current version of the target aviation product rules to a saved state, and returning the current version of the target aviation product rules to the business end for modification by the business end.

[0057] It should be noted that when the audit result returned by the audit end indicates that the target aviation product rules have passed the audit, the rule status of the target aviation product rules will be configured as a saved status, waiting for the target aviation product rules to take effect. Although the rules in the saved status are compliant and accurate, they still need to wait for subsequent publishing operations to take effect. On the contrary, if the audit result indicates that the target aviation product has not passed the audit, the system will return it to the business end, and the business end can modify it to meet the audit requirements, and then review the modified aviation product rules again.

[0058] It should be noted that, if the target aviation product rules have passed the review, the rule database should be queried according to the aviation product code of the target aviation product rules to obtain the historical version of the target aviation product, determine whether there are old rules corresponding to the aviation product currently in operation, and avoid system confusion and sales accidents caused by the simultaneous operation of new and old rules based on the version information.

[0059] It should be noted that based on historical version information, the system can also generate a timeline of rule changes or a change history map to intuitively display the evolution of the rules from creation to the current state, including the time point of each change, the reason for the change, and the rule status after the change.

[0060] Step S104, publishing the current version of the target aviation product rule based on the version information of the target aviation product rule, making the current version of the target aviation product rule effective, and configuring the rule state of the current version of the target aviation product rule to be a published state.

[0061] It should be noted that the version information of the target aviation product rules can indicate whether the current version of the target aviation product rules is the initial version. The release method of the target aviation product rules is determined based on whether the target aviation product rules are the initial version, including direct release and overwrite release. Overwrite release means that while the current version of the target aviation product rules takes effect, the historical version of the target aviation product rules is invalidated, thereby achieving seamless connection between the old and new versions of the rules, ensuring that only a single version of the effective rules exists within the same time period.

[0062] Optionally, the current version of the target aviation product rules is published based on the version information of the target aviation product rules, and the step of making the current version of the target aviation product rules effective includes: when the version information of the target aviation product rules indicates that the current version of the target aviation product rules is a non-initial version of the target aviation product rules, extracting a target historical version of the target aviation product rules from the historical version, wherein the target historical version is a historical version in a published state; publishing the current version of the target aviation product rules to make the current version of the target aviation product rules effective, and invalidating the target historical version of the target aviation product rules at the time point when the current version of the target aviation product rules takes effect, wherein invalidating the target historical version ensures that there is only one version of the target aviation product rules in a published state at the same time point.

[0063] It should be noted that in order to ensure that only one version of the rules is in effect at the same time and to avoid aviation product sales accidents caused by the effectiveness of multiple versions of the rules, when publishing a version, the embodiment of the present invention first needs to identify the current version of the target aviation product rules and determine the version status of the current version. If the current version of the target aviation product rules is a non-initial version corresponding to the rule, that is, the rule is not created for the first time, and a historical version in the published state already exists in the current system, then it is necessary to identify the target historical version in the published state. While publishing the current version of the target aviation product rules, the target historical version in the published state is terminated to make the target historical version of the target aviation product rules invalid, thereby achieving seamless connection between the old and new rules.

[0064] Optionally, the target aviation product rules are published based on the version information of the target aviation product rules, and the step of making the target aviation product rules effective includes: when the version information of the target aviation product rules indicates that the version of the target aviation product rules is the initial version under the target aviation product, the target aviation product rules are published to make the target aviation product rules effective.

[0065] It should be noted that if there is no historical version of the target aviation product rules, the newly created target aviation product rules are the initial version, and there will be no published target historical version. In this case, the latest created current version of the target aviation product rules is directly published to make the current version of the target aviation product rules effective. After the target aviation product rules take effect, they can be queried by users and the corresponding aviation products can be purchased based on the rules.

[0066] Optionally, after making the target aviation product rule effective, it also includes: receiving an aviation product rule query request from the user end, and obtaining a query field based on the aviation product rule query request; querying a rule database based on the query field to obtain M aviation product rules, where M is a positive integer; screening the M aviation product rules based on the rule status of the M aviation product rules to obtain aviation product rules that meet user needs, and pushing the aviation product rules that meet user needs to the user end.

[0067] It should be noted that when users need to purchase relevant aviation products, they can query the aviation product rule information corresponding to the aviation products through the aviation product rule effectiveness system. The system receives the aviation product rule query request from the user end, and obtains multiple aviation product rules based on the query field selected by the user, such as passenger type, time information, airport information, product type, etc., and then filters them according to the rule status of the aviation product rules, retains the aviation product rules in the published state, obtains aviation product rules that meet user needs, and pushes them to the user end, so as to realize rapid query of aviation product rule information and make the aviation product rule information transparent to users.

[0068] Through the above steps, an aviation product rule creation request from the business end is received, and based on the aviation product rule creation request, aviation product rule information corresponding to the target aviation product rule to be created is obtained, wherein the aviation product rule information at least includes: aviation product name, aviation product code, rule code, and rule applicability information; and based on the aviation product rule information, the target aviation product rule is verified to obtain a verification result, and then, when the verification result indicates that the target aviation product rule has passed the verification, the rule database is queried based on the aviation product code in the target aviation product rule information to obtain a historical version of the target aviation product rule, and version information is marked for the target aviation product rule based on the historical version to obtain the current version of the target aviation product rule, and finally, based on the version information of the target aviation product rule, the current version of the target aviation product rule is published, so that the current version of the target aviation product rule takes effect, and the rule status of the current version of the target aviation product rule is configured to be published.

[0069] In this embodiment, multiple product rules for aviation products are marked by version information. When the business end creates a target aviation product rule, the database is queried by the aviation product code to obtain the historical version of the target aviation product rule. Based on the historical version, the historical version is invalidated while the target aviation product rule is taking effect, so that only one version of the aviation product rule is valid at the same time, thereby achieving the purpose of automatically switching between old and new rules and eliminating the time difference in the effectiveness of the rules. The technical effect of seamless switching between old and new rules and improving the processing efficiency of old rules is achieved, avoiding the abnormal sales of aviation products caused by the time difference in the effectiveness of the rules, and thus solving the technical problem in the related technology that when publishing new aviation product rules, business personnel need to manually query and mine the old rules in the published state and eliminate them, which is inefficient.

[0070] Another optional specific implementation is described in detail below.

[0071] The above-mentioned aviation product rule validation method is applied to the aviation product rule validation system, which includes a rule configuration module, a rule publishing module and a rule query module. Specifically,

[0072] The rule configuration module is used to maintain product rules, check whether fields are required, data compliance, and rule duplication, etc., to complete the configuration and storage of rules. For published rules, if modifications are made, a new version (the aviation product code remains unchanged) must be generated based on the original rules for maintenance.

[0073] In the rule publishing module, after the rules are created, they need to be submitted for approval. After approval, the rules can be automatically or manually published. For multiple versions of rules, after the new version of the rule is approved, the old version of the rule will be automatically invalidated when it is published.

[0074] The rule query module matches the available product rules according to the query request. When multiple rules are matched for the same aviation product, the rules in the expired and saved states need to be filtered out, and the aviation product rules in the published state need to be pushed to the user.

[0075] Figure 2 is a schematic diagram of an optional process for the effectiveness of aviation product rules according to an embodiment of the present invention, specifically, the execution process for the effectiveness of aviation product rules, such as Figure 2 As shown in the figure, the implementation process of aviation product rules specifically includes:

[0076] Step 1, start;

[0077] Step 2: The business end configures the target aviation product rules;

[0078] When creating a rule, first check whether the rule name is legal and whether it is repeated. If it is repeated, the subsequent verification will be terminated and an error message will be returned. The business personnel log in to the effective system of the aviation product rule on the business end, select the rule in the menu, and open the product rule information configuration page through the new operation. Fill in the basic content of the product rule, sales restrictions and other information, and submit the created target aviation product rule and creation request, and send it to the rule verification system.

[0079] Step 3: Verify the target aviation product rules. If the verification passes, execute step 4. If the verification fails, return to the business end and repeat step 2.

[0080] The rule verification module parses the rule creation request, obtains the target aviation product rule information, and verifies the compliance and mandatory items of the rule fields.

[0081] If the verification fails, a friendly error message will be displayed to improve the efficiency of rule creation.

[0082] Step 4: query historical versions and mark version information for target aviation product rules;

[0083] After the product rule is successfully created, a target aviation product rule in a saved state is generated and a version is marked for it. After the rule is successfully saved, it needs to be further approved (optional operation) and published (mandatory operation) to make the rule formally effective (that is, the rule status is published), queried and used by external systems, and thus applied to the product sales process.

[0084] If the rule needs to be approved, the business personnel submit it to the review end. After approval, the rule status is saved and the approval status is approved. At this time, the rule can be manually published (the business personnel manually perform the publishing operation) or the system can automatically publish it (the system automatically performs the publishing operation according to the approval status).

[0085] Step 5: If the version information of the target aviation product rule indicates that it is a non-initial version, the historical version will be invalidated while the target aviation product rule is released. Otherwise, if the version information of the target aviation product rule indicates that it is an initial version, the target aviation product rule will be directly released and the version will be marked.

[0086] Step six, end.

[0087] The rule configuration module mainly provides users with a rule maintenance page. When performing corresponding operations on rules in different states, the system needs to complete the corresponding verification and correctly identify the rule version. The following is a detailed explanation through a rule example:

[0088] Assume that there is a saved product rule for Airbus Intermodal, the product code is P001, and the rule ID is 1001, as shown in Table 1:

[0089] Table 1: Example of an aviation product rule

[0090]

[0091] Scenario 1: The user creates an Airbus product from Airport B to Airport C through the "Add" operation with a product code of P002, which is sold from 2023-11-01 to 2023-12-31. It is suitable for adults. Since this product rule is created for the first time and has no association with the P001 rule, when the rule is saved successfully, the system identifies the version of the product rule as V1, automatically generates a new rule ID of 1002, and the rule status is saved.

[0092] Table 2: Example table after adding new rules

[0093]

[0094]

[0095] Scenario 2: The user performs the "Edit" operation on the product rule of P001, and changes the airport and operating route to Airport B, Airport B site -> Airport C site. After the rule is saved successfully, since the editing operation is performed on the basis of P001, but the rule status of P001 is saved, when the rule is saved successfully, the system does not need to generate a new rule ID or a new version.

[0096] Table 3: Example table after editing the original rules

[0097]

[0098] Scenario 3: The user executes the "Publish" operation for the product rule P001 after it has been approved. After the release is successful, the system records the rule status as published.

[0099] Table 4: An example table after publishing the original rules

[0100]

[0101] Scenario 4: Due to policy adjustments, airline users now need to extend the sales date to 2024-3-1, so the rules need to be modified. Perform the "Edit" operation on P001. At this time, the system recognizes that the operation is performed in the "Published" state. Therefore, after the modified rule is successfully saved, the system needs to recreate a rule with ID 1002, but the product code is still P001, and mark the rule version as V2, and the rule status is saved.

[0102] Table 5 An example table of creating a new rule when there is a historical version

[0103]

[0104] Under the premise of approval (for rules that require approval), when releasing a new version Vn+1 (whether manually or automatically), the system needs to query whether there is a released Vn version with the same product code through product code association. If so, the system needs to automatically terminate the Vn version when releasing the Vn+1 version. The following is a detailed explanation through rule examples:

[0105] Assume that the current Airbus intermodal transport has the following product rules:

[0106] Table 6 Example of another aviation product rule

[0107]

[0108]

[0109] Scenario 1: The system executes the "Publish" operation on the rule with rule ID 1002. At this time, the system associates and queries the rule with rule ID 1001 in the database through product code P001, and determines that the rule status is published. Therefore, when executing the publish instruction for 1002, in addition to updating the rule status of 1002 to published, the system will automatically execute the expiration operation on rule 1001 and update its rule status to expired.

[0110] Table 7: An example table after publishing aviation product rules

[0111]

[0112] Scenario 2: The "Publish" operation is performed on the rule with rule ID 1003. At this time, the system does not find other rules associated with the product code P002 in the database, and determines that the rule status is saved. Therefore, the publish instruction is executed on 1003, and the rule status is updated to published.

[0113] Table 8 Another example table after publishing aviation product rules

[0114]

[0115]

[0116] The rule query module means that when an external query request is input, it needs to verify the query request, find all rules that match the query request, filter the matched rules according to logic, and finally output valid rules.

[0117] The following is a detailed explanation of the rules example:

[0118] Assume that the current Airbus intermodal transport has the following product rules:

[0119] Table 9 Example of another aviation product rule

[0120]

[0121]

[0122] The current query scenario for Airbus products is: an adult wants to book a bus ticket from Airport A to Location A on December 10, 2023.

[0123] Based on the above scenario, the query request input is: (passenger type) adult, (time) December 10, 2023, (airport) airport A, (bus route) airport A station -> station A.

[0124] The rule query steps are as follows:

[0125] First, according to the rule status, the expired and saved aviation product rules are filtered out, and the published aviation product rules are retained for subsequent judgment.

[0126] Then filter out by airport, and keep the rules of airport A required by the user for subsequent judgment.

[0127] Filter by operating routes and retain the rule of Airport A -> Place A for subsequent judgment.

[0128] Finally, filter by applicable sales date and passenger type, and keep the rules with applicable sales date including December 10, 2023 and adults. The above filtering results meet the requirements and can be output as the final effective rules. The output results are as follows:

[0129] Table 10 Example table of aviation product rules obtained by filtering based on user needs

[0130]

[0131]

[0132] In the embodiment of the present invention, a strategy for eliminating the time difference in the effectiveness of aviation product rules through multiple versions is proposed. Through the aviation product rule effectiveness system through rule creation, rule publishing and rule query services, the rules effective in production will not be affected by the new rule approval process. When the approved new rules are published and take effect, the old rules are automatically terminated, thereby achieving seamless switching between the old and new rules in production, improving the processing efficiency of the new and old rules, and avoiding chaos in aviation product sales caused by the time difference between the effectiveness and expiration of the new and old rules.

[0133] The following is a detailed description in conjunction with another embodiment.

[0134] Embodiment 2

[0135] An aviation product rule validation device provided in this embodiment includes multiple implementation units, each implementation unit corresponds to each implementation step in the above-mentioned embodiment 1. Its specific implementation methods and beneficial effects can refer to the above-mentioned method embodiments and will not be repeated here.

[0136] Figure 3 is a schematic diagram of an optional aviation product rule validation device according to an embodiment of the present invention, such as Figure 3 As shown, the aviation product rule validation device may include: a receiving unit 31, a verification unit 32, an acquisition unit 33, and a validation unit 34, wherein:

[0137] The receiving unit 31 is used to receive an aviation product rule creation request from a business end, and obtain aviation product rule information corresponding to a target aviation product rule to be created based on the aviation product rule creation request, wherein the aviation product rule information at least includes: an aviation product name, an aviation product code, a rule code, and rule applicability information;

[0138] A verification unit 32, configured to verify the target aviation product rule based on the aviation product rule information to obtain a verification result;

[0139] An acquisition unit 33 is configured to query a rule database based on the aviation product code in the target aviation product rule information to acquire a historical version of the target aviation product rule when the verification result indicates that the target aviation product rule has passed the verification, mark version information for the target aviation product rule based on the historical version, and obtain a current version of the target aviation product rule;

[0140] The validation unit 34 is used to publish the current version of the target aviation product rule based on the version information of the target aviation product rule, make the current version of the target aviation product rule effective, and configure the rule state of the current version of the target aviation product rule to be a published state.

[0141] The above-mentioned aviation product rule validation device receives an aviation product rule creation request from the business end through a receiving unit 31, and obtains aviation product rule information corresponding to the target aviation product rule to be created based on the aviation product rule creation request, wherein the aviation product rule information at least includes: aviation product name, aviation product code, rule code, and rule applicability information; verifies the target aviation product rule based on the aviation product rule information through a verification unit 32 to obtain a verification result; when the verification result indicates that the target aviation product rule has passed the verification, the acquisition unit 33 queries the rule database based on the aviation product code in the target aviation product rule information to obtain a historical version of the target aviation product rule, marks the version information for the target aviation product rule based on the historical version, and obtains the current version of the target aviation product rule; and publishes the current version of the target aviation product rule based on the version information of the target aviation product rule through an validation unit 34, so that the current version of the target aviation product rule takes effect, and configures the rule status of the current version of the target aviation product rule to a published status.

[0142] In this embodiment, multiple product rules for aviation products are marked by version information. When the business end creates a target aviation product rule, the database is queried by the aviation product code to obtain the historical version of the target aviation product rule. Based on the historical version, the historical version is invalidated while the target aviation product rule is taking effect, so that only one version of the aviation product rule is valid at the same time, thereby achieving the purpose of automatically switching between old and new rules and eliminating the time difference in the effectiveness of the rules. The technical effect of seamless switching between old and new rules and improving the processing efficiency of old rules is achieved, avoiding the abnormal sales of aviation products caused by the time difference in the effectiveness of the rules, and thus solving the technical problem in the related technology that when publishing new aviation product rules, business personnel need to manually query and mine the old rules in the published state and eliminate them, which is inefficient.

[0143] Optionally, the effectiveness unit includes: a first extraction module, used to extract a target historical version of the target aviation product rule from the historical version when the version information of the target aviation product rule indicates that the current version of the target aviation product rule is a non-initial version of the target aviation product rule, wherein the target historical version is a historical version in a published state; a first publishing module, used to publish the current version of the target aviation product rule to make the current version of the target aviation product rule effective, and invalidate the target historical version of the target aviation product rule at the time point when the current version of the target aviation product rule takes effect, wherein invalidating the target historical version ensures that there is only one published version of the target aviation product rule at the same time point.

[0144] Optionally, the validation unit includes: a second publishing module, used to publish the target aviation product rule to make the target aviation product rule effective when the version information of the target aviation product rule indicates that the version of the target aviation product rule is an initial version under the target aviation product.

[0145] Optionally, the aviation product rule validation device also includes: a first generation module, used to generate the current version of the target aviation product rules and obtain the rule review requirements of the target aviation product rules; a first sending module, used to send the current version of the target aviation product rules to the review end when the rule review requirements indicate that the target aviation product rules need to be reviewed, and receive the review results returned by the review end.

[0146] Optionally, the aviation product rule validation device also includes: a first configuration module, which is used to configure the rule status of the current version of the target aviation product rules to a saved state and wait for the target aviation product rules to take effect when the audit result indicates that the current version of the target aviation product has passed the audit; a second configuration module, which is used to configure the rule status of the current version of the target aviation product rules to a saved state and return the current version of the target aviation product rules to the business end for modification by the business end when the audit result indicates that the current version of the target aviation product has not passed the audit.

[0147] Optionally, the aviation product rule validation device also includes: a first receiving module, used to receive an aviation product rule query request from a user terminal, and obtain a query field based on the aviation product rule query request; a first query module, used to query a rule database based on the query field to obtain M aviation product rules, where M is a positive integer; a first screening module, used to screen the M aviation product rules based on their rule states to obtain aviation product rules that meet user needs, and push the aviation product rules that meet user needs to the user terminal.

[0148] Optionally, the verification unit includes: a first verification module, used to verify the required fields of the aviation product rule information based on the required field rules to obtain the required field verification results; a second verification module, used to verify the compliance of the aviation product rule information based on the field compliance rules to obtain the compliance verification results; a second acquisition module, used to obtain the verification results of the target aviation product rules based on the required field verification results and the compliance verification results.

[0149] The device for implementing the above-mentioned aviation product rules may also include a processor and a memory. The above-mentioned receiving unit 31, verification unit 32, acquisition unit 33, implementation unit 34, etc. are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize corresponding functions.

[0150] The processor includes a kernel, which retrieves the corresponding program unit from the memory. One or more kernels can be set, and the aviation product rules can be made effective by adjusting the kernel parameters.

[0151] The above-mentioned memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one storage chip.

[0152] According to another aspect of an embodiment of the present invention, there is further provided a computer-readable storage medium, the computer-readable storage medium including a stored computer program, wherein when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute any one of the above-mentioned methods for implementing aviation product rules.

[0153] According to another aspect of an embodiment of the present invention, there is also provided an electronic device, comprising one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by one or more processors, the one or more processors implement a method for implementing any one of the above-mentioned aviation product rules.

[0154] According to another aspect of an embodiment of the present invention, a computer program product is provided. The computer program product includes a computer program, wherein when the computer program is executed by a processor, the method for implementing any one of the above-mentioned aviation product rules is implemented.

[0155] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program that is initialized with the following method steps: receiving an aviation product rule creation request from a business end, and obtaining aviation product rule information corresponding to a target aviation product rule to be created based on the aviation product rule creation request, wherein the aviation product rule information includes at least: aviation product name, aviation product code, rule code, and rule applicability information; verifying the target aviation product rule based on the aviation product rule information to obtain a verification result; when the verification result indicates that the target aviation product rule has passed the verification, querying a rule database based on the aviation product code in the target aviation product rule information to obtain a historical version of the target aviation product rule, marking version information for the target aviation product rule based on the historical version, and obtaining a current version of the target aviation product rule; publishing the current version of the target aviation product rule based on the version information of the target aviation product rule, so that the current version of the target aviation product rule takes effect, and configuring the rule status of the current version of the target aviation product rule to a published status.

[0156] The present application also provides a computer program product, which, when executed on a data processing device, is also suitable for executing a program that is initialized with the following method steps: publishing the current version of the target aviation product rules based on the version information of the target aviation product rules, and the step of making the current version of the target aviation product rules effective includes: when the version information of the target aviation product rules indicates that the current version of the target aviation product rules is a non-initial version of the target aviation product rules, extracting the target historical version of the target aviation product rules from the historical version, wherein the target historical version is a historical version in a published state; publishing the current version of the target aviation product rules to make the current version of the target aviation product rules effective, and invalidating the target historical version of the target aviation product rules at the time point when the current version of the target aviation product rules takes effect, wherein invalidating the target historical version ensures that there is only one published version of the target aviation product rules at the same time point.

[0157] The present application also provides a computer program product, which, when executed on a data processing device, is also suitable for executing a program that is initialized with the following method steps: publishing the target aviation product rules based on the version information of the target aviation product rules, and the step of making the target aviation product rules effective includes: when the version information of the target aviation product rules indicates that the version of the target aviation product rules is the initial version under the target aviation product, publishing the target aviation product rules to make the target aviation product rules effective.

[0158] The present application also provides a computer program product, which, when executed on a data processing device, is also suitable for executing an initialization program having the following method steps: the aviation product rule information also includes rule review requirements, and after obtaining the current version of the target aviation product rules, it also includes: generating the current version of the target aviation product rules, and obtaining the rule review requirements of the target aviation product rules; when the rule review requirements indicate that the target aviation product rules need to be reviewed, sending the current version of the target aviation product rules to the review end, and receiving the review results returned by the review end.

[0159] The present application also provides a computer program product, which, when executed on a data processing device, is also suitable for executing a program that initializes the following method steps: after receiving the audit result returned by the audit end, it also includes: when the audit result indicates that the current version of the target aviation product has passed the audit, the rule status of the current version of the target aviation product rules is configured to a saved state and wait for the target aviation product rules to take effect; when the audit result indicates that the current version of the target aviation product has not passed the audit, the rule status of the current version of the target aviation product rules is configured to a saved state, and the current version of the target aviation product rules is returned to the business end for modification by the business end.

[0160] The present application also provides a computer program product, which, when executed on a data processing device, is also suitable for executing a program that initializes the following method steps: after making the current version of the target aviation product rule effective, it also includes: receiving an aviation product rule query request from a user terminal, and obtaining a query field based on the aviation product rule query request; querying a rule database based on the query field to obtain M aviation product rules, where M is a positive integer; screening the M aviation product rules based on the rule status of the M aviation product rules to obtain aviation product rules that meet user needs, and pushing the aviation product rules that meet user needs to the user terminal.

[0161] The present application also provides a computer program product, which, when executed on a data processing device, is also suitable for executing a program that is initialized with the following method steps: the step of verifying the target aviation product rules based on the aviation product rule information includes: verifying the required fields of the aviation product rule information based on the required field rule to obtain the required field verification result; verifying the compliance of the aviation product rule information based on the field compliance rule to obtain the compliance verification result; and obtaining the verification result of the target aviation product rules based on the required field verification result and the compliance verification result.

[0162] Figure 4 1 is a hardware structure block diagram of an electronic device (or mobile device) for executing a method for implementing aviation product rules according to an embodiment of the present invention. Figure 4 As shown, the electronic device may include one or more processors ( Figure 4 402a, 402b, ..., 402n are used to illustrate that the processor 402 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 404 for storing data. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a keyboard, a power supply and / or a camera. A person skilled in the art can understand that Figure 4 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 4 More or fewer components as shown, or with Figure 4 Different configurations are shown.

[0163] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0164] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0165] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0166] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0167] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0168] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0169] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for implementing aviation product rules, characterized in that: include: Receive an aviation product rule creation request from a business end, and acquire aviation product rule information corresponding to a target aviation product rule to be created based on the aviation product rule creation request, wherein the aviation product rule information at least includes: an aviation product name, an aviation product code, a rule code, and rule applicability information; Verifying the target aviation product rule based on the aviation product rule information to obtain a verification result; If the verification result indicates that the target aviation product rule has passed the verification, querying a rule database based on the aviation product code in the target aviation product rule information to obtain a historical version of the target aviation product rule, marking version information for the target aviation product rule based on the historical version, and obtaining a current version of the target aviation product rule; The current version of the target aviation product rule is published based on the version information of the target aviation product rule to make the current version of the target aviation product rule effective, and the rule state of the current version of the target aviation product rule is configured as a published state.

2. The validation method according to claim 1, characterized in that: The steps of publishing the current version of the target aviation product rule based on the version information of the target aviation product rule and making the current version of the target aviation product rule effective include: In a case where the version information of the target aviation product rule indicates that the current version of the target aviation product rule is a non-initial version of the target aviation product rule, extracting a target historical version of the target aviation product rule from the historical version, wherein the target historical version is a historical version in a published state; The current version of the target aviation product rules is published to make the current version of the target aviation product rules effective, and the target historical version of the target aviation product rules is invalidated at the time when the current version of the target aviation product rules takes effect, wherein the invalidation of the target historical version ensures that there is only one published version of the target aviation product rules at the same time point.

3. The validation method according to claim 1, characterized in that: The step of publishing the target aviation product rule based on the version information of the target aviation product rule to make the target aviation product rule effective includes: In a case where the version information of the target aviation product rule indicates that the version of the target aviation product rule is an initial version under the target aviation product, the target aviation product rule is published to make the target aviation product rule effective.

4. The validation method according to claim 1, characterized in that: The aviation product rule information also includes rule review requirements, and after obtaining the current version of the target aviation product rule, it also includes: Generate a current version of the target aviation product rules, and obtain the rule review requirements of the target aviation product rules; When the rule review requirement indicates that the target aviation product rule needs to be reviewed, the current version of the target aviation product rule is sent to the review end, and the review result returned by the review end is received.

5. The validation method according to claim 4, characterized in that: After receiving the audit result returned by the audit end, the method further includes: If the audit result indicates that the current version of the target aviation product has passed the audit, configuring the rule status of the current version of the target aviation product rule to be saved and waiting for the target aviation product rule to take effect; When the audit result indicates that the current version of the target aviation product has not passed the audit, the rule status of the current version of the target aviation product rules is configured to be saved, and the current version of the target aviation product rules is returned to the business end for modification by the business end.

6. The validation method according to claim 1, characterized in that: After the current version of the target aviation product rule is made effective, it also includes: Receiving an aviation product rule query request from a user terminal, and acquiring a query field based on the aviation product rule query request; Querying the rule database based on the query field to obtain M aviation product rules, where M is a positive integer; The M aviation product rules are screened based on the rule states of the M aviation product rules to obtain the aviation product rules that meet the user's needs, and the aviation product rules that meet the user's needs are pushed to the user terminal.

7. The validation method according to claim 1, characterized in that: The step of verifying the target aviation product rule based on the aviation product rule information includes: Verifying the required fields of the aviation product rule information based on the required field rules to obtain required field verification results; Verifying the compliance of the aviation product rule information based on the field compliance rule to obtain a compliance verification result; A verification result of the target aviation product rule is obtained based on the required field verification result and the compliance verification result.

8. An aviation product rule validation device, characterized in that: include: A receiving unit, configured to receive an aviation product rule creation request from a business end, and acquire aviation product rule information corresponding to a target aviation product rule to be created based on the aviation product rule creation request, wherein the aviation product rule information at least includes: an aviation product name, an aviation product code, a rule code, and rule applicability information; A verification unit, configured to verify the target aviation product rule based on the aviation product rule information to obtain a verification result; A generating unit, configured to generate a target aviation product rule and configure a rule state of the target aviation product rule to a saved state if the verification result indicates that the target aviation product rule has passed the verification; An acquiring unit is configured to, if the verification result indicates that the target aviation product rule has passed the verification, query a rule database based on the aviation product code in the target aviation product rule information to acquire a historical version of the target aviation product rule, mark version information for the target aviation product rule based on the historical version, and obtain a current version of the target aviation product rule; The validation unit is used to publish the current version of the target aviation product rule based on the version information of the target aviation product rule, so that the current version of the target aviation product rule is effective, and configure the rule state of the current version of the target aviation product rule to be a published state.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored computer program, wherein when the computer program is executed, the device where the computer-readable storage medium is located is controlled to execute the method for implementing aviation product rules as described in any one of claims 1 to 7.

10. An electronic device, characterized in that: The invention comprises one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method for implementing the aviation product rules described in any one of claims 1 to 7.

Images