IP Library › Granted Patent US 7,127,519
Granted Patent B2
US 7,127,519 · App. 09/848,127 · Granted Oct 24, 2006

Back off methods and systems

Assignee: Lucent Technologies Inc.
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 7,127,519
App. No.
09/848,127
Granted
Oct 24, 2006
Kind
B2
Abstract

A Near Optimal Fairness (NOF) algorithm is disclosed for resolving data collisions in a network shared by a plurality of users. The NOF algorithm calculates an optimal back-off or contention window which is broadcast to users competing for system bandwidth. The NOF algorithm handles data contention in cycles and guarantees that each user competing for system bandwidth within a cycle will make a successful reservation before the cycle ends and a new cycle begins. The size of the back-off window is preferably equal to the number of successful reservations in the previous cycle, and functions as an estimate of the number of competing users in the current cycle.

Claims (30)

1. A method for resolving data collision in a network shared by a plurality of users, the method comprising:

calculating a first back-off window based at least in part on an estimate of a number of users on the network;

sending the first back-off window to a plurality of users of the network;

calculating a second back-off window based at least in part on a smallest integer equal to or greater than a number, which number results from a product of a number of collisions that occurred within the first back-off window and an average of a number of users in the network involved in a collision; and

sending the second back-off window to one or more of the plurality of users of the network.

2. The method of claim 1 , further comprising calculating subsequent back-off windows based at least in part on the number of collisions that occurred within a prior back-off window and sending the subsequent back-off windows to one or more of the plurality of users of the network.

3. The method of claim 1 , further comprising initiating a cycle with a number of users that can compete for network resources during the cycle.

4. The method of claim 3 , wherein calculating the second back-off window comprises calculating the second back-off window in the same cycle as the step of calculating the first back-off window.

5. The method of claim 3 , further comprising ending the cycle when there are no collisions within a back-off window.

6. The method of claim 3 , further comprising initiating a second cycle subsequent to the first cycle with a number of users that can compete for network resources during the second cycle.

7. The method of claim 3 , wherein initiating a cycle comprises initiating a cycle based on a number of users that successfully reserved network resources during a prior cycle.

8. The method of claim 1 , wherein the step of calculating the second back-off window based at least in part on the number of collisions that occurred within the first back-off window comprises calculating the second back-off window based on the product of the number of collisions that occurred within the first back-off window and a value for the average of number of users in the network involved in a collision of approximately 2.3922.

9. A method for resolving data collision in a network shared by a plurality of users, the method comprising:

sending a first back-off window to a plurality of users of the network;

calculating a second back-off window based at least in part on a smallest integer equal to or greater than a number, which number results from product of the number of users that collided while attempting to reserve network resources during the first back-off window and an average of number of users in the network involved in a collision;

sending the second back-off window to one or more of the plurality of users of the network; and

limiting network reservation attempts in the second back-off window to users that collided while attempting to reserve network resources during the first back-off window.

10. The method of claim 9 , further comprising calculating subsequent back-off windows based on a number of users that collided in a prior back-off window and sending the subsequent back-off windows to one or more of the plurality of users of the network.

11. The method of claim 10 , further comprising limiting network reservation attempts in the subsequent back-off windows to the users that collided while attempting to reserve network resources during a prior back-off window.

12. The method of claim 9 , further comprising initiating a first cycle with a number of users that can compete for network resources during the cycle.

13. The method of claim 12 , further comprising initiating a second cycle when no collisions occurred during a back-off window in the first cycle.

14. The method of claim 9 , wherein the step of calculating the second back-off window based at least in part on the number of users that collided while attempting to reserve network resources during the first back-off window comprises calculating the second back-off window based on a product of the number of collisions that occurred within the first back-off window and a value for the average of number of users in the network involved in a collision of approximately 2.3922.

15. A system for resolving data collisions in a shared network, comprising:

a plurality of remote devices; and an access point in communication with the plurality of remote devices, wherein the access point further comprises:

a switch for communicating with the plurality of remote devices;

a transceiver for sending information to and receiving information from the plurality of remote devices; and a collision resolution device communicably coupled to the transceiver and the switch, wherein the collision resolution device sends an initial back-off window to the plurality of remote devices;

wherein the collision resolution device calculates and sends a subsequent back-off window based at least in part on a smallest integer equal to or greater than a number, which number results from a product of a number of collisions that occurred within the within the first back-off window and an average number of users in the network involved in a collision; and

wherein the collision resolution device limits the remote devices that can compete for network resources in the subsequent back-off window to remote devices that unsuccessfully attempted to reserve network resources in the initial back-off window.

16. The system of claim 15 , wherein the size of the initial back-off window is based on an estimate of remote devices competing for network resources.

17. The system of claim 15 , wherein the subsequent back-off window is calculated based at least in part on a product of the number of collisions that occurred within the initial back-off window and a value of 2.3922.

Assignments (3)
RELEASE OF SECURITY INTEREST Recorded Oct 9, 2014
From: CREDIT SUISSE AG
To: ALCATEL-LUCENT USA INC.
Reel/Frame 033950/0261 →
SECURITY INTEREST Recorded Mar 7, 2013
From: ALCATEL-LUCENT USA INC.
To: CREDIT SUISSE AG
Reel/Frame 030510/0627 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 29, 2001
From: LI, CHIH-PENG
To: LUCENT TECHNOLOGIES, INC.
Reel/Frame 012148/0916 →
Continuity (1)
Related Publication 20020188750A1 · Dec 12, 2002