The Problem With Jitter

Jitter has been around for as long as the telecommunications industry has been trying to shift bits and bytes from A to B. Jitter is not cool, it’s unloved and nobody wants it and just like the bore at an office party it won’t go away. Now, just to be clear, we are talking about physical layer jitter here i.e. the ability of clock recovery circuits to function correctly and to determine if the data is a one or a zero or the closure of an eye diagram in the time domain. If you are expecting to hear about packets or packet jitter then this blog is not for you!

The higher speed circuitry, required for 100GbE, makes jitter a much bigger challenge than it was in the past. It’s much more difficult to have clean, open eye diagrams free of noise at 25GHz clock speeds. This is specified in IEEE 802.3. However, when the Ethernet clock is also used as part of the synchronization chain (i.e. Synchronous Ethernet, or SyncE), then there is another jitter standard which also has to be met, ITU-T G.8262. This places limits on jitter at much lower frequencies to ensure jitter doesn’t propagate down the synchronization chain.

G.8262 specifies that a SyncE clock must not generate more than 1.2UI pk-pk jitter measured over the 20kHz to 200MHz frequency range. This is hard enough, but the sting in the tail is the jitter tolerance limit – the amount of jitter a clock must tolerate on its input and still function correctly. Jitter tolerance is defined in the form of a mask from 10Hz to 100kHz, with as much as 6445 UI of jitter (250ns) at 10Hz.

Much of the industry focus has been on meeting the Jitter Generation requirements but, in reality, experience shows that much of the equipment out there can struggle to meet the tight Jitter Tolerance limits; especially at the top end of the mask at frequencies around 100kHz. If I was concerned about the quality of the equipment I was about to approve that’s where I’d look. Just saying.

Tim Frost
Strategic Technology Manager, Calnex Solutions.

Recent Blogs

Related Blogs

Partial Support for Partial Timing

Jul 20, 2017
For a long time now, operators have been asking about how to use PTP to transfer time…
2778 Read more
accurate_timing_in_financial_trading

Accurate Timing in Financial Trading

Feb 09, 2020
Today’s financial trading ‘floor’ is a data warehouse with racks of servers conducting…
678 Read more

Tim Frost’s ITSF Conference Highlights

Dec 06, 2019
This year’s ITSF was the biggest ever – and I’ve been attending since 2005. We had more…
1356 Read more

Archived Blogs

1686 More
1869 More

Timing not Telecoms

Nov 08, 2016
1251 More

5G Coming Soon

Aug 22, 2016
1260 More

What is 1588 PTP?

Aug 04, 2016
1685 More

5G on the Horizon

Aug 01, 2016
1291 More

What is a PTP Clock?

Apr 09, 2016
1577 More

What is Time Error?

Oct 21, 2015
1285 More

LTE-A & VoLTE Rollout

Sep 22, 2015
1222 More

LTE Picks Up Speed

Aug 22, 2015
1205 More

What is the Time?

Aug 22, 2015
1230 More

Mobile and Sync

Aug 22, 2015
1206 More

What is SyncE?

Aug 22, 2015
2454 More
1338 More

Microwave Update

Aug 22, 2015
1306 More

Unravelling Standards

Aug 22, 2015
1274 More

Partial Progress?

Aug 22, 2015
1199 More

Interpreting ITU

Aug 22, 2015
1217 More

Confusion Rules!

Aug 22, 2015
1265 More

Basestations Need Sync

Aug 22, 2015
1264 More

ITSF 2015 Edinburgh

Aug 22, 2015
1215 More

India to Follow China?

Aug 07, 2015
1227 More
HOW CAN CALNEX HELP YOU FURTHER?

Click your area of interest below for more tutorials and real-world case studies.