Systems and methods for service flow retention in a wireless communication system

• US 8,385,275 B2
• Filed: 01/31/2009
• Issued: 02/26/2013
• Est. Priority Date: 01/31/2009
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Shi, Guangming Carl, Chin, Tom, Lee, Kuo-Chun
• Primary Examiner(s): Wu, Jianye
• Application Number:
  US12/363,731
• Publication Number:
  US 20100195581A1
• Time in Patent Office: 1,487 Days
• Field of Search: None
• US Class Current: 370/329
• CPC Class Codes: H04W 76/25 Maintenance of established connections
• CPC Class Codes: H04W 76/38 triggered by timers

Abstract

A subscriber station may determine whether a service flow between the subscriber station and a base station is retained during an idle mode of the subscriber station. The subscriber station may reactivate the service flow when the subscriber station exits the idle mode. The subscriber station may monitor whether the service flow has data activity. The subscriber station may delete the service flow if there is no data activity.

Claims

1. A method for service flow retention in a wireless communication system, the method being implemented by a subscriber station, the method comprising:

determining whether to retain a service flow between the subscriber station and a base station during an idle mode of the subscriber station, wherein the determining is based on a data demand metric, and wherein the data demand metric indicates the likelihood that data demand for the service flow will resume within a particular amount of time;

reactivating the service flow when the subscriber station exits the idle mode;

monitoring whether the service flow has data activity; and

deleting the service flow if there is no data activity.

2. The method of claim 1, further comprising storing information about the service flow before the subscriber station enters the idle mode.

3. The method of claim 1, wherein the determining whether to retain the service flow comprises:

adding a new parameter to the service flow that indicates whether the service flow should be retained; and

determining whether to retain the service flow based on the new parameter.

4. The method of claim 1, wherein the reactivating the service flow comprises:

sending, to the base station, a request that the base station verify that there is enough available bandwidth to support the service flow;

receiving a response from the base station based on the request;

changing a set type Quality of Service (QoS) parameter of the service flow to admitted and active if the response indicates there is enough available bandwidth; and

changing the set type QoS parameter of the service flow to provisioned if the response indicates there is not enough available bandwidth.

5. The method of claim 1, wherein the reactivating the service flow comprises:

sending, to the base station, a request that the base station verify that there is enough available bandwidth to support the service flow;

receiving a response from the base station based on the request; and

changing a set type Quality of Service (QoS) parameter of the service flow to provisioned even if the response indicates there is enough available bandwidth.

6. The method of claim 1, wherein the reactivating the service flow comprises renegotiating service flow activation or deactivation with the base station if there is not enough available bandwidth for the service flow.

7. The method of claim 1, wherein the monitoring whether the service flow has data activity comprises:

initializing a counter when the service flow is created;

incrementing the counter when the service flow has no data transmissions during a normal mode;

resetting the counter when the service flow has a data transmission during the normal mode; and

identifying the service flow as not having data activity if the counter exceeds a threshold value.

8. The method of claim 1, wherein the monitoring whether the service flow has data activity comprises:

initializing a timer to zero when the service flow is created;

allowing the timer to run until there is a data transmission;

resetting the timer when the data transmission occurs; and

identifying the service flow as not having data activity if the timer exceeds a threshold value.

9. A subscriber station for service flow retention in a wireless communication system, comprising:

a processor;

memory in electronic communication with the processor; and

instructions stored in the memory, the instructions being executable by the processor to;

determine whether to retain a service flow between the subscriber station and a base station during an idle mode of the subscriber station, wherein the determining whether to retain the service flow is based on a data demand metric, and wherein the data demand metric indicates the likelihood that data demand for the service flow will resume within a particular amount of time;

reactivate the service flow when the subscriber station exits the idle mode;

monitor whether the service flow has data activity; and

delete the service flow if there is no data activity.

10. The subscriber station of claim 9, wherein the instructions are also executable to store information about the service flow before the subscriber station enters the idle mode.

11. The subscriber station of claim 9, wherein the determining whether to retain the service flow comprises:

adding a new parameter to the service flow that indicates whether the service flow should be retained; and

determining whether to retain the service flow based on the new parameter.

12. The subscriber station of claim 9, wherein the reactivating the service flow comprises:

sending, to the base station, a request that the base station verify that there is enough available bandwidth to support the service flow;

receiving a response from the base station based on the request;

changing a set type Quality of Service (QoS) parameter of the service flow to admitted and active if the response indicates there is enough available bandwidth; and

changing the set type QoS parameter of the service flow to provisioned if the response indicates there is not enough available bandwidth.

13. The subscriber station of claim 9, wherein the reactivating of the service flow comprises:

sending to the base station a request that the base station verify that there is enough available bandwidth to support the service flow;

receiving a response from the base station based on the request; and

changing a set type Quality of Service (QoS) parameter of the service flow to provisioned even if the response indicates there is enough available bandwidth.

14. The subscriber station of claim 9, wherein the reactivating the service flow comprises renegotiating service flow activation or deactivation with the base station if there is not enough available bandwidth for the service flow.

15. The subscriber station of claim 9, wherein the monitoring whether the service flow has data activity comprises:

initializing a counter when the service flow is created;

incrementing the counter when the service flow has no data transmissions during a normal mode;

resetting the counter when the service flow has a data transmission during the normal mode; and

identifying the service flow as not having data activity if the counter exceeds a threshold value.

16. The subscriber station of claim 9, wherein the monitoring whether the service flow has data activity comprises:

initializing a timer to zero when the service flow is created;

allowing the timer to run until there is a data transmission;

resetting the timer when the data transmission occurs; and

identifying the service flow as not having data activity if the timer exceeds a threshold value.

17. A subscriber station for service flow retention in a wireless communication system, comprising:

means for determining whether to retain a service flow between the subscriber station and a base station during an idle mode of the subscriber station, wherein determining whether to retain the service flow is based on a data demand metric, and wherein the data demand metric indicates the likelihood that data demand for the service flow will resume within a particular amount of time;

means for reactivating the service flow when the subscriber station exits the idle mode;

means for monitoring whether the service flow has data activity; and

means for deleting the service flow if there is no data activity.

18. The subscriber station of claim 17, further comprising means for storing information about the service flow before the subscriber station enters the idle mode.

19. The subscriber station of claim 17, wherein the means for determining whether the service flow is retained comprises:

means for adding a new parameter to the service flow that indicates whether the service flow should be retained; and

means for determining whether to retain the service flow based on the new parameter.

20. The subscriber station of claim 17, wherein the means for reactivating the service flow comprises:

means for sending, to the base station, a request that the base station verify that there is enough available bandwidth to support the service flow;

means for receiving a response from the base station based on the request;

means for changing a set type Quality of Service (QoS) parameter of the service flow to admitted and active if the response indicates there is enough available bandwidth; and

means for changing the set type QoS parameter of the service flow to provisioned if the response indicates there is not enough available bandwidth.

21. The subscriber station of claim 17, wherein the means for reactivating the service flow comprises:

means for sending, to the base station, a request that the base station verify that there is enough available bandwidth to support the service flow;

means for receiving a response from the base station based on the request; and

means for changing a set type Quality of Service (QoS) parameter of the service flow to provisioned even if the response indicates there is enough available bandwidth.

22. The subscriber station of claim 17, wherein the means for reactivating the service flow comprises renegotiating service flow activation or deactivation with the base station if there is not enough available bandwidth for the service flow.

23. The subscriber station of claim 17, wherein the means for monitoring whether the service flow has data activity comprises:

means for initializing a counter when the service flow is created;

means for incrementing the counter when the service flow has no data transmissions during a normal mode;

means for resetting the counter when the service flow has a data transmission during the normal mode; and

means for identifying the service flow as not having data activity if the counter exceeds a threshold value.

24. The subscriber station of claim 17, wherein the means for monitoring whether the service flow has data activity comprises:

means for initializing a timer to zero when the service flow is created;

means for allowing the timer to run until there is a data transmission;

means for resetting the timer when the data transmission occurs; and

means for identifying the service flow as not having data activity if the timer exceeds a threshold value.

25. A computer-program product for service flow retention in a wireless communication system, the computer-program product comprising a non-transitory computer-readable medium having instructions thereon, the instructions comprising:

code for determining whether to retain a service flow between the subscriber station and a base station during an idle mode of the subscriber station, wherein determining whether to retain the service flow is based on a data demand metric, and wherein the data demand metric indicates the likelihood that data demand for the service flow will resume within a particular amount of time;

code for reactivating the service flow when the subscriber station exits the idle mode;

code for monitoring whether the service flow has data activity; and

code for deleting the service flow if there is no data activity.