| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Solomon, I guess I didn’t make my points clear. Let me clarify the question: “The Allocation ID subfield shall be unique per the DMG Measurement setup ID”
could be interpreted as two distinct meanings:
BR, Chaoming 发件人: Solomon Trainin <strainin@xxxxxxxxxxxxxxxx>
Hi Chaoming, Thank you for the comment. Please note that “The Allocation ID subfield, when set to a nonzero value, identifies an airtime allocation from Source AID to Destination AID”. So, the rule “The Allocation ID subfield shall be unique per the DMG Measurement setup ID” is to use the airtime for one particular DMG Measurement setup ID. Even when different Source AID and Destination AID use the allocated airtime, it is still limited for one specific DMG Measurement setup ID. Best regards, Solomon Trainin +972547885738 From:
罗朝明(Chaoming Luo) <luochaoming@xxxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi Solomon, Thanks for the clarification! I understand your intention now. But still has a few comments for wording: “The Allocation ID subfield shall be unique per the DMG Measurement setup ID”
sounds confusing, since multiple STAs may receive same DMG MS ID. E.g., Could Allocation ID 1 be used for both STA 2 and 4 participating DMG MS ID 3? Or your text is indeed enforcing the use of same Allocation ID for multiple STAs participating in the same
DMG MS? Note that in baseline we have “Except for CBAP allocations with broadcast Source AID and broadcast Destination AID, the
tuple (Source AID, Destination AID, Allocation ID) uniquely identifies the allocation”, which means Allocation ID singly does not identify an allocation. BR, Chaoming 发件人: Solomon Trainin <strainin@xxxxxxxxxxxxxxxx>
Hello Chaoming, You noted that the SP allocation shall contain the DMG Measurement setup ID. There is no such need. Destination AID indicates the responder participating in the SP. From the extended schedule element, the responder knows that it participates in the SP at the specified time, and the instance information is delivered
in the DMG Sensing Request frame, just as it is in the case of CBAP. Best regards, Solomon Trainin +972547885738 OPPO 本电子邮件及其附件含有OPPO公司的保密信息，仅限于邮件指明的收件人使用（包含个人及群组）。禁止任何人在未经授权的情况下以任何形式使用。如果您错收了本邮件，请立即以电子邮件通知发件人并删除本邮件及其附件。 This e-mail and its attachments contain confidential information from OPPO, which is intended only for the person or entity whose address is
listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please
notify the sender by phone or email immediately and delete it! To unsubscribe from the STDS-802-11-TGBF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBF&A=1 |