Hi Edward, Motion 116 is passed in the last Joint call, but it isn't changed in r35. Can you add the change? Move to add to the TGbe SFD: • TGbe supports the below pilot indices for 26/52/106/242/484RU in 80/160/320MHz PPDU • In a OFDMA/non-OFDMA with puncturing 80MHz EHT PPDU • [Pilot indices in 40MHz]-256, [Pilot indices in 40MHz]+256 • In a OFDMA/non-OFDMA with puncturing 160MHz EHT PPDU • [Pilot indices in 80MHz]-512, [Pilot indices in 80MHz]+512 • In a OFDMA/non-OFDMA with puncturing 320MHz EHT PPDU • [Pilot indices in 160MHz]-1024, [Pilot indices in 160MHz]+1024 Move: Second: Discussion: Preliminary Result: • Note: This motion contains an amendment to the text from SP #79 • [20/0838r3 (Pilot subcarriers for new tone plan, Jinyoung Chun, LGE), SP#2, Y/N/A: 35/0/2] Best regards, Jinyoung From: Edward Au [mailto:edward.ks.au@xxxxxxxxx]
Sent: Thursday, July 2, 2020 11:06 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] Announcement: Motions for TGbe on Thursday 9th of July 2020 at 10:00am ET- Deadline Reminder Acknowledged with thanks, Chunyu. Correct -- this motion is for R1/R2 feature discussion, and doesn't result in any text to be added into SFD. If your motion is passed, may I know if there is anything I need to add into the SFD? Just want to confirm as your proposed text is not that actionable from the editing point of view. Thanks :)
Regards,
Edward Hi, Alfred: Can you add the following motion from SP of contribution DCN 11-20/697r3 to the list? Move to support a staged feature development to support latency sensitive applications as following o Release 1: • A basic framework under multi-link operation framework that includes link management and QoS provisioning • Channel access optimization/design for low latency o Release 2: • Extend to support multi-BSS coordination for low latency • Any additional features (including additional channel access improvements) Notes • Channel access improvement for low latency implies more predictable channel access • R1 can include any other essential components to make the framework functional. • Whether to introduce different mechanisms for different classes of low-latency applications is TBD Hi Alfred, In the last PHY call (6/22), there was a SP as below because the original SP has a typo. l Do you support to replace straw poll #79 in 565r32 with SP2 in 838r3? 35Y/0N/2A So I think we need to change SP#79 as below. Straw poll #79 Do you support the below pilot indices for 26/52/106/242/484RU in 80/160/320MHz PPDU of 11be? · in a OFDMA/non-OFDMA with puncturing 80MHz EHT PPDU o [Pilot indices in 40MHz]-256, [Pilot indices in 40MHz]+256 · in a OFDMA/non-OFDMA with puncturing 160MHz EHT PPDU o [Pilot indices in 80MHz]-512, [Pilot indices in 80MHz]+512 · in a OFDMA/non-OFDMA with puncturing 320MHz EHT PPDU o [Pilot indices in 160MHz]-1024, [Pilot indices in 160MHz]+1024 [#SP79] [20/0838r3 (Pilot subcarriers for new tone plan, Jinyoung Chun, LGE), SP#2, Y/N/A: 35/0/2] Best regards, Jinyoung From: Alfred Asterjadhi [mailto:asterjadhi@xxxxxxxxx]
Sent: Thursday, June 25, 2020 6:54 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] Announcement: Motions for TGbe on Thursday 9th of July 2020 at 10:00am ET- Deadline Reminder Hi Ross, That is correct. Those are covered by Motion 115 in 11-20/841r5. The deadline is for any other motions. Hi Alfred, For the SPs currently in Edward's document, are they default added to the motion list? --------------------------------------------------
regards
于健 Ross Yu
Sent from Great Huawei Mate 20X 主 题：[STDS-802-11-TGBE] Announcement: Motions for TGbe on Thursday 9th of July 2020 at 10:00am ET- Deadline Reminder Please let me know if you have any requests for motions to be added to the July 9th Agenda by today, Wednesday EOD ET. This is an advanced notification that TGbe will run motions during the Joint teleconference scheduled on Thursday 09th of July 2020 at 10:00am ET.
I will be uploading the motions document with the new motions by Thursday, so if you have any requests/suggestions please let me know by Wednesday.
Let me know if you have any questions. -- Qualcomm Technologies Inc. Office #: +1 858 658 5302
-- Qualcomm Technologies Inc. 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 |