Method and apparatus for distributed transactions in a data communication network

• US 9,418,364 B2
• Filed: 01/28/2014
• Issued: 08/16/2016
• Est. Priority Date: 10/25/2013
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Stridh, Kenny
• Primary Examiner(s): Shingles, Kristie
• Application Number:
  US14/165,981
• Publication Number:
  US 20150120531A1
• Time in Patent Office: 931 Days
• Field of Search: 709/217, 709/238
• US Class Current: 1/1
• 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/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, the global transaction comprising transaction executing instances, the transaction executing instances comprising 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 operations comprising:

receiving a global transaction initiation message comprising a plurality of sub transactions for execution by corresponding ones of the transaction executing instances;

sorting the plurality of the sub transactions for sending at least one prepare transaction message associated with the at least one reliable transaction executing instance;

sending the at least one prepare transaction message to corresponding ones of the at least one reliable transaction executing instance for corresponding ones of the plurality of sub transactions associated with the at least one reliable transaction executing instance;

upon receiving confirmation of receipt of all of the at least one prepare transaction message, sending an execution message to the one unreliable transaction executing instance for a corresponding sub transaction associated with the one unreliable transaction executing instance; and

if said execution message is successful, sending a commit prepared transaction to the at least one reliable transaction executing instance for the corresponding sub transactions.

2. A method according to claim 1 wherein, after the receiving the global transaction initiation message, performing operations comprising:

registering the global transaction initiation message in a storage.

3. A method according to claim 2 wherein the transaction orchestrator node further performs operations comprising:

registering associated sub transactions.

4. A method according to claim 2 wherein the registering further comprises registering an associated sub transaction of the plurality of sub transaction for each transaction executing instance of the transaction executing instances.

5. A method according to claim 1 wherein the receiving the global transaction initiation further comprises:

determining, based on a number of transaction executing instances, that the global transaction comprises a plurality of sub transactions.

6. A method according to claim 1 wherein the at least one prepare transaction message comprises a global transaction identity.

7. A method according to claim 1 wherein, if said execution message is unsuccessful, performing a rollback procedure for the at least one reliable transaction executing instance for corresponding sub transactions.

8. A method according to claim 1, the operations further comprising:

if the at least one of the prepare transaction messages is unsuccessful, performing a rollback procedure for the reliable transaction executing instances for corresponding ones of the sub transactions.

9. A transaction orchestrator node for executing a global transaction in a transaction execution system comprising 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 perform operations comprising;

receiving a global transaction initiation message comprising a plurality of sub transactions for execution by corresponding ones of the transaction executing instances;

sorting the plurality of the sub transactions for sending at least one prepare transaction message associated with the at least one reliable transaction executing instance;

sending the at least one prepare transaction message to corresponding ones of the at least one reliable transaction executing instance for corresponding ones of the plurality of sub transactions associated with the at least one reliable transaction executing instance;

upon receiving confirmation of receipt of all the at least one prepare transaction message, sending an execution message to the one unreliable transaction executing instance for a corresponding sub transaction associated with the one unreliable transaction executing instance; and

if said execution message is successful sending a commit prepared transaction to the at least one reliable transaction executing instance for the corresponding sub transactions.

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

registering the global transaction initiation message in a storage.

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

registering the associated sub transactions.

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

registering an associated sub transaction of the plurality of sub transactions for each transaction executing instance of the transaction executing instances.

13. A transaction orchestrator node according to claim 9, wherein the memory is further containing instructions that, when executed by the processor, cause the transaction orchestrator node to performs operations comprising:

determining, based on a number of transaction executing instances, that the global transaction comprises a plurality of sub transactions.

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

15. A transaction orchestrator node according to claim 9, wherein the memory is further containing instructions that, when executed by the processor, cause the transaction orchestrator node to, if said execution message is unsuccessful, perform a rollback procedure for the at least one reliable transaction executing instance for corresponding sub transactions.

16. A transaction orchestrator node according to claim 9, wherein the memory is further containing instructions that, when executed by the processor, cause the transaction orchestrator node to, if the at least one of the prepare transaction message is unsuccessful, perform a rollback procedure for the reliable transaction executing instances for corresponding ones of the sub transactions.

17. A transaction orchestrator node according to claim 9 wherein the storage is a persistent storage.

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

19. 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 comprising transaction executing instances, the transaction executing instances comprising 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 operations comprising:

receiving a global transaction initiation message comprising a plurality of sub transactions for execution by corresponding ones of the transaction executing instances;

sorting the plurality of the sub transactions for sending at least one prepare transaction message associated with the at least one reliable transaction executing instance;

sending the at least one prepare transaction message to corresponding ones of the at least one reliable transaction executing instance for corresponding ones of the plurality of sub transactions associated with the at least one reliable transaction executing instance;

upon receiving confirmation of receipt of all of the at least one prepare transaction message, sending an execution message to the one unreliable transaction executing instance for a corresponding sub transaction associated with the one unreliable transaction executing instance; and

if said execution message is successful, sending a commit prepared transaction to the at least one reliable transaction executing instance for the corresponding sub transactions.