Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
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 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 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 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> Hello TGbq participants, As mentioned on Thursday, we will be holding 3 teleconferences in August/September 2025: 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 |