Doc.: IEEE 802.11-09/0562r0 Submission May 2009 L. Chu et alSlide 1 MCF Issues Date: 2009-05-10 Authors:

Slides:



Advertisements
Similar presentations
Doc.: IEEE /272a Submission June 2001 S. Choi, Philips Research Slide 1 Problems with IEEE (e) NAV Operation and ONAV Proposal Javier del.
Advertisements

Doc.: IEEE /xxxxr0 Submission May 2010 Jarkko Kneckt, NokiaSlide 1 M-QoS Comments Date: Authors:
Doc.: IEEE /1355r2 11ah Submission Date: Authors: Nov 2012 James Wang, MediaTek Slide 1.
Doc.: IEEE /0696r2 SubmissionLiwen Chu Etc.Slide 1 Slot-based Power Save without PS-Poll Date: Authors: Date: July, 2012.
Doc.: IEEE /0798r1 Submission July 2008 L. Chu Etc.Slide 1 HT Features in Mesh Network Date: Authors:
Doc.: IEEE /0798r3 Submission September 2008 L. Chu Etc.Slide 1 HT Features in Mesh Network Date: Authors:
Doc.: IEEE /630r1a Submission S. Choi, Philips Research November 2001 Slide 1 HC Recovery and Backoff Rules Sunghyun Choi and Javier del Prado.
Doc.: IEEE /1325r0 Submission Nov PS-Poll TXOP Date: Authors: David Xun Yang, Huawei, et. al.Slide 1.
PS-Poll TXOP Using RTS/CTS Protection
Doc.: IEEE /630r4a Submission S. Choi, Philips Research January 2002 Slide 1 HC Recovery and Backoff Rules Sunghyun Choi and Javier del Prado.
Doc.: IEEE /1123r0 Submission September 2010 Zhu/Kim et al 1 Date: Authors: [TXOP Sharing for DL MU-MIMO Support]
Slide 1 doc.: IEEE /1092r0 Submission Simone Merlin, Qualcomm Incorporated September 2010 Slide 1 ACK Protocol and Backoff Procedure for MU-MIMO.
Submission doc.: IEEE /1357r3 Nov Slide 1 Dynamic TIM and Page Segmentation Date: Authors: Weiping Sun, Seoul National University.
Doc.: IEEE /879r3 Submission August 2004 Abel Dasylva, Nortel NetworksSlide 1 Class-based Contention Periods (CCP) for the n MAC A. Dasylva,
Submission doc.: IEEE /1454r1 November 2014 Jarkko Kneckt (Nokia)Slide ax Power Save Discussion Date: Authors:
Submission doc.: IEEE /1454r0 November 2014 Jarkko Kneckt (Nokia)Slide ax Power Save Discussion Date: Authors:
Submission doc.: IEEE 11-12/279r0 March 2012 Jarkko Kneckt, NokiaSlide ai simulations Date: Authors:
Doc.: IEEE /1303r5 Submission November 2010 Jarkko Kneckt (Nokia)Slide 1 Overlapping BSS Co-Existence Date: Authors:
Doc.: IEEE /1468r0 Submission Dec 2008 Ashish Shukla, Marvell SemiconductorSlide 1 ERP Protection in IEEE s Mesh Network Date:
Doc.: IEEE /1265r0 Submission November 2008 Liwen Chu, et al.Slide 1 STA Communication Inside a BSS and Outside the Context of a BSS Date:
Submission doc.: IEEE 11-12/0281r0 March 2012 Jarkko Kneckt, NokiaSlide 1 Recommendations for association Date: Authors:
Doc.: IEEE /0880r2 Submission Scheduled Trigger frames July 2015 Slide 1 Date: Authors: A. Asterjadhi, H. Choi, et. al.
Doc.: IEEE /0102r2 SubmissionLiwen Chu Etc.Slide 1 TGah Power Saving Date: Authors: Date: Jan, 2012.
Doc.: IEEE /0840r1 Submission AP Assisted Medium Synchronization Date: Authors: September 2012 Minyoung Park, Intel Corp.Slide 1.
Doc.: IEEE /1234r0 Submission October 2008 L. Chu Etc.Slide s Power Saving Issues Date: Authors:
Doc.: IEEE /0071r0 January 2013 Submission Channel indication in RAW/TWT Date: Authors: Merlin, Qualcomm Slide 1.
Doc.: IEEE /1047r0 September 2015 SubmissionStéphane Baron et. al., Canon Random RU selection process upon TF-R reception Date: Slide.
Submission doc.: IEEE /1348 Multiple NAVs for Spatial Reuse Date: Slide 1IITP Authors: Nov 2015 NameAffiliationAddressPhone Evgeny.
Doc.: IEEE r1 SubmissionAlexander Safonov, IITP RASSlide 1 Parameterized QoS for s mesh networks Date: March 2012 Authors:
Doc.: IEEE /0635r2 Submission July 2008 L. Chu Etc.Slide 1 MDA Issues Date: Authors:
Doc.: IEEE /0819r1 Submission July 2012 Hongyuan Zhang, et. Al.Slide 1 Preamble Discussions Date: Authors:
Doc.: IEEE /1086r0 SubmissionSlide 1 Date: Authors: Improved Virtual Carrier Sensing Mechanism for 45GHz Sep ZTE Corp.
Submission doc.: IEEE /0098r0 January 2016 Assaf Kasher, IntelSlide 1 Channel bonding proposals Date: Authors:
Doc.: IEEE /1165r0 Submission November 2005 Fischer (Broadcom), Stephens (Intel) et. al.Slide 1 Joint Proposal MAC Report Notice: This document.
Resolutions to Static RTS CTS Comments
Doc.: IEEE /0116r0 SubmissionLiwen Chu Etc.Slide 1 Low Collision EDCA Date: Authors: Date: Jan, 2012.
Channel Access in A-BFT over Multiple Channels
Doc.: IEEE /0624r2 SubmissionLiwen Chu Etc.Slide 1 Scheduled Medium Access For Large Low Power BSS Date: Authors: Date: May, 2012.
Doc.: IEEE /1468r1 Submission Jan 09 Ashish Shukla, Marvell SemiconductorSlide 1 ERP Protection in IEEE s Mesh Network Date:
Submission doc.: IEEE /0662r0 May, 2016 Jing Ma, NICTSlide 1 Further consideration on channel access rule to facilitate MU transmission opportunity.
Submission doc.: IEEE /0353r1 March 2016 Hanseul Hong, Yonsei UniversitySlide 1 MU-RTS/CTS for TWT Protection Date: Authors:
AP access procedure for UL MU operation
Power Efficient PS Poll
MCCA Comments Resolution 159 ppt
Suggested comment resolution on MDA Access Fraction (MAF)
Multicast/Broadcast Communication With Acknowledge
EDCA and BlockAck Extensions for Reliable Multicast/Broadcast Services
Overlapping BSS Co-Existence
RTS CTS Rule Amendment Date: Authors: Date: January 2011
Scheduled Medium Access For Large Low Power BSS
Resolution for CID 118 and 664 Date: Authors: Month Year
Slot-based Power Save without PS-Poll
Slot-based Power Save Improvement
Comment Resolutions Date: Authors: February 2008
80MHz/160MHz Protection Date: Authors: Date: September 2010
Access during an MCCAOP by mesh STAs that are not the MCCAOP owner
MCCA Comments Resolution 159 ppt
Power Efficient PS Poll
HT Features in Mesh Network
Overlapping BSS Co-Existence
80MHz/160MHz Protection Date: Authors: Date: September 2010
80MHz/160MHz Protection Date: Authors: Date: September 2010
Applicability of 11s MCCA to HCCA OBSS
VTS Robust Multicast/Broadcast Protocol
80MHz/160MHz Protection Date: Authors: Date: September 2010
MDA Simulation Study: MDAOP Stretching and Other Concerns
80MHz/160MHz Protection Date: Authors: Date: September 2010
Resolutions of the Remaining Power Management Comments
80MHz/160MHz Protection Date: Authors: Date: September 2010
Enhancement of Low Power Medium Access STAs
Presentation transcript:

doc.: IEEE /0562r0 Submission May 2009 L. Chu et alSlide 1 MCF Issues Date: Authors:

doc.: IEEE /0562r0 Submission May 2009 L. Chu et alSlide 2 MCCAOP MCF EDCA

doc.: IEEE /0562r0 Submission May 2009 L. Chu et alSlide 3 MCCAOP and EDCA TXOP A MCCAOP may includes multiple EDCA TXOPs. RAV makes the processing complicated. –A MCCA-capable mesh STA needs to maintain NAV and RAV. –RAV creates further unfairness among MCCA-capable mesh STAs and legacy mesh STAs. Duration MCCAOP TXOP Limit MCCA Owner CF-End Data NAV MCCA-Capable STA Data RAV Reset RAV? If yes, MCCA-capable STA may contend with MCCAOP Owner. If no, it is unfair compared with legacy STA. NAV Legacy STA Reset NAC Data

doc.: IEEE /0562r0 Submission May 2009 L. Chu et alSlide 4 EDCA TXOP, PSMP & HCCA PSMP allows a STA to transmit frames from multiple ACs in a TXOP which can save more power. –Why doesn’t MCCA allow a STA to transmit frames from multiple ACs in a MCCAOP to save more power? The AP can start PSMP TXOP through EDCAF or PIFS without backoff. The EDCA TXOP definition is accordingly changed to: –“Note that, as for an EDCA TXOP, a multiple frame transmission is granted to an EDCAF, not to a non-AP STA or AP, so that the multiple frame transmission is permitted only for the transmission of a frame of the same AC as the frame that was granted the EDCA TXOP, unless the EDCA TXOP obtained is used by an AP for a PSMP sequence, in which case, this AC transmission restriction does not apply to either the AP or the STAs participating in the PSMP sequence, but the specific restrictions on transmission during a PSMP sequence described in 9.16 (PSMP Operation) do apply”. In a reserved HCCA TXOP, it is up to the polled STA to decide which frames to transmit regardless the granted TXOP for a special TS. –Why does MCCA have the restriction that the reserved MCCAOP shall only transmit the frames for the indicated AC?

doc.: IEEE /0562r0 Submission May 2009 L. Chu et alSlide 5 Different DTIM Beacon Intervals In a mesh BSS, each mash STA can select different DTIM Beacon interval. –A MP can not reference its Neighbor MP’s MDAOP TXOP as a fixed offset with respect to its own MDAOP TXOP, because the MDAOP TXOP “slide” with respect to each other. TDBTT Subinterval TDIM Beacon Interval Offset TDBTT Subinterval TDIM Beacon Interval Offset TDBTT Subinterval Duration Subinterval TDIM Beacon Interval TDBTT TDIM Beacon Interval Subinterval

doc.: IEEE /0562r0 Submission May 2009 L. Chu et alSlide 6 Solutions: Reference DTIM Beacon Interval for MCCA Solution 1: all MCCA-capable mesh STAs use the default DTIM interval as its DTIM interval if they want to use MCCA. –Otherwise, MCCA is disabled in a MCCA-capable STA if the default DTIM interval is not used. –The DBTT is random selected to avoid beacon collision. Solution 2: all MCCA-capable mesh STAs use the default DTIM interval as the reference interval to select MCCAOP.

doc.: IEEE /0562r0 Submission May 2009 L. Chu et alSlide 7 Solutions: MCCAOP is Equal to EDCA TXOP RAV is not required. –A MCCA-capable mesh STA SHALL interpret the reception of a CF-End frame as a NAV reset. It is fair to legacy STAs and MCCA-capable STAs after receiving CF-End from MCCA Owner and MCCA Responder. The protocol becomes simple. Duration MCCAOP MCCA Owner CF-End Data NAV MCCA-Capable STA Data NAV Legacy STA Reset NAC

doc.: IEEE /0562r0 Submission May 2009 L. Chu et alSlide 8 Solutions: MCCAOP Access In a MCCAOP, it is up to the MCCAOP owner to decide which frames to transmit regardless the granted AC. This is similar to HCCA reserved SP and PSMP reserved SP. This can further save the power when MCCA is used for power saving.

doc.: IEEE /0562r0 Submission May 2009 L. Chu et alSlide 9 MCCA MCF EDCA

doc.: IEEE /0562r0 Submission May 2009 L. Chu et alSlide 10 TXOP Truncation A TXOP owner may transmit a CF-End frame to truncate the NAV when it empties its transmission queue. An AP may respond by transmitting a CF-End frame after SIFS. A non-AP STA that is not the TXOP holder shall not transmit a CF-End frame. –This is unfair to the neighbor mesh STAs of the TXOP receiver in a mesh BSS. A STA shall interpret the reception of a CF-End frame as a NAV reset. In a MBSS, if source mesh STA only transmits CF-End to truncate a TXOP, it is not fair to the neighboring mesh STAs of the destination STA. Solution: in subclause add the following sentence “in a mesh BSS, a TXOP receiver may respond by transmitting a CF-End frame after SIFS. ”

doc.: IEEE /0562r0 Submission May 2009 L. Chu et alSlide 11 MCF EDCAF Backoff & Retransmission Mesh STA is added to EDCA backoff procedure and Retransmission procedure. But a mesh STA has the same rules of the backoff and retransmission as a QoS STA. –Since a mesh STA is a QoS STA, the mesh STA is not required to be mentioned in these places. Solution: delete subclause and from the draft.