Rev 0: Initial Version of the Document s5

Rev 0: Initial Version of the Document s5

<p>July 2016 doc.: IEEE 802.11-16/xxxxr0doc.: IEEE 802.11- 16/xxxxr00 IEEE P802.11 Wireless LANs</p><p>EIFS</p><p>Date: 2016-07-13</p><p>Author(s): Name Affiliation Address Phone email 5775 Morehouse Dr, San Diego, Alfred Asterjadhi Qualcomm Inc. +1-858-658-5302 [email protected] CA 92109</p><p>Abstract This submission proposes resolutions for multiple comments related to TGax D0.1 with the following CIDs (4 CIDs): - 162, 2444, 2443, 2623</p><p>Revisions: - Rev 0: Initial version of the document.</p><p>Submission page 3 Alfred Asterjadhi, Qualcomm Inc. July 2016 doc.: IEEE 802.11-16/xxxxr0doc.: IEEE 802.11- 16/xxxxr00 Interpretation of a Motion to Adopt</p><p>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.</p><p>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).</p><p>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.</p><p>PARS I (EIFS)</p><p>CID Commenter P.L Comment Proposed Change Resolution 1298 EIFS rules need to be updated for HE As in comment. Revised – .01 PPDUs since the TXOP duration is included in the SIG-A. Easy fix EIFS = Agree in principle with the comment. Proposed DIFS if received HE PPDU. resolution is inline with the suggested change (specifying that EIFS shall not be invoked if a valid Alfred TXOP_DURATION that updates the NAV is present 162 Asterjadhi in the RXVECTOR parameter). </p><p>Also proposed resolution adds the TXOP Duration field in the TXVECTOR/RXVECTOR table.</p><p>TGax editor to make the changes shown in 11- 16/0835r0 under all headings that include CID 162. Yongho 39.4 The HE AP may receive one or more A- As per comment Seok 4 MPDU(s) that are carried in the HE trigger-based PPDU. In that case, even though all A-MPDU sub-frames in one A- Revised – MPDU is not received correctly, the HE AP shall not invoke the EIFS if at least Agree in principle with the comment. Proposed one frame in other A-MPDU is correctly resolution is inline with the suggested change received. (specifying that EIFS shall not be invoked if a valid Accordingly, change the last paragraph of 244 TXOP_DURATION that updates the NAV is present the sub-clause 10.3.2.3.7 as the following: 4 in the RXVECTOR). "EIFS shall not be invoked if the NAV is updated by the frame that would have Also proposed resolution adds the TXOP Duration caused an EIFS, such as when the FCS field in the TXVECTOR/RXVECTOR table. fails and the L-SIG TXOP function employs L-SIG information to update the TGax editor to make the changes shown in 11- NAV. EIFS shall not be invoked for a 16/0835r0 under all headings that include CID 2444. PPDU that contains one or more A- MPDU(s) if one or more of its frames of at least one A-MPDU in the PPDU are received correctly." 244 Yongho 39.4 Because the HE STA can update the NAV As per comment Revised – 3 Seok 4 from the HE-SIG-A field in the received HE PPDU, it shall not invoke the EIFS Agree in principle with the comment. Proposed when it receives a valid HE-SIG-A in the resolution is inline with the suggested change HE PPDU. (specifying that EIFS shall not be invoked if a valid Change the last paragraph of the sub- TXOP_DURATION that updates the NAV is present clause 10.3.2.3.7 as the following: in the RXVECTOR). "EIFS shall not be invoked if the NAV is updated by the frame that would have Also proposed resolution adds the TXOP Duration caused an EIFS, such as when the FCS field in the TXVECTOR/RXVECTOR table. fails and the L-SIG TXOP function employs L-SIG information to update the TGax editor to make the changes shown in 11- NAV. EIFS shall not be invoked for an A- 16/0835r0 under all headings that include CID 2443. MPDU if one or more of its frames are received correctly. EIFS shall not invoked if a valid TXOP duration value in HE-</p><p>Submission page 3 Alfred Asterjadhi, Qualcomm Inc. July 2016 doc.: IEEE 802.11-16/xxxxr0doc.: IEEE 802.11- 16/xxxxr00 SIG-A field of a HE PPDU is identified." Young Hoon 53.3 When a STA correctly receives a valid Modify the final paragraph of Kwon 3 HE-SIG-A in a HE PPDU and identifies 10.3.2.3.7 EIFS sub-clause (in TXOP Duration field in the HE-SIG-A, REVmc_D5.2) to "EIFS shall not the STA has identified valid TXOP be invoked if valid TXOP Duration Revised – Duration information even in case the value is identified by the frame that STA fails to decode the payload of the would have caused an EIFS, such Agree in principle with the comment. Proposed PPDU. Therefore, in case the STA fails to as when resolution is inline with the suggested change decode the payload, additional waiting for the FCS fails and the L-SIG TXOP (specifying that EIFS shall not be invoked if a valid EIFS time does not protect possible function employs L-SIG TXOP_DURATION that updates the NAV is present 262 response frame at all because TXOP information to update the NAV, or in the RXVECTOR). 3 Duration field in the HE-SIG-A already valid TXOP Duration value in the indicated similar information. In current HE-SIG-A field of an HE PPDU is Also proposed resolution adds the TXOP Duration spec., it is written as "EIFS shall not be identified and the FCS of the field in the TXVECTOR/RXVECTOR table. invoked if the NAV is updated by the payload of the HE PPDU fails. frame that would have caused an EIFS." EIFS TGax editor to make the changes shown in 11- However, in case of TXOP Duration value shall not be invoked for an A- 16/0835r0 under all headings that include CID 2623. in HE-SIG-A field, it is not needed the MPDU if one or more of its frames NAV to be updated for EIFS not being are received correctly.". invoked. For this end, extending current spec. text is necessary.</p><p>Discussion: None.</p><p>10.3.2.3.7 EIFS</p><p>TGax Editor: Insert the following sentence at the end of this paragraph (#CID 162, 2444, 2443, 2623):</p><p>EIFS shall not be invoked if the NAV is updated by the frame that would have caused an EIFS, such as when the FCS fails and the L-SIG TXOP function employs L-SIG information to update the NAV. EIFS shall not be invoked for an A-MPDU if one or more of its frames are received correctly. EIFS shall not be invoked if a valid TXOP_DURATION parameter is present in the RXVECTOR of a received HE PPDU.</p><p>TGax Editor: Insert the following row (ignoring the header row) in Table 26-1 (#CID 162, 2444, 2443, 2623):</p><p>Table 261 - TXVECTOR and RXVECTOR parameters</p><p>T R Par X X ame Condition Value V V ter E E C C T T</p><p>TXO P _DU RATION Indicates a duration of time that is used to update Y Y the NAV for this TXOP (see 25.2.1 (Updating two NAVs)), except for a value of 127 which indicates an invalid value of TXOP duration in SIG-A.</p><p>F OR MAT is HE _SU, HE _MU, HE _EXT _ SUor HE _TR IG</p><p>Submission page 3 Alfred Asterjadhi, Qualcomm Inc. July 2016 doc.: IEEE 802.11-16/xxxxr0doc.: IEEE 802.11- 16/xxxxr00</p><p>Submission page 3 Alfred Asterjadhi, Qualcomm Inc.</p>

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    4 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us