The Problem: Your design must meet the 100 mui peak-peak Jitter Generation requirement of gr 2531



Download 89.91 Kb.
Date conversion17.07.2018
Size89.91 Kb.
U

nderstanding OmniBER 718 Option 210



  1. The Problem: Your design must meet the 100 mUI peak-peak Jitter Generation requirement of GR 2531.

Jitter Generation refers to the intrinsic jitter generated within a Network Element (NE). It is measured at the output of the NE, with no jitter or wander applied at the input.


The 100 mUI peak-peak jitter requirement applies to Category II interfacesError: Reference source not found, which include all OC-N optical and STS-N electrical interfaces to SONET NEs.
Jitter is a noise process, so it is statistical in nature. Maximum peak-peak jitter is accumulated and measured over a 60 second interval2. Low- and high-pass filters are also used, to limit the measurement to the jitter frequency range of interest3.




100 mUI

100 mUI

(GR-253)

GR-253


Cat II Jit Gen

Requirement




  1. A possible solution?

    What about using a tester with jitter measurement accuracy per O.172?

Most SONET jitter testers available today specify the accuracy of their jitter measurement according to ITU-T recommendation O.172.

O.172 specifies jitter measurement accuracy in a number of ways, all in terms of maximum peak-peak jitter using a concatenated SDH (SONET) signal with a 2231 PRBS payload4. The total measurement error allowable comprises fixed and variable components:
±R% of reading ±W


  • R is the variable component, expressed as a % of the reading. R varies according to the frequency of jitter present in the signal. At STM-16 (OC-48), R ranges from ±7% for low jitter frequencies to ±20% for high jitter frequencies.

  • W is the fixed error, expressed in UI. This is the intrinsic jitter of the tester’s receiver.




  • O.172 jitter measurement accuracy cannot guarantee compliance with GR-253!

100 mUI

100 mUI

(GR-253)

GR-253


Cat II Jit Gen

Requirement



100 mUI

tester


intrinsic

jitter


20%

7%

50 mUI

tester


intrinsic

jitter



20%

10%

O.172


f1–f4

O.172

f3–f4

(narrow band)



  1. The best solution!

    Select from two OmniBER 718 models with superior jitter intrinsic performance!


For some time now, OmniBER has delivered the industry’s best jitter intrinsic performance in the shape of option 200. Typically, this allows designers to work to a 30 mUI safe design margin for peak-peak jitter.


Now, OmniBER also offers a new version – option 210 – that guarantees receiver jitter intrinsics, 30% lower than its current best-in-class levels5. You can now work, with even more confidence, to a 45 mUI safe design margin for peak-peak jitter.
With this significant increase in safe design margin, you can save R&D time, and so benefit from reduced costs and faster time-to-market!



100 mUI

100 mUI

(GR-253)

GR-253


Cat II Jit Gen

Requirement



100 mUI

tester


intrinsic

jitter

20%


7%

50 mUI

tester


intrinsic

jitter



20%

10%

O.172


f1–f4

O.172


f3–f4

(narrow band)




50 mUI

tester


intrinsic

jitter


20%

7%

35 mUI

tester


intrinsic

jitter



20%

7%

OmniBER


Option 210

f1–f4



30 mUI safe

design margin

45 mUI safe

design margin

OmniBER


Option 200

(typical)

f1–f4

The Full Story…

Bandwidth Comparison





GR-2536

O.172 f1-f47

O.172 f3-f4Error: Reference source not found

OmniBER 718

options 200 & 210




HP

LP

f1

HP

f4

LP

Meets GR-253?

f3

HP

f4

LP

Meets GR-253?

HP

LP

Meets GR-253?

OC-48

12 kHz

20 MHz

5 kHz

20 MHz



1 MHz

20 MHz



5 kHz

20 MHz


OC-12


12 kHz

5 MHz

1 kHz

5 MHz



250 kHz

5 MHz



1 kHz

5 MHz



OC-3

12 kHz

1.3 MHz

500 Hz

1.3 MHz



65 kHz

1.3 MHz



500 Hz

1.3 MHz



STS-3

12 kHz

1.3 MHz

500 Hz

1.3 MHz



65 kHz

1.3 MHz



500 Hz

1.3 MHz



OC-1

12 kHz


400 kHz

100 Hz

400 kHz



20 kHz

400 kHz



100 Hz

400 kHz



STS-1

12 kHz

400 kHz

100 Hz

400 kHz



20 kHz

400 kHz



100 Hz

400 kHz


In addition to the high-pass filters listed above, OmniBER also offers a 12 kHz high-pass filter at all rates, convenient for GR-253 peak-peak and rms jitter measurements.



Peak-Peak Jitter Comparison




GR-253


O.172 f1-f4

OmniBER 718 opt 200

OmniBER 718 opt 210




Max
pk-pk
8

W9

Max R10

Meets GR-253?

W (typical)

Max R

Meets GR-253?

W

Max R

Meets GR-253?

OC-48

100 mUI

100 mUI

±20%



50 mUI

±20%



35 mUI

±20%



OC-12

100 mUI

100 mUI

±15%




50 mUI

±15%



35 mUI

±15%



OC-3

100 mUI

70 mUI

±10%



35 mUI

±10%



35 mUI

±10%



STS-3

100 mUI

70 mUI

±10%



35 mUI

±10%



35 mUI

±10%



OC-1

100 mUI

70 mUI

n/a

?

35 mUI

±8%



35 mUI

±8%




STS-1

100 mUI

n/a

n/a

?

35 mUI

±8%



35 mUI

±8%



RMS Jitter Comparison







GR-253

O.172 f1-f4

OmniBER 718

options 200 & 210




Max
rmsError: Reference source not found


W

W (typical)

Max R

Meets GR-253?

OC-48

10 mUI

n/a

4 mUI

±20%



OC-12

10 mUI


n/a

4 mUI

±15%



OC-3

10 mUI

n/a

4 mUI

±10%



STS-3

10 mUI

n/a

4 mUI

±10%



OC-1

10 mUI

n/a

4 mUI

±8%



STS-1

10 mUI

n/a

4 mUI

±8%


O.172 treats rms jitter measurement as optional11, so it contains no accuracy specification for rms jitter measurement.




1 Telcordia Technologies GR-253-CORE Issue 3 September 2000, section 5.6.2.3.6 Category II Jitter Generation, requirement R5-258.

2 See GR-253-CORE section 5.6.1 Network Interface Jitter Criteria.

3 See GR-253-CORE section 5.6.2.3 Jitter Generation.


4 ITU-T O.172 (03/2001), section 9.4 Measurement accuracy.

5 30% reduction in receiver jitter intrinsics applies at OC-48 and OC-12 data rates.

6 Figures from GR-253-CORE section 5.6.2.3 and Table 5-9.

7 Figures from ITU-T O.172 Table 7/O.172.

8 Figures from GR-253-CORE section 5.6.2.3.6, requirement R5-258.

9 Figures from ITU-T O.172 Table 8/O.172.

10 Figures from ITU-T O.172 Table 10/O.172.

11 See ITU-T O.172 section 9.2.3 Measurement of RMS jitter.

Page of

© Agilent Technologies UK Ltd. 2001






The database is protected by copyright ©hestories.info 2017
send message

    Main page