identified as Inter-BSS frame for NAV update. TGax editor changes as shown in the as specified in 11-17/0347r. 5506 Yet another power save Delete the scheme it adds Revised – scheme. In this case it is nothing new. stating that a STA can go When the received into power save if it is not packet is not for the STA, interested in the received if the STA enters the packet. Hmm...it can do doze for NAV/PPDU that now withut the need duration, the STA may to define what packets the miss the PPDU sent from STA is not interested in. the STA’s associated AP In general if the packet is because the AP might not for the STA, having not know whether the checked the NAV/duration STA enters the doze a STA could doze if it state or not. wants. There is no need But, during Intra-PPDU to go through all this text TX times, AP will never which, as I said, merely send the STA any defines a packet that the packet. Therefore, we STA need not decode. I need to list the correct can't see the need for this conditions for the STA to at all and furthermore it enter the doze state involves no interoperablity without its packet loss. at all and is at the Intra-PPDU PS is defined discretion of the STA - if it for the purpose. wants to doze then let it. Instead of entering the doze state during PPDU, STA may discard the PPDU as the resolution of CID 7602. TGax editor makes changes as shown in the as specified in 5938 Besides intra-PPDU As suggested Revised – power save for HE Power saving for STAs, allowing them frames may create to enter doze mode till the the problem of failing the end of an inter-BSS intended packet PPDU TXOP with reception. For example, if received power > a STA enters the doze OBSS_PDmax may state during the further save some power. PPDU duration, the STA may not receive a frame sent from its associated AP. Instead of entering the doze state during PPDU, STA may discard the PPDU as the resolution of CID 7602.
identified as Inter-BSS frame for NAV update. TGax editor changes as shown in the as specified in 11-17/0347r. 5506 Yet another power save scheme. In this case it is stating that a STA can go into power save if it is not interested in the received packet. Hmm...it can do that now withut the need to define what packets the STA is not interested in. In general if the packet is not for the STA, having checked the NAV/duration a STA could doze if it wants. There is no need to go through all this text which, as I said, merely defines a packet that the STA need not decode. I can't see the need for this at all and furthermore it involves no interoperablity at all and is at the discretion of the STA - if it wants to doze then let it. Delete the scheme it adds nothing new. Revised – When the received packet is not for the STA, if the STA enters the doze for NAV/PPDU duration, the STA may miss the PPDU sent from the STA’s associated AP because the AP might not know whether the STA enters the doze state or not. But, during Intra-PPDU TX times, AP will never send the STA any packet. Therefore, we need to list the correct conditions for the STA to enter the doze state without its packet loss. Intra-PPDU PS is defined for the purpose. Instead of entering the doze state during PPDU, STA may discard the PPDU as the resolution of CID 7602. TGax editor makes changes as shown in the as specified in 5938 Besides intra-PPDU power save for HE STAs, allowing them to enter doze mode till the end of an inter-BSS PPDU TXOP with received power > OBSS_PDmax may further save some power. As suggested Revised – Power saving for frames may create the problem of failing the intended packet reception. For example, if a STA enters the doze state during the PPDU duration, the STA may not receive a frame sent from its associated AP. Instead of entering the doze state during PPDU, STA may discard the PPDU as the resolution of CID 7602.
11-17-0347-02-00ax-lb225-cr-on-intra-ppdu-ps-27-14-1.docx