Hi Alfred,
There is a typo in my previous email (thanks You-wei), please help to add these two PHY motions:
Motion 1: Move to include the following text to the 11bn SFD (DCN# 12-24/1831r2, DCN# 11-24/1840r0):
·
Keep other fields except the disregard bits in Common field for non-OFDMA transmission in UHR-SIG to be the same as that in common field for non-OFDMA transmission in EHT-SIG as following.
B0-B3
|
B4-B5
|
B6-B8
|
B9
|
B10-B11
|
B12
|
B13-B15
|
B16-B18
|
Spatial Reuse
|
GI+LTF Size
|
Number of UHR-LTF Symbols
|
LDPC Extra Symbol Segment
|
Pre-FEC padding Factor
|
PE Disambiguity
|
Disregard
|
Number of non-OFDMA Users
|
Result: no objection
Motion 2:
Move to include the following text to the 11bn SFD (DCN# 12-24/1831r2):
·
Keep the Common field format of UHR-SIG for OFDMA transmission adheres to the Table 36-33 of 11be D7.0
Note: The entries defined for OFDMA + MU-MIMO in RU Allocation table may be updated
Common field for OFDMA transmission
|
B0-B3
|
B4-B5
|
B6-B8
|
B9
|
B10-B11
|
B12
|
B13-B16
|
B17-B16+9N
|
B17+9N-B20+9N
|
B21+9N-B26+9N
|
B27+9N-B26+9N+9M
|
B27+9N+9M-B30+9N+9M
|
B31+9N+9M-B36+9N+9M
|
Spatial Reuse
|
GI+LTF Size
|
Number of UHR-LTF Symbols
|
LDPC Extra Symbol Segment
|
Pre-FEC padding Factor
|
PE Disambiguity
|
Disregard
|
RU Allocation-A
|
CRC
|
Tail
|
RU Allocation-B
|
CRC
|
Tail
|
Result: no objection
Thanks,
Juan
From: You-Wei Chen <ywchen77115@xxxxxxxxx>
Sent: Thursday, December 5, 2024 2:08 PM
To: Fang, Juan <juan.fang@xxxxxxxxx>
Cc: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Motions List for December 19th
Hi Alfred,
Please add the followings to the PHY Motion list:
Motion 1: Move to include the following text to the 11bn SFD (DCN# 11-24/1695r1, 11-24/1840r0):
Signaling design for MU MIMO User field in UHR-SIG field as shown in the below figure.
-
Also when Coding field indicates LDPC, then 2XLDPC indication:
-
Bit22 set to 1: TX encode LDPC using code size as 2x1944
-
Bit22 set to 0: TX encode LDPC using code size of 648, 1296, or 1944.
Result: no objection
Motion 2: Move to include the following text to the 11bn SFD (DCN# 11-24/1695r1, 11-24/1840r0):
Signaling design for non-MU MIMO User field in UHR-SIG field as shown in the below figure.
-
Bit19 set to 1: UEQM is applied, B20-21 are redefined to indicate UEQM patterns.
-
Bit19 set to 0: EQM is applied. (B20 and B21 are Bfed and Coding bits)
-
Alos when Coding field indicates LDPC, then 2XLDPC indication:
-
Bit22 set to 1: TX encode LDPC using code size as 2x1944
-
Bit22 set to 0: TX encode LDPC using code size of 648, 1296, or 1944
Result: no objection
btw, the motion request sent by Juan, the DCN number should be 12-24/1831r2.
BR,
You-Wei
Hi Alfred,
Please help add the following to the TGbn PHY motion list:
Motion 1: Move to include the following text to the 11bn SFD (DCN# 12-24/1381r2, DCN# 11-24/1840r0):
·
Keep other fields except the disregard bits in Common field for non-OFDMA transmission in UHR-SIG to be the same as that in common field for non-OFDMA transmission in EHT-SIG as following.
B0-B3
|
B4-B5
|
B6-B8
|
B9
|
B10-B11
|
B12
|
B13-B15
|
B16-B18
|
Spatial Reuse
|
GI+LTF Size
|
Number of UHR-LTF Symbols
|
LDPC Extra Symbol Segment
|
Pre-FEC padding Factor
|
PE Disambiguity
|
Disregard
|
Number of non-OFDMA Users
|
Result: no objection
Motion 2:
Move to include the following text to the 11bn SFD (DCN# 12-24/1381r2):
·
Keep the Common field format of UHR-SIG for OFDMA transmission adheres to the Table 36-33 of 11be D7.0
Note: The entries defined for OFDMA + MU-MIMO in RU Allocation table may be updated
Common field for OFDMA transmission
|
B0-B3
|
B4-B5
|
B6-B8
|
B9
|
B10-B11
|
B12
|
B13-B16
|
B17-B16+9N
|
B17+9N-B20+9N
|
B21+9N-B26+9N
|
B27+9N-B26+9N+9M
|
B27+9N+9M-B30+9N+9M
|
B31+9N+9M-B36+9N+9M
|
Spatial Reuse
|
GI+LTF Size
|
Number of UHR-LTF Symbols
|
LDPC Extra Symbol Segment
|
Pre-FEC padding Factor
|
PE Disambiguity
|
Disregard
|
RU Allocation-A
|
CRC
|
Tail
|
RU Allocation-B
|
CRC
|
Tail
|
Result: no objection
Thanks,
Juan
This is a gentle reminder to send me (including the reflector) an e-mail with a list of candidate motions for December 19th. The deadline for these requests is Decemeber 7th.
I am providing below the announcement i made during yesterday's Joint Telco:
·
We have motions scheduled during the Joint telco of December 19th, 2024.
§
We need to get WG approval and send a 10-day advanced notice for the motions that we plan to run during that session.
§
To meet this requirement and align with our MO, I need by Dec 7th, 2024:
·
Members that have SPs with “super majority” positive opinion (75+%) to send me the text of that SP so that I can add to the motion list
·
Members that have SPs that are queued to be ran before/during December 19th, 2024, to send me the text of that SP so that I can add to the motion list
·
If the SP shows “super majority” (75+%) positive opinion prior to the scheduled motion, then we keep the corresponding motion and update the note below the motion with the
SP result
·
If the SP does not show “super majority” positive opinion prior to the scheduled motion or is not ran, then we will remove the corresponding motion from the motion list.
·
Note: Text changes to the motion text during this 10-day period is fine as long as it does not lead to major technical changes to the motion.
§
Per procedure, other motions are allowed to be requested as well provided that they are sent by Dec 7th, 2024, and they are approved by the WG chair.
--
IEEE802.11 TGbe/TGbn Chair,
Qualcomm Technologies Inc.
Office #: +1 858 658 5302
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
|