Doc.: IEEE 802.11-Yy/Xxxxr1

Doc.: IEEE 802.11-Yy/Xxxxr1

April 2011 doc.:IEEE 802.11-11/0518r1

IEEE P802.11
Wireless LANs

Few clarifications and fixes
Date: 07 April 2011
Author(s):
Name / Affiliation / Address / Phone / email
Solomon Trainin / Intel Corporation / 972547885738 / s
Kasher Assaf / Intel Corporation /
Carlos Cordeiro / Intel Corporation /
Gal Basson / Wilocity /
CID / Page / Line / Clause / Duplicate of CID / Resn Status / Comment / Proposed Change
2286 / 183.00 / 40 / 9.2.11 / C / The DBand CTS contains two address fields that allows to provide address of the intended receiver even in the DBand CTS to self as well that makes sense for NAV identification. / Change format of the DBand CTS to self and implement relevant changes in the NAV section.
2284 / 185.00 / 1 / 9.6.0g / C / Specific case of Low Power PHY is not covered. The rule to decide about the BA and BAR MCS is not clear. / Provide rule for response to the frames transmitted by Low Power PHY. Provide separate definition of the BA and BAR MCS.
2285 / 187.00 / 35 / 9.7d.1 / C / Aggregation of the BA frame in an A-MPDU is limited to placed at first in the A-MPDU and to contain single copy only. There is no need for such a limitation for Tgad. / Provide definition to allow multiple copies of BA inside the A-MPDU
2287 / 247.00 / 26 / 9.25.5.1 / C / In some cases when a frame is sent as part of the TxSS or RxSS sequence the accumulated drift may cause contention with the responding STA. / Provide solution to eliminate contention when responding to the sweeping sequence.
2067 / 232.00 / 9 / 9.25.1.1.2 / C / RXSS as defined in the specification will have interoperability problems due to the tolerance on SBIFS and the accumulation of errors over multiple packets in the sweep. The receiving station will not know when to switch its antenna array configuration. / Modify RXSS to resolve this problem. A contribution to 802.11ad on this topics is being developed.

CID2284

Editor: modify as follows:

9.6.0g

A control frame that is not BA, nor BAR and that is not a control response frame shall be transmitted by a DBand STA using an MCS from the mandatory MCS set of the DBand SC modulation class or using DBand Control modulation class, or using the DBand low power SC modulation class.

A DBand control response frame that is not a BA, nor ACK frame shall be transmitted using the same type of PHYmodulation class as the frame that elicited the response and shall use the highest mandatory MCS index that is the same as or lower than the MCS of the frame that elicited the response.

A DBand STA transmitting ACK or BA frame that is a response to a frame sent using DBand low power SC modulation class shall use the same modulation class and the MCS chosen from the DBand low power SC Supported MCS set of the STA that transmitted the frame that solicited the response. The MCS index shall be the same as or lower than the MCS of the frame that solicited the response.

A DBand STA transmitting ACK or BA frame that is a response to a frame sent using DBand Control modulation class shall use DBand Control modulation class.

A DBand STA transmitting ACK frame or BA frame in response to a frame sent using DBand SC modulation class or DBand OFDM modulation class shall use an MCS from the mandatory MCS set of the DBand SC modulation class and shall use the highest MCS index that the Data Rate is the same as or lower than that of the frame that elicited the response.

A DBand STA transmitting a BAR frame that is not a response transmission may use any MCS supported by the receiver as reported in its Supported MCS set.

A DBand STA transmitting a BA frame that is a response transmission shall transmit the frame using the same modulation class as the frame that solicited the response and the MCS chosen from the

Supported MCS set of the STA that transmitted the frame that solicited the response.

CID2287

CID2067

Editor: modify as follows:

9.2.3.6 SBIFS

to vary from the nominal SBIFS value (aSBIFSTime) by more than +0.031 usec±10% of aSBIFSTime.

------

Editor: modify as follows:

9.23.3 AT transmission rules

The PCP/AP shall not start transmission of a request frame sooner than a MAX (guard time, 3*SIFS time) (9.23.6.4 Guard time) following the end of the previous BTI or A-BFT when present in the BI.

Editor: modify P247L39 of Spec 1.1 as follows:

begin an RSS (9.25.1.2) 3* SIFS time following the completion of an ISS, provided there is sufficient time in the allocation for the responder to transmit an ScS frame and the responder received an ScS frame from the initiator during the ISS. If the end of the allocation is reached and the responder did not

Editor: modify P248L9of Spec 1.1 as follows:

The initiator shall begin an ScS Feedback (9.25.1.3) 3*SIFS time following the completion of an RSS,

Editor: modify the first line in 9.25.4.1 as follows:

The PCP/AP shall allocate an A-BFT period 3*SIFS time following the completion of a BTI that

Editor: modify P231L20-22 as follows:

responder TXSS has the CDOWN field set to zero. Each transmitted ScS frame shall be separated by an interval of time equal to SBIFS, except if the allocation ends as described in 9.25.3and9.25.5or if the end of an ScS slot is reached as described in9.25.4 or when the responder completed a full sweep of all its transmit sectors and is ready to transmit to another Dband antenna of the initiator. In this case the next transmission is separated from the previous transmission by 6*SIFS interval. This is indicated in Figure 95.

CID2067

Editor: modify P232L34-38 as follows:

If the responder has more than one DBand antenna, the initiator repeats its initiator sector sweep for the number of DBand antennas indicated by the responder in the Number of DBand Antennas field within the responder’s DBand Capabilities element. Repetitions of the initiator sector sweep are separated by an interval equal to 6*SIFS time. In this case CDOWN indicates the number of sectors until the end of transmission from all initiator’sDBand antennas to all responder’sDBand antennas.

------

CID2285

Editor: modify as follows:

Table 7-57y—A-MPDU contents in the data enabled immediate response context

In the OBand if the preceding PPDU contains an implicit or explicit Block Ack request for a TID for which an HT-immediateBlock Ack agreement exists at most one BlockAck for this TID, in which case it occurs at the start of the A-MPDU.

In the DBand if the preceding PPDU contains an implicit or explicit Block Ack request for a TID for which an HT-immediateBlock Ack agreement exists one or more equal BlockAck’s for this TID.

------

CID2286

Editor: modify as follows:

9.2.11 NAV distribution

“… the node may first transmit a CTS frame with the RA field equal to its own MAC address (CTSto-self) if operating in the OBand, or a DBandCTS with the RA field equal to the TA field and equal to

its own MAC address and the TA field equal to the MAC address of other DBand STA the forthcoming transmission of the first DBand STA is intended (DBandCTS-to-self) if operating in the DBand. A duration value in the frame protects the pending transmission, plus possibly an ACK frame.”

9.23.10 Multiple NAV timers update

} else if (received_frame = ACK) {

R_DST  received_frame(RA)

R_SRC  0

} else if (received_frame = DBandCTS-To-Self){

R_DST  0

R_SRC  received_frame(TA)

} else {

______

Break

}

} else if (received_frame = DBandCTS-To-Self) {

If(NAVSRC(x) = R_SRC) {

N_TIMER  x

Break

}

} elseif (NAVSRC(x) = R_SRC & (NAVDST(x) = R_DST

Submissionpage 1Solomon Trainin, Intel et al