| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Po-kai, Thank you for accommodating my comments #1 and #4. For the deferred items #2 and #3, I recommend that you discuss item #2 with various PHY and MAC people to see if we need some consistent terms. For item #3,
I see reshuffling entries within a table without changing them is totally under your discretion as the Technical Editor. So, please feel free to consider it at a time that is convenient for you. Thanks, Yunsong Yang Huawei Device USA Inc. 10180 Telesis Court, STE 165 San Diego, CA 92121 Phone: +1-858-754-3638 From: Huang, Po-kai [mailto:po-kai.huang@xxxxxxxxx]
Hi Yunsong, Thanks for the comments. I incorporate the editorial suggestion for the first and fourth comment.
For the second and third comment, as discussed with you offline, we agree that this is more like spec polishing and can be done later. Best, Po-Kai From: Yangyunsong [mailto:yangyunsong@xxxxxxxxxx]
Hi Po-kai, I have a few comments and suggestions as follows: 1. P4, clause 4.3.15a:
Suggest adding text as highlighted below, because, obviously, a HT AP, VHT AP, or HE AP without the added capability is not necessarily a WUR AP. “WUR AP supports the features of HT AP, VHT AP, or HE AP, and has the capability to transmit WUR PPDU.” 2. P4, clause 4.3.15a:
The proposed PHY spec text in 11-18-0152r04 uses the following highlighted terms, instead of WUP AP and WUR non-AP STA. Suggest making these two terms consistent,
one way or the other. “32.1 Introduction … A STA that supports WUR PHY specification may be a
WUR transmitter STA. A WUR transmitter STA shall be capable of transmitting the WUR PPDU.
A STA that supports WUR PHY specification may be a
WUR receiver STA. A WUR receiver STA shall be capable of receiving the WUR PPDU. …” 3. P6, Table 9-xxx – Subfields of WUR Parameters field from WUR AP:
Suggest getting the subfields organized in the table, for example, placing parameters (such as WUR Beacon period, WUR Operating Class, and WUR Channel) that
tend to be common in the front and placing parameters (such as WUR ID and Duty Cycle Info) that tend to be for individual STA in the back. 4. P8, Clause 9.4.2.263: Suggest the following changes (and confirm my understanding that the supported bands is for the WUR channel only (i.e., STA doesn’t indicate its PCR supported
bands that the STA is not capable of operating its WURx on): For WUR AP, the
Supported Band
For WUR non-AP STA, the Supported Bands field indicates the supported bands
for the WUR channel. The encoding of the field is TBD. Thanks, Yunsong Yang Huawei Device USA Inc. 10180 Telesis Court, STE 165 San Diego, CA 92121 Phone: +1-858-754-3638 From: *** 802.11 TGba - WUR- Wake-up Radio Operation *** [mailto:STDS-802-11-TGBA@xxxxxxxx]
On Behalf Of Huang, Po-kai Hi all, My apology. I upload the wrong version in the previous email.
Please use revision 2 as shown in the following link. Best, Po-Kai From: *** 802.11 TGba - WUR- Wake-up Radio Operation *** [mailto:STDS-802-11-TGBA@xxxxxxxx]
On Behalf Of Huang, Po-kai Hi all, I have uploaded the revised spec texts about WUR negotiation and WUR mode. The document accommodates the comments that I have received during
Tuesday presentation and the offline discussion with George and Jarkko. Track changes are on. Please let me know if you have further comments. Best, Po-Kai From: *** 802.11 TGba - WUR- Wake-up Radio Operation *** [mailto:STDS-802-11-TGBA@xxxxxxxx]
On Behalf Of Minyoung Park Dear all, If you had a presentation on the spec text and resolved comments, please upload the revision to the mentor server and send an email to the group for review. We will have approval on the final spec text on Thursday AM1. Regards, Minyoung |