| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Dibakar, I have same view with Yunbo. There are too many issues to be discussed for MU cases. Let keep them to R2 discussion. It is good to keep TF with unified design now from STA implementation point of view. BR, Xiangxin Unisoc Technologies Co., Ltd. +86 21 20360600 3324 From: Liyunbo <liyunbo@xxxxxxxxxx>
Hi Dibakar, Thanks for the offline discussion about the signaling of time allocation, you already know my opinions. Here I just want to repeat it here to the group for others to consider. I prefer Option 2 (in common info), the reasons are below:
1)
Signaling in common info aligned with current TF design, UL Length in basic TF servers a very similar function as time allocation here;
2)
Signaling in common info can support well for allocation for single STA (what Trigger SU mechanism currently supports), and can also support allocation to multiple STAs
(will be discussed in R2), as long as multiple STA are allocated for same time duration (e.g. Co-SR, Co-OFDMA);
3)
What opt 2 can not support is the scenario that allocate time to multiple STAs and each STA has different time duration. I think it is not a simple extension for current
Trigger SU. It may affect a lot for signaling and procedure, not only the time allocation. I think we need discuss the use case and procedure first before we go into the frame format design;
4)
In R2, if the group agree to allocate time for multiple STAs, and each STA allows to has different time duration. There are still a lot of reserved field to carry the signaling
or add a new MU-RTS TXS TF mode, in that case we can have a brand new frame format design for it. So there is no concern that opt2 will close the door for future extension. Regards, Yunbo 发件人: Das, Dibakar [mailto:dibakar.das@xxxxxxxxx]
Hi all, I uploaded document 268r4 related to the channel access for triggered SU.
Regarding the signaling of the time allocation, I received two opposite offline feedback.
Option 1: signal the information in User Info. This will allow an easy extension in R2 in case we want to extend this signaling for other purposes such as Multi-user TXOP Sharing or C-TDMA. Option 2: signal the information in Common Info, in particular the UL Length field. This keeps it aligned with baseline design of the TF wrt usage of UL Length field. However, it makes
it more convoluted to extend the signaling for any multi-user cases in future because 1. It changes the signaling location for same functionality (i.e., allocated time) based on whether its for SU or MU and 2. The number of available reserved bits in User
Info is much smaller than one in Common Info which could result in different granularity of time allocation in the SU and MU variants.
Personally, I think Option 1 is more forward-looking and will simplify the design for any multi-user TXOP sharing procedure while not adding any complexity for the SU cases in r1. However, the current document assumes
Option 2. Please let me know if you have a preference on Option 1 or Option 2 and if you have any suggestions on how to resolve this issue. Regards, Dibakar From: Arik Klein <arik.klein@xxxxxxxxxx>
Hi Dibakar, Thanks for the document. Please review my comments in the attached document. Regards, Arik From: Das, Dibakar <dibakar.das@xxxxxxxxx>
Hi all, I uploaded a new revision of
268r2 (Triggered SU channel access) to mentor. Please review. I tentatively added as co-author the members who contributed to the spec text. Please let me know offline if you don’t want your name to be included and I can remove it in the next revision. Regards, Dibakar From: Das, Dibakar <dibakar.das@xxxxxxxxx>
Hi Alfred, Please add the following PDT to queue:
Regards, Dibakar From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Hello all, I uploaded an updated version of the agendas, which contains the agenda for the next conference calls, scheduled on Monday, February
08 (MAC/PHY), 10:00-12:00 ET. The agendas can be found here: DIAL IN DETAILS FOR MONDAY: Join the MAC meeting here:
https://ieeesa.webex.com/ieeesa/j.php?MTID=m0a0a9cac185f64cce900514e8966e029
Meeting number: 179 045 1588 Meeting password: wireless (94735377 from phones and video systems) Join the PHY meeting here:
https://ieeesa.webex.com/ieeesa/j.php?MTID=m974d0a1712c60e96e275d9e504af8977 Meeting number: 179 596 9157 Meeting password: wireless (94735377 from phones and video systems) Please let me know if you have any questions and/or clarifications. Best Regards, Alfred -- Alfred Asterjadhi, PhD IEEE802.11 TGbe Chair, Qualcomm Technologies Inc. Cell #: +1 858 263 9445 Office #: +1 858 658 5302 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
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
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 |