MANAGEMENT OF TCP/IP MESSAGING IN WIRELESS NETWORKS

• US 20130064179A1
• Filed: 09/14/2011
• Published: 03/14/2013
• Est. Priority Date: 09/14/2011
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Attar, Rashid Ahmed Akbar, Lott, Christopher Gerard, Ghosh, Donna, He, Linhai, Cherian, George
• Granted Patent: US 8,774,208 B2
• Time in Patent Office: Days
• US Class Current: 370/328
• CPC Class Codes: H04L 47/323 Discarding or blocking control packets, e.g. ACK packets
• CPC Class Codes: H04W 28/0268 using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] negotiating SLA or negotiating QoS H04W28/24

Abstract

Some implementations of the present invention provide mechanisms for gating the transmission of FIN and other short overhead messages of the like in order to improve spectral efficiency. In some implementations spectral efficiency is improved by reducing the number of air-link connections established to merely transmit FIN and other short overhead messages of the like. In one implementation FIN messages are buffered in a queue and transmitted when an air-link connection is established to transmit higher value messages. In one implementation FIN messages are buffered and transmitted when the contents of the buffer breach a threshold that justifies the establishment of an air-link connection to transmit the contents of the buffer.

Claims

1. A method comprising:

determining whether a data unit is at least one of a first data type and a second data type; and

delaying the transmission of data of the first data type until an air-link connection is established for the transmission of data of the second data.

2. The method of claim 1, wherein the second data type has a higher value than the first data type.

3. The method of claim 1, wherein the second data type includes at least one of time-critical information for an application server and non-overhead information.

4. The method of claim 1, wherein the first data type includes data that can be delayed without substantially diminishing the user experience.

5. The method of claim 4, wherein the first type of data is at least one of a FIN packet, a session close, and a socket close command.

6. The method of claim 4, wherein the first type of data is a packet comprising primarily overhead information.

7. The method of claim 1, further comprising:

receiving a data unit of the first packet type from an application;

storing the data unit in a buffer in order to delay transmission; and

transmitting a false acknowledgement to at least one of the application and an operating system in response to receiving the first data unit.

8. The method of claim 7, wherein the data unit includes a socket close command.

9. The method of claim 7, further comprising sensing the establishment of an air-link connection for the transmission of data units of the second type.

10. The method of claim 9, further comprising releasing the data units in the buffer to a radio stack in response to establishing the air-link connection.

11. The method of claim 9, further comprising releasing the data units in the buffer to a communication protocol stack in response to establishing the air-link connection.

12. The method of claim 11, wherein the communication protocol includes at least some elements of the Transmission Control Protocol/Internet Protocol suite.

13. The method of claim 7, further comprising:

determining that the contents of the buffer has breached a threshold;

establishing an air-link connection in response to the breach; and

transmitting the data units in the buffer.

14. The method of claim 13, wherein transmitting the data units in the buffer includes releasing the data units in the buffer to a radio stack.

15. The method of claim 13, wherein transmitting the data units in the buffer includes releasing the data units in the buffer to a communication protocol stack.

16. The method of claim 1, further comprising:

receiving a data unit of the first packet type from an application;

storing the data unit in a buffer; and

transmitting an acknowledgement to at least one of the application and an operating system in response to receiving the first data unit.

17. The method of claim 16, wherein the acknowledgement includes information intended to bypass a limit on the number of open sockets that can be simultaneously maintained by a device.

18. The method of claim 17, wherein the limit is policed by at least the operating system.

19. The method of claim 1, further comprising transmitting data units of the first data type in response to the establishment of an air-link connection.

20. A computer program product for managing air-link connections that when executed cause an apparatus to:

determine whether a data unit is at least one of a first data type and a second data type; and

delay the transmission of data of the first data type until an air-link connection is established for the transmission of data of the second data.

21. The computer program product of claim 20, wherein the second data type has a higher value than the first data type.

22. The computer program product of claim 20, wherein the second data type includes at least one of time-critical information for an application server and non-overhead information.

23. The computer program product of claim 20, wherein the first data type includes data that can be delayed without substantially diminishing the user experience.

24. The computer program product of claim 23, wherein the first type of data is at least one of a FIN packet, a session close, and a socket close command.

25. The computer program product of claim 23, wherein the first type of data is a packet comprising primarily overhead information.

26. The computer program product of claim 20, further comprising instructions that when executed cause an apparatus to:

receive a data unit of the first packet type from an application;

store the data unit in a buffer in order to delay transmission; and

transmit a false acknowledgement to at least one of the application and an operating system in response to receiving the first data unit.

27. The computer program product of claim 26, wherein the data unit includes a socket close command.

28. The computer program product of claim 26, further comprising instructions that when executed cause an apparatus to sense the establishment of an air-link connection for the transmission of data units of the second type.

29. The computer program product of claim 26, further comprising instructions that when executed cause an apparatus to release the data units in the buffer to a radio stack in response to establishing the air-link connection.

30. The computer program product of claim 28, further comprising instructions that when executed cause an apparatus to release the data units in the buffer to a communication protocol stack in response to establishing the air-link connection.

31. The computer program product of claim 30, wherein the communication protocol includes at least some elements of the Transmission Control Protocol/Internet Protocol suite.

32. The computer program product of claim 26, further comprising instructions that when executed cause an apparatus to:

determine that the contents of the buffer has breached a threshold;

establish an air-link connection in response to the breach; and

transmit the data units in the buffer.

33. The computer program product of claim 32, wherein transmitting the data units in the buffer includes releasing the data units in the buffer to a radio stack.

34. The computer program product of claim 32, wherein transmitting the data units in the buffer includes releasing the data units in the buffer to a communication protocol stack.

35. The computer program product of claim 20, further comprising instructions that when executed cause an apparatus to:

receive a data unit of the first packet type from an application;

store the data unit in a buffer; and

transmit an acknowledgement to at least one of the application and an operating system in response to receiving the first data unit.

36. The computer program product of claim 35, wherein the acknowledgement includes information intended to bypass a limit on the number of open sockets that can be simultaneously maintained by a device.

37. The computer program product of claim 36, wherein the limit is policed by at least the operating system.

38. The computer program product of claim 20, further comprising instructions that when executed cause an apparatus to transmit data units of the first data type in response to the establishment of an air-link connection.

45. The apparatus of claim 38, further comprising:

means for receiving a data unit of the first packet type from an application;

means for storing the data unit in a buffer in order to delay transmission; and

means for transmitting a false acknowledgement to at least one of the application and an operating system in response to receiving the first data unit.

46. The apparatus of claim 45, wherein the data unit includes a socket close command.

47. The apparatus of claim 45, further comprising means for sensing the establishment of an air-link connection for the transmission of data units of the second type.

48. The apparatus of claim 45, further comprising means for releasing the data units in the buffer to a radio stack in response to establishing the air-link connection.

49. The apparatus of claim 47, further comprising means for releasing the data units in the buffer to a communication protocol stack in response to establishing the air-link connection.

50. The apparatus of claim 49, wherein the communication protocol includes at least some elements of the Transmission Control Protocol/Internet Protocol suite.

51. The apparatus of claim 45, further comprising:

means for determining that the contents of the buffer has breached a threshold;

means for establishing an air-link connection in response to the breach; and

means for transmitting the data units in the buffer.

52. The apparatus of claim 51, wherein transmitting the data units in the buffer includes releasing the data units in the buffer to a radio stack.

53. The apparatus of claim 51, wherein transmitting the data units in the buffer includes releasing the data units in the buffer to a communication protocol stack.

57. The apparatus of claim 38, further comprising means for transmitting data units of the first data type in response to the establishment of an air-link connection.

39. An apparatus comprising:

means for determining whether a data unit is at least one of a first data type and a second data type; and

means for delaying the transmission of data of the first data type until an air-link connection is established for the transmission of data of the second data.

40. The apparatus of claim 39, wherein the second data type has a higher value than the first data type.

41. The apparatus of claim 39, wherein the second data type includes at least one of time-critical information for an application server and non-overhead information.

42. The apparatus of claim 39, wherein the first data type includes data that can be delayed without substantially diminishing the user experience.

43. The apparatus of claim 42, wherein the first type of data is at least one of a FIN packet, a session close, and a socket close command.

44. The apparatus of claim 42, wherein the first type of data is a packet comprising primarily overhead information.

54. The apparatus of claim 39, further comprising:

means for receiving a data unit of the first packet type from an application;

means for storing the data unit in a buffer; and

means for transmitting an acknowledgement to at least one of the application and an operating system in response to receiving the first data unit.

55. The apparatus of claim 54, wherein the acknowledgement includes information intended to bypass a limit on the number of open sockets that can be simultaneously maintained by a device.

56. The apparatus of claim 55, wherein the limit is policed by at least the operating system.

58. An apparatus comprising:

a controller configured to determine whether a data unit is at least one of a first data type and a second data type, delay the transmission of data of the first data type until an air-link connection is established for the transmission of data of the second data.

59. The apparatus of claim 58, wherein the second data type has a higher value than the first data type.

60. The apparatus of claim 58, wherein the second data type includes at least one of time-critical information for an application server and non-overhead information.

61. The apparatus of claim 58, wherein the first data type includes data that can be delayed without substantially diminishing the user experience.

62. The apparatus of claim 61, wherein the first type of data is at least one of a FIN packet, a session close, and a socket close command.

63. The apparatus of claim 61, wherein the first type of data is a packet comprising primarily overhead information.

64. The apparatus of claim 58, wherein the controller is further configured to:

receive a data unit of the first packet type from an application;

store the data unit in a buffer in order to delay transmission; and

transmit a false acknowledgement to at least one of the application and an operating system in response to receiving the first data unit.

65. The apparatus of claim 64, wherein the data unit includes a socket close command.

66. The apparatus of claim 64, wherein the controller is further configured to sense the establishment of an air-link connection for the transmission of data units of the second type.

67. The apparatus of claim 64, wherein the controller is further configured to release the data units in the buffer to a radio stack in response to establishing the air-link connection.

68. The apparatus of claim 66, wherein the controller is further configured to release the data units in the buffer to a communication protocol stack in response to establishing the air-link connection.

69. The apparatus of claim 68, wherein the communication protocol includes at least some elements of the Transmission Control Protocol/Internet Protocol suite.

70. The apparatus of claim 64, wherein the controller is further configured to:

determine that the contents of the buffer has breached a threshold;

establish an air-link connection in response to the breach; and

transmit the data units in the buffer.

71. The apparatus of claim 70, wherein transmitting the data units in the buffer includes releasing the data units in the buffer to a radio stack.

72. The apparatus of claim 70, wherein transmitting the data units in the buffer includes releasing the data units in the buffer to a communication protocol stack.

73. The apparatus of claim 58, wherein the controller is further configured to:

receive a data unit of the first packet type from an application;

store the data unit in a buffer; and

transmit an acknowledgement to at least one of the application and an operating system in response to receiving the first data unit.

74. The apparatus of claim 73, wherein the acknowledgement includes information intended to bypass a limit on the number of open sockets that can be simultaneously maintained by a device.

75. The apparatus of claim 74, wherein the limit is policed by at least the operating system.

76. The apparatus of claim 58, wherein the controller is further configured to transmit data units of the first data type in response to the establishment of an air-link connection.