IP Library Granted Patent US 8,638,662
Granted Patent B2
US 8,638,662 · App. 13/179,924 · Granted Jan 28, 2014

Method of implementing packet-based resource allocation and persistent resource allocation in a wireless communication system

Inventors: Stan Vitebsky (Morristown, NJ); Yang Yang (Parsippany, NJ)
Assignee: Alcatel Lucent
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,638,662
App. No.
13/179,924
Granted
Jan 28, 2014
Kind
B2
Abstract

The present invention provides a method of allocating resources in a wireless communication system. The method includes requesting persistent allocation of resources for a data spurt in response to detecting the beginning of the data spurt and performing non-persistent resource allocation for at least one packet in the data spurt. The non-persistent resource allocation is performed in response to determining that persistent resources are not available for allocation. The method also includes transmitting the packet using the allocated non-persistent resources.

Claims (25)

1. A scheduler for use in a wireless communication system comprising: one or more processors having; the scheduler being configured to:

receive requests for persistent allocation of resources for a data spurt in response to determining that the data spurt is ready for transmission over an air interface; and

perform non-persistent resource allocation for at least one packet in the data spurt in response to determining that persistent resources are not available for allocation, wherein determining that persistent resources are not available for allocation comprises determining that an elapsed time since detection of the beginning of the data spurt has exceeded a predetermined threshold value prior to the persistent allocation of the resources.

2. A scheduler for use in a wireless communication system comprising: one or more processors having; the scheduler being configured to:

receive requests for persistent allocation of resources for a data spurt in response to determining that the data spurt is ready for transmission over an air interface; and

perform non-persistent resource allocation for at least one packet in the data spurt in response to determining that persistent resources are not available for allocation, wherein determining that persistent resources are not available for allocation comprises determining that an overhead associated with persistent resource allocation is larger than an overhead associated with non-persistent resource allocation.

3. The scheduler of claim 1 or 2 , wherein the scheduler is configured to receive requests for persistent allocation of resources for the data spurt provided by at least one of a voice application, a Voice over Internet Protocol (VoIP) application, a video telephony application, a push-to-talk application, a streaming video application, a constant bit rate application, or a guaranteed bit rate application.

4. The scheduler of claim 1 or 2 , wherein the scheduler is configured to receive requests for at least one of a timeslot, frequency, code sequence, tone, sub-carrier, tile, resource block, base node, or power.

5. The scheduler of claim 1 or 2 , wherein the scheduler is configured to:

perform persistent resource allocation for the data spurt; and

switch from persistent resource allocation to non-persistent resource allocation in response to determining that an overhead associated with persistent resource allocation is larger than an overhead associated with non-persistent resource allocation.

6. The scheduler of claim 1 or 2 , wherein the scheduler is configured to determine whether resources for the data spurt can be persistently allocated.

7. The scheduler of claim 6 , wherein the scheduler is configured to determine that resources for the data spurt can be persistently allocated when an overhead associated with persistent allocation is less than an overhead associated with non-persistent allocation.

8. The scheduler of claim 6 , wherein the scheduler is configured to monitor at least one condition for completing the persistent allocation and determine whether said at least one condition for completing the persistent allocation is satisfied.

9. The scheduler of claim 7 , wherein the scheduler is configured to monitor said at least one condition concurrently with performing the non-persistent resource allocation for said at least one packet and transmitting said at least one packet using the allocated non-persistent resources.

10. The scheduler of claim 6 , wherein the scheduler is configured to perform persistent allocation of resources to the data spurt so that at least a portion of the data spurt can be transmitted using the persistently allocated resources.

11. The scheduler of claim 10 , wherein the scheduler is configured to end non-persistent allocation of resources to packets in the data spurt.

12. The scheduler of claim 11 , wherein the scheduler is configured to perform persistent allocation of resources concurrently with non-persistent allocation of resources for a selected period of time prior to ending non-persistent allocation of resources.

13. The scheduler of claim 12 , wherein the scheduler is configured to select the period of time for concurrent persistent and non-persistent allocation of resources.

14. The scheduler of claim 13 , wherein the scheduler is configured to select the period of time based upon at least one of a number of packets in a queue or a target packet latency.

15. The scheduler of claim 6 , wherein the scheduler is configured to:

monitor at least one condition for completing the persistent allocation;

determine that said at least one condition for completing the persistent allocation is not satisfied; and

resume non-persistent allocation of resources to at least one packet in the data spurt in response to determining that said at least one condition for completing the persistent allocation is not satisfied.

16. The scheduler of claim 1 or 2 , wherein the scheduler is configured to detect the beginning of the data spurt in response to initiation of a new data spurt, initiation of an application that provides the data spurt, or handoff of a communication session.

Assignments (9)
RELEASE OF SECURITY INTEREST Recorded May 21, 2019
From: BANK OF AMERICA, N.A.
To: LGS INNOVATIONS LLC
Reel/Frame 049247/0557 →
RELEASE OF SECURITY INTEREST Recorded May 2, 2019
From: BANK OF AMERICA, N.A.
To: LGS INNOVATIONS LLC
Reel/Frame 049074/0094 →
NOTICE OF GRANT OF SECURITY INTEREST IN PATENTS Recorded Jul 19, 2017
From: LGS INNOVATIONS LLC
To: BANK OF AMERICA, N.A.
Reel/Frame 043254/0393 →
RELEASE OF SECURITY INTEREST Recorded Oct 9, 2014
From: CREDIT SUISSE AG
To: ALCATEL-LUCENT USA INC.
Reel/Frame 033949/0016 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 23, 2014
From: ALCATEL LUCENT
To: LGS INNOVATIONS LLC
Reel/Frame 032743/0584 →
RELEASE OF SECURITY INTEREST Recorded Apr 1, 2014
From: CREDIT SUISSE AG
To: ALCATEL-LUCENT USA INC.
Reel/Frame 032578/0931 →
SECURITY INTEREST Recorded Apr 1, 2014
From: LGS INNOVATIONS LLC
To: BANK OF AMERICA NA
Reel/Frame 032579/0066 →
MERGER Recorded Mar 5, 2014
From: LUCENT TECHNOLOGIES INC.
To: ALCATEL-LUCENT USA INC.
Reel/Frame 032354/0009 →
SECURITY INTEREST Recorded Mar 7, 2013
From: ALCATEL-LUCENT USA INC.
To: CREDIT SUISSE AG
Reel/Frame 030510/0627 →
Continuity (2)
Continuation 11946205 · Nov 28, 2007
Related Publication 20110261789A1 · Oct 27, 2011