Transaction management

• US 8,929,878 B2
• Filed: 05/18/2010
• Issued: 01/06/2015
• Est. Priority Date: 05/20/2009
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Griot, Miguel, Song, Osok, Maganti, Nagaraja Kumar
• Primary Examiner(s): SAMS, MATTHEW C
• Application Number:
  US12/782,084
• Publication Number:
  US 20110130157A1
• Time in Patent Office: 1,694 Days
• Field of Search: 370/338, 370/230, 370/235, 370/329, 370/395.21, 370/328, 370/331, 370/348, 370/351, 455/406, 455/411, 455/452.1, 455/452.2, 455/422.1, 455/68, 714/18
• US Class Current: 455/422.1
• CPC Class Codes: H04W 76/11 Allocation or use of connection identifiers
• CPC Class Codes: H04W 76/30 Connection release

Abstract

Transaction identifiers for transactions are managed to mitigate potential mismatches that may occur in the event a message associated with the transaction is not delivered to the intended destination. For example, in the event an access terminal accepts a bearer context request, the access terminal may not immediately release the transaction identifier associated with that transaction. In this way, in the event the access terminal receives a second bearer context request associated with that same transaction identifier (e.g., due to the accept message not reaching the network), the access terminal may send a second accept message in response to the second bearer context request.

Claims

1. A method of communication, comprising:

receiving, by an access terminal, a first evolved packet system (EPS) session management (ESM) message, wherein the first ESM message comprises an EPS bearer context request and a transaction identifier;

sending, by the access terminal, a second ESM message in response to the receipt of the first ESM message, wherein the second ESM message accepts the EPS bearer context request, and wherein the access terminal does not immediately release the transaction identifier in conjunction with accepting the EPS bearer context request;

receiving, by the access terminal, a third ESM message, wherein the third ESM message comprises a retransmission of the EPS bearer context request and the transaction identifier; and

sending, by the access terminal, a fourth ESM message in response to the receipt of the third ESM message, wherein the fourth ESM message accepts the EPS bearer context request.

2. The method of claim 1, further comprising:

starting a timer based on the receipt of the first ESM message;

maintaining a record of the transaction identifier after sending the second ESM message; and

deleting the record if the timer expires or stops.

3. The method of claim 1, further comprising:

starting a timer based on the receipt of the first ESM message;

determining whether the third ESM message is received before the timer expires or stops; and

controlling whether the fourth ESM message is sent based on the determination.

4. The method of claim 1, further comprising:

storing the transaction identifier in a queue;

determining whether the transaction identifier is in the queue when the third ESM message is received; and

controlling whether the fourth ESM message is sent based on the determination.

5. The method of claim 4, further comprising:

determining whether the transaction identifier is associated with a successful transaction; and

controlling whether the transaction identifier is stored in the queue based on the determination of whether the transaction identifier is associated with a successful transaction.

6. The method of claim 4, wherein the queue comprises a first-in first-out memory.

7. The method of claim 1, further comprising:

maintaining a current transaction identifier by incrementing the current transaction identifier every time a new transaction is commenced; and

determining whether the transaction identifier included in the third ESM message is within a defined count of the current transaction identifier when the third ESM message is received; and

controlling whether the fourth ESM message is sent based on the determination.

8. The method of claim 1, further comprising sending a bearer resource request, wherein:

the bearer resource request includes the transaction identifier; and

the first ESM message is received as a result of sending the bearer resource request.

9. The method of claim 8, wherein:

the bearer resource request comprises a packet data network connectivity request, a bearer resource allocation request, or a bearer resource modification request; and

the first ESM message comprises an activate default EPS bearer context request, an activate dedicated EPS bearer context request, or a modify EPS bearer context request.

10. The method of claim 1, further comprising:

receiving a lower layer indication that the second ESM message was not delivered; and

deactivating an EPS bearer context associated with the EPS bearer context request as a result of the receipt of the lower layer indication.

11. The method of claim 1, further comprising delaying activation or modification of an EPS bearer context associated with the EPS bearer context request until receipt of a lower layer indication that the second ESM message was delivered.

12. The method of claim 1, further comprising:

receiving a lower layer indication that the second ESM message was delivered; and

releasing the transaction identifier as a result of the receipt of the lower layer indication.

13. An access terminal, comprising:

a receiver configured to receive a first evolved packet system (EPS) session management (ESM) message, wherein the first ESM message comprises an EPS bearer context request and a transaction identifier; and

a transmitter configured to send a second ESM message that accepts the EPS bearer context request in response to the receipt of the first ESM message, wherein the access terminal does not immediately release the transaction identifier in conjunction with accepting the EPS bearer context request, and wherein;

the receiver is further configured to receive a third ESM message that comprises a retransmission of the EPS bearer context request and the transaction identifier, and

the transmitter is further configured to send a fourth ESM message that accepts the EPS bearer context request in response to the receipt of the third ESM message.

14. The access terminal of claim 13, further comprising:

a timing controller configured to start a timer based on the receipt of the first ESM message; and

a transaction identifier manager configured to maintain a record of the transaction identifier after sending the second ESM message, and further configured to delete the record if the timer expires or stops.

15. The access terminal of claim 13, further comprising:

a timing controller configured to start a timer based on the receipt of the first ESM message, and further configured to determine whether the third ESM message is received before the timer expires or stops; and

a communication controller configured to control whether the fourth ESM message is sent based on the determination.

16. The access terminal of claim 13, further comprising:

a transaction identifier manager configured to store the transaction identifier in a queue, and further configured to determine whether the transaction identifier is in the queue when the third ESM message is received; and

a communication controller configured to control whether the fourth ESM message is sent based on the determination.

17. The access terminal of claim 16, further comprising a transaction identifier manager configured to:

determine whether the transaction identifier is associated with a successful transaction; and

control whether the transaction identifier is stored in the queue based on the determination of whether the transaction identifier is associated with a successful transaction.

18. The access terminal of claim 16, wherein the queue comprises a first-in first-out memory.

19. The access terminal of claim 13, further comprising:

a transaction identifier manager configured to maintain a current transaction identifier by incrementing the current transaction identifier every time a new transaction is commenced, and further configured to determine whether the transaction identifier included in the third ESM message is within a defined count of the current transaction identifier when the third ESM message is received; and

a communication controller configured to control whether the fourth ESM message is sent based on the determination.

20. The access terminal of claim 13, wherein:

the transmitter is further configured to send a bearer resource request;

the bearer resource request includes the transaction identifier; and

the first ESM message is received as a result of sending the bearer resource request.

21. The access terminal of claim 20, wherein:

the bearer resource request comprises a packet data network connectivity request, a bearer resource allocation request, or a bearer resource modification request; and

the first ESM message comprises an activate default EPS bearer context request, an activate dedicated EPS bearer context request, or a modify EPS bearer context request.

22. The access terminal of claim 13, further comprising:

a communication controller configured to receive a lower layer indication that the second ESM message was not delivered; and

a bearer manager configured to deactivate an EPS bearer context associated with the EPS bearer context request as a result of the receipt of the lower layer indication.

23. The access terminal of claim 13, further comprising a bearer manager configured to delay activation or modification of an EPS bearer context associated with the EPS bearer context request until receipt of a lower layer indication that the second ESM message was delivered.

24. The access terminal of claim 13, further comprising:

a communication controller configured to receive a lower layer indication that the second ESM message was delivered; and

a transaction identifier manager configured to release the transaction identifier as a result of the receipt of the lower layer indication.

25. An access terminal, comprising:

means for receiving a first evolved packet system (EPS) session management (ESM) message, wherein the first ESM message comprises an EPS bearer context request and a transaction identifier;

means for sending a second ESM message in response to the receipt of the first ESM message, wherein the second ESM message accepts the EPS bearer context request, and wherein the access terminal does not immediately release the transaction identifier in conjunction with accepting the EPS bearer context request;

means for receiving a third ESM message, wherein the third ESM message comprises a retransmission of the EPS bearer context request and the transaction identifier; and

means for sending a fourth ESM message in response to the receipt of the third ESM message, wherein the fourth ESM message accepts the EPS bearer context request.

26. The access terminal of claim 25, further comprising:

means for starting a timer based on the receipt of the first ESM message;

means for maintaining a record of the transaction identifier after sending the second ESM message; and

means for deleting the record if the timer expires or stops.

27. The access terminal of claim 25, further comprising:

means for starting a timer based on the receipt of the first ESM message;

means for determining whether the third ESM message is received before the timer expires or stops; and

means for controlling whether the fourth ESM message is sent based on the determination.

28. The access terminal of claim 25, further comprising:

means for storing the transaction identifier in a queue;

means for determining whether the transaction identifier is in the queue when the third ESM message is received; and

means for controlling whether the fourth ESM message is sent based on the determination.

29. The access terminal of claim 28, further comprising:

means for determining whether the transaction identifier is associated with a successful transaction; and

means for controlling whether the transaction identifier is stored in the queue based on the determination of whether the transaction identifier is associated with a successful transaction.

30. The access terminal of claim 28, wherein the queue comprises a first-in first-out memory.

31. The access terminal of claim 25, further comprising:

means for maintaining a current transaction identifier by incrementing the current transaction identifier every time a new transaction is commenced;

means for determining whether the transaction identifier included in the third ESM message is within a defined count of the current transaction identifier when the third ESM message is received; and

means for controlling whether the fourth ESM message is sent based on the determination.

32. The access terminal of claim 25, further comprising means for sending a bearer resource request, wherein:

the bearer resource request includes the transaction identifier; and

the first ESM message is received as a result of sending the bearer resource request.

33. The access terminal of claim 32, wherein:

the bearer resource request comprises a packet data network connectivity request, a bearer resource allocation request, or a bearer resource modification request; and

the first ESM message comprises an activate default EPS bearer context request, an activate dedicated EPS bearer context request, or a modify EPS bearer context request.

34. The access terminal of claim 25, further comprising:

means for receiving a lower layer indication that the second ESM message was not delivered; and

means for deactivating an EPS bearer context associated with the EPS bearer context request as a result of the receipt of the lower layer indication.

35. The access terminal of claim 25, further comprising means for delaying activation or modification of an EPS bearer context associated with the EPS bearer context request until receipt of a lower layer indication that the second ESM message was delivered.

36. The access terminal of claim 25, further comprising:

means for receiving a lower layer indication that the second ESM message was delivered; and

means for releasing the transaction identifier as a result of the receipt of the lower layer indication.

37. A non-transitory computer-readable medium comprising code for causing a computer to:

receive, by an access terminal, a first evolved packet system (EPS) session management (ESM) message, wherein the first ESM message comprises an EPS bearer context request and a transaction identifier;

send, by the access terminal, a second ESM message in response to the receipt of the first ESM message, wherein the second ESM message accepts the EPS bearer context request, and wherein the access terminal does not immediately release the transaction identifier in conjunction with accepting the EPS bearer context request;

receive, by the access terminal, a third ESM message, wherein the third ESM message comprises a retransmission of the EPS bearer context request and the transaction identifier; and

send, by the access terminal, a fourth ESM message in response to the receipt of the third ESM message, wherein the fourth ESM message accepts the EPS bearer context request.

38. The non-transitory computer-readable medium of claim 37, further comprising code for causing the computer to:

start a timer based on the receipt of the first ESM message;

maintain a record of the transaction identifier after sending the second ESM message; and

delete the record if the timer expires or stops.

39. The non-transitory computer-readable medium of claim 37, further comprising code for causing the computer to:

start a timer based on the receipt of the first ESM message;

determine whether the third ESM message is received before the timer expires or stops; and

control whether the fourth ESM message is sent based on the determination.

40. The non-transitory computer-readable medium of claim 37, further comprising code for causing the computer to:

store the transaction identifier in a queue;

determine whether the transaction identifier is in the queue when the third ESM message is received; and

control whether the fourth ESM message is sent based on the determination.

41. The non-transitory computer-readable medium of claim 40, further comprising code for causing the computer to:

determine whether the transaction identifier is associated with a successful transaction; and

control whether the transaction identifier is stored in the queue based on the determination of whether the transaction identifier is associated with a successful transaction.

42. The non-transitory computer-readable medium of claim 40, wherein the queue comprises a first-in first-out memory.

43. The non-transitory computer-readable medium of claim 37, further comprising code for causing the computer to:

maintain a current transaction identifier by incrementing the current transaction identifier every time a new transaction is commenced;

determine whether the transaction identifier included in the third ESM message is within a defined count of the current transaction identifier when the third ESM message is received; and

control whether the fourth ESM message is sent based on the determination.

44. The non-transitory computer-readable medium of claim 37, wherein:

the non-transitory computer-readable medium further comprises code for causing the computer to send a bearer resource request;

the bearer resource request includes the transaction identifier; and

the first ESM message is received as a result of sending the bearer resource request.

45. The non-transitory computer-readable medium of claim 44, wherein:

the bearer resource request comprises a packet data network connectivity request, a bearer resource allocation request, or a bearer resource modification request; and

the first ESM message comprises an activate default EPS bearer context request, an activate dedicated EPS bearer context request, or a modify EPS bearer context request.

46. The non-transitory computer-readable medium of claim 37, further comprising code for causing the computer to:

receive a lower layer indication that the second ESM message was not delivered; and

deactivate an EPS bearer context associated with the EPS bearer context request as a result of the receipt of the lower layer indication.

47. The non-transitory computer-readable medium of claim 37, further comprising code for causing the computer to delay activation or modification of an EPS bearer context associated with the EPS bearer context request until receipt of a lower layer indication that the second ESM message was delivered.

48. The non-transitory computer-readable medium of claim 37, further comprising code for causing the computer to:

receive a lower layer indication that the second ESM message was delivered; and

release the transaction identifier as a result of the receipt of the lower layer indication.

49. A method of communication, comprising:

receiving, by an access terminal, a first evolved packet system (EPS) session management (ESM) message, wherein the first ESM message comprises an EPS bearer context request and includes a transaction identifier;

sending, by the access terminal, a second ESM message in response to the receipt of the first ESM message, wherein the second ESM message accepts the EPS bearer context request;

starting a timer based on the sending of the second ESM message;

receiving, by the access terminal, a lower layer indication that the second ESM message was delivered;

stopping the timer as a result of the receipt of the lower layer indication; and

releasing the transaction identifier as a result of the receipt of the lower layer indication.

50. The method of claim 49, wherein the timer provides an indication of a period of time during which receipt of a retransmission of the first ESM message triggers sending of a third ESM message that accepts the EPS bearer context.

51. The method of claim 50, wherein expiration of the timer provides an indication that receipt of a retransmission of the first ESM message does not trigger sending of a third ESM message that accepts the EPS bearer context.

52. The method of claim 49, further comprising delaying activation or modification of an EPS bearer context associated with the EPS bearer context request until receipt of the lower layer indication.

53. An access terminal, comprising:

a receiving configured to receive a first evolved packet system (EPS) session management (ESM) message, wherein the first ESM message comprises an EPS bearer context request and includes a transaction identifier;

a transmitter configured to send a second ESM message in response to the receipt of the first ESM message, wherein the second ESM message accepts the EPS bearer context request; and

a timing controller configured to start a timer based on the sending of the second ESM message;

the receiver is further configured to receive a lower layer indication that the second ESM message was delivered;

the timing controller is further configured to stop the timer as a result of the receipt of the lower layer indication; and

releasing the transaction identifier as a result of the receipt of the lower layer indication.

54. The access terminal of claim 53, wherein the timer provides an indication of a period of time during which receipt of a retransmission of the first ESM message triggers sending of a third ESM message that accepts the EPS bearer context.

55. An access terminal, comprising:

means for receiving a first evolved packet system (EPS) session management (ESM) message, wherein the first ESM message comprises an EPS bearer context request and includes a transaction identifier;

means for sending a second ESM message in response to the receipt of the first ESM message, wherein the second ESM message accepts the EPS bearer context request;

means for starting a timer based on the sending of the second ESM message;

means for receiving a lower layer indication that the second ESM message was delivered;

means for stopping the timer as a result of the receipt of the lower layer indication; and

means for releasing the transaction identifier as a result of the receipt of the lower layer indication.

56. The access terminal of claim 55, wherein the timer provides an indication of a period of time during which receipt of a retransmission of the first ESM message triggers sending of a third ESM message that accepts the EPS bearer context.

57. A non-transitory computer-readable medium comprising code for causing a computer to:

receive, by an access terminal, a first evolved packet system (EPS) session management (ESM) message, wherein the first ESM message comprises an EPS bearer context request and includes a transaction identifier;

send, by the access terminal, a second ESM message in response to the receipt of the first ESM message, wherein the second ESM message accepts the EPS bearer context request;

start a timer based on the sending of the second ESM message;

receive, by the access terminal, a lower layer indication that the second ESM message was delivered;

stop the timer as a result of the receipt of the lower layer indication; and

release the transaction identifier as a result of the receipt of the lower layer indication.

58. The non-transitory computer-readable medium of claim 57, wherein the timer provides an indication of a period of time during which receipt of a retransmission of the first ESM message triggers sending of a third ESM message that accepts the EPS bearer context.