CN109491766B - Method, device and system for delivering transaction message and message server - Google Patents
Method, device and system for delivering transaction message and message server Download PDFInfo
- Publication number
- CN109491766B CN109491766B CN201811182007.4A CN201811182007A CN109491766B CN 109491766 B CN109491766 B CN 109491766B CN 201811182007 A CN201811182007 A CN 201811182007A CN 109491766 B CN109491766 B CN 109491766B
- Authority
- CN
- China
- Prior art keywords
- state
- transaction
- transaction message
- submission
- message
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/466—Transaction processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a method, a device and a system for delivering transaction messages and a message server, wherein the method for delivering the transaction messages comprises the following steps: receiving a review request sent by a message server for a transaction message, wherein the review request comprises: a status change record of the object; acquiring a state submission record of the object; determining a retrieval result according to the state change record and the state submission record; and sending the result of the inquiry to the message server so that the message server determines whether to deliver the transaction message according to the result of the inquiry.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method, an apparatus, a system, and a message server for delivering a transaction message.
Background
A transaction is composed of an action of sending a message and a sender business logic action. The sending of the transaction message comprises two phases: the first phase is to send a transaction message to the message server; the second phase is to send the transaction state to the message server, which will post the transaction message to the subscriber if the transaction state is commit, and will cancel the post transaction message if the transaction state is rollback.
However, due to poor network signals, etc., the second phase often cannot be implemented, i.e., the message server cannot receive the transaction status.
In view of this, the message server will check back the transaction message to confirm whether the transaction message is delivered. How to improve the accuracy of the review and the delivery efficiency of the transaction message is a problem that technicians pay attention to the method all the time.
Disclosure of Invention
In view of this, the embodiment of the present invention provides a method, an apparatus, a system and a message server for delivering a transaction message.
In a first aspect, an embodiment of the present invention provides a method for delivering a transaction message, including:
receiving a review request sent by a message server for a transaction message, wherein the review request comprises: a status change record of the object;
acquiring a state submission record of the object;
determining a retrieval result according to the state change record and the state submission record;
and sending the result of the inquiry to the message server so that the message server determines whether to deliver the transaction message according to the result of the inquiry.
Preferably, the first and second electrodes are formed of a metal,
the state change record includes: the state after the 1 st change is changed to the state after the M time change;
the state commit record includes: the state after the 1 st submission is changed to the state after the Nth submission;
wherein M, N is an integer greater than 1;
the determining a result of the review according to the state change record and the state submission record includes:
and determining whether the state after each change in the state change record is the same as the state after each submission in the state submission record, if so, determining that the rechecking result is the delivery of the transaction message, and otherwise, determining that the rechecking result is the non-delivery of the transaction message.
Preferably, the first and second electrodes are formed of a metal,
the state change record includes: a first state to a current state;
wherein the first state to the current state are changed states corresponding to E times of continuous changes; from the first change, F changes are needed when the object reaches the current state, and F is larger than E;
the state commit record includes: the state after the 1 st submission is changed to the state after the H-th submission;
when A, B, C, D does not exist, so that the state after A submission to the state after B submission and the state after C submission to the state after D submission are the same as the state from the first state to the current state,
the determining a result of the review according to the state change record and the state submission record includes:
determining Q, S whether the status after Q time submission to S time submission is the same as the status from the first status to the current status, if so, determining that the result of the recheck is to deliver the transaction message, otherwise, determining that the result of the recheck is not to deliver the transaction message.
Preferably, the first and second electrodes are formed of a metal,
before the receiving the request for the reply sent by the message server for the transaction message, further comprising:
starting a transaction;
changing the state of the object according to the transaction;
determining the state change record according to the state of the changed object;
sending the transaction message to the message server, wherein the transaction message comprises: the state change record.
Preferably, the first and second electrodes are formed of a metal,
after the sending the transaction message to the message server, before the receiving a response request sent by the message server for the transaction message, further comprising:
and determining whether the transaction is executed, if so, committing the transaction, updating the state commit record, and otherwise, rolling back the transaction.
Preferably, the first and second electrodes are formed of a metal,
the state change record includes: the state after the 1 st change is changed to the state after the R-th change;
the state commit record includes: the state after the 1 st submission is changed to the state after the T-th submission;
wherein R, T is an integer greater than 1;
the determining a result of the review according to the state change record and the state submission record includes:
determining whether the R changed states are all the same as the corresponding order of committed states, and if so,
determining whether K exists so that the state after the K submission is the same as the state after the R change, and R < K is less than or equal to T, if so,
and determining that the back check result is that the transaction message is not delivered.
In a second aspect, an embodiment of the present invention provides a method for delivering a transaction message, including:
sending a check request back to a delivery device of the transaction message for the transaction message, wherein the check request comprises: the state change record of the object, so that the delivery device of the transaction message determines the result of the retrieval according to the state change record;
receiving the response result sent by the delivery device of the transaction message;
and determining whether to deliver the transaction message according to the checking result.
Preferably, the first and second electrodes are formed of a metal,
before the sending back a check request to a delivery device of a transaction message for the transaction message, further comprising:
the transaction message sent by a delivery device receiving the transaction message, wherein the transaction message comprises: the state change record.
Preferably, the first and second electrodes are formed of a metal,
after the transaction message sent by the delivery device receiving the transaction message, before sending a check request back to the delivery device of transaction message for the transaction message, further comprising:
determining a time interval between the current time and the time of receiving the transaction message;
when the time interval is larger than a preset time threshold and the transaction state for the transaction message is sent by the delivery device which does not receive the transaction message within the time interval, executing the transmission request for the transaction message back to the delivery device of the transaction message;
wherein the transaction state comprises: commit, or rollback.
Preferably, the first and second electrodes are formed of a metal,
the determining whether to deliver the transaction message according to the result of the check includes:
when the rechecking result is that the transaction message is delivered, delivering the transaction message;
or the like, or, alternatively,
the determining whether to deliver the transaction message according to the result of the check includes:
and when the rechecking result is that the transaction message is not delivered, deleting the transaction message.
In a third aspect, an embodiment of the present invention provides a device for delivering a transaction message, including:
a receiving unit, configured to receive a review request sent by a message server for a transaction message, where the review request includes: a status change record of the object;
the acquisition unit is used for acquiring the state submission record of the object;
the determining unit is used for determining a retrieval result according to the state change record and the state submission record;
and the sending unit is used for sending the inquiry result to the message server so that the message server determines whether to deliver the transaction message according to the inquiry result.
Preferably, the first and second electrodes are formed of a metal,
the state change record includes: the state after the 1 st change is changed to the state after the M time change;
the state commit record includes: the state after the 1 st submission is changed to the state after the Nth submission;
wherein M, N is an integer greater than 1;
and the determining unit is used for determining whether the M changed states are the same as the states after the submission of the corresponding sequence, if so, determining that the rechecking result is the delivery of the transaction message, and otherwise, determining that the rechecking result is the non-delivery of the transaction message.
Preferably, the first and second electrodes are formed of a metal,
the state change record includes: the target state and the current state obtained after the target state is changed for one time;
the state commit record includes: the state after the 1 st submission is changed to the state after the H-th submission;
when the number of the same post-commit states as the current state is greater than 1 and the kind of the repeatedly occurring post-commit states is less than 2,
the determining unit is configured to determine whether a G exists, so that a state after the G-1 st submission is the same as the target state and a state after the G-th submission is the same as the current state, if so, determine that the review result is to deliver the transaction message, otherwise, determine that the review result is not to deliver the transaction message;
wherein H, G is an integer greater than 1, and G is greater than 1 and less than or equal to H.
Preferably, the first and second electrodes are formed of a metal,
further comprising:
a change unit for opening a transaction; changing the state of the object according to the transaction; determining the state change record according to the state of the changed object; sending the transaction message to the message server, wherein the transaction message comprises: the state change record.
Preferably, the first and second electrodes are formed of a metal,
the change unit is further used for determining whether the transaction is executed, if so, submitting the transaction and updating the state submission record, otherwise, rolling back the transaction.
Preferably, the first and second electrodes are formed of a metal,
the state change record includes: the state after the 1 st change is changed to the state after the R-th change;
the state commit record includes: the state after the 1 st submission is changed to the state after the T-th submission;
wherein R, T is an integer greater than 1;
and the determining unit is used for determining whether the R changed states are the same as the states after the submission in the corresponding sequence, if so, determining whether K exists, so that the state after the K submission is the same as the state after the R change, and R < K is less than or equal to T, and if so, determining that the recheck result is that the transaction message is not delivered.
In a fourth aspect, an embodiment of the present invention provides a message server, including:
a sending unit, configured to send a check request to a delivery device of a transaction message for the transaction message, where the check request includes: the state change record of the object, so that the delivery device of the transaction message determines the result of the retrieval according to the state change record;
a first receiving unit, configured to receive the result of the check sent by the delivery apparatus of the transaction message;
a first determining unit, configured to determine whether to deliver the transaction message according to the result of the check.
Preferably, the first and second electrodes are formed of a metal,
further comprising:
a second receiving unit, configured to receive the transaction message sent by the delivery device of the transaction message, where the transaction message includes: the state change record.
Preferably, the first and second electrodes are formed of a metal,
further comprising:
a second determining unit, configured to determine a time interval between a current time and a time when the transaction message is received; when the time interval is larger than a preset time threshold and the transaction state aiming at the transaction message is sent by a delivery device which does not receive the transaction message in the time interval, triggering the sending unit;
wherein the transaction state comprises: commit, or rollback.
Preferably, the first and second electrodes are formed of a metal,
the first determining unit is used for delivering the transaction message when the response result is that the transaction message is delivered;
or the like, or, alternatively,
the first determining unit is configured to delete the transaction message when the review result is that the transaction message is not delivered.
In a fifth aspect, an embodiment of the present invention provides a system for delivering a transaction message, including: the device for delivering the transaction message according to any embodiment and the message server according to any embodiment.
The embodiment of the invention adopts at least one technical scheme which can achieve the following beneficial effects: the corresponding back check logic of the delivery method of the transaction message is simple, and only the judgment of the state change record of the object and the state submission record of the object is involved. No matter how the state machine circulation relationship changes, the back check logic is kept unchanged, the maintenance cost is low, and the accuracy is higher.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a flow chart of a method for delivering a transaction message according to an embodiment of the present invention;
FIG. 2 is a block diagram of a state machine according to an embodiment of the present invention;
FIG. 3 is a flow chart of a method for delivering a transaction message according to another embodiment of the present invention;
FIG. 4 is a flow chart of a method for delivering a transaction message according to another embodiment of the present invention;
FIG. 5 is a flow chart of a method for delivering a transaction message according to another embodiment of the invention;
FIG. 6 is a schematic structural diagram of a device for delivering transaction messages according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a message server according to an embodiment of the present invention;
FIG. 8 is a diagram illustrating a structure of a system for delivering transaction messages according to an embodiment of the present invention;
fig. 9 is a flowchart of another transaction message delivery method according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer and more complete, the technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention, and based on the embodiments of the present invention, all other embodiments obtained by a person of ordinary skill in the art without creative efforts belong to the scope of the present invention.
As shown in fig. 1, an embodiment of the present invention provides a method for delivering a transaction message, which is applied to a device for delivering a transaction message, and the method may include the following steps:
step 101: receiving a review request sent by a message server for a transaction message, wherein the review request comprises: a status change record of the object.
The request for checking back may be the transaction message itself, or may be a request carrying the transaction message identifier. The state change record of the object records the change process of the state of the object, wherein the change process comprises at least two changed states of the object, and the object can be a transaction list, a reimbursement list and the like.
In an actual application scenario, the state change record of the object may be represented by a state machine, and the state machine may learn the transition of each state of the object in the life cycle.
As shown in fig. 2, is a state machine corresponding to the transaction order. As can be seen from FIG. 2, the change process of the status from creation to completion of the transaction order is "A → B → C → D → B → C → E", and the status change record of the object can be "ABCDBCE".
Further, the reply request may also include a state of an object corresponding to the transaction message.
It should be noted that the transaction order is treated as a change from creation to state a.
Step 102: and acquiring a state submission record of the object.
A state commit record of the object is obtained from the database, the state commit record recording a commit process of the state of the object. Similar to the state change records, the state commit records may also be represented by a state machine.
Step 103: and determining a retrieval result according to the state change record and the state submission record.
Step 104: and sending the rechecking result to the message server so that the message server determines whether to deliver the transaction message according to the rechecking result.
The method has simple rechecking logic and only relates to the judgment of the state change record of the object and the state submission record of the object. No matter how the state circulation relation of the object changes, the back check logic of the method is kept unchanged, the maintenance cost is low, and the method has high accuracy.
Step 103 can be implemented in at least two ways:
mode 1:
in one embodiment of the invention, the state change record comprises: the state after the 1 st change is changed to the state after the M time change;
the state commit record includes: the state after the 1 st submission is changed to the state after the Nth submission;
wherein M, N is an integer greater than 1;
step 103 comprises:
and determining whether the M changed states are the same as the states after the submission in the corresponding sequence, if so, determining that the result of the check is the delivery transaction message, and otherwise, determining that the result of the check is the non-delivery transaction message.
For example, if the state of the object is represented by an english letter, and if M is 4, the state after the first change is a, the state after the second change is B, the state after the third change is C, and the state after the fourth change is D, the state change record may be "ABCD", may also be "DCBA", and may also be "CABD".
It can be seen from this that the states after change in the state change record are not necessarily arranged in the order of change from front to back, but may follow other rules. The status commit record is similar and will not be described in detail herein.
It should be noted that, in this method, the state change record and the state commit record need to follow the same rule. For example, if the state after the first commit is a, the state after the second commit is B, the state after the third commit is C, and the state after the fourth commit is E, the state commit record is "ABCE", and, following the above example, the state change record is "ABCD". If the status commit record is "DCBA", the status change record is "ECBA".
Wherein the transaction message corresponds to the state after the mth change. For example, the state change records are arranged in sequence from front to back according to the change sequence, and the state change record contained in the transaction message is "ABCDEF" corresponding to the object changed from the state E to the state F; the state change record contained in the transaction message is "ABCD" which corresponds to the object changing from state C to state D.
In an embodiment of the invention, the review result comprises "deliver transaction message or not deliver transaction message". In an actual application scenario, the query result may further include "the transaction state is commit or the transaction state is rollback", and may further include "the M changed states are all the same as the committed states in the corresponding order or the M changed states are not all the same as the committed states in the corresponding order".
Since the state change record includes the state after the 1 st change to the state after the M-th change (the transaction message corresponds to the M-th change), the method 1 can avoid a result of the retrieval error due to the state loop change of the object.
Mode 2:
in order to reduce the impact of the state change record being too long due to the multiple changes of the state of the object on the transmission process of the query request, in one embodiment of the invention,
the state change record includes: a first state to a current state;
wherein the first state to the current state are changed states corresponding to E times of continuous changes; from the first change, F changes are needed when the object reaches the current state, and F is larger than E;
the state commit record includes: the state after the 1 st submission is changed to the state after the H-th submission;
when A, B, C, D does not exist, the state after A submission to the state after B submission and the state after C submission to the state after D submission are the same as the state from the first state to the current state,
determining a recall result according to the state change record and the state submission record, comprising:
determining Q, S whether the status after Q time submission to S time submission is the same as the status from the first status to the current status, if so, determining the result of the check as a delivery transaction message, otherwise, determining the result of the check as a non-delivery transaction message.
For example, since the status change record is "DC", the status change record is "abcdccefc", and "DC" does not appear repeatedly in the status change record, the determination can be made by this method. In the present embodiment, Q-4 and S-5 are present.
In the method 2, in order to increase the transmission speed of the search request, the state change record does not need to include all the states of the object before the current state. However, the partial state of the object before the current state contained in the state change record should ensure the accuracy of the review.
In the embodiment of the present invention, the status change record may be "CDC", "BCDC", or the like, and the review result is the same as that in the case where the status change record is "DC".
In one embodiment of the present invention, before receiving a query request sent by a message server for a transaction message, the method further comprises:
starting a transaction;
changing the state of the object according to the transaction;
determining a state change record according to the state of the changed object;
sending a transaction message to a message server, wherein the transaction message comprises: and (6) recording the state change.
Referring to fig. 2, taking the change of the object from the state B to the state C as an example, the states of the object may be spliced to obtain the state change record according to the sequence of the change. Based on this, after the change, the state change record is "ABC". In the case of different methods, corresponding to the above-described methods 1 and 2, there may be a difference in the corresponding status change records.
In one embodiment of the invention, after sending the transaction message to the message server, before receiving a response request sent by the message server for the transaction message, the method comprises the following steps:
determining whether the transaction is executed, if so, committing the transaction, updating the state commit record, otherwise, rolling back the transaction.
Whether the transaction is executed, i.e., whether the change is complete, and if so, the transaction needs to be committed locally and the state commit record stored in the database is updated. For example, the object is changed from state B to state C, the state commit record is changed to "ABC" when the object is committed locally, and if the transaction is not executed, the state commit record is still "AB".
To avoid delivering duplicate transaction messages, in one embodiment of the invention, the state change record includes: the state after the 1 st change is changed to the state after the R-th change;
the state commit record includes: the state after the 1 st submission is changed to the state after the T-th submission;
wherein R, T is an integer greater than 1;
determining a recall result according to the state change record and the state submission record, comprising:
determining whether the R changed states are all the same as the corresponding order of committed states, and if so,
determining whether K exists so that the state after the K submission is the same as the state after the R change, and R < K is less than or equal to T, if so,
and determining that the result of the check is a non-delivery transaction message.
For example, the status change record is "ABCD" and the status commit record is "ABCDBCD", wherein the status after 1 st to 4 th changes is the same as the status after 1 st to 4 th commits, respectively, and according to the foregoing embodiment, the reply result should be determined to be a delivery transaction message. However, considering that state D occurs later, in order to reduce the impact of repeated delivery on the subscribing user, in the embodiment of the present invention, the recheck result is determined as a non-delivery transaction message. For example, the state D has a problem with the account, and the user is notified by a transaction message without repeated notification.
As shown in fig. 3, the embodiment of the present invention takes equation 1 as an example to describe in detail a method for delivering a transaction message, where the method includes:
step 301: the transaction is opened.
Taking the change from state C to state D in the state machine shown in fig. 2 as an example, the object is to change the state of an object from C to D.
Step 302: the state of the object is changed according to the transaction.
Step 303: and determining a state change record according to the state of the changed object.
The status change record is determined to be "ABCD".
Step 304: sending a transaction message to a message server, wherein the transaction message comprises: and (6) recording the state change.
Step 305: it is determined whether the transaction is to be executed, if so, step 306 is performed, otherwise, step 307 is performed.
Step 306: the transaction is committed, the state commit record is updated, and step 308 is performed.
After the transaction completes the local commit, the state commit record is changed to "ABCD".
Step 307: the transaction is rolled back.
When the transaction rolls back, it is stated that the state of the object is still C and the state commit record is "ABC".
Step 308: receiving a review request sent by a message server for a transaction message, wherein the review request comprises: a status change record of the object; the state change record includes: the state after the 1 st change is changed to the state after the M time change, wherein M is an integer larger than 1.
Step 309: obtaining a state commit record of an object, wherein the state commit record comprises: the state after the 1 st submission to the state after the Nth submission, wherein N is an integer greater than 1. .
Step 310: and determining whether the state after each change in the state change record is the same as the state after each submission in the state submission record, if so, executing step 311, otherwise, executing step 312.
When the transaction commits, step 311 is performed, and when the transaction rolls back, step 312 is performed.
Step 311: the result of the reply is determined to be a posted transaction message and step 313 is performed.
Step 312: and determining that the result of the check is a non-delivery transaction message.
Step 313: and sending the rechecking result to the message server so that the message server determines whether to deliver the transaction message according to the rechecking result.
As shown in fig. 4, an embodiment of the present invention provides a method for delivering a transaction message, which is applied to a message server, and includes:
step 401: sending a check request back to a delivery device of the transaction message for the transaction message, wherein the check request comprises: the state change record of the object, so that the delivery device of the transaction message determines the result of the retrieval according to the state change record;
step 402: receiving a check-back result sent by a delivery device of the transaction message;
step 403: and determining whether to deliver the transaction message according to the check result.
According to the method, the state change record of the object is added in the retrieval request, so that the retrieval logic is kept unchanged no matter how the state flow relation of the object changes, the maintenance cost is low, and the accuracy is higher.
It should be noted that, the method for delivering the transaction message applied to the message server side corresponds to the method for delivering the transaction message applied to the transaction message delivery device side, and the description of the method for delivering the transaction message applied to the transaction message delivery device side in the foregoing embodiment is also applicable to the method for delivering the transaction message applied to the message server side, and details are not repeated below.
In one embodiment of the present invention, before sending the check request back to the delivery device of the transaction message for the transaction message, further comprising:
the transaction message is sent by a delivery device which receives the transaction message, wherein the transaction message comprises: and (6) recording the state change.
When a check-back request for a transaction message is sent, the corresponding transaction message may be directly sent to the delivery device of the transaction message in the form of the check-back request.
In an actual application scenario, after a transaction message is received, a transaction state for the transaction message may not be received for a long time, so that the transaction message cannot be processed in time, and the whole service process is affected.
To address the above, in one embodiment of the invention, before the transaction message is sent by the delivery device receiving the transaction message and the request is sent back to the delivery device of the transaction message for the transaction message, the method further comprises:
determining a time interval between the current time and the time of receiving the transaction message;
when the time interval is larger than a preset time threshold and the transaction state aiming at the transaction message is sent by the delivery device which does not receive the transaction message within the time interval, executing to send a check request aiming at the transaction message to the delivery device of the transaction message;
wherein the transaction state comprises: commit, or rollback.
When the transaction state of the received transaction message is commit, the transaction message is delivered to the user subscribed to the transaction message, and when the transaction state of the received transaction message is rollback, the transaction message can be deleted.
In one embodiment of the invention, determining whether to deliver the transaction message based on the result of the check comprises:
when the rechecking result is the delivery transaction message, delivering the transaction message;
in one embodiment of the invention, determining whether to deliver the transaction message based on the result of the check comprises:
and when the check-back result is that the transaction message is not delivered, deleting the transaction message.
In addition, when the check-back result is that the transaction message is not delivered, the transaction message can be marked or put aside.
In one embodiment of the present invention, as shown in fig. 5, a method for delivering a transaction message includes:
step 501: the transaction message is sent by a delivery device which receives the transaction message, wherein the transaction message comprises: and (6) recording the state change.
Step 502: determining a time interval between the current time and the time when the transaction message is received, and executing step 503 when the time interval is greater than a preset time threshold and a transaction state for the transaction message is sent by a delivery device which does not receive the transaction message within the time interval, wherein the transaction state includes: commit, or rollback.
Step 503: sending a check request back to a delivery device of the transaction message for the transaction message, wherein the check request comprises: the status change record of the object so that the delivery device of the transaction message determines the result of the review based on the status change record.
Step 504: and if the result of the check back sent by the delivery device receiving the transaction message is the delivery transaction message, executing step 505, and if the result of the check back is the non-delivery transaction message, executing step 506.
Step 505: and delivering the transaction message.
Step 506: the transaction message is deleted.
As shown in fig. 6, an embodiment of the present invention provides a device for delivering a transaction message, including:
a receiving unit 601, configured to receive a query request sent by a message server for a transaction message, where the query request includes: a status change record of the object;
an obtaining unit 602, configured to obtain a status submission record of an object;
a determining unit 603, configured to determine a result of the review according to the state change record and the state submission record;
a sending unit 604, configured to send the review result to the message server, so that the message server determines whether to deliver the transaction message according to the review result.
In one embodiment of the invention, the state change record comprises: the state after the 1 st change is changed to the state after the M time change;
the state commit record includes: the state after the 1 st submission is changed to the state after the Nth submission;
wherein M, N is an integer greater than 1;
a determining unit 603, configured to determine whether the state after each change in the state change record is the same as the state after each commit in the state commit record, if so, determine that the result of the query is a delivery transaction message, otherwise, determine that the result of the query is a non-delivery transaction message.
In one embodiment of the invention, the state change record comprises: a first state to a current state;
wherein the first state to the current state are changed states corresponding to E times of continuous changes; from the first change, F changes are needed when the object reaches the current state, and F is larger than E;
the state commit record includes: the state after the 1 st submission is changed to the state after the H-th submission;
when A, B, C, D does not exist, the state after A submission to the state after B submission and the state after C submission to the state after D submission are the same as the state from the first state to the current state,
a determining unit 603, configured to determine Q, S whether the status after the qth commit to the status after the S commit is the same as the status from the first status to the current status, if so, determine that the result of the query is a delivery transaction message, otherwise, determine that the result of the query is a non-delivery transaction message.
In one embodiment of the invention, the apparatus further comprises:
a change unit for opening a transaction; changing the state of the object according to the transaction; determining a state change record according to the state of the changed object; sending a transaction message to a message server, wherein the transaction message comprises: and (6) recording the state change.
In an embodiment of the invention, the change unit is further configured to determine whether a transaction is executed, if so, commit the transaction, update the state commit record, otherwise, roll back the transaction.
In one embodiment of the invention, the state change record comprises: the state after the 1 st change is changed to the state after the R-th change;
the state commit record includes: the state after the 1 st submission is changed to the state after the T-th submission;
wherein R, T is an integer greater than 1;
a determining unit 603, configured to determine whether the R changed states are all the same as the states after submission in the corresponding sequence, and if so, determine whether K exists, so that the state after the kth submission is the same as the state after the R change, and R < K is less than or equal to T, and if so, determine that the result of the query is that no transaction message is delivered.
As shown in fig. 7, an embodiment of the present invention provides a message server, including:
a sending unit 701, configured to send a query request to a delivery device of a transaction message for the transaction message, where the query request includes: the state change record of the object, so that the delivery device of the transaction message determines the result of the retrieval according to the state change record;
a first receiving unit 702, configured to receive a review result sent by a delivery apparatus of a transaction message;
a first determining unit 703, configured to determine whether to deliver the transaction message according to the result of the check.
In one embodiment of the present invention, the message server further comprises:
a second receiving unit, configured to receive a transaction message sent by a delivery apparatus of the transaction message, where the transaction message includes: and (6) recording the state change.
In one embodiment of the present invention, the message server further comprises:
a second determining unit, configured to determine a time interval between the current time and the time when the transaction message is received; when the time interval is larger than a preset time threshold and the transaction state aiming at the transaction message is sent by the delivery device which does not receive the transaction message in the time interval, triggering the sending unit;
wherein the transaction state comprises: commit, or rollback.
In an embodiment of the invention, the first determining unit 703 is configured to deliver the transaction message when the review result is the delivery transaction message.
In an embodiment of the invention, the first determining unit 703 is configured to delete the transaction message when the result of the check is that the transaction message is not delivered.
As shown in fig. 8, an embodiment of the present invention provides a system for delivering a transaction message, including: a transaction message delivery device 801 of any of the above embodiments and a message server 802 of any of the above embodiments.
As shown in fig. 9, the embodiment of the present invention takes a delivery system of a transaction message as an example, and describes in detail a delivery method of a transaction message, including:
step 901: the message server sends a check request back to the delivery device of the transaction message for the transaction message.
Step 902: the delivery device of the transaction message receives a review request, wherein the review request comprises: a status change record of the object.
Step 903: the delivery device of the transaction message obtains a status commit record for the object.
Step 904: and the delivery device of the transaction message determines the rechecking result according to the state change record and the state submission record and sends the rechecking result to the message server.
Step 905: and the message server receives the rechecking result and determines whether to deliver the transaction message according to the rechecking result.
In the system, the state change record of the object is introduced, so that the back check logic of the transaction message is simple and clear. When the state of the object changes in the flow relationship, the lookback logic does not require additional maintenance. The system can enable the state change of the object to be traceable, improves readability, and has stronger expansion capability.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. The use of the phrase "including a" does not exclude the presence of other, identical elements in the process, method, article, or apparatus that comprises the same element, whether or not the same element is present in all of the same element.
The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (21)
1. A method for delivering transaction messages, comprising:
receiving a review request sent by a message server for a transaction message, wherein the review request comprises: a state change record used for recording the change process of the state of an object, wherein the state change record comprises the changed state of the object; the object is a business object processed by the transaction message;
acquiring a state submission record of a submission process for recording the state of the object, wherein the state submission record comprises the submitted state of the object;
determining a retrieval result according to the state change record and the state submission record;
and sending the result of the inquiry to the message server so that the message server determines whether to deliver the transaction message according to the result of the inquiry.
2. The method for delivering transaction messages according to claim 1,
the state change record includes: the state after the 1 st change is changed to the state after the M time change;
the state commit record includes: the state after the 1 st submission is changed to the state after the Nth submission;
wherein M, N is an integer greater than 1;
the determining a result of the review according to the state change record and the state submission record includes:
and determining whether the state after each change in the state change record is the same as the state after each submission in the state submission record, if so, determining that the rechecking result is the delivery of the transaction message, and otherwise, determining that the rechecking result is the non-delivery of the transaction message.
3. The method for delivering transaction messages according to claim 1,
the state change record includes: a first state to a current state;
wherein the first state to the current state are changed states corresponding to E times of continuous changes; from the first change, F changes are needed when the object reaches the current state, and F is larger than E;
the state commit record includes: the state after the 1 st submission is changed to the state after the H-th submission;
when A, B, C, D does not exist, so that the state after A submission to the state after B submission and the state after C submission to the state after D submission are the same as the state from the first state to the current state,
the determining a result of the review according to the state change record and the state submission record includes:
determining Q, S whether the status after Q time submission to S time submission is the same as the status from the first status to the current status, if so, determining that the result of the recheck is to deliver the transaction message, otherwise, determining that the result of the recheck is not to deliver the transaction message.
4. The method for delivering transaction messages according to claim 1, further comprising, before the receiving the response request sent by the message server for the transaction message:
starting a transaction;
changing the state of the object according to the transaction;
determining the state change record according to the state of the changed object;
sending the transaction message to the message server, wherein the transaction message comprises: the state change record.
5. The method for delivering transaction messages according to claim 4, after the sending the transaction message to the message server, before the receiving the response request sent by the message server for the transaction message, further comprising:
and determining whether the transaction is executed, if so, committing the transaction, updating the state commit record, and otherwise, rolling back the transaction.
6. The method for delivering transaction messages according to claim 1,
the state change record includes: the state after the 1 st change is changed to the state after the R-th change;
the state commit record includes: the state after the 1 st submission is changed to the state after the T-th submission;
wherein R, T is an integer greater than 1;
the determining a result of the review according to the state change record and the state submission record includes:
determining whether the R changed states are all the same as the corresponding order of committed states, and if so,
determining whether K exists so that the state after the K submission is the same as the state after the R change, and R < K is less than or equal to T, if so,
and determining that the back check result is that the transaction message is not delivered.
7. A method for delivering transaction messages, comprising:
sending a check request back to a delivery device of the transaction message for the transaction message, wherein the check request comprises: a state change record for recording a change process of a state of an object, wherein the object is a business object processed by the transaction message; the state change record comprises the changed state of the object, so that the delivery device of the transaction message determines a recall result according to the state change record and the state commit record of the object, wherein the state commit record is used for recording the commit process of the state of the object, and the state commit record comprises the committed state of the object;
receiving the response result sent by the delivery device of the transaction message;
and determining whether to deliver the transaction message according to the checking result.
8. The method for delivering transaction messages according to claim 7,
before the sending back a check request to a delivery device of a transaction message for the transaction message, further comprising:
the transaction message sent by a delivery device receiving the transaction message, wherein the transaction message comprises: the state change record.
9. The method for delivering transaction messages according to claim 8,
after the transaction message sent by the delivery device receiving the transaction message, before sending a check request back to the delivery device of transaction message for the transaction message, further comprising:
determining a time interval between the current time and the time of receiving the transaction message;
when the time interval is larger than a preset time threshold and the transaction state for the transaction message is sent by the delivery device which does not receive the transaction message within the time interval, executing the transmission request for the transaction message back to the delivery device of the transaction message;
wherein the transaction state comprises: commit, or rollback.
10. The method for delivering transaction messages according to claim 7,
the determining whether to deliver the transaction message according to the result of the check includes:
when the rechecking result is that the transaction message is delivered, delivering the transaction message;
or the like, or, alternatively,
the determining whether to deliver the transaction message according to the result of the check includes:
and when the rechecking result is that the transaction message is not delivered, deleting the transaction message.
11. A device for delivering transaction messages, comprising:
a receiving unit, configured to receive a review request sent by a message server for a transaction message, where the review request includes: a state change record used for recording the change process of the state of an object, wherein the state change record comprises the changed state of the object; the object is a business object processed by the transaction message;
an obtaining unit, configured to obtain a state submission record of a submission process for recording a state of the object, where the state submission record includes a submitted state of the object;
the determining unit is used for determining a retrieval result according to the state change record and the state submission record;
and the sending unit is used for sending the inquiry result to the message server so that the message server determines whether to deliver the transaction message according to the inquiry result.
12. The means for delivering transaction messages as claimed in claim 11,
the state change record includes: the state after the 1 st change is changed to the state after the M time change;
the state commit record includes: the state after the 1 st submission is changed to the state after the Nth submission;
wherein M, N is an integer greater than 1;
the determining unit is configured to determine whether the state after each change in the state change record is the same as the state after each commit in the state commit record, if so, determine that the recheck result is to deliver the transaction message, and otherwise, determine that the recheck result is not to deliver the transaction message.
13. The means for delivering transaction messages as claimed in claim 11,
the state change record includes: a first state to a current state;
wherein the first state to the current state are changed states corresponding to E times of continuous changes; from the first change, F changes are needed when the object reaches the current state, and F is larger than E;
the state commit record includes: the state after the 1 st submission is changed to the state after the H-th submission;
when A, B, C, D does not exist, so that the state after A submission to the state after B submission and the state after C submission to the state after D submission are the same as the state from the first state to the current state,
the determining unit is configured to determine Q, S whether the status after the qth commit to the status after the sth commit is the same as the status from the first status to the current status, if so, determine that the review result is to deliver the transaction message, otherwise, determine that the review result is not to deliver the transaction message.
14. The device for delivering transaction messages as claimed in claim 11, further comprising:
a change unit for opening a transaction; changing the state of the object according to the transaction; determining the state change record according to the state of the changed object; sending the transaction message to the message server, wherein the transaction message comprises: the state change record.
15. The means for delivering transaction messages as claimed in claim 14,
the change unit is further used for determining whether the transaction is executed, if so, submitting the transaction and updating the state submission record, otherwise, rolling back the transaction.
16. The means for delivering transaction messages as claimed in claim 11,
the state change record includes: the state after the 1 st change is changed to the state after the R-th change;
the state commit record includes: the state after the 1 st submission is changed to the state after the T-th submission;
wherein R, T is an integer greater than 1;
and the determining unit is used for determining whether the R changed states are the same as the states after the submission in the corresponding sequence, if so, determining whether K exists, so that the state after the K submission is the same as the state after the R change, and R < K is less than or equal to T, and if so, determining that the recheck result is that the transaction message is not delivered.
17. A message server, comprising:
a sending unit, configured to send a check request to a delivery device of a transaction message for the transaction message, where the check request includes: a state change record for recording a change process of a state of an object, wherein the object is a business object processed by the transaction message; the state change record comprises the changed state of the object, so that the delivery device of the transaction message determines a recall result according to the state change record and the state commit record of the object, wherein the state commit record is used for recording the commit process of the state of the object, and the state commit record comprises the committed state of the object;
a first receiving unit, configured to receive the result of the check sent by the delivery apparatus of the transaction message;
a first determining unit, configured to determine whether to deliver the transaction message according to the result of the check.
18. The message server of claim 17, further comprising:
a second receiving unit, configured to receive the transaction message sent by the delivery device of the transaction message, where the transaction message includes: the state change record.
19. The message server of claim 18, further comprising:
a second determining unit, configured to determine a time interval between a current time and a time when the transaction message is received; when the time interval is larger than a preset time threshold and the transaction state aiming at the transaction message is sent by a delivery device which does not receive the transaction message in the time interval, triggering the sending unit;
wherein the transaction state comprises: commit, or rollback.
20. A message server as claimed in claim 17,
the first determining unit is used for delivering the transaction message when the response result is that the transaction message is delivered; or the like, or, alternatively,
the first determining unit is configured to delete the transaction message when the review result is that the transaction message is not delivered.
21. A system for delivering transaction messages, comprising: a transaction message delivery device as claimed in any one of claims 11 to 16 and a message server as claimed in any one of claims 17 to 20.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811182007.4A CN109491766B (en) | 2018-10-10 | 2018-10-10 | Method, device and system for delivering transaction message and message server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811182007.4A CN109491766B (en) | 2018-10-10 | 2018-10-10 | Method, device and system for delivering transaction message and message server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109491766A CN109491766A (en) | 2019-03-19 |
| CN109491766B true CN109491766B (en) | 2022-03-04 |
Family
ID=65689438
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811182007.4A Active CN109491766B (en) | 2018-10-10 | 2018-10-10 | Method, device and system for delivering transaction message and message server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109491766B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114826803B (en) * | 2022-04-26 | 2023-10-31 | 北京字跳网络技术有限公司 | Conference state processing method and device, electronic equipment and medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105824842A (en) * | 2015-01-07 | 2016-08-03 | 阿里巴巴集团控股有限公司 | Distributed transaction processing method and system |
| CN107766080A (en) * | 2016-08-23 | 2018-03-06 | 阿里巴巴集团控股有限公司 | transaction message processing method, device, equipment and system |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040187108A1 (en) * | 2003-02-21 | 2004-09-23 | Knowles W. Jeffrey | Method of scheduling and event processing in computer operating system |
| US10282228B2 (en) * | 2014-06-26 | 2019-05-07 | Amazon Technologies, Inc. | Log-based transaction constraint management |
| CN105592117B (en) * | 2014-10-23 | 2019-01-25 | 阿里巴巴集团控股有限公司 | A kind for the treatment of method and apparatus of transaction message |
| CN105893395B (en) * | 2015-01-26 | 2019-04-02 | 阿里巴巴集团控股有限公司 | The message of distributed transaction returns checking method and its system |
| CN105988861B (en) * | 2015-02-04 | 2019-06-11 | 阿里巴巴集团控股有限公司 | The sending method and device of transaction message |
| CN106155775B (en) * | 2015-04-28 | 2020-02-21 | 菜鸟智能物流控股有限公司 | Message processing method, device and system |
| CN106168915A (en) * | 2016-04-25 | 2016-11-30 | 云南电网有限责任公司昆明供电局 | Distributed system architecture data process consistency ensuring method |
| CN106021277A (en) * | 2016-04-27 | 2016-10-12 | 湖南蚁坊软件有限公司 | State-based method for implementation of lock-less distributed ACID consistency |
-
2018
- 2018-10-10 CN CN201811182007.4A patent/CN109491766B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105824842A (en) * | 2015-01-07 | 2016-08-03 | 阿里巴巴集团控股有限公司 | Distributed transaction processing method and system |
| CN107766080A (en) * | 2016-08-23 | 2018-03-06 | 阿里巴巴集团控股有限公司 | transaction message processing method, device, equipment and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109491766A (en) | 2019-03-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107450979B (en) | Block chain consensus method and device | |
| CN108418851B (en) | Policy issuing system, method, device and equipment | |
| TWI694342B (en) | Data cache method, device and system | |
| CN107038041B (en) | Data processing method, error code dynamic compatibility method, device and system | |
| CN110992038B (en) | Transaction processing method, device and equipment | |
| CN108599973B (en) | Log association method, device and equipment | |
| CN111143513B (en) | Sensitive word recognition method and device and electronic equipment | |
| CN110399359A (en) | A kind of data retrogressive method, device and equipment | |
| CN110263050B (en) | Data processing method, device, equipment and storage medium | |
| US11175993B2 (en) | Managing data storage system | |
| CN111581239A (en) | Cache refreshing method and electronic equipment | |
| CN113806143B (en) | Remote disaster recovery method, system and electronic equipment | |
| CN111402058B (en) | Data processing method, device, equipment and medium | |
| CN110297955A (en) | A kind of information query method, device, equipment and medium | |
| CN109582398A (en) | A kind of condition processing method, device and electronic equipment | |
| CN109491766B (en) | Method, device and system for delivering transaction message and message server | |
| CN108647112B (en) | Data backup method and device and distributed transaction processing system | |
| CN113643030B (en) | Transaction processing method, device and equipment | |
| CN108470043A (en) | A kind of acquisition methods and device of business result | |
| CN110852752B (en) | Method, device, equipment and storage medium for processing recharge order withdrawal exception | |
| CN110502551A (en) | Data read-write method, system and infrastructure component | |
| CN109388764A (en) | A kind of update method of local cache, device, equipment and system | |
| CN115033350A (en) | Execution method and device of distributed transaction | |
| CN111339117B (en) | Data processing method, device and equipment | |
| CN107645541B (en) | Data storage method and device and server |
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 |