02 - SDH Introduction

Introduction to SDH
Module of SDH and 6325 FP 1.1 Training (KTI)

16-03-2006 / Flemming Gerdstrm
SDH intro, 060320.ppt
Course plan
> The background for SDH (including History)
> SDH basics, including
> Topics and Case studies
> The End (of part one, or of.)

> Introduction to Functional modelling
> Key standards
> How to find a standard and other relevant material
Time line
Analogue telephony
Digital telephony
(PDH)
Development of the Synchronous Optical NETwork

(SONET) started in mid 80s at Bellcore
SONET
TMN
Digitally based telephony transmission systems

developed in the 60s and early 70s
SDH
OTN
First international Synchronous Digital Hierarchy

(SDH) standard based on SONET work in 88
Optical Telecom. Network (OTN) from late 90s
SDH and SONET (and TMN) evolve in parallel
PDH basics I A/D
A/D
64 kbit/s
BUT........
> different analog-to8 kHz / 8 bit
digital coding, and
> different multiplexing

of multiple channels
PDH basics II - Multiplexing
3 0 :1
m ux
6 4 k b it / s
4 :1
m ux
2 0 4 8 k b it / s
( " 2 M b it/s " )
4 :1
m ux
8 4 4 8 k b it / s
( " 8 M b it/s " )
4 :1
m ux
3 4 3 6 8 k b it / s
( " 3 4 M b it / s " )
4 :1
m ux
1 3 9 2 6 4 k b it/s
( " 1 4 0 M b it/s " )
( t o lin e
t e r m in a l)
5 6 4 9 9 2 k b it/s
( " 5 6 5 M b it/s " )
PDH basics III - Multiplexing

hierarchies
Hierarchy level
Hierarchical bit rates based on a first level of:

1 544 kbit/s
2 048 kbit/s
64 kbit/s
64 kbit/s
1 544 kbit/s
2 048 kbit/s
6 312 kbit/s
8 448 kbit/s
32 064 kbit/s
44 736 kbit/s
34 368 kbit/s
97 728 kbit/s
(note 1)
139 264 kbit/s
(note 2)
(-)
564 992 kbit/s
[Japan]
[North Am.]
[Europe plus...]
Note 1: equipment using proprietary rates, e.g. ~274 Mbit/s, have been seen.
Note 2: references to a line rate of (about) 400 Mbit/s has been seen.
PDH basics IV - Add/Drop

multiplexer
140/
34
34/
8
8/
2
2/
8
1 4 0 M b it / s
8/
34
34/
140
1 4 0 M b it / s
2 M b it / s
extensive asynchronous multiplexing/demultiplexing required

(lots of PLLs etc.)!
inflexible upgrading
limited/proprietary supervision (no management standards)
The network needs behind SONET
identified need for new/more cross-connect and add/drop functions, but

PDH multiplexing inflexible
identified need for more comprehensive management functions
(dynamic control, performance reporting, etc.)
(only fixed rate signals addressed by PDH)
Synchronous multiplexing !
Synchronous signal structure

Serial signal stream:
F
time
N
ROWS
B
2
Order of transmission
N x M Bytes
B
F denotes an 8-bit frame byte

B denotes an 8-bit signal byte
M
COLUMNS
SDH/SONET Add/Drop multiplexer
s y n c h ro n o u s
m u x /d e m u x
m ap/
dem ap
2 M b it / s
few asynchronous multiplexing/demultiplexing stages

very inflexible upgrading
comprehensive supervision (management standards)
{ Find the. - error(?) }
STM Frame (I) - The STM-1 frame

155.520 Mbit/s serial signal
F
125us
2430 bytes
1
9 bytes
9 bytes
9 bytes
9 bytes
9 bytes
9 bytes
9 bytes
9 bytes
9 bytes
3
261 bytes
261 bytes
261 bytes
261 bytes
261 bytes
261 bytes
261 bytes
261 bytes
261 bytes
9 bytes
261 bytes
Overhead
payload
9 BYTES + 261 BYTES = 270 BYTES 270 BYTES x 9 = 2430 BYTES

2430 BYTES/FRAME x 8 BITS/BYTE x 8000 FRAMES/SEC = 155.520Mbit/s
STM Frame (II)

- Multiplexing in the payload area
Over
head
(OH)
STM-1 frame:
Higher order
Virtual Container:
Payload
O
H
Payload
Lower order
Virtual Containers:
(Large) client signal
(mapped)
O Pay
H load
O Pay
H load
(Small) client signal

...
O Pay
H load
STM Frame (III) - The STM-N frame

one byte:
3
bit: 1 2
. . .
3
interleave depth no.
2
1
1
2
125 us
Order of
transmission
STM Frame (IV) - An STM-4 frame

example
125 us
1
2
> STM-N, N=4 => 622.08 Mbit/s

Sequence of
Transmission
STM Frame (V) - STM-N

multiplexing
STM-N frame:
Over
head
(OH)
Payload
Higher order
Virtual Containers:
2
1
O
O H
H
...
Payload
Payload
O
H
Payload
...
SDH signal hierarchy and line rates

Synchronous
Transport Module
Line Rate
Mbit/s
STM-1
155.520 (*)
STM-4
622.080 (**)
STM-16
2488.320
STM-64
9953.280
STM-256
39813.120
* Both electrical and optical interfaces

** Proprietary electrical interfaces
SDH Multiplexing structure, basic (ITU-T)
xN
STM-N
x1
AU-4
AUG
VC-4
x3
x1
TUG-3
x3
TU-3
C-4
139264 kbit/s
C-3
44736 kbit/s
34368 kbit/s
VC-3
x7
AU-3
VC-3
x7
TUG-2
x1
TU-2
VC-2
C-2
6312 kbit/s
TU-12
VC-12
C-12
2048 kbit/s
TU-11
VC-11
C-11
1544 kbit/s
x3
x4
Groups
Pointer processing
Multiplexing
Aligning
Mapping
Note: These are the

rates of the tributary
signals and not the
C-n capacities!
SDH Multiplexing structure, ETSI
xN
STM-N
x1
AUG
AU-4
VC-4
x1
x3 TUG-3
C-4
139264 kbit/s
TU-3
VC-3
C-3
44736 kbit/s
34368 kbit/s
TU-2
VC-2
C-2
6312 kbit/s
TU-12
VC-12
C-12
2048 kbit/s
VC-11
C-11
1544 kbit/s
x7
x1
TUG-2
x3
Groups
Pointer processing
Multiplexing
Aligning
Mapping
Real SDH !
SDH/SONET Cross-connect
(more)
STM-Ns
STM-N
(more)
STM-Ns
mux/demux/
cross-connect
STM-N
mapping
HO
mapping
LO
tributaries
Alignment of signals
Input signal at:
Port A:
Port B:
Port C:
Port D:
etc.
Common frame phase on all output signals:
Port A:
Port B:
etc.
note *)
Placing the HO VC in the STM-1

frame
Ideally:
Over
head
(OH)
In reality:
Over
head
(OH)
Overhead:
Pointer
P
O
H
(C-4)
P
O
H
(C-4)
Placing the HO VC in the STM-1 frame (II)
The AU-4:
AU pointer
P
O
H
(VC-4)
The AUG:
(AU pointer)
( SOH )
P
O
H
(VC-4)
Adjusting the pointer from input to output

AU-4 frame phase at input:
incoming
frame start
AU pointer
P
O
H
(C-4)
P
O
H
(C-4)
AU-4 frame phase at output:

outgoing
frame start
AU pointer
time
Rate adaptation: the pointer mechanism
(Overhead)
Pointer
(Overhead)
(Overhead)
Pointer
(Overhead)
Virtual Container
Positive pointer justification
Pointer
Virtual Container
Pointer
+1
Negative pointer justification
Pointer
Virtual Container
Pointer
-1
Placing LO VCs in the HO VC (I)

> Mapping of three TUG-3s into a (V)C-4:
1
TUG-3
1
TUG-3
1
TUG-3
(A)
(B)
(C)
A
1 B
2 C
3 A
1 B
2 C
3 A
1
1 2 3 4 5 6 7 8 9 10
FIXED STUFF
VC-4 POH
86
....
86
86
A
1 B
2 C
3 A
1 B
2 C
3
261
Placing LO VCs in the HO VC (II)

> Mapping a VC-3 into a TUG-3 (via TU-3):
86 Columns
Fixed stuff
H1
H2
H3
85 Columns
J1
B3
C2
G1
F2
H4
F3
K3
N1
VC-3 POH
TUG-3
VC-3
Placing LO VCs in the HO VC (III)

> Mapping VC-2, VC-12 and VC-11 into a TUG-3 (via TUG-2 and TUs):
86 Columns
TUG-2
TUG-2
TUG-3
TU-12
PTRs
Fixed stuff
Fixed stuff
TU-2
PTR
POH
(7 * TUG-2)
. ..
POH
POH
.......
VC-2
VC-12
VC-12
3 * VC-12 (or 4 * VC-11)

in 1 * TUG-2
Placing LO VCs in the HO VC (IV)

> Mapping a TU-2, TU-12 and TU-11 into a TUG-2:
Numbering of TUs: The (K,L,M) scheme

> TUs (LO VCs) are numbered by the so-called
(K,L,M) scheme, where:

> K is the number of the TUG-3, i.e. 1 to 3
> L is the number of the TUG-2, i.e. 1 to 7
> M is the number of the TU-12, i.e. 1 to 3 or
the number of the TU-11, i.e. 1 to 4.
> For TU-3, L=M=0
> For TU-2, M=0
> Examples:
> A TU-3 (VC-3) in the first TUG-3 is numbered; (1,0,0)
> The first TU-12 (VC-12) in the last TUG-2 in the last TUG-3 is numbered:
(3,7,1)
> The scheme can be augmented by including the number of the VC-4
in the STM-N frame so that any LO VC within the STM-N signal can
be unambiguously identified. Furthermore, in equipment you also
augment with port no. (in module), slot no., shelf and rack no.
TU multiframing (I)
> Each TU-12 frame consists of 4 columns of 9 rows,
i.e. 36 bytes in total per frame; correspondingly for the
TU-2 and TU-11 frames.
> Carrying a 2 Mbit/s payload requires at least 32 bytes.

> This would leave 4 bytes for a pointer, path overhead and
any mapping overhead;
too little!
> Hence a multiframe is defined.
TU multiframing (II)
Mapping of a 140 Mbit/s signal into STM-N

Payload 140 Mbit/s
Container-4
VC-4 POH
AU-4 PTR
AU-4 PTR
SOH
Logical association
Physical association
AUG
Container-4
VC-4
VC-4
AU-4
VC-4
AUG
AUG
STM-N
Mapping of a 2 Mbit/s signal into STM-N

Payload 2 Mbit/s
Container-1
VC-1 POH
VC-1
TU-1 PTR
TU-1 PTR
TU-1 PTR
TUG-2
AU-4 PTR
AU-4 PTR
SOH
AUG
Logical association
Physical association
VC-1
TUG-3
VC-4 POH
Container-1
TUG-3
TU-1
VC-1
TUG-2
VC-1
TUG-2
TUG-3
TUG-3
VC-4
AU-4
VC-4
AUG
AUG
STM-N
Exercise I SDH Multiplexing
Exercise:
Show the multiplexing structure for an STM-4 signal carrying:
- one 140 Mbit/s signal
- three 34 Mbit/s signals, and
- one hundred and twenty-six 2 Mbit/s signals
Exercise I - SDH Multiplexing; hints
x 4
STM-4
AUG
AU-4
AUG
...
AUG
...
AUG
...
VC-4
1 x 139264 kbit/s
Other blocks to use:

AU-4
VC-4
TUG-3
TU-3
VC-3
C-3
TUG-2
TU-12
VC-12
C-12
C-4
3x
34368 kbit/s
126 x
2048 kbit/s
Exercise I - SDH Multiplexing Solution
x 4
STM-4
AUG
AU-4
VC-4
AUG
AU-4
VC-4
AUG
AU-4
VC-4
AUG
AU-4
VC-4
C-4
x 3
x 3
x 3
TUG-3
TUG-3 x 7
TUG-3 x 7
TUG-2
TUG-2
x 3
x 3
1 x 139264 kbit/s
TU-3
VC-3
C-3
3x
TU-12
VC-12
C-12
63 x
2048 kbit/s
TU-12
VC-12
C-12
63 x
2048 kbit/s
34368 kbit/s
> Additional question: What if you only have 63 x 2 Mbit/s

(and the same # of 140 Mbit/s and 34 Mbit/s signals) ?
Exercise I - SDH Multiplexing Solution, part 2
> What if you only have 63 x 2 Mbit/s

(and the same # of 140 Mbit/s and 34 Mbit/s signals) ?
STM-4
x4
AUG
AU-4
VC-4
AUG
AU-4
VC-4
AUG
AU-4
VC-4
AU-4
AUG
or
x3
x3
TUG-3
TUG-3
x7
TUG-2
x3
1 x 139264 kbit/s
TU-3
VC-3
C-3
3x
TU-12
VC-12
C-12
63 x
34368 kbit/s
2048 kbit/s
1 x VC-4 Unequipped
or
1x
AU-4
AIS
C-4
VC-4
x
3
or
TUG-3
some
other
welldefined
signal
x
1
or
x
7
TUG-2
x
3
TU-3
1 x VC-3 Unequipped
TU-12
63 x VC-12 Unequipped
or
VC-m
some welldefined signal
OVERHEAD types and use
Basic overhead use

>
>
>
>
>
>
>
>
>
Alignment (e.g. framing)

Channel identification (trace identifier)
Bit error monitoring (e.g. parity)
Remote indications
Payload structure indication
Data channel
Auxiliary (data) channel
Protection signalling channel
... plus others depending on the layer
STM-1 Section overhead (SOH)

9 bytes
A1 A1 A1 A2 A2 A2 J0
B1
E1
F1
D1
D2
D3
Administrative Unit Pointer(s)
B2 B2 B2 K1
K2
D4
D5
D6
D7
D8
D9
D10
D11
D12
S1
M1 E2
261bytes
RSOH
Payload
MSOH
9 rows
RSOH = Regenerator section overhead
MSOH = Multiplexer section overhead
STM-1 overhead use

>
>
>
>
>
>
>
>
>
=> A1, A2
=> J0
=> B1, B2
Remote indications
=> M1, K2
=> ((H1, H2))
Data channel
=> D1-D3, D4-D12
Auxiliary user and data channels
=> F1, E1, E2
Protection signalling channel
=> K1, K2
... plus others depending on the layer
=> S1
STM-N SOH - example for STM-4
VC-4 Path overhead (POH)

column:
1
261
J1
B3
C2
G1
F2
payload area
H4
(261 columns x 9 rows)
F3
K3
N1
VC-12 Path overhead

V5
Multiframe #1
payload
area
J2
Multiframe #2
payload
area
N2
Multiframe #3
payload
area
K4
Multiframe #4
payload
area
byte 1
V5:
byte 35
BIP-2
REI (RFI)
RDI
byte 1
byte 35
byte 1
K4:
byte 35
(undefined)
byte 1
virtual concatenation OH
multiframe and extended signal label
byte 35
The multiframe is indicated by the VC-4 POH H4 byte (bits [7:8])

Signal Label
VC-n overhead use

VC-4, VC-3:
>
>
>
>
>
>
>
>
>
VC-12:
*)
(H1, H2)
(V1, V2, H4 )
J1
J2
B3
V5
Remote indications
G1
V5
Payload structure indication (signal label) C2
V5 (,K4)
Data channel
Auxiliary user and data channels
F2, F3
Protection signalling channel (APS)
K3
(K4)
... plus others depending on the layer and H4, N1

use
K4, N2
Definition of specific OH elements on the following slides
The Trail Trace Identifier (TTI)

> For SDH a 16-byte TTI format is defined:
> Inserted in bytes J0, J1, J2

> When unused J0/J1/J2 should contain all-ZEROes
Bit error monitoring; BIP-n

> B1, B2, B3 and V5[1:2] are used for Bit interleaved parity (BIP): BIP-8, BIP-24N, BIP-8
and BIP-2, respectively.
> BIP is even parity calculated over the relevant bits in the frame and inserted in the
next frame
> Bit interleaved means that for BIP-n n parity calculations done
in parallel
Bit error monitoring; BIP-8 in B1

> Example: B1 (BIP-8):
etc.
etc.
etc.
...
etc.
etc.
etc.
Bit error monitoring; BIP-24 in B2

etc.
etc.
etc.
...
etc.
Remote indications
> Remote Defect Indication (RDI):
> a bit (or code in more bits) is set in the frame(s) in the transmit
(source) direction, when a defect is detected in the receive (sink)
direction;
> the insertion continues while the defect is detected
> Remote Error Indication (REI):

> each frame the result of the bit error monitoring in the receive
(sink) direction is inserted in the transmit (source) direction
> the result inserted as REI is the number of BIP-n errors detected
Remote indication: MS REI

A received frame:
etc.
Next transmitted frame:
etc.
...
BIP-1 calculation
Next received frame:
B2
M1
comparison
... result
inserted
in M1
added to the result

of the other BIP-1
calculations, and...
Exercise II MS REI range
Exercise:
For STM-1 there are three B2 bytes, i.e. up to 3 * 8 = 24 BIP errors can
be detected per frame and inserted in the M1 byte in the return direction.
1) How many B2 BIP errors can be detected for an STM-16 signal ?
2) How many B2 BIP errors can be detected for an STM-64 signal ?
2.1) is this a problem ?
Exercise II MS REI range;

solution
B2 BIP error detection ranges:
STM-1:
3 * 8 = 24
STM-4:
4 * 3 * 8 = 96
STM-16:
16 * 3 * 8 = 384
> 255 !
STM-64:
64 * 3 * 8 = 1536
>> 255 !!
For STM-64 and above:
M0
(M1 is only one

(8 bit) byte!)
M1
}
16-bit range (64k) for REI

> Signal Label for VC-3 and VC-4 (C2 byte):
Payload structure indication (II)

> Signal Label for VC-12 (bit 5-7 of the V5 byte):
In K4[1]:
Synchronisation Status Message (SSM)

> SSM byte: S1[5:8]
Synchronisation networks
> (see separate slides, now or later)
Other overhead elements
> To be discussed as part of the MSP 1+1 and VCAT

presentations
Comparison of terms: SDH vs. SONET

SDH:
SONET:
STM-N frame
STS-N frame
Regenerator
SOH
AU pointer
Section
overhead
STM-N payload
Multiplexer
SOH
Section
overhead
(example)
VC-4 Virtual Container
STS-N Envelope Capacity

Line
overhead
Transport
overhead
Path overhead (POH)
Path overhead (POH)
Container C-4
STS
payload
pointer
(example)
STS-3c Payload Capacity
STS-3c Synchronous Payload

Envelope (SPE)
FG742.dsf
981026
Comparison of terms: SDH vs. SONET (II)

SDH:
SONET:
Synchronous Transport Module
Synchronous Transport Signal
STM-N frame
STS-N frame
Section overhead (Reg./Mux.)
Transport overhead (Sect./Line)
Administrative Unit (AU)
AU pointer
STS payload pointer
(HO) Virtual Container (VC)
Synchronous Payload Envelope (SPE)
(HO) VC Path overhead (POH)
STS Path overhead (POH)
Container
Payload capacity
Tributary Unit (TU)
(LO) Virtual Container (VC)
Virtual Tributary (VT)
TU Pointer
VT Payload Pointer
Suggested further reading:

ANSI T1.105 SONET standard ( - which includes cross-refs to SDH terms(!))
Bellcore specification GR-253-CORE (Section 3)
SDH Multiplexing structure, ANSI-T1

xN
x1
STM-N
"AUG"
"AU-3-3c"
"VC-3-3c"
C-4
139 264 kbit/s
C-3
44 736 kbit/s
33 368 kbit/s
x3
AU-3
VC-3
x7
TUG-2
x1
TU-2
VC-2
C-2
6 312 kbit/s
TU-12
VC-12
C-12
2 048 kbit/s
TU-11
VC-11
C-11
1 544 kbit/s
x3
x4
Groups
Pointer processing
Multiplexing
Aligning
Mapping
This is SONET
in SDH terms!
Multiplexing structure extensions (I)

> Contiguous concatenation (spelled out):
STM-256
AUG-256
AU-4-256c
VC-4-256c
C-4-256c
AU-4-64c
VC-4-64c
C-4-64c
AU-4-16c
VC-4-16c
C-4-16c
AU-4-4c
VC-4-4c
C-4-4c
STM-64
AUG-64
STM-16
AUG-16
STM-4
AUG-4
4
STM-1
AUG-1
AU-4
C-4
VC-4
3
STM-0
AU-3
TUG-3
TU-3
C-3
VC-3
7
7
1
TUG-2
AU-4
Pointer processing
Multiplexing
VC-3
TU-2
VC-2
C-2
TU-12
VC-12
C-12
TU-11
VC-11
C-11
3
4
Aligning
Mapping
Notice that this is the diagram including the SONET mux routes!
Concatenation, contiguous
Large client signal
Pointer
CI pointers
P
O Payload
H
Payload
Payload
contiguous concatenated VCs
=> VC-n-Xc
Payload
Multiplexing structure extensions (II)

Sub-STM-0 interfaces => G.708:
STM-64 1 AUG64
4
STM-16
AUG16
AU-4-16c
VC-4-16c
C-4-16c
AU-4-4c
VC-4-4c
C-4-4c
4
STM-4
AUG4
4
STM-1
AUG1
AU-4
C-4
VC-4
3
STM-0
AU-3
TUG-2n (**)
VC-3
C-3
VC-3
7
sSTM-2n (**)
TU-3
TUG-3
n (**)
7
1
TUG-2
TU-2
VC-2
C-2
TU-12
VC-12
C-12
TU-11
VC-11
C-11
3
sSTM-1k (*)
TUG- 1k (*)
k (*)
4
T1530320-99
Pointer processing
Aligning
Multiplexing
Mapping
SSTM-1k, 2n multiplexing routes
(*) k = 1, 2, 4, 8 and 16
(**) n = 1, 2 and 4
C-n Container-n
SDH Multiplexing structure, 1988(!)

AU-32
C-32
H22,
44736
kbit/s
VC-21
C-21
6312
kbit/s
VC-11
C-11
H11,
1544
kbit/s
C-4
139264
kbit/s
VC-12
C-12
H12,
2048
kbit/s
VC-22
C-22
8448
kbit/s
C-31
H21,
34368
kbit/s
VC-32
x7
TU-21
TU-32
x3
STM-N
xN
STM-1
x3
AU-4
TUG-21
x3
x21
x4
TU-11
VC-4
x16
x5
x5
x4
x4
TU-31
TUG-22
TU-12
x4
TU-22
x4
AU-31
VC-31
Alas, you didnt hear much about...

Optical interfaces
WDM
Tandem Connection Monitoring
Virtual Concatenation
=> and then again . see later slides!
Protection
=> see later separate slides!
Synchronisation
Timing, jitter & wander
The End (of part one, or of )
THE End THE FUTURE
The Future (II)
SDH will be around for a while, because of:

LARGE INSTALLED SDH BASE !!
Easier to extend existing network than to deploy all-new network !
A number of issues, notably in terms of supervision, not yet solved
for emerging technologies !
but an optical network (OTN) has been defined

and packet transport, e.g. Ethernet, is being defined!
The Future (III)
New/recent SDH extensions / upgrades:

Transport of data signals via Virtual concatenation !!
Mapping into OTN
Tandem Connection Monitoring(?)
Signalled path set-up (external request for capacity)
Functional
transport
modelling
Functional modelling - Overview I
The purpose of doing layer functional modelling is to:

get a concise overview of which information (signal) is present where
get a uniform description of like functions
support layered transmission network management
complement the layered management model
Functional modelling - Overview II

to /fro m S 4 _ T T o r M S n / S 4 _ A
S4
n /2
n /2
M S n /S 4
n /2
M S n /S 4
n /2
M Sn_AI
M S n /S 4
n /2
M S n /S 4
M Sn_AI
M SnP
2 fs h
M SnP
2 fs h
M SnP
2 fs h
M SnP_C I
M SnP_C I
M S nP
2 fs h
M SnP
2 fs h
M Sn/
M S n P 2 fs h
M SnP_CI
M S n /S 4
M Sn_AI
M S nP
2 fs h
M SnP
2 fs h
M SnP
2 fs h
M SnP_C I
M SnP
_CI
n /2
M S n /S 4
M S n P 2 fs h
SSF
SSD
APS
n /2
M S n /S 4
M Sn_AI
M S - S P R in g
s u b - la y e r
n /2
M S n /S 4
P
APS
M S n/
M S n P 2 fs h
M S nP
_C I
M Sn/
M S n P 2 fs h
TSF
TSD
SSF
SSD
APS
APS
M Sn/
M S n P 2 fs h
TSF
TSD
SD_CI
P 0s_C I
P 0s_C I
SD _C I
S D _C I
P 0s_C I
P 0s_C I
SD _C I
M S n /S D
M S n /P 0 s
M S n /P 0 s
M S n /S D
M S n /S D
M S n /P 0 s
M S n /P 0 s
M S n /S D
M SnP_AI
M Sn
M SnP_AI
M Sn
M Sn
M Sn
P r o t e c tio n
W est
W o r k in g
E ast
F G 6 2 3 .D R W
970509
Functional modelling - Overview III

Anomalies (#XXX), Defects (dXXX)
& Consequent Actions (aXXX):
Source
direction:
Fault Causes (cXXX) &

Performance Primitives (pXXX):
Management SET (sXXX), GET (gXXX)

& ACTION (aXXX) operations:
Sink
direction:
CI_SSF
1)
Notes:
0) If the MSn/S4_A source function is not connected to another
atomic function, then an S4 UNEQ signal must be input to the

MSn/S4_A source function instead
0)
2)
diRMSFail
=> MS-AIS
aSSF <= dAIS or dLOP

aAIS <= dAIS or dLOP
dAIS
dLOP
MSn/S4
1) CI_SSF = true:
cAIS <= dAIS and (sAIS_Reported = enable) and (not AI_TSF)

cLOP <= dLOP and (not AI_TSF)
- if the MSn/S4_A source function is connected to an adaptation

sink function with aSSF = true as output, or
- if the MSn/S4_A source function is connected to a port on the
S4_C function, which is having AIS forced;
otherwise, CI_SSF = false.
sAIS_Reported [enable, disable]

sConc_auto_mode [enable, disable]
gConc_status [normal, concatenated]
aTSF <= dAIS or (dEXC and (sEXC_consequent_actions = enable))

aAIS <= dAIS or (dEXC and (sEXC_consequent_actions = enable))
CI_SSF => aAIS
dAIS
dEXC
dDEG
dRDI
#EDCV(N)
#EDCV(F)
MSn
aTSF => aRDI
#EDCV(N) => aREI
aSSF <= AI_TSF
RSn/MSn
cAIS <= dAIS and MON and (not CI_SSF)

cEXC <= dEXC and MON and (not CI_SSF)
cDEG <= dDEG and MON and (not CI_SSF)
cRDI <= dRDI and (sRDI_Reported = enable)
and MON and (not CI_SSF)
pN_DS <= aTSF or dEQ
pN_EBC <= nN_B (#EDCV(N))
pF_DS <= dRDI
pF_EBC <= nF_B (#EDCV(F))
dTIM 3)
dDEG
#EDCV(N)
AcTI
RSn
cTIM <= dTIM and MON and (not CI_SSF)

cDEG <= dDEG and MON and (not CI_SSF) and (not dTIM)
pN_DS <= CI_SSF or dTIM or dEQ
dLOF
aTSF <= dLOS
OSn
'diRMSFail' is an equipment defect which can be detected at a

module interface, refer to [ETS 05] and [ETS 03]
sRDI_Reported [enable, disable]
gSTM_level [n]
sExpected_TTI [16-bytes, NULL]
3) A NULL value for sExpected_TTI implies that
gAccepted_TTI [16-bytes, NULL] (~ AcTI)
the 'dTIM' defect detection shall be suppressed
sTransmitted_TTI [16-bytes, NULL] (~ TxTI)
sSignal_degrade_threshold [1E-5, -6, -7, -8, -9, -10]
sTermination_point_mode [MON, NMON]
sTIM_consequent_actions [enable, disable]
aSSF <= dLOF or AI_TSF

aAIS <= dLOF or AI_TSF
OSn/RSn
2)
gSTM_level [n]
aTSF <= (dTIM and (sTIM_consequent_actions = enable)) or CI_SSF

aAIS <= (dTIM and (sTIM_consequent_actions = enable)) or CI_SSF
TxTI
gSTM_level [n]
sEXC_consequent_actions [enable, disable]
cLOF <= dLOF and (not AI_TSF)
gSTM_level [n]
cLOS <= dLOS and MON
sLOS_aTSF_extension [enable, disable]

gSTM_level [n]
sPort_mode [MON, NMON, AUTO]
4)
dLOS
4) sLOS_aTSF_extension determines whether the 'aTSF'
consequent action shall be extended (enable) or not (disable)

for 3s after 'dLOS' has cleared.
5) the 'aLaserActive' consequent action is described in
the section 'Laser Control Process'
aLaserActive 5)
Source
direction:
Sink
direction:
Figure 2-1/[Common ETS 04]: TTF-n (Optical) Compound Function (n = 1, 4, 16, 64)
Functional modelling - Overview IV
Figure 5-5/G.806:
Example of SDH equipment
functional specification
Functional modelling - Building the model I

Wanted:
transfer of information (a signal)....
from here....
.... to here
Functional modelling - Building the model II
add overhead for

supervision....
.... and check that the signal

was transferred correctly
Trail
in a trail
termination
source function
in a trail
termination
sink function
transfer the signal via a topological

component called a connection
Functional modelling - Building the model III

Maybe some packaging, rate adaptation, multiplexing,
etc. of the carried payload signal is required....
.... that is done in the adaptation function
Trail
Functional modelling - Building the model IV

Layers may now be put on top of each other....
two individual
signals...
... are multiplexed
Functional modelling - Building the model V

... but maybe they do not have the same final destination:
Trail
Trail
Trail
Trail
Functional modelling
- the Trail Termination function
Used for integrity supervision of the transferred signal
In the source end there may be added:
In the sink end there may be detected for:
error detection code
loss of signal
trail trace identifier
server signal fail / AIS
remote (bit) error indication signal
misconnection
remote defect indication signal
bit errors
all in the overhead (OH)!

far-end performance
- the Adaptation function
Represents conversion processes between the client
layer and the server layer
Processes that may be present in the adaptation function:
scrambling/descrambling
encoding/decoding
alignment (FAS/PTR generation, framing, pointer interpretation)
bit rate adaptation
frequency justification
multiplexing/demultiplexing, including inverse multiplexing
timing recovery
smoothing
payload identification
only some of these uses OH!
- the Connection function
Used for routeing and protection processes
Connection types may be:
unidirectional connections
bidirectional connections
broadcast connections
bridge connections (protection source end)
conditionally switched (protection sink end)
When used for protection the Connection function may also include an APS processor
this uses OH but inserted via the server adaptation function

Functional modelling - Practical example I

SSF
Mention:
Alarm disabling
(eventually in
separate slide):
RS-TIM, MS-AIS,
AU-AIS, S4-UNEQ,
etc.
All ONEs (AIS) insertion and propagation in the sink direction in case of STM1dLOF
Functional modelling - Practical example II

'1'
'1'
aSSF
MS1/S4
'1'
plus AIS pointer
other adaptation
functions
MS1
AU4dAIS
aSSF
MS1/S4
H1
'1'
MSOH
RS1/MS1
MSOH
'1'
MS1
'1'
RSOH
H2
RS1
'1'
other adaptation
functions
MSOH
RS1/MS1
RS1
RSOH
'1'
MSOH
All ONEs (AIS) generation in the source and detection in the sink direction
Functional modelling - Practical example III

Anomalies (#XXX), Defects (dXXX)
& Consequent Actions (aXXX):
Source
direction:
Fault Causes (cXXX) &

Performance Primitives (pXXX):
Management SET (sXXX), GET (gXXX)

& ACTION (aXXX) operations:
Sink
direction:
CI_SSF
1)
Notes:
0) If the MSn/S4_A source function is not connected to another
atomic function, then an S4 UNEQ signal must be input to the

MSn/S4_A source function instead
0)
2)
diRMSFail
=> MS-AIS
aSSF <= dAIS or dLOP

aAIS <= dAIS or dLOP
dAIS
dLOP
MSn/S4
1) CI_SSF = true:
cAIS <= dAIS and (not AI_TSF) and (sAIS_Reported = enable)

cLOP <= dLOP and (not AI_TSF)
- if the MSn/S4_A source function is connected to an adaptation sink

function with aSSF = true as output, or
- if the MSn/S4_A source function is connected to a port on the S4_C
function, which is having AIS forced;
otherwise, CI_SSF = false.
sAIS_Reported [enable, disable]

sConc_auto_mode [enable, disable]
gConc_status [normal, concatenated]
aTSF <= dAIS or (dEXC and (sEXC_consequent_actions = enable))

aAIS <= dAIS or (dEXC and (sEXC_consequent_actions = enable))
CI_SSF => aAIS
dAIS
dEXC
dDEG
dRDI
#EDCV(N)
#EDCV(F)
MSn
aTSF => aRDI
#EDCV(N) => aREI
aSSF <= AI_TSF
RSn/MSn
cAIS <= dAIS and MON and (not CI_SSF)

cEXC <= dEXC and MON and (not CI_SSF)
cDEG <= dDEG and MON and (not CI_SSF)
cRDI <= dRDI and MON and (not CI_SSF)
and (sRDI_Reported = enable)
pF_DS <= dRDI
pF_EBC <= nF_B (#EDCV(F))
dTIM 3)
dDEG
#EDCV(N)
AcTI
RSn
cTIM <= dTIM and MON and (not CI_SSF)

cDEG <= dDEG and MON and (not CI_SSF) and (not dTIM)
dLOF
aTSF <= dLOS
OSn
'diRMSFail' is an equipment defect which can be detected at a

module interface, refer to [ETS 05] and [ETS 03]
sRDI_Reported [enable, disable]
gSTM_level [n]
sExpected_TTI [16-bytes, NULL]
3) A NULL value for sExpected_TTI implies that
gAccepted_TTI [16-bytes, NULL]
(~ AcTI)
the 'dTIM' defect detection shall be suppressed
sTransmitted_TTI [16-bytes, NULL] (~ TxTI)
sTIM_consequent_actions [enable, disable]
aSSF <= dLOF or AI_TSF

aAIS <= dLOF or AI_TSF
OSn/RSn
2)
gSTM_level [n]
aTSF <= (dTIM and (sTIM_consequent_actions = enable)) or CI_SSF

aAIS <= (dTIM and (sTIM_consequent_actions = enable)) or CI_SSF
TxTI
gSTM_level [n]
sEXC_consequent_actions [enable, disable]
cLOF <= dLOF and (not AI_TSF)
gSTM_level [n]
cLOS <= dLOS and MON
sLOS_aTSF_extension [enable, disable]

gSTM_level [n]
sPort_mode [MON, NMON, AUTO]
4)
dLOS
4) sLOS_aTSF_extension determines whether the 'aTSF' cons. action
shall be extended (enable) or not (disable) for 3s after 'dLOS' has

cleared.
5) the 'aLaserActive' consequent action is described in
the section 'Laser Control Process'
aLaserActive 5)
Source
direction:
Sink
direction:
Figure 2-1/[Common ETS 04]: TTF-n (Optical) Compound Function (n = 1, 4, 16, 64)
Relevant Standards
Key standards - I
Transport:
ITU-T
ETSI
G.707
(ETS 300 147)
G.783, G.806
ETS 300 417-series
G.805, G.803
(ETS 300 417-1-1)
G.703
(ETS 300 166)
G.957, G.691, G.692
(ETS 300 232)
G.810 - 813
ETS 300 462-series
G.825
(no equivalent)
G.841, G.842
TS 101 009 / ...010

EN 300 746
Key standards - II
Management:
ITU-T
ETSI
G.784
ETS 300 417-7-1
G.774
(ETS 300 304)
M.2100-series
M.3000-series
X.700-series
But there are many, many more!
Key standards - III

Relevant standards organisations:
ITU-T
ETSI
ANSI-T1 ATIS
ISO/IEC
IETF
IEEE
Fora (TMF, OIF, MEF, etc.)
But also Operators specifications and regional/

national standards are important!
Finding the standards

Main (internal) source of material:
The
Standards Library
Which is:
web based =>
http://dkbawww01.dk.tellabs.com/webdata/se/PPSE_web/Standardisation/pages/Overview.html
the Standards file area on DKNTFS03 ( \\DKNTFS03\groups\LIB\STANDARD\ )

( a collection of (still) paper-based material ( B.3.2.22 ) )
( the Product Planning & Systems Engineering Bulletin Board
( in an Outlook Exchange Public Folder ) )
Suggested further reading

Broadband networking: ATM, SDH and SONET
Mike Sexton & Andy Reid (Artech, 1997)
SDH Telecommunications Standard Primer (Tektronix)
( - HTML and PDF versions)

[ http://www.tek.com/Measurement/cgi-bin/framed.pl?Document=
+ notes(!)
/Measurement/App_Notes/sdhprimer/&FrameSet=communications ]
Acterna (prev.: W&G): SDH Pocket Guide
[ http://www.acterna.com/global/products/descriptions/ANT/
ant_documentation_pocketguides.html ]
An Introduction to SONET (Nortel, PDF-file)
+ notes(!)
[ http://www.nortelnetworks.com/products/01/sonet/collateral/sonet_101.pdf
]
G.707:2000
G.806:2000
G.783:2000
see => the SDH-intro page on PPSEweb
Beware of: GN-Elmi SDH brochure -> outdated(!)

Suggested further reading (II)

Next Generation SDH/SONET : Evolution or Revolution
Huub van Helvoort (John Wiley & Sons, 8 April 2005)
SDH/SONET Explained in Functional Models

Huub van Helvoort (John Wiley & Sons, 14 October 2005)
Additional links
> All PP&SE documents are available via (links in) the PP&SE intranet
web page(s) at:
http://dkbawww01.dk.tellabs.com/webdata/se/PPSE_web/index.html
> A database of acronyms and abbreviations used in Tellabs-DK internal

specifications is found via the PP&SE pages or directly at:
http://esw-web1/esw/Abbreviations/Default.php
> What is function descriptions (like Concatenation) are found at:

http://dkbawww01.dk.tellabs.com/webdata/se/PPSE_web/Documents/pages/
hatis_index.htm
(i.e. via Documents, Product Feature Tutorials in the index for the PP&SE web pages)
> Tellabs 6325 Edge Node FP 1.1 documents are found via :
http://dkbawww01.dk.tellabs.com/webdata/se/Documents/pages/6325_FP11_
Documents.html

02 - SDH Introduction

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

02 - SDH Introduction

Загружено:

Авторское право:

Доступные форматы

Introduction to SDH

Module of SDH and 6325 FP 1.1 Training (KTI)

> The End (of part one, or of.)

SDH intro, 060320.ppt

Development of the Synchronous Optical NETwork

Digitally based telephony transmission systems

First international Synchronous Digital Hierarchy

SDH intro, 060320.ppt

PDH basics I A/D

digital coding, and

> different multiplexing

SDH intro, 060320.ppt

PDH basics II - Multiplexing

SDH intro, 060320.ppt

PDH basics III - Multiplexing

Hierarchical bit rates based on a first level of:

139 264 kbit/s

564 992 kbit/s

SDH intro, 060320.ppt

PDH basics IV - Add/Drop

extensive asynchronous multiplexing/demultiplexing required

SDH intro, 060320.ppt

The network needs behind SONET

identified need for new/more cross-connect and add/drop functions, but

SDH intro, 060320.ppt

Synchronous signal structure

F denotes an 8-bit frame byte

SDH intro, 060320.ppt

SDH/SONET Add/Drop multiplexer

few asynchronous multiplexing/demultiplexing stages

STM Frame (I) - The STM-1 frame

9 BYTES + 261 BYTES = 270 BYTES 270 BYTES x 9 = 2430 BYTES

STM Frame (II)

(Small) client signal

STM Frame (III) - The STM-N frame

interleave depth no.

SDH intro, 060320.ppt

STM Frame (IV) - An STM-4 frame

> STM-N, N=4 => 622.08 Mbit/s

STM Frame (V) - STM-N

SDH intro, 060320.ppt

SDH signal hierarchy and line rates

* Both electrical and optical interfaces

SDH Multiplexing structure, basic (ITU-T)

Note: These are the

SDH Multiplexing structure, ETSI

SDH intro, 060320.ppt

SDH intro, 060320.ppt

Placing the HO VC in the STM-1

SDH intro, 060320.ppt

Placing the HO VC in the STM-1 frame (II)

SDH intro, 060320.ppt

Adjusting the pointer from input to output

AU-4 frame phase at output:

Rate adaptation: the pointer mechanism

SDH intro, 060320.ppt

Positive pointer justification

SDH intro, 060320.ppt

Negative pointer justification

SDH intro, 060320.ppt

Placing LO VCs in the HO VC (I)

SDH intro, 060320.ppt

Placing LO VCs in the HO VC (II)

SDH intro, 060320.ppt