doc.: IEEE 802.11-01/560r1 Submission John Kowalski, Sharp November 2001 Adding Rate Parameter to...

November 2001 doc.: IEEE 802.11-01/560r1

Submission

John Kowalski, Sharp

Adding Rate Parameter to the TSPEC /Queue State

ElementJohn Kowalski

Sharp

November 2001 doc.: IEEE 802.11-01/560r1

Submission

John Kowalski, Sharp

Outline

• Why it’s needed and how to get it?• Proposed Normative Text changes• Motion!

November 2001 doc.: IEEE 802.11-01/560r1

Submission

John Kowalski, Sharp

Why it’s needed:

• Currently there’s NO standardized method or requirement for rate negotiation.

• Rate negotiation can be “sped up” if the MAC can suggest a rate to start from- if it’s below that rate, stop the negotiation right there. If it’s above the rate, all the better.

• A PHY RATE NEEDS TO BE NEGOTIATED BEFORE THE OVERALL TXOP CAN BE GRANTED! THIS IS A MAC LAYER FUNCTION!

November 2001 doc.: IEEE 802.11-01/560r1

Submission

John Kowalski, Sharp

How to get it?

• Previous statistics • RSSL• Etc.

November 2001 doc.: IEEE 802.11-01/560r1

Submission

John Kowalski, Sharp

Proposed Normative Text Changes (1)

• After Maximum Burst Size (7.3.2.15

{Maximum TXOP} , add 2 octets:– 1 octet for Rate information

(unsigned, each bit = 0.5 Mbps.)– 1 reserved octet.

• (The latter is a good idea for growth, “c.y.a.” ...)

November 2001 doc.: IEEE 802.11-01/560r1

Submission

John Kowalski, Sharp

Proposed Normative Text Changes (2)

• {After definition of Maximum Burst size in 7.3.2.15 add the following Normative Text:}

• {In Peter Johanssen’s Queue State proposal, add the following text at the bottom of the normative text (not the note) in 7.3.2.22:}

“The Rate field gives the minimum rate necessary for successful transport under this TXOP. It is an 8 bit unsigned integer; each bit represents 0.5 Mbps. ”

November 2001 doc.: IEEE 802.11-01/560r1

Submission

John Kowalski, Sharp

Additional Comment (informative)

• “This rate information is used to ensure that the TSPEC negotiated is sufficient to match the required throughput for transmission. In a typical implementation, a TSPEC is not granted if the transmitter and receiver cannot transmit in such a way as to meet the TSPEC at or above the PHY rate specified in this field. This parameter is used to ensure that data flows into the MAC can be supported over the air.”

November 2001 doc.: IEEE 802.11-01/560r1

Submission

John Kowalski, Sharp

MOTION:

• To incorporate the changes outlined in this presentation as normative text for the draft of 802.11e.