I would like to use this email thread to discuss the sounding rate ceiling issue related to the 10 TU associated with the Availability Bitmap in Chaoming's 22/0977r8. This is related to 22/1621r0.
As the time unit of the Availability Bitmap is 10 TU, the implied maximum sounding frequency is about 100 Hz (97.7Hz, to be exact). But there are many important applications such as fall detection, gesture recognition, gait monitoring, speed estimation that call for higher sounding frequency (e.g. 500 Hz, 1000Hz, 1500Hz, or 2000 Hz).
So far two concerns have been raised in the conference calls:
(1) If sounding frequency is too high, CSI reporting may require too much data bandwidth. (But this is not a problem if CSI is not reported.)
(2) If sounding frequency is too high, the Availability Bitmap is too big to send. (Size of Availability Bitmap is controlled by Count.)
I propose in 22/1621r0 a step (A): use one of the reserved bits to indicate two time units (e.g. "1"= 10 TU, "0"=alternate time unit (TBD)).
I see a few options of using step (A):
1. Do (A) only when CSI is not reported. No alternate time unit when CSI is reported.
2. Do (A) whether CSI is reported or not, with same alternate time unit.
3. Do (A) with two alternate time units: a first alternate time unit (e.g. 1 TU) when CSI is reported, and a second alternate time unit (e.g. 0.1 TU) when CSI is not report.
2. Do (A) whether CSI is reported or not, with same alternate time unit.
3. Do (A) with two alternate time units: a first alternate time unit (e.g. 1 TU) when CSI is reported, and a second alternate time unit (e.g. 0.1 TU) when CSI is not report.
Please kindly comment.
Thanks,
Oscar
--
Oscar Au Vice president IP & standardization 512.825.1412 (m) |