| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Dear Nancy, thanks for the brilliant analysis. To be honest, the whole channelization and operating classes are still quite confusing for me and I am too short in my time currently to work into that topic as
thoroughly as needed. There is one more risk I wanted to discuss. Given that the chip (with baseband and RF included) decides to work, say, somewhere in the 5 GHz band, at the output we need to scan the whole band and
identify the most suitable downconversion frequency to reach the right IF center frequency that is used over the LC channel. That should happen in the few µs at the beginning of every packet, for all the three bands in parallel, right.
Without any logical information coming out of the chip I expect this is hardly impossible. That all would open the question again that we need access to the baseband-RF interface inside the chip
where such information is of course available. If chipset vendors are not willing to open that interface, the TGbb standard could not be implemented. I would be interested to understand the positions of the proposers on the scanning issue.
Best regards - Volker
Von: Nancy Lee [mailto:nancy.lee@signify.com]
Hi Volker, The figures from Chong show the tx and rx chains for an implementation using existing 802.11 chipsets that have integrated RF components. Admittedly this is an inefficient and bulky implementation, but it has the major
advantage that it can be realized today with commercially available chipsets. The figures you provide are a nice improvement of D0.6 Figure 1, showing a (future) baseband implementation, i.e. using chipsets that do not contain RF components. I see two choices for TGbb:
For choice 2, we further need to deal with the question of whether those chipsets are configured for 2.4 GHz, 5 GHz, or 6 GHz operation, When discussing with Dorothy last week, we determined that it is not possible for
an implementation configured for one band (e.g., 2.4 GHz) to interoperate with an implementation configured for a different band (e.g., 6 GHz), because we know the channelization and operating classes for the different bands are not interoperable. I see the
following options:
Regards, -Nancy From: ** STDS-802-11-TGbb -- Light Communication Task Group** <STDS-802-11-TGBB@xxxxxxxxxxxxxxxxx>
On Behalf Of Jungnickel, Volker
Dear Chong, Nancy, I have had a different understanding of the second graph. What I suggested as a baseband implementation, besides the bulky down-conversion graph, is enclosed. I have removed the radio-specific parts and the bias addition point before the OFE because this is different at least in HHI OFEs which are always AC coupled. The bias settings are
not usually accessible. I have left the DC block in in case some alien OFEs would outputs any spurious DC signals. In my personal opinion, one could leave the bias and DC block out of the entire chain. The RF folks will ask us as experts anyway in case they
want to use an OFE. It should always be AC-coupled, both ways. Please let me know if the enclosed figure is fine with you. Best regards - Volker Von: ** STDS-802-11-TGbb -- Light Communication Task Group** <STDS-802-11-TGBB@xxxxxxxxxxxxxxxxx>
im Auftrag von Chong Han <chong.han@xxxxxxxxxxxx> Dear all, The document is updated to version 3 with the figure changed. The current figure contains both the modifications for LC and the original figure from Fig. 17-12.
Link: https://mentor.ieee.org/802.11/dcn/21/11-21-1688-03-00bb-proposed-changes-for-tgbb-draft-0-6.docx Regards, Chong From: ** STDS-802-11-TGbb -- Light Communication Task Group** <STDS-802-11-TGBB@xxxxxxxxxxxxxxxxx>
On Behalf Of Chong Han CAUTION:
This email originated from outside of pureLiFi. Do not click links or open attachments unless you recognize the sender and know for certain that the content is safe. Dear all, I’ve uploaded the doc. 11-21/1688r2 which has the updated 40 MHz channel in the 2.4 GHz band mapping, the Figure 1 and its description, and the subclauses moved to the general PHY section.
The link is here: https://mentor.ieee.org/802.11/dcn/21/11-21-1688-02-00bb-proposed-changes-for-tgbb-draft-0-6.docx Regards, Chong To unsubscribe from the STDS-802-11-TGBB list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBB&A=1
To unsubscribe from the STDS-802-11-TGBB list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBB&A=1
To unsubscribe from the STDS-802-11-TGBB list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBB&A=1
The information contained in this email may be confidential and/or legally protected under applicable law. The message is intended solely for
the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this email is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender
by return e-mail and destroy all copies of the original email. To unsubscribe from the STDS-802-11-TGBB list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBB&A=1 |