Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
--- This message came from the IEEE 802.11 Working Group Reflector ---
Hi all CIDs 1059 and 2109 observe that aRxPHYStartDelay is defined differently in different PHY clauses and even differently for different PHY formats defined in the same PHY clause. Meanwhile aRxPHYStartDelay is used in the MAC clauses as if
it were a single constant. A) One option is for the PHY to expose all values of aRxPHYStartDelay to the MAC and for the MAC to select the
maximum aRxPHYStartDelay among the values relevant to the current context. This approach is defined in 22/576 under CID 1059.
This is a simple fix but (as Youhan points out) suffers from the problem that aRxPHYStartDelay can be very high for HE/EHT MU PPDUs (hundreds of usec, which is longer than the duration of two short PPDUs) due to the HESIGB/EHTSIG fields,
yet oftentimes the MAC clauses uses aRxPHYStartDelay to determine if the PHY is actively processing a PPDU or not, in order to determine if the MAC can transmit something else. Thus a short value of aRxPHYStartDelay is generally preferred. B) Another set of options attempts to provide a smaller value (or a smaller set of values) of aRxPHYStartDelay:
Any comments / concerns / suggestions / recommended directions are welcome. Best regards Brian To unsubscribe from the STDS-802-11 list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11&A=1 |