A universal points account management method and system

Abstract

The embodiment of the present invention provides a general points account management method and system, the method comprising: setting activity rules associated with points; accessing various components to obtain the transaction flow of each component; performing points calculation on the transaction flow of the component according to the rule engine to generate a points result file; wherein the rule engine is configured with some activity rules associated with points; adjusting the corresponding accounts according to the account category and account number in the points result file. The embodiment of the present invention implements the application of key technologies such as distributed campus multi-active architecture, streaming computing, rule engine, and sub-library and sub-table, greatly improving data processing performance. The constructed points account system has strong scalability and can meet the rapid expansion of points types in different scenarios.

Description

Technical Field

[0001] The present invention relates to point management, and in particular to a universal point account management method and system. Background Art

[0002] The existing platform points account is independent of the traditional CCB account and is directly linked to customer information.

[0003] In the process of implementing the present invention, the inventors found that there are at least the following problems in the prior art:

[0004] Normally, points accounts are independent of each other, different products correspond to different accounts, and it is cumbersome to query points transaction record information, and the cost of handling problems is high. Summary of the invention

[0005] The embodiment of the present invention provides a universal points account management method and system to solve the technical problems that querying points transaction record information is complicated and the cost of processing the problem is high.

[0006] In a first aspect, an embodiment of the present invention provides a universal points account management method, which includes:

[0007] Set activity rules associated with points;

[0008] Access each component and obtain the transaction flow of each component;

[0009] Calculating the points of the transaction flow of the component according to the rule engine to generate a points result file; wherein the rule engine is configured with part of the activity rules associated with the points;

[0010] Adjust the corresponding accounts according to the account category and account serial number in the points result file.

[0011] In a second aspect, an embodiment of the present invention provides a universal points account management system, which includes:

[0012] A setting module is used to set activity rules associated with points;

[0013] The access module is used to access various components and obtain the transaction flow of each component;

[0014] A calculation module is used to calculate the points of the transaction flow of the component according to the rule engine and generate a points result file; wherein the rule engine is configured with some of the activity rules associated with the points; and an adjustment module is used to adjust the corresponding accounts according to the account category and account serial number in the points result file.

[0015] In a third aspect, an embodiment of the present invention provides a computer-readable storage medium having a computer program stored thereon, which implements the universal points account management method when executed by a processor.

[0016] In a fourth aspect, an embodiment of the present invention provides a computer device, comprising:

[0017] one or more processors;

[0018] A storage device for storing one or more programs;

[0019] When the one or more programs are executed by the one or more processors, the one or more processors are enabled to implement the universal points account management method.

[0020] The above technical solution has the following beneficial effects:

[0021] The embodiment of the present invention adopts sub-library and sub-table, and transactions are completely isolated. There is no need to consider the tedious matters of transaction isolation, and the error rate is low; it has strong versatility and is easy to extract common and unified implementation; the business operation is simple and pure; it can support parameterized adjustment of the validity period, the point cleaning algorithm is simple, and it supports service-oriented design. Calculation and batch processing basically do not involve batch operations on accounts, and can all be converted into single account operations. It is simpler to support 7*24 hours. This reduces the impact of the validity period parameter setting on the system implementation plan and reduces the complexity of point cleaning; it is easy to control the data scale of the point account master file.

[0022] The embodiment of the present invention realizes the application of key technologies such as distributed campus multi-active architecture, streaming computing, rule engine, sub-library and sub-table, which greatly improves data processing performance. The constructed points account system has strong scalability and can meet the rapid expansion of points types in different scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0024] Figure 1 It is an overall flow chart of a universal points account management method according to an embodiment of the present invention;

[0025] Figure 2 It is an overall design diagram of the integral calculation of an embodiment of the present invention;

[0026] Figure 3is a specific processing flow chart of the preprocessing of an embodiment of the present invention;

[0027] Figure 4 is a diagram of a basic integral calculation process according to an embodiment of the present invention;

[0028] Figure 5 is a processing logic diagram of the rule engine of an embodiment of the present invention;

[0029] Figure 6 It is a functional block diagram of a universal points account management system provided by an embodiment of the present invention;

[0030] Figure 7 is a functional block diagram of a computing module provided by an embodiment of the present invention;

[0031] Figure 8 It is a functional block diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0032] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0033] The following is a terminology explanation:

[0034] Transfer-out party: The business initiation point, which uses the "eventual consistency" solution to control the cross-database operation process of the subject.

[0035] Transfer-in party: Provide positive transactions and corresponding reverse transactions to meet the reversal function under abnormal circumstances. Also need to provide transactions for querying the transfer-in status.

[0036] One of the technical problems solved by the embodiments of the present invention is: supporting the comprehensive points calculation of different products, opening up multi-channel points usage, centrally managing customer feedback activities, realizing the merger and use of in-bank points accounts, and supporting the query of the full amount of points transaction records.

[0037] The embodiment of the present invention supports the comprehensive points calculation of different products, opens up the use of points through multiple channels, and traditional accounts are independent of each other, which are directly linked to customer information. The points account management method and system of the embodiment of the present invention distinguishes the corresponding products and activities by the points account type and the points account serial number, realizes the accumulation of customer points, supports the comprehensive points calculation of different products, opens up the use of points through multiple channels, realizes the merger and use of points accounts within the bank, and can query the full amount of points transaction records at the same time.

[0038] Figure 1 This is an overall flow chart of a general points account management method according to an embodiment of the present invention. Figure 1 As shown, the method comprises the following steps:

[0039] S110: Setting activity rules associated with points.

[0040] In this embodiment, the activity rules associated with points may include: calculation rules for calculating points, and any one or more of customer screening rules for screening customers, filtering rules for filtering invalid transaction flows, and verification rules for verifying the points cap value.

[0041] The points customer service management system supports flexible configuration of activities, and can set basic points rules, points reward activity rules and points feedback activity rules. Corresponding to the points accumulation and points redemption scenarios, the activity rules can be set according to different conditions. In this embodiment, the points customer service management system, its function is to configure the points activity rules, including: basic points rules, points reward activity rules and points feedback activity rules. The points feedback rules correspond to the points feedback activities, mainly the rules for redeeming points, such as the points redemption ratio, the points redemption minimum limit and other points usage rules. The activity rules associated with points are mainly used to screen transaction flows and calculate the accumulable points value. Specifically, the calculation rules for points calculation set in step S110 may include steps S112-S116.

[0042] Step S112: Setting basic points rules.

[0043] Basic points rules are for daily points calculation for products and transactions. They are valid for a long time and increase with the addition of new salable products. They do not attach characteristics of customers and contracts. Basic points are not restricted by activities and are directly applicable to rules. There is one basic rule for each salable product, and the source of rule elements is mainly the transaction information of the product.

[0044] Step S114: Setting the points reward activity rules.

[0045] The reward points calculation for specific marketing activities is limited to the activity time, customer range, and product range. The dimensions of reward rules include time, product, customer, transaction and other levels, and the source of rule elements also involves multiple components such as comprehensive points, customer information, and products. Reward rules are the corresponding rules under the points reward activity. Multiple reward rules can be set for the same reward activity.

[0046] Step S116: Setting the points reward activity rules.

[0047] The time, customers, and service content of the points feedback are limited through activities. The dimensions of the rules are mainly the time, customers, and service content of the feedback. The elements of the rules come from the corresponding online transactions. The elements of the points transferred by the third party are derived from the product number and time.

[0048] S120: Connect to each component and obtain the transaction flow of each component.

[0049] The points calculation management system supports data access for different scenarios and can be flexibly set according to the current scenario. After setting the corresponding activities, it receives the transaction data of each component, matches the reward activity rules according to the information of configuring different components, and calculates the points according to the corresponding activity rules that are matched. The reward activity rules can be associated with the basic points rules, and the transaction flow that matches the basic points rules can match the corresponding reward activity rules. Match the values ​​of the corresponding fields in the transaction data with the values ​​set in the reward rules. For example, when the rule sets the transaction type to consumption, the rule will only be matched when the transaction type in the transaction flow is consumption.

[0050] Differentiate data sources for different scenarios, such as credit card components, Dragon Payment components, etc.

[0051] The data of each component is the transaction flow of the corresponding channel, and the channels for obtaining points are expanded by connecting to each component.

[0052] Credit card consumption refers to the transaction flow paid by using credit cards, which can be divided into transactions using credit cards through WeChat and using credit cards through Alipay. When setting up activities, you can set up activities separately according to the transaction channels.

[0053] After filtering out invalid transactions, the basic points rules and points reward activity rules are matched according to the data in the valid transactions. When the data in the transaction completely matches the data set in the rule engine, a piece of data with a rule number is generated. Specifically, the value in the data is passed to the rule engine, and the rule engine returns the matched rule number, associates the rule number with this transaction, and generates a new piece of data.

[0054] For example, when setting the points rule, if you set the transaction type to 4, you can get twice the points of the transaction amount. In this case, only transactions with transaction type 4 will match the points rule in the transaction data, and the accumulated points will be calculated based on the transaction amount.

[0055] In this embodiment, invalid transactions can be filtered out based on some general rules, such as merchants that do not count points, blacklisted customers, and other conditions.

[0056] S130: Rule engine calculation: This step calculates the points of the transaction flow of the above components according to the rule engine and generates a points result file.

[0057] Optionally, this step may specifically include the following processing steps: screening the transaction flows of the components, filtering the transaction flows that do not count points, and generating valid transaction flows; matching corresponding points calculation rules in the rule engine based on the valid transaction flows; performing points calculation based on the matched points calculation rules to generate a points result file.

[0058] S140: Adjusting the points account: This step adjusts the corresponding account according to the account type and account sequence number in the points result file.

[0059] In some embodiments, the account category and account number can be used to identify an independent account. The points value obtained by the same customer in different channels may not be universal, so it is necessary to use the account category and account number to distinguish them. The same is true when using points. Points obtained in one channel can only be used in the current scenario.

[0060] In this embodiment, the activity rules associated with the points include the rules in the rule engine, and the rules stored in the rule engine are only part of the rule information of the activity rules associated with the points.

[0061] The rule engine is only a part of the points activity rules, and is also generated in the configuration of the activity rules associated with the points. The transaction flows of different components must also be combined with the rules that are not in the rule engine (that is, the rules other than the rule engine in the activity rules associated with the points) to calculate the points and generate the points result file. Calculation based on the rule engine is only part of the points calculation. The cap value verification will also be performed later. When the activity sets the bonus points cap value, it will be verified later whether the customer's accumulated points in the current activity have reached the cap value.

[0062] Rule engine: The design goal is to separate the integral calculation and integral activity configuration parts from the application code, so that the calculation / configuration activity part is not bound to the business logic, so as to achieve dynamic maintenance and easy expansion. In some exemplary embodiments, the calculation part of the rule engine uses jexl3 expressions. jexl3 supports many grammatical rules and can meet many requirements that may be involved in calculations, logical judgments, loops, etc. When the rule engine is accessed for the first time, the rule engine will read all templates (formula templates used when calculating integrals) into the working memory at one time, and will no longer be loaded repeatedly in the future, but will read the memory to improve execution efficiency. The rule engine is a restriction when setting rules, and the integral value is calculated according to the set formula when the rules are met.

[0063] In this embodiment, the rule engine calculates at the end of each day, unloads the rule file, screens the transaction flow of the upstream components, filters the flow that does not record points, generates a valid flow file, performs rule matching calculation, and generates a points result file. The above-mentioned rule matching calculation means: when setting the rule, a corresponding calculation rule will be generated at the same time, and the corresponding calculation rule will be found through the rule number and flow data, and the accumulative points value will be calculated according to the transaction amount in the flow data. Specifically, when setting the rule, the conditions for matching the rules will be set, such as transaction amount, transaction channel, transaction method, etc., which will be stored in the rule engine; at the same time, it will also set how many points can be accumulated if the conditions are met, such as how many times the points can be given according to the consumption amount, or how many points can be accumulated according to the number of consumption. This is the calculation rule, and the two are associated through the rule number. First, the data that meets the conditions is matched in the rule engine, and then the accumulative points value is calculated by the formula.

[0064] The characteristics of point calculation are large amount of calculation, high concurrency, high requirements for flexibility and scalability, and high complexity of calculation logic. Point calculation includes four major processing processes: preprocessing, point rule screening, point calculation, and point calculation result update. Point calculation includes rule engine calculation, which only calculates the point value that the current transaction flow should obtain according to the rules. Point calculation includes rule engine calculation and subsequent capping value verification to calculate the final points that the customer can obtain in this transaction in this activity, that is, the final accumulated point value. Figure 2 This is the overall design diagram of the integral calculation of the embodiment of the present invention. Figure 2 As shown, the integral calculation specifically includes the following steps:

[0065] S132: Step 1, preprocessing step, which is to preprocess the input data for integral calculation.

[0066] Figure 3 Detailed processing flow chart of the preprocessing of the embodiment of the present invention. Figure 3 As shown, in some exemplary embodiments, the preprocessing step S132 may include the following processing sub-steps:

[0067] S132_1: Product component data field mapping step. This step processes the product source data files from various channels into a unified interface file. As an example, this step can be further refined into the following steps:

[0068] S132_11: Input or obtain product source data file.

[0069] S132_12: Field mapping is performed on the product source data file to obtain a unified interface file for point calculation. In this embodiment, since the data fields of each component are different, they need to be processed separately, the data source is identified by the component number, and the data is processed into the required data format.

[0070] S132_13: Output the unified interface file for the integral calculation.

[0071] S132_14: According to the unified interface file for point calculation, the transaction type is determined. In this embodiment, the transaction type is determined by the corresponding component according to the needs of each component. For example, Long Pay includes recharge, withdrawal, face-to-face transfer, payment, refund (return transaction), ATM withdrawal, withdrawal application, sending red envelopes, receiving red envelopes, etc.

[0072] S132_15: When the transaction type is a return transaction, the accumulated points are eliminated according to the original transaction serial number. Specifically, there is a field in the transaction data called transaction type, and whether it is a return transaction can be determined according to its value.

[0073] S132_16: When the transaction type does not belong to a return transaction and the transaction type matches the transaction type set in the rule, it is determined to perform the points calculation. Specifically, when setting the reward activity rule, the transaction type will be set, and the subsequent calculation will be performed only when the transaction type in the transaction flow matches the transaction type set in the points rule, otherwise the transaction flow will be set as invalid.

[0074] S132_2: Customer screening step. In this step, the customer information data is screened according to the customer screening rules to form a list of customers that meet the customer screening rules. As an example, when setting the rules, the customer screening rules can be set, such as setting the customer star rating to be greater than 3 to match. In the subsequent calculation, the customer star rating will be queried to determine whether it meets the conditions for accumulating points.

[0075] S132_3: Points rule loading step. In this step, all points rules required for points calculation are obtained through the rule engine and the online library. The process of loading points activities and rules is to load certain data in the online library into the rule engine. Optionally, when initialized every day, the rules that take effect on that day will be screened out in the online library and loaded into the rule engine. In this embodiment, a points activity is added first, and the rules corresponding to the points activity are configured based on the points activity, that is, the activity comes first, and then the rules. Points activities include: activity name, points validity period and other activity-related information, and rules include cap value, customer information and other rule information.

[0076] Preferably, the sub-steps included in the above step S132 may be executed in the order of S132_3, S132_2, and S132_1.

[0077] S134: Step 2, points rule screening step, this step screens out the data range for points calculation from the pre-processed data according to the filtering rules for filtering invalid transaction flows. As an example, this step filters out the flow that does not count points, such as blacklisted merchants, blacklisted customers and other conditions.

[0078] In some exemplary implementations, step S134 may include the following sub-steps:

[0079] S134_1: Obtain one or more points rules from the rule engine. As an example, the one or more points rules may be selected from one or more of the following: basic points rules, bonus points rules corresponding to a single transaction, and bonus points rules corresponding to cumulative transactions.

[0080] S134_2: According to the obtained one or more integral rules, one or more filtering processes are performed on the pre-processed input data to obtain a filtered data range. As an example, in this step, any one or more of the following filtering processes are performed:

[0081] According to the basic integration rules, the pre-processed input data is filtered;

[0082] Filter the pre-processed input data according to the reward points rules corresponding to a single transaction;

[0083] The pre-processed input data is filtered according to the reward points rules corresponding to the accumulated transactions.

[0084] In this embodiment, the bonus point rules can be divided into independent bonus rules and bonus rules associated with basic points.

[0085] S134_3: Output the filtered data range.

[0086] S136: Step 3, the point calculation step, which is to calculate the points according to the calculation formula. In this step, the specific calculation formula is related to the rule setting. For example, the ratio of the amount to the points can be set according to the amount, or a fixed point value can be awarded according to the number of consumptions. In this step, the points are calculated according to the calculation formula to generate the original point value (including the calculation of the basic points and the bonus points); according to the upper limit of the points set in the rules, the final accumulable point value is determined.

[0087] The above fixed points value is awarded based on the number of consumption. For example, if you spend three times at a merchant that calculates points through Long Pay, you can accumulate 3,000 points. Only if the customer spends three times at a merchant that calculates points through Long Pay during the event, will the corresponding 3,000 points be accumulated after the third consumption.

[0088] In some exemplary implementations, step S136 may include the following sub-steps:

[0089] S136_1: Perform basic points calculation according to the basic points rule.

[0090] S136_2: Calculate the reward points rules corresponding to a single transaction according to the points reward activity rules.

[0091] S136_3: According to the points reward activity rules, the reward points rules corresponding to the accumulated transactions are calculated.

[0092] S136_4: Integral adjustment This step is optional and can be omitted in some implementations.

[0093] S136_5: Get the original value of the integral calculation. The original value of the integral calculation is calculated by matching the rules, finding the corresponding calculation formula, and calculating according to the data in the flow. The original value of the integral calculation depends on how the rules are set. The original value of the integral calculation can be set as a fixed value or set to a ratio with the transaction amount to calculate the integral value.

[0094] S136_6: Get the final integral calculation result. In this step, the final integral calculation result is determined based on the original integral calculation value, the accumulated integral value and the integral upper limit determined by the verification rule for the integral cap value verification. Specifically, the integral cap value can be set when setting the rule. The final integral calculation result is calculated based on the sum of the calculated original value and the accumulated integral value under the rule, and compared with the set cap value. This step is an online transaction, and the previous one is data batch processing. After the data is processed into the required format, the automatic task calls the online transaction to determine the final calculation result, so as to adjust the account balance and generate the integral details.

[0095] S138: Step 4, the integral calculation result updating step, which synchronizes the integral calculation result to the online library through the online service.

[0096] In some exemplary implementations, step S138 may include the following sub-steps:

[0097] S138_1: Perform a detailed summary to obtain the final accumulated points value for the customer.

[0098] S138_2: Call the synchronous online points data service to update the account.

[0099] Figure 4 This is the basic integral calculation process of the embodiment of the present invention. Figure 4 As shown, Figure 4 The points in the system include basic points. Taking basic points as an example, the points calculation is a process of filtering according to the rules through a unified interface file and combining the points calculation formula to generate points details. Through the single transaction points calculation, the points value that can be obtained from a single transaction data is calculated.

[0100] The point result update is to summarize the accumulated points of each rule and adjust the customer's point balance and other related information. In this way, the complex account and detail update business logic can be controlled through a unified online service. Avoid the update logic being distributed in both online and batch, which increases the complexity of subsequent maintenance. Through online transactions, the update unit is controlled in a single customer's account, which can better support 365*24, avoid the cumbersome problems caused by batch operations and batch data, and improve customer experience.

[0101] The above-mentioned batch refers to batch processing of data, which mainly includes filtering and screening of pipelines, matching rules, and calculating integral values.

[0102] Among them, the above-mentioned online refers to the calculated points result file, calling the online service one by one, determining the final points calculation result according to the points upper limit, and then adjusting the account points balance.

[0103] Figure 4 The basic integral calculation process mainly includes the following steps:

[0104] S210: Receive the transaction flow pushed by the upstream component, that is, the unified interface file, and filter out invalid transaction flow on the unified interface file, for example, according to the rule of not counting points, filter out invalid flow, or according to the product dimension points rule (differentiated according to the saleable product number), or according to the blacklist customer rule. After filtering out invalid transaction flow, the specified condition data (such as transaction type, transaction number, transaction channel, transaction amount, transaction method, etc.) in the valid transaction flow is transmitted to the rule engine, and the rule engine returns the matched rule number, associates the rule number with this valid transaction flow, and generates a new flow data. Figure 4 The source data filtering rules in the code refer to filtering the original flow pushed by the upstream components.

[0105] S220: According to the matched rule number, obtain the score calculation formula or method corresponding to the rule number. Then calculate the single transaction score according to the corresponding score calculation formula, and generate the initial score accumulation details. The initial score accumulation details may include: customer number, rule number, accumulation time, initial accumulated score value, source transaction serial number, etc.

[0106] S230: Call the online service to calculate the final score value that can be obtained. The calling of the online service is to adjust the score upper limit according to the initial score accumulation details and the accumulated score statistics information, calculate the final score value, that is, obtain the adjusted score accumulation details. The above-mentioned accumulated score statistics information may include: customer number, rule number, daily accumulated value, monthly accumulated value, current accumulated value, etc. The above-mentioned adjusted score accumulation details may include: customer number, rule number, accumulated score value, etc. The accumulated score value here is the score value that the customer finally obtains after passing the verification. The daily accumulation is how many points the customer has accumulated in total under this activity on that day. The monthly accumulation is how many points the customer has accumulated in total under this activity in that month. The annual accumulation is how many points the customer has accumulated in total under this activity in that year.

[0107] S240: This step is also performed in the online service. After the final points value is calculated, it is convenient for adjusting the account points balance and generating or updating the points details.

[0108] Figure 5 This is the processing logic and execution process of the rule engine of the embodiment of the present invention. Figure 5 As shown, the activity rules, date screening rules, product transaction screening rules and customer screening rules are put into the points rule engine. The rule engine makes the setting of rules more flexible. One points activity corresponds to one rule group, which contains multiple rules. Through the rule group, multiple restrictions can be configured under one activity. One activity corresponds to one rule group, and the rule group contains the conditions that can match the activity. When setting the rules, you can set the date rule transaction type. After setting the date rule, the rule can only be matched if the transaction date meets the conditions. Figure 5 The main tasks are to set the rule engine node, call the rule engine client, and match the rules. The rule engine includes a rule library that stores multiple scoring rules.

[0109] The rule assembly module is used to perform domain analysis on the data in the domain field table and to parse the rule table data to form a rule decision tree. Rule decision tree: The tree structure formed by the rule conditions.

[0110] The rule parsing module is used to parse the data in the rule table.

[0111] The query and storage engine module is used to query and store rule engine information.

[0112] Working memory is used to store domain fields, rule groups, rule decision trees and other information. One bonus point activity corresponds to a rule group, which contains multiple rules. The same bonus point activity can be configured through the rule group. A rule group is a collection of rules corresponding to an activity. Domain field: The value of the set rule condition, for example: if the transaction type is equal to 4, 4 is stored in the domain field.

[0113] The rule base is used to store rule tables, domain field tables and other related information.

[0114] The execution engine module is used to load a rule set and parse the rules. At the same time, according to the rule reasoning engine, the parsed rules are executed on the specific input data objects.

[0115] Pattern matchers are used to decide which rule to execute and when to execute it.

[0116] An agenda manager determines the order in which the rules picked by the pattern matcher are executed.

[0117] Design engine module, used to set conflict detection module and rule verification module.

[0118] The conflict detection module is used to resolve conflicts and put the activated rules in order.

[0119] The rule verification module is used to verify whether the data matches the rules.

[0120] S140: Adjust the points account.

[0121] This step can adjust the corresponding accounts according to the account type and account number in the points result file to adjust the account points balance.

[0122] The embodiment of the present invention adopts the technology of sub-library and sub-table to support large data volume and high concurrency. According to the scheme of hashing the "customer number", the data segmentation design is carried out. The embodiment of the present invention is oriented to all individual customers of the bank and 27 asset products. The amount of data is large, and the technology of sub-library and sub-table is adopted to reduce the processing pressure of a single database; the sub-library and sub-table are divided vertically and then horizontally. Vertical refers to the internal division of the comprehensive integration into mutually isolated basic modules, and horizontal refers to the horizontal segmentation of the table within each module.

[0123] Account structure features: Each account record only stores the accumulated data within the current validity period;

[0124] Account balance relationship: Available points = calculated points + increased points - reduced points - redeemed points.

[0125] The core of cross-database operations lies in the control of data consistency and integrity, which are divided into transferor and transferee based on the participating entities.

[0126] The advantages of the embodiments of the present invention are:

[0127] The embodiment of the present invention adopts sub-library and sub-table, and transactions are completely isolated. There is no need to consider the tedious matters of transaction isolation, and the error rate is low; it has strong versatility and is easy to extract common and unified implementation; the business operation is simple and pure; it can support parameterized adjustment of the validity period, the point cleaning algorithm is simple, and it supports service-oriented design. Calculation and batch processing basically do not involve batch operations on accounts, and can all be converted into single account operations. It is simpler to support 7*24 hours. This reduces the impact of the validity period parameter setting on the system implementation plan and reduces the complexity of point cleaning; it is easy to control the data scale of the point account master file.

[0128] The embodiment of the present invention realizes the application of key technologies such as distributed campus multi-active architecture, streaming computing, rule engine, sub-library and sub-table, which greatly improves data processing performance. The constructed points account system has strong scalability and can meet the rapid expansion of points types in different scenarios.

[0129] Figure 6 is a functional block diagram of a universal points account management system provided by an embodiment of the present invention. Figure 6 As shown, it includes:

[0130] A setting module is used to set activity rules associated with points;

[0131] The access module is used to access various components and obtain the transaction flow of each component;

[0132] A calculation module, used to calculate the points of the transaction flow of the component according to the rule engine and generate a points result file; wherein the rule engine is configured with part of the activity rules associated with the points;

[0133] The account adjustment module is used to adjust the corresponding accounts according to the account category and account sequence number in the score result file.

[0134] In an optional embodiment, the activity rules associated with points include: point calculation rules for calculating points, and any one or any more of customer screening rules for screening customers, filtering rules for filtering invalid transaction flows, and verification rules for verifying the points cap value; wherein, when setting the calculation rules for calculating points, the setting module is specifically used to execute any one or any more of the following: setting basic point rules; setting point reward activity rules; setting point feedback activity rules.

[0135] In an optional embodiment, the access module can be specifically used to: connect the data of each component, match the reward rules according to the information of configuring different components, and calculate the points according to the matched activity rules.

[0136] In an optional embodiment, the calculation module can be specifically used to: screen the transaction flows of the components, filter the transaction flows that do not count points, and generate valid transaction flows; match the corresponding points calculation rules in the rule engine based on the valid transaction flows; and perform points calculation based on the matched points calculation rules to generate a points result file.

[0137] In an optional embodiment, if Figure 7 As shown, the calculation module may specifically include:

[0138] Preprocessing unit: used to preprocess the input data for integral calculation;

[0139] Points rule screening unit: used to screen out the data range for points calculation from the pre-processed data according to the filtering rules for filtering invalid transaction flows;

[0140] An integral calculation unit: used to calculate the integral according to the filtered data range and the calculation formula contained in the integral calculation rule matched from the rule engine to obtain the integral calculation result;

[0141] Point calculation result updating unit: used to synchronize the point calculation result to the online library through the online service.

[0142] In an optional embodiment, the preprocessing unit is specifically used to: process the product source data file into a unified interface file; filter the customer information data according to the customer screening rules to form a customer list that meets the customer screening rules; and obtain all required points calculation rules through the rule engine and the online library.

[0143] In an optional embodiment, the integral calculation unit may specifically include:

[0144] A first calculation subunit, used for performing basic integral calculation according to the basic integral rule;

[0145] A second calculation subunit is used to calculate the reward points rules corresponding to a single transaction according to the points reward activity rules;

[0146] A third calculation subunit is used to calculate the reward points rules corresponding to the accumulated transactions according to the points reward activity rules;

[0147] Get the subunit to obtain the original value of the integral calculation;

[0148] The final integral calculation subunit is used to determine the final integral calculation result according to the integral calculation original value, the accumulated integral value and the integral upper limit determined by the verification rule for performing integral capping value verification.

[0149] The embodiment of the present invention further provides an electronic device, such as Figure 8 As shown, it includes one or more processors 301 , a communication interface 302 , a memory 303 and a communication bus 304 , wherein the processor 301 , the communication interface 302 , and the memory 303 communicate with each other via the communication bus 304 .

[0150] Memory 303, used for storing computer programs;

[0151] The processor 301 is used to implement each step of any one of the above-mentioned universal points account management methods when executing the program stored in the memory 303.

[0152] The points account management method of the embodiment of the present invention distinguishes corresponding products and activities through the points account type and the points account serial number, realizes the accumulation of customer points, supports the comprehensive points calculation of different products, opens up multi-channel points use, and realizes the merger and use with the in-bank points account.

[0153] The communication bus mentioned in the above electronic device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. The communication interface is used for communication between the above electronic device and other devices.

[0154] The memory may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0155] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0156] An embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, each step of any one of the above-mentioned universal points account management methods is implemented.

[0157] Those skilled in the art may also understand that the various illustrative logical blocks, units, and steps listed in the embodiments of the present invention may be implemented by electronic hardware, computer software, or a combination of the two. In order to clearly demonstrate the interchangeability of hardware and software, the various illustrative components, units, and steps described above have generally described their functions. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the described functions for each specific application, but such implementation should not be understood as exceeding the scope of protection of the embodiments of the present invention.

[0158] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0159] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, electronic device, and readable storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0160] The above description is only a preferred embodiment of the present invention and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.

Claims

1. A general points account management method, characterized in that: include: Set activity rules associated with points; Access each component and obtain the transaction flow of each component; The transaction flow of the component is calculated based on the rule engine to generate a score result file; wherein, the rule engine is configured with some of the activity rules associated with the points; the rule engine separates the score calculation and the score activity configuration part from the application code, so that the calculation / configuration activity part is not bound to the business logic; when the rule engine is accessed for the first time, the rule engine will read all the formula templates used for calculating the points into the working memory at one time, and will no longer be loaded repeatedly in the future, but read the memory; the score calculation includes the rule engine calculation and the subsequent cap value verification to calculate the final points that the customer can obtain in this activity for this transaction, that is, the final accumulated score value; Adjust the corresponding accounts according to the account type and account serial number in the points result file; The activity rules associated with points include: a point calculation rule for performing point calculation, and any one or more of a customer screening rule for screening customers, a filtering rule for filtering invalid transaction flows, and a verification rule for performing point cap verification; wherein the calculation rules set for performing point calculation specifically include any one or more of the following: Set basic points rules; set points reward activity rules; set points feedback activity rules; The basic points rules are for daily points calculation for products and transactions, are valid for a long time, increase with the addition of new saleable products, and do not attach characteristics of customers and contracts; basic points are not restricted by activities and are directly applicable to the rules; one saleable product corresponds to one basic rule, and the source of the rule elements is mainly the transaction information of the product; The points reward activity rules are for the calculation of reward points for specific marketing activities, and limit the activity time, customer range and product range; the dimensions of the reward rules include time, product, customer and transaction, and the sources of rule elements involve comprehensive points, customer information and products; the reward rules are the corresponding rules under the points reward activity, and multiple reward rules are set for the same reward activity; The points feedback activity rules limit the time, customers and service content of the points feedback through the activities. The dimensions of the rules are mainly the time, customers and service content of the feedback; the elements of the rules are derived from the corresponding online transactions; the points transferred by the third party are derived from the product number and time; The said calculating the points of the transaction flow of the said component according to the rule engine and generating the points result file specifically includes: Screening the transaction flow of the component, filtering the transaction flow that does not count the points, generating a valid transaction flow; matching the corresponding points calculation rule in the rule engine according to the valid transaction flow; performing points calculation according to the matched points calculation rule to generate a points result file, including: Preprocessing step: preprocessing input data for integral calculation; integral rule screening step: screening the data range for integral calculation from the preprocessed data according to the filtering rules for filtering invalid transaction flows; integral calculation step: calculating the integral according to the screened data range and the calculation formula included in the integral calculation rule matched from the rule engine to obtain the integral calculation result; integral calculation result updating step: synchronizing the integral calculation result to the online library through the online service; The pre-processing step comprises: S132_1: Product component data field mapping step, processing the product source data files from various channels into a unified interface file, including: S132_11: Input or obtain product source data file; S132_12: Perform field mapping on the product source data file to obtain a unified interface file for point calculation; since the data fields of each component are different, they need to be processed separately, and the data source is identified by the component number, and the data is processed into the required data format; S132_13: Output the integral calculation unified interface file; S132_14: According to the unified interface file for point calculation, the transaction type is determined by the corresponding component according to the requirements of each component; S132_15: When the transaction type is a return transaction, the accumulated points are eliminated according to the original transaction serial number; there is a field in the transaction data called transaction type, and its value can be used to determine whether it is a return transaction; S132_16: When the transaction type does not belong to a return transaction and the transaction type matches the transaction type set in the rule, it is determined to execute the points calculation; when setting the reward activity rules, the transaction type will be set, and the subsequent calculation will only be performed when the transaction type in the transaction flow matches the transaction type set in the points rule, otherwise the transaction flow will be set as invalid; S132_2: Customer screening step, screening customer information data according to customer screening rules to form a list of customers that meet the customer screening rules; customer screening rules can be set when setting rules, and the customer star rating will be queried in subsequent calculations to determine whether it meets the conditions for accumulating points; S132_3: Points rule loading step, obtain all points rules required for points calculation through the rule engine and online library; the process of loading points activities and rules is to load certain data in the online library into the rule engine; when initializing every day, the rules that take effect on the day will be screened out from the online library and loaded into the rule engine; first add points activities, and configure the rules corresponding to the points activities based on the points activities, that is, there are activities first and then rules; points activities include: activity name, points validity period and other activity-related information, and rules include cap value, customer information and other rule information; the execution order of the above steps can be S132_3, S132_2, S132_1; The points rule screening step includes: receiving the transaction flow pushed by the upstream component, that is, the unified interface file, filtering the invalid transaction flow from the unified interface file, including filtering the invalid transaction flow according to the rule of not counting points, filtering the invalid transaction flow according to the product dimension points rule based on the saleable product number, or filtering the invalid transaction flow according to the blacklist customer rule; after filtering out the invalid transaction flow, transmitting the specified condition data including the transaction type, transaction number, transaction channel, transaction amount and transaction method in the valid transaction flow to the rule engine, the rule engine returns the matched rule number, associates the rule number with the valid transaction flow, and generates a new flow data; The points calculation step includes: obtaining a points calculation formula or method corresponding to the rule number according to the matched rule number; then calculating the points of a single transaction according to the corresponding points calculation formula obtained, and generating initial points accumulation details; the initial points accumulation details include: customer number, rule number, accumulation time, initial accumulated points value and source transaction serial number; Calling the online service to calculate the final score value that can be obtained; the calling of the online service is to adjust the score upper limit according to the initial score accumulation details and the accumulated score statistical information, and calculate the final score value, that is, to obtain the adjusted score accumulation details; the accumulated score statistical information includes: customer number, rule number, daily accumulated value, monthly accumulated value and annual accumulated value; the adjusted score accumulation details include: customer number, rule number and accumulated score value; the accumulated score value is the score value that the customer finally obtains after passing the verification; the daily accumulated value is how many points the customer has accumulated in total under this activity on that day; the monthly accumulated value is how many points the customer has accumulated in total under this activity in that month; the annual accumulated value is how many points the customer has accumulated in total under this activity in that year; The step of updating the points calculation result includes: calculating the final points value in the online service to adjust the account points balance and generate or update the points details.

2. The method according to claim 1, characterized in that The access to each component and obtaining the transaction flow of each component specifically includes: After setting up the corresponding activities, the transaction data of each component is received, the points reward activity rules are matched according to the information of the configured different components, and the points are calculated according to the matched activity rules.

3. The method according to claim 1, characterized in that The pre-processing step specifically includes: Process product source data files into unified interface files; Screen customer information data according to customer screening rules to form a list of customers that meet the customer screening rules; All the required integral rules for integral calculation are obtained through the rule engine and the online library.

4. The method according to claim 1, characterized in that: The step of calculating the integral according to the filtered data range and the calculation formula contained in the integral calculation rule matched from the rule engine to obtain the integral calculation result specifically includes: Perform basic points calculation according to the basic points rule; According to the points reward activity rules, the reward points rules corresponding to a single transaction are calculated; According to the points reward activity rules, the reward points rules corresponding to the accumulated transactions are calculated; Get the original value of integral calculation; The final integral calculation result is determined according to the integral calculation original value, the accumulated integral value and the integral upper limit determined by the verification rule for performing integral capping value verification.

5. A universal points account management system, characterized in that: include: A setting module is used to set activity rules associated with points; The access module is used to access various components and obtain the transaction flow of each component; A calculation module is used to calculate the points of the transaction flow of the component according to the rule engine and generate a points result file; wherein, the rule engine is configured with some of the activity rules associated with points; the rule engine separates the points calculation and points activity configuration parts from the application code, so that the calculation / configuration activity parts are not bound to the business logic; when the rule engine is accessed for the first time, the rule engine will read all the formula templates used for calculating points into the working memory at one time, and will no longer be loaded repeatedly in the future, but read from the memory; the points calculation includes the calculation of the rule engine and the subsequent capping value verification to calculate the points that the customer can finally obtain in this activity for this transaction, that is, the final accumulated points value; An account adjustment module, used to adjust the corresponding accounts according to the account category and account sequence number in the score result file; The activity rules associated with points include: a point calculation rule for performing point calculation, and any one or more of a customer screening rule for screening customers, a filtering rule for filtering invalid transaction flows, and a verification rule for performing point cap verification; wherein the calculation rules set for performing point calculation specifically include any one or more of the following: Set basic points rules; set points reward activity rules; set points feedback activity rules; The basic points rules are for daily points calculation for products and transactions, are valid for a long time, increase with the addition of new saleable products, and do not attach characteristics of customers and contracts; basic points are not restricted by activities and are directly applicable to the rules; one saleable product corresponds to one basic rule, and the source of the rule elements is mainly the transaction information of the product; The points reward activity rules are for the calculation of reward points for specific marketing activities, and limit the activity time, customer range and product range; the dimensions of the reward rules include time, product, customer and transaction, and the sources of rule elements involve comprehensive points, customer information and products; the reward rules are the corresponding rules under the points reward activity, and multiple reward rules are set for the same reward activity; The points feedback activity rules limit the time, customers and service content of the points feedback through the activities. The dimensions of the rules are mainly the time, customers and service content of the feedback; the elements of the rules are derived from the corresponding online transactions; the points transferred by the third party are derived from the product number and time; The calculation module is specifically used to: screen the transaction flow of the component, filter the transaction flow that does not count points, and generate a valid transaction flow; match the corresponding point calculation rule in the rule engine according to the valid transaction flow; perform point calculation according to the matched point calculation rule to generate a point result file, specifically including: Preprocessing unit: used for preprocessing input data for integral calculation; integral rule screening unit: used for screening out a data range for integral calculation from the preprocessed data according to a filtering rule for filtering invalid transaction flow; integral calculation unit: used for calculating integral according to the screened data range and a calculation formula included in the integral calculation rule matched from the rule engine to obtain an integral calculation result; integral calculation result updating unit: used for synchronizing the integral calculation result to the online library through an online service; The pre-processing unit is specifically used for: S132_1: Product component data field mapping step, processing the product source data files from various channels into a unified interface file, including: S132_11: Input or obtain product source data file; S132_12: Perform field mapping on the product source data file to obtain a unified interface file for point calculation; since the data fields of each component are different, they need to be processed separately, and the data source is identified by the component number, and the data is processed into the required data format; S132_13: Output the integral calculation unified interface file; S132_14: According to the unified interface file for point calculation, the transaction type is determined by the corresponding component according to the requirements of each component; S132_15: When the transaction type is a return transaction, the accumulated points are eliminated according to the original transaction serial number; there is a field in the transaction data called transaction type, and its value can be used to determine whether it is a return transaction; S132_16: When the transaction type does not belong to a return transaction and the transaction type matches the transaction type set in the rule, it is determined to execute the points calculation; when setting the reward activity rules, the transaction type will be set, and the subsequent calculation will only be performed when the transaction type in the transaction flow matches the transaction type set in the points rule, otherwise the transaction flow will be set as invalid; S132_2: Customer screening step, screening customer information data according to customer screening rules to form a list of customers that meet the customer screening rules; customer screening rules can be set when setting rules, and the customer star rating will be queried in subsequent calculations to determine whether it meets the conditions for accumulating points; S132_3: Points rule loading step, obtain all points rules required for points calculation through the rule engine and online library; the process of loading points activities and rules is to load certain data in the online library into the rule engine; when initializing every day, the rules that take effect on the day will be screened out from the online library and loaded into the rule engine; first add points activities, and configure the rules corresponding to the points activities based on the points activities, that is, there are activities first and then rules; points activities include: activity name, points validity period and other activity-related information, and rules include cap value, customer information and other rule information; the execution order of the above steps can be S132_3, S132_2, S132_1; The points rule screening unit is specifically used to: receive the transaction flow pushed by the upstream component, that is, the unified interface file, and filter the invalid transaction flow from the unified interface file, including filtering the invalid flow according to the rule of not counting points, filtering out the invalid flow according to the product dimension points rule based on the saleable product number, or filtering out the invalid flow according to the blacklist customer rule; after filtering out the invalid transaction flow, transmitting the specified condition data including the transaction type, transaction number, transaction channel, transaction amount and transaction method in the valid transaction flow to the rule engine, and the rule engine returns the matched rule number, associates the rule number with this valid transaction flow, and generates a new flow data; The point calculation unit is specifically used to: obtain a point calculation formula or method corresponding to the rule number according to the matched rule number; then calculate the single transaction points according to the corresponding point calculation formula obtained, and generate initial point accumulation details; the initial point accumulation details include: customer number, rule number, accumulation time, initial accumulated point value and source transaction serial number; Calling the online service to calculate the final score value that can be obtained; the calling of the online service is to adjust the score upper limit according to the initial score accumulation details and the accumulated score statistical information, and calculate the final score value, that is, to obtain the adjusted score accumulation details; the accumulated score statistical information includes: customer number, rule number, daily accumulated value, monthly accumulated value and annual accumulated value; the adjusted score accumulation details include: customer number, rule number and accumulated score value; the accumulated score value is the score value that the customer finally obtains after passing the verification; the daily accumulated value is how many points the customer has accumulated in total under this activity on that day; the monthly accumulated value is how many points the customer has accumulated in total under this activity in that month; the annual accumulated value is how many points the customer has accumulated in total under this activity in that year; The point calculation result updating unit is specifically used to: calculate the final point value in the online service to adjust the account point balance and generate or update the point details.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the universal points account management method as described in any one of claims 1 to 4 is implemented.

7. A computer device, characterized in that: It includes: one or more processors; A storage device for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the universal points account management method as described in any one of claims 1-4.

Images