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

Re: [STDS-802-11-TGBE] Reminder-Action Required: Ramping Up LB275 comment resolutions

Hi Vishnu,

On 2, the spec says that a bit is set to 1 when the corresponding link is recommended. So if there is no recommendation, all bits are set to 0. It seems to be clear.

Regards,
Minyoung

On Fri, Nov 10, 2023 at 9:04 AM Vishnu Ratnam <vishnu.r@xxxxxxxxxxx> wrote:

Hi Minyoung,

 

As discussed offline, I do not agree with the resolution of the below CID 19851. I am suggesting the below a resolution for the consideration of the group.

 

Regards,

Vishnu

 

19851

Vishnu Ratnam

35.3.12.4

543.46

A mechanism should be provided in the traffic indication procedure, for an AP affiliated with an AP MLD to recommend one or more non-AP MLD(s) with default TTLM to wake up STAs operating on all links to receive BUs when the traffic buffer at AP MLD is large.

When a non-AP MLD that is in the default mapping mode detects that the bit corresponding to its AID is equal to 1 in the TIM element and the Multi-Link Traffic Indication element is present in a Beacon frame and the Multi-Link Traffic Indication element includes a Per-Link Traffic Indication Bitmap n subfield that corresponds to the non-AP MLD, the non-AP MLD shall operate as follows: (i) if all bits of the Per-Link Traffic Indication Bitmap n subfield are set to 0, all non-AP STAs affiliated with the non-AP MLD should issue a PS-Poll frame, or a U-APSD trigger frame if the STA is using U-APSD and all ACs are delivery enabled, to retrieve buffered BU(s) from the AP MLD. (ii) if not all bits of the Per-Link Traffic Indication Bitmap n subfield are set to 0, any non-AP STA affiliated with the non-AP MLD that operates on the link(s) indicated as 1 in the Per-Link Traffic Indication Bitmap n subfield may issue a PS-Poll frame, or a U-APSD trigger frame if the STA is using U-APSD and all ACs are delivery enabled, to retrieve buffered BU(s) from the AP MLD.

 

Discussion:

The CID (and proposed resolution) identify two issues:

  1. A mechanism for recommending multiple STAs of a non-AP MLD with default TTLM mapping to wake up to receive BUs is missing.
  2. It is unclear if an AP MLD can set all the bits of a Per Link Traffic Indication Bitmap subfield of an MLTI element for an AID to 0. It is also unclear how a non-AP MLD interprets such an indication.

I am fine with rejecting point 1 above due to lack of consensus, but we still need a resolution to point 2. The spec also does not clarify the indication used by the AP MLD in the Per-Link Traffic Indication Bitmap if it doesn’t have a link recommendation for a non-AP MLD.

 

Suggested change:

 

Add the following text to clause 35.3.12.4:

 

All bits of a Per-Link Traffic Indication Bitmap n subfield of an Multi-Link Traffic Indication element corresponding to either a non-MLD non-AP STA or a non-AP MLD in default mapping mode for which the AP MLD does not intend to provide a link recommendation, shall be set to 0.

 

When a non-AP MLD that is in the default mapping mode (see 35.3.7.2.2 (Default mapping mode)) detects that the bit corresponding to its AID is equal to 1 in the TIM element and the Multi-Link Traffic Indication element is not present in a Beacon frame or the Multi-Link Traffic Indication element is present in a Beacon frame but the Multi-Link Traffic Indication element does not include a Per-Link Traffic Indication Bitmap n subfield that corresponds to the non-AP MLD or the Multi-Link Traffic Indication element is present in a Beacon frame and Multi-Link Traffic Indication element includes a Per-Link Traffic Indication Bitmap n subfield that corresponds to the non-AP MLD with all bits set to 0, any non-AP STA affiliated with the non-AP MLD may issue a PS-Poll frame, or a U-APSD trigger frame if the STA is using U-APSD and all ACs are delivery enabled, to retrieve buffered BU(s) from the AP MLD.

 

 

From: Minyoung Park <mpark.ieee@xxxxxxxxx>
Sent: Tuesday, October 17, 2023 1:01 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] Reminder-Action Required: Ramping Up LB275 comment resolutions

 

Caution: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

 

Hi Alfred,

 

I'll prepare resolutions for the following unresolved CIDs:

CIDs: 19127, 19213, 19473, 19475, 19584, 19851

in the following CR doc:

11-23-1803-00-00be LB275 CR Misc.

 

Please schedule this for Nov 2nd. MAC call.

 

Regards,

Minyoung

 

On Mon, Oct 16, 2023 at 8:55 AM Alfred Asterjadhi <asterjadhi@xxxxxxxxx> wrote:

Please consider this as a gentle reminder for the action items below.

 

Regards,


AA

 

On Tue, Oct 10, 2023 at 12:34 PM Alfred Asterjadhi <asterjadhi@xxxxxxxxx> wrote:

Hello all,

 

We are targeting to complete the comment resolution for LB275 by November F2F. In order to ensure that all comments are resolved and that we avoid concentration of resolutions during the last sessions I would like to request the POCs to respond to the following:

  1. Call for assignees to ramp up LB275 comment resolutions:
    • If you are an assignee (POC) who has not resolved all of the comments assigned to you then please:
      1. Prepare and upload CRs that resolve all of the CIDs that are assigned to you by EOB of October 17th 2023 or
      2. Obtain a DCN for your planned CRs, provide the list of CIDs that each CR will resolve, and send a request (also to be sent by EOB of October 17th) for agenda time (include in the e-mail the earliest day the doc will be ready as well) or
      3. Coordinate with TGbe officers and TTT members to re-assign some CIDs to (TTT) members by that same deadline (EOB of October 17th).
    • After the deadline has passed, the TGbe officers will initiate the redistribution of any of the CIDs that do not have a corresponding CR document to other assignees.
  1. Call for assignees (POCs) to check on “comments presented and no consensus yet” in 11-23/1375r9
    • There are currently 125 CIDs in this category (based on 1375r9).
    • CIDs in that list, for which there has been no request for SP within two weeks after the presentation, have ended in quarantine.
    • SPs for quarantined CIDs (refer to Item 11 of the guidelines) are expected to be run during the Nov 1st Joint conf call
      • SP for quarantined CIDs: "The chair is expected to run a SP on a resolution for that CID (proposed resolution by member/no consensus resolution)."

Thanks to all the members for all the work done so far and please feel free to let me know if you have any questions. 

 

Regards,

 

Alfred

--

Alfred Asterjadhi, PhD

IEEE802.11 TGbe Chair,

Qualcomm Technologies Inc.

Cell #:    +1 858 263 9445

Office #: +1 858 658 5302


 

--

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