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

Re: [STDS-802-11] TGme topic for WG: Vendor Specific Trigger Type

--- This message came from the IEEE 802.11 Working Group Reflector ---

Hi Brian

When review the document #576, I have the following questions regarding the short PPDU detection (bear with me if this has already been discussed):

  1. … for a mimum duration of 4+8+0+4+min(20,20) = 28us or seven 11a/g OFDM symbols

Is this a typo? Should be 36 or 9 symbol? If so, the following need to be changed?

If the check of the parity bit is valid and the RATE field indicates 6 Mb/s in non-HT but the LENGTH field value in the L-SIG field indicates less than seven non-HT OFDM symbols, a PHY-RXSTART.indication primitive is not issued.

  1. For VHT, your calculations means there are at least 6 symbols after L-SIG. why the below is less than 5 instead of less than 6?

b) the L-SIG field indicates less than five OFDM symbols after the L-SIG field,

 

3. IMO, if we really want to use the LENGTH field to identify non-HT PPDU, it’s better to directly use the value of L_LENGTH instead of converting to number of symbols. E.g. for VHT, minimum time after L-SIG is 24us per your calculations, so LENTH field < 24/4*3-3 = 15 means PPDU is not VHT.

 

BRs,

Xiaogang.

 

From: Brian Hart (brianh) <00000c7561051aea-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Saturday, July 16, 2022 4:03 PM
To: STDS-802-11@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11] TGme topic for WG: Vendor Specific Trigger Type

 

--- This message came from the IEEE 802.11 Working Group Reflector ---

Hi all

 

In 11me, CID  1056, there is a proposal to add a Vendor Specific Trigger Type in order to facilitate prototyping. Any comments / concerns / suggestions / recommended directions are welcome.

 

The latest proposed language for this is in 22/576 (and see below):

 

TGme Editor, make the following changes to D1.0 shown by Word track changes under CID 1056

 

Table 9-46—Trigger Type subfield encoding(11ax)

Trigger Type subfield value

Trigger frame variant

0

Basic

1

Beamforming Report Poll (BFRP)

2

MU-BAR

3

MU-RTS

4

Buffer Status Report Poll (BSRP)

5

GCR MU-BAR

6

Bandwidth Query Report Poll (BQRP)

7

NDP Feedback Report Poll (NFRP)

8-1415

Reserved

15

Vendor Specific

 

The Trigger Dependent Common Info subfield in the Common Info field is optionally present based on the value of the Trigger Type field (see 9.3.1.22.2 (Basic Trigger frame format) to 9.3.1.22.10 (Vendor Specific Trigger frame format))

 

9.3.1.22.10 Vendor Specific Trigger frame format

 

The Trigger Dependent Common Info subfield is not present in the Vendor Specific Trigger frame. The Trigger Dependent User Info subfield of the Vendor Specific Trigger frame is defined in Figure 9-97a (Trigger Dependent User Info subfield format in the Vendor Specific Trigger frame).

 

 

Length

Organization Identifier

Vendor Specific Content

Octets

2

j

0 or more

 

Figure 9-97a (Trigger Dependent User Info subfield format in the Vendor Specific Trigger frame)

 

The Length field indicates the number of octets in the Trigger Dependent User Info subfield excluding the Length field.

 

The Organization Identifier field (see 9.4.1.31 (Organization Identifier field)) identifies the entity that has

defined the content of the Vendor Specific Content field. See 9.4.1.31 (Organization Identifier field) for the definition of j.

 

10.28 MAC frame processing

10.28.13 Trigger frame parsing

 

A STA that encounters an unknown Trigger Type subfield in the Common Info field of a Trigger frame shall ignore the frame.

 

Best regards

Brian

 

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

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