Re: [STDS-802-11-TGBN] Confirmation topics for the Editor meeting regard

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

Nope, still not seeing "CBF" anywhere. And not seeing "compressed beamforming"

either, except in "compressed beamforming feedback matrix", which I think is

obviously "compressed {beamforming feedback matrix}" not

"{compressed beamforming} feedback matrix".

Thanks,

Mark

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

Samsung Cambridge Solution Centre Tel: +44 1223 434600

1 Cambridge Square, Cambridge CB4 0AE Fax: +44 1223 434601

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

From: HARRY BIMS <harrybims@xxxxxxxxxx>
Sent: Thursday, 29 May 2025 19:25
To: Mark Rison <m.rison@xxxxxxxxxxx>
Cc: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Confirmation topics for the Editor meeting regarding abbreviation and acronyms

Take a look at 19.3.12.3.6 ini 802.11-2024.

Harry

On May 29, 2025, at 1:19 PM, Mark Rison <m.rison@xxxxxxxxxxx> wrote:

Hello Xiaogang,

802.11 doesn't have certification documents, so whatever you're referring

to is outside the scope of 802.11. I don't even know what "compressed

beamforming" is, in fact -- we compress beamforming reports (so maybe we

have compressed beamforming reports, CBRs), but not the beamforming itself.

Perhaps this is a bug that needs to be fixed in these certification

documents?

Thanks,

Mark

--

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

Samsung Cambridge Solution Centre Tel: +44 1223 434600

1 Cambridge Square, Cambridge CB4 0AE Fax: +44 1223 434601

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

From: Xiaogang Chen <xiaogang.g.chen@xxxxxxxxx>
Sent: Thursday, 29 May 2025 16:17
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] 回复: Confirmation topics for the Editor meeting regarding abbreviation and acronyms

Hi Mark,

Although CBF has not been used in IEEE 802.11, it has widely been used as abbreviation for "compressed beamforming" in certification document. To avoid confusion in the certification process, I suggest to keep it as CoBF or something similar. Thanks.

On Thu, May 29, 2025 at 7:44 AM Mark Rison <m.rison@xxxxxxxxxxx> wrote:

> CBF is already used for compressed beamforming

Where? I do not find this in 802.11-2024 (nor do I find it in 11be/D7.0).

Thanks,

Mark

--

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

Samsung Cambridge Solution Centre Tel: +44 1223 434600

1 Cambridge Square, Cambridge CB4 0AE Fax: +44 1223 434601

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

From: Yujian (Ross Yu) <00001792b51ef4ea-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Thursday, 15 May 2025 11:01
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] 回复: Confirmation topics for the Editor meeting regarding abbreviation and acronyms

Hello all,

Regarding the following abbreviations, as CBF is already used for compressed beamforming.

I will keep the following abbreviations as they are for now:

Co-BF

Co-SR

Co-TDMA

Co-RTWT

Will further check with the editor group. And get back. Thanks.

Regards

Ross Jian Yu 于健

Huawei Technologies

发件人: Yujian (Ross Yu)
发送时间: 2025年5月13日 8:30
收件人: 'Yusuke Asai' <yusuke.asai@xxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
抄送: 'Stacey, Robert' <robert.stacey@xxxxxxxxx>
主题: 回复: Confirmation topics for the Editor meeting regarding abbreviation and acronyms

Hello Yusuke-san and all,

Regarding the questions below, please find the feedback from the editor's group:

To Ross > Could you please confirm these topics at the next Editor meeting and feedback to TGbn members?

- Do we need to add the abbreviation terms (Subclause 3.4) that are already used in the baseline standard or amendments but have not explicitly been defined in subclause 3.4 yet?

(e.g. CFO, SINR, RL-SIG are already used but not included in the subclause 3.4.)

Ross: if the abbreviations are only locally used, then provide abbreviation when the term is firstly used. No need to add them into subclause 3.4. If the abbreviations are globally used in the whole draft, then could provide abbreviations also in subclause 3.4.

- Do we need to define the abbreviation terms that are newly defined in subclause 3.2?

(e.g. TGbn D0.1 newly defines DRU in subclause 3.2. Do we also need to define abbreviation of DRU in subclause 3.4 as well?)

Ross: the answer is no.

- How do we utilize the hyphen?

(e.g. Which is better for the abbreviation of "intermediate FCS", IFCS or I-FCS?)

Ross: recommend no hyphen, so IFCS.

Also, for the following multi-AP mechanism in 11bn, the following style is recommended:

CBF

CSR

CTDMA

CRTWT

Besides, do not over use abbreviations, for example CoAP doesn’t save much compared with coordinated AP.

Please see if you have any other comments or concerns. If not, I plan to do a global editorial change in the next revision of the draft accordingly.

Regards

Ross Jian Yu 于健

Huawei Technologies

-----邮件原件-----
发件人: Yusuke Asai <yusuke.asai@xxxxxxx>
发送时间: 2025年5月12日 14:23
收件人: Yujian (Ross Yu) <ross.yujian@xxxxxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
主题: RE: Confirmation topics for the Editor meeting regarding abbreviation and acronyms

Hello Ross,

Thank you!

Regards,

Yusuke.

-----Original Message-----

From: Yujian (Ross Yu) <ross.yujian@xxxxxxxxxx>

Sent: Monday, May 12, 2025 9:18 PM

To: Yusuke Asai（淺井裕介） <yusuke.asai@xxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx

Subject: 回复: Confirmation topics for the Editor meeting regarding abbreviation and acronyms

Hi Yusuke-San,

Thanks. Will collect feedback and get back to this group.

Regards

Ross Jian Yu 于健

Huawei Technologies

-----邮件原件-----

发件人: Yusuke Asai <yusuke.asai@xxxxxxx>

发送时间: 2025年5月12日 14:14

收件人: Yujian (Ross Yu) <ross.yujian@xxxxxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx

主题: Confirmation topics for the Editor meeting regarding abbreviation and acronyms

Hello Ross and TGbn members,

In the presentation of 25/0717r1 (CC for abbreviation and acronyms) during the last TGbn joint session, there are several topics that should be confirmed.

To Ross > Could you please confirm these topics at the next Editor meeting and feedback to TGbn members?

- Do we need to add the abbreviation terms (Subclause 3.4) that are already used in the baseline standard or amendments but have not explicitly been defined in subclause 3.4 yet?

(e.g. CFO, SINR, RL-SIG are already used but not included in the subclause 3.4.)

- Do we need to define the abbreviation terms that are newly defined in subclause 3.2?

(e.g. TGbn D0.1 newly defines DRU in subclause 3.2. Do we also need to define abbreviation of DRU in subclause 3.4 as well?)

- How do we utilize the hyphen?

(e.g. Which is better for the abbreviation of "intermediate FCS", IFCS or I-FCS?)

To TGbn members > If there are other topics that should be confirmed, please share them.

Best regards,

Yusuke

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

--

BRs,

Xiaogang.

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