Transaction processing control method and system

[0048] In order to make the technical problems, technical solutions and beneficial effects to be solved by the present invention clearer and clearer, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention, but not to limit the present invention.

[0049] The invention provides a transaction processing control method.

[0050] Reference figure 1 , figure 1 It is a schematic flowchart of the first embodiment of the transaction processing control method of the present invention.

[0051] In the first embodiment, the transaction processing control method includes:

[0052] Step S10: After receiving a transaction request, the transaction processing control system determines the transaction type corresponding to the transaction request;

[0053] In this embodiment, the transaction processing control system receives the transaction request sent by the user, for example, the user inputs relevant information (for example, the identity information of the sender and receiver of the transaction, transaction information, etc.) on the mobile phone, tablet computer, self-service terminal equipment, etc. Type information, etc.) after the transaction request, such as receiving the transaction request sent by the user after inputting relevant information on the transaction client pre-installed in the mobile phone, tablet computer, self-service terminal equipment, etc., or receiving the user’s mobile phone, tablet computer , Self-service terminal equipment and other terminal browser system after inputting relevant information to send transaction request.

[0054] After the transaction processing control system receives the transaction request sent by the user, it determines the transaction type corresponding to the transaction request. For example, it can be classified according to the business category of the transaction request, and the same or similar businesses can be classified into one category, for example, financial Type transactions (such as transfer transactions, online payment transactions, etc.), query transactions (such as account balance query transactions, transaction details query transactions), etc.

[0055] Step S20: Analyze the database type corresponding to the determined transaction type according to the predetermined mapping relationship between the transaction type and the database type, the database type including a main database and a read-only database associated with data in the main database;

[0056] After the transaction type corresponding to the transaction request is determined, the database types corresponding to different transaction types can be analyzed according to the predetermined mapping relationship between the transaction type and the database type. The database type includes the main database and the database type corresponding to the main database. The read-only database associated with the data. The situation where the data in the main database is associated with the read-only database includes but is not limited to: the main database is completely synchronized with the read-only database, or the data synchronization delay time between the main database and the read-only database is relatively small, And so on in other circumstances, it is not limited here.

[0057] In one embodiment, the database type mapping can be performed for different operation modes of the database according to different transaction types. For example, financial transactions require operations such as reading and writing data in the database, and then financial transactions are predetermined The type and the main database are in a mapping relationship; the query transaction only needs to read data in the database, and the query transaction type and the read-only database are determined in advance as a mapping relationship.

[0058] In another embodiment, after calculating the transaction data of the core transaction system, the number of transactions with higher importance of the core transaction system (financial transactions such as transfer transactions, online payment transactions, etc.) accounted for the total number of transactions Usually low (for example, about 40%), transactions with low importance (query transactions such as account balance query transactions, transaction details query transactions, etc.) account for a relatively high proportion of the total number of transactions (for example, about 60%). If the transactions of higher importance and transactions of lower importance in the core transaction system share the same database resources, it will usually cause transactions with lower importance to preempt the resources of transactions with higher importance, which will often cause The system processing channel of relatively high importance transactions is blocked, and the timely processing of relatively high importance transactions cannot be guaranteed. Therefore, in this embodiment, different transaction types can be mapped to their database types according to their importance. For example, transactions with higher importance, such as financial transaction types, can be mapped to the main database in advance. Low transactions such as query transactions and read-only databases are mapped to ensure that relatively low-importance transactions will not preempt the database resources of relatively high-importance transactions, thereby ensuring the timely processing of relatively high-importance transactions . Specifically, the importance of different transaction types can be rated, and the transaction types with the importance level exceeding the preset level are regarded as higher importance transaction types, such as financial transactions; the importance level is less than or equal to the preset level as the more important transaction type. Low transaction types, such as query transactions, etc. Then, according to the importance of different transaction types, you can pre-determine the mapping relationship between the higher transaction types and the main database, and the lower transaction types and read-only The database is a mapping relationship.

[0059] Of course, users can also pre-define the mapping relationship between different transaction types and database types according to actual application needs. For example, the current transaction types that need urgent or urgent processing can be pre-determined as the mapping relationship with the main database to ensure The timely processing of this transaction type is not limited here.

[0060] In step S30, if the analyzed database type is the main database, respond to the transaction request based on the main database, or if the analyzed database type is a read-only database, respond to the transaction request based on the read-only database.

[0061] If the database type corresponding to the transaction type of the transaction request is analyzed according to the predetermined mapping relationship between the transaction type and the database type as the master database, the transaction request is responded to based on the master database. If the master database responds to the transaction request The data in the main database is read and written.

[0062] If the database type corresponding to the transaction type of the transaction request is a read-only database based on the analysis of the mapping relationship between the predetermined transaction type and the database type, the transaction request is responded to based on the read-only database, and the read-only database responds to the transaction request. The transaction requests an operation to read data in the read-only database.

[0063] In this embodiment, after receiving the transaction request, the transaction type corresponding to the transaction request is determined, and the database type corresponding to the transaction type is determined. If the database type is the main database, the transaction request is responded to based on the main database. If the type is a read-only database, the transaction request is responded to based on the read-only database. Since it can respond to transaction requests based on different databases according to different transaction types, that is, database split processing is performed for transaction requests of different transaction types, so as to avoid mutual grabbing resources when processing transaction requests of different transaction types. It can be different according to user-defined settings. Transaction types are allocated to corresponding database responses, so as to ensure that different transaction types are not affected by other transaction types and can be processed in a timely manner to improve transaction processing efficiency.

[0064] Such as figure 2 As shown, the second embodiment of the present invention proposes a transaction processing control method, which, on the basis of the foregoing embodiment, further includes:

[0065] Step S40: Synchronize the data in the main database to the read-only database in real time or regularly; or, if there is data to be written in the main database, synchronize the written data to the read-only database.

[0066] In this embodiment, the data in the main database is synchronized to the read-only database in real time or at regular intervals, and when data is written in the main database, the written data is synchronized to the read-only database in real time to achieve The data synchronization between the main database and the read-only database ensures that when responding to transaction requests of different transaction types, the data read in the main database and the read-only database are consistent, thereby ensuring the transaction Correctness.

[0067] In addition, this step S40 can be performed before step S10, can also be performed between step S10, step S20, and step S30, or can be performed after step S30, which is not limited here. figure 2 Here, only the step S40 is performed before step S10 as an example for illustration.

[0068] Further, in other embodiments, the predetermined transaction types include financial transactions and query transactions, the financial transactions correspond to the main database, the query transactions correspond to the read-only database, and the Step S30 includes:

[0069] If the analyzed database type is the main database, in response to the transaction request, read transaction data from the main database and/or write transaction data to the main database;

[0070] If the analyzed database type is the read-only database, in response to the transaction request, read transaction data corresponding to the transaction request from the read-only database and feed back the read transaction data to the sender of the transaction request .

[0071] In this embodiment, if the predetermined transaction types include financial transactions such as transfer transactions, online payment transactions, etc., and query transactions such as account balance query transactions, transaction details query transactions, etc., and the corresponding financial transaction is determined in advance. In the main database, the query transaction corresponds to the read-only database. Then, if it is analyzed that the database type corresponding to the transaction type of the transaction request is the main database, then based on the main database, respond to the transaction request, read transaction data from the main database and/or write transaction data to the main database . If it is analyzed that the database type corresponding to the transaction type of the transaction request is a read-only database, then the transaction request is responded to based on the read-only database, the transaction data corresponding to the transaction request is read from the read-only database and read The transaction data is fed back to the sender of the transaction request, such as self-service inquiry terminal, mobile terminal, etc.

[0072] This embodiment can respond to different databases according to different transaction types, realize database shunt processing for transaction requests of different transaction types, avoid grabbing resources when processing transaction requests of different transaction types, and improve transaction processing efficiency.

[0073] Further, in other embodiments, the predetermined transaction types include financial transactions and query transactions, the financial transactions correspond to the main database, the query transactions correspond to the read-only database, and the Step S30 also includes:

[0074] If the analyzed database type is a read-only database, perform data synchronization delay check on the read-only database;

[0075] If the data synchronization delay verification of the read-only database is successful, in response to the transaction request, the transaction data corresponding to the transaction request is read from the read-only database and the read transaction data is fed back to the sending of the transaction request square;

[0076] If the data synchronization delay verification of the read-only database fails, in response to the transaction request, the transaction data corresponding to the transaction request is read from the main database and the read transaction data is fed back to the sender of the transaction request .

[0077] In this embodiment, if it is analyzed that the database type corresponding to the transaction type of the transaction request is a read-only database, then before responding to the transaction request, the read-only database needs to be checked for data synchronization delay, that is, the check office Whether the data synchronization delay of the read-only database relative to the main database meets the transaction requirements.

[0078] In one embodiment, the method for checking the data synchronization delay of the read-only database may include: determining the data synchronization delay of the read-only database relative to the main database according to a predetermined synchronization delay time determination method Time, for example, the data synchronization delay time relative to the main database can be obtained from the preset type parameter of the read-only database through a predetermined command, for example, if the read-only database and the main database are both Oracle databases , Oracle database provides a view v$dataguard_stats, which contains real-time data synchronization delay time, you can pass a predetermined SQL command on the read-only database (for example, select value from v$dataguard_stats where name='apply lag') Then, the data synchronization delay time of the read-only database relative to the main database can be obtained. After the data synchronization delay time of the read-only database relative to the main database is determined, the determined data synchronization delay time can be compared with a preset delay time (for example, 2 seconds), if the determined data synchronization delay time Is greater than the preset delay time (for example, 2 seconds), it is determined that the data synchronization delay verification of the read-only database has failed; if the determined data synchronization delay time is less than or equal to the preset delay time (for example, 2 seconds), then It is determined that the data synchronization delay verification of the read-only database is successful.

[0079] If it is determined that the data synchronization delay verification of the read-only database is successful, the read-only database responds to the transaction request based on the read-only database, reads the transaction data corresponding to the transaction request from the read-only database and reads the transaction data Feedback to the sender of the transaction request, such as self-service inquiry terminals, mobile terminals, etc.

[0080] If it is determined that the data synchronization delay verification of the read-only database fails, based on the master database responds to the transaction request, the transaction data corresponding to the transaction request is read from the master database and the read transaction data is fed back to The sender of the transaction request is a self-service inquiry terminal, a mobile terminal, etc.

[0081] In this embodiment, if it is analyzed that the database type corresponding to the transaction type of the transaction request is a read-only database, before using the read-only database to respond to the transaction request, the read-only database is also checked for data synchronization delay . If the data synchronization delay check of the read-only database is successful, that is, the data synchronization delay time of the read-only database relative to the main database is relatively small, it means that the data synchronization frequency of the read-only database and the main database is high. The read-only database can be consistent with the data of the main database, and can meet the requirements of processing business, then the read-only database is directly used to respond to the transaction request such as query transaction (account balance query transaction, transaction detail information query transaction )Wait. If the data synchronization delay check of the read-only database fails, that is, the data synchronization delay time of the read-only database relative to the main database is relatively large, it means that the data synchronization frequency of the read-only database and the main database is low. The read-only database can not be consistent with the data of the main database, and cannot meet the requirements of processing business, then the main reading database is used to respond to the transaction request such as query transaction (account balance query transaction, transaction detail information query transaction ), etc. to ensure the accuracy of the transaction request response.

[0082] The present invention further provides a transaction processing control system.

[0083] Reference image 3 , image 3 It is a schematic diagram of the functional modules of the first embodiment of the transaction processing control system of the present invention.

[0084] In the first embodiment, the transaction processing control system includes:

[0085] The determination module 01 is used to determine the transaction type corresponding to the transaction request after receiving a transaction request;

[0086] In this embodiment, the transaction processing control system receives the transaction request sent by the user, for example, the user inputs relevant information (for example, the identity information of the sender and receiver of the transaction, transaction information, etc.) on the mobile phone, tablet computer, self-service terminal equipment, etc. Type information, etc.) after the transaction request, such as receiving the transaction request sent by the user after inputting relevant information on the transaction client pre-installed in the mobile phone, tablet computer, self-service terminal equipment, etc., or receiving the user’s mobile phone, tablet computer , Self-service terminal equipment and other terminal browser system after inputting relevant information to send transaction request.

[0087] After the transaction processing control system receives the transaction request sent by the user, it determines the transaction type corresponding to the transaction request. For example, it can be classified according to the business category of the transaction request, and the same or similar businesses can be classified into one category, for example, financial Type transactions (such as transfer transactions, online payment transactions, etc.), query transactions (such as account balance query transactions, transaction details query transactions), etc.

[0088] The analysis module 02 is used to analyze the database type corresponding to the determined transaction type according to the predetermined mapping relationship between the transaction type and the database type. The database type includes a main database and a read-only data associated with the data in the main database. database;

[0089] After the transaction type corresponding to the transaction request is determined, the database types corresponding to different transaction types can be analyzed according to the predetermined mapping relationship between the transaction type and the database type. The database type includes the main database and the database type corresponding to the main database. The read-only database associated with the data. The situation where the data in the main database is associated with the read-only database includes but is not limited to: the main database is completely synchronized with the read-only database, or the data synchronization delay time between the main database and the read-only database is relatively small, And so on in other circumstances, it is not limited here.

[0090] In one embodiment, the database type mapping can be performed for different operation modes of the database according to different transaction types. For example, financial transactions require operations such as reading and writing data in the database, and then financial transactions are predetermined The type and the main database are in a mapping relationship; the query transaction only needs to read data in the database, and the query transaction type and the read-only database are determined in advance as a mapping relationship.

[0091] In another embodiment, after calculating the transaction data of the core transaction system, the number of transactions with higher importance of the core transaction system (financial transactions such as transfer transactions, online payment transactions, etc.) accounted for the total number of transactions Usually low (for example, about 40%), transactions with low importance (query transactions such as account balance query transactions, transaction details query transactions, etc.) account for a relatively high proportion of the total number of transactions (for example, about 60%). If the transactions of higher importance and transactions of lower importance in the core transaction system share the same database resources, it will usually cause transactions with lower importance to preempt the resources of transactions with higher importance, which will often cause The system processing channel of relatively high importance transactions is blocked, and the timely processing of relatively high importance transactions cannot be guaranteed. Therefore, in this embodiment, different transaction types can be mapped to their database types according to their importance. For example, transactions with higher importance, such as financial transaction types, can be mapped to the main database in advance. Low transactions such as query transactions and read-only databases are mapped to ensure that relatively low-importance transactions will not preempt the database resources of relatively high-importance transactions, thereby ensuring the timely processing of relatively high-importance transactions . Specifically, the importance of different transaction types can be rated, and the transaction types with the importance level exceeding the preset level are regarded as higher importance transaction types, such as financial transactions; the importance level is less than or equal to the preset level as the more important transaction type. Low transaction types, such as query transactions, etc. Then, according to the importance of different transaction types, you can pre-determine the mapping relationship between the higher transaction types and the main database, and the lower transaction types and read-only The database is a mapping relationship.

[0092] Of course, users can also pre-define the mapping relationship between different transaction types and database types according to actual application needs. For example, the current transaction types that need urgent or urgent processing can be pre-determined as the mapping relationship with the main database to ensure The timely processing of this transaction type is not limited here.

[0093] The response module 03 is configured to respond to the transaction request based on the main database if the analyzed database type is a primary database, or, if the analyzed database type is a read-only database, respond to the transaction based on the read-only database request.

[0094] If the database type corresponding to the transaction type of the transaction request is analyzed according to the predetermined mapping relationship between the transaction type and the database type as the master database, the transaction request is responded to based on the master database. If the master database responds to the transaction request The data in the main database is read and written.

[0095] If the database type corresponding to the transaction type of the transaction request is a read-only database based on the analysis of the mapping relationship between the predetermined transaction type and the database type, the transaction request is responded to based on the read-only database, and the read-only database responds to the transaction request. The transaction requests an operation to read data in the read-only database.

[0096] In this embodiment, after receiving the transaction request, the transaction type corresponding to the transaction request is determined, and the database type corresponding to the transaction type is determined. If the database type is the main database, the transaction request is responded to based on the main database. If the type is a read-only database, the transaction request is responded to based on the read-only database. Since it can respond to transaction requests based on different databases according to different transaction types, that is, database split processing is performed for transaction requests of different transaction types, so as to avoid mutual grabbing resources when processing transaction requests of different transaction types. It can be different according to user-defined settings. Transaction types are allocated to corresponding database responses, so as to ensure that different transaction types are not affected by other transaction types and can be processed in a timely manner to improve transaction processing efficiency.

[0097] Such as Figure 4 As shown, the second embodiment of the present invention proposes a transaction processing control system, and on the basis of the foregoing embodiment, it further includes:

[0098] The synchronization module 04 is used to synchronize the data in the main database to the read-only database in real time or regularly; or, if there is data to be written in the main database, synchronize the written data to the read-only database.

[0099] In this embodiment, the data in the main database is synchronized to the read-only database in real time or at regular intervals, and when data is written in the main database, the written data is synchronized to the read-only database in real time to achieve The data synchronization between the main database and the read-only database ensures that when responding to transaction requests of different transaction types, the data read in the main database and the read-only database are consistent, thereby ensuring the transaction Correctness.

[0100] Further, in other embodiments, the predetermined transaction types include financial transactions and query transactions, the financial transactions correspond to the main database, the query transactions correspond to the read-only database, and the above response Module 03 is also used for:

[0101] If the analyzed database type is the main database, in response to the transaction request, read transaction data from the main database and/or write transaction data to the main database;

[0102] If the analyzed database type is the read-only database, in response to the transaction request, read transaction data corresponding to the transaction request from the read-only database and feed back the read transaction data to the sender of the transaction request .

[0103] In this embodiment, if the predetermined transaction types include financial transactions such as transfer transactions, online payment transactions, etc., and query transactions such as account balance query transactions, transaction details query transactions, etc., and the corresponding financial transaction is determined in advance. In the main database, the query transaction corresponds to the read-only database. Then, if it is analyzed that the database type corresponding to the transaction type of the transaction request is the main database, then based on the main database, respond to the transaction request, read transaction data from the main database and/or write transaction data to the main database . If it is analyzed that the database type corresponding to the transaction type of the transaction request is a read-only database, then the transaction request is responded to based on the read-only database, the transaction data corresponding to the transaction request is read from the read-only database and read The transaction data is fed back to the sender of the transaction request, such as self-service inquiry terminal, mobile terminal, etc.

[0104] This embodiment can respond to different databases according to different transaction types, realize database shunt processing for transaction requests of different transaction types, avoid grabbing resources when processing transaction requests of different transaction types, and improve transaction processing efficiency.

[0105] Further, in other embodiments, the predetermined transaction types include financial transactions and query transactions, the financial transactions correspond to the main database, the query transactions correspond to the read-only database, and the above response Module 03 is also used for:

[0106] If the analyzed database type is a read-only database, perform data synchronization delay check on the read-only database;

[0107] If the data synchronization delay verification of the read-only database is successful, in response to the transaction request, the transaction data corresponding to the transaction request is read from the read-only database and the read transaction data is fed back to the sending of the transaction request square;

[0108] If the data synchronization delay verification of the read-only database fails, in response to the transaction request, the transaction data corresponding to the transaction request is read from the main database and the read transaction data is fed back to the sender of the transaction request .

[0109] In this embodiment, if it is analyzed that the database type corresponding to the transaction type of the transaction request is a read-only database, then before responding to the transaction request, the read-only database needs to be checked for data synchronization delay, that is, the check office Whether the data synchronization delay of the read-only database relative to the main database meets the transaction requirements.

[0110] In one embodiment, the method for checking the data synchronization delay of the read-only database may include: determining the data synchronization delay of the read-only database relative to the main database according to a predetermined synchronization delay time determination method Time, for example, the data synchronization delay time relative to the main database can be obtained from the preset type parameter of the read-only database through a predetermined command, for example, if the read-only database and the main database are both Oracle databases , Oracle database provides a view v$dataguard_stats, which contains real-time data synchronization delay time, you can pass a predetermined SQL command on the read-only database (for example, select value from v$dataguard_stats where name='apply lag') Then, the data synchronization delay time of the read-only database relative to the main database can be obtained. After the data synchronization delay time of the read-only database relative to the main database is determined, the determined data synchronization delay time can be compared with a preset delay time (for example, 2 seconds), if the determined data synchronization delay time Is greater than the preset delay time (for example, 2 seconds), it is determined that the data synchronization delay verification of the read-only database has failed; if the determined data synchronization delay time is less than or equal to the preset delay time (for example, 2 seconds), then It is determined that the data synchronization delay verification of the read-only database is successful.

[0111] If it is determined that the data synchronization delay verification of the read-only database is successful, the read-only database responds to the transaction request based on the read-only database, reads the transaction data corresponding to the transaction request from the read-only database and reads the transaction data Feedback to the sender of the transaction request, such as self-service inquiry terminals, mobile terminals, etc.

[0112] If it is determined that the data synchronization delay verification of the read-only database fails, based on the master database responds to the transaction request, the transaction data corresponding to the transaction request is read from the master database and the read transaction data is fed back to The sender of the transaction request is a self-service inquiry terminal, a mobile terminal, etc.

[0113] In this embodiment, if it is analyzed that the database type corresponding to the transaction type of the transaction request is a read-only database, before using the read-only database to respond to the transaction request, the read-only database is also checked for data synchronization delay . If the data synchronization delay check of the read-only database is successful, that is, the data synchronization delay time of the read-only database relative to the main database is relatively small, it means that the data synchronization frequency of the read-only database and the main database is high. The read-only database can be consistent with the data of the main database, and can meet the requirements of processing business, then the read-only database is directly used to respond to the transaction request such as query transaction (account balance query transaction, transaction detail information query transaction )Wait. If the data synchronization delay check of the read-only database fails, that is, the data synchronization delay time of the read-only database relative to the main database is relatively large, it means that the data synchronization frequency of the read-only database and the main database is low. The read-only database can not be consistent with the data of the main database, and cannot meet the requirements of processing business, then the main reading database is used to respond to the transaction request such as query transaction (account balance query transaction, transaction detail information query transaction ), etc. to ensure the accuracy of the transaction request response.

[0114] It should be noted that in this article, the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, It also includes other elements not explicitly listed, or elements inherent to the process, method, article, or device. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, article or device that includes the element.

[0115] Through the description of the above embodiments, those skilled in the art can clearly understand that the method of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is Better implementation. Based on this understanding, the technical solution of the present invention essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes several instructions to enable a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the method described in each embodiment of the present invention.

[0116] The preferred embodiments of the present invention are described above with reference to the accompanying drawings, and the scope of rights of the present invention is not limited thereby. The sequence numbers of the foregoing embodiments of the present invention are only for description, and do not represent the superiority of the embodiments. In addition, although a logical sequence is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than here.

[0117] Those skilled in the art can implement the present invention in many variations without departing from the scope and essence of the present invention. For example, the features of one embodiment can be used in another embodiment to obtain another embodiment. Any modification, equivalent replacement and improvement made within the technical concept of the application of the present invention shall fall within the scope of the rights of the present invention.