Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Roberto, Thanks a lot for your responses to my questions. I will need some time to digest. I would also expect this to be food for further questions and discussions. Kind regards, Peter From: Roberto Rodes [mailto:roberto.rodes@xxxxxxxxxxxx]
Hi Peter, I just realized my emails to the reflector have been getting rejected after my company II-VI rebranded as Coherent. I wrote (or tried) to the reflector last week asking for
few days to get back to you. Sorry about that. Thank you for your questions. There are a lot of questions indeed, but they are all fair. Some of them will deserve a future contribution and discussion, but for now, please
read below our responses. Your questions are in black, our replies in red: The first question which I raised was related to the range between OMAouter min (for max TDECQ), being 4.4 dBm, and OMAouter max, being 5 dBm, and how that would work in
manufacturing, considering that during the cu project there were requests to raise that difference for the 400GBASE-LR4-6 from 2.1 to 2.5 dB.
It was my understanding that you acknowledged that this range was tighter than desirable and that it would need to be considered if it would be possible to raise the OMAouter
max to 5.5 dBm. Correct, and what I tried to say during the meeting is that the increase in OMAouter max does not necessarily require an increase on AOPmax. We will bring a contribution
on this. For instance, on 400G-DR4, OMAouter max is higher than AOPmax. This however raises further questions:
We think 1.1-1.3dB is a reasonable OMA range @ TDECQmax considering that 800G-LR4 is based on LAN-WDM with cooled lasers. For reference,
400G-LR4 has 1.6dB OMA range@TDECQmax. EMLs and MZMs can use laser current as a nob to tune OMA while maintaining modulator condition. This was harder on traditional DMLs.
Yes, a nominal Tx power of 5 dBm (OMAouter) is achievable with current 200G PAM4 laser technology. We will bring some contribution on this in the future. For reference, EML for 802.3cn 200G-ER4 has an OMAouter
range of 3.4 to 7.4dBm, 400G-ER8 has a range of 2.4 to 6.4 dBm, and 100G Lambda MSA’s 100G-ER1-40 has a range of 4.7 to 7.9dBm.
While we do not have overload data on 200G/lane TIAs yet, we expect no overload issue with 5.5dBm based on 100G/lane receivers. Receiver power is at TP3, before DMUX. For reference, 100G-LR1-20 specifies +6.6dBm
AOP max for PIN-based receivers.
The impact of 0.5dB higher OMA while maintaining AOPmax is modest, and it will be further quantified by using updated parameters later. One intermediate question is related to the proposal for “Difference in launch power between any two lanes” to be “3 dB” max. Is this average launch power or OMA? In the in-force specifications for 400GBASE-FR4 and 400GBASE-LR4-6 it is in OMA. Per IEEE methodology, this delta is based on OMA. We will be more explicit on future contributions Now back to my second question raised at last week’s meeting. In your specification proposal on slide 6, you propose a max difference in launch power between any two lanes of 3 dB. Shouldn’t we take that range into consideration for the analysis of FWM? Yes, our simulations (used in rodes_3df_01a_2211) take into consideration of the power delta between lanes with a statistical approach. The margin on power in slide#5
is large, even a 3dB higher FWM crosstalk ( for a 3dB lower power victim lane) would still be negligible. In October there was a presentation by your co-author Xiang Liu proposing to use a flat distribution of power per channel, whereas his first (and superseded) presentation
assumed a range of 3 dB. Wouldn’t we need to use that range of 3 dB for the FWM analysis? Yes, we need to consider the “worst-case max difference in launch power”, and do so with a statistical approach because such worst cases only occur with a small probability.
This has been done in our contribution rodes_3df_01a_2211. I have run wider Tx OMA distributions with no significant change in results. We could add results into a later presentation. Now, having been able to further look into the proposals in your updated presentation, I have some further questions for clarification, especially around the assessment of
FWM penalty.
Slide#5 on rodes_3df_01a_2211 uses a combination of 3 gaussian distributions, the same as the distributions show in in the
October presentation (rodes_3df_01b_221012 slide#8) There is no clipping or truncating of the combined distribution at 1306 or 1322nm. We are truncating the distribution between
1300nm and 1324nm. We did not include a flat distribution in our November contributions because it is a misrepresentation of the fiber distributions
(as discussed during our October contribution) resulting on misleading probability results of the MonteCarlo Analysis.
As proposed by Chris Cole in cole_3df_01a_2211, it will be beneficial for IEEE 802.3df and 802.3dj to “explore adoption of the following example ZDW (Zero Dispersion Wavelength) limits for use in calculating
penalties for all SMF PMDs (Physical Medium Dependents), ZDWmin = 1306nm and ZDWmax = 1322nm” in the Nov. Plenary meeting, and “explore use of (realistic) ZDW distribution in statistical link performance analysis”, as done in rodes_3df_01a_2211.
As you know, these engineering specs have generated sufficient interest in our Task Force, and are pending further discussion and agreement by our Task Force members. We can help on further analyze different limits to evaluate when/where we are close to running off a cliff
Lambda0 combines 3 gaussian distributions, basically splittin the number of iterations of the MC analysis based on market share for 3 manufacturers and each manufacturer distribution is gaussian. The combined
distribution is not exactly gaussian, but a ‘Gaussian Mixture’ distribution Average Optical Powers have gaussian distributions for each lane
No, the AOP has Gaussian distribution with std =0.5dB, but we are not setting a range for the OMA. OMA is the result of the AOP and ER tunability range. The OMA distribution tents to be narrower because each
module would adjust the ER (within certain range) based on AOP to meet certain OMA target. Then on the combined TDECQ + FWM penalty.
Yes, we expect that the combined TDECQ + FWM penalty never goes above 3.9 dB under the outage probability to be specified.
Yes, when a channel is facing large dispersion (positive or negative), the FWM will be negligible
Slide#9 on rodes_3df_01b_221012 shows the relation of lambda zero with dispersion and FWM. The FWM penalty will be negligible for each channel outside certain lambda0 range. The dotted sections of the lines in the graph below represent
the ranges of lambda0 with negligible FWM. In general, FWM starts to be a possibility with fiber lambda0 ~1305nm or lower. You can see how at 9.5ps/nm and -28.4ps/nm you only need to worry about CD, and not about FWM.
I am sorry for the many questions raised in this email but I think it’s important to get clear answers in our attempt to create a robust and manufacturable 800G-LR4 specification
and to remove any shred of doubt. Thank you Peter for all these relevant questions. They are very important to build a robust spec. We hope we have satisfactorily answered all of them, and we will
continue working with all Task Force members to refine the 800G-LR4 IMDD specifications together. We understand that we still have plenty of work ahead. Regards, Roberto From: Peter Stassar <000017da312dfb6f-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi Chris, Thanks. Looking forward to the further information. Happy Thanksgiving to you, our colleagues and their families. Kind regards, Peter From: Chris Cole [mailto:chris@xxxxxxxxxxxxxxx]
Hello Peter,
Happy Thanksgiving everyone
On Tue, Nov 22, 2022 at 6:43 AM Peter Stassar <000017da312dfb6f-dmarc-request@xxxxxxxxxxxxxxxxx> wrote:
To unsubscribe from the STDS-802-3-B400G list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G&A=1 [listserv.ieee.org]
To unsubscribe from the STDS-802-3-B400G list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G&A=1 To unsubscribe from the STDS-802-3-B400G list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G&A=1 To unsubscribe from the STDS-802-3-B400G list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G&A=1 |