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

Re: [STDS-802-11-TGBE] TGbe Teleconference [08/29/2019]: Reminder

Hi Abhi,


Thank you for the good questions.


For question#1, I do not have the answer for the first two sub questions right now. We assume these parameters will be available finally. As the timing requirement, if it is also provided by upper layer, I assume they can have a latency budget analysis or planning to assign the proper timing requirement to 802.11 MAC. As the duplication threshold, I think it can be an internal parameter and its value might be variable depends on the implementation.


For question#2, you are right that the AP by default will not know the status of STA-B. We do not have very good solution right now but the following two examples can be considered:

1.      AP frequently send the trigger frame for UORA and STA-B send its request to indicate the RTA duplication state using UORA

2.      If control channel is available, STA-B can send the RTA duplication state notification to AP via control channel


Best Regards,


Alan Jauh

From: Abhishek Patil [mailto:appatil@xxxxxxxxxxxxxxxx]
Sent: Friday, August 30, 2019 3:04 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] TGbe Teleconference [08/29/2019]: Reminder


Hi Alan,


Thank you for you presentation in doc 11-19/1101r1 (Conditional packet duplication in multi-link systems).


I have a few questions:

  1. How does the MAC layer identify an RTA frame? Where is this information carried? Also, how does the upper layer provide timing requirements and duplication threshold for an RTA frame to the MAC layer?
  2. On slide #8, you propose that an AP could take over the TXOP ownership from one STA (STA-A) and pass it to another STA (STA-B) that is in RTA duplication state. How would the AP have knowledge of a STA’s local queue information – i.e., how does an AP know that a certain RTA packet queue on STA-B has reached the duplication threshold?






From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Sent: Wednesday, August 28, 2019 1:14 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBE] TGbe Teleconference [08/29/2019]: Reminder


CAUTION: This email originated from outside of the organization.

Hello all, 


This is a reminder that we have the fifth conference call of the series scheduled for tomorrow Thursday (August 29th) between 19:30 - 22:00 ET.


The teleconferences agenda is posted below:


Below is a list of the contributions that are expected to be presented (in green) and contributions that are in the back up queue (in yellow), i.e., that may be discussed if there is time.

If your name appears in the list please make sure to attend the meeting and that your contribution is uploaded to the IEEE mentor server. If you cannot attend the conf call please send a notification prior to the conference call. 

In addition, please note that for each contribution i have noted the number of SPs I found (or was notified) for each document. 

If you do plan to run a SP please send a notification asap so that we can plan accordingly (need to setup an e-poll etc, details to follow in a separate e-mail if necessary).

·1085r0–High Level EHT Preamble Structure            (Rui Cao)

·0951r0–Discussion on Multi-band/channel Access Method  (Liuming Lu)

·1081r0–Multi-Link Aggregation - Gain Analysis (Latency) (Abhishek Patil)

·1095r0–Multi-link requirement discussion (Yonggang Fang)

·1100r1–Per Packet Multiple Link Selection (Alan Jauh)

·1101r1–Conditional Packet Dup. in Multiple Link System (Alan Jauh)

·1116r0–Channel access in multi-band operation (Yunbo Li)

·1128r0–Multi-link transmission (Rojan Chitrakar)

·1144r0–Channel Access for Multi-link Operation (Insun Jang)

·1159r0–Multilink operation capability announcement (Liwen Chu)


Teleconferences are bound by the conditions stipulated by the documentation below. Please review them and bring up any questions/concerns you may have before proceeding with the teleconference


IEEE Patent Policy -

Patent FAQ -
LoA Form -
Affiliation FAQ -
Anti-Trust FAQ -
Ethics -
IEEE 802.11 Working Group Operations’ Manual –



To join the meeting:

Conference ID: 808-571-868


Best Regards,


To unsubscribe from the STDS-802-11-TGBE list, click the following link:

To unsubscribe from the STDS-802-11-TGBE list, click the following link:

This email (including its attachments) is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. Unauthorized use, dissemination, distribution or copying of this email or the information herein or taking any action in reliance on the contents of this email or the information herein, by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is strictly prohibited. If you are not the intended recipient, please do not read, copy, use or disclose any part of this e-mail to others. Please notify the sender immediately and permanently delete this e-mail and any attachments if you received it in error. Internet communications cannot be guaranteed to be timely, secure, error-free or virus-free. The sender does not accept liability for any errors or omissions.
本邮件及其附件具有保密性质,受法律保护不得泄露,仅发送给本邮件所指特定收件人。严禁非经授权使用、宣传、发布或复制本邮件或其内容。若非该特定收件人,请勿阅读、复制、 使用或披露本邮件的任何内容。若误收本邮件,请从系统中永久性删除本邮件及所有附件,并以回复邮件的方式即刻告知发件人。无法保证互联网通信及时、安全、无误或防毒。发件人对任何错漏均不承担责任。

To unsubscribe from the STDS-802-11-TGBE list, click the following link: