REVERSE LINK CONTROL TO REDUCE FORWARD LINK LATENCY

• US 20130044599A1
• Filed: 08/16/2011
• Published: 02/21/2013
• Est. Priority Date: 08/16/2011
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Cherian, George, He, Linhai, Ghosh, Donna, Lott, Christopher Gerard, Attar, Rashid Ahmed Akbar
• Granted Patent: US 9,900,799 B2
• Time in Patent Office: Days
• US Class Current: 370/235
• CPC Class Codes: H04L 47/2433 Allocation of priorities to traffic types
• CPC Class Codes: H04W 28/0205 at the air interface dynamic wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 72/569 of the traffic information

Abstract

Some implementations provide a method for prioritizing reverse link packets so that particular reverse link packets are transmitted with a reduced latency in order to improve spectral efficiency of the forward link. The method also optionally includes weighting packets according to their determined lengths, and transmitting packets based on the determined weights. In one implementation, the method includes sorting packets at least according to one of size, type and nature of the data in the packets. Accordingly, sorting of the packets includes at least one of determining the size and the type of each packet. In one implementation, sorting the packets includes deep-packet inspection to determine a respective priority value for each packet.

Claims

1. A method comprising:

determining a respective priority for one or more reverse link packets, wherein the respective priority for a reverse link packet is based on at least the estimated impact of the delay in sending the reverse link packet on a corresponding forward link; and

transmitting reverse link packets based on at least the determined priority for the reverse link packets.

2. The method of claim 1, wherein the estimated impact includes at least one of an estimate of the amount of time the forward link may be idle, an estimate of the likelihood that the forward link may be idle, and an estimated measure of the underutilization of the forward link.

3. The method of claim 1, further comprising:

receiving an indicator of a measure of a reverse link data rate; and

determining the priorities for the packets based at least in part on the indicator of the reverse link data rate.

4. The method of claim 3, further comprising comparing the indicator to a threshold value.

5. The method of claim 4, wherein the threshold includes a lower bound, below which an access terminal can expect lower than nominal data rates on the reverse link to an access point.

6. The method of claim 4, wherein the threshold is an upper bound, above which an access terminal can expect lower than nominal data rates on the reverse link to an access point.

7. The method of claim 4, further comprising transmitting unsorted packets when the indicator does not breach the threshold value.

8. The method of claim 1, further comprising determining at least one of the packet, type of the packet and the nature of the data included in the packet, wherein the estimated impact is based at least on one of the size of the packet, type of the packet and the nature of the data included in the packet.

9. The method of claim 1, wherein determining a respective priority for one or more reverse link packets includes:

determining the length of a packet; and

prioritizing the packet based at least on the determined length.

10. The method of claim 9, wherein prioritization based on at least on the determined length includes favoring packets below a particular length threshold.

11. The method of claim 1, wherein determining a respective priority for one or more reverse link packets includes:

determining the type of a packet; and

prioritizing the packet based at least on the determined type.

12. The method of claim 11, wherein prioritization based on at least on the determined type includes favoring particular types.

13. The method of claim 1, wherein determining a respective priority for one or more reverse link packets includes:

determining the nature of the data included in the packet; and

prioritizing the packet based at least on the determined nature of the data.

14. The method of claim 13, wherein determining the nature of the data includes deep-packet inspection of the packet.

15. The method of claim 13, wherein prioritization based on at least on the determined nature of the data includes favoring particular types of data.

16. The method of claim 15, wherein GET packets for advertising information are given a low priority.

17. The method of claim 15, wherein DNS packets are given a relatively high priority.

18. The method of claim 1, wherein determining a respective priority for one or more reverse link packets includes:

determining whether the packet is related to a foreground or background application; and

prioritizing the packet based at least on whether the packet is related to a foreground or background application.

19. The method of claim 18, wherein determining whether the packet is related to a foreground or background application is based at least in part on information from an operating system managing applications on an access terminal.

20. The method of claim 1, further comprising:

sorting prioritized packets into respective queues for corresponding priority levels;

setting at least one frequency of service value for each priority level; and

servicing the respective queues based at least on the corresponding frequency of service value for the respective priority level.

21. The method of claim 20, wherein at least one frequency of service value is based on a particular priority level and an indicator of the reverse link data rate.

22. The method of claim 20, wherein the priority levels are rank based at least on one of the estimated impact includes at least one of an estimate of the amount of time the forward link may be idle, an estimate of the likelihood that the forward link may be idle, and an estimated measure of the underutilization of the forward link.

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

determine a respective priority for one or more reverse link packets, wherein the respective priority for a reverse link packet is based on at least the estimated impact of the delay in sending the reverse link packet on a corresponding forward link; and

transmit reverse link packets based on at least the determined priority for the reverse link packets.

24. The computer program product of claim 23, wherein the estimated impact includes at least one of an estimate of the amount of time the forward link may be idle, an estimate of the likelihood that the forward link may be idle, and an estimated measure of the underutilization of the forward link.

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

receive an indicator of a measure of a reverse link data rate; and

determine the priorities for the packets based at least in part on the indicator of the reverse link data rate.

26. The computer program product of claim 25, further comprising instructions that when executed cause an apparatus to compare the indicator to a threshold value.

27. The computer program product of claim 26, wherein the threshold includes a lower bound, below which an access terminal can expect lower than nominal data rates on the reverse link to an access point.

28. The computer program product of claim 26, wherein the threshold is an upper bound, above which an access terminal can expect lower than nominal data rates on the reverse link to an access point.

29. The computer program product of claim 26, further comprising instructions that when executed cause an apparatus to transmit unsorted packets when the indicator does not breach the threshold value.

30. The computer program product of claim 23, further comprising instructions that when executed cause an apparatus to determine at least one of the packet, type of the packet and the nature of the data included in the packet, wherein the estimated impact is based at least on one of the size of the packet, type of the packet and the nature of the data included in the packet.

31. The computer program product of claim 23, wherein determining a respective priority for one or more reverse link packets further comprises instructions that when executed cause an apparatus to:

determine the length of a packet; and

prioritize the packet based at least on the determined length.

32. The computer program product of claim 31, wherein prioritization based on at least on the determined length includes favoring packets below a particular length threshold.

33. The computer program product of claim 23, wherein determining a respective priority for one or more reverse link packets further comprises instructions that when executed cause an apparatus to:

determine the type of a packet; and

prioritize the packet based at least on the determined type.

34. The computer program product of claim 33, wherein prioritization based on at least on the determined type includes favoring particular types.

35. The computer program product of claim 23, wherein determining a respective priority for one or more reverse link packets further comprises instructions that when executed cause an apparatus to:

determine the nature of the data included in the packet; and

prioritize the packet based at least on the determined nature of the data.

36. The computer program product of claim 35, wherein determining the nature of the data further comprises instructions that when executed cause an apparatus to perform deep-packet inspection of the packet.

37. The computer program product of claim 35, wherein prioritization based on at least on the determined nature of the data further comprises instructions that when executed cause an apparatus to favor particular types of data.

38. The computer program product of claim 37, wherein GET packets for advertising information are given a low priority.

39. The computer program product of claim 37, wherein DNS packets are given a relatively high priority.

40. The computer program product of claim 23, wherein determining a respective priority for one or more reverse link packets further comprises instructions that when executed cause an apparatus to:

determine whether the packet is related to a foreground or background application; and

prioritize the packet based at least on whether the packet is related to a foreground or background application.

41. The computer program product of claim 40, wherein determining whether the packet is related to a foreground or background application is based at least in part on information from an operating system managing applications on an access terminal.

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

sort prioritized packets into respective queues for corresponding priority levels;

set at least one frequency of service value for each priority level; and

service the respective queues based at least on the corresponding frequency of service value for the respective priority level.

43. The computer program product of claim 42, wherein at least one frequency of service value is based on a particular priority level and an indicator of the reverse link data rate.

44. The computer program product of claim 42, wherein the priority levels are rank based at least on one of the estimated impact includes at least one of an estimate of the amount of time the forward link may be idle, an estimate of the likelihood that the forward link may be idle, and an estimated measure of the underutilization of the forward link.

45. An apparatus comprising:

means for determining a respective priority for one or more reverse link packets, wherein the respective priority for a reverse link packet is based on at least the estimated impact of the delay in sending the reverse link packet on a corresponding forward link; and

means for transmitting reverse link packets based on at least the determined priority for the reverse link packets.

46. The apparatus of claim 45, wherein the estimated impact includes at least one of an estimate of the amount of time the forward link may be idle, an estimate of the likelihood that the forward link may be idle, and an estimated measure of the underutilization of the forward link.

47. The apparatus of claim 45, further comprising:

means for receiving an indicator of a measure of a reverse link data rate; and

means for determining the priorities for the packets based at least in part on the indicator of the reverse link data rate.

48. The apparatus of claim 47, further comprising means for comparing the indicator to a threshold value.

49. The apparatus of claim 48, wherein the threshold includes a lower bound, below which an access terminal can expect lower than nominal data rates on the reverse link to an access point.

50. The apparatus of claim 48, wherein the threshold is an upper bound, above which an access terminal can expect lower than nominal data rates on the reverse link to an access point.

51. The apparatus of claim 48, further comprising means for transmitting unsorted packets when the indicator does not breach the threshold value.

52. The apparatus of claim 45, further comprising means for determining at least one of the packet, type of the packet and the nature of the data included in the packet, wherein the estimated impact is based at least on one of the size of the packet, type of the packet and the nature of the data included in the packet.

53. The apparatus of claim 45, wherein said means for determining a respective priority for one or more reverse link packets includes:

means for determining the length of a packet; and

means for prioritizing the packet based at least on the determined length.

54. The apparatus of claim 53, wherein prioritization based on at least on the determined length includes favoring packets below a particular length threshold.

55. The apparatus of claim 45, wherein said means for determining a respective priority for one or more reverse link packets includes:

means for determining the type of a packet; and

means for prioritizing the packet based at least on the determined type.

56. The apparatus of claim 55, wherein prioritization based on at least on the determined type includes favoring particular types.

57. The apparatus of claim 45, wherein said means for determining a respective priority for one or more reverse link packets includes:

means for determining the nature of the data included in the packet; and

means for prioritizing the packet based at least on the determined nature of the data.

58. The apparatus of claim 57, wherein said means for determining the nature of the data includes means for performing deep-packet inspection of the packet.

59. The apparatus of claim 57, wherein prioritization based on at least on the determined nature of the data includes favoring particular types of data.

60. The apparatus of claim 59, wherein GET packets for advertising information are given a low priority.

61. The apparatus of claim 59, wherein DNS packets are given a relatively high priority.

62. The apparatus of claim 45, wherein said means for determining a respective priority for one or more reverse link packets includes:

means for determining whether the packet is related to a foreground or background application; and

means for prioritizing the packet based at least on whether the packet is related to a foreground or background application.

63. The apparatus of claim 62, wherein said means for determining whether the packet is related to a foreground or background application is based at least in part on information from an operating system managing applications on an access terminal.

64. The apparatus of claim 45, further comprising:

means for sorting prioritized packets into respective queues for corresponding priority levels;

means for setting at least one frequency of service value for each priority level; and

means for servicing the respective queues based at least on the corresponding frequency of service value for the respective priority level.

65. The apparatus of claim 64, wherein at least one frequency of service value is based on a particular priority level and an indicator of the reverse link data rate.

66. The apparatus of claim 64, wherein the priority levels are rank based at least on one of the estimated impact includes at least one of an estimate of the amount of time the forward link may be idle, an estimate of the likelihood that the forward link may be idle, and an estimated measure of the underutilization of the forward link.

67. An apparatus comprising:

a controller configured to determine a respective priority for one or more reverse link packets, wherein the respective priority for a reverse link packet is based on at least the estimated impact of the delay in sending the reverse link packet on a corresponding forward link, and transmit reverse link packets based on at least the determined priority for the reverse link packets.

68. The apparatus of claim 67, wherein the estimated impact includes at least one of an estimate of the amount of time the forward link may be idle, an estimate of the likelihood that the forward link may be idle, and an estimated measure of the underutilization of the forward link.

69. The apparatus of claim 67, wherein the controller is further configured to:

receive an indicator of a measure of a reverse link data rate; and

determine the priorities for the packets based at least in part on the indicator of the reverse link data rate.

70. The apparatus of claim 69, wherein the controller is further configured to compare the indicator to a threshold value.

71. The apparatus of claim 70, wherein the threshold includes a lower bound, below which an access terminal can expect lower than nominal data rates on the reverse link to an access point.

72. The apparatus of claim 70, wherein the threshold is an upper bound, above which an access terminal can expect lower than nominal data rates on the reverse link to an access point.

73. The apparatus of claim 70, wherein the controller is further configured to transmit unsorted packets when the indicator does not breach the threshold value.

74. The apparatus of claim 67, wherein the controller is further configured to determine at least one of the packet, type of the packet and the nature of the data included in the packet, wherein the estimated impact is based at least on one of the size of the packet, type of the packet and the nature of the data included in the packet.

75. The apparatus of claim 67, wherein in order to determine a respective priority for one or more reverse link packets the controller is further configured to:

determine the length of a packet; and

prioritize the packet based at least on the determined length.

76. The apparatus of claim 75, wherein prioritization based on at least on the determined length includes favoring packets below a particular length threshold.

77. The apparatus of claim 67, wherein in order to determine a respective priority for one or more reverse link packets the controller is further configured to:

determine the type of a packet; and

prioritize the packet based at least on the determined type.

78. The apparatus of claim 77, wherein prioritization based on at least on the determined type includes favoring particular types.

79. The apparatus of claim 67, wherein in order to determine a respective priority for one or more reverse link packets the controller is further configured to:

determine the nature of the data included in the packet; and

prioritize the packet based at least on the determined nature of the data.

80. The apparatus of claim 79, wherein in order to determine the nature of the data the controller is further configured to perform deep-packet inspection of the packet.

81. The apparatus of claim 79, wherein in order to prioritize based on at least on the determined nature of the data the controller is further configured to favor particular types of data.

82. The apparatus of claim 81, wherein GET packets for advertising information are given a low priority.

83. The apparatus of claim 81, wherein DNS packets are given a relatively high priority.

84. The apparatus of claim 67, wherein in order to determine a respective priority for one or more reverse link packets the controller is further configured to:

determine whether the packet is related to a foreground or background application; and

prioritize the packet based at least on whether the packet is related to a foreground or background application.

85. The apparatus of claim 84, wherein determining whether the packet is related to a foreground or background application is based at least in part on information from an operating system managing applications on an access terminal.

86. The apparatus of claim 67, wherein the controller is further configured to:

sort prioritized packets into respective queues for corresponding priority levels;

set at least one frequency of service value for each priority level; and

service the respective queues based at least on the corresponding frequency of service value for the respective priority level.

87. The apparatus of claim 86, wherein at least one frequency of service value is based on a particular priority level and an indicator of the reverse link data rate.

88. The apparatus of claim 86, wherein the priority levels are rank based at least on one of the estimated impact includes at least one of an estimate of the amount of time the forward link may be idle, an estimate of the likelihood that the forward link may be idle, and an estimated measure of the underutilization of the forward link.