Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-11-TGM] Comment resolution on aRxPHYStartDelay in 23/138 (CID 3038)



--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---

Hi Xiaogang – many thanks for the review! Inline -B

 

From: Xiaogang Chen <xiaogang.chen@xxxxxxxx>
Sent: Friday, February 10, 2023 9:34 PM
To: Brian Hart (brianh) <brianh@xxxxxxxxx>; STDS-802-11-TGM@xxxxxxxxxxxxxxxxx
Subject: RE: Comment resolution on aRxPHYStartDelay in 23/138 (CID 3038)

 

Hi Brian,

Can you help to clarify the following understandings:

  1. The main benefit of the new primitive is to unify the aRxPHYStartDelay? (it’s still not unified but less dependent on other parameters)

[Unification is somewhat of a side-effect; mainly this proposal is to deal with the fact that aRxPHYStartDelay has multiple values in the PHY clauses but a single value in the MAC and related sections, and so to reconcile that inconsistency. An important side-effect is that the new primitive RXEARLYSIG.indication allows for lower values of aRxPHYStartDelay.]

 

  1. For some times, e.g. ACKTimeout or CTSTimeout, there is no difference no matter choosing RXEARLYSIG.indication or PHY-RXSTART.indication because it’s non-HT?

[Basically yes. Now, if their times are identical, the proposal is that no RXEARLYSIG.indication is even issued, just PHY-RXSTART.indication (i.e., the proposal makes minimal changes).]

 

  1. Since aRxPHYStartDelay is using a fixed value now, RXEARLYSIG.indication becomes mandatory to issue and PHY-RXSTART.indication becomes optional in most cases?

[I’d say this a little differently. In terms of timeouts, the earlier of RXEARLYSIG.indication (if present) and PHY-RXSTART.indication is used. PHY-RXSTART.indication is still always needed to convey all the SIG fields.]

 

BRs,

Xiaogang.

 

From: Brian Hart (brianh) <00000c7561051aea-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, February 8, 2023 9:21 AM
To: STDS-802-11-TGM@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGM] Comment resolution on aRxPHYStartDelay in 23/138 (CID 3038)

 

--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---

Hi all

 

Heads up that this CID will be discussed on Monday Feb 27. The comment resolution creates a new primitive PHY-RXEARLYSIG.ind to report when a PPDU is being received *before* the end of the final SIG. This allows fr oa smaller aRxPHYStartDelay  and then for Ack/CTS/etc timeouts to occur earlier, since, for the classic OFDM PHYs, a single value of 24usec can typically be achieved. There are also changes to clarify that there can be multiple values of aRxPHYStartDelay and the MAC selects among them according to context.

 

Please feel free to review and provide feedback beforehand in order to help keep the 11me telecon discussion efficient.

 

Best regards

Brian

 

 


To unsubscribe from the STDS-802-11-TGM list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM&A=1

ZEKU

信息安全声明:本邮件包含信息归发件人所在组织ZEKU所有。 禁止任何人在未经授权的情况下以任何形式(包括但不限于全部或部分披露、复制或传播)使用包含的信息。若您错收了本邮件,请立即电话或邮件通知发件人,并删除本邮件及附件。

Information Security Notice: The information contained in this mail is solely property of the sender's organization ZEKU. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email immediately and delete it.


To unsubscribe from the STDS-802-11-TGM list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM&A=1