Hi Chris,
If I may add, regarding TXVECTOR parameters related to NDP transmissions, they are PHY specific and each PHY has defined methods to specify the NDP. E.g., for EHT PHY, the FORMAT has to be EHT_MU and PSDU_LENGTH = 0 signals an EHT Sounding NDP. HE/VHT
have similar tables. In my opinion, what is unclear now in 11bf is how to specify the NDP format for each sequence, especially if 11bf defines a new Sensing NDPA.
Regards,
Rojan
-----Original Message-----
From: Yan Xin <0000181ed67b5ae9-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, January 26, 2022 3:03 AM
To: STDS-802-11-TGBF@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBF] draft baseline PDT for "NDP format"
Hi Chris:
Thanks for sharing the questions.
For the case of 11az, HE ranging NDP uses 2x HT-LTF with 8 us symbol duration, which is a specific case of HE-LTFs (with alternative parameters GIs, 1x / 2x/ 4x). For 11bf, I think we need to have further discussion on the parameters related to the NDP
for sensing.
Thanks,
Yan.
-----Original Message-----
Sent: Friday, January 21, 2022 6:03 PM
Subject: Re: [STDS-802-11-TGBF] draft baseline PDT for "NDP format"
This is an interesting point, one which I wouldn’t mind discussing a bit further to understand the limitations.
I agree that we already have multiple NDP types defined, and creating a new one is outside the scope. But, what about defining TXVECTOR parameters for which are used to transmit the existing NDPs. Is this something we have flexibility to define, and
if so, where would we define it?
Thanks and regards,
-Chris
________________________________________________________________________
________________________________________________________________________