doc.: IEEE /630r1a Submission S. Choi, Philips Research November 2001 Slide 1 HC Recovery and Backoff Rules Sunghyun Choi and Javier del Prado Philips Research USA Briarcliff Manor, New York

doc.: IEEE /630r1a Submission S. Choi, Philips Research November 2001 Slide 2 References IEEE e/D1.3 IEEE /412r0: “Aligning e HCF and h TPC operations ” by A. Soomro, S.Choi and J. del Prado IEEE /128r1: “HCF Channel Access And Inter-BSS Channel Sharing” by J.-M. Ho, et al.

doc.: IEEE /630r1a Submission S. Choi, Philips Research November 2001 Slide 3 Introduction Status as of e/D1.3

doc.: IEEE /630r1a Submission S. Choi, Philips Research November 2001 Slide 4 Problem Statement e/D1.3 has both recovery and backoff rule of HC, which look inconsistent HC backoff is not needed if the HC has the full control over the medium However, backoff is needed if Overlapping BSS (OBSS) exists HC Backoff may result in collision with its own ESTAs in the QBSS

doc.: IEEE /630r1a Submission S. Choi, Philips Research November 2001 Slide e/D1.3 Says … Clause 9.10 of D1.3 reads: “A HC may perform a backoff following an interruption of a frame exchange sequence due to lack of an expected response from an (E)STA, or due to detection of CCA busy within a CFP or CFB. This backoff shall occur under the rules of the EDCF, using dot11CWmin[7] and dot11AIFS[7].”

doc.: IEEE /630r1a Submission S. Choi, Philips Research November 2001 Slide e/D1.3 Says … And Clause of D1.3 reads: “ESTAs, including the HC, are required to respond within any frame exchange sequence after a SIFS period. If the beginning of reception of an expected response, as detected by the occurrence of PHY-CCA.indication(busy) at the ESTA which is expecting the response, does not occur during the first slot time following SIFS, that ESTA may initiate recovery by transmitting after PIFS from the end of the last transmission. This recovery after PIFS is only permitted by the ESTA expecting the response. This ESTA is the HC in case of a QoS (+)CF-Poll frame, and is the TXOP holder in case of a QoS data type frame transmitted during a CFB”

doc.: IEEE /630r1a Submission S. Choi, Philips Research November 2001 Slide 7 Status as of e/D1.3 …therefore, after sending a QoS (+)CF-Poll frame, the HC senses the medium and: –If PHY-CCA.indication busy is not detected The HC may recover transmission by sending a second frame (ref ) The HC may perform backoff (ref. 9.10) –If PHY-CCA.indication busy is detected The HC remains silent during the rest of the CFB (ref ) The HC may perform backoff (ref. 9.10); but, will not due to

doc.: IEEE /630r1a Submission S. Choi, Philips Research November 2001 Slide 8 But… After sending QoS (+)CF-Poll frame, detecting PHY-CCA.indication(busy) is enough, and it is not needed to receive the frame correctly Was the QoS (+)CF-Poll received correctly? Is the frame received by the HC from the Polled (E)STA? If these two things are not true, it results in the loss of the TXOP. But, no way to find it out!

doc.: IEEE /630r1a Submission S. Choi, Philips Research November 2001 Slide 9 Proposed Solution

doc.: IEEE /630r1a Submission S. Choi, Philips Research November 2001 Slide 10 Proposed Solution (1) If PHY-CCA.indication (busy) is not detected within PIFS after the HC sending any frame which requires response, e.g., QoS (+)CF- Poll, the HC may recover transmission or perform backoff both after PIFS –Which one to do is up to the HC algorithm, and out of the scope of e spec. –For example, the HC may want to backoff if it knows the OBSS existence.

doc.: IEEE /630r1a Submission S. Choi, Philips Research November 2001 Slide 11 Proposed Solution (2) If PHY-CCA.indication (busy) is detected within PIFS after the HC sending a QoS (+)CF-Poll frame: –The HC needs to have PHY-RXSTART.indication before PHY-CCA.indication (idle). –If PHY-RXSTART.indication happens, the HC assumes that the TXOP was granted successfully. –If PHY-RXSTART.indication does not happen, it could mean a collision of the QoS (+)CF-Poll with another frame, e.g., from neighboring HC, so HC may perform backoff after PHY-CCA.indication (idle)

doc.: IEEE /630r1a Submission S. Choi, Philips Research November 2001 Slide 12 Proposed Solution (3) If PHY-CCA.indication(busy) is detected within PIFS after the HC sending an RTS or non-CF- Poll QoS Data(+) frame: –If there were PHY-RXSTART.indication, PHY- CCA.indication(idle), and PHY-RXEND.indication, and the response is not received correctly, the HC may retransmit the frame or transmit another frame after SIFS from PHY-CCA.indication(idle) –If there was not PHY-RXSTART.indication before PHY-CCA.indication (idle), it may perform backoff as it may mean a collision

doc.: IEEE /630r1a Submission S. Choi, Philips Research November 2001 Slide 13 HC Backoff Rules For the random backoff procedure HC shall use: –AIFS HC = PIFS (a fixed MIB value) –CW min = CW max = CW HC (a fixed MIB value) –CW HC could be 3 (ref. 01/128r1) –The random backoff will reduce collisions with other HCs The HC may set AIFS [i] for every i to > PIFS+ CW HC –Increasing the AIFS [i] will avoid collisions with EDCF access

doc.: IEEE /630r1a Submission S. Choi, Philips Research November 2001 Slide 14 Summary HC recovery or backoff depending on PHY- RXSTART.indication(.) as well as PHY- CCA.indication(.) Random backoff with fixed contention window size for HCs to avoid collisions with other HCs Increasing AIFS[i] for EDCF access to avoid collision with HC A best-effort & simple approach to handle OBSS problem