Discussion on 11be R2 Scope and Main Solution
The document from November 2021 discusses the scope of the 11be R2 release, highlighting the need to keep the scope small to effectively manage features. The timeline, target milestones, and challenges in defining features for the second release are outlined. The main solution proposed involves moving the numerous and complex features in the category of Coordinated APs/Multi-AP to the next 11 program to streamline development.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
November 2021 doc.: 21/1598r1 Discussion on 11be R2 scope Date: 2021-11-08 Authors: Name Affiliations Address Phone email Laurent Cariou Intel Robert Stacey Intel Carlos Cordeiro Intel George Cherian Qualcomm Vinko Erceg Broadcom Submission Slide 1 Laurent Cariou, Intel Corporation
November 2021 doc.: 21/1598r1 TGbe Timeline PAR approved First TG meeting D0.1 D1.0 Letter Ballot D2.0 LB D3.0 LB Initial Sponsor Ballot (D4.0) Final 802.11 WG approval 802 EC approval RevCom and SASB approval Mar 2019 May 2019 Sept 2020 May 2021 Mar 2022 Nov 2022 May 2023 Mar 2024 Mar 2024 May 2024 We are here Stable Release 1 Features Stable Release 2 Features Submission
November 2021 doc.: 21/1598r1 Discussion on 11be R2 scope (1/2) Target for 11be is: R1 stable with D2.0 in March 2022 R2 stable with D4.0 in May 2023 2-year cycle between releases (R1/R2) R2 scope (market-wise) is usually smaller and our preference is to keep it like that 4-year cycle between 802.11 generations Plan is for next .11 project (following 11be) to be 4-year shifted compared to 11be timeline Meaning starting scope discussions in 2022 for a TG start mid-2023. Submission Slide 3 Laurent Cariou, Intel Corporation
November 2021 doc.: 21/1598r1 Discussion on 11be R2 scope (2/2) Number of features that will make it to 11be second release products will be smaller that the number of features that will make it to 11be first release products In spite of great and successful effort to reduce/limit 11be R1 scope, we still have defined too many features for the market to absorb That means that some 11be R1 features already defined will naturally come to market with a second release of product (R2) The number of features left to define in 11be R2 to complete the R2 product program is therefore even more limited Limited time to define 11be R2 features Conclusion: we should keep 11be R2 scope small Submission Slide 4 Laurent Cariou, Intel Corporation
November 2021 doc.: 21/1598r1 Main solution to fix R2 scope issue Among the features that have been identified as candidate for 11be, the features in the category of Coordinated APs / Multi-AP are particularly numerous and challenging to define (C-TDMA, C-OFDMA, C-SR, coordinated beamforming, joint processing, ) We believe that this category of Multi-AP features should be moved to next .11 program As we ve seen in the past, it is difficult to split this category into multiple parts due to the commonality of signaling Multi-AP features will constitute a very good feature set for next .11 program We believe choosing just one flavor of Multi-AP will not fix the issue A minimal common set of features/signaling need to be added to incorporate even just a single flavor/mode Obviously don t want different signaling for different flavors/modes Design of this minimal set of features/signaling will therefore need to take into considerations all the flavors/modes Gains evaluation will take too much time If we want to pick one, more discussion/time needed to select the one This would be the main factor to reconcile the issue raised in previous slides regarding timeline/scope of 11be R2. Submission Slide 5 Laurent Cariou, Intel Corporation
November 2021 doc.: 21/1598r1 SP Do you support that: Multi-AP features are not defined in 11be C-TDMA, C-OFDMA, C-SR, C-BF, joint transmission for single and multi-user Submission Slide 6 Laurent Cariou, Intel Corporation
