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

Re: [STDS-802-11-TGBQ] TGbq teleconference announcement - 19, 26 August and 2 September 2025



Hi Xiangxin,

 

Thanks for reviewing the SP texts and providing your questions.

Here is the response below.

[// Xiangxin Gu] Should sub-7 GHz link and mmWave link be defined as terminologies ?

Jonghoe: In fact, the intention was not to propose to define the formal terminology to be included within the 11bq addendum.

Rather, it was to propose terms that are expected to be frequently used in TGbq discussions, along with their clear definitions and short aliases for simple use within the TGbq discussion.

In this regard, I would suggest to use IMMW AP/STA to indicate the AP/Non-AP MLD having a sub-7GHz link and a link operating mmWave band.

 [// Xiangxin Gu] What’s the intention for the first bullet ? The baseline has support a non-AP MLD to get information in Beacon of each link through ML Probe procedure.

Jonghoe: The statement in the first bullet is technically straightforward, stating the already supported behavior.

Although it is already supported in existing MLO, we may need some modifications for non-standalone mmWave link support based on the 11be MLO.

Specficially, one of proposals regarding SP5, which prevents exchanging multi-link probe request/response frame over the mmWave link, is related to this.

So, the first bullet can be considered as one of permissible behaviors under the potentially modified MLO that will be defined in TGbq.

 

[// Xiangxin Gu] The first bullet is not accurate. Association is between MLDs.

For the second bullet, what’s the difference between “delete” and “remove” ?

Jonghoe: ‘delete’ is to removing the mmWave link from the setup link from the non-AP MLD side while ‘remove’ is removing affiliated mmWave link from the AP MLD.

Each of them corresponds to ‘AP  Removal’ and ‘Delete Link’ Reconfiguration Operation Type in the Reconfiguration Multi-Link element for MLO link management.

 

 

Regards,

Jonghoe KOO

Communications Standards Research Team, Samsung Research

Samsung Electronics

 

From: 顾祥新 (Xiangxin Gu) <000046f9987a2d10-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Tuesday, August 12, 2025 11:05 AM
To: STDS-802-11-TGBQ@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBQ] TGbq teleconference announcement - 19, 26 August and 2 September 2025

 

Hi Jonghoe,

 

Thanks for initiating these SPs. Several questions in line.

 

 

BR,

 

Xiangxin Gu

Institute of Communication Technology

unisoc-signature

 

From: Edward Au <edward.ks.au@xxxxxxxxx>
Sent: Friday, August 8, 2025 6:38 PM
To: STDS-802-11-TGBQ@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBQ] TGbq teleconference announcement - 19, 26 August and 2 September 2025

 

Dear Jonghoe,

 

Thanks for your clarification.   You are the corresponding author of your contribution and I will wait for your confirmation on SP3a and SP3b.

 

Regards,

Edward

 

On Fri, Aug 8, 2025 at 2:36 AM Jonghoe Koo <jh89.koo@xxxxxxxxxxx> wrote:

Dear Edward,

 

Thanks for scheduling the presentation and providing kind guidance.

 

Regarding the number of SPs, if SP3a and SP3b are considered counterstatements to each other and can be viewed as a single SP, then the total number of SPs would indeed be 7.

 

Would it be possible for me to provide my preference on how to proceed the SP3a and SP3b (e.g., whether to introduce both SPs at the same call or to introduce SP3b later next call if SP3a fails.) after internal discussion?

 

Regards,

Jonghoe KOO

Communications Standards Research Team, Samsung Research

Samsung Electronics

 

From: Edward Au <edward.ks.au@xxxxxxxxx>
Sent: Thursday, August 7, 2025 10:41 PM
To: STDS-802-11-TGBQ@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBQ] TGbq teleconference announcement - 19, 26 August and 2 September 2025

 

Dear Jonghoe,

 

Thanks for your email.

 

1.  A question for clarification - as shown in the email below and the contribution 25/1193 - it seems to me that the number of straw polls is 7, not 8.   Please kindly clarify.

 

2.  I will allocate approximately 60 minutes for you to present a short summary of your contribution, followed by discussing and conducting each of the straw polls on Tuesday, 19 August 2025 (10:00am ET to 11:30am ET).

 

3.  You already set a good example in asking our participants their comments on your contribution and the respective straw polls.   Hope that we may have discussions/feedback received in this email reflector.

 

Regards,

Edward

 

 

 

On Wed, Aug 6, 2025 at 6:32 AM Jonghoe Koo <jh89.koo@xxxxxxxxxxx> wrote:

Dear Edward,

 

I would like to queue the following 8 SPs to present and discuss in any of three August/September TGbq teleconference calls.

The SPs are from 25/1193 which was presented at the July Interim meeting and the texts are slightly editorial changed.

Since the number of SPs are eight and the detailed content includes MLO-specific terminologies defined in 11be, it would be much nice to have a discuss them offline in order to gather comments for enhancing the SP texts before presenting them in a call.

So, it would be appreciated if members could provide any technical feedback or suggest deferring SPs that are not appropriate for discussion at this time to ensure efficient discussion during the call.

Regarding the above, I would be grateful if the Chair could kindly provide guidance on the direction of the pre-discussion proceedings.

 

The list of SP texts that I would like to request to put in the agenda is as follows:

-----------------------------------------------

SP1 – IMMW AP and IMMW STA terminologies

 

        Do you support to define the following terminologies for TGbq?

        TBD IMMW AP is the AP MLD that has one or more than one link operating on 2.4, 5, or 6 GHz bandwidth and has the only one link operating on 42-71 GHz bandwidth

        TBD IMMW STA is the non-AP MLD that has one or more than one link operating on 2.4, 5, or 6 GHz bandwidth and has the only one link operating on 42-72 GHz bandwidth

NOTE 1: TBD sub-7 GHz link is the term to indicate the one of the links operating on 2.4, 5, or 6 GHz bandwidth

NOTE 2: TBD mmWave link is the term to indicate the link operating on 42-71 GHz bandwidth and defined by the TGbq amendment

NOTE 3: Both TBD IMMW AP and TBD IMMW STA shall follow the additional rules or exceptions as defined in the TGbq amendment

        Result: Y/N/A

[// Xiangxin Gu] Should sub-7 GHz link and mmWave link be defined as terminologies ?

 

SP2 – Beacon discussion

        Do you support to add the following statement to the TGbq SFD?

        TBD IMMW AP shall transmit a Beacon via one of TBD sub-7GHz links containing the Reduced Neighbor Report element or the Basic Multi-Link element with the Per-STA Profile subelement corresponding to the TBD mmWave link in the Basic Multi-Link element

        TBD IMMW AP shall not transmit a Beacon via the TBD mmWave link containing the Reduced Neighbor Report element or the Basic Multi-Link element with the Per-STA Profile subelement corresponding to the TBD sub-7GHz links

        Result: Y/N/A

 [// Xiangxin Gu] Whats the intention for the first bullet ? The baseline has support a non-AP MLD to get information in Beacon of each link through ML Probe procedure.

 

SP3a – Beacon discussion (defining mmWave beacon)

        Do you agree the following statement?

        TBD IMMW AP may transmit via the TBD mmWave link a TBD IMMW Beacon in addition to the Beacon transmitted on one of the TBD sub-7GHz links

        Result: Y/N/A

 

SP3b – Beacon discussion (if SP3a does not get majority support)

        Do you agree the following statement?

        TGbq should not define a TBD IMMW Beacon that is periodically transmitted in addition to the Beacon transmitted on one of the TBD sub-7GHz links

        Result: Y/N/A

 

SP4 – mmWave link setup

        Do you support to add the following statement to the TGbq SFD?

        TBD IMMW STA shall follow the MLO defined in TGbe when it performs (re)association procedure with a TBD IMMW AP

        TBD IMMW STA and TBD IMMW AP shall follow the ML (re)setup and the ML reconfiguration procedures defined in TGbe when it adds/deletes/removes the TBD mmWave link

        Result: Y/N/A

[// Xiangxin Gu] The first bullet is not accurate. Association is between MLDs.

For the second bullet, whats the difference between delete and remove ?

 

SP5 – mmWave link shall not be a reporting AP during the ML discovery procedure

        Do you support to add the following statement to the TGbq SFD?

        TBD IMMW STA shall not transmit a Probe Request frame or multi-link Probe Request frame to the TBD IMMW AP over the TBD mmWave link

        Result: Y/N/A

 

SP6 – mmWave link setup and addition

        Do you support to add the following statement to the TGbq SFD?

        There are two cases that TBD IMMW STA (re)associates with the TBD IMMW AP and enables the TBD mmWave link.

        Case 1) TBD IMMW STA associates with a TBD IMMW AP by transmitting a multi-link Association Request frame with Basic Multi-Link element containing the Per-STA Profile for the TBD mmWave link in the Basic Multi-Link element

        Case 2) TBD IMMW STA which has associated with the TBD IMMW AP performs ML (re)setup to add the TBD mmWave link by transmitting to the TBD IMMW AP a Link Reconfiguration Request frame and the TBD IMMW AP responds to the TBD IMMW STA with the Link Reconfiguration Response frame with the status code of SUCCESS.

        Other additional cases are TBD

        Result: Y/N/A

 

SP7 – non-standalone characteristic of mmWave link from the setup link perspective

        Do you support to add the following statement to the TGbq SFD?

        TBD IMMW STA shall not delete or remove the all the TBD sub-7 GHz links if the TBD mmWave link is enabled, i.e., the TBD IMMW STA shall not have the TBD mmWave link as the only one setup link.

        Result: Y/N/A

 

 

Regards,

Jonghoe KOO

Communications Standards Research Team, Samsung Research

Samsung Electronics

 

From: Edward Au <edward.ks.au@xxxxxxxxx>
Sent: Friday, August 1, 2025 4:40 AM
To: STDS-802-11-TGBQ@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBQ] TGbq teleconference announcement - 19, 26 August and 2 September 2025

 

Hello TGbq participants,

 

As mentioned on Thursday, we will be holding 3 teleconferences in August/September 2025:

Tuesday, 19 August, 10:00am ET to 11:30am ET

Tuesday, 26 August, 10:00am ET to 11:30am ET

Tuesday, 2 September, 10:00am ET to 11:30am ET

 

Please let me know if you have any contribution and/or straw poll that you would like to present/consider in one of these teleconference calls.

 

Regards,

Edward


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

 


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

 

 


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


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

 



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