Académique Documents
Professionnel Documents
Culture Documents
Outline
Background (analog telephony, TDM, PDH) SONET/SDH history and motivation Architecture (path, line, section) Rates and frame structure Payloads and mappings Protection and rings VCAT and LCAS Handling packet data
2
Background
PSTN Network
class 5 switch
Analog voltages and copper wire used only in last mile, Time Division Multiplexing of digital signals in the network
Extensive use of fiber optic and wireless physical links T1/E1, PDH and SONET/SDH synchronous protocols Signaling can be channel/trunk associated or via separate network (SS7)
4
TDM Timing
Time Domain Multiplexing relies on all channels (timeslots) having precisely the same timing
(frequency and phase) In order to enforce this, the TDM device itself frequently performs the digitization
digital signals analog signals
5
If the TDM switch does not digitize the analog signals then there can be a problem the clocks used to digitize do not have identical frequencies we get byte slips!
(well, actually, we can get bit slips first )
exaggerated pictorial example
1 2 3 4 5 6 7 8 9
Numerical example: clock derived from 8000 Hz. quartz crystal typical crystal accuracy = 50 ppm So 2 crystals can differ by 100 ppm i.e. 0.8 samples / second So difference is 1 sample after 1 seconds
component signals
9
1 1 1
2 2 2
3 3 3
4 4 4
5 5 5
6 6 6
7 7 7
9 8 8
TDM
6
The Fix
We must ensure that all the clocks have the same frequency Every telephony network has an accurate clock called a stratum 1, or Primary Reference Clock All other clocks are directly or indirectly locked to it (master slave) A TDM receiving device can lock onto the source clock based on the incoming data (FLL, PLL) For this to work, we must ensure that the data has enough transitions
1 0 transitions no transitions
7
Comparing Clocks
A clock is said to be isochronous (isos=equal, chronos=time) if its ticks are equally spaced in time 2 clocks are said to be synchronous
(syn=same chronos=time)
(plesio=near chronos=time)
if they are nominally with the same frequency but are not locked
PDH principle
If we want yet higher rates, we can mux together TDM signals (tributaries) We could demux the TDM timeslots and directly remux them
insist that the mux provide clock to all tributaries (not always possible, may already be locked to a network) somehow transport tributary with its own clock across a higher speed network with a different clock (without spoiling remote clock recovery)
PDH Hierarchies
level
0
*
64 kbps 30
*
24
24 J1 1.544 Mbps
*
1 2 3 4
E1 2.048 Mbps
*
T1 1.544 Mbps
*
E2 8.448 Mbps
*
T2 6.312 Mbps
*
J2 6.312 Mbps
*
4 T3
E3
34.368 Mbps
*
44.736 Mbps
*
J3 32.064 Mbps
*
J4 97.728 Mbps
10
Japan
4:1 Multiplexer
11
1:4 Demultiplexer
12
PDH Justification
In addition to FAS, PDH overhead includes
justification control (C-bits) and justification opportunity stuffing (S-bits) Assume the tributary bitrate is B T Positive justification payload is expected at highest bitrate B+T if the tributary rate is actually at the maximum bitrate then all payload and S bits are filled if the tributary rate is lower than the maximum then sometimes there are not enough incoming bits so the s-bits are not filled and C-bits indicate this Negative justification payload is expected at lowest bitrate B-T if the tributary rate is actually the minimum bitrate then payload space suffices if the tributary rate is higher than the minimum then sometimes there are not enough positions to accommodate so S-bits in the overhead are used and the C-bits indicate this Positive/Negative justification payload is expected at nominal bitrate B positive or negative justification is applied as required
13
30
DSMX 64k/2
1
30
DSMX 34/140
PCMX 30
64 30
DSMX 2/8
14
9 10 11 12 13 14 15 6 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
15
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Si
Si (M)
A Sa Sa Sa Sa Sa 4 5 6 7 8
Si: Reserved for international use Sa4: Non urgent Alarm (0=Alarm) A: Remote alarm (1=urgent Alarm)
Sa4 to Sa8: Spare bits or used for message based data links (point-to-point applications) FAS: Frame alignment signal (0011011) NFAS: Non frame alignment signal
16
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Si
MFAS
a b c d a
NMFAS
b c d
Si (M)
A Sa Sa Sa Sa Sa 4 5 6 7 8
signalling subscr. n
Si: Reserved for international use Sa4: Non urgent Alarm (0=Alarm) A: Remote alarm (1=urgent Alarm) Y: Remote MF alarm (1=Alarm) E: CRC error indication (0=Error) Sa4 to Sa8: Spare bits or used for message based data links (point-to-point applications) FAS: Frame alignment signal (0011011) NFAS: Not frame alignment signal
17
multiframe
fr 6 fr 7 fr 8 fr 9 fr 10 fr 11 fr 12 fr 13 fr 14 fr 15
sub multiframe 1
sub multiframe 2
Si
MFAS
a b c d a
NMFAS
b c d
Si (M)
Sa Sa Sa Sa Sa 4 5 6 7 8
signalling subscr. n
Si: Reserved for international use Sa4: Non urgent Alarm (0=Alarm) A: Remote alarm (1=urgent Alarm) Y: Remote MF alarm (1=Alarm) Sa4 to Sa8: Spare bits or used for message based data links (point-to-point applications) FAS: Frame alignment signal (0011011) 18 NFAS: Not frame alignment signal
multiframe
fr 6 fr 7 fr 8 fr 9 fr 10 fr 11 fr 12 fr 13 fr 14 fr 15
sub multiframe 1
sub multiframe 2
2.048 kbit/s frame: 32x8 bit=256 bit in 125s signalling information encoded voice / data signals
0 1 2 3 4 5 6 7 8
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Si
MFAS
a b c d a
NMFAS
b c d
Si (M)
Sa Sa Sa Sa Sa 4 5 6 7 8
signalling subscr. n
C4 0 E2 1
Si: Reserved for international use Sa4: Non urgent Alarm (0=Alarm) A: Remote alarm (1=urgent Alarm) Y: Remote MF alarm (1=Alarm) E: CRC error indication (0=Error) M: Transmitting CRC multiframe alignment signal ( CRC MFAS: 001011 ) Sa4 to Sa8: Spare bits or used for message based data links (point-to-point applications) FAS: Frame alignment signal (0011011) 19 NFAS: Not frame alignment signal
1a 2a 3a 4a
1b 2b 3b 4b
1c 2c 3c 4c s1 s2 s3 s4
1 1
1 0 1 0
0 0
0 A N
A: Alarm Bit N: National Spare Bit 1a: Stuffing Control Bit S: Stuffing Bit
34.368 kbit/s; frame length 1536 bit; 44.7 us; ITU-T G.751
10 2 372 4 380 4 380 4 4 376
1a 2a 3a 4a
1b 2b 3b 4b
1c 2c 3c 4c s1 s2 s3 s4
1 1 1 1
0 1
0 0
0 A N 20
10
1a 2a 3a 4a
1b 2b 3b 4b
1c 2c 3c 4c
1d 2d 3d 4d
1e 2e 3e 4e s1 s2 s3 s4
1 1 1 1 1 0 1 0 0 0 0 0 A N N N
A: Alarm Bit N: National Spare Bit 1a,b,c,d: Stuffing Control Bit S: Stuffing Bit
21
In addition to locking on to bit-rate, we need to recognize the frame structure We identify frames by adding Frame Alignment Signal The FAS is part of the frame overhead (which also includes "C-bits", OAM, etc.) Each layer in PDH hierarchy adds its own overhead For example
E1 2 overhead bytes per 32 bytes overhead 6.25 % E2 4 E1s = 8.192 Mbps out of 8.448Mbps
so there is an additional 0.256 Mbps = 3 % 22 altogether 4*30*64 kbps = 7.680 Mbps out of 8.448 Mbps or 9.09% overhead
11
PDH overhead
digital signal T1 T2 T3 T4 E1 E2 E3 E4 data rate (Mbps) 1.544 6.312 44.736 274.176 2.048 8.448 34.368 139.264 voice channels 24 96 672 4032 30 120 480 1920 overhead percentage 0.52 % 2.66 % 3.86 % 5.88 % 6.25 % 9.09 % 10.61 % 11.76 %
23
OAM
major faults could go undetected for long periods of time hard to characterize and localize faults when reported minor defects might be unnoticed indefinitely
Solution is to add mechanisms based on overhead As PDH networks evolved, more and more overhead was dedicated to Operations, Administration and Maintenance (OAM) functions including:
24
12
USA
Europe
564992 kbit/s
x4
4.
97728 kbit/s
x3
274176 kbit/s
x3 x6
139264 kbit/s
x4
3.
32064 kbit/s
x5
44736 kbit/s
x7
34368 kbit/s
x4
2. order
6312 kbit/s
x4 x3
8448 kbit/s
x4
primary rate
1544 kbit/s
2048 kbit/s
x 24
x 30/31
64 kbit/s
25
26
13
PDH Equipment
AIS
PDH Equipment
AIS
27
140 Mbit/s
stand-by
34 - 140 8 - 34 2-8 34 - 140 8 - 34 2-8
1,2 ................. 64
1,2 ................. 64
28
14
29
PDH limitations
Rate limitations
Copper interfaces defined Need to mux/demux hierarchy of levels (hard to pull out a single timeslot) Overhead percentage increases with rate
E 2.048, 8.448, 34.348, 139.264 T 1.544, 3.152, 6.312, 44.736, 91.053, 274.176 J 1.544, 3.152, 6.312, 32.064, 97.728, 397.2
15
31
Standardization !
hierarchy of signals, all multiple of basic rate (50.688) basic rate about 50 Mbps to carry DS3 payload bit-oriented mux mechanisms to carry DS1, DS2, DS3
Many other proposals were merged into 1987 draft document (rate 49.920) In summer of 1986 CCITT express interest in cooperation
needed a rate of about 150 Mbps to carry E4 wanted byte oriented mux byte mux US wanted 13 rows * 180 columns CEPT wanted 9 rows * 270 columns US would use basic rate of 51.84 Mbps, 9 rows * 90 columns CEPT would use three times that rate - 155.52 Mbps, 9 rows * 270 columns
Compromise!
32
16
VC-4
STS-3C SPE
TUG-2 VT group
x1
VC-2
VT-SPE
C-2
SDH
ITU-T G.707
x4
VC-12
VT-SPE
x3
VT-2
C-12
SONET
TU-11 VT-1.5
VC-11
VT-SPE
C-11
33
34
17
Synchronous Transfer Signals are bit-signals (OC are optical) Like all TDM signals, there are framing bits at the beginning of the frame However, it is convenient to draw SONET/SDH signals as rectangles
35
9 rows
Each STS-1 frame is 90 columns * 9 rows = 810 bytes There are 8000 STS-1 frames per second so each byte represents 64 kbps (each column is 576 kbps) Thus the basic STS-1 rate is 51.840 Mbps
36
18
9 rows
Synchronous Transport Modules are the bit-signals for SDH Each STM-1 frame is 270 columns * 9 rows = 2430 bytes There are 8000 STM-1 frames per second Thus the basic STM-1 rate is 155.520 Mbps 3 times the STS-1 rate!
37
The STM-4/16/64 bit rate is obtained as integer multiples of the STM-1 tributary bit rate. Clock offset at the tributary side is taken into consideration by pointer adaptation on the STM-n output signal.
38
19
SONET/SDH Rates
SONET STS-1 STS-3 STS-12 STS-48 STS-192 STM-1 STM-4 STM-16 STM-64 SDH columns 90 270 1080 4320 17280 rate 51.84M 155.52M 622.080M 2488.32M 9953.28M
STS-N has 90N columns STM-M corresponds to STS-N with N = 3M SDH rates increase by factors of 4 each time STS/STM signals can carry PDH tributaries, for example: STS-1 can carry 1 T3 or 28 T1s or 1 E3 or 21 E1s 40 STM-1 can carry 3 E3s or 63 E1s or 3 T3s or 84 T1s
20
SONET/SDH tributaries
SONET STS-1 STS-3 STS-12 STS-48 STS-192 STM-1 STM-4 STM-16 STM-64 SDH T1 28 84 336 1344 5376 T3 1 3 12 48 192 E1 21 63 252 1008 4032 E3 1 3 12 48 1 4 16 E4
192 64
E3 and T3 are carried as Higher Order Paths HOPs) E1 and T1 are carried as Lower Order Paths (LOPs)
(the numbers are for direct mapping)
41
Frame Structure
42
21
9 rows
6 rows
Section overhead is 3 rows * 3 columns = 9 bytes = 576 kbps framing, performance monitoring, management Line overhead is 6 rows * 3 columns = 18 bytes = 1152 kbps protection switching, line maintenance, mux/concat, SPE pointer SPE is 9 rows * 87 columns = 783 bytes = 50.112 Mbps
43
STS-1 Overhead
A1 section overhead B1 D1 H1 B2 line overhead D4 D7 A2 E1 D2 H2 K1 D5 D8 J0 F1 D3 H3 K2 D6 D9
3 rows of section overhead frame sync (A1, A2) section trace (J0) error control (B1) section orderwire (E1) Embedded Operations Channel (Di) 6 rows of line overhead pointer and pointer action (Hi) error control (B2) Automatic Protection Switching signaling (Ki) Data Channel (Di) Synchronization Status Message (S1) Far End Block Error (M0) line orderwire (E2)
44
22
RSOH
3 4 5 AU Pointer
Payload
(transport capacity)
MSOH
9
RSOH: Regenerator section overhead MSOH: Multiplex section overhead Payload: Area for information transport Transport capacity of one Byte: 64 kbit/s Frame capacity: 270 x 9 x 8 x 8000 = 155.520 Mbit/s Frame repetition time: 125 s
45
RSOH AU Pointer
AU-4
VC-4 MSOH
VC-4 POH
C-4
46
23
MSOH
STM-1 has 9 (different) columns of transport overhead ! RS overhead is 3 rows * 9 columns Pointer overhead is 1 row * 9 columns MS overhead is 5 rows * 9 columns SPE is 9 rows * 261 columns
47
9 rows
270*N columns
3 STS-1s can form an STS-3 4 STM-1s (STS-3s) can form an STM-4 (STS-12) 4 STM-4s (STS-12s) can form an STM-16 (STS-48) etc. for STM-N (STS-3N) The procedure is byte-interleaving
48
24
Byte-interleaving
...
49
STM-1 Overhead
A1 RSOH B1 D1 A1 m m A1 m m A2 E1 D2 A2 m m A2 J0 F1 D3 res res res res m media dependent
(defined for SONET radio)
AU pointers
B2 D4 MSOH D7 D10 S1 B2 B2 K1 D5 D8 D11 M1 K2 D6 D9 D12 E2
50
SOH
25
J0 - regenerator section trace (in early SONET - a counter called C1) enables receiver to be sure that the section connection is still OK enables identifying individual STS/STMs after muxing J0 goes through a 16 byte sequence MSBs are J0 framing (100000) Cs are CRC-7 of previous frame S are 15 7-bit characters section access point identifier
1 0 C1 C2 C3 C4 C5 C6 C7 S S S S S S S
0 S S S S S S S
51
26
4 MSBs are New Data Flag, 10 LSBs are actual offset value (0 782)
When offset=522 the STS-1 SPE is in a single STS-1 frame In all other cases the SPE straddles two frames When offset is a multiple of 87, the SPE is rectangular
To compensate for clock differences we have pointer justification When negative justification H3 carries the extra data When positive justification byte after H3 is stuffing byte
53
SONET Justification
If tributary rate is above nominal, negative justification is needed
When less than 8 more bits than expected in buffer NDF is 0110 offset unchanged When 8 extra bits accumulate NDF is set to 1001 H1 H2 extra extra byte placed into H3 offset is decremented by 1 (byte)
54
27
K1 and K2 are used for Automatic Protection Switching (see later) D4 D12 are a 576 Kbps Data Communications Channel
55
28
57
We saw that the pointer the line overhead points to the STS path overhead POH 58 (after re-arranging) POH is one column of 9 rows (9 bytes = 576 kbps)
29
STS-1 HOP
1 30 59 87
1 column of SPE is POH 2 more (fixed stuffing) columns are reserved We are left with 84 columns = 756 bytes = 48.384 Mbps for payload This is enough for a E3 (34.368M) or a T3 (44.736M)
59
1 column of overhead for path (576 Kbps) POH is responsible for path type identification path performance monitoring status (including of mapped payloads) virtual concatenation path protection trace
POH
60
30
C2 (hex) 00 01 02 04 12 13
Payload type unequipped nonspecific LOP (TUG) E3/T3 E4 ATM PoS RFC 1662 LAPS X.85 10G Ethernet GFP
61
of previous payload C2 path signal label identifies the payload type (examples in table)
16 18 1A 1B CF
PoS - RFC1619
31
LOP
7 VTGs
1 30 59 87
1 2 3 4 5 6 7
To carry lower rate payloads, divide the 84 available columns into 7 * 12 interleaved columns, i.e. 7 Virtual Tributary (VT) Groups
there are different types of VT in order to carry different types of payload all VTs in VT group must be of the same type (no mixing) but different VT groups in same SPE can have different VT types
63
32
LO Path Overhead
LOP OH is responsible for timing, PM, REI, LO Path APS signaling is 4 MSBs of byte K4
H4=XXXXXX00
V1 pointer
125 msec
V5
VC11 25B VC12 34B
H4=XXXXXX01
V2 pointer
J2
500 msec
H4=XXXXXX10
V3 pointer
N2
H4=XXXXXX11
V4 pointer
K4
65
Payload Capacity
VT1.5/VC-11 has 3 columns = 27 bytes = 1.728 Mbps but 2 bytes are used for overhead (V1/V2/V3/V4 and V5/J2/N2/K4) so actually only 25 bytes = 1.6 Mbps are available Similarly VT2/VC-12 has 4 columns = 36 bytes = 2.304 Mbps but 2 bytes are used for overhead So actually only 34 bytes = 2.176 Mbps are available
66
33
LOP Overhead
V5 consists of
BIP (2b) REI (1b) RFI (1b) Signal label (3b) (uneq, async, bit-sync, byte-sync, test, AIS) RDI (1b)
SDH Containers
Tributary payloads are not placed directly into SDH Payloads are placed (adapted) into containers The containers are made into virtual containers (by adding
POH)
Next, the pointer is used the pointer + VC is a TU or AU Tributary Unit adapts a lower order VC to high order VC Administrative Unit adapts higher order VC to SDH TUs and AUs are grouped together until they are big enough We finally get an Administrative Unit Group To the AUG we add SOH to make the STM frame 68
34
Formally
C-n n = 11, 12, 2, 3, 4 VC-n = POH + C-n TU-n = pointer + VC-n (n=11, 12, 2, 3) AU-n = pointer + VC-n (n=3,4) TUG = N * TU-n AUG = N * AU-n STM-N = SOH + AUG
69
Multiplexing
or it may contain 3 AU-3s each with a VC-3s with an E3 and inside the AUG are 3 pointers to the AU-3s
J1 B3 C2 G1 H1 H1 H1 H2 H2 H2 F2 H4 F3 K3 N1 H3 H3 H3
70
35
More Multiplexing
Lower rate STMs can be combined into higher rate STMs AUGs can be combined into STMs AUs can be combined into AUGs TUGs can be combined into high order VCs Lower rate TUs can be combined into TUGs etc.
71
AUG
STM-0
AU-3
C3
C2
C12
C11
36
STS-1
VT6 SPE
VT2 SPE
73
VT1.5 SPE
When mapping tributaries into VCs, PDH-like bit-stuffing is used For E1 and T1 there are several options
Asynchronous mapping (framing-agnostic) Bit synchronous mapping Byte synchronous mapping (time-slot aligned)
E4 into VC-4, E3/T3 into VC-3 are always asynchronous T1 into VC-11 may be any of the 3
(in byte synchronous the framing bit is placed in the VC overhead)
74
37
SONET/SDH Architecture
75
Layers
SONET was designed with definite layering concepts Physical layer optical fiber (linear or ring)
when exceed fiber reach regenerators regenerators are not mere amplifiers, regenerators use their own overhead fiber between regenerators called section (regenerator section)
input and output at this level are Virtual Tributaries (VCs) actually 2 layers
lower order VC (for low bitrate payloads) higher order VC (for high bitrate payloads)
76
38
SONET architecture
ADM
Path Termination Line Termination
regenerator
Section Termination
ADM
Line Termination Path Termination
line protected multiplexed SONET payload section physical link between adjacent elements
SDH terminology
78
39
SDH Repeater
STM-n STM-n Applications: Line Signal Regeneration in Point-to-Point and Ring Networks
79
EAST
STM-1/4
STM-1/4
......
80
40
34 Mbit/s
34 2 140
2 2 34 2 2 140
34 Mbit/s
VC12
140 Mbit/s
VC4
34
VC 4 VC 3 VC 12
VC3
VC11 VC12
VC12
2 (1.5)Mbit/s
81
4 4 4
Sync MUX Management Communication Unit Service Channel Unit Overhead Processing Unit
4 4 4 4
STM-16
SLX 1/16
Sync DEMUX
STM-16
82
41
TM ADM
STM-1, STM-4
2Mbit/s 34Mbit/s
ATM Switch
ADM
STM-1
STM-4/-16 ADM
DXC
LAN ADM : Add Drop Multiplexer DXC : Digital Cross Connect TM : Terminal Multiplexer 2Mbit/s STM-1 / STS-3c Gateway to SONET 34Mbit/s 140Mbit/s STM-1 STM-4
2Mbit/s
83 SDH
Trunk Network L 2
STM-16
Trunk Network L1
STM-1 Exchange
Trunk Network L2
Local Network
Local Exchange
FlexMux
Subscriber Access
Mux 64/2M
84
42
85
Network Resilience
86
43
87
What is protection ?
SONET/SDH need to be highly reliable (five nines) Down-time should be minimal (less than 50 msec) So systems must repair themselves (no time for manual intervention) Upon detection of a failure (dLOS, dLOF, high BER) the network must reroute traffic (protection switching) from working channel to protection channel The Network Element that detects the failure (tail-end NE) initiates the protection switching The head-end NE must change forwarding or to send duplicate traffic Protection switching is unidirectional Protection switching may be revertive (automatically revert to working channel)
working channel
protection channel
head-end NE
tail-end NE
88
44
head-end bridge
tail-end bridge
working channel
protection channel
signaling channel
89
90
channel B
45
May be at any layer (only OC-n level protects against fiber cuts)
working channel
46
W W P
1 : N Protection scheme
93
W W P
94
1 : N Protection scheme
47
95
B-C
48
Traffic B -> A
ADM
Unidirectional Ring
traffic between A-B uses the entire length of ring
97
Of all the possible combinations, only a few are in use Unidirectional Path Switched Rings protects tributaries extension of 1+1 to ring topology Bidirectional Line Switched Rings (two-fiber and four-fiber versions) called Multiplex Section Shared Protection Ring in SDH simultaneously protects all tributaries in STM extension of 1:1 to ring topology
98
49
UPSR
Working channel is in one direction protection channel in the opposite direction All traffic is added in both directions decision as to which to use at drop point (no signaling) Normally non-revertive, so effective two diversity paths Good match for access networks 1 access resilient ring less expensive than fiber pair per customer Inefficient for core networks no spatial reuse every signal in every span in both directions node needs to continuously monitor every tributary to be dropped
99
Fiber 2 : unidirectional
Tributary
Tributary
D
100
50
Fiber 2 : unidirectional
Tributary
Tributary
D
101
Fiber 2 : unidirectional
Tributary
Tributary
D
102
51
Protection
Tributary
Tributary
Working
103
Protection
Tributary
Tributary
Working
104
52
Protection
Tributary
Tributary
Working
105
BLSR
Switch at line level less monitoring When failure detected tail-end NE signals head-end NE Works for unidirectional/bidirectional fiber cuts, and NE failures Two-fiber version half of OC-N capacity devoted to protection only half capacity available for traffic Four-fiber version full redundant OC-N devoted to protection twice as many NEs as compared to two-fiber
106
53
Fiber 2
Tributary
working protection
Tributary
D
107
Fiber 2
Tributary
working protection
Tributary
D
108
54
Fiber 2
Tributary
working protection
Tributary
D
109
Tributary
Tributary
D
110
55
Tributary
Tributary
D
111
Tributary
Tributary
D
112
56
Tributary
Tributary
D
113
Tributary
Tributary
D
114
57
Tributary
Tributary
D
115
116
58
EVENTS SDH
Phys./Reg. Sect.
LOS TSE LSS LTI OOF LOF B1 B2 MS-AIS MS-RDI MS-REI AU-LOP AU-NDF AU-AIS AU-PJE B3 HP-UNEQ HP-RDI HP-REI HP-TIM HP-PLM TU-LOP TU-NDF TU-AIS TU-LOM BIP-2/B3 LP-RDI LP-REI LP-RFI LP-TIM LP-PLM LCD Loss Of Signal Test Sequence Error (Bit Err.) Loss of Sequence Synchron. Loss of incoming Timing Ref. Out Of Frame Loss Of Frame Regenerator Section BIP Err. Multiplex Section BIP Err. Multiplex Section AIS Mux Sect. Remote Defect Ind. Mux Sect. Remote Errro Ind. Loss Of AU Pointer New Data Flag AU Pointer AU Alarm Ind. Signal AU Pointer Just. Event HO Path BIP Errors HO Path Unequipped HO Path Remote Defect Ind. HO Path Remote Error Ind. HO Path Trace Ident. Mismatch HO Path Payload Label Mism. Loss Of TU Pointer New Data Flag TU Pointer TU AIS Loss Of Multiframe LO Path BIP Errors LO Path Remote Defect Ind. LO Path Remote Error Ind. LO Path Remote Failure Ind. LO Path Trace Ident. Mismatch LO Path Payload Label Mism. Loss of Cell Delineation I.610 Correctable Header Errors Uncorrectable Header Errors Virtual Path AIS I.610 Virtual Path Remote Defect Indication I.610 Virtual Channel AIS I.610 Virtual Channel Remot Defect Indication I.610 Virtual Channel AIS & Virtual, Path AIS simultan. (O.191) Virtual Channel RDI & Virtual, Path RDI simultan. (O.191) Loss Of Continuity I.610
EVENTS SONET
Line (L) Phys./Section
LOS TSE LSS LTI OOF LOF B1 B2 AIS-L RDI-L REI-L LOP-P NDF-P AIS-P B3 UNEQ-P RDI-P REI-P PDI-P TIM-P PLM-P LOP-V NDF-V AIS-V LOM UNEQ-V RDI-V REI-V RFI-V PDI-V TIM-V PLM-V Loss Of Signal Test Sequence Error Loss of Sequence Synchr. Loss of inc. TimingRef Out Of Frame Loss Of Frame Section BIP Errors Line BIP Errors Line AIS Line remote Defect Ind. Line Remote Error Ind. SP Loss Of Pointer SP New Data Flag SP AIS SP BIP Errors SP Unequipped SP Remote Deect. Ind. SP Remote ERrro Ind. SP Payload Defect Ind. SP Trace Ident. Mismatch SP Payload Label Mismatch VP Loss Of Pointer VP New Data Flag VP AIS Loss Of Multiframe VP Unequipped VP Remote Defect Ind. VP Remote Error Ind. VP Remote Failure Ind. VP Payload Defect Ind. VP Trace Ident. Mismatch VP Payload Label Mism.
ATM Path
VT Path (VP)
117
RSOH
AU-PTR
Payload
MSOH B3: - Covers the transmission paths from beginning to the end (tributary to tributary)
118
59
BIP-8
B1
Receive Side
frame n+1
frame n
recalculation at Rx side
Comparison
with the Tx side value
BIP-8
B1
119
Bit interleaved data field structure of the area covered BIP-24: 24 bits (B2) Field width: BIP-8: 8 bits (B1, B3) BIP-2: 2 bits (V5) Column by column parity check for even numbers of "1"
Example: 24 bit interleaved parity check (BIP-24)
Byte 1 Byte 2 1 11 1 1 1 1 1 1 1 1 1 1 1 11 1 0 11 1 0 1 11 0 1 01 0 1 1
1 0 0 0 0 1 1 0 1 0 1 0 0 1 0 1 1 0 0 1 1 1 0 1 1 1 0 0 0 1
Byte 3
1 1 0 0 1 1 1 1 0 0 1 1 1 0 1 0 1 0 0 0 1 0 1 1 1 1 1
1 2 3
801 BIP-24
1 1
1 0
0 0
1 1
0 0
1 0
0 0
1 0
1 1
0 0
1 1 1120 0
0 0
1 0
0 0
0 0
1 1
1 0
1 1
0 0
0 1
1 0
0 0
1 0
60
"1" AIS
"1" HP-UNEQ HP-TIM HP-BIP Err. HP-REI HP-RDI TU-AIS TU-LOP LOM HP-PLM "1" AIS
"1"
"1"
AIS
"1" AIS
121
122
61
All "1" in the entire TU incl. TU pointer 8 to 10 NDF enable or 8 to 10 invalid pointers VC-3: C2 = all "0" for >=frames; VC-12: V5 (bits 5,6,7) = 000 for >=5 frames VC-3: J1 mismatch; VC-12: J2 mismatch VC-3: C2 mismatch; VC-12: V5 (bits 5,6,7) mismatch Mismatch of the recovered and computed BIP-2 (V5) V5 (bit 8) = 1, if TU-2 path AIS or signal failure received V5 (bit 3) = 1, if >=1 errors were detected by BIP-2 V5 (bit 4) = 1, if a failure is declared
Perfomance Parameter
ITU-T G.821 ES Errored Second SES
10E-3 Second with > 1 bit error Second with BER > 1 x
62
125
Synchronization Network
Primary Reference Clock
long term: holdover 24h:
PRC
Caesium (Stratum 1)
requ : 1 x 10-11 typ : 5 x 10-12 Rubidium (Stratum 2) requ : 1.6 x 10-8 , 1 x 10-10 typ : 4 x 10-11 , 2 x 10-11
SSU
SSU
SEC
SDH Equip .
SEC
SDH Equip .
SEC
SDH Equip .
126
63
G.813 SEC
G.813 SEC
G.813 SEC
Limits: Max. Max. 10 x G.812 TNC 60 x G.813 SEC, though no more than 20 between 2 TNCs
127
Osc.
128
64
Hold-over Mode
Phase error [ ns]
129
130
65
ITU-T Definitions Network Primary Reference Clocks Synchron. Supply Clocks (ST2) Equipment Clocks (ST3) G.810 G.825 G.811 G.812 G.813 (G.81s)
ETSI ETS 300 462-1 ETS 300 462-3 ETS 300 462-6 ETS 300 462-4 ETS 300 462-5
131
132
66
Jitter: Jitter is the short-term phase variations of the significant instants of a digital signal from their ideal positions in time. It is the deviation of the significant instants of a digital signal from the ideal, equidistant values. The significant instant can be any convenient, easily identifiable point on the signal such as the rising or falling edge of a pulse. Otherwise stated, the transitions of a digital signal invariably occur either too early or too late when compared to a perfect square wave. Wander: A second parameter closely related to jitter is wander. Wander similarly refers to long-term variations in the significant instants. ITU-T G.810 classifies jitter frequencies below 10 Hz as wander and frequencies at or above 10 Hz as jitter.
133
Jittered Signal
Jitter
134
67
Interference Signal
Pattern dependent jitter Phase noise Delay variation Stuffing and wait time jitter Mapping jitter Pointer jitter
135
Signal Input
Pattern
N 1
f
V
HP
LP
Clock
Frequency Divider
Phase Detector
f
V
~ 1 Hz
Phase Detector
VCO
136
68
Wander 10 Hz
Total Jitter
0,15UI
137
Time
Measurement Period
138
69
Network output jitter (G.825) Network element output jitter (G.783, G.813) Jitter transfer function (G.958) Jitter and Wander tolerance (G.825, G.813)
139
WANDER Definitions
Wander TIE MTIE Long-term timing variation (below 10 Hz) "Time Interval Error" "Max. Time Interval Error"
TDEV "Time Deviation", timing variation as a function of integration time. Provides information about the spectral content. TVAR "Time Variation", square of TDEV ADEV MADEV "Allen Deviation" "Modified Allen Deviation"
Definitions specified in ITU-T Rec. G.810
140
70
TIE max
MTI E
TIE min
TIE at t End
142
71
143
Network Management
Basic tasks of network management:
Administrative functions: Operation: links) Maintenance: Identifing and elimination of impairments Network supervising Network linking (anomalies, defects) (reserve links, additional
Operative functions:
72
TMN Overlay
Q
Central OS
Q Q
Local
OS
Q Q ECC
CC
Q ECC
ADM
CC
ADM
ADM
ADM
145
Central OS
Q3 Q3
Q3
ADM
Local NE Manager OS Q3
Q ECC
Q ECC
DXC
ADM
STM-N
STM-N
DXC
ADM
ADM
73
OS
Q3
Data Communication Network
Workstation
DCN
Q3 Q3
Mediation Device
MD
Q2 or Q1
Local Communication Network
Workstation
LCN
Qx
Network Element Network Element
Workstation
NE
NE
MD: Conversion between different interfaces (Information Conversion Function ICF: manufacturer-specific information model -> operator specific information model)
147
Interoperability in TMN
Interoperability problems because of
X
TMN Operations System
multi vendor networks heterogenous technology different standards for protocols and management information
Q3 Q3
QMonitor provides
QMonitor
based on DominoWAN DominoLAN DA-30
Qecc Qecc
easy adaptation to the interface (autoconfiguration) decoding of protocols and management information automatic detection of errors in management information SDH/SONET Qecc access with transmission analyzers . 148
Qecc
74
149
150
75
Concatenation
Payloads that dont fit into standard VT/VC sizes can be accommodated by concatenating of several VTs / VCs For example, 10 Mbps doesnt fit into any VT or VC so w/o concatenation we need to put it into an STS-1 (48.384 Mbps) the remaining 38.384 Mbps can not be used We would like to be able to divide the 10 Mbps among 7 VT1.5/VC-11 s = 7 * 1.600 = 11.20 Mbps or 5 VT2/VC-12 s = 5 * 2.176 = 10.88 Mbps
151
Concatenation (cont.)
There are 2 ways to concatenate X VTs or VCs: Contiguous Concatenation (G.707 11.1) HOP STS-Nc (SONET) or VC-4-Nc (SDH) or LOP 1-7 VC-2-Nc into a VC-3 since has to fit into SONET/SDH payload only STS-Nc : N=3 * 4n or VC-4-Nc : N=4n components transported together and in-phase requires support at intermediate network elements
Virtual Concatenation (VCAT G.707 11.2) HOP STS-1-Xv or STS-Nc-Xv (SONET) or VC-3/4-Xv (SDH) or LOP VT-1.5/2/3/6-Xv (SONET) or VC-11/12/2-Xv (SDH) LOP: X 64 (limitation due to bits in header) HOP: X 256 payload split over multiple STSs / STMs fragments may follow different routes requires support only at path terminations requires buffering and differential delay alignment
152
76
STS-3
270 columns
9 rows
STS-3c
153
However, an STS-Nc signal is not as easily separable when we want to add/drop component signals
154
77
Virtual Concatenation
H4
VCAT is an inverse multiplexing mechanism (round-robin) VCAT members may travel along different routes in SONET/SDH network 155 Intermediate network elements dont need to know about VCAT
(unlike contiguous concatenation that is handled by all intermediate nodes)
in VC-4 X 21 C 142.464
So we have many permissible rates 1.600, 2.176, 3.200, 4.352, 4.800, 6.400, 6.528, 6.784, 8.000, 156
78
in STS-3c X 21 C 142.464 So we have many permissible rates 1.600, 2.176, 3.200, 3.328, 4.352, 4.800, 6.400, 6.528, 6.656, 6.784, 157
Efficiency Comparison
rate 10 w/o VCAT STS-1 efficiency 21% with VCAT VT2-5v VC-12-5v 100 STS-3c VC-4 1000 STS-48c VC-4-16c 42% 67% STS-1-2v VC-3-2v STS-3c-7v VC-4-7v 95% 100% efficiency 92%
158
79
PDH VCAT
VCAT overhead octet
1st frame of 4 E1s Recently ITU-T G.7043 expanded VCAT to E1,T1,E3,T3 Enables bonding of up to 16 PDH signals to support higher rates Only bonding of like PDH signals allowed (e.g. cant mix E1s and T1s) Multiframe is always per G.704/G.832 (e.g. T1 ESF 24 frames, E1 16 frames) 1 byte per multiframe is VCAT overhead (SQ, MFI, MST, CRC) Supports LCAS (to be discussed next) each E1 time
TS0
159
frames of an E1
TS0
There is one VCAT overhead octet per multiframe, so net rate is T1: (24*24-1=) 575 data bytes per 3 ms. multiframe = 191.666 kB/s E1: (16*30-1=) 495 data bytes per 2 ms multiframe = 247.5 kB/s T3 and E3 can also be used We will show the overhead octet format later (when using LCAS, the overhead octet is called VLI)
160
80
Delay Compensation
802.1ad Ethernet link aggregation cheats
each identifiable flow is restricted to one link doesnt work if single high-BW flow works even with a single flow
Requirement for over second compensation Must compensate to the bit level
but since frames have Frame Alignment Signal the VCAT mechanism only needs to identify individual frames
161
VCAT Buffering
Since VCAT components may take different paths At egress the members are no longer in the proper temporal relationship VCAT path termination function buffers members and outputs in proper order (relying on POH sequencing)
(up to 512 ms of differential delay can be tolerated)
VCAT defines a multiframe to enable delay compensation length of multiframe determines delay that can be accommodated H4 byte in members POH contains : sequence indicator (identifies component) (number of bits limits X) MFI multiframe indicator (multiframe sequencing to find differential delay)
162
81
MFI1 (4 bits) appears once per frame and counts from 0 to 15 to sequence the multiframe MFI2 (8bits) appears once per multiframe and counts from 0 to 255
For LOP SDH (bit 2 of K4 byte) a 32 bit frame is built and a 5-bit MFI is dedicated 32 multiframes of 16 ms give the needed 512 ms
163
it doesnt allocate the members still need control protocols to perform actual allocation LCAS is a handshake protocol
it enables the path ends to negotiate the additional / deletion it guarantees that there will be no loss of data during change it can determine that a proposed member is ill suited it allows automatic removal of faulty member
164
82
83
H4 format
MFI2 bits 1-4 MFI2 bits 5-8 CTRL 0 0 GID 0 0 0 0 0 0 CRC-8 bits 1-4 CRC-8 bits 5-8 MST bits more MST bits 0 0 RS-ACK 0 0 0 0 0 0 0 0 0 SQ bits 1-4 SQ bits 5-8 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 MFI1 0 0 0 0 0 1 0 1 1 0 1 0 1 1 1 1 0 0 0 0 0 1 0 1 1 0 1 0 1 1 1 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1
reserved fields
0 0 0
16 frame multiframe
reserved fields
0 0 0 0
167
H4 Format
CRC-8 (when using K4 it is CRC-3) covers the previous 14 frames (not synced on multiframe) polynomial x8 + x2 + x + 1 MST
each VCG member carries the status of all members so we need 256 bits of member status this is done by muxing MST bits there are MST bits per multiframe and 32 multiframes in an MST multiframe no special sequencing, just MFI2 multiframe mod 32 single bit indentifier all members of VCG share the same bit cycles through 215-1 LFSR sequence different VCGs use different phase offsets of sequence
GID
168
84
Step 1: NMS provisions new member source sends CTRL=IDLE for new member GID=g SQ=1 CTRL=NORM GID=g SQ=2 CTRL=NORM sink sends MST=FAIL for new member
GID=g SQ=3 CTRL=EOS 169 GID=g SQ=FF CTRL=IDLE
Step 3: source sends CTRL=EOS for new member GID=g SQ=1 CTRL=NORM new member starts to carry traffic sink sends RS-ACK
Note 1: several new members may be added at once
GID=g SQ=2 CTRL=NORM GID=g SQ=3 CTRL=NORM GID=g SQ=4 CTRL=EOS
Note 2: removing a member is similar Source puts CTRL=IDLE for member to be removed and stops using it All member sequence numbers must be adjusted
170
85
Step 1: sink sends MST=FAIL for member 2 source sends CTRL=DNU (special treatment if EoS) and ceases to use member 2
Note: if EoS fails, renumber to ensure EoS is active
GID=g SQ=1 CTRL=NORM GID=g SQ=2 CTRL=DNU GID=g SQ=3 CTRL=NORM GID=g SQ=4 CTRL=EOS
Step 2: sink sends MST=OK indicating defect is cleared source returns CTRL to NORM and starts using the member again
Note: if NMS decides to permanently remove the member, proceed as in previous slide
171
172
86
PPP is ideal for data transport over such a link PoS uses PPP in HDLC framing to provide a byte-oriented
interface to the SONET/SDH infrastructure
PoS Architecture
IP PPP HDLC SONET/SDH
PoS is based on PPP in HDLC framing Since SONET/SDH is byte oriented, byte stuffing is employed A special scrambler is used to protect SONET/SDH timing PoS operates on IP packets If IP is delivered over Ethernet
the Ethernet is terminated (frame removed) Ethernet must be reconstituted at the far end require routers at edges of SONET/SDH network
174
87
PoS Details
IP packet is encapsulated in PPP default MTU is 1500 bytes up to 64,000 bytes allowed if negotiated by PPP FCS is generated and appended PPP in HDLC framing with byte stuffing 43 bit scrambler is run over the SPE byte stream is placed octet-aligned in SPE (e.g. 149.760 Mbps of STM-1) HDLC frames may cross SPE boundaries
175
POS Problems
PoS is BW efficient but POS has its disadvantages
BW must be predetermined HDLC BW expansion and nondeterminacy BW allocation is tightly constrained by SONET/SDH capacities
e.g. GBE requires a full OC-48 pipe so lose RPR, VLAN, 802.1p, multicasting, etc
88
LAPS
X.85 IP over SDH using LAPS X.86 Ethernet over LAPS Use ISO HDLC format
Implement connectionless byte-oriented protocols over SDH X.85 is very close to (but not quite) IETF PoS
177
GFP Architecture
A new approach, not based on HDLC Defined in ITU-T G.7041 (also numbered Y.1303) originally developed in T1X1 to fix ATM limitations (like ATM) uses HEC protected frames instead of HDLC
Ethernet
IP
HDLC
other
GFP client specific part GFP common part SDH OTN other
Client may be PDU-oriented (Ethernet MAC, IP) or block-oriented (GBE, fiber channel) GFP frames are octet aligned contain at most 65,535 bytes consist of a header + payload area Any idle time between GFP frames is filled with GFP idle frames
178
89
core header
Idle GFP frames have PLI=0 have no payload area Non-idle GFP frames have 4 bytes in payload area the payload has its own header 2 payload modes : GFP-F and GFP-T optionally protect payload with CRC-32
179
180
90
GFP Modes
GFP-F - frame mapped GFP Good for PDU-based protocols (Ethernet, IP, MPLS) or HDLC-based ones (PPP) Client PDU is placed in GFP payload field GFP-T transparent GFP Good for protocols that exploit physical layer capabilities In particular 8B/10B line code
used in fiber channel, GbE, FICON, ESCON, DVB, etc Were we to use GFP-F would lose control info, GFP-T is transparent to these codes Also, GFP-T neednt wait for entire PDU to be received (adding delay!)
181
91