Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-11-TGBE] (2) [STDS-802-11-TGBE] Discussion on rTWT SP traffic prioritization (11-21/1115,1020)



  Hello Chunyu,

Thanks for the detailed summary of the meeting.

 

I have a question on the way of indicating TID.

It seems that there were two (potential) candidates to specify TID(s), an implicit way and an explicit way.

I believe that the explicit way is extending the trigger frame to include target TID.

I didn't get what the implicit way is and how it is expected to operate.

Could you elaborate more about it?

 

Regards,

Jonghun

 

--------- Original Message ---------

Sender : Chunyu Hu <chunyuhu07@xxxxxxxxx>

Date : 2021-08-18 04:09 (GMT+9)

Title : Re: [STDS-802-11-TGBE] Discussion on rTWT SP traffic prioritization (11-21/1115,1020)

 

Thanks folks for joining the meeting. Here is a summary of Monday's meeting (8-9:30AM, 08/16/2021):

 

1) Rubayet presented 11-21/1020: Handling Fairness Issue in Restricted TWT

2) Q/As for the presentation.

3) Re-cap of 11-21/1115r0 (CC36-CR-35.6 Traffic Prioritization During Restricted TWT SPs

4) Q/As

 

Captured a few technical points at high level (not a comprehensive list):

1) is there a need to extend the trigger frame to specify a TID or TIDs in basic/BSRP? 

Boyce also brought up a similar question to NFRP.

 

Concerns were raised --

The function might be able to fulfil in an implicit way. Extending the trigger frame might be difficult / despite possible.

Needs to compare implicit and explicit way. Stephane will share some slides evaluating the implicit way.

Supporting point -- might be best to do it explicitly rather than depending on timing which is tricky.

 

Chunyu will follow up with Stephane, Boyce and let's gather proposals/analysis  for further discussion (probably another call).

 

2) Boyce proposed to add some text clarifying on TID w/ rTWT: it's expected that a STA maps latency sensitive traffic to a TID that is likely not overlapping with latency tolerance traffic to let the overall design work better.

Chunyu will follow up with Boyce on text.

 

3) prioritizing vs restricting:

Rubayet clarified that he prefers "restricting" the rTWT SP member STA should restrict their traffic during SP to be only TIDs_L(AP, STA); if running out the traffic, then the AP or rTWT member STA should terminate the SP between them.

Basically, e.g. in slide 10 of 11-21/1115r0, and put the STAs in set2 into set3, and remove set2.

I brought up a situation to consider: the rTWT AP/STA may run out of DL or UL traffic only and there is still pending traffic in the other direction.

This one needs further discussion.

 

Folks who joined the meeting or weren't able to, please feel free to comment and share your opinions.

We can have another call next week.

 

Thanks!

Chunyu

 

On Sun, Aug 15, 2021 at 9:43 AM Chunyu Hu <chunyuhu07@xxxxxxxxx> wrote:

Hi, all:

 

The contribution 11-21/1115r0 (CC36-CR-35.6 Traffic Prioritization During Restricted TWT SPs) was presented in the 08/12/2021 meeting.

There were many people in the Q queue that were not able to raise their questions. I've noted down: Rojan, Stephane, Mohamed, Liangxiao, Jason, Guarav, GGeorge, Bo and Sanghyun.

Please feel free to raise your questions here or offline to me.

 

There is a related contribution on this topic by Rubayet:

11-21/1020: Handling Fairness Issue in Restricted TWT

 

Suggested by the chair, please join us an offline meeting to discuss the topic.

Date/time: 

Monday 08/16/2021, 8-9:30AM

(If most folks cannot make it this time, we can move to Tuesday morning same time.)

 

Agendar:

Presentation (20min): 11-21/1020

Q/A for 11-21/1115 and 11-21/1020.

 

Folks if want to put the invite on your calendar, please let me know.

 

Thank you!

Chunyu

 

 

Chunyu Hu is inviting you to a scheduled Zoom meeting.

Topic: 11be discussion: rTWT SP traffic prioritization
Time: Aug 16, 2021 08:00 AM Pacific Time (US and Canada)

Join Zoom Meeting
https://fb.zoom.us/j/99758851146

Meeting ID: 997 5885 1146
Passcode: 123
One tap mobile
+16699006833,,99758851146#,,,,*123# US (San Jose)
+12532158782,,99758851146#,,,,*123# US (Tacoma)

Dial by your location
        +1 669 900 6833 US (San Jose)
        +1 253 215 8782 US (Tacoma)
        +1 346 248 7799 US (Houston)
        +1 301 715 8592 US (Washington DC)
        +1 312 626 6799 US (Chicago)
        +1 929 205 6099 US (New York)
        877 853 5247 US Toll-free
        888 788 0099 US Toll-free
        833 548 0276 US Toll-free
        833 548 0282 US Toll-free
Meeting ID: 997 5885 1146
Passcode: 123
Find your local number: https://fb.zoom.us/u/abLrR4rynD

Join by SIP
99758851146@xxxxxxxxxxx

Join by H.323
162.255.37.11 (US West)
162.255.36.11 (US East)
115.114.131.7 (India Mumbai)
115.114.115.7 (India Hyderabad)
213.19.144.110 (Amsterdam Netherlands)
213.244.140.110 (Germany)
103.122.166.55 (Australia Sydney)
103.122.167.55 (Australia Melbourne)
149.137.40.110 (Singapore)
64.211.144.160 (Brazil)
149.137.68.253 (Mexico)
69.174.57.160 (Canada Toronto)
65.39.152.160 (Canada Vancouver)
207.226.132.110 (Japan Tokyo)
149.137.24.110 (Japan Osaka)
Meeting ID: 997 5885 1146
Passcode: 123


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