Tgax Editor: Modify the Sub-Clause 8.3.5 As the Following

February 2017 doc.: IEEE 802.11-12/1234r021

IEEE P802.11 Wireless LANs

LB225 CR Sub-clause 8.3.5

Date: 2017-02-02

Author(s): Name Affiliation Address Phone email 9008 Research Drive, Irvine, CA, Yongho Seok NEWRACOM [email protected] 92618

Submission page 1 Yongho Seok, NEWRACOM February 2017 doc.: IEEE 802.11-12/1234r021

Interpretation of a Motion to Adopt

A motion to approve this submission means that the editing instructions and any changed or added material are actioned in the TGax Draft. This introduction is not part of the adopted material.

Editing instructions formatted like this are intended to be copied into the TGax Draft (i.e. they are instructions to the 802.11 editor on how to merge the text with the baseline documents).

TGax Editor: Editing instructions preceded by “TGax Editor” are instructions to the TGax editor to modify existing material in the TGax draft. As a result of adopting the changes, the TGax editor will execute the instructions rather than copy them to the TGax Draft.

CID Page Clause Comment Proposed Change Resolution 6935 15.21 8.3.5.2. Why does the remove STA_INDEX and Revised- 2 STA_INDEX need to be repurpose the USER_INDEX The difference between added? Since the to provide the index function STA_INDEX and STA_INDEX and the for HE MU PPDUs. USER_INDEX is not USER_INDEX seem to be Also rewrite the descriptive clearly described in basically provide the paragraphs for USER_INDEX current draft text. same function and both and STA_INDEX so that it is operate using the u value clear what the behavior is of For a VHT MU PPDU, the USER_INDEX when used to provide an index for the the u value (i.e., in a VHT MU PPDU and a HE MU users. It would seem USER_INDEX) provides MU PPDU. to be simpler to extend an index for MU users. the USER_INDEX to The u value is typically a provide the necessary sequential interger value. function and behavior of (e.g., 0, 1, 2 and 3). the STA_INDEX for HE MU PPDUs. Also note For an HE MU PPDU, an that since the element of the User_INDEX parameter is STA_ID_LIST parameter only present for a VHT (i.e., STA_INDEX) MU PPDU, it would seem provides an index of MU that a VHT STA would be users. very confused by For example, if an RU is presence of a intended for a single STA_INDEX as it would STA, then the occupy the same location STA_INDEX corresponds in the PHY-DAT.request to the AID of the STA as the USER_INDEX receiving the DATA would. contained in that RU.

I agree that both have conceptually same purpose. But, the detailed parameter value is very different and also the use cases of the STA_INDEX are broad than the USER_INDEX.

TGax editor makes changes as shown in the as specified in 11- 17/0223r21. 3102 15.22 8.3.5.2. Why do we need both Throughout the draft, replace Revised-

CID Page Clause Comment Proposed Change Resolution 2 USER_INDEX and all references to STA_INDEX The difference between STA_INDEX? They both with USER_INDEX. STA_INDEX and seem to describe exactly USER_INDEX is not the same concept. clearly described in As these both support current draft text. "multi-user" (not "multi- STA") operation, the For a VHT MU PPDU, existing term is the the u value (i.e., preferable. USER_INDEX) provides an index for MU users. The u value is typically a sequential interger value. (e.g., 0, 1, 2 and 3).

For an HE MU PPDU, an element of the STA_ID_LIST parameter (i.e., STA_INDEX) provides an index of MU users. For example, if an RU is intended for a single STA, then the STA_INDEX corresponds to the AID of the STA receiving the DATA contained in that RU.

TGax editor makes changes as shown in the as specified in 11- 17/0223r21. 7707 15.34 8.3.5.2. How is STA_INDEX Remove the new parameter. Revised- 2 different from Merge the reference to Table The difference between USER_INDEX? 28-1 into the existing text for STA_INDEX and USER_INDEX on condition of USER_INDEX is not an HE MU PPDU. clearly described in current draft text.

For a VHT MU PPDU, the the u value (i.e., USER_INDEX) provides an index for MU users. The u value is typically a sequential interger value. (e.g., 0, 1, 2 and 3).

For an HE MU PPDU, an

CID Page Clause Comment Proposed Change Resolution element of the STA_ID_LIST parameter (i.e., STA_INDEX) provides an index of MU users. For example, if an RU is intended for a single STA, then the STA_INDEX corresponds to the AID of the STA receiving the DATA contained in that RU.

TGax editor makes changes as shown in the as specified in 11- 17/0223r21. 8494 15.34 8.3.5.2. There is no need for a Remove STA_INDEX. Revised- 2 new STA_INDEX Update the text for The difference between parameter. USER_INDEX USER_INDEX to include HE STA_INDEX and and STA_INDEX are MU PPDU. Use same name USER_INDEX is not semantically equivalent. for PHY-DATA.indication. clearly described in Let's choose one and current draft text. stick with it. For a VHT MU PPDU, the the u value (i.e., USER_INDEX) provides an index for MU users. The u value is typically a sequential interger value. (e.g., 0, 1, 2 and 3).

For an HE MU PPDU, an element of the STA_ID_LIST parameter (i.e., STA_INDEX) provides an index of MU users. For example, if an RU is intended for a single STA, then the STA_INDEX corresponds to the AID of the STA receiving the DATA contained in that RU.

I agree that both have conceptually same

CID Page Clause Comment Proposed Change Resolution purpose. But, the detailed parameter value is very different and also the use cases of the STA_INDEX are broad than the USER_INDEX.

TGax editor makes changes as shown in the as specified in 11- 17/0223r21. 4715 15.35 8.3.5.2. There are two cases HE As in comment. Revised- 2 DL MU PPDU and HE UL Agree in principleAgree MU PPDU. This in principle. statement applies to the The current description of DL MU PPDU, while for STA_INDEX makes a the UL MU PPDU it is the confusion. transmitter identifier. Also it is not really an index of Change the description the user (well actually of STA_INDEX. yes) but for consistency specify it as the AID of the TGax editor makes user (and add a reference changes as shown in the to 27.11.1 as specified in 11- (STA_ID_LIST). Similar 17/0223r21. observation for the next subclause 8.3.5.3.2. 6936 15.48 8.3.5.3. Why does the Replace STA_INDEX with Revised- 2 STA_INDEX need to be USER_INDEX. The difference between added? Since the STA_INDEX and STA_INDEX and the USER_INDEX is not USER_INDEX seem to be clearly described in basically provide the current draft text. same function and both operate using the u value For a VHT MU PPDU, to provide an index for the USER_INDEX MU users. It would seem provides an index for MU to be simpler to extend users. the USER_INDEX to provide the necessary For an HE trigger-based function for HE trigger- PPDU, the STA_INDEX based PPDUs. provides an index of an HE trigger-based PPDU. Typically it is identified as an AID of the transmitter of an HE trigger-based PPDU.

TGax editor makes changes as shown in the as specified in 11- 17/0223r21. 4716 15.56 8.3.5.3. "request" should be As in comment. Revised- 2 "indication". Also need to Agree in principleAgree keep consistency on how in principle. we call this PPDU. Maybe Change “request” to define an acronym HE “indication”.

CID Page Clause Comment Proposed Change Resolution Trigger Based PPDU (HE TB PPDU) and stick with HE trigger-based PPDU it throughout the draft. has been consistenly used throughput the draft. No change on the naming is needed.

TGax editor makes changes as shown in the as specified in 11- 17/0223r21. 6937 15.56 8.3.5.3. Reuse the USER_INDEX Replace the sentence with: Revised- 2 to provide the function of The USER_INDEX parameter The difference between the STA_INDEX is present for an HE trigger- STA_INDEX and based PPDU and indicates USER_INDEX is not the index of the user in clearly described in the RXVECTOR to which the current draft text. accompanying DATA octet applies; otherwise, this For a VHT MU PPDU, parameter is not present. the USER_INDEX provides an index for MU users.

For an HE trigger-based PPDU, the STA_INDEX provides an index of an HE trigger-based PPDU. Typically it is identified as an AID of the transmitter of an HE trigger-based PPDU.

TGax editor makes changes as shown in the as specified in 11- 17/0223r21. 5432 15.65 8.3.5.1 What has IPI got to do Delete this instruction Rejected- 0.3 with it? The only completely. I agree that The IPI- parameter present in this STATE parameter is not primitive is IPI STATE. related with the This has nothing to do OBSS_PD. with OBSS_PD. But, the purpose of the PHY- CCARESET.request usage on the spartial resuse (e.g., OBSS_PD) is as the following.

“The effect of receipt of this primitive by the PHY entity is to reset the PHY to the state appropriate for the end of a received frame and to initiate a new CCA evaluation

CID Page Clause Comment Proposed Change Resolution cycle.” 4717 16.01 8.3.5.1 This additional generation Replace paragraph with: Revised- 0.3 is applicable to HE STAs. "This primitive can Agree in principleAgree Also refer to the general additionally be generated by in principle. spatial reuse subclause the MAC sublayer for the Geralized the generating rather than to the OBSS- local HE PHY entity when the condition of the PHY- PD pased subclause only. spatial reuse conditions CCARESET.request defined in 27.9 (Spatial primivie. Reuse) are met. TGax editor makes changes as shown in the as specified in 11- 17/0223r21.

TGax editor: modify the sub-clause 8.3.5 as the following:

* PHY service specification

* Detailed PHY service specifications

* PHY SAP detailed service specification

* PHY-DATA.request

* Semantics of the service primitive

Change the subclause as follows: The primitive provides the following parameter: PHY-DATA.request( DATA USER_INDEX STA_INDEX )

The DATA parameter is an octet of value X'00' to X'FF'.

The USER_INDEX parameter (typically identified as u for a VHT STA; see NOTE 1 at the end of Table 21-1 (TXVECTOR and RXVECTOR parameters)) is present for a VHT MU PPDU and indicates the index of the user in the TXVECTOR to which the accompanying DATA octet applies; otherwise, this parameter is not present.

The STA_INDEX parameter (obtained from STA_ID_LIST in Table 28-1 (TXVECTOR and RXVECTOR parameters) is present for an HE MU PPDU and indicates the index of the user in the TXVECTOR to which the accompanying DATA octet applies; otherwise, this parameter is not present.

T he STA _INDEX parameter (identified as an element of the STA_ID_LIST parameter; see STA_ID_LIST parameter in Table 28-1 (TXVECTOR and RXVECTOR parameters) and 27.11.1 (STA_ID_LIST)) is present for an HE MU PPDU and indicates the STA or group of STAs that is the recipient of an RU to which the accompanying DATA octet applies; otherwise, this parameter is not present.

* PHY-DATA.indication

* Semantics of the service primitive

Change the subclause as follows: The primitive provides the following parameter: PHY-DATA.requestindication( DATA STA_INDEX )

The DATA parameter is an octet of value X'00' to X'FF'.

The STA_INDEX parameter is present for an HE trigger-based PPDU and indicates the index of the user in the RXVECTOR to which the accompanying DATA octet applies; otherwise, this parameter is not present.

T he STA _INDEX parameter (identified as an AID of the transmitter of the DATA contained in an HE trigger-based PPDU; see STA_ID_LIST parameter in Table 28-1 (TXVECTOR and RXVECTOR parameters) ) is present for an HE trigger-based PPDU and indicates the STA of an RU from which the accompanying DATA octet applies; otherwise, this parameter is not present.

* PHY-CCARESET.request

* When generated

Insert the following after the 1st paragraph:

This primitive is also generated by the MAC sublayer for the local PHY entity when the conditions are met to perform OBSS_PD-based spatial reuse operation as defined in 27.9.2 (OBSS_PD-based spatial reuse operation) the spatial reuse conditions defined in 27.9 (Spatial Reuse) are met.

Submission page 1 Yongho Seok, NEWRACOM