[STDS-802-11-TGM] Updated REVme PHY ad hoc comment spreadsheet -- MOTION

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

Hello,

https://mentor.ieee.org/802.11/dcn/21/11-21-0727-05-000m-revme-phy-comments.xls

has been uploaded. The following resolutions, from the PHY Motion D and D2 tabs,

are due to be motioned during the session at 10:00 ET (14:00 UTC) on Monday 25 October:

CID	Commenter	Comment	Proposed Change	Resolution
283	Mark RISON	A description of the ERP PHY transmit procedure is missing	Add a Subclause 18.3.4a PHY transmit procedure	REVISED (PHY: 2021-10-18 15:19:38Z) At (D0.0) 2944.58, add new subclause 18.3.4a as follows, and renumber subclauses: "18.3.4a PHY transmit procedure The transmit procedure for Clause 18 (Extended Rate PHY (ERP) specification) when TXVECTOR parameter FORMAT is equal to NON_HT and TXVECTOR parameter NON_HT_MODULATION is ERP-DSSS or ERP-CCK is described in 15.3.6 (Transmit PHY) or 16.2.5 (Transmit PHY), respectively. The transmit procedure and state machine when TXVECTOR parameter FORMAT is equal to NON_HT and TXVECTOR parameter NON_HT_MODULATION is ERP-OFDM is described in 17.3.11 (Transmit PHY), except for the signal extension (refer to 18.3.2.4 (ERP-OFDM PPDU format))."
12	Bo Sun	In VHT and HE PHY, we defined TXVECTOR/RXVECTOR parameters table in a duplication way which includes parameters that will not be present in specific PHY. Such design will accumulate more and more redundant parameters of no no use but increasing the complexity of the table and spec pages.	Update table 21-1 and improve the TXVECTOR/RXVECTOR table for 11ax to remove redundant and meaningless parameters. Keep parameters that only make sense to the specific PHY layer.	REVISED (PHY: 2021-09-28 12:40:54Z) Note to Commenter: The proposed text update below removes TX/RXVECTOR parameters not used by the ‘current’ PHY. Instruction to Editor: Implement the proposed text updates for CID 12 in 11-21/1136r1 <https://mentor.ieee.org/802.11/dcn/21/11-21-1136-01-000m-cc35-txvector-rxvector.docx>
21	Brian Hart	Because of past/current technologies like TX antenna diversity switching and future looking technologies like massive MIMO, we should clean up the usage of "antenna" in 802.11 PHY clauses, since oftentimes this is a simplfication and really we are referring to the output of a TX chain (that might be conected to 1 antenna as expected, or multiple antennas with separately controlled phasing, or a switch and then multiple antennas). Closely related, the currently defined term "antenna connector" is needed (but that name is not good) and we also need an agreed term for a physical antenna connector.	a) change "antenna connector" to "logical antenna connector" for clarity. b) define a new term or terms like "physical antenna connector", "antenna port", "TX chain output", "RX chain output" to represent the single output of a TX chain / single input of an RX chain c) carefully review instances of "logical antenna connector" that don't make sense, such as section 15.4.4.10, and replace by the new term.	REJECTED (PHY: 2021-10-18 14:31:48Z) This comment has been withdrawn by the commenter.
20	Brian Hart	The language describing spatial expansion is confusing / misleading for pilot tones in VHTSIGB: "have pilots inserted following the steps described in 21.3.10.10 (Pilot subcarriers). The VHT-SIG-B field constellation points are mapped to N STS,u space-time streams by the user-specific elements of the first column of the P VHT-LTF matrix" suggests pilot insertion first and second multiplication by P for all tones, which differs from (21-47). (21-47 is assumed to be correct since it closely follows the VHT Daa field equation in this regard.	Change to "have pilots inserted following the steps described in 21.3.10.10 (Pilot subcarriers). The data subcarriers of the VHT-SIG-B field constellation points are mapped to N STS,u space-time streams by the user-specific elements of the first column of the P VHT-LTF matrix"	ACCEPTED (PHY: 2021-10-01 15:48:40Z)
18	Brian Hart	11be is adding the concept that some reserved PHY bits or values are Validate and some are Disregard. This concept works well for certain fields in PHY clauses.	Define the LSIG Reserved bit and the 8 undefined values of the RATE field as "Validate", conditioned on dot1SomethingSomething (to allow for legacy implementations that might not check these fields). Incorporate these Validate checks and dot11SomethingSomething into the RX procedure (17.3.12).	REVISED (PHY: 2021-09-20 22:07:22Z) Incorporate the changes for CID 18 in 11-21/0965r7: https://mentor.ieee.org/802.11/dcn/21/11-21-0965-07-000m-cc35-phy-cids-19-18-14-15-527.docx
98	John Coffey	This introductory subclause establishes that "tests in this subclause" are carried out in a conducted configuration. This makes sense for many requirements, in particular for minimum receiver sensitivity, but not for energy detect, cf. 3208.20 (21.3.18.5.4), where the receiver should defer whenever a power level of -62 dBm is encountered over the air.	At a minimum, add the qualifier "Except where otherwise noted," before "Each output port". At 3208.20, change "any signal" to "any signal, however received,", and add at end of paragraph "The requirements of this paragraph apply for all received signals; in particular, they are not limited to configurations in which each output port of a transmitting STA are connected through a cable to each input port of the receiving STA."	REVISED (PHY: 2021-10-18 15:06:29Z) At 3204.53, replace the paragraph with: “For tests in this subclause, the input levels are measured at the antenna connector and are referenced as the average power per receive antenna. For tests in Subclauses 21.3.18.1, 21.3.18.2, and 21.3.18.3, the number of spatial streams under test shall be equal to the number of utilized transmitting STA antenna (output) ports and also equal to the number of utilized device under test input ports. Except where otherwise noted, each output port of the transmitting STA shall be connected through a cable to one input port of the device under test.”

Thanks,

Mark

Mark RISON, Standards Architect, WLAN English/Esperanto/Français

Samsung Cambridge Solution Centre Tel: +44 1223 434600

Innovation Park, Cambridge CB4 0DS Fax: +44 1223 434601

ROYAUME UNI WWW: http://www.samsung.com/uk

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

[STDS-802-11-TGM] Updated REVme PHY ad hoc comment spreadsheet -- MOTION planned MONDAY (25 OCT)