Method and platform for configuring automatic billing engine in combination with protocol and service data

Abstract

The application discloses a kind of automatic charging engine configuration method and platform combined with agreement and service data, it is related to automatic charging technical field, it includes: S1, the rule quantifier for establishing for user to configure the charging rule in agreement, running obtains quantized charging rule;S2, the element extractor for being used to identify the unique field of service data and obtain the charging element corresponding to the service data, running obtains charging element;S3, the trigger of establishing including trigger, agreement / rule set matcher, rule engagement, running obtains the specific charging rule entry needing execution;S4, the data processor including calculator, generator, collection and payment processor, running obtains charging result.The application has the effect that more flexible automatic charging demand can be satisfied.

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 using calculators and abacus, which is inefficient and cannot meet the increasingly diverse 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, this application provides an automatic billing engine configuration method and platform that combines protocol and business data.

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

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

[0007] S1. Establishing a rule quantizer for users to configure billing rules within the protocol and running the resulting quantified billing rules; wherein the configurable content includes one or more of the following: fee item, unit price, currency, settlement unit, billing method, reference element, trigger method, trigger condition, hierarchical logical relationship of billing conditions, billing hit matching condition, collection item, collection tax rate, protocol unique identifier, and matching type;

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

[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 entries that need to be executed;

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

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

[0012] The calculator is configured to calculate according to the content of the rule quantizer configuration, the generator is configured to wrap the result calculated by the calculator according to the content of the rule quantizer configuration, and the collection and payment processor is configured to perform secondary processing on the fee item generated by the generator according to the content of the rule quantizer configuration to form a corresponding collection item or payment item.

[0013] Optionally, the hierarchical logical relationship of the fee item maintenance, billing condition maintenance, and billing hit matching condition maintenance is maintained in a tree or other parent-child structure as a carrier, and the lower-level entries store the unique identifier of the upper entry.

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

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

[0016] Optionally, the working mode of the rule meshing device includes multiple modes, which include:

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

[0018] If the current is step calculation, the maximum / minimum billing rule is taken, the rule meshing device adopts all meshing results, and after calculation, the results are summed, the maximum / minimum value is processed according to the corresponding rule.

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

[0020] Optionally, the collection and payment of the billing result are reversely fitted and the fee item information is deformed.

[0021] In a second aspect, the application provides an automatic billing platform combining a protocol and business data, which adopts the following technical solution:

[0022] An automatic billing platform combining a protocol and business data includes:

[0023] A rule quantizer configured to allow a user to configure a billing rule in the protocol and run to obtain a quantized billing rule;

[0024] An element extractor configured to identify a unique field of business data and obtain a billing element corresponding to the business data, and run to obtain a billing element;

[0025] An adaptation trigger comprising a trigger, a protocol / rule set matcher, a rule engager, and running to get specific charging rule items that need to be executed; wherein the trigger is used for charging triggering according to the content of the rule quantifier configuration, the protocol / rule set matcher is used for matching service and rule set according to the content of the rule quantifier configuration, and the rule engager is used for screening charging rule items that need to be specifically executed according to the content of the rule quantifier configuration;

[0026] A data processor comprising a calculator, a generator, a data processor of a collection and payment processor, and running to get charging results; wherein the calculator is used for calculation according to the content of the rule quantifier configuration, the generator is used for packaging the results calculated by the calculator according to the content of the rule quantifier configuration, and the collection and payment processor is used for secondary processing of the items generated by the generator according to the content of the rule quantifier configuration, forming corresponding collection items or payment items.

[0027] In summary, the present application has the following beneficial technical effects: can be applied in most information systems or system groups with protocol and service data, realizes configurable automatic charging, is suitable for most quantifiable charging rule scenarios, and can more flexibly meet the demand for automatic charging. BRIEF DESCRIPTION OF DRAWINGS

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

[0029] Figure 2 is a running schematic diagram of the rule quantifier of the present application;

[0030] Figure 3 is a case schematic diagram of the quantified charging condition of the present application;

[0031] Figure 4 is a running schematic diagram of the element extractor of the present application;

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

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

[0034] Figure 7 is a schematic diagram of other parent-child structures of the present application;

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

[0036] The following will be combined with the drawings Figures 1-7 The present application will be further described in detail.

[0037] The embodiment of the application discloses an automatic charging engine configuration method combined with a protocol and service data, which can be applied to most information systems or system groups with protocols and service data, realizes configurable automatic charging, is suitable for most quantifiable charging rule scenes, and can more flexibly meet automatic charging demands.

[0038] With reference to Figures 1-6 The automatic charging engine configuration method combined with a protocol and service data comprises the following steps.

[0039] S1, establishing a rule quantifier for a user to configure charging rules in a protocol, and running to obtain quantified charging rules.

[0040] The configurable content comprises one or more of a fee item, a unit price, a currency, a settlement unit, a charging mode, a reference element, a triggering mode, a triggering condition, a hierarchical logical relationship of charging conditions, a charging hit matching condition, a collection fee item, a collection tax rate, a protocol unique identifier, and a matching (service) type.

[0041] The rule quantifier is realized by a front-end page program+background program+database storage mode. In terms of the front end, a corresponding UI interface is created, which should have good page design and interactivity, so as to facilitate the user to conveniently configure quantified rules. The background program is mainly responsible for receiving data transmitted by the front end, verifying and storing configuration information in the database.

[0042] It should be noted that the fee item maintenance, the hierarchical logical relationship maintenance of charging conditions, and the charging hit matching condition maintenance take a tree or other parent-child structure as a carrier and store the unique identifier of the upper item in the lower item. Specifically,

[0043] The rule branch logic takes a tree or other parent-child structure as a carrier, and the parent-child attribute relationship of rule items needs to be considered at the time of design. The unique identifier of the parent item is stored in the child item to realize the storage of the parent-child attribute relationship. The front end can also further strengthen the logic of the parent-child attribute in vision by folding and unfolding the tree at the time of design.

[0044] S2, establishing an element extractor for identifying a unique field of service data and obtaining a charging element corresponding to the service data, and running to obtain the charging element.

[0045] In the embodiment, the element extractor is implemented by using database technology. In the case of low performance requirement, the business data table can be queried by using database view or stored procedure, and the column-to-row method is used to realize unlimited extraction and expansion of the billing elements. In the case of high performance requirement, the stored procedure or background program processing method is recommended. When the business data is stored or changed, the billing element of the corresponding business item is updated in the special billing element table, so that the billing element can be obtained more efficiently when triggering, judging and billing.

[0046] In another embodiment of the present application, the element extractor preloads the business data information based on a big data unit and / or an OCR unit. Specifically,

[0047] Based on the big data unit: the platform implementing the method can analyze the commonly used billing elements in the industry, automatically list multiple billing elements with high use probability according to the billing proportion or weight, and preload before actual use by the user.

[0048] Based on the OCR unit: the protocol content uploaded by the user is read, the keyword frequency and weight of the text appearance element are analyzed, and the element is preloaded.

[0049] S3, an adaptive trigger including a trigger, a protocol / rule set matcher, and a rule engagement is established, and the specific billing rule item to be executed is obtained by running.

[0050] The trigger is used to trigger billing according to the content configured by the rule quantifier. The triggering mode of the trigger includes one or more of timing triggering, conditional triggering, and manual triggering. Specifically,

[0051] Timing triggering uses a timer. When the set time is reached, the triggering engine triggers billing. Conditional triggering is a monitoring triggering method based on specified condition values. When the corresponding monitored elements meet the configured conditions, the triggering engine triggers billing. Manual triggering is usually provided as a function call interface. When the call instruction is received, the triggering engine triggers billing immediately. The trigger is generally implemented by using database technology or a background program. If the database technology is used, the timer, trigger, and stored procedure of the database are used to realize timing, conditional, and manual triggering. If the background program is used, the timing task and the polling triggering condition are used to realize the implementation.

[0052] Protocol / rule set matcher is used to match the traffic with the rule set according to the content of the rule quantifier configuration. Specifically, in the system with protocol and traffic data, the traffic is usually carried out according to a certain protocol. Through the protocol unique identifier configured by the rule quantifier, the matched traffic type content, the protocol / rule set matcher can find the charging rule set that needs to be executed for the traffic that needs to be charged. The protocol matcher is generally implemented based on a database query statement, and the protocol and traffic type attributes of the traffic data are used to search the charging rule set containing the same attributes.

[0053] Rule engager is used to filter the specific charging rule item that needs to be executed according to the content of the rule quantifier configuration. Specifically, according to the hierarchical logical relationship of the charging condition configured by the rule quantifier and the charging hit matching condition, the rule engager can combine the charging elements extracted by the element extractor to strip the charging rule with hierarchical structure and determine the specific charging rule item that needs to be executed.

[0054] The difficulty of the rule engager lies in how to hit the specific charging rule item that needs to be executed. Under the tree-shaped hierarchical logic, a preset pruning algorithm is used, that is, starting from the parent node, the entire charging rule set is polled layer by layer. If it is judged that the trigger condition of the charging item is met, the child item of the charging item is continued to be polled until a charging item without a child item is hit, that is, the specific charging rule item that needs to be executed is hit. Other items that do not meet the trigger condition 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 charging efficiency can be improved by artificially writing the charging rule item with a larger centralized probability in the front position. In other special charging scenarios, other algorithms can also be considered to further optimize the charging efficiency.

[0055] It should be noted that the working mode of the rule engager is multiple, which includes:

[0056] If the current is ordinary charging, the rule engager takes the data with the highest priority as the result;

[0057] If the current is ladder calculation, maximum / minimum charging rule, the rule engager adopts all the engagement results, and after calculation, the results are summed, maximum / minimum value processing is performed according to the corresponding rule.

[0058] In particular, in the charging mode of ladder charging, maximum value charging, etc., the engager needs to return all the engagement results for processing in the next link. The pruning algorithm can also be used, but after hitting, it does not interrupt, and the result set is returned.

[0059] S4, a data processor including a calculator, a generator, and a collection and payment processor is established, and the charging result is obtained by running.

[0060] The calculator is configured to calculate the cost according to the content of the rule quantizer, specifically: based on the unit price, the charging mode, and the reference element, the actual calculation of the cost is performed. The charging mode usually contains a simple unit price quantity mode, and more advanced charging modes such as step charging and compound interest charging can also be designed according to actual needs. When designing the program, different charging mode methods are written for different charging modes. When the calculation is executed, the method of the program is determined by the charging mode configured on the charging item, and the unit price and the charging element are transmitted into the method by parameter passing to perform the operation and obtain the calculation result.

[0061] The generator is configured to package the result calculated by the calculator according to the content of the rule quantizer, and to actually package the cost item according to the cost item, the currency, and the settlement unit, so as to form cost item data that can be stored and actually used. The generator is a packaging component, which is implemented by a background program. The cost item information configured on the charging item and the calculation result generated by the calculator are transmitted into the method of the generator by parameter passing, so as to form a complete cost item data record, and the data record is stored in the database, thereby completing the generation and storage of the charging result.

[0062] The collection and payment processor is configured to perform secondary processing on the cost item generated by the generator according to the content of the rule quantizer, so as to form a corresponding collection item or payment item. The collection and payment processor can reprocess and package the cost item according to the collection cost item and the collection tax rate, form a corresponding collection and payment cost item, and form a corresponding logical connection. The collection and payment processor is an enhanced generator based on actual business needs, which is implemented by a background program. The cost item data generated by the generator is called out from the database, combined with the collection and payment information configured on the cost item, and transmitted into the method of the collection and payment processor by parameter passing, so as to produce a new cost item data record for storage, and simultaneously update the corresponding collection and payment cost item data record, and store the binding relationship between the two.

[0063] According to the above setting, the method can be applied in most information systems or system groups with protocol and business data, and automatic charging can be realized in a configurable manner. The method is suitable for most quantifiable charging rule scenarios, and can more flexibly meet the demand for automatic charging.

[0064] In the embodiments of the present application, other parent-child structures are as shown in Figure 7 Taking the loading and unloading cost charging of a unit as an example:

[0065] The first behavior is in a layer;

[0066] The second to sixth behaviors are in a layer; the ninth behavior is in the same layer; the twelfth behavior is in the same layer; and the fifteenth behavior is in the same layer;

[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 entering the fee calculation branch, the engine 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 it 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 sequence until they are hit. If a record of loading operation is hit during the process, it will be 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 result are reversely fitted and the fee item information is deformed.

[0072] The purpose of the above steps is to bind the logical relationship between collection and payment.

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

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

[0075] Currently, there are the following requirements:

[0076] 1) For business and financial approval, these two payment items still need to have a clear correlation 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 quantifier configured to be configured by a user for charging rules in a protocol and to run to obtain quantified charging rules;

[0082] a factor extractor configured to identify unique fields of service data and to obtain charging factors corresponding to the service data, and to run to obtain charging factors;

[0083] a trigger adapter including a trigger, a protocol / rule set matcher, and a rule engager, and to run to obtain specific charging rule entries to be executed; wherein the trigger is configured to trigger charging according to contents configured by the rule quantifier, the protocol / rule set matcher is configured to match service and rule sets according to contents configured by the rule quantifier, and the rule engager is configured to screen charging rule entries to be specifically executed according to contents configured by the rule quantifier;

[0084] a data processor including a calculator, a generator, and a collection and payment processor, and to run to obtain charging results; wherein the calculator is configured to calculate according to contents configured by the rule quantifier, the generator is configured to wrap results calculated by the calculator according to contents configured by the rule quantifier, and the collection and payment processor is configured to further process items generated by the generator according to contents configured by the rule quantifier to form corresponding collection items or payment items.

[0085] The above components have been described in the previous method embodiment, and thus will not be described again.

[0086] The above are preferred embodiments of the present application, and are not intended to limit the protection scope of the present application, thus: any equivalent changes made according to the structure, shape, principle of the present application should be covered within the protection scope of the present application.

Claims

1. A method for configuring an automatic charging engine that binds a protocol and service data, the method comprising: receiving a protocol and service data; and configuring the automatic charging engine based on the protocol and the service data. The method comprises the following steps: S1, establishing a rule quantifier for configuring charging rules in a user agreement, and running to obtain quantized charging rules; wherein, the configurable contents include one or more of the following: fee item, unit price, currency, settlement unit, charging mode, reference element, trigger mode, trigger condition, hierarchical logical relationship of charging condition, charging hit matching condition, collection fee item, collection tax rate, agreement unique identifier, matching type; S2, establishing an element extractor for identifying unique fields of service data and obtaining charging elements corresponding to the service data; S3, establishing an adaptive trigger including a trigger, an agreement / rule set matcher, and a rule meshing device, and running to obtain specific charging rule entries that need to be executed; Wherein, the trigger is used for charging triggering according to the contents configured by the rule quantifier, the agreement / rule set matcher is used for matching service and rule set according to the contents configured by the rule quantifier, and the rule meshing device is used for screening charging rule entries that need to be executed according to the contents configured by the rule quantifier; S4, establishing a data processor including a calculator, a generator, and a collection and payment processor, and running to obtain charging results; Wherein, the calculator is used for calculation according to the contents configured by the rule quantifier, the generator is used for packaging the results calculated by the calculator according to the contents configured by the rule quantifier, and the collection and payment processor is used for secondary processing of the fee items generated by the generator according to the contents configured by the rule quantifier, to form corresponding collection items or payment items; The maintenance of fee items, the maintenance of hierarchical logical relationship of charging conditions, and the maintenance of charging hit matching conditions are carried out by taking a tree or other parent-child structure as a carrier and storing the unique identifier of the lower entry in the upper entry; The element extractor preloads the service data information based on a big data unit and / or an OCR unit; the element extractor is implemented by using database technology; in a scene with low performance requirement, the service data table is queried by using a database view or a storage process, and the column is converted into a row to realize the extraction and expansion of charging elements; in a high-performance requirement scene, the storage process or the background program processing mode is adopted to update the charging elements of the corresponding service items in the charging element table when the service data is stored or changed; The element extractor preloads the service data information based on a big data unit and / or an OCR unit; specifically: Based on a big data unit: based on the analysis of charging elements in the industry, the charging elements are automatically listed according to the proportion or weight of charging, and are preloaded before actual use by the user; Based on the OCR unit: reading the agreement content uploaded by the user, analyzing the keyword frequency and weight of the text element, and preloading the element.

2. The method of claim 1, wherein the binding agreement and business data automatic billing engine configuration method is characterized by: The trigger mode of the trigger includes one or more of the following: timing trigger, conditional trigger, and manual trigger.

3. The method of claim 1, wherein the binding agreement and business data automatic billing engine configuration method is characterized by: The working mode of the rule meshing device includes the following: If it is a normal charging, the rule meshing device takes the data with the highest priority as the result; If the current is ladder calculation, the maximum / minimum billing rules, the rule engagement uses all the engagement results, and after the calculation, the results are summed according to the corresponding rules, and the maximum / minimum value processing is performed.

4. The method of claim 3, wherein the binding agreement and the automatic billing engine configuration method for the business data is characterized by: The rule engagement hits the specific billing rule items that need to be executed by the preset pruning algorithm.

5. The method of claim 1, wherein the binding agreement and business data automatic billing engine configuration method is characterized by: The billing results are reversely fitted and the fee item information is deformed.

6. An automatic billing platform that combines a protocol with service data, characterized by, The automatic billing engine configuration method of the binding protocol and the service data is realized, and comprises: A rule quantifier is configured for a user to configure the billing rules in the protocol and run the quantified billing rules; An element extractor is configured to identify the unique fields of the service data and obtain the corresponding billing elements of the service data, and run the billing elements; An adaptation trigger comprises a trigger, a protocol / rule set matcher, and a rule engagement, and runs the specific billing rule items that need to be executed; wherein the trigger is configured to trigger billing according to the content configured by the rule quantifier, the protocol / rule set matcher is configured to match the service and the rule set according to the content configured by the rule quantifier, and the rule engagement is configured to filter the specific billing rule items that need to be executed according to the content configured by the rule quantifier; A data processor comprises a calculator, a generator, and a data processor of a collection and payment processor, and runs the billing results; wherein the calculator is configured to calculate according to the content configured by the rule quantifier, the generator is configured to wrap the results calculated by the calculator according to the content configured by the rule quantifier, and the collection and payment processor is configured to perform secondary processing on the fee items generated by the generator according to the content configured by the rule quantifier, to form the corresponding collection items or payment items.

Images