METHOD AND APPARATUS FOR DISTRIBUTED TRANSACTIONS IN A DATA COMMUNICATION NETWORK

• US 20150120531A1
• Filed: 01/28/2014
• Published: 04/30/2015
• Est. Priority Date: 10/25/2013
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: STRIDH, Kenny
• Granted Patent: US 9,418,364 B2
• Time in Patent Office: Days
• US Class Current: 705/39
• CPC Class Codes: G06F 11/1474 in transactions G06F16/20 takes precedence
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/027 involving a payment switch or gateway
• CPC Class Codes: G06Q 20/0855 involving a third party
• CPC Class Codes: G06Q 20/407 Cancellation of a transaction
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

A method and transaction orchestrator node for executing a global transaction in a transaction execution system. The transaction execution system is involving at least one reliable transaction executing instance supporting a reserve/commit protocol and one unreliable transaction executing instance that does not support a reserve/commit protocol. The transaction orchestrator node is receiving a global transaction initiation message involving plural sub transactions for execution by the involved corresponding transaction executing instances and sending a prepare transaction message to involved reliable transaction executing instances for corresponding sub transactions. Upon receiving confirmation of all prepare transaction messages the transaction orchestrator node is sending an execution message to the involved unreliable transaction executing instance for a corresponding sub transaction. If the execution message is successful the transaction orchestrator node is sending a commit prepared transaction to the involved reliable transaction executing instances for the corresponding sub transactions.

Claims

1. A method for executing a global transaction performed by a transaction orchestrator node in a transaction execution system involving at least one reliable transaction executing instance supporting a reserve/commit protocol and one unreliable transaction executing instance that does not support a reserve/commit protocol, the transaction orchestrator node performing the steps of:

receiving a global transaction initiation message involving plural sub transactions for execution by the involved corresponding transaction executing instances;

sending a prepare transaction message to involved reliable transaction executing instances for corresponding sub transactions; and

upon receiving confirmation of all prepare transaction messages sending an execution message to the involved unreliable transaction executing instance for a corresponding sub transaction; and

if said execution message is successful sending a commit prepared transaction to the involved reliable transaction executing instances for the corresponding sub transactions.

2. A method according to claim 1 wherein, after the step of receiving, sorting the involved sub transactions for sending the prepare transaction message to involved reliable transaction executing instances before sending the execution message to the involved unreliable transaction executing instance.

3. A method according to claim 1 wherein, after the step of receiving, performing the further step of registering the global transaction initiation message in a storage.

4. A method according to claim 3 wherein the registering further comprises registering the associated sub transactions.

5. A method according to claim 3 wherein the registering further comprises registering associated sub transactions, one for each transaction executing instance.

6. A method according to claim 1 wherein the step of receiving further comprising determining, based on the number of involved transaction executing instance, that the global transaction is involving plural sub transactions.

7. A method according to claim 1 wherein the prepare transaction message includes a global transaction identity.

8. A method according to claim 1 wherein, if said execution message is unsuccessful, performing a rollback procedure for the involved reliable transaction executing instances for corresponding sub transactions.

9. A method according to claim 1 wherein, if said prepare transaction message is unsuccessful;

performing a rollback procedure for the involved reliable transaction executing instances for corresponding sub transactions.

10. A transaction orchestrator node for executing a global transaction in a transaction execution system involving at least one reliable transaction executing instance supporting a reserve/commit protocol and one unreliable transaction executing instance that does not support a reserve/commit protocol, the node comprising:

a processor;

a memory containing instructions that, when executed by the processor, cause the node to;

receive a global transaction initiation message involving plural sub transactions for execution by the involved corresponding transaction executing instances;

send a prepare transaction message to involved reliable transaction executing instances for corresponding sub transactions; and

upon receiving confirmation of all prepare transaction messages send an execution message to the involved unreliable transaction executing instance for a corresponding sub transaction; and

if said execution message is successful send a commit prepared transaction to the involved reliable transaction executing instances for the corresponding sub transactions.

11. A transaction orchestrator node according to claim 10 wherein the memory is further containing instructions that, when executed by the processor, cause the node to:

sort the involved sub transactions for sending the prepare transaction message to involved reliable transaction executing instances before sending the execution message to the involved unreliable transaction executing instance.

12. A transaction orchestrator node according to claim 10, wherein the memory is further containing instructions that, when executed by the processor, cause the node to:

register the global transaction initiation message in a storage.

13. A transaction orchestrator node according to claim 12, wherein the memory is further containing instructions that, when executed by the processor, cause the node to register the associated sub transactions.

14. A transaction orchestrator node according to claim 12, wherein the memory is further containing instructions that, when executed by the processor, cause the node to:

register associated sub transactions, one for each transaction executing instance.

15. A transaction orchestrator node according to claim 10, wherein the memory is further containing instructions that, when executed by the processor, cause the node to determine, based on the number of involved transaction executing instance, that the global transaction is involving plural sub transactions.

16. A transaction orchestrator node according to claim 10, wherein the memory is further containing instructions that, when executed by the processor, cause the node to include a global transaction identity in the prepare transaction message.

17. A transaction orchestrator node according to claim 10, wherein the memory is further containing instructions that, when executed by the processor, cause the node to, if said execution message is unsuccessful, perform a rollback procedure for the involved reliable transaction executing instances for corresponding sub.

18. A transaction orchestrator node according to claim 10, wherein the memory is further containing instructions that, when executed by the processor, cause the node to, if said prepare transaction message is unsuccessful;

perform a rollback procedure for all involved reliable transaction executing instances for corresponding sub.

19. A transaction orchestrator node according to claim 10 wherein the storage is a persistent storage.

20. A transaction orchestrator node according to claim 19 wherein the persistent storage conforms to principles which guarantee that database transactions are processed reliably, such as atomicity, consistency, isolation, durability principles.

21. A computer program product, comprising a non-transitory computer readable medium and a computer program stored on the computer readable medium, the computer program comprising computer readable code means, which when run in a computer being configured as a transaction orchestrator node for executing a global transaction in a transaction execution system involving at least one reliable transaction executing instance supporting a reserve/commit protocol and one unreliable transaction executing instance that does not support a reserve/commit protocol, causes the computer to perform the following steps:

receiving a global transaction initiation message involving plural sub transactions for execution by the involved corresponding transaction executing instances;

sending a prepare transaction message to involved reliable transaction executing instances for corresponding sub transactions; and

upon receiving confirmation (440) of all prepare transaction messages sending an execution message to the involved unreliable transaction executing instance for a corresponding sub transaction; and

if said execution message is successful sending a commit prepared transaction to the involved reliable transaction executing instances for the corresponding sub transactions.