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

Re: [STDS-802-11-TGBE] TGbe Teleconferences [01/05/2022, and 01/06/2022]: Agendas Posted

Hello Vishnu,

The text is stating that a STA affiliated with a non-AP MLD is considered to have lost medium sync on a link on which it is operating when it cannot perform CCA on that link. For the EMLSR operation, there are two cases identified: 
(1) when a STA affiliated with the non-AP MLD on the other EMLSR links is exchanging frames with an AP affiliated with an AP MLD  
(2) when the non-AP MLD decided to use one of the EMLSR links to receive a group addressed frame but haven't received one yet.

In the text, (1) is covered by 
"during frame exchanges between an AP affiliated with an AP MLD and one of the other STAs operating on the other EMLSR links, which are affiliated with the same non-AP MLD"
and (2) is covered by
"while not transmitting nor receiving on that same link"

I believe covering the two cases gives more clarity in the spec.

Regards,
Minyoung

On Fri, Feb 4, 2022 at 8:19 AM Vishnu Ratnam <vishnu.r@xxxxxxxxxxx> wrote:

Hi Minyoung,

 

Thank you for the response. I am not quite sure I completely follow the argument. The text “is considered to have lost medium synchronization if it is not able to perform CCA on that link while it is neither transmitting nor receiving on that link” indicates that situations when the STA is either transmitting or receiving on that link are excluded from consideration of loss of medium synch. So the situation you mention will not happen I think.


Also doesn’t “while not transmitting or receiving on that same link” already include “during frame exchanges between an AP affiliated with an AP MLD and one of the other STAs” ? So since it is an “either/or” statement, the additional second part of the statement is unnecessary probably?

 

Regards,

Vishnu

 

From: Minyoung Park <mpark.ieee@xxxxxxxxx>
Sent: Wednesday, February 2, 2022 12:15 PM
To: Vishnu Vardhan Ratnam <vishnu.r@xxxxxxxxxxx>
Cc: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] TGbe Teleconferences [01/05/2022, and 01/06/2022]: Agendas Posted

 

Hello Vishnu,

 

Sorry, I may have missed your email. 

The two cases cover the main reasons why a STA on one of the EMLSR links loses medium sync and gives more clarification to readers. If we remove the second case (Tx/Rx on the other links) and leave it as a generic statement then it can be interpreted as if a STA loses medium sync even during the listening operation on that link, which is not correct.

 

Regards,

Minyoung  

 

 

On Tue, Feb 1, 2022 at 8:41 PM Vishnu Ratnam <vishnu.r@xxxxxxxxxxx> wrote:

Hi Minyoung,

 

Thank you for your CR 1484r2 but I have one question regarding it. I am not sure if you received my email comments regarding 1484r1 so I am responding here. Why not be generic and just say: “is considered to have lost medium synchronization if it is not able to perform CCA on that link while it is neither transmitting nor receiving on that link”. Is there a need to specify reasons for not being able to perform CCA (e.g. TX/RX on other links etc.)? The reason list might keep growing if people come up with other corner cases.
In fact, the current text seems to restrict under which cases a loss of CCA ability counts as loss of medium synchronization. Shouldn’t it apply for any situation of CCA loss (unless the particular STA is itself transmitting or receiving on that link)?

 

Regards,

Vishnu

 

 

From: Minyoung Park <mpark.ieee@xxxxxxxxx>
Sent: Tuesday, February 1, 2022 4:24 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] TGbe Teleconferences [01/05/2022, and 01/06/2022]: Agendas Posted

 

Hi Alfred,

 

Please add the following two SPs for the MAC call:

  • 11-21/1483r3 CC36 CR CID 7888
  • 11-21/1484r2 CC36 CR EMLSR medium sync

I updated the documents based on the discussion during the last MAC call and offline discussions.

 

Regards,

Minyoung

 

On Tue, Jan 4, 2022 at 1:30 PM Alfred Asterjadhi <asterjadhi@xxxxxxxxx> wrote:

Hello all,

 

First of all I would like to wish everybody a Happy New Year!

 

I uploaded an updated version of the agendas, which contains the agenda for the next conference calls, scheduled on Wednesday January 05 (JOINT), 10:00-12:00 ET and Thursday January 06 (MAC), 10:00-12:00 ET. 

 

The agendas can be found here:

https://mentor.ieee.org/802.11/dcn/21/11-21-1775-18-00be-nov-jan-tgbe-teleconference-agenda.docx

 

Note for CR documents: Please update the baseline to TGbe D1.31 for the CR documents.

 

DIAL IN DETAILS FOR WEDNESDAY:

Join the JOINT meeting here: https://ieeesa.webex.com/ieeesa/j.php?MTID=m47e46089d108a8ef448b7a3a11976593

Meeting number: 233 886 75218 Meeting password: wireless (94735377 from phones and video systems)

 

DIAL IN DETAILS FOR THURSDAY:

Join the MAC meeting here: https://ieeesa.webex.com/ieeesa/j.php?MTID=mff9e3bd94518bedcc608845d389fdd3e

Meeting number: 234 227 52561 Meeting password: wireless (94735377 from phones and video systems)

 

Let me know if you have any questions and/or suggestions.

 

Best Regards,

 

Alfred

 

--

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

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