Access during an MCCAOP by mesh STAs that are not the MCCAOP owner

Slides:



Advertisements
Similar presentations
Doc.: IEEE /xxxxr0 Submission May 2010 Jarkko Kneckt, NokiaSlide 1 M-QoS Comments Date: Authors:
Advertisements

Doc.: IEEE /0117r0 Submission January 2010 Michael Bahr, Siemens AGSlide 1 TBTT Announce in DTIM Beacons Date: Authors:
Doc.: IEEE /1294r0 Submission September 2011 Rolf de Vegt, QualcommSlide 1 Spec Framework Text for.11ah Bandwidth Modes Date: Authors:
PS-Poll TXOP Using RTS/CTS Protection
Doc.: IEEE /1123r0 Submission September 2010 Zhu/Kim et al 1 Date: Authors: [TXOP Sharing for DL MU-MIMO Support]
Doc.: IEEE /1303r5 Submission November 2010 Jarkko Kneckt (Nokia)Slide 1 Overlapping BSS Co-Existence Date: Authors:
Doc.: IEEE /0065r2 Submission January 2011 Ivan Pustogarov, IITP RASSlide 1 GCR for mesh Date: January 2011 Authors:
Doc.: IEEE /1468r0 Submission Dec 2008 Ashish Shukla, Marvell SemiconductorSlide 1 ERP Protection in IEEE s Mesh Network Date:
Doc.: IEEE s Submission January 2011 Dee Denteneer, PhilipsSlide 1 MCCAOP Advertisement discussion Date: Authors:
Doc.: IEEE /1047r0 September 2015 SubmissionStéphane Baron et. al., Canon Random RU selection process upon TF-R reception Date: Slide.
Doc.: IEEE /0562r0 Submission May 2009 L. Chu et alSlide 1 MCF Issues Date: Authors:
Doc.: IEEE r1 SubmissionAlexander Safonov, IITP RASSlide 1 Parameterized QoS for s mesh networks Date: March 2012 Authors:
Submission doc.: IEEE /0615r0 May 2012 Sudheer Grandhi, InterDigital CommunicationsSlide 1 Considerations for early NAV indication Date:
Doc.: IEEE /0072r0 Submission January 2009 Slide 1 Proxy ARP Issue for Direct Link Setup Notice: This document has been prepared to assist IEEE.
Resolutions to Static RTS CTS Comments
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:
Peer Power Save Mode Date: Authors: March 2008 March 2008
Wide Scanning Requests and Responses
ANQP-SD Response When Service Mismatches
GCR for mesh Date: January 2011 Authors: January 2011 July 2010
AP access procedure for UL MU operation
Long SlotTime Option for RTS/CTS Procedure
Channel Access Efficiency
Fair and Protected DLS September 2007 Date:
Channel Access for WUR FDMA
MCCA Comments Resolution 159 ppt
MCCAOP Advertisements
Considerations on Trigger Frame for Random Access Procedure
Multicast/Broadcast Communication With Acknowledge
Fair and Protected DLS September 2007 Date:
EDCA and BlockAck Extensions for Reliable Multicast/Broadcast Services
MAC Clarifications Date: Authors: September 2016
Audio and video support by MCCA
EDCA Enhancement to Improve Link Reliability for Multicast Streams
Peer Power Save Mode Date: Authors: March 2008 March 2008
Overlapping BSS Co-Existence
Overlapping BSS Co-Existence
Scheduled Medium Access For Large Low Power BSS
AP Location Capability
Resolution for CID 118 and 664 Date: Authors: Month Year
MDA comments categorization
QoS STA function applied to Mesh STA
Proposed Resolutions to RFI comments of LB 166 on IEEE s D7.0
Comment Resolutions Date: Authors: February 2008
Explanations on CID #10076 Date: Authors: May 2006 May 2006
HCF medium access rules
QoS map addition Date: Authors: May 2007 May 2007
Overlapping BSS Co-Existence
Setting of DTIM Interval for MCCA
QoS STA function applied to Mesh STA
Peer Power Save Mode Date: Authors: January 2008
PS-Poll TXOP Date: Authors: Month Year
July 2007 doc.: IEEE /2090r0 Aug 2007 Discussion on CCA Sensing on 20/40 MHz Secondary Channel with PIFS and DIFS Date: Authors: Notice:
Random Access UL MU Resource Allocation and Indication
802.11ax Spec Development Process Proposal
Long SlotTime Option for RTS/CTS Procedure
Direct transmission in PSM
MCCAOP Advertisements
Resolutions of the Remaining Power Management Comments
Setting of DTIM Interval for MCCA
Proposed Change to Intra-Mesh Congestion Notification Frame
GCR for mesh Date: January 2011 Authors: January 2011 July 2010
MRG for mesh Date: July 2010 Authors: July 2010 July 2010
Reserving STA Date: Authors: January 2011 January 2011
Channel Access for WUR FDMA
Considerations on Trigger Frame for Random Access Procedure
MRG IFS Correction Date: July 2010 Authors: July 2010 Month Year
Month Year doc.: IEEE /1081r0 May, 2016
Peer Traffic Indication enhancements
Presentation transcript:

Access during an MCCAOP by mesh STAs that are not the MCCAOP owner Month Year doc.: IEEE 802.11-yy/xxxxr0 Access during an MCCAOP by mesh STAs that are not the MCCAOP owner Date: November 10, 2010 Authors: Alexander Safonov, IITP RAS Alexander Safonov, IITP RAS

Month Year doc.: IEEE 802.11-yy/xxxxr0 Abstract According to the draft 7.02, an MCCA enabled mesh STA shall not initiate its transmissions within MCCAOPs owned by other STAs But the STA can easily initiate its transmission before the MCCAOP, no matter how much time left before the MCCAOP beginning This rule causes a problem: however MCCA enabled mesh STAs declare that they respect MCCAOPs owned by other STAs, it fact they do not, as their EDCA TXOPs still may overlap with MCCAOPs owned by others The value of MCCA diminishes because of this problem The problem can be solved by adding one more paragraph to the draft, which is proposed in this submission Alexander Safonov, IITP RAS Alexander Safonov, IITP RAS

Problem Statement Although MCCA capable mesh STAs are not allowed to start their transmissions within MCCAOPs owned by others, they are allowed to start transmissions shortly before the MCCAOPs. So, MCCAOP and EDCA TXOPs may overlap This may lead to: 1)MCCA TXOP truncation or 2) collisions, in case of hidden stations Alexander Safonov, IITP RAS

Possible solution 1 Just before its packet transmission, a station checks whether it has enough time to send this packet before the next MCCAOP i.e. the station checks the inequality: TDATA+TSIFS+TACK < tMCCA - current_time where tMCCA is the MCCAOP start time If OK, the STA starts its transmission If NOT OK, the STA defers its transmission and starts new round of the backoff procedure after the MCCAOP is finished Alexander Safonov, IITP RAS

Possible solution 2 Just before its packet transmission, a station checks whether it has enough time to send this packet before the next MCCAOP i.e. the station checks the inequality: TDATA+TSIFS+TACK < tMCCA - current_time where tMCCA is the MCCAOP start time If OK, the STA starts its transmission If NOT OK, the STA defers its transmission and starts new round of the backoff procedure immediately Alexander Safonov, IITP RAS

Possible normative text covering both solution 1 and solution 2 Add the following text after the first sentence of the second paragraph of clause 9.9a.3.11.2 in IEEE 802.11s_D7.02 “When a MCCA enabled mesh STA obtains an EDCA TXOP, the STA shall not start its transmission if the TXOP cannot be finished before the start of an MCCAOP corresponding to a reservation in its neighborhood MCCAOP times. Instead, the STA shall defer the transmission and initiate another backoff procedure with the same value of CW.” Alexander Safonov, IITP RAS

Strawpoll Should the normative text in the previous slide be considered for inclusion in the current draft? Yes: No: Abstain: Alexander Safonov, IITP RAS

Acknowledgement The proposal was made in the framework of ICT FP7 project FLAVIA Alexander Safonov, IITP RAS