Logistics business rule checking method, computer device, storage medium and product

Abstract

The application relates to a logistics business rule checking method, a computer device, a storage medium and a product. The method comprises the following steps: generating total checking rules of a logistics business according to checking environment information of the logistics business, wherein the total checking rules comprise multiple rule checking components and rule checking links, and the multiple rule checking components are independent of each other; selecting step: selecting a current rule checking item from all rule checking items of the multiple rule checking components according to the rule checking links; checking to-be-checked business information of the logistics business according to the current rule checking item, obtaining a checking sub-result of a rule checking item of the logistics business; returning to the selecting step under the condition that the current rule checking item is checked, until all rule checking items are selected, and obtaining a checking total result corresponding to all checking sub-results. The method improves the checking efficiency of logistics business rule checking.

Description

Technical Field

[0001] This application relates to the field of logistics technology, and in particular to a method for verifying logistics business rules, computer equipment, computer-readable storage medium, and computer program product. Background Technology

[0002] With the continuous development of the Internet, the logistics field is also undergoing gradual technological iteration. Many tasks in the logistics field can be carried out with the support of the Internet. For example, in order to improve operational efficiency and reduce operating costs, rule verification of logistics operations is an indispensable part of logistics management and operation. Rule verification of logistics operations is implemented by business personnel designing business logic code.

[0003] Currently, in the process of validating logistics business rules, business personnel typically edit hard code as business rule conditions, and the validity of the validation is determined based on these conditions. However, due to the large scale and complexity of logistics business rule validation scenarios, the development cycle of hard code is too long, which easily leads to excessively long validation times for logistics business rules. Therefore, the current validation efficiency for logistics business rules is low. Summary of the Invention

[0004] Therefore, it is necessary to provide a logistics business rule verification method, computer equipment, computer-readable storage medium, and computer program product that improves the verification efficiency of logistics business rule verification in response to the above-mentioned technical problems.

[0005] Firstly, this application provides a method for verifying logistics business rules, including:

[0006] Based on the verification environment information of the logistics business, a general verification rule for the logistics business is generated, wherein the general verification rule includes multiple rule verification components and rule verification links, and the multiple rule verification components are independent of each other;

[0007] Selection step: Based on the rule verification link, select the current rule verification item from all rule verification items of the multiple rule verification components;

[0008] Based on the current rule verification item, the business information to be verified in the logistics business is verified to obtain the verification sub-result of the rule verification item of the logistics business.

[0009] If the current rule verification item is verified, return to the selection step until all rule verification items have been selected, and obtain the total verification result corresponding to all the verification sub-results.

[0010] In one embodiment, generating the overall verification rules for the logistics business based on the verification environment information of the logistics business includes:

[0011] Based on the verification environment information, query the default verification rule for the logistics business in the preset rule verification table;

[0012] The default verification rules are adjusted to obtain the overall verification rules for the logistics business.

[0013] In one embodiment, adjusting the default verification rules to obtain the overall verification rules for the logistics business includes at least one of the following:

[0014] The default rule verification link of the default verification rule is adjusted, and the adjusted default verification rule is used as the total verification rule;

[0015] The default rule validation component of the default validation rule is adjusted, and the adjusted default validation rule is used as the total validation rule.

[0016] The default rule verification link and default rule verification component of the default verification rule are adjusted together, and the adjusted default verification rule is used as the total verification rule.

[0017] In one embodiment, the adjustment of the default rule verification chain and the default rule verification component for the default verification rule includes:

[0018] Query the verification idle time points under the default rule verification link;

[0019] Based on the verification idle time point, update the default rule verification link and deploy the preset rule verification component at the verification idle time point.

[0020] In one embodiment, selecting the current rule verification item from all rule verification items of the plurality of rule verification components according to the rule verification link includes:

[0021] Based on the rule verification link, candidate rule verification components are selected from the plurality of rule verification components, wherein the candidate rule verification components include a plurality of candidate rule verification items;

[0022] Based on the verification priority of the plurality of candidate rule verification items, the current rule verification item is selected from the plurality of candidate rule verification items.

[0023] In one embodiment, the step of verifying the logistics business information to be verified based on the current rule verification item to obtain the verification sub-result of the logistics business rule verification item includes:

[0024] Based on the verification dimension to which the current rule verification item belongs, extract the target business information to be verified from the business information to be verified, wherein the verification dimension includes at least one of the following four: identity verification dimension, service verification dimension, permission verification dimension, and security verification dimension.

[0025] Based on the verification conditions of the current rule verification item, the target business information to be verified is verified to obtain the information verification results of the logistics business under each verification dimension;

[0026] Based on the verification results of each piece of information, a verification sub-result is generated for the rule verification items of the logistics business.

[0027] In one embodiment, generating a verification sub-result for the rule verification item of the logistics business based on the verification results of each of the information includes:

[0028] By integrating the verification results of each piece of information and the corresponding verification dimension weights, the verification quality index of the rule verification item of the logistics business is obtained.

[0029] If the verification quality index is greater than the preset verification quality index threshold, a verification sub-result is generated indicating that the current rule verification item has passed verification.

[0030] If the verification quality index is less than or equal to the preset verification quality index threshold, a verification sub-result is generated indicating that the current rule verification item has failed verification.

[0031] Secondly, this application also provides a logistics business rule verification device, comprising:

[0032] The generation module is used to generate the overall verification rules for the logistics business based on the verification environment information of the logistics business. The overall verification rules include multiple rule verification components and rule verification links, and the multiple rule verification components are independent of each other.

[0033] The selection module is used to select the following step: based on the rule verification link, select the current rule verification item from all rule verification items of the multiple rule verification components;

[0034] The first verification module is used to verify the business information to be verified of the logistics business according to the current rule verification item, and obtain the verification sub-result of the rule verification item of the logistics business.

[0035] The second verification module is used to return to the selection step after the current rule verification item has been verified, until all rule verification items have been selected, and obtain the total verification result corresponding to all the verification sub-results.

[0036] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0037] Based on the verification environment information of the logistics business, a general verification rule for the logistics business is generated. This general verification rule includes multiple rule verification components and rule verification links, with the multiple rule verification components operating independently. The selection steps are as follows: Based on the rule verification link, the current rule verification item is selected from all rule verification items of the multiple rule verification components; based on the current rule verification item, the business information to be verified in the logistics business is verified to obtain the verification sub-result of the rule verification item for the logistics business; if the verification of the current rule verification item is completed, the selection steps are returned until all rule verification items have been selected, resulting in a total verification result corresponding to all the verification sub-results.

[0038] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0039] Based on the verification environment information of the logistics business, a general verification rule for the logistics business is generated. This general verification rule includes multiple rule verification components and rule verification links, with the multiple rule verification components operating independently. The selection steps are as follows: Based on the rule verification link, the current rule verification item is selected from all rule verification items of the multiple rule verification components; based on the current rule verification item, the business information to be verified in the logistics business is verified to obtain the verification sub-result of the rule verification item for the logistics business; if the verification of the current rule verification item is completed, the selection steps are returned until all rule verification items have been selected, resulting in a total verification result corresponding to all the verification sub-results.

[0040] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0041] Based on the verification environment information of the logistics business, a general verification rule for the logistics business is generated. This general verification rule includes multiple rule verification components and rule verification links, with the multiple rule verification components operating independently. The selection steps are as follows: Based on the rule verification link, the current rule verification item is selected from all rule verification items of the multiple rule verification components; based on the current rule verification item, the business information to be verified in the logistics business is verified to obtain the verification sub-result of the rule verification item for the logistics business; if the verification of the current rule verification item is completed, the selection steps are returned until all rule verification items have been selected, resulting in a total verification result corresponding to all the verification sub-results.

[0042] The aforementioned logistics business rule verification method, computer equipment, computer-readable storage medium, and computer program product first generate a general verification rule for the logistics business based on the verification environment information. This general verification rule includes multiple rule verification components and rule verification links; that is, the general verification rule is obtained by combining multiple rule verification components based on the rule verification links. This enables the automatic generation of the general verification rule for the logistics business based on the verification environment information. Then, it executes a selection step through the rule verification links to select the current rule verification item from all rule verification items of the multiple rule verification components. Based on the current rule verification item, it verifies the business information to be verified in the logistics business, thereby obtaining the verification sub-result of the rule verification item for the logistics business. Finally, the current rule is verified. Once the verification items are completed, return to the selection step until all rule verification items have been selected, and obtain the total verification result corresponding to each verification sub-result. This achieves the goal of integrating business rule conditions sequentially through rule verification items and rule verification components, transforming the hard-code development process for logistics business into a rule verification item configuration process. Since both rule verification items and rule verification components can pre-integrate business rule conditions, no hard-code development is required during the verification process. Therefore, this overcomes the technical defect that the large and complex rule verification scenarios of logistics business lead to excessively long hard-code development cycles, resulting in excessively long rule verification times for logistics business. Thus, the verification efficiency of logistics business rule verification is improved. Attached Figure Description

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

[0044] Figure 1This is a flowchart illustrating a logistics business rule verification method in one embodiment;

[0045] Figure 2 This is a flowchart illustrating the logistics business rule verification method in another embodiment;

[0046] Figure 3 This is a structural block diagram of a logistics business rule verification device in one embodiment;

[0047] Figure 4 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0048] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0049] First, it should be understood that in the logistics field, the process of verifying rules for logistics operations is usually quite complex. For example, taking the "monthly settlement control order verification" of logistics settlement operations as an example, its verification rules involve monthly settlement card number validity verification, branch control verification, whether branch mapping exists, intra-regional branch verification, inter-regional branch verification, whether channel verification exists, channel access code verification, same-city whitelist validity verification, whitelist validity verification, card number and branch whitelist verification, channel whitelist validity verification, and enterprise ID control verification, among other rule verification items. Furthermore, each rule verification item contains numerous branch conditions, making the verification rule logic for logistics operations lengthy and requiring various hard-coded judgments. Moreover, if different logistics... Designing separate rule validation code for each business operation is time-consuming. During this process, the reusability of the rule validation logic decreases, and the coupling between modules becomes very high. If a small piece of logic changes, it can affect other modules, necessitating comprehensive regression testing for verification. Currently, in logistics business rule validation, business personnel typically edit hard-coded rules as conditions, and validation is judged based on these conditions. This method, influenced by software development cycles and human subjectivity, easily leads to excessively long validation times for logistics business rules. Therefore, there is an urgent need for a logistics business rule validation method that improves the efficiency of validation.

[0050] In one embodiment, such as Figure 1As shown, a logistics business rule verification method is provided. This embodiment uses the application of this method to a terminal as an example. The terminal includes, but is not limited to, personal computers, laptops, smartphones, and tablets. The terminal includes a generation module, a selection module, a verification module, and a validation module. The generation module is used to generate a total verification rule for the logistics business based on the verification environment information of the logistics business. The total verification rule includes multiple rule verification components and rule verification links. The selection module is used to select the current rule verification item from all rule verification items of multiple rule verification components according to the rule verification link. The first validation module is used to verify the logistics business information to be verified based on the current rule verification item to obtain the verification sub-result of the rule verification item of the logistics business. The second validation module is used to return to the selection step when the current rule verification item is completed, until all rule verification items are extracted and the total verification result corresponding to each verification sub-result is obtained. Through the generation module, selection module, and first validation module, the method is verified. The information interaction between the block and the second verification module can directly obtain all rule verification items matching the logistics business. Then, by selecting the current rule verification item from all rule verification items, the business information to be verified in the logistics business is verified, obtaining the verification sub-results of the rule verification items for the logistics business. After all rule verification items have been selected as the current rule verification item and the verification is completed, the total verification result corresponding to each verification sub-result is obtained. That is, by reusing the rule verification items in the rule verification component, the verification of the business information to be verified in the logistics business can be completed, thus eliminating the need to write hard code for business conditions. Therefore, it avoids the situation where the development cycle of hard code is too long due to the large and complex rule verification scenario of the logistics business, which easily leads to excessively long time consumption for rule verification of the logistics business. Therefore, it can improve the verification efficiency of the logistics business rule verification. It is understood that this method can also be applied to servers, and can also be applied to systems including terminals and servers, and implemented through the interaction between terminals and servers. In this embodiment, the method includes the following steps:

[0051] Step 202: Generate the overall verification rules for the logistics business based on the verification environment information of the logistics business. The overall verification rules include multiple rule verification components and rule verification links, and the multiple rule verification components are independent of each other.

[0052] It should be noted that logistics operations can specifically include logistics settlement operations or logistics order management operations. Understandably, logistics operations are typically large and complex. However, rule verification for logistics operations is essential. Taking "monthly settlement order management" as an example, managing orders settled monthly can maintain the stability of the cooperative relationship. However, different logistics operations often have different verification rules. Even a small change in business logic can require business personnel to spend a significant amount of time writing hard code. If the order of different rule verification items under related verification rules needs to be adjusted, large-scale modifications are required, essentially rewriting the verification method. Furthermore, implementing hot-change verification processes is extremely difficult. Based on the above, current logistics business rule verification methods struggle to guarantee verification efficiency when dealing with the complex verification needs of logistics application scenarios. Therefore, this embodiment proposes a logistics business rule verification method.

[0053] It should be noted that by integrating and setting the rule validation items for logistics operations, the reuse of validation rule conditions under each rule validation item can be achieved. Furthermore, by integrating different rule validation items into components, the reuse of validation rule conditions under each rule validation item can be achieved at a higher structural level. For example, in one feasible approach, LiteFlow can be used to transform the waterfall-style code into a code structure with components as the core concept. Since the components are independent of each other, any rule validation component can be defined using a script, and different rule validation components are only associated and driven by the overall validation rule. In this case, LiteFlow can replace multiple hard-coded judgment conditions during the logistics operation orchestration process, which can reduce the branches of rule validation conditions and decouple business code. That is, the overall validation rule is composed of multiple independent rule validation components combined in the order of the rule validation chain. It can be understood that the rule validation component is the implementation unit of the rule validation logic, and the rule validation chain is used to identify the execution order and logical relationship of multiple rule validation components.

[0054] It's worth noting that LiteFlow can orchestrate rule validation for different logistics operations. Specifically, it allows for pre-setting preset rule validation tables, which include information such as ID primary key, application name, link name, link description, EL form format, creation time, and update time. LiteFlow is essentially a powerful, modern rule engine framework that integrates orchestration features with all the characteristics of a rule engine. As an orchestration-based rule engine framework, component orchestration helps decouple business code, making each business segment a component. Therefore, using LiteFlow can transform waterfall-style code into a code structure centered on components. The advantage of this structure lies in its arbitrary orchestration and the decoupling between components, allowing components to be defined using scripts. LiteFlow can be equipped with the DSL syntax of open-source rule engines. It also has independent script components that support many scripting languages. By integrating with Java, it can use scripts to write arbitrary validation rules. In addition, LiteFlow supports placing orchestration rules and scripts in a database or registry center. Its arbitrarily expandable interface can realize the customization of various validation rules. By using validation environment information, a rule index of the total validation rules of the logistics business can be built in the preset rule validation table. The validation environment information is used to characterize the validation environment in which the logistics business is located. Specifically, it can be the system name or scenario identifier, etc. For example, in one feasible approach, assuming the logistics business is logistics management, the validation environment information can be the system code number, QR code parcel delivery, same-city mini-program parcel delivery, or regular App parcel delivery, etc.

[0055] As an example, step 202 includes: obtaining the first verification environment information and the second verification environment information of the logistics business; concatenating the first verification environment information and the second verification environment information into a rule index; and querying the total verification rule of the logistics business in a preset rule verification table according to the rule index. The total verification rule includes multiple rule verification components and rule verification links, and the multiple rule verification components are independent of each other.

[0056] Step 204, Selection Step: Based on the rule verification link, select the current rule verification item from all rule verification items of multiple rule verification components.

[0057] It should be noted that the rule validation link identifies the execution order of different rule validation components. For example, in one implementable method, assuming that the rule validation components include rule validation component A, rule validation component B, rule validation component C, and rule validation component D, the execution order of the different rule validation components can be indicated by the rule validation link as: rule validation component C, rule validation component B, rule validation component A, and rule validation component D.

[0058] As an example, the selection steps are as follows: Based on the rule verification chain, all rule verification items of multiple rule verification components are identified to obtain multiple rule verification item identifiers. Based on the size relationship between multiple rule verification items, the current rule verification item is selected from all rule verification items.

[0059] Step 206: Verify the business information to be verified in the logistics business according to the current rule verification item, and obtain the verification sub-result of the rule verification item of the logistics business.

[0060] It should be noted that multiple rule validation items within the same rule validation component may differ, and rule validation items between different rule validation components may be the same or different. For example, in one feasible implementation, assuming the rule validation component is a monthly settlement card number validity component, the rule validation items under this component may include "monthly settlement card number type validation" and "monthly settlement card number status validation," etc. Specifically, the validation logic of "monthly settlement card number type validation" can be as follows: "Determine whether the monthly settlement card number status is in an effective or pre-cancellation state. If it is in an effective or pre-cancellation state, the validation passes; if it is in a draft, pending, pre-effective, or cancelled state, the validation fails." "Determine whether the monthly settlement card number is frozen. If it is frozen, the validation fails; if it is unfrozen, the validation passes." In summary, only when the monthly settlement card number is in an effective or pre-cancellation state and not frozen can the monthly settlement card number validity validation pass.

[0061] It should be noted that the business information to be verified refers to the business information that is waiting to be verified. For example, in one feasible approach, assuming that the logistics business is a monthly settlement control order verification business, the business information to be verified may include monthly settlement card number, monthly settlement card number information cache data, branch parameters, and parameter branch codes, etc. It can be understood that in the process of verifying based on the current rule verification item, it is only necessary to extract the information related to the verification logic of the current rule verification item for verification.

[0062] As an example, step 206 includes: extracting the portion of business information to be verified that conforms to the current rule verification item from the business information to be verified in the logistics business, and obtaining the verification sub-result of the rule verification item of the logistics business by verifying whether the portion of business information to be verified meets the verification rule conditions of the current rule verification item.

[0063] Step 208: If the current rule verification item has been verified, return to the selection step until all rule verification items have been selected, and obtain the total verification result corresponding to each verification sub-result.

[0064] As an example, step 208 includes: if the current rule verification item verification is completed, return to the execution selection step: according to the rule verification chain, select the current rule verification item from all rule verification items of multiple rule verification components until all rule verification items are selected, obtain each verification sub-result, and integrate each verification sub-result into the total verification result.

[0065] In the above-mentioned logistics business rule verification method, the overall verification rule for the logistics business is first obtained by querying a preset rule verification table based on the verification environment information of the logistics business. This overall verification rule includes multiple rule verification components and rule verification links. These rule verification components are independent of each other. Then, a selection step is executed: based on the rule verification link, the current rule verification item is selected from all rule verification items of the multiple rule verification components. Then, based on the current rule verification item, the business information to be verified in the logistics business is verified to obtain the verification sub-result of the rule verification item for the logistics business. Finally, if the verification of the current rule verification item is completed, the process returns to the selection step until all rule verification items are verified. Once the selection is complete, the total verification result corresponding to each verification sub-result is obtained. This allows for the sequential integration of business rule conditions through rule verification items and rule verification components, transforming the hard-code development process for logistics operations into a rule verification item configuration process. Since both rule verification items and rule verification components can pre-integrate business rule conditions, no hard-code development is required during the verification process. This overcomes the technical drawback of the large and complex rule verification scenarios in logistics operations, which often result in excessively long hard-code development cycles and consequently, excessively long rule verification times for logistics operations. Therefore, the verification efficiency for logistics operations rule verification is improved.

[0066] In one embodiment, such as Figure 2 As shown, based on the verification environment information of the logistics business, the overall verification rules for the logistics business are generated, including:

[0067] Step 302: Based on the verification environment information, query the default verification rules for logistics business in the preset rule verification table.

[0068] It should be noted that the default verification rules configured for different logistics businesses are uniformly stored in the preset rule verification table, which makes it easy to directly query the default verification rules for the logistics business. Furthermore, during the rule verification of the current logistics business, the default verification rules stored in the preset rule verification table may not meet the user's verification needs. Therefore, the default verification rules can be manually adjusted by setting adjustment commands.

[0069] As an example, step 302 includes: using the verification environment information as an index, querying the default verification rules for logistics operations in the preset rule verification table.

[0070] Step 304: Adjust the default verification rules to obtain the overall verification rules for logistics operations.

[0071] As an example, step 304 includes: adjusting the default verification rules according to the rule adjustment instructions input by the user to obtain the total verification rules for the logistics business.

[0072] In this embodiment, by pre-setting a preset rule verification table, the default verification rules configured for different logistics businesses are integrated into the preset rule verification table. This allows for direct lookup of matching default verification rules based on the verification environment information during the logistics business rule verification process. Finally, the default verification rules for the logistics business are adjusted based on the user's input rule adjustment command to obtain the overall verification rules for the logistics business. This achieves the goal of matching the overall verification rules for the logistics business in real time based on user needs, rather than always relying on the default verification rules for logistics business verification. Therefore, this lays the foundation for improving the verification efficiency of logistics business rules and enhances the flexibility of logistics business verification.

[0073] In one embodiment, the default verification rules are adjusted to obtain the overall verification rules for the logistics business, which include at least one of the following:

[0074] Adjust the default rule validation chain of the default validation rule and use the adjusted default validation rule as the overall validation rule; adjust the default rule validation component of the default validation rule and use the adjusted default validation rule as the overall validation rule; adjust both the default rule validation chain and the default rule validation component of the default validation rule and use the adjusted default validation rule as the overall validation rule.

[0075] It should be noted that the methods for adjusting default validation rules vary depending on the application scenario requirements. For example, when adjusting default validation rules, one can adjust the default rule validation component, the default rule validation chain, or both simultaneously. Specifically, when adjusting the default rule validation component, one can add a preset rule validation component or modify one or more rule validation components within the default rule validation component. When adjusting the default rule validation chain, one can modify the component validation order of the default rule validation chain. Adjusting both the default rule validation chain and the default rule validation component can be understood as modifying both the component form of the default rule validation component and the execution order of the different rule validation components.

[0076] As an example, the default rule verification link of the default verification rule is updated, and the overall verification rule for logistics business is generated based on the updated default rule verification link and the default rule verification component under the default verification rule; the default verification rule component of the default verification rule is modified, and the overall verification rule for logistics business is generated based on the modified default verification rule component and the default rule verification link under the default verification rule; the default rule verification link is updated to obtain the updated default rule verification link, the default rule verification component is updated to obtain the updated default rule verification component, and the default rule verification link and the default rule verification component are integrated together to form the overall verification rule for logistics business.

[0077] In this embodiment, during the adjustment of the default verification rules, the default rule verification link can be adjusted separately, the default rule verification component can be adjusted separately, or the default rule verification link and the default rule verification component can be adjusted together based on the actual needs of the verification scenario. This ensures that the adjusted total verification rules can actually match the application requirements of the scenario, thus laying a foundation for further improving the flexibility of verification for logistics business rules.

[0078] In one embodiment, the default rule validation chain and the default rule validation component are adjusted together, including:

[0079] Query the verification idle time points under the default rule verification link; based on the verification idle time points, update the default rule verification link, and deploy the preset rule verification component at the verification idle time points.

[0080] It should be noted that during the joint adjustment of the default rule verification link and the default rule verification component, the busy verification time point under the overall verification rule of the logistics business can be determined. The busy verification time point is the time point when the default rule verification component is deployed for verification. That is, in order not to affect the execution of the existing default rule verification component, the preset rule verification component is inserted into the query-obtained idle verification time point. When the preset rule verification component is set at the idle verification time point, it can be understood that the default rule verification link of the default verification rule is updated due to the update of the idle verification time point, thus completing the joint adjustment of the default rule verification link and the default rule verification component.

[0081] As an example, the overall verification time period of the default rule verification chain is obtained. Based on the time identifier of each default rule verification component, the verification idle time points under the default rule verification chain are extracted within the overall verification time period. Based on the verification idle time points, the default rule verification chain is updated, and the preset rule verification components are deployed at the verification idle time points.

[0082] In this embodiment, during the joint adjustment of the default rule verification link and the default rule verification component, the verification idle time point under the default rule verification link can be directly located, and the default rule verification link can be updated through the verification idle time point. The preset rule verification component is deployed at the verification idle time point, thereby achieving the purpose of synchronous updating of the default rule verification link and the default rule verification component. Therefore, the verification effect of logistics business rule verification is improved.

[0083] Understandably, the above logistics business verification method can be implemented based on LiteFlow. Using LiteFlow to implement business orchestration can achieve parallel verification. Verification rules can be dynamically configured according to scenarios and systems. Adding new systems and scenarios does not require code development; only rule configuration needs to be added.

[0084] In one embodiment, based on the rule validation chain, the current rule validation item is selected from all rule validation items of multiple rule validation components, including:

[0085] Based on the rule verification chain, candidate rule verification components are filtered from multiple rule verification components, where each candidate rule verification component includes multiple candidate rule verification items; based on the verification priority of the multiple candidate rule verification items, the current rule verification item is selected from the multiple candidate rule verification items.

[0086] It should be noted that during the selection of the current rule verification item, since the verification priorities of rule verification items of different rule verification components and rule verification items of the same rule verification component are different, when selecting the current rule verification item from all rule verification items, in addition to selecting according to the execution order given by the rule verification chain, it can also be selected based on the verification priority of different candidate rule verification items.

[0087] As an example, based on the relationship between the verification timing of the rule verification chain and the preset timing threshold, multiple rule verification components are divided to obtain candidate rule verification components, where each candidate rule verification component includes multiple candidate rule verification items. Based on the verification resources of these multiple candidate rule verification items, the verification priority of each candidate rule verification item is determined, and the current rule verification item is selected from among the multiple candidate rule verification items based on the verification priority. This embodiment selects the current rule verification item sequentially based on the verification priority of all rule verification items in multiple candidate rule verification components, thus ensuring that rule verification items with higher verification priority are selected first. Therefore, this lays the foundation for further improving the verification effect of logistics business rule verification.

[0088] In one embodiment, the logistics business information to be verified is verified according to the current rule verification item, resulting in a verification sub-result for the logistics business rule verification item, including:

[0089] Based on the verification dimension to which the current rule verification item belongs, extract the target business information to be verified from the business information to be verified. The verification dimension includes at least one of the following: identity verification dimension, service verification dimension, permission verification dimension, and security verification dimension. Based on the verification conditions of the current rule verification item, verify the target business information to be verified to obtain the information verification results of the logistics business under each verification dimension. Based on the information verification results, generate the verification sub-results of the rule verification items of the logistics business.

[0090] It should be noted that rule verification for different logistics businesses involves multiple verification dimensions. Specifically, the dimensions involved in rule verification for logistics businesses can be divided into at least one of the following: identity verification dimension, service verification dimension, permission verification dimension, and security verification dimension. For example, in one feasible approach, assuming the logistics business is a monthly settlement order management business, the rule verification component under the identity verification dimension includes a monthly settlement card number validity verification component. Its specific verification logic is as follows: obtain the monthly settlement card number information cache data, determine the monthly settlement card number status, if it is in an effective or pre-cancellation state, the verification passes; if it is in a draft, pending, pre-effective, or cancelled state, the verification fails; determine whether the monthly settlement card number is frozen. If the card number is frozen, the verification will fail; if it is unfrozen, the verification will pass. Only if the monthly billing card number is in an active or pre-cancellation state and not frozen can the final verification pass. The rule verification components under the service verification dimension include branch verification - branch management verification component, branch verification - whether branch verification is required component, and branch verification - out-of-area branch verification component, etc. The rule verification components under the permission verification dimension include whitelist validity verification component, same-city whitelist validity verification component, enterprise ID management verification component, card number branch whitelist component, etc. The rule verification components under the security verification dimension include channel verification - whether channel verification is required component, channel whitelist validity verification component, and channel access code verification component, etc. In the network verification - network management verification component, the verification logic is as follows: It retrieves the cached data of the monthly settlement card number information; checks if the network address of the monthly settlement card number is empty; if empty, the verification fails; otherwise, it passes. It also checks if the network address code of the sending address is empty; if empty, the verification fails; otherwise, it passes. Finally, it checks if the network address code of the sending address is the same as the network address code of the monthly settlement card number; if different, the verification fails; if the same, it passes. Only when the monthly settlement card number is not empty, the network address code is not empty, and the network address code of the sending address is valid. The district / department to which the card belongs must be the same as the district / department to which the monthly billing card number belongs for the final verification to pass. The verification logic of the "Point Verification - Is Point Verification Required?" component is as follows: Determine whether point verification is required. If the passed point parameter is empty, point verification is not required. If it is not empty, point verification is required. The verification logic of the "Channel Verification - Is Channel Verification Required?" component is as follows: Obtain the monthly billing card number information cache. Determine whether the monthly billing card number information cache exists. If it exists, continue with the following verification. If it does not exist, the verification fails. Determine whether channel access code verification is required. If the channel access code in the monthly billing card number information cache is empty, channel access code verification is not required. If the channel access code in the monthly billing card number information cache is not empty, channel access code verification is required.The validation logic of the whitelist validity verification component is as follows: First, retrieve the local cache to check if the order restriction switch exists. If the switch value is "true", continue with the following validation; otherwise, return "whitelist validation passed". Next, retrieve the monthly settlement card number information cache and check if it exists. If it exists, continue with the following validation; otherwise, return "validation failed". Then, check if the orderer's mobile phone number and the sender's mobile phone number are empty. If they are not empty, continue with the following validation; otherwise, return "validation failed". Finally, call the monthly settlement management interface to query if order restrictions exist. If the order restriction switch is not enabled, the validation passes. If the order restriction is enabled and the item is in the whitelist, the validation passes. If the order restriction is enabled but the item is not in the whitelist, the validation fails. The local whitelist validity verification component orchestrates by first retrieving the local cache to check if the order restriction switch exists. If the switch value is "true", continue with the following validation; otherwise, return "local whitelist validation passed". The list verification passed; retrieve the monthly billing card number information cache, check if the cache exists, if it exists, continue with the following verification, otherwise return verification failed directly; check if the orderer's mobile phone number and the sender's mobile phone number are empty, if not empty, continue with the following verification; call the monthly billing manager's local whitelist interface to query if there are order restrictions, if the order restriction switch is not turned on, the verification passed, if the order restriction is turned on and it is in the whitelist, the local whitelist verification passed, if the order restriction is turned on but it is not in the whitelist, the local whitelist verification failed; the specific verification logic of the enterprise ID management verification component is as follows: retrieve the monthly billing card number information cache, check if the cache exists, if it exists, continue with the following verification, otherwise return verification failed directly; check if the monthly billing card number information has blocked sensitive billing information, if it is plaintext, return that the monthly billing card number does not support SF ID ordering, verification failed, if it is encrypted, return verification passed. The specific verification logic of the card number and branch whitelist verification component is as follows: Retrieve the monthly billing card number information cache, check if the cache exists. If it exists, continue with the following verification; otherwise, return "verification failed". Check if the passed-in branch code parameter is empty. If it is empty, return "branch code empty" and "verification failed". Check if the monthly billing card number and branch are in the whitelist. If they are, the verification passes; otherwise, the verification fails and "branch code mismatch" is returned. The specific verification logic of the channel whitelist validity verification component is as follows: First, retrieve whether the order restriction switch exists from the local cache. If the switch value is "true", continue with the following verification; otherwise, return "channel whitelist verification passed". Retrieve the monthly billing card number information cache, check if the cache exists. If it exists, continue with the following verification; otherwise, return "verification failed". Check if the orderer's mobile phone number and the sender's mobile phone number are empty. If they are not empty, continue with the following verification; otherwise, return "verification failed".The system calls the Monthly Settlement Manager API to check for order restrictions. If the order restriction switch is not enabled, it returns an error indicating a mismatch between the ordering channel and the verification fails. If the channel is in the whitelist, the verification passes. If the order restriction is enabled and the channel is not in the whitelist, it returns an error indicating that the channel is not in the whitelist and the verification fails. The specific verification logic of the channel access code verification component is as follows: It retrieves the cached Monthly Settlement Card Number information and checks if the cache exists. If it exists, it continues with the following verification; otherwise, it directly returns a verification failure. It checks whether the passed channel and access code are consistent with the channel access code in the Monthly Settlement Card Number cache. If they are consistent, the verification passes; otherwise, the ordering channel is mismatched, and the verification fails. The specific verification logic of the branch verification - out-of-area branch verification component is as follows: Retrieve the monthly billing card number information cache; check if the cache exists; if it exists, continue with the following verification; otherwise, return a verification failure. Check if the input parameter, the branch code, is empty; if it is not empty, continue with the following verification; otherwise, return that the branch code is empty, and the verification fails. Retrieve if the monthly billing card number out-of-area to third-party agreement personalized cache exists; if it exists, continue with the following verification; otherwise, return that the branch code does not match, and the verification fails. Check if the monthly billing card number to out-of-area third-party agreement personalized cache contains freight transfer to a third party and... Fixed service points are configured. If the monthly billing card number and the input service point code are in the cache of the fixed service point for third-party users outside the region, the verification passes. Next, it checks if the input service point code is in the fixed service point of the third-party agreement outside the region; if so, the verification passes. Then, it checks if the input service point code exists in the parent service point of the third-party service within the region; if so, the verification passes; otherwise, it returns a service point code mismatch. Finally, it checks if the input service point code exists in the mapped service point corresponding to the express delivery service point or heavy freight service point; if so, the verification passes; otherwise, it returns a service point code mismatch and the verification fails. If the monthly billing card number is transferred to an external third-party agreement in the personalized cache, and there is no fixed branch, the verification passes; otherwise, it returns a branch code mismatch and the verification fails. The specific verification logic of the branch verification - intra-regional branch verification component is as follows: Retrieve the monthly billing card number information cache, check if the cache exists, if it exists, continue with the following verification; otherwise, directly return that the monthly billing card number does not exist and the verification fails; check if the input parameter branch code is empty, if it is not empty, continue with the following verification; otherwise, return that the branch code is empty and the verification fails; check if the order verification intra-regional branch verification switch is turned on. If the switch value is... If the condition is "true" and the branch code of the input parameter belongs to the Hong Kong region and the monthly billing card number of the input parameter is in the whitelist cache of the third-party agreement within the transfer region, then the verification passes; otherwise, continue with the following verification: Check if the branch code of the input parameter is in the fixed branch of the third-party agreement within the transfer region; if so, the verification passes; Check if the branch code of the input parameter exists in the parent branch of the third-party agreement within the transfer region; if so, the verification passes; otherwise, return a branch code mismatch and the verification fails.The system checks if the input branch code exists in the mapped branch for either the express delivery branch or the heavy freight branch. If it does, the validation passes; otherwise, it returns a branch code mismatch and the validation fails.

[0091] As an example, based on the verification dimension to which the current rule verification item belongs, the target business information to be verified is extracted from the business information to be verified. The verification dimension includes at least one of the following: identity verification dimension, service verification dimension, permission verification dimension, and security verification dimension. The matching relationship between the target business information to be verified and the verification conditions of the current rule verification item is detected to determine the information verification results of the logistics business under each verification dimension. The information verification results are then integrated into the verification sub-results of the rule verification items of the logistics business.

[0092] In this embodiment, the target business information to be verified is determined by the verification dimension to which the current rule verification item belongs, so as to enable accurate matching between the current rule verification item and the target business information to be verified. In other words, it lays the foundation for the subsequent verification process and effectively avoids the defect of incorrectly selecting the business information to be verified. Therefore, it further improves the verification efficiency of logistics business rule verification.

[0093] In one embodiment, based on the verification results of each piece of information, a verification sub-result for the rule verification items of the logistics business is generated, including:

[0094] By integrating the verification results of various information and the corresponding verification dimension weights, the verification quality index of the rule verification item for logistics business is obtained; if the verification quality index is greater than the preset verification quality index threshold, a verification sub-result for the current rule verification item is generated; if the verification quality index is less than or equal to the preset verification quality index threshold, a verification sub-result for the current rule verification item is generated.

[0095] It should be noted that in the process of generating the verification sub-results of the rule verification items for logistics business, the degree of influence of the information verification results under different verification dimensions on the verification sub-results varies. Therefore, different verification dimension weights can be set for different information verification results, thereby realizing the quantification of the verification quality assessment of the rule verification items for logistics business, that is, obtaining the verification quality index, and finally using the verification quality index to generate the verification sub-results.

[0096] As an example, based on the verification results of each piece of information and the corresponding verification dimension weights, the verification quality index of the rule verification items for logistics business is calculated; if the verification quality index is greater than the preset verification quality index threshold, a verification sub-result for the current rule verification item that has passed verification is generated; if the verification quality index is less than or equal to the preset verification quality index threshold, a verification sub-result for the current rule verification item that has failed verification is generated.

[0097] In this embodiment, by setting different verification dimension weights for different information verification results, a quantitative evaluation of the verification quality of rule verification items is achieved. Based on the quantitative evaluation of verification quality, a verification sub-result for the current rule verification item is finally generated, thereby realizing the transformation of the verification of the current rule verification item from qualitative to quantitative. Therefore, it lays the foundation for improving the verification accuracy of logistics business rule verification.

[0098] The logistics business rule verification method in this embodiment integrates business rule conditions sequentially through rule verification items and rule verification components, transforming the hard-code development process for logistics business into a rule verification item configuration process. Since both rule verification items and rule verification components can pre-integrate business rule conditions, no hard-code development is required during the verification process. Therefore, it overcomes the technical defect that the large and complex rule verification scenario of logistics business leads to an excessively long hard-code development cycle, which in turn makes the rule verification of logistics business time-consuming. Thus, it improves the verification efficiency of logistics business rules.

[0099] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0100] Based on the same inventive concept, this application also provides a logistics business rule verification device for implementing the logistics business rule verification method described above. The solution provided by this device is similar to the implementation described in the above method; therefore, the specific limitations in one or more embodiments of the logistics business rule verification device provided below can be found in the limitations of the logistics business rule verification method described above, and will not be repeated here.

[0101] In one exemplary embodiment, such as Figure 3 As shown, a logistics business rule verification device is provided, including: a generation module 401, a selection module 402, a first verification module 403, and a second verification module 404, wherein:

[0102] The generation module 401 is used to generate the overall verification rules for the logistics business based on the verification environment information of the logistics business. The overall verification rules include multiple rule verification components and rule verification links, and the multiple rule verification components are independent of each other.

[0103] The selection module 402 is used to select the following step: based on the rule verification link, select the current rule verification item from all rule verification items of the plurality of rule verification components;

[0104] The first verification module 403 is used to verify the business information to be verified of the logistics business according to the current rule verification item, and obtain the verification sub-result of the rule verification item of the logistics business.

[0105] The second verification module 404 is used to return to the selection step after the current rule verification item has been verified, until all rule verification items have been selected, and obtain the total verification result corresponding to all the verification sub-results.

[0106] In one embodiment, the generation module 401 is further configured to:

[0107] Based on the verification environment information, the default verification rule for the logistics business is queried in the preset rule verification table; the default verification rule is adjusted to obtain the total verification rule for the logistics business.

[0108] In one embodiment, the generation module 401 is further configured to:

[0109] The default rule verification link of the default verification rule is adjusted, and the adjusted default verification rule is used as the total verification rule; the default rule verification component of the default verification rule is adjusted, and the adjusted default verification rule is used as the total verification rule; the default rule verification link and the default rule verification component of the default verification rule are both adjusted, and the adjusted default verification rule is used as the total verification rule.

[0110] In one embodiment, the generation module 401 is further configured to:

[0111] Query the verification idle time point under the default rule verification link; update the default rule verification link according to the verification idle time point, and deploy the preset rule verification component at the verification idle time point.

[0112] In one embodiment, the selection module 402 is further configured to:

[0113] According to the rule verification link, candidate rule verification components are filtered among the plurality of rule verification components, wherein the candidate rule verification components include a plurality of candidate rule verification items; according to the verification priority of the plurality of candidate rule verification items, the current rule verification item is selected from the plurality of candidate rule verification items.

[0114] In one embodiment, the first verification module 403 is further configured to:

[0115] Based on the verification dimension to which the current rule verification item belongs, the target business information to be verified is extracted from the business information to be verified, wherein the verification dimension includes at least one of the following four dimensions: identity verification dimension, service verification dimension, permission verification dimension, and security verification dimension; based on the verification conditions of the current rule verification item, the target business information to be verified is verified to obtain the information verification results of the logistics business under each of the verification dimensions; based on each of the information verification results, the verification sub-results of the rule verification items of the logistics business are generated.

[0116] In one embodiment, the first verification module 403 is further configured to:

[0117] By integrating the verification results of each piece of information and the corresponding verification dimension weights, a verification quality index for the rule verification item of the logistics business is obtained; if the verification quality index is greater than a preset verification quality index threshold, a verification sub-result is generated indicating that the current rule verification item has passed verification; if the verification quality index is less than or equal to the preset verification quality index threshold, a verification sub-result is generated indicating that the current rule verification item has failed verification.

[0118] Each module in the aforementioned logistics business rule verification device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0119] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 4As shown. The computer device includes a processor, memory, input / output interface, communication interface, display unit, and input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interface. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The input / output interface is used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a logistics business rule verification method. Those skilled in the art will understand that... Figure 4 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0120] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0121] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0122] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0123] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0124] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0125] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for validating logistics business rules, characterized in that, The method includes: Based on the verification environment information of the logistics business, a general verification rule for the logistics business is generated, wherein the general verification rule includes multiple rule verification components and rule verification links, and the multiple rule verification components are independent of each other; Selection step: Based on the rule verification link, select the current rule verification item from all rule verification items of the multiple rule verification components; Based on the current rule verification item, the business information to be verified in the logistics business is verified to obtain the verification sub-result of the rule verification item of the logistics business. If the current rule verification item is verified, return to the selection step until all rule verification items have been selected, and obtain the total verification result corresponding to all the verification sub-results.

2. The method according to claim 1, characterized in that, The step of generating the overall verification rules for the logistics business based on the verification environment information of the logistics business includes: Based on the verification environment information, query the default verification rule for the logistics business in the preset rule verification table; The default verification rules are adjusted to obtain the overall verification rules for the logistics business.

3. The method according to claim 2, characterized in that, The adjustment of the default verification rules to obtain the overall verification rules for the logistics business shall include at least one of the following: The default rule verification link of the default verification rule is adjusted, and the adjusted default verification rule is used as the total verification rule; The default rule validation component of the default validation rule is adjusted, and the adjusted default validation rule is used as the total validation rule. The default rule verification link and default rule verification component of the default verification rule are adjusted together, and the adjusted default verification rule is used as the total verification rule.

4. The method according to claim 3, characterized in that, The adjustment of the default rule verification link and the default rule verification component includes: Query the verification idle time points under the default rule verification link; Based on the verification idle time point, update the default rule verification link and deploy the preset rule verification component at the verification idle time point.

5. The method according to claim 1, characterized in that, The step of selecting the current rule verification item from all rule verification items of the plurality of rule verification components according to the rule verification link includes: Based on the rule verification link, candidate rule verification components are selected from the plurality of rule verification components, wherein the candidate rule verification components include a plurality of candidate rule verification items; Based on the verification priority of the plurality of candidate rule verification items, the current rule verification item is selected from the plurality of candidate rule verification items.

6. The method according to claim 1, characterized in that, The step of verifying the logistics business information to be verified according to the current rule verification item to obtain the verification sub-result of the rule verification item of the logistics business includes: Based on the verification dimension to which the current rule verification item belongs, extract the target business information to be verified from the business information to be verified, wherein the verification dimension includes at least one of the following four: identity verification dimension, service verification dimension, permission verification dimension, and security verification dimension. Based on the verification conditions of the current rule verification item, the target business information to be verified is verified to obtain the information verification results of the logistics business under each verification dimension; Based on the verification results of each piece of information, a verification sub-result is generated for the rule verification items of the logistics business.

7. The method according to claim 6, characterized in that, The step of generating a verification sub-result for the rule verification item of the logistics business based on the verification results of each of the aforementioned information includes: By integrating the verification results of each piece of information and the corresponding verification dimension weights, the verification quality index of the rule verification item of the logistics business is obtained. If the verification quality index is greater than the preset verification quality index threshold, a verification sub-result is generated indicating that the current rule verification item has passed verification. If the verification quality index is less than or equal to the preset verification quality index threshold, a verification sub-result is generated indicating that the current rule verification item has failed verification.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images