Data processing method, electronic device and program product

Abstract

The invention provides a data processing method, electronic equipment and a program product. The data processing method comprises the following steps: acquiring project code information in target transaction data; based on a first mapping relation, charging condition information corresponding to the project coding information is determined, and the first mapping relation is at least a mapping relation between preset project coding information and preset charging condition information; judging whether the target transaction data meets a charging condition in the charging condition information or not; and under the condition that the target transaction data meets the charging condition, based on a second mapping relationship, determining the item code information and charging rule information corresponding to the code of the charging condition met by the target transaction data, the second mapping relationship is at least a mapping relationship among the preset item code information, the preset charging condition code and the preset charging rule information; and performing cost calculation on the target transaction data based on the charging rule information to obtain a cost calculation result.

Description

Technical Field

[0001] The present disclosure relates to technical fields such as computers and payments, and in particular to a data processing method, an electronic device, a readable storage medium, and a program product. Background Art

[0002] In the payment field, there are extensive needs for fee calculation, such as the need to calculate the total amount of payments, the total amount of income, the total amount of commissions, etc.

[0003] In the related art, manual calculation is used to calculate the fees for the relevant amounts involved in multiple transactions. However, manual calculation is slow. Summary of the invention

[0004] The present disclosure provides a data processing method, an electronic device, a readable storage medium, and a program product.

[0005] According to one aspect of the present disclosure, there is provided a data processing method, comprising: Obtaining item coding information in target transaction data; Determine the billing condition information corresponding to the project coding information based on a first mapping relationship, wherein the first mapping relationship is at least a mapping relationship between preset project coding information and pre-designed billing condition information; Determining whether the target transaction data satisfies the charging condition in the charging condition information; In the case where the target transaction data satisfies the charging condition, determining, based on a second mapping relationship, charging rule information corresponding to the project code information and the code of the charging condition satisfied by the target transaction data, wherein the second mapping relationship is at least a mapping relationship between preset project code information, pre-designed fee condition code and pre-designed fee rule information; and The target transaction data is charged based on the charging rule information to obtain a charge calculation result.

[0006] According to the data processing method of at least one embodiment of the present disclosure, the charging condition in the charging condition information includes a plurality of charging sub-conditions; Determining whether the target transaction data satisfies the charging condition in the charging condition information includes: matching the target transaction data with the multiple charging sub-conditions respectively; and In a case where the target transaction data satisfies the multiple charging sub-conditions, it is determined that the target transaction data satisfies the charging condition in the charging condition information.

[0007] According to the data processing method of at least one embodiment of the present disclosure, each of the charging sub-conditions includes a parameter code and a condition type and a condition value corresponding to the parameter code; The method further comprises: For one of the charging sub-conditions, determining whether the parameter value corresponding to the parameter code in the target transaction data satisfies the condition type and the condition value; and In a case where the parameter value satisfies the condition type and the condition value, it is determined that the target transaction data satisfies one of the billing sub-conditions.

[0008] According to the data processing method of at least one embodiment of the present disclosure, the charging condition information further includes deduplication information, and the deduplication information includes a deduplication type and a deduplication parameter encoding; The method further comprises: Determine a deduplication parameter value corresponding to the deduplication type based on a third mapping relationship, wherein the third mapping relationship is at least a mapping relationship between a preset deduplication type and a preset deduplication parameter value; and When the parameter value corresponding to the deduplication parameter code in the target transaction data is the same as the deduplication parameter value, and a parameter value with the same deduplication type exists in the target transaction data, processing of the target transaction data is stopped.

[0009] According to the data processing method of at least one embodiment of the present disclosure, when the target transaction data satisfies the billing condition, determining the billing rule information corresponding to the item code information and the code of the billing condition satisfied by the target transaction data based on the second mapping relationship, including: When the deduplication parameter value corresponding to the deduplication type cannot be determined, or the parameter value corresponding to the deduplication parameter encoding in the target transaction data is different from the deduplication parameter value, or the parameter value identical to the deduplication type does not exist in the target transaction data, if the target transaction data satisfies the billing conditions, then based on the second mapping relationship, the billing rule information corresponding to the item coding information and the encoding of the billing conditions satisfied by the target transaction data is determined.

[0010] According to at least one embodiment of the present disclosure, the data processing method further includes: When the deduplication parameter value corresponding to the deduplication type cannot be determined, or the parameter value corresponding to the deduplication parameter code in the target transaction data is different from the deduplication parameter value, or the parameter value identical to the deduplication type does not exist in the target transaction data, a mapping relationship between the deduplication type and the parameter value corresponding to the deduplication parameter code in the target transaction data is generated, and the generated mapping relationship is stored in the third mapping relationship.

[0011] According to the data processing method of at least one embodiment of the present disclosure, the charging rule information includes a rate type and a rate; Performing fee calculation on the target transaction data based on the charging rule information to obtain a fee calculation result includes: Calculating a fee based on multiple of the target transaction data, the rate type, and the rate; and The fee calculation result is obtained according to the fee.

[0012] According to at least one embodiment of the present disclosure, a data processing method is provided, wherein the fee is calculated according to the target transaction data, the rate type and the rate, including: In the case where the rate type is a fixed amount type, using the rate as the fee; and When the rate type is a proportional type, the product of the rate and the transaction amount in the target transaction data is used as the fee.

[0013] According to the data processing method of at least one embodiment of the present disclosure, the charging rule information also includes a minimum fee and a maximum fee; The fee calculation result is obtained according to the fee, including: When the fee is less than or equal to the minimum fee, the minimum fee is used as the fee calculation result; In the case where the fee is greater than the minimum fee and less than the maximum fee, taking the fee as the fee calculation result; and When the fee is greater than or equal to the maximum fee, the maximum fee is used as the fee calculation result.

[0014] According to at least one embodiment of the data processing method of the present disclosure, after calculating the fee for the target transaction data based on the charging rule information to obtain the fee calculation result, the method further includes: Based on a fourth mapping relationship, determining at least one statistical dimension parameter code corresponding to the project code information, wherein the fourth mapping relationship is at least a mapping relationship between preset project code information and at least one preset statistical dimension parameter code; Generate a target SQL query statement according to the at least one statistical dimension parameter code and a predefined SQL statement template, wherein the target SQL query statement is used to perform dimensional statistics on a cost calculation result of at least one target transaction data based on the at least one statistical dimension parameter code; and Execute the target SQL query statement to obtain dimension statistical results.

[0015] According to another aspect of the present disclosure, an electronic device is provided, comprising: a memory storing execution instructions; and a processor executing the execution instructions stored in the memory, so that the processor executes the data processing method of any embodiment of the present disclosure.

[0016] According to another aspect of the present disclosure, a readable storage medium is provided, wherein the readable storage medium stores execution instructions, and when the execution instructions are executed by a processor, the execution instructions are used to implement the data processing method of any embodiment of the present disclosure.

[0017] According to another aspect of the present disclosure, a computer program product is provided, including a computer program, wherein when the computer program is executed by a processor, the data processing method of any embodiment of the present disclosure is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The accompanying drawings illustrate exemplary embodiments of the present disclosure and together with the description serve to explain the principles of the present disclosure. These drawings are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of this specification.

[0019] Figure 1 It is a flowchart of a data processing method according to an embodiment of the present disclosure.

[0020] Figure 2 It is a schematic diagram of a process of determining whether a charging condition is met according to an embodiment of the present disclosure.

[0021] Figure 3 It is a flowchart of a data processing method according to another embodiment of the present invention.

[0022] Figure 4 It is a flowchart of a data processing method according to another embodiment of the present invention.

[0023] Figure 5 The figure is a schematic diagram of the cost calculation process according to one embodiment of the present disclosure.

[0024] Figure 6 FIG. 4 is a schematic diagram of a process of determining fees according to an embodiment of the present disclosure.

[0025] Figure 7 It is a schematic diagram of a process of determining a cost calculation result according to an embodiment of the present disclosure.

[0026] Figure 8 It is a schematic diagram of the process of dimensional statistics according to an embodiment of the present disclosure.

[0027] Fig. 9 It is a schematic block diagram of the structure of a data processing system according to one embodiment of the present disclosure.

[0028] Fig.10 It is a schematic block diagram of the structure of a billing system according to an embodiment of the present disclosure.

[0029] Fig.11 It is a flowchart of a data processing method according to another embodiment of the present invention.

[0030] Fig.12 It is a schematic block diagram of the structure of a data processing device according to one embodiment of the present disclosure.

[0031] Fig.13 It is a schematic block diagram of the structure of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0032] The present disclosure is further described in detail below in conjunction with the accompanying drawings and examples. It is understood that the specific examples described herein are only used to explain the relevant content, rather than to limit the present disclosure. It should also be noted that, for ease of description, only the parts related to the present disclosure are shown in the accompanying drawings.

[0033] It should be noted that, in the absence of conflict, the embodiments and features of the embodiments in the present disclosure can be combined with each other. The technical solution of the present disclosure will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0034] The data involved in cost calculation is ever-changing. For example, sometimes the data involved is the payment amount, sometimes the data involved is the income amount, and sometimes the data involved is the commission amount. At the same time, the billing rules required for cost calculation are cumbersome and complicated. For example, sometimes different billing rules need to be selected according to the transaction type, sometimes different billing rules need to be selected according to the transaction time and transaction location, and sometimes different billing rules need to be selected according to the billing rate. Therefore, in the case of manual cost calculation, it is necessary to repeatedly search for the data involved in the cost calculation and repeatedly change the billing rules, which leads to low cost calculation efficiency; and if you accidentally misread the amount or select the wrong billing rule, it will lead to calculation errors and reduce the accuracy of cost calculation.

[0035] To this end, the present disclosure proposes a data processing method.

[0036] The data processing method disclosed in the present invention can be used for electronic devices to automatically calculate the cost of target transaction data and obtain the cost calculation result. In the present disclosure, electronic devices include but are not limited to mobile phones, tablet computers, laptops, personal computers, wearable devices, ATMs, etc.

[0037] For the convenience of description and to make the technical solutions of the specific implementation methods of the present disclosure easier to understand, before describing the data processing method implemented in the present disclosure, the technical terms involved in the specific implementation methods of the present disclosure are explained as follows: Billing conditions: one of the criteria for fee calculation. If the billing conditions are met, the fee calculation can be performed, but whether the fee calculation is performed can be further determined in combination with other criteria. If the billing conditions are not met, the fee calculation is not performed.

[0038] Billing rules: are the standards and methods for fee calculation, that is, they are used to indicate how to calculate fees.

[0039] JOIN operation: It is used to combine rows from two or more tables based on certain conditions.

[0040] UNION operation: used to combine the result sets of two or more SELECT statements. SELECT is a keyword used to specify a query to retrieve data from the database.

[0041] Figure 1 FIG. 1 is a schematic diagram showing the overall flow of a data processing method M100 according to an embodiment of the present disclosure. Figure 1 The method shown includes steps S110 to S150. The method can be executed by electronic devices such as mobile phones and computers.

[0042] Specifically, Figure 1 The methods shown include: S110, obtaining item coding information in target transaction data; The project coding information can characterize the project to which the target transaction data belongs. Considering that the billing condition information and billing rule information corresponding to different projects may be different, the project coding information in the target transaction data is determined in advance, so as to facilitate the subsequent accurate determination of the billing condition information and billing rule information related to the target transaction data through the project coding information.

[0043] The target transaction data may be a transaction data in the standard transaction flow detail table. A batch may include multiple transaction data. The transaction flow detail table may include multiple batches whose execution status is pending execution.

[0044] In one example, the electronic device extracts incremental transaction data from each project's business database every day, aggregates and processes billing-related factors in the incremental transaction data, such as transaction time, location, and end-of-day balance (which can be achieved through operations such as join and union in MYSQL), and outputs them to a transaction statement or an end-of-day balance statement, where the transaction statement can store every transaction of the account, and the end-of-day balance statement can store the balance of the account at the end of each day.

[0045] Next, the electronic device obtains the first configuration data, which is used to indicate the name of the transaction flow table, the name of the daily balance table and the data query conditions corresponding to different project coding information, and queries the transaction data in the corresponding transaction flow table and the daily balance table according to the data query conditions and the pre-acquired transaction time range. After each transaction data in the transaction flow table and the daily balance table is queried, the transaction data in the transaction flow table and the daily balance table can be deleted to avoid duplication when subsequent tasks are re-run.

[0046] Secondly, the electronic device obtains second configuration data, and the second configuration data is used to indicate the field name of the field value in the transaction flow details table and the day-end balance details table when it is stored in the transaction flow details standard table, and the first condition that needs to be met when the transaction data in the transaction flow details table and the day-end balance details table are stored in the transaction flow details standard table. The first condition may include one or more of the data length condition, the data format condition, and the data enumeration value condition, and according to the first condition, it is judged whether each transaction data in the transaction flow details table and the day-end balance details table can be stored in the transaction flow details standard table. If one transaction data in the transaction flow details table and the day-end balance details table meets the first condition, the transaction data is stored in the transaction flow details standard table; if one transaction data in the transaction flow details table and the day-end balance details table does not meet the first condition, the transaction data is not stored in the transaction flow details standard table. It can be understood that if the field name of a field value A in the transaction flow detail table or the end-of-day balance detail table is B, the second configuration data can be used to determine that the corresponding field name of the field value A when stored in the transaction flow detail standard table is C, and B and C can be different. In this way, it is convenient for transaction data in different projects to be stored in the same transaction flow detail standard table with the same field name. When a new project is connected, there is no need to modify the code again. By configuring the first configuration data and the second configuration data, the new project can be quickly connected, improving efficiency and scalability. In addition, the electronic device also generates batch information corresponding to the transaction data based on the transaction time in the transaction data. The batch information includes a batch number, an execution status, etc., and stores the batch information in a preset batch table, and stores the batch number in the transaction flow detail standard table. Then, the electronic device can use a transaction data corresponding to a batch number in the transaction flow detail standard table whose execution status is to be executed (i.e., it has not participated in the fee calculation) as the target transaction data. If multiple transaction data corresponding to a batch number are all processed as target transaction data in turn, the execution status of the batch number can be changed to successful execution.

[0047] S120: Determine the charging condition information corresponding to the project coding information based on the first mapping relationship, wherein the first mapping relationship is at least a mapping relationship between the preset project coding information and the preset charging condition information; Exemplarily, the first mapping relationship includes not only the preset project coding information and the preset design fee condition information corresponding to the preset project coding information, but also one or more of the primary key information, data status information, review status information, creator information, updater information, creation time, and update time corresponding to the preset project coding information. The first mapping relationship may be in the form of a data table. The first mapping relationship may be preset by relevant personnel.

[0048] S130, determining whether the target transaction data satisfies the charging condition in the charging condition information; The charging condition information corresponding to the item coding information may include multiple of the charging condition coding, the charging condition and the deduplication information.

[0049] By judging whether the target transaction data meets the billing conditions in the billing condition information, it can be determined whether to continue to execute the subsequent steps. It is understandable that if a target transaction data meets the billing conditions in the billing condition information, it can be combined with other standards (such as deduplication parameter values) to determine whether to perform fee calculation, thereby further improving the accuracy of fee calculation, or it can be directly calculated without combining other standards; if a target transaction data does not meet the billing conditions in the billing condition information, then for this target transaction data, the subsequent fee calculation steps will no longer be executed.

[0050] S140. When the target transaction data satisfies the charging condition, based on the second mapping relationship, determining the charging rule information corresponding to the project code information and the code of the charging condition satisfied by the target transaction data, wherein the second mapping relationship is at least a mapping relationship between the preset project code information, the pre-designed fee condition code and the pre-designed fee rule information; Exemplarily, the second mapping relationship includes not only the preset project coding information and the pre-design fee condition coding and pre-design fee rule information corresponding to the preset project coding information, but also one or more of the primary key information, data status information, review status information, creator information, updater information, creation time, and update time corresponding to the preset project coding information. The second mapping relationship may be in the form of a data table. The second mapping relationship and the first mapping relationship may be stored in the same data table, or may be stored in different data tables respectively, which is not limited here. The second mapping relationship may be preset by relevant personnel.

[0051] S150: Calculate the cost of the target transaction data based on the charging rule information to obtain a cost calculation result.

[0052] The charging rule information may include multiple of the charging rule code, charging rule name, charging time range, rule object, rate type, rate, minimum fee and maximum fee. After obtaining the charging rule information, it is possible to determine how to calculate the fee for the target transaction data.

[0053] The data processing method of the disclosed embodiment accurately determines the billing condition information and billing rule information through the project coding information in the target transaction data, and automatically calculates the fees, thereby improving the degree of automation of data processing, improving the efficiency of fee calculation, reducing manual intervention, and improving the accuracy of fee calculation.

[0054] Regarding step S130, in some embodiments of the present disclosure, the charging condition in the charging condition information includes multiple charging sub-conditions; accordingly, step S130 may include the following: Figure 2 Steps S131 to S132 are shown.

[0055] S131. Match the target transaction data with multiple billing sub-conditions respectively.

[0056] The target transaction data may include multiple parameter values, and the multiple charging sub-conditions may be constraints for the multiple parameter values ​​respectively. By matching the target transaction data with the multiple charging sub-conditions respectively, it is possible to determine which charging sub-conditions the target transaction data satisfies.

[0057] S132. When the target transaction data satisfies multiple charging sub-conditions, determine whether the target transaction data satisfies the charging condition in the charging condition information.

[0058] Exemplarily, if the target transaction data satisfies all the charging sub-conditions of a charging condition, it can be determined that the target transaction data satisfies the charging condition in the charging condition information.

[0059] If the billing condition information includes multiple billing conditions, and one billing condition includes multiple billing sub-conditions, then when the target transaction data satisfies all billing sub-conditions of any billing condition, it can be determined that the target transaction data satisfies the billing conditions in the billing condition information; when the target transaction data does not satisfy all billing sub-conditions of any billing condition, it can be determined that the target transaction data does not satisfy the billing conditions in the billing condition information.

[0060] If the billing condition information includes multiple billing conditions, and one billing condition includes a billing sub-condition, then when the target transaction data satisfies the billing sub-condition of any billing condition, it can be determined that the target transaction data satisfies the billing condition in the billing condition information; when the target transaction data does not satisfy the billing sub-condition of any billing condition, it can be determined that the target transaction data does not satisfy the billing condition in the billing condition information.

[0061] If the billing condition information includes only one billing condition, and one billing condition includes multiple billing sub-conditions, then when the target transaction data meets all the billing sub-conditions of the billing condition, it can be determined that the target transaction data meets the billing condition in the billing condition information; when the target transaction data does not meet any of the billing sub-conditions of the billing condition, it is determined that the target transaction data does not meet the billing condition in the billing condition information.

[0062] If the billing condition information includes only one billing condition, and one billing condition includes only one billing sub-condition, then when the target transaction data satisfies one billing sub-condition of one billing condition, it can be determined that the target transaction data satisfies the billing condition in the billing condition information; when the target transaction data does not satisfy one billing sub-condition of one billing condition, it can be determined that the target transaction data does not satisfy the billing condition in the billing condition information.

[0063] The data processing method of the above-mentioned implementation method uses multiple billing sub-conditions to determine whether the target transaction data meets the billing conditions in the billing condition information, thereby improving the accuracy of the judgment result. In addition, multiple billing sub-conditions can make the judgment logic more flexible, which is conducive to adapting to complex business scenarios, facilitating more accurate matching of different transaction situations, and improving the fairness and rationality of billing.

[0064] In some embodiments of the present disclosure, each charging sub-condition includes a parameter code and a condition type and a condition value corresponding to the parameter code; accordingly, the data processing method M100 may also include the following: Figure 3 Steps S160 to S170 are shown.

[0065] S160. For a billing sub-condition, determine whether the parameter value corresponding to the parameter code in the target transaction data satisfies the condition type and condition value.

[0066] The target transaction data may include a field name identical to the parameter code in the billing sub-condition, and then the field value corresponding to the field name is the parameter value corresponding to the parameter code in the target transaction data; or, the target transaction data does not include a field name identical to the parameter code in the billing sub-condition, but there is a field name associated with the parameter code in the target transaction data (the association relationship is pre-set, and the associated field name and parameter code may refer to the same parameter value), and then the field value corresponding to the associated field name is the parameter value corresponding to the parameter code in the target transaction data.

[0067] The condition type may include one or more of equal to, not equal to, greater than, greater than or equal to, less than, less than or equal to, contains, does not contain, and remove duplicates. The condition value is preset and can be empty, or one value or multiple values, which are not limited here. The condition value may include one or more of numbers, English letters, Chinese characters, and symbols.

[0068] S170. When the parameter value satisfies the condition type and the condition value, determine that the target transaction data satisfies a billing sub-condition.

[0069] When there are multiple condition values ​​in a billing sub-condition, if the parameter value corresponding to the parameter code in the target transaction data satisfies the condition type and any condition value in the billing sub-condition, it can be determined that the target transaction data satisfies the billing sub-condition.

[0070] In an example, in a billing sub-condition, the parameter code is transType, the condition type is equal to, and the condition value is withdrawal. The field name string1 in the target transaction data and the parameter value referred to by transType are the same. If the parameter value of the field name string1 in the target transaction data is withdrawal, it can be determined that the target transaction data meets this billing sub-condition.

[0071] The data processing method of the above implementation further refines the billing sub-conditions by defining each billing sub-condition as a specific parameter code, condition type and condition value, thereby enhancing the flexibility and configurability of the billing sub-conditions.

[0072] In some embodiments of the present disclosure, the charging condition information further includes deduplication information, the deduplication information includes a deduplication type and a deduplication parameter code, and the deduplication information is used to guide deduplication, thereby avoiding reducing the accuracy of the charging result due to repeated charging; accordingly, the data processing method M100 may also include the following: Figure 4 Steps S180 to S190 are shown.

[0073] S180. Determine a deduplication parameter value corresponding to the deduplication type based on a third mapping relationship, wherein the third mapping relationship is at least a mapping relationship between a preset deduplication type and a preset deduplication parameter value.

[0074] Exemplarily, in addition to the preset deduplication type and the preset deduplication parameter value corresponding to the preset deduplication type, the third mapping relationship may also include one or more of preset project coding information, primary key information corresponding to the preset project coding information, batch information, data effective range (trial, temporary, formal), transaction date, billing rule coding information, creator information, updater information, creation time, and update time. The third mapping relationship may be in the form of a data table. The third mapping relationship may be preset by relevant personnel.

[0075] S190: When the parameter value corresponding to the deduplication parameter code in the target transaction data is the same as the deduplication parameter value, and the target transaction data has a parameter value of the same deduplication type, stop processing the target transaction data.

[0076] The target transaction data may include a field name that is identical to the deduplication parameter code in the deduplication information, and then the field value corresponding to the field name is the parameter value corresponding to the deduplication parameter code in the target transaction data; or, the target transaction data does not include a field name that is identical to the deduplication parameter code in the deduplication information, but there is a field name associated with the deduplication parameter code in the target transaction data (the association relationship is pre-set, and the associated field name and deduplication parameter code may refer to the same parameter value), and then the field value corresponding to the associated field name is the parameter value corresponding to the deduplication parameter code in the target transaction data.

[0077] The deduplication parameter value and the parameter value corresponding to the deduplication parameter code in the target transaction data essentially belong to the same deduplication parameter code, for example, they belong to the contract number, so the two can be compared to accurately perform deduplication. Multiple transactions under the same contract number can be charged only once, so if the deduplication parameter value and the parameter value corresponding to the deduplication parameter code in the target transaction data are the same, and there is a parameter value of the same deduplication type in the target transaction data, it means that the contract number associated with the target transaction data has been charged before, and the target transaction data should not be charged again at this time, that is, the processing of the target transaction data should be stopped.

[0078] The data processing method of the above implementation avoids repeated processing of the same data by deduplicating information in the billing condition information, thereby avoiding unnecessary cost calculation errors, which is beneficial to improving the accuracy of data processing and reducing waste of system resources.

[0079] Regarding step S140, in some embodiments of the present disclosure, specifically, it can be: when the deduplication parameter value corresponding to the deduplication type cannot be determined, or the parameter value corresponding to the deduplication parameter encoding in the target transaction data is different from the deduplication parameter value, or the parameter value identical to the deduplication type does not exist in the target transaction data, if the target transaction data satisfies the billing conditions, then based on the second mapping relationship, determine the billing rule information corresponding to the item coding information and the encoding of the billing conditions satisfied by the target transaction data.

[0080] In the case where the deduplication parameter value corresponding to the deduplication type in the third mapping relationship is empty, the deduplication parameter value corresponding to the deduplication type cannot be determined. In the case where the deduplication parameter value corresponding to the deduplication type cannot be determined, or the parameter value corresponding to the deduplication parameter encoding in the target transaction data is different from the deduplication parameter value, or the target transaction data does not contain the same parameter value as the deduplication type, it indicates that the target transaction data participates in the fee calculation for the first time, so there is no need to deduplicate the target transaction data, and the subsequent data processing steps can be continued for the target transaction data.

[0081] The data processing method of the above-mentioned embodiment continues to execute subsequent data processing steps for the target transaction data when the deduplication parameter value corresponding to the deduplication type cannot be determined, or the parameter value corresponding to the deduplication parameter encoding in the target transaction data is different from the deduplication parameter value, or the parameter value identical to the deduplication type does not exist in the target transaction data, thereby ensuring the accurate execution of the data processing method.

[0082] In some embodiments of the present disclosure, the data processing method M100 may further include: when the deduplication parameter value corresponding to the deduplication type cannot be determined, or the parameter value corresponding to the deduplication parameter encoding in the target transaction data is different from the deduplication parameter value, or there is no parameter value with the same deduplication type in the target transaction data, generating a mapping relationship between the deduplication type and the parameter value corresponding to the deduplication parameter encoding in the target transaction data, and storing the generated mapping relationship in a third mapping relationship.

[0083] The data processing method of the above-mentioned implementation method generates a mapping relationship between the deduplication type and the parameter value corresponding to the deduplication parameter code in the target transaction data, and stores the generated mapping relationship in a third mapping relationship. It can timely supplement the content of the third mapping relationship, thereby avoiding subsequent fee calculation for transaction data with the same parameter value, avoiding repeated processing of the same data, and thus avoiding unnecessary fee calculation errors, which is conducive to improving the accuracy of data processing and reducing waste of system resources.

[0084] Regarding step S150, in some embodiments of the present disclosure, the charging rule information includes a rate type and a rate; accordingly, step S150 may include: Figure 5 Steps S151 to S152 are shown.

[0085] S151. Calculate fees according to multiple of the target transaction data, rate type and rate.

[0086] The rate type is used to indicate how to use the rate for fee calculation. Therefore, the fee can be calculated based on the target transaction data, rate type and rate, or based on the rate type and rate. There is no limitation here.

[0087] S152. Obtain a cost calculation result based on the cost.

[0088] The fees may be directly used as the fee calculation result, or the fees may be processed in other ways or combined with other data to obtain the fee calculation result, which is not limited here.

[0089] The data processing method of the above implementation enriches the charging rules through rate types and rates, thereby increasing the diversity of the charging rules, being able to better meet the needs of different business scenarios, and improving the accuracy of fee calculation.

[0090] Regarding step S151, in some embodiments of the present disclosure, it may include the following steps: Figure 6 Steps S1511 to S1512 are shown.

[0091] S1511. When the rate type is a fixed amount type, the rate is used as the fee.

[0092] When the rate type is a fixed amount type, the fee to be recorded is independent of the transaction amount in the target transaction data, and the fee is fixed to the rate value.

[0093] S1512: When the rate type is a proportional type, the product of the rate and the transaction amount in the target transaction data is used as the fee.

[0094] When the rate type is a proportion type, the fee to be recorded is related to the transaction amount in the target transaction data, and a certain proportion of the transaction amount in the target transaction data is used as the fee according to the rate value.

[0095] The data processing method of the above implementation can adopt different cost calculation methods for different rate types, thereby meeting the cost calculation requirements in different business scenarios and improving the accuracy of cost calculation.

[0096] Regarding step S152, in some embodiments of the present disclosure, the charging rule information also includes a minimum fee and a maximum fee; accordingly, step S152 may include: Figure 7 Steps S1521 to S1523 are shown.

[0097] S1521. When the fee is less than or equal to the minimum fee, the minimum fee shall be used as the fee calculation result.

[0098] S1522. When the fee is greater than the minimum fee and less than the maximum fee, the fee is used as the fee calculation result.

[0099] S1523. When the fee is greater than or equal to the maximum fee, the maximum fee is used as the fee calculation result.

[0100] The data processing method of the above implementation mode prevents unreasonable charges caused by abnormal data by setting the minimum fee and the maximum fee, thereby improving the accuracy of fee calculation.

[0101] In some embodiments of the present disclosure, after step S150, the following may also be included: Figure 8 Steps S210 to S230 are shown.

[0102] S210. Determine at least one statistical dimension parameter code corresponding to the project coding information based on a fourth mapping relationship, wherein the fourth mapping relationship is at least a mapping relationship between preset project coding information and at least one preset statistical dimension parameter code.

[0103] Exemplarily, in addition to the preset project coding information and at least one preset statistical dimension parameter code corresponding to the preset project coding information, the fourth mapping relationship may also include one or more of the statistical dimension code corresponding to the preset project coding information, the statistical dimension name, the data status information, the review status information, the creator information, the updater information, the creation time, and the update time. The fourth mapping relationship may be in the form of a data table. The fourth mapping relationship may be preset by relevant personnel, and the number of preset statistical dimension parameter codes corresponding to one preset project coding information may be set according to actual statistical needs, which is not limited here.

[0104] A statistical dimension code represents a statistical dimension, a statistical dimension parameter code represents a statistical dimension parameter, and a statistical dimension can have at least one statistical dimension parameter. In one example, the statistical dimension is encoded as cityDimGd (i.e., city statistics), and accordingly, the statistical dimension parameter is encoded as cityName (i.e., city), so that statistics on the city dimension can be performed. In another example, the statistical dimension is encoded as cityinoutDimGd (i.e., city deposit and withdrawal statistics), and accordingly, the statistical dimension parameters are encoded as cityName (i.e., city) and transType (i.e., transaction type), so that statistics on the two dimensions of city and transaction type can be performed.

[0105] S220. Generate a target SQL query statement according to at least one statistical dimension parameter code and a predefined SQL statement template, wherein the target SQL query statement is used to perform dimensional statistics on a cost calculation result of at least one target transaction data based on at least one statistical dimension parameter code.

[0106] By writing at least one statistical dimension parameter code into a predefined SQL statement template, a target SQL query statement can be obtained.

[0107] In one example, the predefined SQL statement template is: select XXX, count(1), sum(YYY) from ZZZ group by XXX. XXX is at least one statistical dimension parameter code. For example, if the statistical dimension parameter code is cityName, XXX is "cityName". If the statistical dimension parameter code is cityName and transType, XXX is "cityName, transType". ZZZ is the storage file name of the fee calculation result. For example, the default value is "t_flow_detail_result". YYY is the fee code in the fee calculation result storage file. For example, the default value is "feeAmt".

[0108] S230: Execute the target SQL query statement to obtain dimension statistics results.

[0109] Since the target SQL query statement includes at least one statistical dimension parameter code, the dimension statistical result under at least one statistical dimension can be obtained by executing the target SQL query statement.

[0110] In addition, you can also count the cost calculation results according to the billing rules, or count the cost calculation results according to the day, month, or year, without any limitation here. The dimension statistics results, cost calculation results, and transaction flow details standard table can be summarized as different worksheets in the same workbook, and the workbook can be uploaded to the file server for storage, so as to facilitate subsequent reference.

[0111] The data processing method of the above implementation mode performs statistics on the cost calculation results in at least one dimension through the target SQL query statement, thereby improving the accuracy and efficiency of data statistics.

[0112] Please combine Fig. 9 and Fig.10 In one example, the data processing system may include a billing system, a billing system database, a business database, a business system and a reconciliation platform. The billing system may include a configuration module, a data access module, an instruction receiving module, a data processing module, a billing batch module, a cost calculation module, a result export module and a data display module. Among them, the configuration module may store the above-mentioned first mapping relationship, the second mapping relationship, the third mapping relationship, the fourth mapping relationship, the first configuration data and the second configuration data, etc. The data stored in the configuration module can be read by other modules. Accordingly, please combine Fig.11 The data processing method may include the following steps S301 to S319. The contents related to steps S301 to S319 can refer to the description of the above implementation method. For the sake of brevity, they will not be repeated here.

[0113] In step S301, the data access module extracts incremental transaction data from each project business database every day, aggregates and processes billing-related factors in the incremental transaction data, such as transaction time, location, and end-of-day balance (which can be achieved through operations such as join and union in MYSQL), and outputs them to the transaction flow table or end-of-day balance table of the billing system database.

[0114] In step S302, when it is determined that the instruction receiving module has received the billing instruction sent by the reconciliation platform, the data processing module converts the transaction data in the transaction flow detail table and the daily balance detail table into transaction data in a unified format based on the first configuration data and the second configuration data obtained from the configuration module, and stores the transaction data in the unified format in the transaction flow detail standard table, wherein the transaction data with the same transaction time on the same day are divided into the same batch.

[0115] In step S303, the billing batch module reads a transaction data as the target transaction data from the batch with the execution status of "to be executed" in the transaction flow detail standard table.

[0116] In step S304, the billing batch module determines the billing condition information corresponding to the project code information based on the first mapping relationship.

[0117] In step S305, the billing batch module determines whether to deduplicate the target transaction data based on the third mapping relationship and the deduplication information in the billing condition information. If so, execute step S309, otherwise execute step S306.

[0118] In step S306, when deduplication is not performed, that is, the deduplication parameter value corresponding to the deduplication type cannot be determined, or the parameter value corresponding to the deduplication parameter code in the target transaction data is different from the deduplication parameter value, or the parameter value with the same deduplication type does not exist in the target transaction data, the billing batch module determines whether the target transaction data meets the billing conditions in the billing condition information. If so, execute step S307, otherwise execute step S311.

[0119] In step S307, when the target transaction data meets the billing conditions, based on the second mapping relationship, the billing batch module determines the billing rule information corresponding to the project coding information and the coding of the billing conditions met by the target transaction data.

[0120] In step S308, the billing batch running module calls the fee calculation module to calculate the fee for the target transaction data based on the billing rule information to obtain the fee calculation result.

[0121] In step S309, when deduplication is not performed, that is, the deduplication parameter value corresponding to the deduplication type cannot be determined, or the parameter value corresponding to the deduplication parameter code in the target transaction data is different from the deduplication parameter value, or the parameter value identical to the deduplication type does not exist in the target transaction data, the billing batch module generates a mapping relationship between the deduplication type and the parameter value corresponding to the deduplication parameter code in the target transaction data, and stores the generated mapping relationship in the third mapping relationship, thereby updating the third mapping relationship.

[0122] In step S310, when deduplication is being performed, that is, when the parameter value corresponding to the deduplication parameter code in the target transaction data is the same as the deduplication parameter value, and there is a parameter value with the same deduplication type in the target transaction data, the billing batch module stops processing the target transaction data.

[0123] In step S311, the billing batch module determines whether the transaction data in the batch with the execution status of pending execution in the transaction flow detail standard table has been traversed, that is, whether there is transaction data that is not used as target transaction data. If so, execute step S312, otherwise execute step S303.

[0124] In step S312, the billing batch module determines at least one statistical dimension parameter code corresponding to the project code information based on the fourth mapping relationship.

[0125] In step S313, the billing batch running module generates a target SQL query statement according to at least one statistical dimension parameter code and a predefined SQL statement template.

[0126] In step S314, the billing batch running module executes the target SQL query statement to obtain the dimension statistical results.

[0127] In step S315, the billing batch running module updates the execution status of the batches with the execution status of pending execution in the transaction flow detail standard table to execution completed.

[0128] In step S316, after obtaining the dimension statistics results, fee calculation results and standard table of transaction flow details through the billing batch module, the result export module aggregates the dimension statistics results, fee calculation results and standard table of transaction flow details as different worksheets into the same workbook, and uploads the workbook to the file server for storage.

[0129] In step S317, upon receiving a data query request from the business system, the data display module obtains the workbook requested by the data query request from the file server and displays the data.

[0130] Based on any of the above implementations, the present disclosure also provides a data processing device.

[0131] Fig.12 It is a schematic block diagram of the structure of a data processing device according to one embodiment of the present disclosure.

[0132] like Fig.12 As shown, the data processing device includes: The acquisition module 110 is used to acquire the item coding information in the target transaction data; A first determination module 120, configured to determine the billing condition information corresponding to the project coding information based on a first mapping relationship, wherein the first mapping relationship is at least a mapping relationship between the preset project coding information and the pre-designed billing condition information; A determination module 130, used to determine whether the target transaction data satisfies the charging condition in the charging condition information; A second determination module 140 is used to determine, when the target transaction data satisfies the charging condition, the charging rule information corresponding to the project code information and the code of the charging condition satisfied by the target transaction data based on the second mapping relationship, wherein the second mapping relationship is at least a mapping relationship between the preset project code information, the pre-designed fee condition code and the pre-designed fee rule information; The calculation module 150 is used to perform fee calculation on the target transaction data based on the charging rule information to obtain a fee calculation result.

[0133] The above-mentioned data processing device may be in the form of computer software, and each module of the above-mentioned data processing device may be implemented by a computer software module.

[0134] In some embodiments of the present disclosure, the billing conditions in the billing condition information include multiple billing sub-conditions; accordingly, the judgment module 130 is used to: match the target transaction data with the multiple billing sub-conditions respectively; and when the target transaction data satisfies multiple billing sub-conditions, determine that the target transaction data satisfies the billing conditions in the billing condition information.

[0135] In some embodiments of the present disclosure, each billing sub-condition includes a parameter code and a condition type and a condition value corresponding to the parameter code; accordingly, the data processing device also includes: a second judgment module, used to judge whether the parameter value corresponding to the parameter code in the target transaction data satisfies the condition type and the condition value for a billing sub-condition; and a third determination module, used to determine that the target transaction data satisfies a billing sub-condition when the parameter value satisfies the condition type and the condition value.

[0136] In some embodiments of the present disclosure, the billing condition information also includes deduplication information, and the deduplication information includes a deduplication type and a deduplication parameter code; accordingly, the data processing device also includes: a fourth determination module, used to determine the deduplication parameter value corresponding to the deduplication type based on a third mapping relationship, wherein the third mapping relationship is at least a mapping relationship between a preset deduplication type and a preset deduplication parameter value; and a stop module, used to stop processing the target transaction data when the parameter value corresponding to the deduplication parameter code in the target transaction data is the same as the deduplication parameter value, and there is a parameter value identical to the deduplication type in the target transaction data.

[0137] In some embodiments of the present disclosure, the second determination module 140 is specifically used for: when the deduplication parameter value corresponding to the deduplication type cannot be determined, or the parameter value corresponding to the deduplication parameter encoding in the target transaction data is different from the deduplication parameter value, or the parameter value identical to the deduplication type does not exist in the target transaction data, if the target transaction data satisfies the billing conditions, then based on the second mapping relationship, determine the billing rule information corresponding to the project coding information and the coding of the billing conditions satisfied by the target transaction data.

[0138] In some embodiments of the present disclosure, the data processing device also includes: a first generation module, which is used to generate a mapping relationship between a deduplication type and a parameter value corresponding to the deduplication parameter encoding in the target transaction data when the deduplication parameter value corresponding to the deduplication type cannot be determined, or the parameter value corresponding to the deduplication parameter encoding in the target transaction data is different from the deduplication parameter value, or the parameter value identical to the deduplication type does not exist in the target transaction data, and store the generated mapping relationship in a third mapping relationship.

[0139] In some embodiments of the present disclosure, the billing rule information includes a rate type and a rate; accordingly, the calculation module 150 is used to: calculate the fee according to the target transaction data, the rate type and multiple rates; and obtain the fee calculation result according to the fee.

[0140] In some embodiments of the present disclosure, the calculation module 150 is used to: when the rate type is a fixed amount type, use the rate as the fee; and when the rate type is a proportional type, use the product of the rate and the transaction amount in the target transaction data as the fee.

[0141] In some embodiments of the present disclosure, the billing rule information also includes a minimum fee and a maximum fee; accordingly, the calculation module 150 is used to: when the fee is less than or equal to the minimum fee, use the minimum fee as the fee calculation result; when the fee is greater than the minimum fee and less than the maximum fee, use the fee as the fee calculation result; and when the fee is greater than or equal to the maximum fee, use the maximum fee as the fee calculation result.

[0142] In some embodiments of the present disclosure, the data processing device also includes: a fifth determination module, used to determine at least one statistical dimension parameter code corresponding to the project coding information based on a fourth mapping relationship, wherein the fourth mapping relationship is at least a mapping relationship between preset project coding information and at least one preset statistical dimension parameter code; a generation module, used to generate a target SQL query statement based on at least one statistical dimension parameter code and a predefined SQL statement template, wherein the target SQL query statement is used to perform dimensional statistics on the cost calculation result of at least one target transaction data based on at least one statistical dimension parameter code; and an execution module, used to execute the target SQL query statement to obtain a dimensional statistical result.

[0143] The implementation process of the functions and effects of each module in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, which will not be repeated here.

[0144] The execution subject of the data processing method in the specific implementation manner of the present disclosure may be a mobile phone, a computer or other electronic device.

[0145] Therefore, based on any one of the above embodiments, the present disclosure further provides an electronic device, which can execute the data processing method of any one of the embodiments described above in the present disclosure.

[0146] Fig.13 1 is a schematic block diagram of the structure of an electronic device 1000 according to an embodiment of the present disclosure.

[0147] The hardware structure of the electronic device 1000 can be implemented using a bus architecture. The bus architecture can include any number of interconnected buses and bridges, depending on the specific application and overall design constraints of the hardware. The bus 1100 connects various circuits including one or more processors 1200, memory 1300 and / or hardware modules together. The bus 1100 can also connect various other circuits 1400 such as peripherals, voltage regulators, power management circuits, external antennas, etc.

[0148] The bus 1100 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Component (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the figure only uses one connecting line, but does not mean that there is only one bus or one type of bus.

[0149] The present disclosure also provides a readable storage medium, in which a computer program is stored, and the computer program is used to implement the above method when executed by a processor. "Readable storage medium" can be any device that can contain, store, communicate, propagate or transmit a program for use in an instruction execution system, device or equipment or in combination with these instruction execution systems, devices or equipment. More specific examples of readable storage media include the following: an electrical connection portion (electronic device) with one or more wirings, a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and editable read-only memory (EPROM or flash memory), an optical fiber device, and a portable read-only memory (CDROM), etc.

[0150] The present disclosure also provides a computer program product. The method of the present disclosure can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed, the process or function of the present disclosure is executed in whole or in part.

[0151] The computer program or instructions may be stored in a readable storage medium or transmitted from one readable storage medium to another readable storage medium, for example, the computer program or instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired or wireless means. The readable storage medium may be any available medium that can be accessed or a data storage device such as a server, data center, etc. that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a digital video disk; it may also be a semiconductor medium, such as a solid state drive. The computer readable storage medium may be a volatile or non-volatile storage medium, or may include both volatile and non-volatile types of storage media.

[0152] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0153] The present disclosure is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the present disclosure. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0154] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0155] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0156] In the description of this specification, the description with reference to the terms "one embodiment / method", "some embodiments / methods", "example", "specific example", or "some examples" etc. means that the specific features, structures, or characteristics described in conjunction with the embodiment / method or example are included in at least one embodiment / method or example of the present disclosure. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment / method or example. Moreover, the specific features, structures, or characteristics described may be combined in any one or more embodiments / methods or examples in a suitable manner. In addition, those skilled in the art may combine and combine different embodiments / methods or examples described in this specification and features of different embodiments / methods or examples, unless they are contradictory.

[0157] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of the present disclosure, "plurality" means at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0158] Those skilled in the art should understand that the above embodiments are only for the purpose of clearly illustrating the present disclosure, and are not intended to limit the scope of the present disclosure. For those skilled in the art, other changes or modifications may be made based on the above disclosure, and these changes or modifications are still within the scope of the present disclosure.

Claims

1. A data processing method, characterized in that: include: Obtaining item coding information in target transaction data; Determine the billing condition information corresponding to the project coding information based on a first mapping relationship, wherein the first mapping relationship is at least a mapping relationship between preset project coding information and pre-designed billing condition information; Determining whether the target transaction data satisfies the charging condition in the charging condition information; In the case where the target transaction data satisfies the charging condition, determining, based on a second mapping relationship, charging rule information corresponding to the project code information and the code of the charging condition satisfied by the target transaction data, wherein the second mapping relationship is at least a mapping relationship between preset project code information, pre-designed fee condition code and pre-designed fee rule information; and The target transaction data is charged based on the charging rule information to obtain a charge calculation result.

2. The data processing method according to claim 1, characterized in that: The charging condition in the charging condition information includes a plurality of charging sub-conditions; Determining whether the target transaction data satisfies the charging condition in the charging condition information includes: Matching the target transaction data with the multiple charging sub-conditions respectively; as well as In a case where the target transaction data satisfies the multiple charging sub-conditions, it is determined that the target transaction data satisfies the charging condition in the charging condition information.

3. The data processing method according to claim 2, characterized in that: Each of the charging sub-conditions includes a parameter code and a condition type and a condition value corresponding to the parameter code; The method further comprises: For one of the charging sub-conditions, determining whether the parameter value corresponding to the parameter code in the target transaction data satisfies the condition type and the condition value; and In a case where the parameter value satisfies the condition type and the condition value, it is determined that the target transaction data satisfies one of the billing sub-conditions.

4. The data processing method according to claim 2, characterized in that: The charging condition information also includes deduplication information, and the deduplication information includes a deduplication type and a deduplication parameter code; The method further comprises: Determine a deduplication parameter value corresponding to the deduplication type based on a third mapping relationship, wherein the third mapping relationship is at least a mapping relationship between a preset deduplication type and a preset deduplication parameter value; and When the parameter value corresponding to the deduplication parameter code in the target transaction data is the same as the deduplication parameter value, and a parameter value with the same deduplication type exists in the target transaction data, processing of the target transaction data is stopped.

5. The data processing method according to claim 4, characterized in that: In the case where the target transaction data satisfies the charging condition, determining, based on the second mapping relationship, charging rule information corresponding to the item code information and the code of the charging condition satisfied by the target transaction data, including: When the deduplication parameter value corresponding to the deduplication type cannot be determined, or the parameter value corresponding to the deduplication parameter encoding in the target transaction data is different from the deduplication parameter value, or the parameter value identical to the deduplication type does not exist in the target transaction data, if the target transaction data satisfies the billing conditions, then based on the second mapping relationship, the billing rule information corresponding to the item coding information and the encoding of the billing conditions satisfied by the target transaction data is determined.

6. The data processing method according to claim 5, characterized in that: The method further comprises: When the deduplication parameter value corresponding to the deduplication type cannot be determined, or the parameter value corresponding to the deduplication parameter code in the target transaction data is different from the deduplication parameter value, or the parameter value identical to the deduplication type does not exist in the target transaction data, a mapping relationship between the deduplication type and the parameter value corresponding to the deduplication parameter code in the target transaction data is generated, and the generated mapping relationship is stored in the third mapping relationship.

7. The data processing method according to claim 1, characterized in that: The charging rule information includes rate type and rate; Performing fee calculation on the target transaction data based on the charging rule information to obtain a fee calculation result includes: Calculating fees based on the target transaction data, the rate type, and multiple of the rates; as well as The fee calculation result is obtained according to the fee.

8. The data processing method according to claim 1, characterized in that: After calculating the fee for the target transaction data based on the charging rule information to obtain the fee calculation result, the method further includes: Based on a fourth mapping relationship, determining at least one statistical dimension parameter code corresponding to the project code information, wherein the fourth mapping relationship is at least a mapping relationship between preset project code information and at least one preset statistical dimension parameter code; Generate a target SQL query statement according to the at least one statistical dimension parameter code and a predefined SQL statement template, wherein the target SQL query statement is used to perform dimensional statistics on a cost calculation result of at least one target transaction data based on the at least one statistical dimension parameter code; and Execute the target SQL query statement to obtain dimension statistical results.

9. An electronic device, characterized in that: include: A memory storing execution instructions; as well as A processor, wherein the processor executes the execution instruction stored in the memory, so that the processor executes the data processing method according to any one of claims 1 to 8.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the data processing method according to any one of claims 1 to 8 is implemented.

Images