CN112613993A - Transaction data processing method and device, computer equipment and storage medium - Google Patents
Transaction data processing method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN112613993A CN112613993A CN202011570641.2A CN202011570641A CN112613993A CN 112613993 A CN112613993 A CN 112613993A CN 202011570641 A CN202011570641 A CN 202011570641A CN 112613993 A CN112613993 A CN 112613993A
- Authority
- CN
- China
- Prior art keywords
- transaction
- abnormal
- identifier
- transaction identifier
- global
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Debugging And Monitoring (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a transaction data processing method, a transaction data processing device, computer equipment and a storage medium. The method comprises the following steps: the core system server obtains a global transaction identifier corresponding to the abnormal transaction and at least one associated local transaction identifier by detecting the abnormal transaction, and sends the global transaction identifier and the at least one associated local transaction identifier to the corresponding service subsystems, so that each service subsystem performs correction processing on the abnormal transaction based on the received global transaction identifier and the corresponding local transaction identifier. The abnormal transactions are detected uniformly through the core system server, all the service subsystems corresponding to the abnormal transactions are confirmed according to the global transaction identification and the corresponding local transaction identification of the abnormal transactions, and correction is executed through all the service subsystems, so that the uniform control over the correction of the abnormal transactions is realized, and the efficiency and the accuracy of correction control are improved.
Description
Technical Field
The present application relates to the field of application systems, and in particular, to a transaction data processing method, apparatus, computer device, and storage medium.
Background
With the development of application system technology, financial institutions often handle daily transactions and management through financial systems. In the transaction process, errors can occur in the response message of the transaction request due to network or system reasons. In this case, the financial system needs to roll back the data of different node changes to the state before operation, i.e. transaction alignment, to ensure the accuracy of the system.
In the prior art, as financial transactions are increasingly frequent, the transaction correcting logic of a financial system is more and more complex, and the transaction correcting efficiency is lower.
Disclosure of Invention
In view of the above, it is necessary to provide a transaction data processing method, apparatus, computer device and storage medium for solving the technical problem of low efficiency in the prior art.
A transaction data processing method applied to a core system server, the core system server being in communication connection with at least one service subsystem, the method comprising:
detecting abnormal transactions;
acquiring a global transaction identifier corresponding to the abnormal transaction and at least one local transaction identifier associated with the global transaction identifier; the global transaction identification is used for identifying the abnormal transaction in the core system server; the local transaction identifier is used for identifying the abnormal transaction in the corresponding service subsystem;
and sending the global transaction identifier and the at least one local transaction identifier to service subsystems corresponding to the at least one local transaction identifier respectively, so that the at least one service subsystem carries out correction processing on the abnormal transaction based on the received global transaction identifier and the corresponding local transaction identifier respectively.
In one embodiment, the detecting of the abnormal transaction includes:
obtaining at least one initial anomalous transaction; the initial abnormal transaction carries a transaction type;
and determining the abnormal transaction from the at least one initial abnormal transaction according to the transaction type.
In one embodiment, before the sending the global transaction identifier and the at least one local transaction identifier to the corresponding at least one service subsystem, the method further includes:
configuring a correcting parameter, a bill type and a correcting function of each transaction type aiming at least one transaction type to obtain a correcting control table corresponding to each transaction type and store the correcting control table for correcting the abnormal transaction;
wherein the straightening parameter characterizes a straightening object; the bill type is used for determining a corresponding positive flow; the positive-going function is used to determine the corresponding positive-going computation logic.
In one embodiment, the method further comprises:
aiming at each service subsystem in the at least one service subsystem, acquiring transaction request messages respectively corresponding to at least one transaction of the service subsystem;
generating a global transaction identifier of a transaction corresponding to the transaction request in the core system server according to each transaction request message in the at least one transaction request message;
determining a business subsystem corresponding to each transaction in the at least one transaction respectively, and generating local transaction identifiers corresponding to the at least one transaction respectively;
and storing the generated global transaction identification and the local transaction identification into registration information.
In one embodiment, the method further comprises:
when target operation of the at least one business subsystem in transaction execution is detected, acquiring an SQL command corresponding to the target operation;
analyzing the SQL command to obtain transaction operation data of the at least one business subsystem corresponding to the transaction;
and storing the transaction operation data corresponding to the at least one service subsystem as corresponding mirror image registration information according to the global transaction identifier and the at least one local transaction identifier.
In one embodiment, the method further comprises:
detecting positive execution information of each service subsystem;
and if the forward flushing execution information indicates that the forward flushing processing is abnormal, generating early warning information containing abnormal information, and sending the early warning information to an early warning terminal to trigger the forward flushing processing to be carried out again aiming at the abnormal transaction.
A transaction data processing method applied to a service subsystem, wherein the service subsystem is in service communication connection with a core system, and the method comprises the following steps:
acquiring a global transaction identifier of an abnormal transaction sent by a core system server and a local transaction identifier associated with the global transaction identifier; the abnormal transaction is detected by the core system server; the global transaction identifier is used for identifying the abnormal transaction in the core system server, and the local transaction identifier is used for identifying the abnormal transaction in the corresponding service subsystem;
inquiring mirror image registration information and an alignment control table corresponding to the abnormal transaction according to the global transaction identifier and the local transaction identifier;
performing correction processing on the abnormal transaction according to the mirror image registration information and a correction control table, and recovering information corresponding to the abnormal transaction in the business subsystem to a state before transaction operation; the mirror image registration information comprises transaction operation data of a transaction related party before the transaction abnormal event occurs; and the conflict control table is configured with conflict rules corresponding to the abnormal transactions.
In one embodiment, the querying, according to the global transaction identifier and the local transaction identifier, the mirror registration information and the alignment control table corresponding to the abnormal transaction includes:
determining pre-registered mirror image registration information corresponding to the abnormal transaction according to the global transaction identifier and the local transaction identifier;
and determining the transaction type of the abnormal transaction according to the global transaction identifier and the local transaction identifier, and determining a pre-configured alignment control table corresponding to the abnormal transaction according to the type of the abnormal transaction.
In one embodiment, the performing rectification processing on the abnormal transaction according to the mirror image registration information and the rectification control table, and restoring the information corresponding to the abnormal transaction in the local service subsystem to a state before transaction operation includes:
acquiring transaction operation information of the abnormal transaction corresponding to the business subsystem from the mirror image registration information;
and according to the conflict control table, the transaction operation information is restored to the state before the transaction operation in a reverse order according to the sequence of the transaction operation.
A transaction data processing apparatus for use with a core system server, the core system server communicatively coupled to at least one business subsystem, the apparatus comprising:
the abnormal transaction detection module is used for detecting abnormal transactions;
the transaction identifier acquisition module is used for acquiring a global transaction identifier corresponding to the abnormal transaction and at least one local transaction identifier associated with the global transaction identifier; the global transaction identification is used for identifying the abnormal transaction in the core system server; the local transaction identifier is used for identifying the abnormal transaction in the corresponding service subsystem;
and the transaction identifier sending module is used for sending the global transaction identifier and the at least one local transaction identifier to the service subsystems corresponding to the at least one local transaction identifier respectively, so that the at least one service subsystem carries out correction processing on the abnormal transaction based on the received global transaction identifier and the corresponding local transaction identifier respectively.
A transaction data processing method device is applied to a business subsystem, the business subsystem is in service communication connection with a core system, and the device comprises:
the transaction identifier receiving module is used for acquiring a global transaction identifier of the abnormal transaction sent by the core system server and a local transaction identifier associated with the global transaction identifier; the abnormal transaction is detected by the core system server; the global transaction identifier is used for identifying the abnormal transaction in the core system server, and the local transaction identifier is used for identifying the abnormal transaction in the corresponding service subsystem;
the query module is used for querying mirror image registration information and a correction control table corresponding to the abnormal transaction according to the global transaction identifier and the local transaction identifier;
the correcting processing module is used for correcting the abnormal transaction according to the mirror image registration information and the correcting control table and restoring the information corresponding to the abnormal transaction in the business subsystem to the state before transaction operation; the mirror image registration information comprises transaction operation data of a transaction related party before the transaction abnormal event occurs; and the conflict control table is configured with conflict rules corresponding to the abnormal transactions.
A computer device comprising a memory storing a computer program and a processor implementing the steps of the transaction data processing method of any of the above embodiments when the processor executes the computer program.
A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, carries out the steps of the transaction data processing method of any of the embodiments described above.
According to the transaction data processing method, the transaction data processing device, the computer equipment and the storage medium, the core system server obtains the global transaction identifier corresponding to the abnormal transaction and the associated at least one local transaction identifier by detecting the abnormal transaction, and sends the global transaction identifier and the associated at least one local transaction identifier to the corresponding business subsystem, so that each business subsystem executes correction processing on the abnormal transaction based on the received global transaction identifier and the corresponding local transaction identifier. The abnormal transactions are detected uniformly through the core system server, all the service subsystems corresponding to the abnormal transactions are confirmed according to the global transaction identification and the corresponding local transaction identification of the abnormal transactions, and correction is executed through all the service subsystems, so that the uniform control over the correction of the abnormal transactions is realized, and the efficiency and the accuracy of correction control are improved.
Drawings
FIG. 1 is a diagram of an application environment of a transaction data processing method in one embodiment;
FIG. 2 is a schematic flow chart diagram of a transaction data processing method according to another embodiment;
FIG. 3 is a schematic flow chart diagram illustrating a transaction data processing method according to another embodiment;
FIG. 4 is a schematic flow chart diagram illustrating a transaction data processing method according to another embodiment;
FIG. 5 is a block diagram of the structure of a transaction data processing device in one embodiment;
FIG. 6 is a block diagram showing the construction of a transaction data processing apparatus according to another embodiment;
FIG. 7 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The transaction data processing method provided by the application can be applied to the application environment shown in fig. 1. Wherein the core system server communicates with the at least one service subsystem over a network. The business subsystems can execute the transaction business according to the configuration, the core system server detects the abnormal transaction, obtains the transaction identification corresponding to the abnormal transaction, sends the transaction identification to the corresponding business subsystems, and each business subsystem executes the transaction correction. The core system server and each service subsystem may be implemented by an independent server or a server cluster composed of a plurality of servers.
In some embodiments, the service subsystem may be a component module of a core system server, and the core system employs a distributed architecture.
In one embodiment, as shown in fig. 2, a transaction data processing method is provided, which is described by taking the example that the method is applied to the core system server in fig. 1, and includes the following steps:
in step S201, an abnormal transaction is detected.
The transaction in the financial system can be divided into forward transaction and transaction reversal, the forward transaction can be carried out according to a normal flow, the transaction reversal can be carried out aiming at the forward transaction, and the transaction in the system is restored to a state before the forward transaction operation. The core system server can configure the flushable orthogonal reciprocity type, and determines to start the flushable positive program according to the transaction type corresponding to the detected transaction abnormal event.
In specific implementation, the core system server may detect transactions of each service subsystem, and if a transaction abnormal event is detected, obtain a transaction corresponding to the transaction abnormal event, and start a forward program as an abnormal transaction to be executed.
Step S202, a global transaction identifier corresponding to the abnormal transaction and at least one local transaction identifier associated with the global transaction identifier are obtained.
The transaction identification information may be information for uniquely determining a transaction, and may include a transaction serial number, a global transaction identification, a local transaction identification, and the like. The global transaction identity may be used to identify the corresponding transaction in the core system server and the local transaction identity may be used to identify the corresponding transaction in the corresponding service subsystem. When a forward transaction starts to establish a task, the core system server may determine unique global transaction identification information of the transaction, determine local transaction identifications corresponding to the service subsystems respectively according to the service subsystems to be called, and establish an association relationship between the global transaction identification and at least one local transaction identification. The core system server may register a global transaction identity and a local transaction identity for a forward transaction when executing the transaction.
In a specific implementation, the core system server may obtain global transaction identification information corresponding to the abnormal transaction and at least one associated local transaction identification from the transaction identification information registered in advance according to the abnormal transaction.
Step S203, sending the global transaction identifier and the at least one local transaction identifier to the service subsystems corresponding to the at least one local transaction identifier, so that the at least one service subsystem performs correction processing on the abnormal transaction based on the received global transaction identifier and the corresponding local transaction identifier, respectively.
And each service subsystem executing the abnormal transaction is respectively configured with a corresponding local transaction identifier. Each business subsystem can respectively execute the transaction correcting program corresponding to the local subsystem. When the transaction is executed, the service subsystems can query the mirror image registration information and the transaction control table corresponding to the abnormal transaction according to the received global transaction identifier and the local transaction identifier corresponding to the local subsystem, and perform transaction processing on the abnormal transaction according to the mirror image registration information and the transaction control table, so that the information corresponding to the abnormal transaction in each service subsystem is recovered to the state before the forward transaction operation.
The mirror image registration information can be transaction operation data information of a transaction related party when each service subsystem executes forward transaction before a transaction abnormal event occurs, and the mirror image registration information can be inquired through a global transaction identifier and a local transaction identifier corresponding to the transaction; the flushing and normalizing control table may be configured with flushing and normalizing rules corresponding to abnormal transactions, and flushing and normalizing rules corresponding to different transaction types may be different.
In a specific implementation, the core system server may send the global transaction identifier and the at least one local transaction identifier to the service subsystems corresponding to the at least one local transaction identifier, and each service subsystem executes a corresponding forward flushing operation, so that the transaction operation data corresponding to the abnormal transaction in each service subsystem is restored to a state before the transaction operation.
In the transaction data processing method, the core system server obtains the global transaction identifier corresponding to the abnormal transaction and the associated at least one local transaction identifier by detecting the abnormal transaction, and sends the global transaction identifier and the associated at least one local transaction identifier to the corresponding business subsystem, so that each business subsystem executes correction processing on the abnormal transaction based on the received global transaction identifier and the corresponding local transaction identifier. The abnormal transactions are detected uniformly through the core system server, all the service subsystems corresponding to the abnormal transactions are confirmed according to the global transaction identification and the corresponding local transaction identification of the abnormal transactions, and correction is executed through all the service subsystems, so that the uniform control over the correction of the abnormal transactions is realized, and the efficiency and the accuracy of correction control are improved.
In one embodiment, the detection of abnormal transactions determined in step S201 includes:
obtaining at least one initial anomalous transaction; the initial abnormal transaction carries a transaction type; and determining the abnormal transaction from at least one initial abnormal transaction according to the transaction type.
In this embodiment, the transaction types of each service system may be multiple, the core system server may preset a flushable orthogonal transaction type, match a transaction corresponding to the detected transaction abnormal event with the flushable orthogonal transaction type, and if the transaction belongs to the flushable orthogonal transaction type, determine that a flushable forward procedure is started, and determine that the transaction is an abnormal transaction. Whether the transaction types can be positively identified or not is judged in advance, and the abnormal transactions are determined, so that the efficiency of positively identifying and starting is improved.
In one embodiment, the core system server may set the transaction global configuration table to preset flushable orthogonal transaction types, non-flushable orthogonal transaction types, and define a time period for which flushable is allowed.
In one embodiment, the method further comprises:
and configuring a correcting parameter, a bill type and a correcting function of each transaction type aiming at least one transaction type, obtaining and storing a correcting control table corresponding to each transaction type, and using the correcting control table to correct abnormal transactions.
In this embodiment, the core system server may pre-configure the alignment control table for each transaction type. So that the service subsystem can call the corresponding conflict control table to execute conflict. The correcting control table can be associated with specific transaction types, and a correcting parameter, a bill type and a correcting function corresponding to each transaction type are respectively configured.
The positive going parameter may indicate a positive going object, for example, the positive going object may be a field level positive going object, or a table level positive going object, and different positive going objects correspond to different positive going rules. The bill type may be used to determine different correction procedures, for example, if the table to be corrected is a bill detail table, a separate correction procedure is executed, and a detail correction function corresponding to the procedure is called. The positive flush function may be used to determine positive flush computation logic, and the positive flush function may include a positive flush execution function, a pre-positive flush condition function, and a post-positive flush condition function, where the pre-positive flush condition function may be a function called before the positive flush, and the post-positive flush condition function may be a function called after the positive flush. When the business subsystem executes the rushing, whether a self-defined condition function before rushing forward and a condition function after rushing forward exist or not can be checked, and if the self-defined condition function before rushing forward and the condition function after rushing forward exist, the condition function before rushing forward and the condition function after rushing forward are called once and executed.
In some embodiments, the alignment control table configured by the core system server may include details such as, for example, the type of transaction, the transaction table, the fields in the table that define the alignment that may be performed in the transaction, and the manner of alignment, such as variable values, fixed values, etc., and may also define the alignment function.
In some embodiments, the positive control table may further include field information, such as a database name, a form statement flag, a table record deletion reservation flag, a field english name, a positive correlation flag, a field positive update manner, a variable value chargeable flag, a variable value override manner, a special value positive flag, a special value list, and the like.
In the scheme of the embodiment, the core system server configures the corresponding alignment control table for each transaction type in advance, so that the corresponding alignment control table can be called to perform alignment during execution, and the alignment rule does not need to be configured for each transaction, thereby reducing the complexity of system development and improving the alignment efficiency.
In one embodiment, the method further comprises:
aiming at each service subsystem in at least one service subsystem, acquiring transaction request messages respectively corresponding to at least one transaction of the service subsystem; generating a global transaction identifier of a transaction corresponding to the transaction request in the core system server according to each transaction request message in at least one transaction request message; determining a business subsystem corresponding to each transaction in at least one transaction respectively, and generating local transaction identifiers corresponding to the at least one transaction respectively; and storing the generated global transaction identification and the local transaction identification into the registration information.
In this embodiment, the core system server may generate a uniform global transaction identifier of the transaction according to the transaction request message sent by each service subsystem when each service subsystem executes the forward transaction, and invoke the service subsystem according to the transaction requirement to generate a local transaction identifier corresponding to each service subsystem. Thereby a global transaction identity and an associated at least one local transaction identity for the transaction may be obtained.
The core system server may store a global transaction identifier corresponding to the transaction and the associated at least one local transaction identifier in registration information, which may be invoked when executing the transaction.
Specifically, if the transaction is determined to be an abnormal transaction, the core system server may query the transaction identifier information registered in advance according to the transaction serial number carried in the abnormal event information, so as to obtain a global transaction identifier of the abnormal transaction and at least one associated local transaction identifier, and may search the operation data corresponding to the abnormal transaction according to the global transaction identifier and the at least one associated local transaction identifier when the transaction is flushed.
In some embodiments, during the execution of the forward transaction, the core system server may record corresponding mirror registration information of the transaction in each service subsystem according to the global transaction identifier and the at least one local transaction identifier.
In some embodiments, the core system server may process the flushing of multiple abnormal transactions, and the core system server may perform the flushing of corresponding abnormal transactions one by one in reverse order from the latest generated global transaction identifier according to the global transaction identifier of each abnormal transaction.
In some embodiments, the core system server may be configured with a unified forward flushing management center module, and is responsible for managing the global transaction identifier and the local transaction identifier of the transaction, and when the transaction needs to be flushed, the forward flushing is performed one by one according to the global transaction identifier in a reverse order for a plurality of abnormal transactions. And aiming at each transaction needing to be corrected, correcting each transaction link one by one in a reverse order according to the sequence of the local transaction identifier.
In the solution of the above embodiment, the core system server may generate the global transaction identifier corresponding to the transaction and the associated at least one local transaction identifier when each service subsystem executes the forward transaction, so as to identify the transaction and register and query the transaction related information, thereby improving the efficiency of transaction data management.
In one embodiment, the method further comprises:
when target operation of at least one business subsystem in transaction execution is detected, acquiring an SQL command corresponding to the target operation; analyzing the SQL command to obtain transaction operation data of the transaction in at least one service subsystem; and storing the transaction operation data corresponding to at least one service subsystem as corresponding mirror image registration information according to the global transaction identifier and the at least one local transaction identifier.
In this embodiment, the core system server may create mirror registration information for transactions performed by each of the service subsystems. The target operation may be a Data operation such as deleting, adding, modifying, and the like, performed on the corresponding database or Data record when each service subsystem executes the forward transaction according to the transaction flow, for example, a Data Management Language (DML) operation, a Data Definition Language (DDL) operation, and the like. SQL (Structured Query Language) may be used to access data and Query, update, and manage relational database systems. The SQL command may carry corresponding transaction operation data, where the transaction operation data may include data before transaction operation update and data after transaction operation update in the service subsystem, and when the transaction is performed, each service subsystem may select field data to be used according to a forward/backward control table to perform backward flushing. For example, when the target operation is a new addition operation, the data before update is empty, when the target operation is a deletion operation, the data after update is empty, and when the target operation is a modification operation, the corresponding fields before and after update have data. The mirror image registration information can be used for recording data change during normal operation of the transaction, and when the transaction needs to be flushed, data before and after transaction processing are acquired from the mirror image registration information.
In the forward transaction process, the core system server may detect a target operation of each service subsystem when performing the forward transaction, intercept an SQL command corresponding to the target operation, and analyze the command to obtain transaction operation data of the transaction in the service subsystem. The core system server may store the transaction operation information, in association with the global transaction identifier of the transaction and the local transaction identifier of the business subsystem, as mirror registration information.
In some embodiments, the core system server may configure a service data mirror center module, which is used to record data changes of each service subsystem during forward transaction, that is, mirror registration information, and obtain the last node data from the service subsystem when the data needs to be flushed. The field information in the mirror registration information may include: global transaction identification, local transaction identification, transaction serial number, operation serial number, transaction date, timestamp, teller serial number, transaction code, application name, server node, process information, operation mode, primary key content, keyword list, pre-update content, post-update content, and the like.
In some embodiments, the business subsystem may generate a plurality of transaction sequence numbers and corresponding transaction operation information when performing forward transactions. The transaction sequence number may be an operation sequence number of the transaction subsystem in forward direction, and the sequence numbers may be sequentially and reversely flushed back in the transaction subsystem in order to ensure accuracy. The local transaction sequence number may be included in the transaction operation data.
According to the scheme of the embodiment, the core system server can detect the forward transaction of the business subsystem, acquire the transaction operation data and store the transaction operation data as the mirror image registration information, so that the transaction process data can be traced, and the efficiency and the accuracy of correcting are improved.
In one embodiment, the method further comprises:
and generating a positive conflict request containing the global transaction identifier and at least one local transaction identifier, sending the positive conflict request to the unified port, and triggering the unified port to send the global transaction identifier and the at least one local transaction identifier to the corresponding at least one service subsystem.
In this embodiment, the core system server may be configured with a unified port connected to each service subsystem, and the unified port may send, according to the request for forwarding of the core system server, the global transaction identifier and the at least one local transaction identifier carried in the request for forwarding to the service subsystems corresponding to each local transaction identifier respectively.
In some embodiments, the unified port may be a facing Gate, the facing Gate may traverse each local transaction identifier, and send the transaction identifier to the corresponding service subsystem, and the service subsystem may perform facing through the configured facing client.
According to the scheme of the embodiment, the core system server can send the corresponding global transaction identifier and the corresponding local transaction identifier to each service subsystem through the unified port, so that the efficiency of positive information transmission is improved.
In one embodiment, the method further comprises:
detecting positive execution information of each service subsystem; and if the forward flushing execution information indicates that the forward flushing processing is abnormal, generating early warning information containing the abnormal information, and sending the early warning information to an early warning terminal.
In this embodiment, the forward flushing execution information may be information fed back in the process of executing forward flushing by each service subsystem, and the abnormal information may include a service subsystem with an abnormal forward flushing, an abnormal type, response information, and the like. The core system server can detect the positive execution information of each service subsystem, if the positive execution information is abnormal, early warning information containing the abnormal information is generated and sent to the early warning terminal.
In some embodiments, the core system server may be configured with a unified early warning center, and configured to receive the abnormal information when the correction is abnormal, and send the abnormal information to the early warning terminal to prompt a worker to perform manual intervention.
According to the scheme of the embodiment, the core system server can send out early warning information in time when each service subsystem is abnormal in flushing, so that the response instantaneity in the flushing process is improved.
In one embodiment, as shown in fig. 3, there is provided a transaction data processing applied to a service subsystem, the service subsystem being in service communication with a core system, including:
step S301, acquiring a global transaction identifier of the abnormal transaction sent by the core system server and a local transaction identifier associated with the global transaction identifier;
the abnormal transaction can be detected by the core system server; the global transaction identity may be used to identify anomalous transactions at the core system server and the local transaction identity may be used to identify anomalous transactions in the corresponding business subsystem.
In a specific implementation, the service subsystem may receive a global transaction identifier of the abnormal transaction and a local transaction identifier corresponding to the local service subsystem, which are sent by the core system server.
Step S302, according to the global transaction identifier and the local transaction identifier, mirror image registration information and a correction control table corresponding to the abnormal transaction are inquired.
In a specific implementation, the service subsystem may obtain, from the core system server, the mirror registration information of the abnormal transaction and obtain an alignment control table including the alignment rule of the transaction of the service subsystem according to the global transaction identifier and the local transaction identifier.
Step S303, carrying out correction processing on the abnormal transaction according to the mirror image registration information and the correction control table, and recovering the information corresponding to the abnormal transaction in the local subsystem to the state before transaction operation;
in a specific implementation, the business subsystem can perform correction processing on the abnormal transaction according to the information registered in the mirror image registration table and the correction rule contained in the correction control table, and restore the information corresponding to the abnormal transaction in the business subsystem to the state before the operation of the abnormal transaction.
In the scheme of the embodiment, the service subsystem acquires the global transaction identifier and the local transaction identifier of the abnormal transaction from the core system server, and queries the corresponding mirror image registration information and the alignment control table to execute alignment processing, so that the information corresponding to the abnormal transaction in the service subsystem is recovered to the state before transaction operation. The business subsystem queries the mirror image registration information and the conflict control table corresponding to the abnormal transaction through the global transaction identifier and the local transaction identifier of the abnormal transaction, can quickly acquire the information corresponding to the abnormal transaction and the conflict rule, and improves the efficiency and the accuracy of conflict execution.
In one embodiment, the step of querying the mirror registration information and the alignment control table corresponding to the abnormal transaction according to the global transaction identifier and the local transaction identifier, which is determined in step S302, includes:
determining pre-registered mirror image registration information corresponding to the abnormal transaction according to the global transaction identifier and the local transaction identifier; and determining the transaction type of the abnormal transaction according to the global transaction identifier and the local transaction identifier, and determining a pre-configured reversal control table corresponding to the abnormal transaction according to the type of the abnormal transaction.
In this embodiment, in the forward transaction process, the core system server may store the global transaction identifier and the local transaction identifier, and the associated transaction operation data in the mirror registration information. The core system server can also pre-configure a conflict and correction control table corresponding to each transaction type.
The service subsystem can acquire mirror image registration information corresponding to the abnormal transaction according to the global transaction identifier and the local transaction identifier. The business subsystem can also determine the transaction type of the abnormal transaction according to the global transaction identifier and the local transaction identifier, and obtain a pre-configured correction control table according to the transaction type.
According to the scheme of the embodiment, the business subsystem can acquire the corresponding mirror image registration information and the conflict control table through the global transaction identifier and the local transaction identifier, so that conflict has a clear content basis and conflict rules, the business subsystem does not need to set conflict rules for each transaction, and the conflict efficiency and accuracy are improved.
In one embodiment, the step of performing a correction process on the abnormal transaction according to the mirror image registration information and the correction control table determined in step S303, and restoring the information corresponding to the abnormal transaction in the business subsystem to a state before the transaction operation includes:
acquiring transaction operation information of abnormal transactions corresponding to the business subsystem from the mirror image registration information; and according to the conflict control table, the transaction operation information is restored to the state before the transaction operation in a reverse order according to the sequence of the transaction operation.
In this embodiment, when the transaction subsystem processes a forward transaction, multiple transaction operation processes may be involved, and when the transaction is abnormal and the timing is required to be executed, the transaction subsystem may restore the transaction operation information to the state before the transaction operation according to the timing control table and in a reverse order according to the sequence of the transaction operation.
In some embodiments, the local transaction subsystem may configure a local transaction sequence number for each transaction operation, which may be included in the transaction operation information. When the business subsystem executes the flushing in the system, the business subsystem can return back one by one in a reverse order according to the local transaction sequence number and restore the business subsystem to the state before the transaction operation one by one.
According to the scheme of the embodiment, the business subsystem can carry out the back flushing one by one according to the sequence of forward transaction operation, and the reliability of the positive flushing result is improved.
In one embodiment, as shown in fig. 4, there is provided a transaction data processing method, including:
the service subsystem starts to start forward transaction, sends a transaction request message to the core system server, acquires a global transaction identifier sent by the core system server and a local transaction identifier determined according to the service subsystem executing the transaction; the core system server registers a global transaction identifier and at least one local transaction identifier corresponding to the transaction.
And the core system server intercepts a corresponding SQL command according to a self-defined database interceptor when detecting that the business system generates DML operation, analyzes the command to obtain an analysis result, and writes the analysis result into a corresponding mirror image table according to the global transaction identifier and the local transaction identifier.
If the core system server detects that the transaction process is abnormal, determining that the transaction belongs to the flushable orthogonal transaction type according to a preset flushable transaction control table, determining the transaction as the abnormal transaction, and starting flushable.
And the core system server inquires a global transaction identifier and at least one local transaction identifier corresponding to the abnormal transaction in the registration information according to the transaction serial number of the abnormal transaction, and sends the global transaction identifier and the at least one local transaction identifier to the corresponding service subsystem through the positive-flushing Gate.
And each service subsystem inquires corresponding mirror image registration information and a correction control table according to the global transaction identifier and the corresponding local transaction identifier, and performs correction, so that the information corresponding to the abnormal transaction in the local subsystem is recovered to the state before the transaction operation.
And the core system server detects the positive flushing execution condition of each service subsystem, generates early warning information carrying abnormal information if positive flushing abnormality occurs, and sends the early warning information to the early warning terminal.
According to the scheme of the embodiment, the core system server acquires the global transaction identifier and the local transaction identifier when each business subsystem starts forward transactions, stores information corresponding to target operation in mirror image registration information, determines the business subsystem corresponding to the flushing when flushing is executed according to the global transaction identifier and the local transaction identifier of the abnormal transactions, queries the corresponding mirror image registration information and the flushing control table by the business subsystem for flushing, and sends out early warning information when the flushing is abnormal, so that the information corresponding to the abnormal transactions and the flushing rule can be quickly acquired when the flushing is performed, the unified control on the flushing of the abnormal transactions is realized, and the flushing efficiency and the flushing accuracy are improved.
It should be understood that although the various steps in the flow charts of fig. 2-4 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-4 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.
In one embodiment, as shown in fig. 5, there is provided a transaction data processing apparatus applied to a core system server, the apparatus 500 comprising:
an abnormal transaction detection module 501, configured to detect an abnormal transaction;
a transaction identifier obtaining module 502, configured to obtain a global transaction identifier corresponding to the abnormal transaction, and at least one local transaction identifier associated with the global transaction identifier; the global transaction identifier is used for identifying abnormal transactions in the core system server; the local transaction identifier is used for identifying abnormal transactions in the corresponding service subsystem;
the transaction identifier sending module 503 is configured to send the global transaction identifier and the at least one local transaction identifier to the service subsystems corresponding to the at least one local transaction identifier, so that the at least one service subsystem performs correction processing on the abnormal transaction based on the received global transaction identifier and the corresponding local transaction identifier.
In one embodiment, the anomalous transaction detection module 501 further includes: the positive-going judging unit is used for acquiring at least one abnormal transaction; the initial abnormal transaction carries a transaction type; and determining abnormal transactions from at least one initial abnormal transaction according to the transaction types.
In one embodiment, the apparatus 500 further includes: the correcting control table module is used for configuring correcting parameters, bill types and correcting functions of all transaction types aiming at least one transaction type, obtaining and storing a correcting control table corresponding to each transaction type, and is used for correcting abnormal transactions; wherein the alignment parameter represents an alignment object; the bill type is used for determining a corresponding positive flow; the positive-going function is used to determine the corresponding positive-going computation logic.
In one embodiment, the apparatus 500 includes: the transaction identifier generation module is used for acquiring transaction request messages respectively corresponding to at least one exchange of at least one service subsystem aiming at each service subsystem in the at least one service subsystem; generating a global transaction identifier of a transaction in a core system server corresponding to the transaction request according to each transaction request message in at least one transaction request message; determining a business subsystem corresponding to each transaction in at least one transaction respectively, and generating local transaction identifiers corresponding to the at least one transaction respectively; and storing the generated global transaction identification and the local transaction identification into the registration information.
In one embodiment, the apparatus 500 includes: the system comprises a mirror image registration information module, a business subsystem and a business subsystem, wherein the mirror image registration information module is used for acquiring an SQL command corresponding to a target operation when the target operation of at least one business subsystem in transaction execution is detected; analyzing the SQL command to obtain transaction operation data of at least one business subsystem corresponding to the transaction; and storing the transaction operation data corresponding to at least one service subsystem as corresponding mirror image registration information according to the global transaction identifier and the at least one local transaction identifier.
In one embodiment, the apparatus 500 includes: the system comprises a forward-flushing abnormity early warning module, a forward-flushing abnormity early warning module and a forward-flushing abnormity early warning module, wherein the forward-flushing abnormity early warning module is used for detecting forward-flushing execution information of each service subsystem; if the forward flushing execution information indicates that the forward flushing processing is abnormal, generating early warning information containing the abnormal information, and sending the early warning information to an early warning terminal to trigger the forward flushing processing to be carried out again aiming at the abnormal transaction.
In one embodiment, as shown in fig. 6, there is provided a transaction data processing apparatus for use with a service subsystem, the service subsystem being in service communication with a core system, the apparatus 600 comprising:
a transaction identifier obtaining module 601, configured to obtain a global transaction identifier of an abnormal transaction sent by a core system server, and a local transaction identifier associated with the global transaction identifier; detecting the abnormal transaction by a core system server; the global transaction identifier is used for identifying abnormal transactions in the core system server, and the local transaction identifier is used for identifying abnormal transactions in the corresponding service subsystem;
the query module 602 is configured to query, according to the global transaction identifier and the local transaction identifier, mirror registration information and an alignment control table corresponding to the abnormal transaction;
the liquidation processing module 603 is used for carrying out liquidation processing on the abnormal transactions according to the mirror image registration information and the liquidation control table, and restoring the information corresponding to the abnormal transactions in the business subsystem to the state before transaction operation; the mirror image registration information comprises transaction operation data of a transaction related party before a transaction abnormal event occurs; and a correcting rule corresponding to the abnormal transaction is configured in the correcting control table.
In one embodiment, query module 602 includes: the mirror image registration information query unit is used for determining pre-registered mirror image registration information corresponding to the abnormal transaction according to the global transaction identifier and the local transaction identifier; and determining the transaction type of the abnormal transaction according to the global transaction identifier and the local transaction identifier, and determining a pre-configured reversal control table corresponding to the abnormal transaction according to the type of the abnormal transaction.
In one embodiment, the forward processing module 603 includes: the system comprises a back flushing unit, a service subsystem and a service subsystem, wherein the back flushing unit is used for acquiring transaction operation information of abnormal transactions corresponding to the service subsystem from mirror image registration information; and according to the conflict control table, the transaction operation information is restored to the state before the transaction operation in a reverse order according to the sequence of the transaction operation.
For the specific definition of the transaction data processing device, reference may be made to the above definition of the transaction data processing method, which is not described herein again. The various modules in the transaction data processing apparatus described above may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
The transaction data processing method provided by the application can be applied to a computer device, the computer device can be a server, and the internal structure diagram of the computer device can be as shown in fig. 7. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile 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 an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing data such as mirror image registration information, identification information and the like. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a transaction data processing method.
Those skilled in the art will appreciate that the architecture shown in fig. 7 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of the above-described method embodiments when executing the computer program.
In an embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (13)
1. A transaction data processing method applied to a core system server, the core system server being in communication connection with at least one service subsystem, the method comprising:
detecting abnormal transactions;
acquiring a global transaction identifier corresponding to the abnormal transaction and at least one local transaction identifier associated with the global transaction identifier; the global transaction identification is used for identifying the abnormal transaction in the core system server; the local transaction identifier is used for identifying the abnormal transaction in the corresponding service subsystem;
and sending the global transaction identifier and the at least one local transaction identifier to service subsystems corresponding to the at least one local transaction identifier respectively, so that the at least one service subsystem carries out correction processing on the abnormal transaction based on the received global transaction identifier and the corresponding local transaction identifier respectively.
2. The method of claim 1, wherein the detecting of the anomalous transaction comprises:
obtaining at least one initial anomalous transaction; the initial abnormal transaction carries a transaction type;
and determining the abnormal transaction from the at least one initial abnormal transaction according to the transaction type.
3. The method of claim 1, further comprising:
configuring a correcting parameter, a bill type and a correcting function of each transaction type aiming at least one transaction type to obtain a correcting control table corresponding to each transaction type and store the correcting control table for correcting the abnormal transaction;
wherein the straightening parameter characterizes a straightening object; the bill type is used for determining a corresponding positive flow; the positive-going function is used to determine the corresponding positive-going computation logic.
4. The method of claim 1, further comprising:
aiming at each service subsystem in the at least one service subsystem, acquiring transaction request messages respectively corresponding to at least one transaction of the service subsystem;
generating a global transaction identifier of a transaction corresponding to the transaction request in the core system server according to each transaction request message in the at least one transaction request message;
determining a business subsystem corresponding to each transaction in the at least one transaction respectively, and generating local transaction identifiers corresponding to the at least one transaction respectively;
and storing the generated global transaction identification and the local transaction identification into registration information.
5. The method of claim 4, further comprising:
when target operation of the at least one business subsystem in transaction execution is detected, acquiring an SQL command corresponding to the target operation;
analyzing the SQL command to obtain transaction operation data of the at least one business subsystem corresponding to the transaction;
and storing the transaction operation data corresponding to the at least one service subsystem as corresponding mirror image registration information according to the global transaction identifier and the at least one local transaction identifier.
6. The method according to any one of claims 1 to 5, further comprising:
detecting positive execution information of each service subsystem;
and if the forward flushing execution information indicates that the forward flushing processing is abnormal, generating early warning information containing abnormal information, and sending the early warning information to an early warning terminal to trigger the forward flushing processing to be carried out again aiming at the abnormal transaction.
7. A transaction data processing method applied to a service subsystem, wherein the service subsystem is in service communication connection with a core system, and the method comprises:
acquiring a global transaction identifier of an abnormal transaction sent by a core system server and a local transaction identifier associated with the global transaction identifier; the abnormal transaction is detected by the core system server; the global transaction identifier is used for identifying the abnormal transaction in the core system server, and the local transaction identifier is used for identifying the abnormal transaction in the corresponding service subsystem;
inquiring mirror image registration information and an alignment control table corresponding to the abnormal transaction according to the global transaction identifier and the local transaction identifier;
performing correction processing on the abnormal transaction according to the mirror image registration information and a correction control table, and recovering information corresponding to the abnormal transaction in the business subsystem to a state before transaction operation; the mirror image registration information comprises transaction operation data of a transaction related party before the transaction abnormal event occurs; and the conflict control table is configured with conflict rules corresponding to the abnormal transactions.
8. The method according to claim 7, wherein the querying the mirror registration information and the alignment control table corresponding to the abnormal transaction according to the global transaction identifier and the local transaction identifier comprises:
determining pre-registered mirror image registration information corresponding to the abnormal transaction according to the global transaction identifier and the local transaction identifier;
and determining the transaction type of the abnormal transaction according to the global transaction identifier and the local transaction identifier, and determining a pre-configured alignment control table corresponding to the abnormal transaction according to the type of the abnormal transaction.
9. The method according to claim 7, wherein the performing a transaction correction process on the abnormal transaction according to the mirror image registration information and a transaction correction control table to restore the information corresponding to the abnormal transaction in the local service subsystem to a state before a transaction operation includes:
acquiring transaction operation information of the abnormal transaction corresponding to the business subsystem from the mirror image registration information;
and according to the conflict control table, the transaction operation information is restored to the state before the transaction operation in a reverse order according to the sequence of the transaction operation.
10. A transaction data processing apparatus for use with a core system server, the core system server communicatively coupled to at least one service subsystem, the apparatus comprising:
the abnormal transaction detection module is used for detecting abnormal transactions;
the transaction identifier acquisition module is used for acquiring a global transaction identifier corresponding to the abnormal transaction and at least one local transaction identifier associated with the global transaction identifier; the global transaction identification is used for identifying the abnormal transaction in the core system server; the local transaction identifier is used for identifying the abnormal transaction in the corresponding service subsystem;
and the transaction identifier sending module is used for sending the global transaction identifier and the at least one local transaction identifier to the service subsystems corresponding to the at least one local transaction identifier respectively, so that the at least one service subsystem carries out correction processing on the abnormal transaction based on the received global transaction identifier and the corresponding local transaction identifier respectively.
11. A transaction data processing apparatus for use with a business subsystem, the business subsystem in communicative connection with a core system service, the apparatus comprising:
the transaction identifier acquisition module is used for acquiring a global transaction identifier of the abnormal transaction sent by the core system server and a local transaction identifier associated with the global transaction identifier; the abnormal transaction is detected by the core system server; the global transaction identifier is used for identifying the abnormal transaction in the core system server, and the local transaction identifier is used for identifying the abnormal transaction in the corresponding service subsystem;
the query module is used for querying mirror image registration information and a correction control table corresponding to the abnormal transaction according to the global transaction identifier and the local transaction identifier;
the correcting processing module is used for correcting the abnormal transaction according to the mirror image registration information and the correcting control table and restoring the information corresponding to the abnormal transaction in the business subsystem to the state before transaction operation; the mirror image registration information comprises transaction operation data of a transaction related party before the transaction abnormal event occurs; and the conflict control table is configured with conflict rules corresponding to the abnormal transactions.
12. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor realizes the steps of the method of any one of claims 1 to 9 when executing the computer program.
13. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011570641.2A CN112613993B (en) | 2020-12-26 | 2020-12-26 | Transaction data processing method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011570641.2A CN112613993B (en) | 2020-12-26 | 2020-12-26 | Transaction data processing method and device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112613993A true CN112613993A (en) | 2021-04-06 |
| CN112613993B CN112613993B (en) | 2022-08-12 |
Family
ID=75247958
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011570641.2A Active CN112613993B (en) | 2020-12-26 | 2020-12-26 | Transaction data processing method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112613993B (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113627890A (en) * | 2021-08-12 | 2021-11-09 | 神州数码融信软件有限公司 | Method for monitoring and processing abnormal flow in automatic approval flow |
| CN113744056A (en) * | 2021-09-07 | 2021-12-03 | 辽宁振兴银行股份有限公司 | Online transaction idempotent method and device |
| CN113837881A (en) * | 2021-09-28 | 2021-12-24 | 中电金信软件有限公司 | Transaction data updating method and device, electronic equipment and storage medium |
| CN114170007A (en) * | 2021-12-14 | 2022-03-11 | 中国建设银行股份有限公司 | Orthogonal easy return message assembly method, program product, medium, and electronic device |
| CN114218056A (en) * | 2021-12-07 | 2022-03-22 | 建信金融科技有限责任公司 | Performance test method and device of transaction system, computer equipment and storage medium |
| CN114500569A (en) * | 2022-01-27 | 2022-05-13 | 中国工商银行股份有限公司 | Data synchronization method, device, equipment and storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104794138A (en) * | 2014-01-22 | 2015-07-22 | 深圳市沃信科技有限公司 | Method, device and system for determining database transaction result |
| US20160048423A1 (en) * | 2014-08-14 | 2016-02-18 | Arm Limited | Transmission control checking for interconnect circuitry |
| CN107609793A (en) * | 2017-10-09 | 2018-01-19 | 税友软件集团股份有限公司 | A kind of method and device of process for producing transaction system abnormality |
| KR102020000B1 (en) * | 2018-10-31 | 2019-09-09 | 주식회사 스위클 | Personal information providing system using one time private key based on block chain of proof of use and method thereof |
| CN111259083A (en) * | 2020-02-13 | 2020-06-09 | 神州数码融信软件有限公司 | Distributed transaction processing method and device |
| CN111369350A (en) * | 2020-03-31 | 2020-07-03 | 中国建设银行股份有限公司 | Orthogonal punching easy processing method and device |
| CN111626858A (en) * | 2020-05-28 | 2020-09-04 | 北京金山云网络技术有限公司 | Processing method and device for transaction, electronic equipment and computer readable medium |
| CN111651244A (en) * | 2020-07-01 | 2020-09-11 | 中国银行股份有限公司 | Processing system for distributed transactions |
| CN112131305A (en) * | 2020-06-19 | 2020-12-25 | 中信银行股份有限公司 | Account processing system |
-
2020
- 2020-12-26 CN CN202011570641.2A patent/CN112613993B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104794138A (en) * | 2014-01-22 | 2015-07-22 | 深圳市沃信科技有限公司 | Method, device and system for determining database transaction result |
| US20160048423A1 (en) * | 2014-08-14 | 2016-02-18 | Arm Limited | Transmission control checking for interconnect circuitry |
| CN107609793A (en) * | 2017-10-09 | 2018-01-19 | 税友软件集团股份有限公司 | A kind of method and device of process for producing transaction system abnormality |
| KR102020000B1 (en) * | 2018-10-31 | 2019-09-09 | 주식회사 스위클 | Personal information providing system using one time private key based on block chain of proof of use and method thereof |
| CN111259083A (en) * | 2020-02-13 | 2020-06-09 | 神州数码融信软件有限公司 | Distributed transaction processing method and device |
| CN111369350A (en) * | 2020-03-31 | 2020-07-03 | 中国建设银行股份有限公司 | Orthogonal punching easy processing method and device |
| CN111626858A (en) * | 2020-05-28 | 2020-09-04 | 北京金山云网络技术有限公司 | Processing method and device for transaction, electronic equipment and computer readable medium |
| CN112131305A (en) * | 2020-06-19 | 2020-12-25 | 中信银行股份有限公司 | Account processing system |
| CN111651244A (en) * | 2020-07-01 | 2020-09-11 | 中国银行股份有限公司 | Processing system for distributed transactions |
Non-Patent Citations (2)
| Title |
|---|
| A. TARALEKAR, G.等: ""One touch multi-banking transaction ATM system using biometric and GSM authentication"", 《 2017 INTERNATIONAL CONFERENCE ON BID》 * |
| 王新立: ""面向交易中间件的分布式事务设计与实现"", 《中国优秀博硕士学位论文全文数据库(硕士)信息科技辑》 * |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113627890A (en) * | 2021-08-12 | 2021-11-09 | 神州数码融信软件有限公司 | Method for monitoring and processing abnormal flow in automatic approval flow |
| CN113627890B (en) * | 2021-08-12 | 2024-04-02 | 神州数码融信软件有限公司 | Method for monitoring and processing abnormal flow in automatic approval flow |
| CN113744056A (en) * | 2021-09-07 | 2021-12-03 | 辽宁振兴银行股份有限公司 | Online transaction idempotent method and device |
| CN113837881A (en) * | 2021-09-28 | 2021-12-24 | 中电金信软件有限公司 | Transaction data updating method and device, electronic equipment and storage medium |
| CN113837881B (en) * | 2021-09-28 | 2023-02-28 | 中电金信软件有限公司 | Transaction data updating method and device, electronic equipment and storage medium |
| CN114218056A (en) * | 2021-12-07 | 2022-03-22 | 建信金融科技有限责任公司 | Performance test method and device of transaction system, computer equipment and storage medium |
| CN114218056B (en) * | 2021-12-07 | 2024-06-25 | 建信金融科技有限责任公司 | Performance test method and device for transaction system, computer equipment and storage medium |
| CN114170007A (en) * | 2021-12-14 | 2022-03-11 | 中国建设银行股份有限公司 | Orthogonal easy return message assembly method, program product, medium, and electronic device |
| CN114500569A (en) * | 2022-01-27 | 2022-05-13 | 中国工商银行股份有限公司 | Data synchronization method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112613993B (en) | 2022-08-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112613993B (en) | Transaction data processing method and device, computer equipment and storage medium | |
| CN110290212B (en) | Service call recording method, device, computer equipment and storage medium | |
| CN109614262B (en) | Service checking method, device and computer readable storage medium | |
| CN108647357B (en) | Data query method and device | |
| CN108595505B (en) | Data query method and device | |
| CN108924258B (en) | Background information pushing method and device, computer equipment and storage medium | |
| US20220092224A1 (en) | Data management system with tamper-evidence | |
| CN111782456B (en) | Anomaly detection method, device, computer equipment and storage medium | |
| CN113238815A (en) | Interface access control method, device, equipment and storage medium | |
| CN113779545A (en) | Data cross-process sharing method, terminal equipment and computer readable storage medium | |
| CN112783866B (en) | Data reading method, device, computer equipment and storage medium | |
| CN113360210A (en) | Data reconciliation method and device, computer equipment and storage medium | |
| CN111522881B (en) | Service data processing method, device, server and storage medium | |
| CN111291063B (en) | Master and backup copy election method, system, computer equipment and storage medium | |
| CN112711606A (en) | Database access method and device, computer equipment and storage medium | |
| CN110543465B (en) | Directory operation method and device, computer equipment and storage medium | |
| CN116010926A (en) | Login authentication method, login authentication device, computer equipment and storage medium | |
| CN114116253A (en) | Message processing method and system for message queue | |
| CN109240906B (en) | Database configuration information adaptation method and device, computer equipment and storage medium | |
| US8321844B2 (en) | Providing registration of a communication | |
| CN117234738B (en) | Block chain system based on artificial intelligent model and intelligent contract processing method | |
| CN117112368B (en) | Abnormality processing method, abnormality processing device, electronic equipment and storage medium | |
| CN112306551B (en) | Historical configuration information acquisition method, system and device | |
| US20230359725A1 (en) | Methods and systems for monitoring the behavior of a process | |
| CN113590642A (en) | Data updating method and device, electronic equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |