Flow Accumulation Control Method, Device and Equipment Based on Asynchronous Alarm Configuration

Abstract

The present invention discloses a traffic cumulative control method, device and equipment based on asynchronous warning configuration. The method includes: embodiments of the present invention provide a traffic cumulative control method, device and equipment based on asynchronous warning configuration, determining whether the transaction request information from the client satisfies the warning rule, if so, determining whether the interception condition is satisfied, if not satisfying the warning rule or the interception condition, completing the transaction and obtaining the transaction record information, if satisfying the interception condition, intercepting the transaction request information, updating the quota configuration table according to the transaction record information, and asynchronously configuring and updating the warning database according to the transaction record information and the quota configuration table when the database update condition is satisfied. The present invention belongs to the technical field of risk control, advancing the process of warning and interception judgment for transaction request information, and asynchronously configuring and updating the warning database without the user's perception after the transaction is completed, reducing the complexity of traffic control processing and improving the processing efficiency.

Description

Technical Field

[0001] The present invention relates to the technical field of risk control, belonging to the application scenario of cumulative control of transaction traffic based on asynchronous alert configuration in intelligent finance, and particularly relates to a method, device and equipment for cumulative traffic control based on asynchronous alert configuration. Background Art

[0002] To avoid transaction risks, enterprises usually need to perform cumulative traffic judgment to achieve quota control and quickly evaluate transaction risks based on quota control. In the prior art, there are mainly two implementation methods for cumulative traffic control. One implementation is to perform real-time accumulation to perform one traffic calculation at the cost of one write, and read the cumulative traffic value at the cost of one read to achieve cumulative traffic judgment and control. However, if new cumulative traffic configuration rules are added, historical transaction traffic will be ignored and cannot be retrospectively judged through the new cumulative traffic configuration rules. Another implementation method is to overcome the drawbacks of the first implementation method. That is, each transaction traffic triggers a data insertion to implement the landing of the original traffic data, and then the cumulative traffic value is obtained by aggregating and reading in a per-transaction cumulative manner. Although the second implementation method can solve the problem of adding new cumulative traffic configuration rules during the cumulative traffic judgment process, the complexity of reading the cumulative traffic value also increases sharply, affecting the data processing performance of the system. Due to the low processing efficiency, the latency of the feedback result of the cumulative traffic judgment increases, and the requirements of high throughput and high availability cannot be met. Therefore, there is a problem of low data processing efficiency in the prior art methods for performing cumulative judgment and control of transaction traffic. Summary of the Invention

[0003] Embodiments of the present invention provide a method, device and equipment for cumulative traffic control based on asynchronous alert configuration, aiming to solve the problem of low data processing efficiency existing in the prior art methods for performing cumulative judgment and control of transaction traffic.

[0004] In a first aspect, embodiments of the present invention provide a method for cumulative traffic control based on asynchronous alert configuration. The method includes:

[0005] If transaction request information from any client is received, determine whether the transaction request information meets a preset alert rule;

[0006] If the transaction request information meets the alert rule, determine whether the transaction request information meets a preset interception condition according to a preset alert database and quota configuration table;

[0007] If the transaction request information does not meet the alert rule or does not meet the interception condition, process the transaction request information to complete the transaction, and record the processing process of the transaction request information to obtain transaction record information;

[0008] If the transaction request information meets the interception condition, intercept the transaction request information and feedback a prompt message indicating transaction failure to the client;

[0009] Update the quota configuration table according to the transaction record information;

[0010] Determine whether the warning rule and the updated quota configuration table meet the preset database update conditions;

[0011] If the database update conditions are met, asynchronously configure and update the warning database according to the transaction record information and the quota configuration table.

[0012] In a second aspect, an embodiment of the present invention provides a traffic accumulation control device based on asynchronous warning configuration, which includes:

[0013] A transaction request information judgment unit, configured to, if transaction request information from any client is received, determine whether the transaction request information meets a preset warning rule;

[0014] An interception judgment unit, configured to, if the transaction request information meets the warning rule, determine whether the transaction request information meets a preset interception condition according to a preset warning database and a quota configuration table;

[0015] A transaction record information acquisition unit, configured to, if the transaction request information does not meet the warning rule or does not meet the interception condition, process the transaction request information to complete the transaction, and record the processing process of the transaction request information to obtain transaction record information;

[0016] A prompt message feedback unit, configured to, if the transaction request information meets the interception condition, intercept the transaction request information and feedback a prompt message indicating transaction failure to the client;

[0017] A quota configuration table update unit, configured to update the quota configuration table according to the transaction record information;

[0018] An update judgment unit, configured to determine whether the warning rule and the updated quota configuration table meet the preset database update conditions;

[0019] An asynchronous configuration update unit, configured to, if the database update conditions are met, asynchronously configure and update the warning database according to the transaction record information and the quota configuration table.

[0020] In a third aspect, an embodiment of the present invention further provides a computer device, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, it implements the traffic cumulative control method based on asynchronous warning configuration described in the first aspect above.

[0021] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, in which the computer-readable storage medium stores a computer program. When the computer program is executed by a processor, the processor is caused to execute the traffic cumulative control method based on asynchronous warning configuration described in the first aspect above.

[0022] An embodiment of the present invention provides a traffic cumulative control method, device, and equipment based on asynchronous warning configuration, which determines whether the transaction request information from the client satisfies the warning rule. If it is satisfied, it determines whether the interception condition is satisfied according to the warning database and the quota configuration table. If the warning rule is not satisfied or the interception condition is not satisfied, the transaction request information is processed to complete the transaction and obtain the transaction record information. If the interception condition is satisfied, the transaction request information is intercepted, the quota configuration table is updated according to the transaction record information, and when the database update condition is satisfied, the warning database is asynchronously configured and updated according to the transaction record information and the quota configuration table. Through the above method, the warning database is asynchronously configured and updated, and the process of warning and intercepting judgment on the transaction request information is preposed. After the transaction is completed, the warning database is asynchronously configured and updated without the user's awareness, reducing the complexity of controlling and processing the transaction traffic data, improving the processing efficiency and the system response speed, and meeting the requirements of high throughput and high availability. Description of the Drawings

[0023] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0024] Figure 1 It is a schematic flowchart of the traffic cumulative control method based on asynchronous warning configuration provided by an embodiment of the present invention;

[0025] Figure 2 It is a schematic diagram of the application scenario of the traffic cumulative control method based on asynchronous warning configuration provided by an embodiment of the present invention;

[0026] Figure 3 It is a schematic sub-flowchart of the traffic cumulative control method based on asynchronous warning configuration provided by an embodiment of the present invention;

[0027] Figure 4 Another sub - process schematic diagram of the traffic cumulative control method based on asynchronous alert configuration provided by an embodiment of the present invention;

[0028] Figure 5 Another sub - process schematic diagram of the traffic cumulative control method based on asynchronous alert configuration provided by an embodiment of the present invention;

[0029] Figure 6 Another sub - process schematic diagram of the traffic cumulative control method based on asynchronous alert configuration provided by an embodiment of the present invention;

[0030] Figure 7 The last sub - process schematic diagram of the traffic cumulative control method based on asynchronous alert configuration provided by an embodiment of the present invention;

[0031] Figure 8 Another process schematic diagram of the traffic cumulative control method based on asynchronous alert configuration provided by an embodiment of the present invention;

[0032] Figure 9 Schematic block diagram of the traffic cumulative control device based on asynchronous alert configuration provided by an embodiment of the present invention;

[0033] Figure 10 Schematic block diagram of the computer device provided by an embodiment of the present invention. Detailed implementation manners

[0034] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are some, but not all, of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0035] It should be understood that when used in this specification and the appended claims, the terms "comprises" and "comprising" indicate the presence of the described features, wholes, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or their combinations.

[0036] It should also be understood that the terms used in this specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. As used in this specification of the present invention and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an", and "the" are intended to include the plural forms.

[0037] It should also be further understood that the term "and / or" used in the specification and appended claims of the present invention refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0038] Please refer to Figure 1 and Figure 2 , Figure 1 is a schematic flowchart of the traffic cumulative control method based on asynchronous alert configuration provided by an embodiment of the present invention; Figure 2 is a schematic diagram of an application scenario of the traffic cumulative control method based on asynchronous alert configuration provided by an embodiment of the present invention; the traffic cumulative control method based on asynchronous alert configuration is applied to the cloud server 10, and the traffic cumulative control method based on asynchronous alert configuration is executed through application software installed in the cloud server 10. A network connection is established between the cloud server 10 and the client 20 to realize the transmission of data information; the cloud server 10 is the server side for executing the traffic cumulative control method based on asynchronous alert configuration to cumulatively control the transaction traffic, such as a server constructed by an enterprise or a government department; the client 20 is a terminal device for the customer to use and establish a network connection with the cloud server to realize the transmission of data information, such as a desktop computer, a laptop computer, a tablet computer or a mobile phone, or a payment terminal such as a POS machine. As Figure 1 shown, the method includes steps S110 to S170.

[0039] S110. If transaction request information from any client is received, determine whether the transaction request information meets a preset alert rule.

[0040] If transaction request information from any client is received, it is determined whether the transaction request information meets a preset warning rule. The warning rule is pre-configured in the cloud server, which can determine whether the transaction request information meets the warning rule. If it meets, subsequent warning interception processing is performed; if it does not meet, the transaction request information is directly released. Specifically, the client can be a payment terminal configured by a merchant. The payment terminal can interact with the consumer's terminal device, the consumer's bank card or credit card. For example, it can scan the QR code displayed on the terminal device (by using a barcode scanner connected to a desktop computer or laptop to scan the QR code, or by using the built-in camera of a mobile phone or tablet to scan the QR code), or interact with the NFC (Near Field Communication) module of the terminal device. The bank card or credit card is used for contactless payment at the payment terminal (such as contactless payment through a POS machine). After the payment terminal reads information such as the payment identifier based on the information interaction, it generates transaction request information and sends it to the cloud server. The cloud server processes the transaction request information to complete the payment operation. The warning rule can be used to determine whether the transaction request information is a large-amount transaction request. For the vast majority of merchants, the proportion of transaction request information that meets the warning rule is extremely low. Therefore, most transaction request information does not require subsequent warning interception processing.

[0041] In one embodiment, as Figure 3 shown, step S110 includes sub-steps S111 and S112.

[0042] S111. Obtain the transaction limit that matches the transaction attribute in the transaction request information in the warning rule.

[0043] Specifically, the transaction request information also includes a merchant identification code and a transaction attribute. The merchant identification code is the identification code information registered by the merchant in the cloud server before the transaction. The merchant identification code corresponds to the merchant one by one. The transaction attribute can be attribute information related to the merchant. For example, the transaction attribute can be catering, clothing, home appliances, or cosmetics, etc. The warning rule contains multiple basic categories, and each basic category corresponds to one or more transaction attributes. The basic category to which the transaction attribute belongs can be obtained according to the transaction attribute of the transaction request information, so as to classify the transaction attribute, and calculate the transaction limit after obtaining the basic limit corresponding to the basic category that matches the transaction attribute, so as to obtain the transaction limit that matches the warning rule according to the transaction attribute.

[0044] For example, in a warning rule, a certain basic category is the "medium amount category". The transaction attributes of the "medium amount category" include cosmetics and dining. The corresponding basic limit for the medium amount category is 500 yuan. If the transaction attribute in a certain transaction request information is dining, then this transaction request information matches the medium amount category. Multiply the basic limit of 500 by the basic coefficient to obtain the transaction limit. For example, if the basic coefficient can be initially configured as 0.75, then the transaction limit corresponding to this transaction request information is 375. More specifically, if there is historical transaction data corresponding to the merchant identification code of the transaction request information, the basic coefficient can be dynamically adjusted according to the historical transaction data corresponding to this transaction request information. For example, if the proportion of historical transaction data that meets the warning rule is greater than 10%, then increase the basic coefficient; if the proportion of historical transaction data that meets the warning rule is less than 1%, then decrease the basic coefficient.

[0045] S112. Determine whether the transaction amount in the transaction request information is greater than the transaction limit to determine whether the transaction request information meets the warning rule.

[0046] The transaction request information also includes the transaction amount, which is the transaction amount generated by this transaction. It can be determined whether the transaction amount is greater than the transaction limit, so as to determine whether the transaction request information meets the warning rule. If the transaction amount is greater than the transaction limit, it is determined that the transaction request information meets the warning rule; if the transaction amount is not greater than the transaction limit, it is determined that the transaction request information does not meet the warning rule.

[0047] S120. If the transaction request information meets the warning rule, determine whether the transaction request information meets the preset interception condition according to the preset warning database and quota configuration table.

[0048] If the transaction request information meets the warning rule, determine whether the transaction request information meets the preset interception condition according to the preset warning database and quota configuration table. The cloud server is also configured with a warning database and a quota configuration table. The warning database is a database used to record warning information, and the quota configuration table is a data table for configuring quota values such as the daily limit for each merchant. It can be determined whether the transaction request information meets the interception condition according to the warning database and the quota configuration table. The interception condition is a judgment condition for judging whether to intercept the transaction request information. Among them, the warning database includes a warning dictionary and a blacklist dictionary.

[0049] In one embodiment, as Figure 4 shown, step S120 includes sub-steps S121, S122, S123, S124, and S125.

[0050] S121. Determine whether the warning dictionary contains the merchant identification code in the transaction request information; S122. If the warning dictionary contains the merchant identification code, obtain the daily limit corresponding to the transaction request information from the quota configuration table.

[0051] The warning dictionary records warning objects and warning record information corresponding to the warning objects. It can be judged whether there is a warning object corresponding to the merchant identification code in the transaction request information in the warning dictionary, and a judgment result on whether the warning dictionary contains the merchant identification code can be obtained. After the merchant completes registration, the daily limit corresponding to the registered merchant can be configured in the quota configuration table. If the warning dictionary contains the merchant identification code, the daily limit corresponding to the merchant identification code can be obtained from the quota configuration table.

[0052] S123. According to the interception condition, determine whether the sum of the transaction amount in the transaction request information and the dangerous amount stored in the blacklist dictionary is greater than the daily limit.

[0053] The blacklist dictionary stores suspected blacklist objects and dangerous record information corresponding to the suspected blacklist objects. The dangerous record information includes dangerous amount and dangerous times. The sum of the transaction amount in the transaction request information and the dangerous amount stored in the blacklist dictionary can be calculated according to the interception condition, and it can be judged whether the obtained calculated value is greater than the daily limit. The dangerous amount in the suspected blacklist object is equivalent to the current warning value. The effect of the original full-volume query is achieved by accumulating the current warning value and the increased value (the newly added transaction amount), that is, an incremental aggregation query is performed based on the current warning value. The incremental aggregation query can also provide a higher parallel throughput. Compared with the full-volume aggregation query from the first transaction to the newly added transaction amount, the corresponding amount can be queried and judged more quickly and a judgment result can be obtained.

[0054] S124. If the warning dictionary does not contain the merchant identification code or the sum of the transaction amount and the dangerous amount is not greater than the daily limit, determine that the transaction request information does not meet the interception condition; S125. If the sum of the transaction amount and the dangerous amount is greater than the daily limit, determine that the transaction request information meets the interception condition.

[0055] If the warning dictionary does not contain the merchant identification code or the sum of the transaction amount and the dangerous amount is not greater than the daily limit, determine that the transaction request information does not meet the interception condition and release the transaction request information. If the sum of the transaction amount and the dangerous amount is greater than the daily limit, determine that the transaction request information meets the interception condition.

[0056] S130. If the transaction request information does not meet the warning rule or the interception condition, process the transaction request information to complete the transaction, and record the processing process of the transaction request information to obtain transaction record information.

[0057] If the transaction request information does not meet the warning rule or the interception condition, it indicates that the transaction request information can be directly released. Process the transaction request information to complete the transaction. For example, the transaction settlement can be completed by deducting the payment for the transaction request information. The processing of this transaction request information is completed. The processing process of the transaction request information can be recorded to obtain transaction record information. Transaction record information is the record information obtained by recording the transaction processing process. The transaction record information at least includes the merchant identification code, transaction amount, transaction status, transaction time, and warning record. The warning record is the information used to record whether the transaction request information corresponding to the transaction record information meets the warning rule.

[0058] S140. If the transaction request information meets the interception condition, intercept the transaction request information and feedback a transaction failure prompt message to the client.

[0059] If the transaction request information meets the interception condition, if the transaction request information meets the interception condition, the transaction request information needs to be intercepted. This payment transaction fails, and a transaction failure prompt message can be feedback to the client. The processing of this transaction request information is completed.

[0060] S150. Update the quota configuration table according to the transaction record information.

[0061] Update the quota configuration table according to the transaction record information. The quota configuration table is also configured with the cumulative amount and cumulative times corresponding to the merchant. The cumulative amount is the cumulative amount obtained by accumulating all the transaction amounts of each merchant on the same day. The cumulative times is the number of times accumulated for all successful transactions of each merchant on the same day. After obtaining the transaction record information, the quota configuration table can be updated.

[0062] In an embodiment, as Figure 5 shown, step S150 includes sub-steps S151, S152, and S153.

[0063] S151. Update the pre-stored transaction base table according to the transaction record information.

[0064] Specifically, a transaction base table is also configured in the cloud server. For each processed transaction request message, the corresponding transaction record information can be recorded in the transaction base table. The transaction base table records the specific processing information of each transaction request message, that is, the transaction base table is used to record the specific information of each transaction. For example, the transaction base table can be constructed based on the Mongo database. In the actual processing process, the transaction base table can also be constructed based on other database technologies.

[0065] S152. Determine whether the transaction status in the transaction record information is successful; S153. If the transaction status in the transaction record information is successful, calculate the quota update information according to the transaction base table and the quota configuration table and update the quota configuration table.

[0066] It can be determined whether the transaction status in the transaction record information is successful. If the transaction status is successful, the quota update information is calculated according to the cumulative amount and cumulative times currently recorded in the transaction base table and the quota configuration table. The quota update information includes the new cumulative quota and the new cumulative times. The changestream can be customized based on the transaction set to update the quota configuration table. Changestream is an abstraction of oplog in the Mongo database. After listening to various Mongo operation commands (such as insert, delete, update, query, etc.) in the transaction base table through changestream, they are replayed. Specifically, the cumulative amount of the current record is added to the newly added transaction amount in the transaction base table to calculate the new cumulative quota, and the cumulative times are incremented by one to obtain the new cumulative times. If the transaction status is not successful, there is no need to update the quota configuration table.

[0067] S160. Determine whether the warning rule and the updated quota configuration table meet the preset database update conditions.

[0068] After the quota configuration table is updated, it can be determined whether the updated quota configuration table and the warning rule meet the preset database update conditions. If the quota configuration table is not updated, that is, there is no need to determine whether it meets the database update conditions. Among them, the database update conditions include the warning dictionary update condition and the blacklist dictionary update condition. It can be sequentially determined whether the warning dictionary update condition and the blacklist dictionary update condition are met based on the quota configuration table. The quota configuration table is also configured with the daily limit times and the safety line of each merchant.

[0069] In one embodiment, as Figure 6 shown, step S160 includes sub-steps S161, S162, and S163.

[0070] S161. Determine whether the cumulative amount and cumulative times in the quota configuration table meet the warning dictionary update condition based on the daily limit, daily limit times, and safety line configured in the quota configuration table.

[0071] Specifically, calculate the quota configuration value according to the daily limit and the safety line, calculate the limit times configuration value according to the daily limit times and the safety line, and determine whether the cumulative amount is greater than the quota configuration value and whether the cumulative times is greater than the limit times configuration value. If the cumulative amount is greater than the quota configuration value or the cumulative times is greater than the limit times configuration value, it is determined that the warning dictionary update condition is met; otherwise, it is determined that the warning dictionary update condition is not met.

[0072] S162. Determine whether the cumulative amount and cumulative times in the quota configuration table meet the blacklist dictionary update condition based on the daily limit, the daily limit times, and the warning rule.

[0073] The warning rule includes a basic limit and a basic coefficient, and the product of the basic limit and the basic coefficient is the transaction limit. It can be determined whether the cumulative times is greater than the daily limit times and whether the cumulative amount is greater than the difference between the daily limit and the transaction limit. If the cumulative times is greater than the daily limit times or the cumulative amount is greater than the difference between the daily limit and the transaction limit, it is determined that the blacklist dictionary update condition is met; otherwise, it is determined that the blacklist dictionary update condition is not met.

[0074] S163. If the cumulative amount and cumulative times in the quota configuration table meet the warning dictionary update condition or meet the blacklist dictionary update condition, it is determined that the database update condition is met.

[0075] Since determining whether the warning dictionary update condition is met is a prerequisite for determining whether the blacklist dictionary update condition is met, if the warning dictionary update condition is met, it does not necessarily mean that the blacklist dictionary update condition is met; if the blacklist dictionary update condition is met, the warning dictionary update condition must be met. If the warning dictionary update condition is met or both the warning dictionary update condition and the blacklist dictionary update condition are met, the warning database needs to be configured and updated, and it is determined that the database update condition is met; if the warning dictionary update condition is not met and the blacklist dictionary update condition is not met, there is no need to configure and update the warning database, and it is determined that the database update condition is not met.

[0076] S170. If the database update condition is met, asynchronously configure and update the warning database according to the transaction record information and the quota configuration table.

[0077] If the database update condition is satisfied, the warning database is asynchronously configured and updated according to the transaction record information and the quota configuration table. Specifically, if the database update condition is satisfied, the warning database can be asynchronously configured and updated based on MQ (Message Queue). The warning database subscribes to MQ messages and performs asynchronous configuration updates based on the received messages. Since the process of configuring and updating the warning database is after the transaction request information is processed, the customer (merchant) is unaware of the asynchronous configuration update process.

[0078] In one embodiment, as Figure 7 shown, step S170 includes sub-steps S171, S172, S173, and S174.

[0079] S171. Generate corresponding new warning record information according to the transaction record information and the quota configuration table; S172. Add the new warning record information to the warning dictionary of the warning database to complete the asynchronous configuration update of the warning dictionary.

[0080] If the database update condition is satisfied, the updated quota configuration table must satisfy the warning dictionary update condition. The merchant identification code and transaction time can be obtained from the transaction record information, the cumulative quota and cumulative times can be obtained from the quota configuration table, and the obtained information is combined to generate new warning record information. Then, the merchant identification code can be used as the warning object of the new warning record information, the cumulative quota is the warning quota of the new warning record information, the cumulative times is the warning times therein, and the transaction time is the warning time therein. Adding the new warning record information to the warning dictionary can complete the asynchronous configuration update of the warning dictionary.

[0081] S173. If the blacklist dictionary update condition is satisfied, generate corresponding new dangerous record information according to the new warning record information and the warning rules; S174. Add the new dangerous record information to the blacklist dictionary of the warning database to complete the asynchronous configuration update of the blacklist dictionary.

[0082] If the updated quota configuration table also meets the blacklist dictionary update rules, corresponding new risk record information can be generated based on the newly added warning records and warning rules. Specifically, the warning rules include a basic quota and a basic coefficient, and the product of the basic quota and the basic coefficient is the transaction quota. The warning object in the newly added warning record information is used as the suspected blacklist object in the new risk record information. The sum of the warning quota and the transaction quota in the newly added warning record information is used as the risk quota in the new risk record information. The warning count in the newly added warning record information is incremented by one and used as the risk count in the new risk record information. The suspected blacklist object, risk quota, and risk count are combined to generate the corresponding new risk record information. Adding the new risk record information to the blacklist dictionary can complete the asynchronous configuration update of the blacklist dictionary.

[0083] In one embodiment, as Figure 8 shown, after step S170, steps S180 and S190 are further included.

[0084] S180. If the preset rule update time point is reached, clear the warning database and the quota configuration table; S190. Configure and update the warning rules and the quota configuration table according to the transaction bottom table.

[0085] The rule update time point can also be configured in the cloud server. If the rule update time point is reached, the information recorded in the warning dictionary and the blacklist dictionary in the warning database can be cleared, and the cumulative quota and cumulative count in the quota configuration table can be cleared. Specifically, the rule update time point can be a certain time point in the early morning every day, such as 00:00:01. The warning rules and the quota configuration table can be configured and updated according to the historical transaction data stored in the transaction bottom table. The basic coefficient in the warning rules and the safety line in the quota configuration table can be configured and updated. Specifically, the warning ratio can be obtained based on the historical transaction data corresponding to each merchant in the transaction bottom table. Based on the warning records in all the historical transaction data of each merchant, the corresponding warning ratio can be statistically obtained. For example, if it is determined that the warning ratio is greater than 10%, the basic coefficient is increased by 0.1; if it is determined that the warning ratio is less than 1%, the basic coefficient is decreased by 0.05. The range of the configurable safety line is [10%, 100%]. The historical transaction data of the merchant can be classified. For example, the transaction attributes corresponding to the merchant, the daily average transaction amount of the merchant, and the daily average transaction count are obtained and quantitatively processed to obtain the merchant quantitative feature information. Each merchant's quantitative feature information is classified according to the preset classification neural network. If it is obtained that the merchant belongs to the small-amount high-frequency transaction type, the configured value of the safety line can be increased on the basis of the original safety line; if it is obtained that the merchant belongs to the high-amount low-frequency transaction type, the configured value of the security can be decreased on the basis of the original safety line.

[0086] The technical method in this application can be applied to the application scenario of cumulative control of transaction traffic based on asynchronous alert configuration, so as to promote the construction of smart finance.

[0087] In the traffic cumulative control method based on asynchronous alert configuration provided by the embodiments of the present invention, it is determined whether the transaction request information from the client meets the alert rule. If it meets, it is determined whether the interception condition is met according to the alert database and the quota configuration table. If the alert rule is not met or the interception condition is not met, the transaction request information is processed to complete the transaction and obtain the transaction record information. If the interception condition is met, the transaction request information is intercepted, the quota configuration table is updated according to the transaction record information, and when the database update condition is met, the alert database is asynchronously configured and updated according to the transaction record information and the quota configuration table. Through the above method, the alert database is asynchronously configured and updated, and the process of alerting and intercepting judgment on the transaction request information is advanced. After the transaction is completed, the alert database is asynchronously configured and updated without the user's perception, reducing the complexity of controlling and processing the transaction traffic data, improving the processing efficiency and system response speed, and meeting the requirements of high throughput and high availability.

[0088] The embodiments of the present invention further provide a traffic cumulative control device based on asynchronous alert configuration. The traffic cumulative control device based on asynchronous alert configuration can be configured in a cloud server, and the traffic cumulative control device based on asynchronous alert configuration is used to execute any embodiment of the foregoing traffic cumulative control method based on asynchronous alert configuration. Specifically, please refer to Figure 9 , Figure 9 which is a schematic block diagram of the traffic cumulative control device based on asynchronous alert configuration provided by the embodiments of the present invention.

[0089] As Figure 9 shown, the traffic cumulative control device 100 based on asynchronous alert configuration includes a transaction request information judgment unit 110, an interception judgment unit 120, a transaction record information acquisition unit 130, a prompt information feedback unit 140, a quota configuration table update unit 150, an update judgment unit 160, and an asynchronous configuration update unit 170.

[0090] The transaction request information judgment unit 110 is used to determine whether the received transaction request information from any client meets the preset alert rule.

[0091] In a specific embodiment, the transaction request information judgment unit 110 includes subunits: a transaction limit acquisition unit, which is used to acquire the transaction limit in the alert rule that matches the transaction attribute in the transaction request information; a transaction amount judgment unit, which is used to judge whether the transaction amount in the transaction request information is greater than the transaction limit, so as to judge whether the transaction request information meets the alert rule.

[0092] An interception judgment unit 120 is configured to, if the transaction request information meets the warning rule, determine whether the transaction request information meets the preset interception condition according to a preset warning database and a quota configuration table.

[0093] In a specific embodiment, the interception judgment unit 120 includes subunits: an identification code judgment unit, configured to determine whether the warning dictionary contains the merchant identification code in the transaction request information; a daily quota acquisition unit, configured to, if the warning dictionary contains the merchant identification code, acquire the corresponding daily quota from the quota configuration table for the transaction request information; a judgment unit, configured to judge whether the sum of the transaction amount in the transaction request information and the dangerous amount stored in the blacklist dictionary is greater than the daily quota according to the interception condition; a first determination unit, configured to determine that the transaction request information does not meet the interception condition if the warning dictionary does not contain the merchant identification code or the sum of the transaction amount and the dangerous amount is not greater than the daily quota; a second determination unit, configured to determine that the transaction request information meets the interception condition if the sum of the transaction amount and the dangerous amount is greater than the daily quota.

[0094] A transaction record information acquisition unit 130 is configured to, if the transaction request information does not meet the warning rule or does not meet the interception condition, process the transaction request information to complete the transaction, and record the processing process of the transaction request information to obtain transaction record information.

[0095] A prompt information feedback unit 140 is configured to, if the transaction request information meets the interception condition, intercept the transaction request information and feedback a prompt information of transaction failure to the client.

[0096] A quota configuration table update unit 150 is configured to update the quota configuration table according to the transaction record information.

[0097] In a specific embodiment, the quota configuration table update unit 150 includes subunits: a transaction bottom table update unit, configured to update a pre-stored transaction bottom table according to the transaction record information; a transaction status judgment unit, configured to judge whether the transaction status in the transaction record information is successful; a quota update unit, configured to, if the transaction status in the transaction record information is successful, calculate quota update information according to the transaction bottom table and the quota configuration table and update the quota configuration table.

[0098] An update judgment unit 160 is configured to judge whether the warning rule and the updated quota configuration table meet the preset database update condition.

[0099] In a specific embodiment, the update judgment unit 160 includes subunits: a first update condition judgment unit, configured to judge whether the cumulative amount and the cumulative times in the quota configuration table meet the warning dictionary update condition according to the daily limit, the daily limit times, and the safety line configured in the quota configuration table; a second update condition judgment unit, configured to judge whether the cumulative amount and the cumulative times in the quota configuration table meet the blacklist dictionary update condition according to the daily limit, the daily limit times, and the warning rule; an update determination unit, configured to determine that the database update condition is met if the cumulative amount and the cumulative times in the quota configuration table meet the warning dictionary update condition or the blacklist dictionary update condition.

[0100] An asynchronous configuration update unit 170, configured to perform asynchronous configuration update on the warning database according to the transaction record information and the quota configuration table if the database update condition is met.

[0101] In a specific embodiment, the asynchronous configuration update unit 170 includes subunits: a new warning record information generation unit, configured to generate corresponding new warning record information according to the transaction record information and the quota configuration table; a warning dictionary configuration update unit, configured to add the new warning record information to the warning dictionary of the warning database to complete the asynchronous configuration update of the warning dictionary; a new dangerous record information generation unit, configured to generate corresponding new dangerous record information according to the new warning record information and the warning rule if the blacklist dictionary update condition is met; a blacklist dictionary configuration update unit, configured to add the new dangerous record information to the blacklist dictionary of the warning database to complete the asynchronous configuration update of the blacklist dictionary.

[0102] In a specific embodiment, the traffic cumulative control device 100 for asynchronous warning configuration further includes subunits: a clearing unit, configured to clear the warning database and the quota configuration table if a preset rule update time point is reached; a configuration update unit, configured to perform configuration update on the warning rule and the quota configuration table according to the transaction bottom table.

[0103] In the traffic cumulative control device based on asynchronous warning configuration provided by the embodiments of the present invention, the above-mentioned traffic cumulative control method based on asynchronous warning configuration is applied to determine whether the transaction request information from the client meets the warning rules. If it meets, it is determined whether the interception condition is met according to the warning database and the quota configuration table. If the warning rules are not met or the interception condition is not met, the transaction request information is processed to complete the transaction and obtain the transaction record information. If the interception condition is met, the transaction request information is intercepted, the quota configuration table is updated according to the transaction record information, and when the database update condition is met, the warning database is asynchronously configured and updated according to the transaction record information and the quota configuration table. Through the above method, the warning database is asynchronously configured and updated, and the process of warning and intercepting judgment on the transaction request information is preposed. After the transaction is completed, the warning database is asynchronously configured and updated without the user's awareness, reducing the complexity of the control and processing of transaction traffic data, improving the processing efficiency and system response speed, and meeting the requirements of high throughput and high availability.

[0104] The above-mentioned traffic cumulative control device based on asynchronous warning configuration can be implemented in the form of a computer program, and this computer program can run on a computer device as shown in Figure 10 .

[0105] Please refer to Figure 10 , Figure 10 which is a schematic block diagram of the computer device provided by the embodiments of the present invention. This computer device can be a cloud server used to execute the traffic cumulative control method based on asynchronous warning configuration to achieve cumulative control of transaction traffic based on asynchronous warning configuration.

[0106] Refer to Figure 10 , the computer device 500 includes a processor 502, a memory, and a network interface 505 connected through a system bus 501. Among them, the memory can include a storage medium 503 and an internal memory 504.

[0107] The storage medium 503 can store an operating system 5031 and a computer program 5032. When the computer program 5032 is executed, the processor 502 can be made to execute the traffic cumulative control method based on asynchronous warning configuration. Among them, the storage medium 503 can be a volatile storage medium or a non-volatile storage medium.

[0108] The processor 502 is used to provide computing and control capabilities to support the operation of the entire computer device 500.

[0109] The internal memory 504 provides an environment for the operation of the computer program 5032 in the storage medium 503. When the computer program 5032 is executed by the processor 502, the processor 502 can be made to execute the traffic cumulative control method based on asynchronous warning configuration.

[0110] The network interface 505 is used for network communication, such as providing data information transmission, etc. Those skilled in the art can understand that Figure 10 the structure shown in Figure 10 is only a block diagram of some structures related to the solution of the present invention, and does not constitute a limitation on the computer device 500 to which the solution of the present invention is applied. The specific computer device 500 may include more or fewer components than those shown in the figure, or combine some components, or have different component arrangements.

[0111] Among them, the processor 502 is used to run the computer program 5032 stored in the memory to implement the corresponding functions in the above-mentioned traffic cumulative control method based on asynchronous alert configuration.

[0112] Those skilled in the art can understand that Figure 10 the embodiment of the computer device shown in Figure 10 does not constitute a limitation on the specific composition of the computer device. In other embodiments, the computer device may include more or fewer components than those shown in the figure, or combine some components, or have different component arrangements. For example, in some embodiments, the computer device may only include a memory and a processor. In such an embodiment, the structures and functions of the memory and the processor are the same as those in Figure 10 the embodiment shown, and will not be elaborated here.

[0113] It should be understood that in the embodiment of the present invention, the processor 502 may be a central processing unit (CPU), and the processor 502 may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0114] In another embodiment of the present invention, a computer-readable storage medium is provided. The computer-readable storage medium may be a volatile or non-volatile computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps included in the above-mentioned traffic cumulative control method based on asynchronous alert configuration are implemented.

[0115] Those skilled in the art can clearly understand that for the convenience and conciseness of description, the specific working processes of the devices, apparatuses, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein. Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present invention.

[0116] In several embodiments provided by the present invention, it should be understood that the disclosed devices, apparatuses, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there can be other division methods, or units with the same function can be aggregated into one unit. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Additionally, the displayed or discussed couplings or direct couplings or communication connections to each other can be indirect couplings or communication connections through some interfaces, devices, or units, or can be electrical, mechanical, or other forms of connection.

[0117] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the objectives of the solution of the embodiments of the present invention.

[0118] In addition, the functional units in each embodiment of the present invention can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

[0119] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. This computer software product is stored in a computer-readable storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned computer-readable storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memories (ROMs), magnetic disks, or optical discs that can store program codes.

[0120] As described above, the above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present invention can easily think of various equivalent modifications or substitutions, and these modifications or substitutions should all be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A traffic cumulative control method based on asynchronous warning configuration, characterized in that The method is applied to a cloud server, and a network connection is established between the cloud server and a client to achieve the transmission of data information. The method includes: If a transaction request message from any client is received, determine whether the transaction request message meets a preset warning rule; If the transaction request message meets the warning rule, determine whether the transaction request message meets a preset interception condition according to a preset warning database and a quota configuration table; If the transaction request message does not meet the warning rule or does not meet the interception condition, process the transaction request message to complete the transaction, and record the processing process of the transaction request message to obtain transaction record information; If the transaction request message meets the interception condition, intercept the transaction request message and feedback a prompt message of transaction failure to the client; Update the quota configuration table according to the transaction record information; Determine whether the warning rule and the updated quota configuration table meet a preset database update condition; If the database update condition is met, asynchronously configure and update the warning database according to the transaction record information and the quota configuration table; The determining whether the transaction request message meets the preset warning rule includes: Obtain a transaction limit that matches the transaction attribute in the transaction request message in the warning rule, including: obtain a basic limit that matches the basic category of the transaction attribute in the warning rule, and multiply the basic limit by a preset basic coefficient to obtain the corresponding transaction limit; Determine whether the transaction amount in the transaction request message is greater than the transaction limit to determine whether the transaction request message meets the warning rule; If there is historical transaction data corresponding to the merchant identification code of the transaction request message, dynamically adjust the basic coefficient according to the historical transaction data corresponding to the transaction request message; the dynamically adjusting the basic coefficient according to the historical transaction data corresponding to the transaction request message; The warning database includes a warning dictionary and a blacklist dictionary. The determining whether the transaction request message meets the preset interception condition according to the preset warning database and the quota configuration table includes: Determine whether the warning dictionary contains the merchant identification code in the transaction request message; If the warning dictionary contains the merchant identification code, obtain the daily limit corresponding to the transaction request message from the quota configuration table; According to the interception condition, determine whether the sum of the transaction amount in the transaction request message and the dangerous amount stored in the blacklist dictionary is greater than the daily limit; If the warning dictionary does not contain the merchant identification code or the sum of the transaction amount and the dangerous amount is not greater than the daily limit, determine that the transaction request message does not meet the interception condition; If the sum of the transaction amount and the dangerous amount is greater than the daily limit, determine that the transaction request message meets the interception condition.

2. The flow accumulation control method based on asynchronous alert configuration according to claim 1, wherein The updating the quota configuration table according to the transaction record information includes: Update a pre-stored transaction base table according to the transaction record information; Determine whether the transaction status in the transaction record information is successful; If the transaction status in the transaction record information is successful, calculate the quota update information based on the transaction bottom sheet and the quota configuration table, and update the quota configuration table.

3. The flow accumulation control method based on asynchronous alert configuration according to claim 1, wherein The judgment of whether the warning rule and the updated quota configuration table meet the preset database update conditions includes: Judging whether the cumulative quota and cumulative times in the quota configuration table meet the warning dictionary update conditions according to the daily limit, daily limit times and safety line configured in the quota configuration table; Judging whether the cumulative quota and cumulative times in the quota configuration table meet the blacklist dictionary update conditions according to the daily limit, the daily limit times and the warning rule; If the cumulative quota and cumulative times in the quota configuration table meet the warning dictionary update conditions or meet the blacklist dictionary update conditions, it is determined that the database update conditions are met.

4. The flow cumulative control method based on asynchronous alert configuration according to claim 3, characterized in that, The asynchronous configuration update of the warning database according to the transaction record information and the quota configuration table includes: Generating corresponding new warning record information according to the transaction record information and the quota configuration table; Adding the new warning record information to the warning dictionary of the warning database to complete the asynchronous configuration update of the warning dictionary; If the blacklist dictionary update conditions are met, generating corresponding new dangerous record information according to the new warning record information and the warning rule; Adding the new dangerous record information to the blacklist dictionary of the warning database to complete the asynchronous configuration update of the blacklist dictionary.

5. The flow accumulation control method based on asynchronous warning configuration according to claim 2, characterized in that After the asynchronous configuration update of the warning database according to the transaction record information and the quota configuration table, it further includes: If the preset rule update time point is reached, clear the warning database and the quota configuration table; Configure and update the warning rule and the quota configuration table according to the transaction bottom sheet.

6. A flow cumulative control device based on asynchronous warning configuration, characterized in that The device is configured in a cloud server, and a network connection is established between the cloud server and the client to realize the transmission of data information. The device includes: A transaction request information judgment unit, configured to judge whether the transaction request information meets the preset warning rule if transaction request information from any client is received; An interception judgment unit, configured to judge whether the transaction request information meets the preset interception conditions according to the preset warning database and quota configuration table if the transaction request information meets the warning rule; A transaction record information acquisition unit, configured to process the transaction request information to complete the transaction if the transaction request information does not meet the warning rule or does not meet the interception conditions, and record the processing process of the transaction request information to obtain transaction record information; A prompt information feedback unit, configured to intercept the transaction request information and feedback a transaction failure prompt information to the client if the transaction request information meets the interception conditions; A quota configuration table update unit, configured to update the quota configuration table according to the transaction record information; An update judgment unit, configured to judge whether the warning rule and the updated quota configuration table meet the preset database update conditions; An asynchronous configuration update unit, configured to, if the database update condition is satisfied, asynchronously update the configuration of the warning database according to the transaction record information and the quota configuration table; The judging whether the transaction request information meets the preset warning rules includes: Obtaining the transaction quota that matches the transaction attribute in the transaction request information in the warning rule, including: obtaining the basic quota that matches the basic category of the transaction attribute in the warning rule, and multiplying the basic quota by a preset basic coefficient to obtain the corresponding transaction quota; Judging whether the transaction amount in the transaction request information is greater than the transaction quota to judge whether the transaction request information meets the warning rule; If there is historical transaction data corresponding to the merchant identification code of the transaction request information, dynamically adjust the basic coefficient according to the historical transaction data corresponding to the transaction request information; the dynamically adjusting the basic coefficient according to the historical transaction data corresponding to the transaction request information; The warning database includes a warning dictionary and a blacklist dictionary. The judging whether the transaction request information meets the preset interception condition according to the preset warning database and the quota configuration table includes: Determining whether the warning dictionary contains the merchant identification code in the transaction request information; If the warning dictionary contains the merchant identification code, obtain the daily quota corresponding to the transaction request information from the quota configuration table; According to the interception condition, judging whether the sum of the transaction amount in the transaction request information and the dangerous amount stored in the blacklist dictionary is greater than the daily quota; If the warning dictionary does not contain the merchant identification code or the sum of the transaction amount and the dangerous amount is not greater than the daily quota, it is determined that the transaction request information does not meet the interception condition; If the sum of the transaction amount and the dangerous amount is greater than the daily quota, it is determined that the transaction request information meets the interception condition.

7. A computer device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the traffic cumulative control method based on asynchronous warning configuration according to any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements the traffic cumulative control method based on asynchronous warning configuration according to any one of claims 1 to 5.

Images