Last modified on 5 April 2013, at 13:55

Clock and Data Recovery/Buffer Memory (Elastic Buffer)/Cascades of Buffers and CDRs, delays and tolerance

TRANSIT DELAY inside the elastic bufferEdit

The elastic buffer essential function is to add a delay to the information stream that, added to the jittered delay in the incoming stream, makes the total delay a fixed amount:

  • first the additional delay is calculated
  • and then it is added.

In general, the total delay is referred to a clock (the read clock) that is not necessarily synchronous with the incoming information stream. An example of elastic buffer is shown in the following figure:

Example of elastic buffer.png

An example of elastic buffer, made with a shift register and a multiplexer. The read operation is made sampling the output of the register stage chosen by the read multiplexer.

The multiplexer is driven by the up and down counting of the write clock pulses minus the read clock pulses.

The pointer jumps between adjacent stages every time one of the two clocks changes the counter, but, as long as the time difference between corresponding pulses of the two clocks is constant, the pointer is always placed on the same stage of the shift register when the reading takes place.

If the write clock is faster, sooner or later it gives one more increment to the counter, and the reading takes place in the next stage (positive justification).

If the read clock is faster, sooner or later it gives one more decrement to the counter, and the reading takes place in the previous stage (negative justification).

When the end of the register is exceeded, a slip takes place and the counter is corrected (for instance to its mid point, or just slipping one step to come back within range, or..).

The following figure shows a particular application where the elastic buffer is used with synchronous clocks ( =from the same clock domain) and implements the function of a phase aligner.

The bit stream enters with the transmission line clock obtained after several regenerations, is delayed by the necessary amount, and gets out with the system clock:

the bit stream (and in several cases also the byte or the frame synchronization) is again perfectly synchronous with the system timings.

In some cases the elastic buffer is written with blocks of bits at every write operation, and discharged by the same amount of bits at every read operation. In this case the frequency of the write and of the read clock is a corresponding submultiple of the incoming serial clock and of the output serial clock.
In practice the write and read cycle in those cases treat an entire byte or an entire frame at each time.
It should also be noted that an elastic buffer is sometimes built by several sections that operate on parallel bit streams received. One example can be the re-sync of truly parallel streams of bits received from a parallel interface, another can be the multiple sampling of a received pulse of a serial transmission for subsequent processing in a DSP.


For instance, in the following figure, let's consider the delay that the signal suffers along the external loop (with 9 regenerations):

Clock paths in the same domain.png
A clock signal that has cumulated jitter along a transmission path is re-synchronized with the system clock.

It is easy to measure the total delay in periods of the system clock at the output of the elastic memory, but it includes the delay added by the elastic buffer. The delay of the elastic buffer must be deducted, and the transmission delay exactly computed. (In the system of the figure above it would also include the transit time added by the 9 regenerators!).

It is important to understand that, inside the elastic buffer, the information of how much delay the buffer memory is adding in any given moment is available.
This point may be relevant when –for instance- it is necessary to measure the transmission line length measuring the transit time. In such case the time spent during the transit throughout the elastic buffer must be deducted.


The jitter TRANSFER AND TOLERANCE OF CASCADED buffers and CDRsEdit

IntroductionEdit

Tolerating input jitter and filtering out its high frequency part are conflicting requirements.

This is evident from the fact that a CDR model has one characteristic frequency that represents both:

  • the frequency beyond which the tolerance is reduced to its bare minimum and
  • the frequency beyond which the low pass rejection (of the same input jitter) becomes effective.

Increasing the characteristic frequency the tolerance improves but more jitter passes trough, and vice-versa.


Linear models are useful even beyond boundary of linearityEdit

Linear mathematical models are -strictly speaking- valid only within the domain of linear systems.

Their usefulness however extends beyond that, because the behavior of any system including non-linearities can be described with good approximation by linear models, as long as the signal has small excursions around a fixed working point.

This is the often case for PLLs, when they are in locked mode with reasonably low input jitter.

"In locked mode, a SEC (SDH equipment slave clocks) will generally mimic the behaviour of a 2-nd order linear analogue phase locked loop.

This allows the use of the terms (equivalent) 3 dB bandwidth and (equivalent) damping factor, as they are used in analog PLL theory,

irrespective of the fact that in the implementation of a SEC, digital and/or non-linear techniques may be used."[1]

It should be remarked that the Recommendation implicitly refers to a 2nd order PLL of type 1, not of type 2.

This is in accordance with the relative merits and preferred applications of the 2nd order loop models presented in this book, because the SEC equipment implements a sophisticated slave CDR and possibly the regeneration of a transmission link.

See also, for another instance, [2] where the linear model is used in computing jitter and wander accumulation in a chain of identical regenerators.


In this page linear models of PLL will be used as a good approximation of real CDRs in locked mode, used in cascade, for their jitter transfer functions and characteristics, for their jitter tolerance functions and characteristics and for the accumulation of generated jitter.

The (approximate and simplified, useful in "normal" cases) rule is:

  • the jitter transfer characteristics (in dB) add for two stages in cascade;
  • the jitter tolerance characteristics of two stages in cascade are obtained by the AND of the two tolerance regions.


The jitter tolerance curves and masks look like one or more steps of a stairwayEdit

The following figure is a specifications of jitter tolerance in form of a mask, and is shaped pretty much like with a stairway with treads and risers!

The tolerance mask looks like a staircase

A very similar masks is present in ITU-T Recommendation G.823 Fig.13 [3] and similar ones in other ITU-T Recommendations[4].

The ITU-T explains that staircase input jitter tolerance masks are the result of requiring compliance of the input jitter with more "single-step" jitter tolerance masks.[5][6]

To better understand how the stairway masks come about, reference can be made to the jitter tolerance functions derived from the mathematical models:

Three magnitude functions of jitter tolerance for the three main loop models in the case of phase-aligner architectures.
For each the lateral eye opening is the same, as is the same the length of the elastic buffer (=phase adder).
The two important 2nd order PLLs are plotted as well, in the under-damped but significant condition of ζ = 0.5.
The natural frequency is 500 KHz (ωn= 3.14 e6 rad/sec) and is the same for each of the three loops (yellow marker).

Some general properties of the tolerance functions can be inferred from the figure above:

  • A flat tread corresponds to a elastic buffer. The horizontal y-axis value can be seen as the buffer margin (positive or negative, whichever is smaller), to absorb the actual wander or jitter.
  • A sloping riser (of asymptotic slope of 20 dB/dec or 40 dB/dec according to the PLL type being respectively 1st or 2nd type) corresponds to a PLL that tracks the input wander or jitter with a phase error that decreases with decreasing frequency correspondingly.
The ITU-T generally specifies its masks with risers of 20 dB/dec, that coincides with asymptotic slopes of type 1 systems, both 1st order or 2nd order[5] [7] (20 dB/dec). (A type 2 system (40 dB/dec) fits easier a mask riser (20 dB/dec)).
  • The corner frequency between a tread and the riser to its left is also the corner frequency of the jitter transfer curve of the corresponding PLL.
  • If a tread has a riser to its left, that buffer that it relates to has writing and reading clocks that are slave to the same master.
  • If the stairway ends to the left with a riser, a single clock domain is involved, and all PLLs (that are suggested in the case of a tolerance mask or modeled in the case of a tolerance function) are slaved to the incoming signal.
  • If the stairway ends to its left with a tread, two clock domains are involved, and the wander (or jitter) between them may make the largest buffer (the upper thread) spill with slips. (Note that this is the case of the phase aligners mask requirements and mathematical models, because the tolerance masks or tolerance functions do not require both clocks to belong to the same clock domain. Nonetheless, their practical application and operation is meant to be within a single clock domain.)


ITU-T jitter tolerance masks covering wander and jitter have two, three or four treads. (The 4 treads masks apply only to asynchronous tributary channels that "tunnel" SDH islands of higher clock rates, the other masks have two or three treads). For more details, see [8]

(Note that a tolerance masks would not require that the actual implementation of a complying equipment follows the considerations listed. It simply implies that an implementation following them is possible)

  • The rightmost two treads (at higher frequencies, above 10 Hz) are related to the tolerance to jitter[9] :
    • the rightmost is the tolerance (LEO) of the wideband CDRs in the regenerators along the path,
    • the next is the tolerance of the node de-jitterers (see below).
  • One or two steps to the left are in the wander range (below 10 Hz).
    • The (possible) first "plateau" to the left (= lowest frequency tread) takes into account all wander sources, in particular the clock wander if in "hold-over" (=free-running) mode of the SDH islands that are traversed by the tributary that the mask refers to.
    • The wander "plateau" (=tread) at higher frequencies takes into account the other causes (excluding the SDH islands clock wander, that does not contribute when plesiochronous channels are not involved) like:
      • bit stuffing to accommodate asynchronous multiplexing[10] of signals;
      • Byte stuffing (pointer justifications demapping the tributaries;
      • Phase transients of the SDH Equipment Clock


The jitter transfer and tolerance of cascaded CDRsEdit

The first CDR circuit met by the incoming signal at the end of a long segment of the physical line (be it twisted pair, coax or fiber, and just after the input stages of the receiver that perform amplification, equalization and filtering) takes care of regenerating the clock with a large jitter tolerance, but -inevitably, with a correspondingly large jitter filtering bandwidth.[11]

This is, for instance, the typical case for line regenerators.

A chain of identical line regenerators behaves very much like a single regenerator, but with cumulated transfer function for the jitter entering the first regenerator corresponding (if represented with dB magnitudes) to the sum of the individual transfer functions and with a jitter tolerance almost equal to the one of a single regenerator. (A more accurate simulation would account also for the jitter generated at each link of the chain [12], but would not produce drastically different conclusions.)


The following figure represents the tolerance and transfer curves of two CDRs with the same clock frequency, following each other in a simple cascade.

Add caption here

The characteristic frequency (transfer and tolerance low-pass corner) is different in the two CDRs.

The cascade tolerates the amount of sinusoidal jitter that is tolerated by the first and then by the second CDR (the tolerance region of the cascade is the AND of the two regions of the individual CDRs).

Beware of possible overshoots of the transfer curves (gain peakings), that may add if the characteristic frequencies are close.

The line regenerators track well even relatively high frequency jitter, thanks to their high corner frequency.


A high corner frequency however is often incompatible with the requirement of reduced jitter at the output of the node.

If a clock with reduced jitter is available at the node, an elastic buffer like the one presented at the beginning of the page may be used.

Add caption here

The read clock (of the elastic buffer in the figure at the beginning of the page) is NOT slave to CDR1. The read clock does not track (the jitter/wander) of CDR1.

In this case the delay line can not compensate a d.c. wander, when this makes the complementary delay drift beyond the delay line extremes.

This is shown by the limited combined tolerance of the elastic buffer at low frequencies. An elastic buffer following a wideband CDR, like in the case just described, would:

  • filter ALL the jitter present in the incoming signal (meaning all the jitter of the incoming signal with respect to the read clock), but
  • be unable to track any d.c. wander (larger than Tol2 in the figure above)of the incoming signal with respect to the read clock.

In many cases this is acceptable, when operating inside a single clock domain, and the application is called a "phase aligner".

A read clock may reach the node using special protocols (PTP, Precision Time Protocols), that has accumulated almost no jitter and that can be used to de-jitter the clock of CDR1.


In other cases a clean clock for the reading may not available, but the jitter of the incoming signal may still be too large.

In that case an arrangement sketched in the following figure is used (that de-jitters i.e. a "de-jitterizer"):

Add caption here

The second CDR is designed for a larger tolerance, but is slave to the clock of the first.

Its larger tolerance is obtained widening the range of the phase comparator:

  1. . the use of the elastic buffer eliminates the LEO tolerance limitation for CDR2, because it samples pulses that have already been regenerated ;
  2. . the range of the phase comparator (or of the shift register, whichever is smaller) becomes the limit to high frequency jitter tolerance in CDR2

The characteristic cut-off frequency of CDR2 is set lower than CDR1, as much as required for de-jittering the output of CDR1.

Add caption here

An example of :16 ratio in the two dividers before the phase comparator of CDR2 in the "dejitterizer" can be found in [11].

The CDR2, very much as any other CDR, once locked centers itself towards the phase that minimizes the input phase difference of the phase comparator.

The residual phase error will be minimum for a type 1 loop, zero for a type 2 loop.

When the error phase is obtained by the feedback provide by the buffer pointer, the centering of the minimum error drives exactly the average buffer length towards its center, very much like the classic CDR points to the eye middle.

OVERFLOW and UNDERFLOW (SLIPS)Edit

Two clocks that differ slightly in frequency (=that wander) with respect to each other, or that jitter significantly with respect to the one another,

will -from time to time- accumulate more phase difference than the buffer can absorb. Then an abrupt correction becomes necessary.


The resulting correction makes the output serial flow (or byte flow) “slip” with respect to the incoming flow.

An interval of bits disappears or is repeated, and the correction is therefore called a slip.


When the reading takes place synchronously or before the corresponding writing cycle (reading clock faster than the writing clock), then an underflow occurs (with a repetition of some information elements).

If the reading clock is too slow with respect to the writing clock and is unable to read one element before the next arrives, then an overflow occurs (and some information elements are skipped = cancelled).


In case of over/underflow, the reading pointer is made slip by the number of reading operations that corresponds to the time (phase) interval to be added to (or subtracted from) the output serial flow.

The type of correction is different whether the elastic buffer is placed between different clock domains or inside the same clock domain (i.e. its clocks, writing and reading, belong to the same clock domain).

The second figure at the beginning of this page shows a case where two different clocks of the same clock domain (the system clock and its copy after many regenerations) are to be re-synchronized together.
This is not the most general case, because in other cases the two clocks may belong to different clock domains.


Elastic buffer slipsEdit

The buffer operates within one clock domain.

The clock used for transmission at the beginning of the long path is separated from the last regenerated clock by a fixed delay (transit times along the path) plus an a.c. jitter and wander.

There is no d.c. component of wander, because the frequencies of the two clocks are locked to the same master clock.

The writing clock into the elastic buffer (= the last regenerated clock of the long path) and its reading clock (something like the initial transmit clock, or a clock that has accumulated different delay, different wander and different jitter) are to be reconciled by the buffer.

The buffer accepts the writing clock as it is, but -owing to its "elastic" characteristic- shifts the reading clock to make the total delay between the two clocks (transit time plus buffer delay) a fixed value (that is an integral value of a minimum "buffer tolerance").


In this case the elastic buffer depth shall conceptually be at least as large as the maximum peak-to-peak value of the wander/jitter, plus twice its justification step (justification step = the phase step taken when adjusting the buffer delay during normal operation).

Before the writing clock is properly locked to the incoming signal, the buffer is kept frozen at its middle point. When it starts operation and correct phase lock is achieved, it is often so well centered that it will operate indefinitely without the need of any slip.

But the lock-in phase may be troubled by irregular transients, or severe disturbances may affect the transmission later on.

The average delay added by the buffer may then be well distant from the average value of the wander/jitter.

If the wander/jitter deviates then significantly from its average value, the buffer may reach its closer end. A slip would becomes necessary.

  • If the slip depth is less than the maximum wander/jitter peak, then the shifting of the reading clock does not reach far enough, and a jitter peak later on may again cause another slip.
An optimum centering of the buffer may require more than one slip. It may look like the elastic buffer simply saturates, in the sense that the reading clock pointer remains at the min or max value allowed, and that the reading clock itself overflows or under flows by small steps until the elastic buffer achieves a good "centering" of normal range of elasticity its around the position of "zero" jitter.
  • If the slip depth is larger that the maximum wander/jitter peak, a slip would recenter the buffer enough to prevent future slips, as long as the wander/jitter stays within its maximum peak-to-peak range.

The first case of small depth offers less transit delay, but carries the risk of more slips. The second corrects efficiently at the first slip, but maintains a longer transit delay. In either case, the buffer depth may be further increased by considerations about the opportunity to execute a slip that preserves some framing characteristics of the payload, as the next subsection outlines.


The buffer operates between two clock domains.
The two clocks do not share a link with a common clock source (=they belong to different clock domains).

The buffer action is complicated by the fact that they exhibit a frequency difference, although small, that makes the phase difference grow slowly but without limit. (The frequency difference generates a d.c. wander in addition to the a.c. wander and jitter).

Slips are inevitable, and the elastic buffer function is to make them rare enough at the expenses of the average transit delay (that is proportional to the minimum time between slips that has been chosen to set the buffer depth).
The minimum buffer depth must be, in addition to the requirement of the case before (maximum peak-to-peak value of the wander/jitter, plus twice its slip depth), also allow for d.c. wader, which means plus twice the depth corresponding to the minimum time between slips generated by the worst case d.c. wander.
The elastic buffer, of depth equal to n clock cycles, is at the boundary between different clock domains of frequencies f1 and f1-Δf. It will be subject to periodic slips (under or overflows), with a period approximately given by:
 \tfrac{\left ( \tfrac{buffer_depth - 1}{2} \right ) }{\Delta f}
The buffer depth in this second case is bigger than in the case of a buffer inside a single clock domain.


Controlled slips (overflow or underflow execution with minimum inconvenience to the “payload”)
In some cases, when the incoming data flow is framed, if a slip is inevitable it may be convenient to slip (cancel or replicate) an entire frame, exactly from beginning to end (e.g. TDM frames of layer 1 synchronization).
Or, if the incoming data have a layer 2 packet structure, it may be convenient to drop or duplicate inter-frame idle characters (e.g. Ethernet inter-frame characters).
To slip an entire frame or character, when the reading clock gets close (e.g. within +/- 5% of the buffer size) to either end of the buffer and a slip appears inevitable within a short time, the decision to slip is taken, but it is put to effect a little later, in coincidence with the start of the next frame. Obviously, the buffer must be long at least 10% more than one entire frame, but this minimum requirement is usually largely exceeded.
The cost is not significantly different whether the buffer memory is organised by bit or by byte. The saving in transit time when organising by bit with respect to organising by byte, is not significant either, as the average delay is expected to be several bytes anyway.


External ReferencesEdit

  1. ITU-T Rec. G.813 Appendix II Considerations on bandwidth requirements, noise accumulation and payload wander accumulation II.1 Introduction
  2. ITU-T G-series Recommendations – Supplement 36, Jitter and wander accumulation in digital networks, 1 Jitter and wander accumulation - Digital regenerator component
  3. ITU-T G.823 March 2003 (The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy) Fig. 13
  4. ITU-T O.172 April 2005 Jitter and wander measuring equipment for digital systems which are based on the synchronous digital hierarchy (SDH)
  5. a b ITU-T G.825 - 2000 03 The control of jitter and wander within digital networks which are based on the synchronous digital hierarchy (SDH), APPENDIX I Relationship between network interface jitter requirements and input jitter tolerance
  6. ITU-T G.8251 (09/2010) - The control of jitter and wander within the optical transport network (OTN), Appendix I Relationship between network interface jitter requirements and input jitter tolerance, I.2 Input jitter tolerance of network equipment
  7. ITU - T G.825 - 2000 03 The control of jitter and wander within digital networks which are based on the synchronous digital hierarchy (SDH), Appendix I Relationship between network interface jitter requirements and input jitter tolerance
  8. G.823 (03/2000) The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy APPENDIX I Wander limit considerations for SDH transport networks
  9. ITU-T G.825 (0372000) The control of jitter and wander within digital networks which are based on the synchronous digital hierarchy (SDH), APPENDIX I Relationship between network interface jitter requirements and input jitter tolerances, I 1 Network interface jitter requirements
  10. ITU-T Rec.G.707/Y.1322 (01/2007) Network node interface for the synchronous digital hierarchy (SDH), 8 Pointers
  11. a b ITU-T Rec. G.8251(09/2010) The control of jitter and wander within the optical transport network (OTN), Appendix IV.4 Jitter generation of regenerators using parallel serial conversion
  12. ITU-T Rec.G.8251 (09/2010) The control of jitter and wander within the optical transport network (OTN), Appendix III Hypothetical reference model (HRM) for 3R regenerator jitter accumulation and Appendix IV 3R regenerator jitter accumulation analyses