| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Will do. Best regards, Xiaofei Clement Wang Principal Engineer | InterDigital T: (631) 622.4028 From: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>
Hi Xiaofei,
From: ** STDS-802-11-TGbc -- Enhanced Broadcast Service ** <STDS-802-11-TGBC@xxxxxxxx>
On Behalf Of Xiaofei Wang WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi Abhi, Those suggestion sounds great. If there is no objections, I can incorporate those in the CR document. Since you proposed this text, I will add you as a co-author to the CR document if there is no objections. Best regards, Xiaofei Clement Wang Principal Engineer | InterDigital T: (631) 622.4028 From: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>
[Subject updated to reflect the correct CID - 1016] Hi Xiaofei, All, Subclause 11.55.2 covers the operations related to EBCS DL. I suggest adding a paragraph as shown below as the last paragraph under the General clause (11.55.2.1): [CID 1016]One or more EBCS traffic streams may be
available for an EBCS receiver to consume without requiring the receiver to explicitly request it from an EBCS AP. If an EBCS traffic stream requires explicit negotiation, the EBCS AP and EBCS receiver shall follow the procedures in 11.55.4.1 (EBCS Negotiation
Procedure for Associated STAs) or 11.55.4.2 (EBCS Negotiation Procedure for Unassociated STAs) to negotiate for EBCS traffic streams depending on the association state of the requesting EBCS receiver with the EBCS AP. The above paragraph is similar to the one from your document with a few changes. I replaced EBCS STA with EBCS receiver. This is based on a discussion we had earlier where an EBCS AP in the neighborhood may be a consumer of a traffic stream.
The term EBCS receiver will cover both AP and non-AP as a consumer. In addition, the change would make clause 11.55.2 to be consistent with several paragraphs in clause 12.13. Other changes based on discussion during Tuesday’s call. With the above addition to clause 11.55.2.1, we do not need to duplicate this text under the EBCS Negotiation Procedure clause. Instead we could directly jump to the two subclause on EBCS negotiation (one for associated case and the other
for unassociated). Furthermore, since EBCS negotiation applies only to EBCS DL procedure, the two subclause (currently 11.55.4.1 and 11.55.4.2 in your doc) need to be moved under 11.55.2. In the current spec, these appear after the EBCS UL procedure – which
is not the right location. These should come under 11.55.2. Same comment applies to 11.55.5 (EBCS Termination Notice Procedure). Please let me know your thoughts. Regards, From: ** STDS-802-11-TGbc -- Enhanced Broadcast Service ** <STDS-802-11-TGBC@xxxxxxxx>
On Behalf Of Xiaofei Wang WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Dear Abhi and all, Please let me know if you have any other suitable locations to add the sentence: One or more EBCS traffic streams may be available for an EBCS non-AP STA to consume without the EBCS STA explicitly requesting them from an EBCS AP. Best regards, Xiaofei Clement Wang Principal Engineer | InterDigital T: (631) 622.4028 E: Xiaofei.wang@xxxxxxxxxxxxxxxx To unsubscribe from the STDS-802-11-TGBC list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBC&A=1 To unsubscribe from the STDS-802-11-TGBC list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBC&A=1 To unsubscribe from the STDS-802-11-TGBC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBC&A=1 |