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

[STDS-802-11-TGAX] 答复: 1528r0 - Segment parser changed to Subblock parser discussion

Hi Xiaogang,

 

Thanks for the comment. Segment parser within a segment is also acceptable to me. And the inline text already mentioned the bits are divided into two frequency subblokcs.

 

Let’s see if others have further comments.

 

regards

于健 Ross Jian Yu

Huawei Technologies

 

发件人: Chen, Xiaogang C [mailto:xiaogang.c.chen@xxxxxxxxx]
发送时间: 2020年9月24日 22:19
收件人: Yujian (Ross Yu) <ross.yujian@xxxxxxxxxx>; STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
主题: RE: 1528r0 - Segment parser changed to Subblock parser discussion

 

Hi Ross,

Given that 80MHz “segment” and “segment parser” is used for a long time and people understand the concept well, not sure we need to change the terminology now.

Since 160MHz has 1 segment, there is a de-parser for 160MHz. And frequency subblock is also not necessarily better than frequency segment IMO.

 

BRs,

Xiaogang.

 

From: *** 802.11 TGax - HEW - High Efficiency WLAN *** <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx> On Behalf Of Yujian (Ross Yu)
Sent: Thursday, September 24, 2020 2:09 AM
To: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGAX] 答复: 1528r0 - Segment parser changed to Subblock parser discussion

 

Retry. Sorry if you have received it twice.

 

regards

于健 Ross Jian Yu

Huawei Technologies

 

发件人: Yujian (Ross Yu)
发送时间: 2020年9月24日 17:00
收件人: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx; 'brianh@xxxxxxxxx' <brianh@xxxxxxxxx>
主题: 1528r0 - Segment parser changed to Subblock parser discussion

 

Hi Brian and all,

 

There is one comment from Brian saying segment parser is not a good term for 160MHz PPDU because there is only one segment for 160MHz PPDU. Subblock parser is a better wording. Technically I agree with Brian. The only concern is that this is a procedure/term used since 11ac. Currently I make the changes as Brian suggested. All your comments are welcome.

 

CID

Page.

Line

Clause Number

Comment

Proposed Change

Resolution

25009

627.65

27.3.11.7.10

On behalf of Brian Hart:

 

From P566L27 in table 27-13, 160M has one frequency segment but 80+80 has two frequency segments, yet oftentimes 160M is treated as having two frequency segments when the correct term is frequency subblock (e.g. P627L65, P628L2, P630L13, P651L38). Also, confusingly, the segment parser for 160M has two outputs (and the deparser has two inputs)

Use "frequency subblock" where this is the more more correct language (check especially P627L65, P628L2, P630L13, P651L38). Add "number of frequency subblocks" to table 27-13; rename "Segment (de)parser to "Frequency subblock (de)parser" throughout the draft.

REVISED

 

Agreed with the commenter. Speify the changes below.

 

Instructions to the editor, plase make the changes as shown under CID 25009 in doc 11-20/1528r0

 

 

There are also 3 other comments that are also assigned to me. Your comments are also welcome.

Below please find the link to the document.

https://mentor.ieee.org/802.11/dcn/20/11-20-1528-00-00ax-sig-b-cr-on-d7-0.doc

 

regards

于健 Ross Jian Yu

Huawei Technologies

 

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

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