| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Tomo Good question on STR/NSTR link using non-EHT PHY. Generally speaking, the later amendment receiver requirement is a superset of the one in previous gen. If a receiver satisfies EHT PHY receive requirement,
it generally can satisfy previous gen requirements. I am open to discussion in the future if we need to add some text to non-EHT receiver requirements when operating as STR.
Thanks, Bin From: tomo.adachi@xxxxxxxxxxxxx <tomo.adachi@xxxxxxxxxxxxx>
CAUTION: This email originated from outside of
the organization. Thanks Bin.
OK. Learning from the past PHY specs, we can expect similar requirements will be set in EHT PHY.
I understand STR/NSTR indeed relates to receiver requirements in the PHY.
But can’t STR/NSTR links use PHYs other than EHT PHY? Or the legacy PHYs in the same band are required to be mandatory anyway, so referring only to EHT
PHY will be enough? When I first read the cited part, I imagined there will be a kind of summary subclause in clause 34 which explains the requirements for STR/NSTR.
Best regards, tomo From: Bin Tian <btian@xxxxxxxxxxxxxxxx>
Hi Tomo and Matt For each amendment, there is a clearly defined set of requirements/specifications for receiver and transmitter. 11be receiver requirements in clause 34 is still under development.
As an example, 11ax receiver requirements (clause 27.3.20) include receiver minimum sensitivity, adjacent channel rejection, max signal input level and CCA sensitivities, etc. I am open to have a discussion in the future on relaxation or special treatment on the requirements of receiver in STR case. We can summarize the discussion outcome in the receiver
specification in clause 34 in the future. Thanks, Bin
From: Matthew Fischer <00000959766b2ff5-dmarc-request@xxxxxxxxxxxxxxxxx>
I cannot clarify what the requirements are in clause 34. One would have to look into the SFD and compendium, but the main one is what was named explicitly in r12, that is, the receiver minimum sensitivity requirement. Bin Tian might provide more clarity. Matthew Fischer Nice Guy Broadcom Inc. +1 408 543 3370 office On Mon, Sep 28, 2020 at 7:10 PM Tomo Adachi <tomo.adachi@xxxxxxxxxxxxx> wrote:
To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 |