TRANSACTION MANAGEMENT

• US 20110130157A1
• Filed: 05/18/2010
• Published: 06/02/2011
• Est. Priority Date: 05/20/2009
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Griot, Miguel, Maganti, Nagaraja Kumar, Song, Osok
• Granted Patent: US 8,929,878 B2
• Time in Patent Office: Days
• US Class Current: 455/466
• 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 a first message, wherein the first message comprises a bearer context request and includes a transaction identifier;

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

receiving a third message, wherein the third message comprises a bearer context request and includes the transaction identifier; and

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

2. The method of claim 1, further comprising:

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

maintaining a record of the transaction identifier after sending the second 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 message;

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

controlling whether the fourth 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 message is received; and

controlling whether the fourth 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 message is within a defined count of the current transaction identifier when the third message is received; and

controlling whether the fourth 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 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 message comprises an activate default bearer context request, an activate dedicated bearer context request, or a modify bearer context request.

10. The method of claim 1, further comprising:

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

deactivating a bearer context associated with the 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 a bearer context associated with the bearer context request until receipt of a lower layer indication that the second message was delivered.

12. The method of claim 1, further comprising:

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

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

13. The method of claim 1, wherein the first and third messages are received by an access terminal and the second and fourth message are sent by the access terminal.

14. An apparatus for communication, comprising:

a receiver configured to receive a first message, wherein the first message comprises a bearer context request and includes a transaction identifier; and

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

the receiver is further configured to receive a third message that comprises a bearer context request and includes the transaction identifier, and

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

15. The apparatus of claim 14, further comprising:

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

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

16. The apparatus of claim 14, further comprising:

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

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

17. The apparatus of claim 14, 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 message is received; and

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

18. The apparatus of claim 17, 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.

19. The apparatus of claim 17, wherein the queue comprises a first-in first-out memory.

20. The apparatus of claim 14, 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 message is within a defined count of the current transaction identifier when the third message is received; and

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

21. The apparatus of claim 14, wherein:

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

the bearer resource request includes the transaction identifier; and

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

22. The apparatus of claim 21, 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 message comprises an activate default bearer context request, an activate dedicated bearer context request, or a modify bearer context request.

23. The apparatus of claim 14, further comprising:

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

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

24. The apparatus of claim 14, further comprising a bearer manager configured to delay activation or modification of a bearer context associated with the bearer context request until receipt of a lower layer indication that the second message was delivered.

25. The apparatus of claim 14, further comprising:

a communication controller configured to receive a lower layer indication that the second 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.

26. An apparatus for communication, comprising:

means for receiving a first message, wherein the first message comprises a bearer context request and includes a transaction identifier;

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

means for receiving a third message, wherein the third message comprises a bearer context request and includes the transaction identifier; and

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

27. The apparatus of claim 26, further comprising:

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

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

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

28. The apparatus of claim 26, further comprising:

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

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

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

29. The apparatus of claim 26, 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 message is received; and

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

30. The apparatus of claim 29, 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.

31. The apparatus of claim 29, wherein the queue comprises a first-in first-out memory.

32. The apparatus of claim 26, 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 message is within a defined count of the current transaction identifier when the third message is received; and

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

33. The apparatus of claim 26, further comprising means for sending a bearer resource request, wherein:

the bearer resource request includes the transaction identifier; and

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

34. The apparatus of claim 33, 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 message comprises an activate default bearer context request, an activate dedicated bearer context request, or a modify bearer context request.

35. The apparatus of claim 26, further comprising:

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

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

36. The apparatus of claim 26, further comprising means for delaying activation or modification of a bearer context associated with the bearer context request until receipt of a lower layer indication that the second message was delivered.

37. The apparatus of claim 26, further comprising:

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

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

38. A computer-program product, comprising:

computer-readable medium comprising code for causing a computer to;

receive a first message, wherein the first message comprises a bearer context request and includes a transaction identifier;

send a second message in response to the receipt of the first message, wherein the second message accepts the bearer context request;

receive a third message, wherein the third message comprises a bearer context request and includes the transaction identifier; and

send a fourth message in response to the receipt of the third message, wherein the fourth message accepts the bearer context request.

39. The computer-program product of claim 38, wherein the computer-readable medium further comprises code for causing the computer to:

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

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

delete the record if the timer expires or stops.

40. The computer-program product of claim 38, wherein the computer-readable medium further comprises code for causing the computer to:

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

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

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

41. The computer-program product of claim 38, wherein the computer-readable medium further comprises 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 message is received; and

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

42. The computer-program product of claim 41, wherein the computer-readable medium further comprises 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.

43. The computer-program product of claim 41, wherein the queue comprises a first-in first-out memory.

44. The computer-program product of claim 38, wherein the computer-readable medium further comprises 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 message is within a defined count of the current transaction identifier when the third message is received; and

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

45. The computer-program product of claim 38, wherein:

the 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 message is received as a result of sending the bearer resource request.

46. The computer-program product of claim 45, 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 message comprises an activate default bearer context request, an activate dedicated bearer context request, or a modify bearer context request.

47. The computer-program product of claim 38, wherein the computer-readable medium further comprises code for causing the computer to:

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

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

48. The computer-program product of claim 38, wherein the computer-readable medium further comprises code for causing the computer to delay activation or modification of a bearer context associated with the bearer context request until receipt of a lower layer indication that the second message was delivered.

49. The computer-program product of claim 38, wherein the computer-readable medium further comprises code for causing the computer to:

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

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

50. A method of communication, comprising:

receiving a first message, wherein the first message comprises a bearer context request and includes a transaction identifier;

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

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

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

stopping the timer as a result of the receipt of the lower layer indication.

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

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

53. The method of claim 50, further comprising delaying activation or modification of a bearer context associated with the bearer context request until receipt of the lower layer indication.

54. The method of claim 50, further comprising releasing the transaction identifier as a result of the receipt of the lower layer indication.

55. An apparatus for communication, comprising:

a receiver configured to receive a first message, wherein the first message comprises a bearer context request and includes a transaction identifier;

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

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

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

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

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

57. An apparatus for communication, comprising:

means for receiving a first message, wherein the first message comprises a bearer context request and includes a transaction identifier;

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

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

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

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

58. The apparatus of claim 57, wherein the timer provides an indication of a period of time during which receipt of a retransmission of the first message triggers sending of a third message that accepts the bearer context.

59. A computer-program product, comprising:

computer-readable medium comprising code for causing a computer to;

receive a first message, wherein the first message comprises a bearer context request and includes a transaction identifier;

send a second message in response to the receipt of the first message, wherein the second message accepts the bearer context request;

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

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

stop the timer as a result of the receipt of the lower layer indication.

60. The computer-program product of claim 59, wherein the timer provides an indication of a period of time during which receipt of a retransmission of the first message triggers sending of a third message that accepts the bearer context.