| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Alfred, I have updated docs 1124 and 1125 based on offline discussions with several members. Could you please add the following docs to the queue? 11-23/1124r3 (LB271 CIDs on TDLS) [SP + 1C] 11-23/1125r4 (LB271 Remaining CIDs on TWT) [SP] 11-23/1276r0 (LB271 Remaining CIDs on TDLS) [1C] **** Hi All,
*********************************
Start of resolution for CID #15244*********************************** Option-1 TGbe editor: Please add the following paragraph as the new last paragraph in clause 35.3.24.3 (Broadcast TWT operation) (#15244) (#15244)An AP affiliated with an NSTR mobile AP MLD and operating on the primary link may advertise a broadcast
TWT schedule for the other AP affiliated with the same NSTR mobile AP MLD and operating on the nonprimary link by including the TWT element containing the corresponding Broadcast TWT Parameter Set field in the STA Profile field of the Per-STA Profile subelement
of the Basic Multi-link element corresponding to the AP operating on the nonprimary link carried in the Beacon frames and Probe Response frame that it transmits on the primary link. The value in the Broadcast TWT Persistence subfield corresponding to the broadcast
TWT schedule shall be in reference to the most recent TBTT and BI indicated by the AP operating on the primary link. TGbe editor: Please revise the first paragraph of clause 35.3.4.4 (Multi-Link element usage in the context of discovery) as the new last paragraph in clause 35.3.24.3
(Broadcast TWT operation) (#15244) If an AP affiliated with an AP MLD is not in a multiple BSSID set or the AP corresponds to a transmitted BSSID in a multiple BSSID set, then the AP, in a Beacon frame
and a Probe Response frame that is not a multi-link probe response that it transmits, — shall include the Multi-Link Control field and the Common Info field of the Basic Multi-Link element for the AP MLD as defined in 9.4.2.312.2 (Basic Multi-Link
element) — shall not include the Link Info field of the Basic Multi-Link element for the AP MLD unless conditions in 35.3.11 (Multi-link procedures for (extended) channel
switching and channel quieting) are satisfied or unless the AP is affiliated with an NSTR mobile AP MLD and operating on the primary link, and advertises a broadcast TWT schedule for the other AP affiliated with the same NSTR
mobile AP MLD and operating on the nonprimary link. — may include a Reconfiguration Multi-Link element as defined in 9.4.2.312.4 (Reconfiguration Multi- Link element) and 35.3.6 (ML reconfiguration). Option-2 TGbe editor: Please add the following paragraphs as the new last two paragraphs in clause 35.3.24.3 (Broadcast TWT operation) (#15244) (#15244)
If an AP affiliated with an NSTR mobile AP MLD and operating on the primary link intends to advertise a broadcast TWT schedule for the AP affiliated with the same NSTR mobile AP MLD and
operating on the nonprimary link, then the AP operating on the primary link may advertise the schedule on the primary link and indicate that the schedule is an aligned schedule by setting the Aligned subfield of the Request Type field in the corresponding
Broadcast TWT Parameter set field to 1. NOTE 1--Since an NSTR mobile AP MLD can have a maximum of two links (the primary link and the nonprimary link), a non-AP MLD associated with the
NSTR mobile AP MLD that receives the advertisement of the aligned schedule, through Beacon and Probe Response frames transmitted on the primary link, can uniquely identify the presence of the aligned schedule on the nonprimary link.
(#15244)
A STA affiliated with a non-AP MLD associated with an NSTR mobile AP MLD that is operating on the nonprimary link, while sending a TWT request to the AP affiliated with the NSTR mobile
AP MLD and operating on the nonprimary link, for requesting membership of the aligned schedule on the nonprimary link, shall use the same Broadcast TWT ID that is used to identify the aligned schedule advertised on the primary link. *********************************
End of resolution for CID #15244*********************************** Best Rubayet From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Hello all, For the MAC ad-hoc meeting, hosted by Fraunhofer HHI, we will have a "registration fee" established, which will cover the catering expenses (breakfast, lunch, coffee, etc) during the 3 days. The catering company only accepts cash
so please make sure you have cash (local Euro currency) available. The current estimate is ~180 euros per person but to make sure we have the most up to date estimate please let Volker and me know
if there are any changes of in-person attendance by
Wednesday, July 5th, 10:00am (CEST, local time). PS: Latest version of the MAC ad-hoc agenda can be found
here (a revised version will be uploaded in the next 24 hours). Please let me know if you have any questions. Regards, Alfred "TGbe will hold a MAC ad-hoc meeting between 6th and 8th of July 2023, hosted by Fraunhofer HHI in Berlin, Germany. The MAC ad-hoc will be held at the location below: Fraunhofer Institute for Telecommunications,
Heinrich-Hertz-Institut, HHI Einsteinufer 37, 10587 Berlin, Germany Detailed agenda will be available prior to the meeting but generally the expectation is to have:
Where the sessions are expected to be: AM1: 09:00 – 10:30 AM2: 10:45 – 12:15 PM1: 13:30 – 15:30 PM2: 16:00 – 18:00 Web conferencing links ( WebEx) will be available for remote participation. In-person attendance of this meeting requires registration. To register please send an e-mail to Volker Jungnickel (volker.jungnickel at hhi.fraunhofer.de) and me
(asterjadhi at gmail.com) with the following subject: “TGbe Ad Hoc July Attendance Request”, and include in the e-mail body the details for each in-person
attendee (1. name, 2. company, 3. e-mail address, 4. vegetarian meal request). The deadline to send the registration e-mail is June 30th 2023. Also please let us
know if you need an additional letter of invitation for this event (i believe the letter of invitation for attending the upcoming IEEE802.11 plenary should suffice). Please use the following contacts for local and/or ad-hoc specific queries: Volker Jungnickel (volker.jungnickel at hhi.fraunhofer.de) and me (asterjadhi at gmail.com). Additional information on the meeting and location (such as hotel recommendations) are in preparation and will be sent as a follow up e-mail. And please feel free to contact me for any questions or issues you may have. Special thanks to Volker and Fraunhofer HHI for hosting the MAC ad-hoc meeting." -- Alfred Asterjadhi, PhD IEEE802.11 TGbe Chair, Qualcomm Technologies Inc. Cell #: +1 858 263 9445 Office #: +1 858 658 5302 To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 |