Addressing Text Collision in IEEE Drafts: Proposed Solutions
Explore the challenges of text collision between IEEE 802.11bh and 802.11be drafts, along with proposed solutions like direct coverage and coordination modes. Learn how to resolve conflicts and ensure consistency in merging the drafts for IEEE standards.
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. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
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.
E N D
Presentation Transcript
Jun. 2024 Doc.: IEEE 802.11-24/1076r0 Some thoughts some thought on the text collision between 11bh and 11be draft Name Jay Yang Affiliations Address Phone email Yang.zhijie@zte.com.cn ZTE YanLi ZTE Yun Li ZTE Bo Sun Sanechips Submission Jay Yang al. (ZTE)
Jun. 2024 Doc.: IEEE 802.11-24/1076r0 CID Name Comment Based on 11bh draft4.0, TGbe extends 11bh feature under MLO framework in 11be draft7.0. Meanwhile, there are several changes on the baseline text of 11bh, 11bh draft should synchronize all the changes made by 11be draft to avoid the inconsistency issue. Proposed Change P/ /L Resolution Resolution 4003 Yang, Jay the commenter will make a contribution on this 36/12 Submission Slide 2 Jay Yang, et al. (ZTE)
Jun. 2024 Doc.: IEEE 802.11-24/1076r0 Recap the status of subclause 12.2.13 in TGbe and TGbh 11bh draft 4.0 text collision start here.. 11bh draft 5.0 11be draft 7.0 Involve PASN ID concept and other changes Involve device ID and IRM under MLO framework and other changes recycle SA text collision issue become serious.. 11bh draft 6.0 11be draft 8.0(if exist) Submission Slide 3 Jay Yang, et al. (ZTE)
Jun. 2024 Doc.: IEEE 802.11-24/1076r0 The problem when both drafts merged into 802.11mf Considering 11bh draft is the first amendment, 11bh draft will be into 802.11mf ahead of 802.11be. How to address the collided text? Directly cover mode: Regardless the text in 11bh draft, proceed it with the text in 11be draft on the collided text Coordination mode: Involve 11bh and 11be experts to discuss collided text and then finalize the rewording text Pros Cons Directly cover Editors can address it May loss some ideas made in 11bh group Need more technical efforts Coordination Editors can t address it Submission Slide 4 Jay Yang, et al. (ZTE)
Jun. 2024 Doc.: IEEE 802.11-24/1076r0 Non-collided text may become collided text Further reword or change on the text may make the non-collided text become collided text As 11be draft also has some changes in the baseline text If we go with directly cover mode, some the new changes in 11bh group may become invalid. If we go with coordination mode, need more efforts to identify the new collided text and provide the corresponding solution. The simple way is to get rid of the comment based on 11bh draft 5.0 --E.g. Reject any technical comment if the text is already reworded by 11be draft --E.g. Reject any technical comment if the new text may cause new collision with 11be draft --E.g. Encourage the commenter to make the comment in TGbe or TGmf. Submission Slide 5 Jay Yang, et al. (ZTE)
Jun. 2024 The following example(1) depicts some collided text between the red line revision and the proposed text in 24/1316(motioned) Doc.: IEEE 802.11-24/1076r0 Submission Slide 6 Jay Yang, et al. (ZTE)
Jun. 2024 The following example(2) depicts the collided text between the reline revision and the proposed text in 24/1316r1(motioned) Doc.: IEEE 802.11-24/1076r0 Submission Slide 7 Jay Yang, et al. (ZTE)
Jun. 2024 Doc.: IEEE 802.11-24/1076r0 Summary Analysis the text collision issue between 11bh draft and 11be draft Propose two options to address the collided text Submission Slide 8 Jay Yang, et al. (ZTE)
Jun. 2024 Doc.: IEEE 802.11-24/1076r0 reference [1].Draft P802.11bh_D5.0 Redline Compared to D4.0 [2]. 24/1006r1-00be-recycle-sa-for-cids-in-subcaluse12-2-12.docx Submission Slide 9 Jay Yang, et al. (ZTE)
Jun. 2024 Doc.: IEEE 802.11-24/1076r0 SP To meet 11bh timeline request and avoid invalid job, do you agree 11bh group should git rid of the CIDs in the recirculation SA with the following approach. 1) Reject any technical comment if the text is already reworded by 11be draft 2) Reject any technical comment if the proposed text may cause new collision with 11be draft 3)Recommand the commenter to submit it again in TGbe or TGmf. Note: Except the technical comments on PASN ID as it s a new feature in 11bh group Submission Slide 10 Jay Yang, et al. (ZTE)
Jun. 2024 Doc.: IEEE 802.11-24/1076r0 THANK YOU Submission
Jun. 2024 Doc.: IEEE 802.11-24/1076r0 SP1 Do you agree to have one or more dedicated TID queue for preemption data delivery? Submission Slide 12 Jay Yang, et al. (ZTE)
