Method for controlling resource allocation in a wireless communication system

• US 20040253940A1
• Filed: 06/11/2003
• Published: 12/16/2004
• Est. Priority Date: 06/11/2003
• Status: Active Grant

• Current Assignee: RPX Corporation
• Original Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Inventors: Bi, Qi, Yang, Yang, Stolyar, Aleksandr, Jiang, Frances, Andrews, Daniel Matthew
• Granted Patent: US 8,730,923 B2
• Time in Patent Office: Days
• US Class Current: 455/405
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/11 Identifying congestion
• CPC Class Codes: H04L 47/12 Avoiding congestion; Recovering from congestion
• CPC Class Codes: H04L 47/20 Traffic policing
• CPC Class Codes: H04L 47/225 Determination of shaping rate, e.g. using a moving window
• CPC Class Codes: H04L 47/245 using preemption
• CPC Class Codes: H04L 47/27 Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/762 triggered by the network
• CPC Class Codes: H04L 47/805 QOS or priority aware
• CPC Class Codes: H04L 47/822 Collecting or measuring resource availability data
• CPC Class Codes: H04L 47/824 Applicable to portable or mobile terminals
• CPC Class Codes: H04W 24/00 Supervisory, monitoring or testing arrangements
• CPC Class Codes: H04W 28/02 Traffic management, e.g. flow control or congestion control
• CPC Class Codes: H04W 28/18 Negotiating wireless communication parameters
• CPC Class Codes: H04W 28/24 Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
• CPC Class Codes: H04W 48/06 based on traffic conditions
• CPC Class Codes: H04W 72/0446 Resources in time domain, e.g. slots or frames
• CPC Class Codes: H04W 8/04 Registration at HLR or HSS [Home Subscriber Server]
• CPC Class Codes: H04W 88/08 Access point devices

Abstract

A resource allocation algorithm identifies a resource hogger in a wireless communication system data sharing arrangement and control shared resource overuse by the resource hogger. In one embodiment, the base station for a given sector in the system tracks the time-slot usage of each active user in the sector. If the usage for any user reaches a predetermined hogger threshold, normal target QoS enforcement is suspended for that user to allow more time slots to be allocated to the other, non-hogger users. When the resource hogger user'"'"'s usage falls below the threshold, target QoS enforcement is returned to that user. Temporarily suspending target QoS enforcement for resource hoggers and allocating the remaining resources to other users prevents resource hoggers from deteriorating performance of the entire system.

Claims

1. A method of controlling resource allocation in a wireless communication system, comprising:

determining whether at least one user is a hogger based on a timeslot usage; and

suspending target QoS requirement enforcement for said at least one user if said at least one user is determined to be a hogger.

2. The method of claim 1, wherein the determining step comprises calculating an estimated timeslot usage over a sliding window containing a plurality of timeslots.

3. The method of claim 1, further comprising calculating an average number of users over the sliding window.

4. The method of claim 1, wherein the determining step comprises comparing a timeslot usage of said at least one user with a hogger threshold.

5. The method of claim 4, further comprising calculating an average number of users over a sliding window containing a plurality of timeslots, and wherein the hogger threshold used in the comparing step is based on the average number of users.

6. The method of claim 4, wherein the hogger threshold used in the comparing step is based on an actual number of users accessing the system during the comparing step.

7. The method of claim 4, wherein the hogger threshold used in the comparing step is a maximum absolute timeslot usage value that is independent of a number of users accessing the system.

8. The method of claim 1, wherein the suspending step comprises conducting a minimum QoS requirement enforcement for the hogger.

9. A method of controlling resource allocation in a wireless communication system having a plurality of users, comprising:

determining whether at least one user is a hogger based on a timeslot usage;

enforcing target QoS requirements for at least one of said plurality of user that is not identified as the hogger;

suspending target QoS requirement enforcement for the hogger; and

updating a user-realized performance for said at least one of plurality of users not identified as the hogger.

10. The method of claim 9, wherein the determining step comprises calculating an estimated timeslot usage over a sliding window containing a plurality of timeslots.

11. The method of claim 9, further comprising calculating an average number of users over the sliding window.

12. The method of claim 9, wherein the determining step comprises comparing a timeslot usage of said at least one user with a hogger threshold.

13. The method of claim 12, further comprising calculating an average number of users over a sliding window containing a plurality of timeslots, and wherein the hogger threshold used in the comparing step is based on the average number of users.

14. The method of claim 12, wherein the hogger threshold used in the comparing step is based on an actual number of users accessing the system during the comparing step.

15. The method of claim 12, wherein the hogger threshold used in the comparing step is a maximum absolute timeslot usage value that is independent of a number of users accessing the system.

16. The method of claim 9, wherein the suspending step comprises conducting a minimum QoS requirement enforcement for the hogger.

17. The method of claim 16, further comprising:

determining a priority for each of said plurality of users not identified as the hogger based on the target QoS requirement; and

determining a priority for each of said plurality of users identified as the hogger based on the minimum QoS requirement.

18. The method of claim 17, wherein the updating step comprises:

updating the user-realized performance for said plurality of users not identified as the hogger based on the target QoS requirement; and

updating the user-realized performance for said plurality of users identified as the hogger based on the minimum QoS requirement.