IEEE P802.11 Wireless LANs Clause 22.3.21 and PMD SAP Comment Resolution Date: 2012-05-10 Author(s): Name Affiliation Address Eldad Perahia Intel Corporation Adrian Stephens Corporation Adrian.p.stephens@intel.com Note to TGac PHY ad-hoc database owner: In what follows, please replace <this-document> with the actual document reference and version in which the comment resolution was discussed and approved. CID Page Clause Comment Proposed Change Resn Status Resolution 4772 Mark 263.10 22.3.21 PMD_CHAN_MAT.ind, ind and PMD_CBW ind are missing Add to text, procedure and flowchart R Revised. The use of the highlighted PMD parameters are already described in Clause 22.6, so it is not necessary to repeat the description. This is the same approach as in Clause 20. However, following Clause 20, the parameters will be included in the PLCP receive procedure
training fields.", which is way too late. And reference from Figure 22-28. It determine whether to switch to a receive procedure in another Clause or for decoding errors. 5226 Sigurd 267.37 22.3.21 Action on VHT-SIG-A unsupported mode not fully reflected in text Figure 22-28 that for VHT-SIG-A unsupported mode, the PLCP issues a PHY_RXSTART.ind., followed by a PHY_RXEND.ind. This is not reflected in the text (see line 46 on page 263). Correct either text or figure. R Revised. TGac editor: In D2.1 P261L41, change “If the VHT-SIG-A indicates an unsupported mode, the PHY shall issue the error condition to “If the VHT-SIG-A indicates an unsupported mode, the PHY set issue PHY_RXSTART.ind (RXVECTOR) then PHY shall issue the error condition 4122 Adrian 267.57 22.3.21 The PMD interface is inadequate to receive an MU PPDU. For the PMD to demodulate a symbol and extract the appropriate user's data requires that it understand which of the STS to demodulate, and which user-specific MCS to expect. However, this information is held in the signal fields, which are comprehended only in the PLCP. 1. Add a new PMD request: with parameters MCS, START_STS, NUM_STS (Add to table 22-62 and new subclauses 22.6.5.x). 2. Update 22.3.21 and figure 22-28 showing generation of this primitive in "Setup PSDU RX". Rejected. Precedent in Clause 18 (802.11a) and Clause 20 (802.11n) is that the PMD has the information from the signal field, e.g. Rate or MCS. No new PMD request is necessary. Discussion:
Change PHY-CCA.ind(STATUS=busy) to PHY-CCA.indiation(busy,primary) Change any “.ind” primitives to “.indication” TGac editor: modify in D2.1 Figure 22-30 as follows: Changes to 22-31: Addition of “Determine if PPDU is filtered out or not” and 2 transitions. TGac editor: modify in D2.1 Figure 22-31 as follows: Comments on PMD CID Page Clause Comment Proposed Change 4770 PMD_RCPI.ind is defined in 22.6.5.9 but not used in 22.3.20 Either show PMD_RCPI.ind in 22.3.20 (rx text, rx procedure, rx flowchart) or delete it Discussion: This is another case where VHT is follow a precedent. .11k did an incomplete job when RCPI was added, and we have propagated this in D2.0, although we have addressed the “continuously available” issue in D2.1. Proposed Resolution: Revised. Modify Figure 22-30 (rx procedure) as shown in <this-document>. This adds a PMD_RCPI.indication(RCPI) primitive at the end of the received PPDU. 4118 Table 22-62 shows only a PMD_TXEND primitive. Figure 22-25 shows more than this. (I have another comment to change Figure 22-24 PMD_TXEND.indication to PMD_TXEND.confirm). Add a PMD_TXEND.confirm in table 22-62. Proposed Resolution:
Make change as indicated (except use range 1 to NUM_USERS in NOTE), and also cite NOTE from TXD_UNIT parameter. Add at the end of 22.6.5.2.2: “The TXD_UNIT parameter is present for one user for an SU PPDU and present per user for an MU PPDU. It is conceptually supplied as an array of values indexed by u, where u takes values 1 to NUM_USERS.” 5457 "aNumberSupportedPowerLevels" is defined in neither REVmb D12.0 nor TGac D2.0. The correct MIB attribute is "dot11NumberSupportedPowerLevels." As in comment. This change is shown under PMD Changes. Proposed Resolution Revised. Change cited “aNumberSupportedPowerLevels” to “dot11NumberSupportedPowerLevelsImplemented”. 4124 "PMD_NON_HT_CH_BANDWIDTH.indication"How does this work? Given that the information is in the service field, it is known to the PLCP, not the PMD. Remove this subclause. Update 293.28. Discussion: The service field is available only after decoding, which according to figure 22-27 (D2) occurs in the PLCP. Proposed Resolution: Make changes as shown in <this-document> under PMD Changes. These remove the cited primitive. 5236 Clarify availability of PMD_CBW.indication The text states that "This primitive be available continuously to the PLCP". It would appear this is not possible, since it relates directly to reception of a packet. What happens if PHY is in receive state and no