Business rule parameter management method and device in financial system, computer equipment, readable storage medium and program product

Abstract

The invention relates to a parameter management method and device for business rules in a financial system, computer equipment, a computer readable storage medium and a computer program product. The method comprises the steps of generating parameter operation data corresponding to an operation request when the operation request for a parameter of a business rule in a financial system is received; performing first auditing on the parameter operation data to obtain a first auditing result; if the first auditing result is that auditing is passed, modifying parameters of the basic library and all the unit libraries through a global transaction based on the parameter operation data; the global transaction is used for binding parameters for modifying the basic library and parameters for modifying the unit libraries into atomic operations, and ensuring that the parameters of the basic library are consistent with those of the unit libraries; and after the modification is completed, sending a parameter change notification to each service node. By adopting the method, the parameter consistency and reliability in the database can be improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of financial technology information technology, and in particular, to a parameter management method and device for business rules in a financial system, computer equipment, computer readable storage medium, and computer program product. BACKGROUND

[0002] The development of financial technology promotes the widespread adoption of a distributed unit architecture by bank credit card systems to cope with high concurrency, high availability, and elastic expansion requirements. Business parameters such as interest calculation, credit, and fees are the core of accurate business operation. The current mode of "centralized storage (base library), distributed use (each unit library)" needs to address the core requirement of efficient and consistent synchronization of base library parameters to each unit library.

[0003] In existing distributed parameter synchronization schemes, there are problems of low data consistency (easy to have inconsistent node parameters) and poor reliability. SUMMARY

[0004] Therefore, it is necessary to provide a parameter management method, device, computer equipment, computer readable storage medium, and computer program product for business rules in a financial system that can improve parameter consistency and reliability.

[0005] In a first aspect, the present application provides a parameter management method for business rules in a financial system, comprising:

[0006] When an operation request for a parameter of a business rule in a financial system is received, generating parameter operation data corresponding to the operation request;

[0007] conducting a first audit on the parameter operation data to obtain a first audit result;

[0008] If the first audit result is passed, modifying the parameters of the base library and all unit libraries based on the parameter operation data through a global transaction; the global transaction is used to bundle the parameters modified in the base library and the parameters modified in the unit libraries as an atomic operation to ensure the consistency of the parameters of the base library and each unit library;

[0009] After the modification is completed, sending a parameter change notification to each business node.

[0010] In one embodiment, generating parameter operation data corresponding to the operation request comprises:

[0011] determining the content before and after the parameter change, the data table name, and the operation type corresponding to the operation request; generating comparison objects before and after the parameter change through a parameter comparison method based on the content before and after the parameter change; and storing the content before and after the parameter change, the data table name, the operation type, and the comparison objects corresponding to the operation request in a parameter audit table to form the parameter operation data.

[0012] In one of the embodiments, based on the parameter operation data, the parameters of the base library and all unit libraries are modified through a global transaction, including:

[0013] Based on the parameter operation data, the parameters in the base library are modified and it is determined whether the parameters in the base library are modified successfully; if the parameters in the base library are modified successfully, the parameters in all unit libraries are modified synchronously based on the modification of the parameters in the base library, and it is determined whether the parameters in all unit libraries are modified successfully; if the parameters in any unit library are modified unsuccessfully, a global transaction rollback mechanism is triggered to undo all the modifications that have been made.

[0014] In one of the embodiments, it is determined whether the parameters in the base library are modified successfully, including:

[0015] The modified parameters in the base library are subjected to business compliance inspection, data integrity inspection, database operation result inspection and parameter version consistency inspection; if all the inspections are passed, the parameters in the base library are modified successfully; if any of the inspections is not passed, the parameters in the base library are modified unsuccessfully.

[0016] In one of the embodiments, the method further includes:

[0017] If the parameters in the base library are modified unsuccessfully, the global transaction rollback mechanism is triggered to undo the modification of the parameters in the base library, and the modification of the parameters in the unit libraries is stopped.

[0018] In one of the embodiments, the method further includes:

[0019] If the first audit result is an audit failure, the modification of the parameters in the base library is stopped.

[0020] In a second aspect, the application further provides a parameter management device for business rules in a financial system, including:

[0021] A generation module is configured to generate parameter operation data corresponding to an operation request when the operation request for the parameters of the business rules in the financial system is received;

[0022] An audit module is configured to perform a first audit on the parameter operation data to obtain a first audit result;

[0023] A modification module is configured to, if the first audit result is an audit pass, modify the parameters of the base library and all unit libraries based on the parameter operation data through a global transaction; the global transaction is configured to bundle the modification of the parameters in the base library and the modification of the parameters in the unit libraries as an atomic operation to ensure that the parameters of the base library and the unit libraries are consistent;

[0024] A notification module is configured to send a parameter change notification to each business node after the modification is completed.

[0025] In a third aspect, the present application provides a computer device, comprising a memory and a processor, the memory storing a computer program, and the processor implementing the following steps when executing the computer program:

[0026] When receiving an operation request for a parameter of a business rule in a financial system, generating parameter operation data corresponding to the operation request;

[0027] Firstly auditing the parameter operation data to obtain a first auditing result;

[0028] If the first auditing result is passed, modifying the parameters of the basic library and all unit libraries based on the parameter operation data through a global transaction; the global transaction is used to bundle the parameters modified in the basic library and the parameters modified in the unit libraries as an atomic operation, so as to ensure that the parameters of the basic library and the unit libraries are consistent;

[0029] After the modification is completed, sending a parameter change notification to each business node.

[0030] In a fourth aspect, the present application provides a computer readable storage medium, which stores a computer program, and the computer program implements the following steps when executed by a processor:

[0031] When receiving an operation request for a parameter of a business rule in a financial system, generating parameter operation data corresponding to the operation request;

[0032] Firstly auditing the parameter operation data to obtain a first auditing result;

[0033] If the first auditing result is passed, modifying the parameters of the basic library and all unit libraries based on the parameter operation data through a global transaction; the global transaction is used to bundle the parameters modified in the basic library and the parameters modified in the unit libraries as an atomic operation, so as to ensure that the parameters of the basic library and the unit libraries are consistent;

[0034] After the modification is completed, sending a parameter change notification to each business node.

[0035] In a fifth aspect, the present application provides a computer program product, comprising a computer program, and the computer program implements the following steps when executed by a processor:

[0036] When receiving an operation request for a parameter of a business rule in a financial system, generating parameter operation data corresponding to the operation request;

[0037] Firstly auditing the parameter operation data to obtain a first auditing result;

[0038] If the first audit result is passed, the parameters of the basic library and all unit libraries are modified based on the parameter operation data through a global transaction; the global transaction is used to bundle the parameters modified in the basic library and the parameters modified in the unit libraries as an atomic operation, so as to ensure that the parameters of the basic library and the unit libraries are consistent;

[0039] When the modification is completed, a parameter change notification is sent to each business node.

[0040] The parameter management method, device, computer equipment, computer readable storage medium and computer program product of the business rule in the financial system, when receiving an operation request for the parameters of the business rule in the financial system, generate parameter operation data corresponding to the operation request; the first audit is performed on the parameter operation data, and the first audit result is obtained; if the first audit result is passed, the parameters of the basic library and all unit libraries are modified based on the parameter operation data through a global transaction; the global transaction is used to bundle the parameters modified in the basic library and the parameters modified in the unit libraries as an atomic operation, so as to ensure that the parameters of the basic library and the unit libraries are consistent; when the modification is completed, a parameter change notification is sent to each business node. Through the cooperative design of the audit process, the global transaction atomic synchronization and the change real-time notification, the compliance control, cross-node strong consistency synchronization and real-time effect of the business parameters can be realized under the distributed architecture, the business calculation deviation and compliance risk caused by inconsistent parameters can be effectively avoided, and the reliability and efficiency of parameter update are improved, which meets the core requirements of high availability and high compliance of the financial system. BRIEF DESCRIPTION OF DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technical solutions, the drawings needed to be used in the description of the embodiments of the present application or the related technical solutions will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other related drawings can be obtained by those skilled in the art without creating any creative labor.

[0042] Figure 1 A flowchart of a parameter management method of a business rule in a financial system in an embodiment;

[0043] Figure 2 A detailed flowchart of a parameter management method of a business rule in a financial system in an embodiment;

[0044] Figure 3 A structure block diagram of a parameter management device of a business rule in a financial system in an embodiment;

[0045] Figure 4 An internal structure diagram of a computer equipment in an embodiment. DETAILED DESCRIPTION

[0046] In order to make the purposes, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and not used to limit the present application.

[0047] In one embodiment, as shown in Figure 1 A parameter management method for business rules in a financial system is provided. The method can be applied to a terminal, a server, or a system including a terminal and a server, and can be implemented through the interaction of the terminal and the server. The method includes the following steps:

[0048] Step 102: When an operation request for a parameter of a business rule in a financial system is received, parameter operation data corresponding to the operation request is generated.

[0049] The parameter operation data includes parameter change core information and execution association information, and specifically includes: a parameter unique identifier (such as a parameter ID and a business module identifier), an operation type (addition, deletion, or modification, corresponding to parameter addition, parameter modification, or parameter deletion), complete parameter content before and after the change (such as old and new interest rate values, and newly added entries of a risk country control list), a target storage table name corresponding to the parameter (a data table name in a basic library and a unit library), and operation context information (such as an operation initiator account, an operation timestamp, and a request IP address).

[0050] Step 104: The parameter operation data is subjected to a first audit, and a first audit result is obtained.

[0051] Optionally, the first audit can be manual or automatic based on preset rules.

[0052] Step 106: If the first audit result is passed, the parameter operation data is used to modify the parameters in the basic library and all unit libraries through a global transaction. The global transaction is used to bundle the modified parameters in the basic library and the modified parameters in the unit libraries as an atomic operation, so as to ensure the consistency of the parameters in the basic library and the unit libraries.

[0053] The global transaction is controlled by the closed loop process of "initialization-preparation-resolution-closing", which specifically includes: first, generating a globally unique transaction ID (GTID), writing the basic library parameter service associated with all unit library parameters, and synchronizing the service, and explicitly executing the rule and timeout threshold of "all success, any failure, and rollback"; then triggering the basic library parameter modification and the unit library parameter synchronization in turn, both types of operations perform "business compliance verification + data integrity verification", and only complete the pre-execution without final submission, and the execution status is fed back to the global transaction manager; after the manager aggregates all node states, if all pre-executions are successful, a commit instruction is sent to make the parameter modifications of the basic library and all unit libraries effective; if any node execution fails or times out, a rollback instruction is immediately sent to cancel the parameter modifications of the basic library and the unit library that have completed the pre-execution, ensuring that the parameters of each node in the distributed environment always remain consistent, without partial updates, partial non-updates, and intermediate states.

[0054] Step 108, after the modification is completed, parameter change notifications are sent to each business node.

[0055] The parameter change notification is centrally published through the ZooKeeper configuration center, and the notification content includes the parameter unique identifier, the latest parameter version number, the change completion timestamp, the operation type, and the core change content (such as "interest rate from 0.05% to 0.03%"). Each business node subscribes to the configuration node corresponding to the parameter in advance, and automatically triggers the local memory cache refresh operation to replace the old parameter with the latest parameter after receiving the notification through the long connection in real time.

[0056] The parameter management method of the business rule in the above financial system, when receiving an operation request for a parameter of a business rule in a financial system, generates parameter operation data corresponding to the operation request; the parameter operation data is subjected to a first audit to obtain a first audit result; if the first audit result is passed, the parameters of the basic library and all unit libraries are modified based on the parameter operation data through a global transaction; the global transaction is used to bundle the parameters modified in the basic library and the parameters modified in the unit library as atomic operations to ensure that the parameters of the basic library and the unit library are consistent; after the modification is completed, parameter change notifications are sent to each business node. Through the collaborative design of the audit process, global transaction atomic synchronization, and real-time change notification, the compliance control, cross-node strong consistency synchronization, and real-time effectiveness of business parameters can be realized under a distributed architecture, effectively avoiding business calculation deviation and compliance risks caused by inconsistent parameters, while improving the reliability and efficiency of parameter updates, meeting the core needs of high availability and high compliance of the financial system.

[0057] In an exemplary embodiment, generating parameter operation data corresponding to the operation request includes:

[0058] The operation request corresponding parameter change before and after the content, data table name and operation type are determined; based on the parameter change before and after the content, the parameter change before and after the comparison object is generated by the parameter comparison method; the parameter change before and after the operation request corresponding content, data table name, operation type and comparison object are stored in the parameter audit table to form the parameter operation data.

[0059] Wherein, when receiving the parameter addition, modification or deletion change request, the system does not directly operate the basic database, but processes according to the following process: through the @InsertParameter, @UpdateParameter, @DeleteParameter and other aspect annotations on the parameter change request triggered method, the parameter change before and after the change request corresponding content, parameter target storage data table name and operation type are automatically captured. Based on the captured parameter change before and after the content, the structured parameter change comparison object is generated by the parameter comparison method, and the specific change information of this parameter is clearly recorded. The parameter change details (including operation context, data table name, operation type) and change comparison results are stored in the parameter audit table, at this time the parameter change request enters the state of waiting for subsequent audit process trigger.

[0060] For example, if the operation request is "adjust the interest rate of credit card interest calculation day from 0.05% to 0.03%", the parameter change before content is "interest rate of interest calculation day 0.05%, effective time 2024-01-01", the change after content is "interest rate of interest calculation day 0.03%, effective time 2025-01-01", the data table name is "t_interest_param", and the operation type is "UPDATE (modify)"; then through the parameter comparison method, the change field (interest rate value, effective time) and the difference between the old and new values are extracted, and the comparison object is generated: { "interest rate value": { "old value": "0.05%", "new value": "0.03%"}, "effective time": { "old value": "2024-01-01", "new value": "2025-01-01"}}; finally, the above change content, data table name, operation type and comparison object are stored in a record in the parameter audit table together with the operation initiator "operation and maintenance account admin", operation time "2025-01-01 10:00:00" and other information, which constitutes the parameter operation data of this operation, for subsequent audit and synchronization process calling.

[0061] In this embodiment, the core information of the operation request is automatically captured by aspect programming, without manual entry of parameter change details, which not only improves the efficiency and accuracy of data collection, but also avoids the omission or error caused by manual entry.

[0062] In an exemplary embodiment, based on the parameter operation data, the parameters of the basic library and all unit libraries are modified through global transaction, including:

[0063] Based on the parameter operation data, the parameters in the base library are modified and it is determined whether the parameters in the base library are modified successfully; if the parameters in the base library are modified successfully, the parameters in all unit libraries are modified synchronously based on the modification of the parameters in the base library, and it is determined whether the parameters in all unit libraries are modified successfully; if the parameters in any unit library are modified unsuccessfully, a global transaction rollback mechanism is triggered to undo all the modifications that have been made.

[0064] For example, if the parameter operation data is “adjust the interest rate of the credit card interest calculation day from 0.05% to 0.03%”, first, the base library parameter modification interface is called according to the data, the interest rate value of the corresponding parameter in the “t_interest_param” table in the base library is updated to 0.03%, and the consistency of the fields, the SQL execution result and the version number increment state are checked to determine whether the base library modification is successful; then, based on the modification result of the base library, a synchronization instruction is sent to all unit libraries to update the corresponding parameters in the “t_interest_param” table in each unit library; if the modification of a unit library fails due to database connection timeout, the global transaction rollback mechanism is triggered immediately: first, the interest rate modification operation completed in the base library is undone, and the original value of 0.05% is restored, and then the rollback is performed on the other unit libraries that have been successfully modified, finally, it is ensured that the parameters of all nodes return to the state before the change.

[0065] In this embodiment, through the step-by-step modification logic of modifying the base library first and then synchronously modifying the unit library, it is ensured that the parameter synchronization is based on the authoritative data source (base library), and the data conflict caused by parallel modification of multiple nodes is avoided; at the same time, through the design of the global transaction rollback mechanism, the pain point of successful modification of some nodes and failure of some nodes in the distributed scenario is completely solved, and the strict requirement of zero error of data in the financial scenario is met.

[0066] In an example embodiment, it is determined whether the parameters in the base library are modified successfully, comprising:

[0067] The modified parameters in the base library are subjected to business compliance test, data integrity test, database operation result test and parameter version consistency test; if all the tests are passed, the modification of the parameters in the base library is successful; if any test is not passed, the modification of the parameters in the base library is unsuccessful.

[0068] For example, the parameter modification of "adjusting the interest rate of credit cards from 0.05% to 0.03%" is modified as follows: check whether the modified interest rate 0.03% is within the legal range of 0.03%-0.05% specified by the central bank, and confirm that there is no violation; compare the actual storage value of the target parameter (interest rate 0.03%, effective time 2025-01-01) in the "t_interest_param" table in the base library with the changed content of the parameter operation data to ensure that there is no missing field or value deviation; query the SQL execution log to confirm that the UPDATE operation status is "successful" and the number of affected rows is 1, with no primary key conflict, connection interruption, or other errors; check whether the parameter version number is incremented from V1.0 to V2.0, consistent with the target version of the parameter operation data. If the above four checks are passed, it is determined that the base library parameter modification is successful; if any check fails, the modification is determined to be unsuccessful.

[0069] In this embodiment, through the four-dimensional inspection system of business compliance, data integrity, operation effectiveness, and version controllability, the core verification scenarios after parameter modification are comprehensively covered, avoiding the flow of illegal parameters into the system and eliminating problems such as incomplete data writing and operation failure.

[0070] In one example embodiment, the method further comprises:

[0071] If the parameter modification in the base library fails, a global transaction rollback mechanism is triggered to undo the parameter modification in the base library, and the subsequent modification of parameters in the unit library is stopped.

[0072] For example, if the parameter operation data is "adjusting the interest rate of credit cards from 0.05% to 0.02%", after determining that the base library parameter modification fails, the global transaction rollback mechanism is triggered immediately to undo the interest rate modification operation that has been executed in the base library, restoring the interest rate to the original value of 0.05%, and stopping the issuance of synchronization modification instructions to each unit library to prevent the spread of incorrect parameters to distributed nodes.

[0073] In this embodiment, by triggering rollback and terminating subsequent processes directly at the base library modification failure link, the synchronization of incorrect parameters to unit libraries is blocked from the source; not only does this avoid the occupation of system resources by invalid unit library synchronization operations, but also prevents business risks caused by data inconsistency between the base library and unit libraries, further enhancing the fault tolerance and security of distributed parameter management.

[0074] In one example embodiment, the method further comprises:

[0075] If the first audit result is not passed, the subsequent modification of parameters in the base library is stopped.

[0076] For example, if the parameter operation data is "add credit card installment early termination fee rate 3%", the audit link finds that the rate exceeds the bank's upper limit of 1%-2% and no compliance approval is provided, and the first audit result is determined to be not passed. At this time, the system directly stops the subsequent parameter modification operation of the basic library and does not trigger any database writing process, and returns the prompt information "audit not passed: fee rate exceeds compliance interval" to the operation initiator.

[0077] In this embodiment, the audit is used as a pre-interception link for parameter modification, and the audit is not passed to terminate the subsequent process, thereby blocking irregular and unreasonable parameter changes from the source. This not only avoids the occupation of system resources by invalid modifications, but also prevents irregular parameters from entering the database and affecting business operation.

[0078] In one embodiment, as Figure 2As shown, a parameter management method of business rules in a financial system is provided, including: when an operation request for a parameter of a business rule in the financial system is received, if the operation request is "adjust the interest rate of the credit card billing date from 0.05% to 0.03%", first determine that the content before the parameter change is "interest rate of the billing date 0.05%, effective time 2024-01-01", the changed content is "interest rate of the billing date 0.03%, effective time 2025-01-01", the data table name is "t_interest_param", and the operation type is "UPDATE (modify)"; then through the parameter comparison method, the changed fields (interest rate value, effective time) and the difference between the old and new values are extracted, and the comparison object is generated: { "interest rate value": { "old value": "0.05%", "new value": "0.03%"}, "effective time": { "old value": "2024-01-01", "new value": "2025-01-01"}}; finally, the above change content, data table name, operation type and comparison object are stored in a record in the parameter audit table together with the operation initiator "operation and maintenance account admin", operation time "2025-01-01 10:00:00" and other information, which constitutes the parameter operation data of this operation. The parameter operation data is manually audited to obtain an audit result. If the manual audit result is passed, first, the interest rate value of the corresponding parameter in the "t_interest_param" table in the basic library is updated to 0.03% according to the data, and it is checked whether the modified interest rate 0.03% is within the legal range of 0.03%-0.05% specified by the central bank, and it is confirmed that there is no violation. Compare the actual storage value (interest rate 0.03%, effective time 2025-01-01) of the target parameter in the "t_interest_param" table in the basic library with the changed content of the parameter operation data to ensure that there is no missing field and value deviation. Query the SQL execution log to confirm that the UPDATE operation status is "success" and the number of affected rows is 1, with no primary key conflict, connection interruption or other errors. Check whether the parameter version number is incremented from V1.0 to V2.0, which is consistent with the target version of the parameter operation data. If the above four tests are passed, it is determined that the modification of the basic library parameter is successful, and then the modification result of the basic library is taken as the benchmark to initiate a synchronization instruction to all unit libraries to update the corresponding parameters in the "t_interest_param" table in each unit library. If the modification of a certain unit library fails due to database connection timeout, the global transaction rollback mechanism is triggered immediately: first, the interest rate modification operation completed in the basic library is cancelled, and the original value of 0.05% is restored, and then the rollback is performed on the other unit libraries that have been successfully modified, finally ensuring that the parameters of all nodes return to the state before the change. If any test fails, it is determined that the modification fails, the global transaction rollback mechanism is triggered, the parameter modification in the basic library is cancelled, and the modification of the parameters in the unit libraries is stopped.When the modification is completed, a parameter change notification is sent to each business node. The parameter change notification is centrally published through the ZooKeeper configuration center, and the notification content includes a parameter unique identifier, a latest parameter version number, a change completion timestamp, an operation type, and core change content (such as "interest rate is adjusted from 0.05% to 0.03%"). Each business node pre-subscribes the configuration node corresponding to the parameter, and after receiving the notification through a long connection in real time, automatically triggers a local memory cache refresh operation to replace the old parameter with the latest parameter after synchronization. If the manual audit result is not passed, the subsequent modification of the parameters of the underlying library is stopped.

[0079] It should be understood that, although each step in the flowchart involved in the above embodiments is displayed in sequence according to the arrow, these steps are not necessarily executed in the order indicated by the arrow. Unless otherwise specified herein, the execution of these steps is not strictly limited in sequence, and these steps can be executed in other orders. Moreover, at least part of the steps in the flowchart involved in the above embodiments can include multiple steps or stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily sequential, but can be alternately executed with at least part of other steps or steps or stages in other steps. It can be understood that the steps in different embodiments can be freely combined as needed, and various non-contradictory schemes formed by the combination are within the scope of protection of the present application.

[0080] In an exemplary embodiment, as shown in FIG. 3, Figure 3 a parameter management device for business rules in a financial system is provided, comprising a generation module 301, an audit module 302, a modification module 303, and a notification module 304, wherein:

[0081] The generation module is configured to generate parameter operation data corresponding to an operation request when receiving the operation request for the parameter of the business rule in the financial system;

[0082] The audit module is configured to perform a first audit on the parameter operation data to obtain a first audit result;

[0083] The modification module is configured to, if the first audit result is passed, modify the parameters of the underlying library and all unit libraries based on the parameter operation data through a global transaction. The global transaction is used to bundle the parameters modified in the underlying library and the parameters modified in the unit library as an atomic operation to ensure that the parameters of the underlying library and each unit library are consistent.

[0084] The notification module is configured to send a parameter change notification to each business node when the modification is completed.

[0085] In an example embodiment, the generating module is further configured to:

[0086] determine the content before and after the parameter change, the data table name and the operation type corresponding to the operation request, generate the comparison objects before and after the parameter change by the parameter comparison method based on the content before and after the parameter change, and store the content before and after the parameter change, the data table name, the operation type and the comparison objects corresponding to the operation request into the parameter audit table to form the parameter operation data.

[0087] In an example embodiment, the modifying module is further configured to:

[0088] modify the parameters in the basic library based on the parameter operation data and determine whether the parameters in the basic library are successfully modified, synchronize the modification of the parameters in all unit libraries based on the modification of the parameters in the basic library if the parameters in the basic library are successfully modified, and determine whether the parameters in all unit libraries are successfully modified, and trigger the global transaction rollback mechanism to undo all the modifications if the parameters in any unit library are unsuccessfully modified.

[0089] In an example embodiment, the modifying module is further configured to:

[0090] perform business compliance verification, data integrity verification, database operation result verification and parameter version consistency verification on the modified parameters in the basic library, and determine that the parameters in the basic library are successfully modified if all the verifications are passed, and determine that the parameters in the basic library are unsuccessfully modified if any of the verifications is failed.

[0091] In an example embodiment, the modifying module is further configured to:

[0092] trigger the global transaction rollback mechanism to undo the modification of the parameters in the basic library and stop the modification of the parameters in the unit libraries if the parameters in the basic library are unsuccessfully modified.

[0093] In an example embodiment, the modifying module is further configured to:

[0094] stop the modification of the parameters in the basic library if the first audit result is failed.

[0095] The above modules in the parameter management device of the business rules in the financial system can be realized by software, hardware and combinations thereof. The above modules can be embedded in or independent of the processor in the computer device in hardware form, or can be stored in the memory in the computer device in software form, so as to be called and executed by the processor.

[0096] In an example embodiment, a computer device is provided, which can be a server, and the internal structure diagram thereof can be as shown in Figure 4As shown in the figure. The computer device includes a processor, a memory, an input / output interface (I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through the system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capability. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store parameter operation data. The input / output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals through network connection. The computer program is executed by the processor to implement a parameter management method of business rules in a financial system.

[0097] Those skilled in the art can understand that Figure 4 The structure shown in the figure is only a block diagram of part of the structure related to the scheme of the present application, and does not constitute a limitation on the computer device to which the scheme of the present application is applied. The specific computer device can include more or fewer components than those shown in the figure, or combine certain components, or have a different component arrangement.

[0098] In one exemplary embodiment, a computer device is provided, including a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the following steps:

[0099] When receiving an operation request for the parameters of the business rules in the financial system, generating parameter operation data corresponding to the operation request;

[0100] Firstly, the parameter operation data is audited to obtain a first audit result;

[0101] If the first audit result is passed, the parameters of the global transaction and all unit libraries are modified based on the parameter operation data; the global transaction is used to bundle the parameters in the modified base library and the parameters in the modified unit library as an atomic operation, so as to ensure that the parameters of the base library and each unit library are consistent;

[0102] After the modification is completed, parameter change notifications are sent to each business node.

[0103] In one embodiment, the processor executing the computer program further implements the following steps:

[0104] Determine the content before and after the parameter change corresponding to the operation request, the data table name and the operation type; generate the comparison object before and after the parameter change through the parameter comparison method based on the content before and after the parameter change; store the content before and after the parameter change corresponding to the operation request, the data table name, the operation type and the comparison object into the parameter audit table to form the parameter operation data.

[0105] In one embodiment, the processor, when executing the computer program, also implements the following steps:

[0106] Based on the parameter operation data, modify the parameters in the basic library and determine whether the parameters in the basic library are modified successfully; if the parameters in the basic library are modified successfully, modify the parameters in all unit libraries based on the parameter modification in the basic library, and determine whether the parameters in all unit libraries are modified successfully; if the parameters in any unit library are modified unsuccessfully, trigger the global transaction rollback mechanism to undo all modifications that have occurred.

[0107] In one embodiment, the processor, when executing the computer program, also implements the following steps:

[0108] Perform business compliance verification, data integrity verification, database operation result verification and parameter version consistency verification on the modified parameters in the basic library; if all verifications pass, the parameters in the basic library are modified successfully; if any verification fails, the parameters in the basic library are modified unsuccessfully.

[0109] In one embodiment, the processor, when executing the computer program, also implements the following steps:

[0110] If the parameters in the basic library are modified unsuccessfully, trigger the global transaction rollback mechanism to undo the modification of the parameters in the basic library, and stop the subsequent modification of the parameters in the unit library.

[0111] In one embodiment, the processor, when executing the computer program, also implements the following steps:

[0112] If the first audit result is not passed, stop the subsequent modification of the parameters in the basic library.

[0113] In one embodiment, a computer readable storage medium is provided, which stores a computer program, and the computer program, when executed by a processor, implements the following steps:

[0114] When receiving an operation request for the parameters of the business rules in the financial system, generate parameter operation data corresponding to the operation request;

[0115] Perform a first audit on the parameter operation data to obtain a first audit result;

[0116] If the first audit result is passed, the parameters of the basic library and all unit libraries are modified based on the parameter operation data through a global transaction; the global transaction is used to bundle the parameters modified in the basic library and the parameters modified in the unit libraries as an atomic operation, so as to ensure that the parameters of the basic library and the unit libraries are consistent;

[0117] When the modification is completed, a parameter change notification is sent to each business node.

[0118] In one embodiment, the computer program, when executed by the processor, further implements the following steps:

[0119] The contents before and after the parameter change corresponding to the operation request, the data table name and the operation type are determined; the comparison objects before and after the parameter change are generated by the parameter comparison method based on the contents before and after the parameter change; the contents before and after the parameter change corresponding to the operation request, the data table name, the operation type and the comparison objects are stored in the parameter audit table to form the parameter operation data.

[0120] In one embodiment, the computer program, when executed by the processor, further implements the following steps:

[0121] Based on the parameter operation data, the parameters in the basic library are modified and it is judged whether the parameters in the basic library are modified successfully; if the parameters in the basic library are modified successfully, the parameters in all unit libraries are modified synchronously based on the modification of the parameters in the basic library, and it is judged whether the parameters in all unit libraries are modified successfully; if the parameters in any unit library are modified unsuccessfully, a global transaction rollback mechanism is triggered to undo all the modifications.

[0122] In one embodiment, the computer program, when executed by the processor, further implements the following steps:

[0123] The parameters in the modified basic library are subjected to business compliance inspection, data integrity inspection, database operation result inspection and parameter version consistency inspection; if all the inspections are passed, the modification of the parameters in the basic library is successful; if any inspection is not passed, the modification of the parameters in the basic library is failed.

[0124] In one embodiment, the computer program, when executed by the processor, further implements the following steps:

[0125] If the modification of the parameters in the basic library is failed, a global transaction rollback mechanism is triggered to undo the modification of the parameters in the basic library, and the modification of the parameters in the unit libraries is stopped.

[0126] In one embodiment, the computer program, when executed by the processor, further implements the following steps:

[0127] If the first audit result is failed, the modification of the parameters of the basic library is stopped.

[0128] In one embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the following steps:

[0129] When receiving an operation request for a parameter of a business rule in a financial system, generating parameter operation data corresponding to the operation request;

[0130] Firstly auditing the parameter operation data to obtain a first audit result;

[0131] If the first audit result is passed, modifying the parameters in the basic library and all unit libraries based on the parameter operation data through a global transaction; the global transaction is used to bundle the parameters in the basic library and the parameters in the unit libraries as an atomic operation to ensure that the parameters in the basic library and the unit libraries are consistent;

[0132] After the modification is completed, sending a parameter change notification to each business node.

[0133] In one embodiment, the computer program, when executed by the processor, further implements the following steps:

[0134] Determining the content before and after the parameter change, the data table name and the operation type corresponding to the operation request; generating comparison objects before and after the parameter change through a parameter comparison method based on the content before and after the parameter change; storing the content before and after the parameter change, the data table name, the operation type and the comparison objects corresponding to the operation request into a parameter audit table to form the parameter operation data.

[0135] In one embodiment, the computer program, when executed by the processor, further implements the following steps:

[0136] Based on the parameter operation data, modifying the parameters in the basic library and judging whether the parameters in the basic library are modified successfully; if the parameters in the basic library are modified successfully, modifying the parameters in all unit libraries based on the modification of the parameters in the basic library and judging whether the parameters in all unit libraries are modified successfully; if the parameters in any unit library are modified unsuccessfully, triggering a global transaction rollback mechanism to undo all modifications.

[0137] In one embodiment, the computer program, when executed by the processor, further implements the following steps:

[0138] Performing business compliance inspection, data integrity inspection, database operation result inspection and parameter version consistency inspection on the modified parameters in the basic library; if all inspections are passed, the parameters in the basic library are modified successfully; if any inspection is not passed, the parameters in the basic library are modified unsuccessfully.

[0139] In one embodiment, the computer program, when executed by the processor, further implements the following steps:

[0140] If the parameter modification in the base library fails, a global transaction rollback mechanism is triggered to undo the parameter modification in the base library and stop subsequent modification of the parameters in the unit library.

[0141] In one embodiment, the computer program, when executed by the processor, further implements the following steps:

[0142] If the first audit result is an audit failure, the operation of modifying the parameters in the base library is stopped.

[0143] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer readable storage medium. When the computer program is executed, it can include the processes of the above-mentioned embodiments. In the embodiments provided in the present application, any reference to a memory, a database or other medium can include at least one of a non-volatile memory and a volatile memory. The non-volatile memory can include a read-only memory (ROM), a magnetic tape, a floppy disk, a flash memory, an optical storage, a high-density embedded non-volatile memory, a resistive random access memory (ReRAM), a magnetoresistive random access memory (MRAM), a ferroelectric random access memory (FRAM), a phase change memory (PCM), a graphene memory, etc. The volatile memory can include a random access memory (RAM) or an external cache memory, etc. As an illustration but not limitation, the RAM can be in various forms, such as a static random access memory (SRAM) or a dynamic random access memory (DRAM), etc. The database involved in the embodiments provided in the present application can include at least one of a relational database and a non-relational database. The non-relational database can include a distributed database based on a block chain, etc., without being limited thereto. The processor involved in the embodiments provided in the present application can be a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., without being limited thereto.

[0144] Any technical features in the above embodiments can be combined, and for the sake of brevity, not all possible combinations are described above, however, any combination of these technical features is deemed to be within the scope of the present application.

[0145] The above embodiments only express several implementation manners of the present application, and the description is relatively specific and detailed, but it should not be understood as a limitation on the patent scope of the present application. It should be pointed out that, for ordinary skilled persons in the art, several modifications and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the appended claims.

Claims

1. A method of parameter management of business rules in a financial system, characterized by, The method comprises: When an operation request for a parameter of a business rule in a financial system is received, generating parameter operation data corresponding to the operation request; Firstly auditing the parameter operation data to obtain a first auditing result; If the first auditing result is passed, modifying the parameters of the basic library and all unit libraries based on the parameter operation data through a global transaction; the global transaction is used to bundle the parameters modified in the basic library and the parameters modified in the unit libraries as an atomic operation, so as to ensure that the parameters of the basic library and the unit libraries are consistent; After the modification is completed, sending a parameter change notification to each business node.

2. The method of claim 1, wherein, The generation of the parameter operation data corresponding to the operation request comprises: Determining the content before and after the parameter change, the data table name and the operation type corresponding to the operation request; Generating comparison objects before and after the parameter change through a parameter comparison method based on the content before and after the parameter change; Storing the content before and after the parameter change, the data table name, the operation type and the comparison objects corresponding to the operation request in a parameter auditing table to form the parameter operation data.

3. The method of claim 1, wherein, The modification of the parameters of the basic library and all unit libraries based on the parameter operation data through a global transaction comprises: Modifying the parameters in the basic library based on the parameter operation data and judging whether the parameters in the basic library are successfully modified; If the parameters in the basic library are successfully modified, synchronously modifying the parameters in all unit libraries based on the modification of the parameters in the basic library, and judging whether the parameters in all unit libraries are successfully modified; If the parameters in any unit library are unsuccessfully modified, triggering a global transaction rollback mechanism to cancel all the modifications.

4. The method of claim 3, wherein, The judgment of whether the parameters in the basic library are successfully modified comprises: Performing business compliance inspection, data integrity inspection, database operation result inspection and parameter version consistency inspection on the modified parameters in the basic library; If all the inspections are passed, the parameters in the basic library are successfully modified; If any inspection is not passed, the parameters in the basic library are unsuccessfully modified.

5. The method of claim 3, wherein, The method further comprises: If the parameters in the basic library are unsuccessfully modified, triggering a global transaction rollback mechanism to cancel the modification of the parameters in the basic library and stopping the subsequent modification of the parameters in the unit libraries.

6. The method of claim 1, wherein, The method further comprises: If the first auditing result is not passed, stopping the subsequent modification of the parameters in the basic library.

7. An apparatus for managing parameters of business rules in a financial system, characterized by The apparatus comprises: A generation module configured to generate parameter operation data corresponding to an operation request for a parameter of a business rule in a financial system when the operation request is received; An auditing module configured to firstly audit the parameter operation data to obtain a first auditing result; A modification module configured to modify the parameters of the basic library and all unit libraries based on the parameter operation data through a global transaction if the first auditing result is passed; the global transaction is used to bundle the parameters modified in the basic library and the parameters modified in the unit libraries as an atomic operation, so as to ensure that the parameters of the basic library and the unit libraries are consistent; A notification module configured to send a parameter change notification to each business node after the modification is completed. 8.A computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the computer device is configured to perform the method according to any one of claims 1-7. The processor implements the steps of the method of any one of claims 1 to 6 when executing the computer program.

9. A computer readable storage medium having stored thereon a computer program, characterized in that, The computer program, which when executed by a processor, implements the steps of the method of any one of claims 1 to 6.

10. A computer program product comprising a computer program, characterized in that, The computer program, which when executed by a processor, implements the steps of the method of any one of claims 1 to 6.

Images