[STDS-802-11-TGBN] TGbn pres 25/1455r0 on "TPE Signaling for DBE"

[Binita Gupta <bingupta.ieee@xxxxxxxxx>]

Hi All,

I presented 25/1455r0 on "TPE Signaling for DBE".

I am starting this thread to address comments received during the pres and requesting for any further feedback.

Please provide your comments/feedback in this thread or to me. 

Thomas Derham • q

- Encapsulating TPE info for DBE BW may be ok

- Does expanding to DBE BW have any impact on Regulatory Info field setting?
<BG> This field defines Indoor AP, Standard Power AP, Very low power AP, etc (See Table E-12 in Annex E). Not sure if expanding to DBE BW would change this designation for the AP. My assumption is that it would not change, but I will double check.

 - Understand Beacon bloating issue, but anyway TPE info would need to be included at some point.

<BG> Inclusion of TPE Info for DBE BW is similar to UHR critical updates (and including IE for that). It is not always included, but only for some period of time to avoid beacon bloating. Same argument that applies to only including CU parameters for some period of time (to avoid beacon bloating) applies for TPE Info for DBE BW. 

- Whether there could be legacy compatibility issues if TPE Info in beacon is updated for DBE BW is to be seen

<BG> One of the MSB of DBE feature is to support it in a way so as to not cause any compatibility/interop issues for legacy. Given frequent changes to TPE IE and providing TPE beyond BSS BW is not much tested, it would be a compatibility risk. We can't test all the legacy devices out there and causing any compatibility issues for getting TPE info for legacy can be a serious concern from regulatory PoV. Hence better to provide TPE info for DBE BW in a way that avoids such compatibility issues.

[V] Reza Hedayat, Apple • q

- Agree we need to provide TPE info for DBE BW

- I think your numbers are not accurate. You are adding numbers for multiple rows from Table 9-337.

<BG> As I explain on slide 3, per baseline 
"One TPE element is included in Beacon for each distinct combination of “Maximum Transmit Power Interpretation” and “Maximum Transmit Power Category” fields (defined in Table E-14, with two possible values)"

Typically there are Multiple TPE elements  included based on regulatory/local requirements. So, it is not inaccurate to say that multiple TPE elements are included.

See below texts from 11.7.5 

and from E.2.7 (6 GHz band), Each different values for Maximum Transmit Power Interpretation, will be a separate TPE element. Besides these, there will be local max transmit powers limit included as separate TPE elements.

- Option 3 does not seem that bad, if any know compatibility issue would be good to share.

<BG> As explained above, it is not possible to test all the legacy devices out there to see if those devices won't have any issues with frequent changes to TPE IE and providing TPE beyond BSS BW. This has not been tested in past. Any compatibility issues (caused by DBE BW TPE) in getting TPE info for legacy devices would be very concerning from regulatory PoV. 

Shravan Kalyankar • deq

[V] Liwen Chu, NXP • q

<BG> Liwen:please let me know your comments.

[V] Laurent Cariou, Intel • btw, as we are on this topic, it would be quite important for non-AP STAs to have DBE BW to always be advertized in beacons all the time

<BG> Laurent, I assume you mean during the time when DBE mode is enabled, correct? Could you clarify why is that needed and retrieving from DBE CU notification is not enough? If needed then we need to add this in the UHR Operation element. Then do we also need to advertise the DBE Disabled Subchannel bitmap along with it? 

Thanks,

Binita

 

---

To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1