Automatic charging engine configuration method and platform combining protocol and service data

Abstract

The invention discloses an automatic charging engine configuration method and platform combining a protocol and service data, and relates to the technical field of automatic charging, and the method comprises the following steps: S1, establishing a rule quantizer for a user to configure a charging rule in a protocol, and operating the quantized charging rule; s2, establishing an element extractor used for identifying a unique field of the service data and obtaining a charging element corresponding to the service data, and running to obtain the charging element; s3, establishing an adaptive trigger comprising a trigger, a protocol / rule set matcher and a rule meshing device, and running to obtain a specific charging rule entry needing to be executed; and S4, establishing a data processor comprising a calculator, a generator and a collection and payment processor, and running the data processor to obtain a charging result. The method and the device have the effect of meeting the automatic charging requirement more flexibly.

Description

Technical Field

[0001] The present application relates to the field of automatic billing technology, and in particular to a method and platform for configuring an automatic billing engine that combines protocols and business data. Background Art

[0002] The billing of transactions and business contracts traditionally relies on manual work with the help of calculators and abacus, which has low work efficiency and cannot meet the increasing billing needs of large trading venues. For this reason, systems / platforms with billing functions and billing modules are gradually being introduced on the market.

[0003] However, the existing above-mentioned system / platform has the following problems: the billing model lacks flexibility and cannot actively adapt to actual business, so this application proposes a new technical solution. Summary of the invention

[0004] In order to more flexibly meet the needs of automatic billing, the present application provides an automatic billing engine configuration method and platform that combines protocol and business data.

[0005] In a first aspect, the present application provides a method for configuring an automatic billing engine combining protocols and service data, using the following technical solutions:

[0006] A method for configuring an automatic billing engine combining protocol and service data, comprising:

[0007] S1. Establish a rule quantifier for users to configure the billing rules in the protocol, and run the quantified billing rules; wherein the configurable content includes one or more of the following: fee items, unit prices, currencies, settlement units, billing methods, reference elements, trigger methods, trigger conditions, hierarchical logical relationships of billing conditions, billing hit matching conditions, agency collection items, agency collection tax rates, protocol unique identifiers, and matching types;

[0008] S2. Establish an element extractor for identifying a unique field of business data and obtaining a billing element corresponding to the business data, and execute the extractor to obtain the billing element;

[0009] S3, establish an adaptation trigger including a trigger, a protocol / rule set matcher, and a rule mesher, and run it to obtain the specific billing rule entry that needs to be executed;

[0010] The trigger is used to trigger charging according to the content configured by the rule quantizer, the protocol / rule set matcher is used to match the service and the rule set according to the content configured by the rule quantizer, and the rule mesher is used to filter the charging rule items that need to be specifically executed according to the content configured by the rule quantizer;

[0011] S4, establishing a data processor including a calculator, a generator, and a collection and payment processor, and running the processor to obtain the billing result;

[0012] Among them, the calculator is used to perform calculations according to the content configured by the rule quantizer, the generator is used to package the results calculated by the calculator according to the content configured by the rule quantizer, and the collection and payment processor is used to perform secondary processing on the fee items generated by the generator according to the content configured by the rule quantizer to form corresponding collection items or payment items.

[0013] Optionally, the fee item maintenance, the hierarchical logical relationship maintenance of the billing conditions, and the billing hit matching condition maintenance are carried out in a tree or other parent-child structure, and the lower-level items store the unique identifiers of the upper items.

[0014] Optionally, the feature extractor preloads business data information based on the big data unit and / or the OCR unit.

[0015] Optionally, the triggering mode of the trigger includes one or more of timed triggering, conditional triggering, and manual triggering.

[0016] Optionally, the regular mesher has multiple working modes, including:

[0017] If the current billing is normal, the rule mesher takes the data with the highest priority as the result;

[0018] If the current calculation is in a step-by-step manner and the maximum / minimum billing rules are used, the rule mesher adopts all meshing results, and after calculation, sums the results according to the corresponding rules and takes the maximum / minimum value.

[0019] Optionally, the rule mesher hits the specific charging rule entry that needs to be executed through a preset pruning algorithm.

[0020] Optionally, the payment and receipt of the billing results are reversely fitted and the fee information is deformed.

[0021] In the second aspect, the present application provides an automatic billing platform combining protocols and service data, using the following technical solutions:

[0022] An automatic billing platform combining protocol and business data, comprising:

[0023] A rule quantizer, which is used for allowing users to configure charging rules in the protocol and running the quantified charging rules;

[0024] An element extractor, which is used to identify a unique field of business data and obtain the corresponding billing element of the business data, and to obtain the billing element by running;

[0025] Adaptation trigger, which includes a trigger, a protocol / rule set matcher, and a rule mesher, and is operated to obtain specific charging rule items that need to be executed; wherein the trigger is used to trigger charging according to the content configured by the rule quantizer, the protocol / rule set matcher is used to match the service and the rule set according to the content configured by the rule quantizer, and the rule mesher is used to screen the charging rule items that need to be specifically executed according to the content configured by the rule quantizer;

[0026] A data processor, which includes a calculator, a generator, and a data processor of a collection and payment processor and operates to obtain billing results; wherein the calculator is used to perform calculations according to the content configured by the rule quantizer, the generator is used to package the results calculated by the calculator according to the content configured by the rule quantizer, and the collection and payment processor is used to perform secondary processing on the fee items generated by the generator according to the content configured by the rule quantizer to form corresponding collection items or payment items.

[0027] In summary, the present application includes the following beneficial technical effects: it can be applied to most information systems or system groups with protocols and business data to achieve configurable automatic billing, is suitable for most quantifiable billing rule scenarios, and can more flexibly meet automatic billing needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 It is a schematic diagram of the overall application process;

[0029] Figure 2 It is a schematic diagram of the operation of the rule quantizer of the present application;

[0030] Figure 3 It is a schematic diagram of the quantitative billing conditions case of this application;

[0031] Figure 4 is a schematic diagram of the operation of the feature extractor of the present application;

[0032] Figure 5 is a schematic diagram of the operation of the adaptation trigger of the present application;

[0033] Figure 6 is a schematic diagram of the operation of the data processor of the present application;

[0034] Figure 7 Schematic diagram of other parent-child structures of this application;

[0035] Figure 8 for Figure 7 Schematic diagram when displayed in a tree structure. DETAILED DESCRIPTION

[0036] The following is combined with Figure 1-7 This application is described in further detail.

[0037] The embodiment of the present application discloses a method for configuring an automatic billing engine that combines protocols and business data. The method can be applied to most information systems or system groups with protocols and business data to achieve configurable automatic billing. It is suitable for most quantifiable billing rule scenarios and can more flexibly meet automatic billing needs.

[0038] Reference Figure 1-Figure 6 , the automatic billing engine configuration method combining protocol and business data includes:

[0039] S1. Establish a rule quantizer for users to configure the charging rules in the protocol, and run it to obtain the quantized charging rules.

[0040] Among them, the configurable content includes one or more of fee items, unit price, currency, settlement unit, billing method, reference elements, trigger method, trigger conditions, hierarchical logical relationship of billing conditions, billing hit matching conditions, collection items, collection tax rate, unique protocol identifier, and matching (business) type.

[0041] The rule quantizer is implemented through the front-end page program + back-end program + database storage. For the front-end, the corresponding UI interface should have good page design and interactivity to facilitate users to easily configure the quantification rules; the back-end program is mainly responsible for receiving the data transmitted by the front-end, verifying and storing the configuration information in the database.

[0042] It should be noted that the maintenance of fee items, the hierarchical logical relationship maintenance of billing conditions, and the maintenance of billing hit matching conditions are carried out in a tree or other parent-child structure, and the lower-level items store the unique identifier of the upper item. Specifically:

[0043] The rule branching logic uses a tree or other parent-child structure as a carrier. It is necessary to consider the parent-child attribute relationship of the rule items during design, and use the child item to store the unique identifier of the parent item to implement the storage of the parent-child attribute relationship. The front-end can also further visually enhance the logic of the parent-child attributes by folding and expanding the tree during design.

[0044] S2. Establish an element extractor for identifying the unique field of business data and obtaining the billing element corresponding to the business data, and run it to obtain the billing element.

[0045] In this embodiment, the factor extractor is implemented using database technology. When the performance requirements are not high, the business data table can be queried through database views or stored procedures, and the column-to-row method can be used to achieve unlimited extraction and expansion of billing factors. In scenarios with high performance requirements, it is recommended to use stored procedures or background program processing to update the billing factors of the corresponding business items in a special billing factor table when the business data is entered or changed, so that the billing factors can be obtained more efficiently during triggering, judgment and billing.

[0046] In another embodiment of the present application, the feature extractor preloads the business data information based on the big data unit and / or the OCR unit, specifically:

[0047] Based on big data unit: The platform implementing this method can analyze the commonly used billing elements in the industry, automatically list multiple billing elements with a high probability of use according to the billing ratio or weight, and preload them before the user actually uses them.

[0048] Based on the OCR unit: read the protocol content uploaded by the user, analyze the keyword frequency and weight of the elements appearing in the text, and preload the elements.

[0049] S3. Establish an adaptation trigger including a trigger, a protocol / rule set matcher, and a rule mesher, and run the trigger to obtain the specific billing rule entry that needs to be executed.

[0050] The trigger is used to trigger charging according to the content configured by the rule quantizer. The triggering mode of the trigger includes one or more of timing triggering, condition triggering, and manual triggering. Specifically:

[0051] Scheduled triggering uses a timer to trigger the engine for billing after the set time is reached; conditional triggering is a monitoring triggering method based on specified conditional values. After the corresponding monitored elements meet the configured conditions, the engine is triggered for billing; manual triggering is usually provided in the form of a call interface for other functions. After receiving the call instruction, the engine is immediately triggered for billing. Triggers are generally implemented through database technology or background programs. If database technology is used, database timers, triggers, and stored procedures are generally used to implement timing, conditional, and manual triggering; if background programs are used, they are generally implemented using scheduled tasks and polling trigger conditions.

[0052] The protocol / rule set matcher is used to match services and rule sets according to the content configured by the rule quantifier. Specifically: in a system with protocols and service data, services are usually carried out according to a certain protocol. Through the unique protocol identifier configured by the rule quantifier and the matching service type content, the protocol / rule set matcher can find the billing rule set that needs to be executed for the service that needs to be billed. The protocol matcher is generally implemented based on a database query statement, using the protocol and service type attributes of the service data to search for the billing rule set containing the same attributes.

[0053] The rule mesher is used to filter the billing rule items that need to be executed according to the content configured by the rule quantizer. Specifically: according to the hierarchical logical relationship of the billing conditions configured by the rule quantizer and the billing hit matching conditions, the rule mesher can combine the billing elements raised by the element extractor to strip the billing rules with a hierarchical structure and determine the specific billing rule items that need to be executed.

[0054] The difficulty of the rule mesher lies in how to hit the specific billing rule items that need to be executed. Under the tree-shaped hierarchical logic, the preset pruning algorithm is used to implement it, that is, starting from the parent node, the entire billing rule set is polled layer by layer. If it is determined that the triggering condition of a billing item is met, the child items of the billing item will continue to be polled until a billing item without child items is hit, that is, the specific billing rule item that needs to be executed is hit, and other items that do not meet the triggering conditions or are not polled are "pruned" and not executed. This algorithm is basically equivalent to sequential search, and its time complexity is O(n), but the billing efficiency can be improved by artificially writing the billing rule items with a higher probability of concentration in the front position. In other special billing scenarios, other algorithms can also be considered to continue to optimize billing efficiency.

[0055] It should be noted that the regular mesher has multiple working modes, including:

[0056] If the current billing is normal, the rule mesher takes the data with the highest priority as the result;

[0057] If the current calculation is in a step-by-step manner and the maximum / minimum billing rules are used, the rule mesher adopts all meshing results, and after calculation, sums the results according to the corresponding rules and takes the maximum / minimum value.

[0058] In particular, under billing modes such as tiered billing and maximum value billing, the mesher needs to return all meshing results for processing in the next link. The same pruning algorithm can be used, but it does not interrupt after hitting the target. Secondly, it continues to execute and return the result set.

[0059] S4. Establish a data processor including a calculator, a generator, and a collection and payment processor, and run them to obtain the billing result.

[0060] Among them, the calculator is used to perform calculations according to the content configured by the rule quantifier, specifically: based on the unit price, billing method, and reference elements, the actual calculation of the cost is performed. The billing method usually includes a simple unit price*quantity model, and more advanced billing methods such as tiered billing and compound interest billing can also be designed according to actual needs. When designing the program, different billing methods are written for different billing methods. When the calculation is executed, the method of calling the program is determined by the billing method configured on the billing item, and the unit price and billing elements are passed into the method through parameter passing to perform the operation and obtain the calculation result.

[0061] The generator is used to package the results of the calculator calculation according to the content configured by the rule quantizer, and to actually package the fee items according to the fee items, currencies, settlement units, etc., to form fee item data that can be stored and actually used. The generator is a packaging component that is implemented through a background program. The fee information configured on the billing item and the calculation results generated by the calculator are passed to the generator method through parameter passing to form a completed fee item data record, and the data record is stored in the database to complete the generation and storage of the billing results.

[0062] The collection and payment processor is used to perform secondary processing on the fee items generated by the generator according to the content configured by the rule quantizer to form corresponding collection items or payment items. It can reprocess and package the fee items according to the collection items and collection tax rates to form corresponding collection and payment items and form corresponding logical connections. The collection and payment processor is an enhanced generator based on actual business needs. It is implemented through a background program. The fee item data produced by the generator is called out from the database, combined with the collection and payment information configured on the fee item, and passed to the collection and payment processor method through parameter transmission. A new fee item data record is generated for storage, and the corresponding collection and payment fee item data record is updated at the same time to store the binding relationship between the two.

[0063] According to the above settings, this method can be applied to most information systems or system groups with protocols and business data to achieve configurable automatic billing. It is suitable for most quantifiable billing rule scenarios and can more flexibly meet automatic billing needs.

[0064] In the embodiments of the present application, other parent-child structures such as Figure 7 As shown, take the charging of loading and unloading fees of a certain unit as an example:

[0065] The first line is a layer;

[0066] The second to sixth rows are at the same level; the ninth row is at the same level; the twelfth row is at the same level; the fifteenth row is at the same level;

[0067] The seventh and eighth rows are on the same level; the tenth and eleventh rows are on the same level; the thirteenth and fourteenth rows are on the same level; the sixteenth and seventeenth rows are on the same level.

[0068] After the engine enters the fee calculation branch, it first matches and identifies the operation content in the order of loading → packing → stacking → belt scale calibration → loading → warehouse entry → loading → stacking. If a branch is hit, it enters the branch and determines whether the branch is a billing branch.

[0069] If it is a billing branch, it will be charged directly. If the branch has sub-branches, the sub-branches will continue to be judged in order until they are hit. If the record of loading and unloading is hit during the process, it is necessary to continue to judge whether it has been weighed.

[0070] If the above is presented in a tree diagram, you can refer to Figure 8 .

[0071] In another embodiment of the present application, the payment and receipt of the billing results are also reversely fitted and the fee information is deformed.

[0072] The purpose of the above steps is to bind the logical relationship between collection and payment. Reverse fitting and fee information deformation, example:

[0073] A project is outsourcing a certain operation process. One of the fee items is charged to customer (A) at RMB 1,000 per order, while the cost to supplier (B) is RMB 800 per order. Moreover, not only the unit price but also the tax rate and fee items are different.

[0074] That is, collection: 1,000 yuan / order, payment: 800 yuan / order.

[0075] Currently, there are the following requirements:

[0076] 1) In terms of business and financial approval, these two payment items still need to have a clear correlation, which is used to determine whether the payment item is a loss and clarify the cause of the expense during approval or statistics;

[0077] 2) There is a fixed algorithm for upper and lower fees, that is, the cost is 0.8 times the revenue. Especially in the case of large-scale billing, users do not want to maintain the fee items and then maintain the payment items again.

[0078] Based on the above example and two requirements, this application further performs: reverse fitting and fee information deformation.

[0079] The embodiment of the present application also discloses an automatic billing platform that combines protocols and business data.

[0080] An automated billing platform that combines agreement and business data, including:

[0081] A rule quantizer, which is used for allowing users to configure charging rules in the protocol and running the quantified charging rules;

[0082] An element extractor, which is used to identify a unique field of business data and obtain the corresponding billing element of the business data, and to obtain the billing element by running;

[0083] Adaptation trigger, which includes a trigger, a protocol / rule set matcher, and a rule mesher, and is operated to obtain specific charging rule items that need to be executed; wherein the trigger is used to trigger charging according to the content configured by the rule quantizer, the protocol / rule set matcher is used to match the service and the rule set according to the content configured by the rule quantizer, and the rule mesher is used to screen the charging rule items that need to be specifically executed according to the content configured by the rule quantizer;

[0084] A data processor, which includes a calculator, a generator, and a data processor of a collection and payment processor and operates to obtain billing results; wherein the calculator is used to perform calculations according to the content configured by the rule quantizer, the generator is used to package the results calculated by the calculator according to the content configured by the rule quantizer, and the collection and payment processor is used to perform secondary processing on the fee items generated by the generator according to the content configured by the rule quantizer to form corresponding collection items or payment items.

[0085] The above composition has been described in the previous method embodiment, so it will not be repeated here.

[0086] The above are all preferred embodiments of the present application, and the protection scope of the present application is not limited thereto. Therefore, any equivalent changes made according to the structure, shape, and principle of the present application should be included in the protection scope of the present application.

Claims

1. A method for configuring an automatic billing engine combining protocol and service data, characterized in that: include: S1. Establish a rule quantifier for users to configure the billing rules in the protocol, and run the quantified billing rules; wherein the configurable content includes one or more of the following: fee items, unit prices, currencies, settlement units, billing methods, reference elements, trigger methods, trigger conditions, hierarchical logical relationships of billing conditions, billing hit matching conditions, agency collection items, agency collection tax rates, protocol unique identifiers, and matching types; S2. Establish an element extractor for identifying a unique field of business data and obtaining a billing element corresponding to the business data, and execute the extractor to obtain the billing element; S3, establish an adaptation trigger including a trigger, a protocol / rule set matcher, and a rule mesher, and run it to obtain the specific billing rule entry that needs to be executed; The trigger is used to trigger charging according to the content configured by the rule quantizer, the protocol / rule set matcher is used to match the service and the rule set according to the content configured by the rule quantizer, and the rule mesher is used to filter the charging rule items that need to be specifically executed according to the content configured by the rule quantizer; S4, establishing a data processor including a calculator, a generator, and a collection and payment processor, and running the processor to obtain the billing result; Among them, the calculator is used to perform calculations according to the content configured by the rule quantizer, the generator is used to package the results calculated by the calculator according to the content configured by the rule quantizer, and the collection and payment processor is used to perform secondary processing on the fee items generated by the generator according to the content configured by the rule quantizer to form corresponding collection items or payment items.

2. The method for configuring an automatic billing engine combining protocol and service data according to claim 1, characterized in that: The fee item maintenance, the hierarchical logical relationship maintenance of the charging conditions, and the charging hit matching condition maintenance are carried out in a tree or other parent-child structure, and the lower-level items store the unique identifiers of the upper items.

3. The method for configuring an automatic billing engine combining protocol and service data according to claim 2, characterized in that: The feature extractor preloads business data information based on the big data unit and / or the OCR unit.

4. The method for configuring an automatic billing engine combining protocol and service data according to claim 1, characterized in that: The triggering mode of the trigger includes one or more of timing triggering, condition triggering, and manual triggering.

5. The method for configuring an automatic billing engine combining protocol and service data according to claim 1, characterized in that: The regular mesher has multiple working modes, including: If the current billing is normal, the rule mesher takes the data with the highest priority as the result; If the current calculation is a step-by-step calculation and the maximum / minimum billing rules are used, the rule mesher adopts all meshing results, and after calculation, sums the results according to the corresponding rules and takes the maximum / minimum value.

6. The method for configuring an automatic billing engine combining protocol and service data according to claim 5, characterized in that: The rule mesher hits the specific charging rule items that need to be executed through a preset pruning algorithm.

7. The method for configuring an automatic billing engine combining protocol and service data according to claim 1, characterized in that: Reverse fitting and fee information deformation are performed on the payment and receipt of the billing results.

8. An automatic billing platform combining protocol and service data, characterized in that: include: A rule quantizer, which is used for allowing users to configure charging rules in the protocol and running the quantified charging rules; An element extractor, which is used to identify a unique field of business data and obtain the corresponding billing element of the business data, and to obtain the billing element by running; Adaptation trigger, which includes a trigger, a protocol / rule set matcher, and a rule mesher, and is operated to obtain specific charging rule items that need to be executed; wherein the trigger is used to trigger charging according to the content configured by the rule quantizer, the protocol / rule set matcher is used to match the service and the rule set according to the content configured by the rule quantizer, and the rule mesher is used to screen the charging rule items that need to be specifically executed according to the content configured by the rule quantizer; A data processor, which includes a calculator, a generator, and a data processor of a collection and payment processor and operates to obtain billing results; wherein the calculator is used to perform calculations according to the content configured by the rule quantizer, the generator is used to package the results calculated by the calculator according to the content configured by the rule quantizer, and the collection and payment processor is used to perform secondary processing on the fee items generated by the generator according to the content configured by the rule quantizer to form corresponding collection items or payment items.

Images