| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
John Thanks for the forwarding. I was not involved as I didn’t subscribe to 100G optx mailing list. Pete’s equation, BER=FER*8/5280, is
basically correct. But not truly. The reality is more complicated as we consider
error propagation or burst errors. e.g., if we assume P(error propag.)=0.4, then we can calculate average error burst length. In brief, when we have an error event, on the average, we actually have multiple bits errors. e.g., assume we have average of 2.5 bits errors when we have a RS symbol error,
then error ratio conversion equation is BER=FER*8*2.5/5280. The next question is what’s the right value for us to assume about
error propagation probability. Finally we will find out using FER as target is different from using BER. Thanks. --- Zhongfeng
From: John_DAmbrosia@xxxxxxxx [mailto:John_DAmbrosia@xxxxxxxx]
All, There is a lengthy thread going on the 802.3bm reflector – and I want to make sure everyone in our Task Force is aware of it. Regards, JOhn From: Mike Dudek
[mailto:mike.dudek@xxxxxxxxxx]
I’ve added some folk from the .bj task force FEC ad-hoc to this thread and changed the title. As stated in a separate e-mail I think that it would be good
if 802.3bj and 802.3bm came to a common understanding of the error ratio requirements. First I’m wondering whether we may be having some confusion between FEC frames and Ethernet Packets (aka frames). The 802.3bj has created a requirement (in draft 1.2)
that is stated in terms of frame error rate, but in context I think it means packet error rate, and I think that may be the most meaningful for a system. Obviously if it is the Packet Error Rate that really matters to the system then we also have to consider
how shorter packets get distributed within FEC frames, (or FEC frames are distributed in long packets). I think the thread below is talking about the FEC frame error rate which I think would be just an intermediate calculation point.
Mike Dudek
QLogic Corporation Senior Manager Signal Integrity 26650 Aliso Viejo Parkway Aliso Viejo CA 92656 949 389 6269 - office. From: Anslow, Peter
[mailto:panslow@xxxxxxxxx] John, a) No, I wouldn’t. The probability of a frame containing 5280 bits having one or more errors in it is one minus the probability that all of the
bits are correct. The probability that they are all correct is the probability that any one bit is correct raised to the power of the number of bits in the frame. Hence the formula. If the BER is low, then this is dominated by the case where there is only
one error per frame and it evaluates to be very close to 1E-12 * 5280 = 5.28E-9. When the BER becomes lower, say 1E-5, the effect of more than one error starts to be seen and it evaluates to 5.14E-2 rather than 5.28E-2. b) A very simple minded analysis might say that the process in a) can be reversed by taking the Frame Error Ratio (FER) and applying the formula: BER = 1-(1-FER)^(1/5280) which evaluates to 1E-12 for FER = 5.28E-9 and is approximately FER/5280 unless the BER is high. However, this conversion
assumes that the errored frames have random errors (since it is the reversal of the calculation in a). However, as you point out, the effect of FEC is to remove the errors from all frames with 7 or less symbol errors. This means that any frame that contains
an error contains at least 8 errors. (8 is actually the dominant case, 9 errors in a frame is much less probable). Consequently, the formula to go from the FER to the
BER is approximately BER = FER*8/5280. Hope that makes my meaning clear, Pete Anslow |
Senior Standards Advisor From: John Petrilla [mailto:john.petrilla@xxxxxxxxxxxxx]
Hello Pete Thanks a) Regarding item 6) below, why would you not use binomial statistics? b) Further down, you write, “Because the errors with FEC
occur in groups of 8 or more per FEC frame, the BER in this case will be at least 8E-12.” I’m not sure what you mean. Could you clarify? Regards, John From: Anslow, Peter [mailto:panslow@xxxxxxxxx]
John, Your proposal with changes / comments in red. 1) For the 100 m MMF objective, definition will be based on the assumption that RS-FEC, RS(528, 514), defined in Clause 91 for 100GBASE-CR4 or
100GBASE-KR4 (hereinafter referred to as KR4 FEC) is available. 2) All of the error correction capability of KR4 FEC is allocated to the link supporting the 100 m MMF objective. 3) The incoming BER for the MMF PMD
(including any errors generated by CAUI-4 if present)
will be equal to or better than 10^-12 and the target corrected BER for the link output will be equal to or better than 10^-12. 4) KR4 FEC uses 528 symbols of 10 bits/symbol yielding a frame size of 5280 bits.
5) There are 514 data symbols and 14 parity symbols providing the ability to correct (528-514)/2 = 7 corrupted symbols.
6) The Frame Error
Ratio, FER, for operation without FEC for a BER = 1E-12 using
P_frame_error = 1-(1-P_bit_error)^5280 is 5.28E-9.
7) In a optical link, assume bit errors are noise generated, independent and random. Further, since there will be no DFEs, error multiplication
is not expected before the descrambler.
8) The worst case that can be corrected is
7 10-bit symbols in error.
Now, I get stuck because I think we need to agree on what the error criterion at the FEC output is. I think that John has assumed that the FEC Frame error ratio (FER) is 5.28E-9 i.e. the same FER as you would get if you had randomly distributed
errors and a BER of 1E-12 or in other words, the same FER as you would expect if you were operating without FEC. Because the errors with FEC occur in groups of 8 or more per FEC frame, the BER in this case will be at least 8E-12. Before going further and calculating what input BER corresponds to a FEC FER of 5.28E-9, I think we need to get agreement that this is the criterion
that we are going to use as it is not strictly in agreement with the objective: “Support a BER better than or equal to 10-12 at the MAC/PLS service interface” Regards, Pete Anslow |
Senior Standards Advisor From: John Petrilla [mailto:john.petrilla@xxxxxxxxxxxxx]
Hello Jonathan Thanks for proposing the meeting and especially for the 8:30 AM Pacific start time. Perhaps we can make some progress on FEC details prior to the meeting. Along that line I’ll propose the following strawman, so that we may have common values
to use for Q and BER in our various analyses. 1) For the 100 m MMF objective, definition will be based on the assumption that RS-FEC, RS(528, 514), defined in Clause 91 for 100GBASE-CR4
or 100GBASE-KR4 (hereinafter referred to as KR4 FEC) is available. 2) All of the error correction capability of KR4 FEC is allocated to the link supporting the 100 m MMF objective. 3) The incoming BER for the MMF PMD will be equal to or better than 10^-12 and the target corrected BER for the link output will
be equal to or better than 10^-12. 4) KR4 FEC uses 528 symbols of 10 bits/symbol yielding a frame size of 5280 bits.
5) There are 514 data symbols and 14 parity symbols providing the ability to correct (528-514)/2 = 7 corrupted symbols.
6) The Frame Error Rate, FER, for operation without FEC for a BER = 1E-12 using binomial statistics (probability density function)
is 5.30E-9. 7) In a optical link, assume bit errors are noise generated, independent and random. Further, since there will be no DFEs, error
multiplication is not expected. 8) The worst case that can be corrected is 7 bit errors for 7 symbols with 1 bit error/symbol.
9) The case equivalent to operation without KR4 FEC is where 8 symbols are corrupted, since for only 7, all errors are corrected.
10) For operation with KR4 FEC, a BER = 6.90E-5 yields an FER of 5.30E-9 (Qi = 3.8119) to match the FER for a BER = 1E-12 (Q = 7.034)
without FEC and 10Log(Qo/Qi) = 2.66 dB. 11) The link model supporting the 100 m MMF objective will use a value of 3.8119 for Q. If there are objection or counter proposals, let’s try to resolve them before the ad hoc meeting. Regards, John From: Jonathan King [mailto:jonathan.king@xxxxxxxxxxx]
Dear all, I’d like to propose
we meet for an MMF Ad Hoc conference call (via Webex) on
29th November, 8.30am Pacific Standard time (4.30pm GMT) . Call duration will be up to 1.5 hours, but can end earlier if meaningful discussion ends. If there aren’t too many objections I’ll confirm the date/time in a couple of days, and send out call details. Our main goal is to progress development of baseline proposals for the 100m reach and 20m reach MMF objectives,
and hopefully
remove a few more TBDs from the proposed Tx and Rx spec tables. Please send presentation requests to me by close of business on
28th November- (I’ll send out the agenda that day). Best wishes jonathan |