Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-11-TGBE] 20/1395r14


Tomoko,

Provided that the EHT PHY subclause follows the pattern of other PHY subclauses, as Bin points out, the new PHY will be an extension of the existing ones.

For example, here is the opening text of the VHT PHY subclause, note in particular, the highlighted text:


21. Very high throughput (VHT) PHY specification
21.1 Introduction
21.1.1 Introduction to the VHT PHY

Clause 21 (Very high throughput (VHT) PHY specification) specifies the PHY entity for a very high
throughput (VHT) orthogonal frequency division multiplexing (OFDM) system (#1587)operating in the 5
GHz band.

In addition to the requirements in Clause 21 (Very high throughput (VHT) PHY specification), a VHT STA
shall be capable of transmitting and receiving PPDUs that are compliant with the mandatory PHY
specifications defined in Clause 19 (High-throughput (HT) PHY specification) (#1587)in the 5 GHz band.

The VHT PHY is based on the HT PHY defined in Clause 19 (High-throughput (HT) PHY specification),
which in turn is based on the OFDM PHY defined in Clause 17 (Orthogonal frequency division
multiplexing (OFDM) PHY specification).



Matthew Fischer
Nice Guy
Broadcom Inc.
+1 408 543 3370 office


On Tue, Sep 29, 2020 at 10:05 AM Bin Tian <btian@xxxxxxxxxxxxxxxx> wrote:

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>
Sent: Monday, September 28, 2020 10:02 PM
To: Bin Tian <btian@xxxxxxxxxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBE] 20/1395r14

 

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>
Sent: Tuesday, September 29, 2020 1:12 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] 20/1395r14

 

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>
Sent: Monday, September 28, 2020 7:19:47 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBE] 20/1395r14

 


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:

 

Hi Matt,

 

“An MLD may indicate a pair of links as STR by setting the TBD field in the TBD elements that it transmits if the receiver requirements specified in clause 34 on one link are met whenever it is transmitting on the other link.”

 

Could you clarify what are specified as requirements in clause 34?

Maybe you can point out the related PDT whose SP has passed in the PHY group.

Thanks.

 

Best regards,

tomo

 

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

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

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature