Re: [STDS-802-11-TGBE] Discussion on 11-21/1147 CC36-CR-35.6 Restricted TWT Announcement

[Chunyu Hu <chunyuhu07@xxxxxxxxx>]

Hi, Rubayet:

Thanks for sharing your comments. Want to first clarify: I think 'network level of view' would be a more suitable description.  'time slice' is the time granularity used in the description.

I agree that additional information about the schedules can be also provided by including them in each schedule specified by the corresponding rTWT parameter set.

Let's follow this line of thought to see what would be alternative design --

1) the additional info include {occupied, full, OBSS}.

2) examining the current bTWT/rTWT parameter set fields, the only available bits are the three reserved bits in the Broadcast TWT Info field (11axD8.0 Figure 9-687b—Broadcast TWT Parameter Set field format).

Functionality can be met by this alternative option. This will use up all reserved fields and no room for flexibility for any future bTWT and/or rTWT specific extension needs without increasing len.

Comparing some other aspect(s):

-- the new IE proposed in 11-21/1147 saves the rTWT supporting STA's computation to reconstruct such a network level of view: it doesn't need to parse each and every bTWT parameter set to recompute.

Given the above evaluation, I agree the alternative option could work but the new one seems a better option.

Let me know your thoughts and we can discuss further.

Thanks.

Chunyu

On Fri, Aug 20, 2021 at 3:58 PM Rubayet Shafin <r.shafin@xxxxxxxxxxx> wrote:

Hi Chunyu,

 

Thank you so much for initiating the discussion thread on this topic. I appreciate it.

 

First thing is -- I am not sure whether the restricted TWT scheduled STAs really need this ‘time slice’-level information? I do see your motivation to provide some additional information to the restricted TWT scheduled STAs by the restricted TWT scheduling AP during the schedule advertisement phase, but this additional information can be at the schedule-level instead of at the ‘time slice’-level, as you are proposing. From per-schedule information about all the advertised schedules, the STAs themselves should be able to figure out the necessary ‘time slice’-level information, and therefore, achieve the ‘consolidated view’ of the entire timeline. For instance, if the STAs know occupancy information for the advertised schedules, they would essentially know the occupancy for each slice.

 

Also, this additional per-schedule information announcement can be accommodated with just minor changes in existing broadcast TWT signaling mechanism.

 

Best

Rubayet

 

From: Chunyu Hu <chunyuhu07@xxxxxxxxx>
Sent: Sunday, August 15, 2021 12:14 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBE] Discussion on 11-21/1147 CC36-CR-35.6 Restricted TWT Announcement

 

Hi, all:

 

I presented 11-21/1147 CC36-CR35.6 Restricted TWT Announcement in last meeting 08/12/2021.

There were still many people in the question queues that were not able to ask. I noted down: Stephan, Bo, Jason, Liangxiao, Mohamed, Yongho, Kiseon, Qi, Liwen, Ming. Sorry if I missed anyone.

 

Would you please raise your questions here or offline to me?

I'll use this thread or offline one as needed. Or have another meeting to discuss this if many questions are similar.

 

Thanks!

Chunyu

---

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