Transport Network Protection
Transport Network Protection
Alberto Bellato CTO Technology and architecture Optical Networks Division ALCATEL Vimercate
Content
>
>
> > > >
Content
>
>
> > > >
>
>
Intermediate nodes
>
>
Intermedia te nodes
OH OH OH
OH
OH
OH
Content
>
>
> > > >
A transport network should provide a mean for a secure traffic delivery between different sites Need to provide a mechanism able to minimize as much as possible the impact of events that may cause the interruption of the service
>
Note that this is different from network security, where there is the need to protect data from external attacks
CONNECTOR FAILURE
CONNECTOR DEFECT
NODE FAILURE
HARDWARE FAILURE
OPTO-ELECTRONIC DEVICE FAILURE POWER SUPPLY FAILURE
SPLICE FAILURE
VIBRATION CRAFT DEFECTS
Content
>
>
> > > >
Network Topologies
Ring Based
Mesh Based Linear
Eventual closure
Ring Based
Linear Eventual
closure
PROTECTION
Protection is a method for the traffic recovery, considered as high priority traffic (Normal traffic) , usually associated to a fast process where the Network Elements (NE) autonomously decide when to act (selfhealing). The protection algorithm is implemented and handled by NEs The protection application makes use of preassigned capacity between nodes (protection transport entity) The alternative path used for traffic recovery, has a either a predefined routing or it is allocated through predefined links Protection transport entity can carry low priority traffic (Extra Traffic) when not in switching condition
Protection application
H G I F A
Working circuit path: GFHIL Failure on section: HI Predefined alternative path (protection path) on GEABL Protection transport entity can be used for the transport of low riority traffic (depending
on the specific protection scheme)
RESTORATION
Restoration is a method for the traffic recovery, usually associated to a slower process, where the switching decision is taken by a Network Management System (NMS) which can be either centralized or distributed through the network. The restoration application makes use of any capacity available between nodes, depending on failure scenario and on traffic matrix The restored path doesn't have a unique predefined routing.
Restoration Application
H G I
F
A
Working circuit path: GFHIL Failure on section: HI NMS decides optimum routing (e.g. GFABIL) among possible alternative paths
(e.g. GEDCL or GFAIL or GFEABL)
Network Topologies
Eventual closure
Content
>
>
> >
>
>
AP
TCP
Sub-network
TCP
AP
AP
TCP
Sub-network
TCP
AP
Layer a Trail
Trail Protection
Intermediate nodes
AP
TCP Sub-network
CP Sub-network
CP Sub-network
TCP
AP
SNC Protection
Intermediate nodes
Architecture Mode
Redundant: Normal Traffic is bridged permanently on working/protection resources Extra Traffic is not supported
End 1 Working
(wk)
End 2
Normal Traffic
Protection (pr)
+ (1 wk + 1 pr)
Shared: Normal Traffic is usually connected to working resource bridge occurs only when protection is required Extra Traffic may be carried by protection resource (when no requested for protection)
End 1 Working
(wk)
End 2
Protection (pr)
: (N1 wk : M pr)
Switching Mode
End 1 Working
(wk)
End 2
Protection (pr)
Each end switches independently on the base of switching criteria locally detected
End 1
Working (wk)
End 2
Both ends, on the base of switching criteria detected, perform bridge & switch triggered by protocol exchange message (Automatic Protection Switching signalling) over protection transport entity
End 1
End 2
End 2
Operation Mode
In revertive operation mode, the traffic signal always returns to the working transport entity, when it has recovered from the defect or the external request is cleared (revertive operation is handled either unidirectionally or bidirectionally consistently to the switching mode of the protection scheme) Revertive unidir
End 1 Working End 2 End 1
Revertive bidir
Working End 2
Protection
In non-revertive operation mode, the traffic signal does not return to the working transport entity, once the defect or the external request affecting working resource has been removed.
The revertive operation mode is applicable both in case of protection resource dedicated to a working resource and in case of protection resource shared among different working transport entities. The revertive mode is appropriate when: the protection resource capacity is required to restore other traffic signal, due to more
urgent need (e.g., protection scheme with shared protection transport entity) the protection resource may be subject to frequent re-arrangement (e.g. where a network has limited capacity and protection routes are frequently re-arranged to maximize network efficiency when changes occur in the network) the protection resource is of significantly lower performance than the working resource (e.g. where the protection transport entity has a worse error performance or longer delay than the working transport entity) an operator needs to know which transport entities are carrying normal traffic in order to simplify the management of the network
Content
>
>
> >
>
>
Hardware (fpga usually) or Software tasks resident into the Network Element able to process input parameters and providing output actions according to the specific protection algorithm
IN DETAILS
EXTERNALLY INITIATED COMMANDS
Available commands allowing the operator to control protection algorithm, by forcing, pre-empting or testing the switching status
Signal Fail All the defect conditions producing the unavailability of the traffic to be protected at the interested layer Signal Degrade
Error condition affecting traffic to be protected at the interested layer, over a specific threshold set by operator (not necessarily producing a unavailability)
Exercise (#n) emulates a switch request (for Normal Traffic #n) without performing any actual switch action, unless the protection transport entity is being used
Clearing previous external command (not addressable by other specific clear command) Clear clears all the switch commands Freeze the protection process (commands under standardization) Freeze the current state of the Protection Algorithm Controller (mainly thought for checking the APS protocol exchange for APS Controller) Clear Freeze clears the Freeze command and allows the Protection Algorithm Controller to evolve on the base of current inputs state
A. Bellato CTO T&A Team - OND 36
Hold-Off Time
Time interval after the detection of a SF or SD and its confirmation as a condition requiring the protection switching procedure
Time
Network Impairment
SF SD trigger
Content
>
>
> >
>
>
Linear protection architecture is applicable to both linear and ring network topology: only End nodes performs a protection activity, due to the resident Protection Algorithm Controller
N.T.
NE 1
P.A.C.
Intermediate node performing traffic cross-connection and alarm (defects / errors) propagation
P.A.C.
NE 3
(Pr) (Wk)
NE 1 NE 3
(Pr)
(Wk)
NE 4
NE 4
NE 2
P.A.C.
NE 2
P.A.C.
N.T.
N.T.
Intermediate nodes performing traffic crossconnection and alarm (defects / errors) propagation
(Wk)
(Pr)
N.T.
(Wk)
Working and Protection resources carried into the same transmission mean (e.g. fiber / )
N.T.
P.A.C.
NE 1
P.A.C.
NE 1
P.A.C.
P.A.C.
NE 3
NE 4
NE 3
NE 4
P.A.C.
NE 2
P.A.C.
NE 2
Working and Protection resources carried into dedicated transmission means (e.g. fiber / )
P.A.C.
N.T.
N.T.
SPRing protection architecture is also applicable to meshed network topology, whenever a closed connection of NEs (i.e. a ring) is identified through the network: again, every node of the ring, performs a protection activity, due to the resident Protection Algorithm Controller
N.T.
Content
>
>
> > >
Linear Ring
>
Protection Algorithm
1+1 1:N M:N
Switching Operation
unidir / bidir unidir / bidir bidir
NE 1 1+1 scheme
Protection (Pr)
NE 2
Cross-connection matrix
1 protection resources dedicated to 1 working resource only Normal Traffic connected (Extra Traffic on protection res. NOT supported) through permanent bridge on the two communication resources (wk/pr) traffic data switched (selected) on the base of switching criteria detected
A. Bellato CTO T&A Team - OND 45
1 + 1 unidir algorithm - I
NE 1
N.T.
(Wk)
NE 2 Protection activity NE 1
(Pr) Switching criterion declaration No Action
NE 2
TAL
Switch Unidirectional Switch completed
[Time]
[Time]
NE 1
N.T.
(Wk)
Switch
NE 2
TAL algorithm evolution time
(Pr)
In non-revertive systems, new switch status is kept also after failure/degrade/command removal from working resource
1 + 1 unidir algorithm - II
Failure/Degrade condition removed from working resource WTR timer starts
Switch present until WTR timer expiring
NE 1
N.T.
(Wk)
NE 2 NE 1
Protection activity NE 2
Failure / Degrade removal Switch
(Pr) No Action
W.T.R. (Switch)
Revert Revert switch on main performed
[Time]
[Time]
NE 1
N.T.
(Wk)
NE 2
W.T.R. timer expiring
(Pr)
At WTR timer expired, starting connectivity re-established (revert switch on working main resource)
1 + 1 bidir algorithm - I
Protection activity NE 1
N.T.
(Wk)
NE 2 NE 1
Switching criterion declaration
NE 2
TAL
(Pr)
Protocol message along protection resource (No Request code) Request Type, Channel identifier
(Bridge)
TAL
(Bridge)
Reverse Request, Channel bridged
TAL
NE 1
N.T.
(Wk)
Switch
NE 2
Switch
Switch
TAL
Bidirectional Switch completed
[Time]
In non-revertive systems, new switch status is kept also after failure/degrade/command removal from working resource, Do Not Revert code is signaled
1 + 1 bidir algorithm - II
Failure/Degrade condition removed from working resource WTR timer starts at tail end
Protection activity NE 2 NE 1
Head end
Failure / Degrade removal
Wait To Restore, Channel bridged Reverse Request, Channel bridged
NE 1
N.T.
(Wk)
NE 2
Tail end
W.T.R.
(Bridge) Switch Revert
Revert
No Request
NE 1
N.T.
(Wk)
NE 2
(Pr) As soon as WTR timer is expired, starting connectivity is re-established on both ends through, No Request code.
Normal Traffic #1 (High Priority) Normal Traffic #n (High Priority) Extra Traffic (Low Priority)
Protection (Pr)
NE 1 1:N scheme
1 protection resource shared among N (1) working resources
NE 2
implicitly bidirectional; protocol exchange along the protection resource the amount of working resources (N) handled, and, consequently, of the Normal Traffics protected, depends on the characteristics of protocol supported (nr of bits/bytes dedicated into signaling) both bridge and switch connections performed on the base of protocol algorithm activation either Null Signal (no meaningful traffic connected) or Extra Traffic (low priority traffic) can be connected to protection resource when protection activity is not required
1 : N bidir algorithm - I
N. T. #1
Working (Wk) No Request code on protocol and E.T./ Null Signal connected on pr)
N. T. #n
Protection (Pr)
E. T.
Bridge
Switch
N. T. #1 recovered
Working (Wk)
Protection (Pr)
1 : N bidir algorithm - II
Br&Sw and E.T. squelching present at both ends until WTR timer expiring
Failure/Degrade condition removed from working resource WTR timer starts at tail end
N. T. #1 recovered
Working (Wk)
Protection (Pr)
N. T. #1
As soon as WTR timer is expired, starting connectivity is reestablished on both ends through protocol Working (Wk)
N. T. #n
Protection (Pr)
E. T.
NE 2
NE 1
Head end
Failure / Degrade removal
Wait To Restore, Channel bridged Reverse Request, Channel bridged
NE 2
Tail end
TAL
Request Type, Channel Identifier
E.T. sq.
W.T.R.
Bridge & Switch Release Switch
TAL
E.T. sq. Bridge
Reverse Request, Channel bridged
TAL
Request Type, Channel bridged
Release Switch Bridge E.T. / N.S. on protection Switch E.T. / N.S. on protection
Switch
TAL
Bidirectional Switch completed
[Time]
TAL algorithm evolution time
[Time]
[Time]
NE 2
N.T.
E.T.
(Pr)
Request Type, Channel Identifier
E.T.
NE 1
N.T.
(Wk)
NE 2
N.T.
E.T.
(Pr)
Request Type, Channel Identifier
E.T.
Request Type from NE2 processed Bridge performed at NE1 (but Switch not performed yet at NE2) transient misconnection between N.T. and E.T. in the direction NE1 > NE2
NE 2
N.T.
Reverse Request from NE1 processed Switch performed at NE2 initial misconnection removed; Bridge performed at NE2 (and Switch not performed yet at NE1) new transient misconnection between N.T. and E.T. in the direction NE2 > NE1
E.T.
(Pr)
Reverse Request, Channel bridged
E.T.
NE 1
N.T.
(Wk)
NE 2
N.T.
Request Type from NE2 processed Switch performed at NE1 new misconnection removed;
E.T.
(Pr) Switch
Request Type, Channel bridged
E.T.
Content
>
>
> > >
Linear Ring
>
Protection Algorithm
1:1 2F/4F classic
Switching Operation
bidir
1:1
4F transoceanic bidir
N.T. E.T.
Protection (Pr)
In 2F topology, same transmission mean (fiber / ) carries both working and protection resources. If N is total number of resources (channels) available as ring line capacity, then:
NE 1
E W
NE 4
W E
NE 2
E
In 4F topology, dedicated transmission mean (fiber / ) carries either working or protection resources. If N is total number of resources (channels) available as ring E.T. line capacity, then:
E.T.
NE 3
Each side of a node interfacing the ring is conventionally named West/East Each node of the ring is involved in protection activity (protocol handling, matrix configuration). Protocol message exchange always occurs between adjacent nodes along protection resources
N.T. E.T.
IDLE state
In Idle state (no protection required through the ring), N.T. is on working resources, E.T. may be configured on protection resources. Protocol signaling carries No request code from each node to the adjacent one
NE 1
Working resource x Bridge
NE 4
Switch P.T.
NE 2
NE 3
PATH
LONG
Full Pass-through Macro-state entered by each node of the ring (not switching), by-passing bridge request not destined to itself; performing also the bidirectional by-pass (EW, W E) of protection resources (Low Priority channels). Pass-through nodes are also called intermediate nodes.
In classic application (2F/4F) the protection path corresponds always to the LONG path of the scheme: the propagation delay for the protected traffic is, then, always maximized. When applied to huge rings including transoceanic links or via satellite links, and depending on the type of service transported, this delay can lead to a final performance degradation of the service
E.T. squelched
Switch Bridge
NE 1
Bridge P.T.
NE 4
Switch P.T.
NE 2
NE 3
PATH LONG
In transoceanic application (4F) the protection path in ring switch condition, corresponds to the LONG path of the scheme only when the protected Normal Traffic is configured between adjacent nodes. With different traffic distribution (where node pass-through occurs) the protection path is limited to the portion of the ring, not fault affected, between nodes terminating the protected Normal Traffic.
Switch
NE 1
Bridge
Pass-through
NE 4
Switch Bridge
NE 2
E.T. squelched
NE 3
PATH
Temporary squelching, if associated LP channels are not required for ring switch connectivity
LONG
Ring Switch, in 4F topology occurs anytime a failure/degrade affects at least two out of four transmission means of a span, in such a way that both one working and one protection resources results fault affected or when a ring command is applied on that span. As for 2F ring, Normal Traffic is recovered through protection resources on the LONG path. In classic (also called terrestrial) application, same behaviour already described about 2F ring, same E.T. squelching policy and same node macro-states apply. In transoceanic application, current standard reference (SDH) states that during ring switch all the Extra Traffics configured through the ring are squelched; after the ring switch is performed, those Low Priority channels not used for Normal Traffic protection are re-connected to Extra Traffic. This is a slow process possibly using communication channels between the nodes of the ring, i.e. control plane, for E.T. re-configuration (protection protocol independent). Both distributed ring switch and Extra Traffic recovery is applicable, due to the knowledge of the whole ring connectivity at each node of the ring (see Traffic Map). The following node macro-states are entered during protection activity:
previous example).
Full Pass-through Macro-state entered by each node of the ring (not switching), by-passing bridge request not destined to itself. The same protocol specified in classic application is used. Pass-through nodes performs ring Bridge&Switch only when adding/dropping (terminating) Normal Traffic to be protected on the base of APS signaling received by both switching nodes; otherwise, they realize the bidirectional by-pass (EW, W E) of protection resources (Low Priority channels). Passthrough nodes are also called intermediate nodes (see grey nodes in previous example).
N.T. recovered
PATH
SHORT
E.T. squelched
NE 1
Bridge
E.T. squelched
NE 2
E.T. kept
NE 4
Switch
K - pass-through
NE 3
PATH
LONG
The protection path corresponds always to the SHORT path of the scheme: i.e. Normal Traffic is recovered through the same span along protection resource.
During span switch (both classic and transoceanic applications) all the Extra Traffics configured in the span fault affected are squelched; while remaining E.T. allocated in different spans of the ring are kept. In transoceanic application, those L.P. channels not required for span switch connectivity, then the associated E.T., are restored after span switch is performed (same way already described for ring switch).
The following node macro-states are entered during protection activity: Switching Macro-state entered by end node of the span interested with switching criteria, initiating a span switch by sending (tail end) to the adjacent switching node, both on the LONG and on the SHORT path of the ring a span bridge request, or acknowledging (head end) , both on LONG/SHORT path, a span bridge request destined to itself. Only switching nodes performs span Bridge&Switch (see yellow nodes in the example). K byte Pass-through Macro-state entered by each node of the ring (not switching), by-passing bridge request sent on the LONG path by switching node. The same protocol specified in classic application is used. K byte Pass-through nodes do not perform any reconfiguration of local connectivity. K-byte Pass-through nodes are also called intermediate nodes. (see grey nodes in the example)
A. Bellato CTO T&A Team - OND 69
NE 1
Span Br&Sw
NE 4
E.T. squelched on adjacent span
NE 2
NE 3
Same Protection channel accessed by switching nodes (NE1-NE3) through Ring Br&Sw with no squelching policy, permanent misconnection produced between N.T. #1 and N.T. #2
N.T. #2
NE 1
E W
N.T. #1 NE 4
W E Pr CH. #x+ N/2
NE 2
E
N.T. #2
NE 3
W Wk CH. #x
N.T. #2
Misconnection avoided through Low Priority channel squelching (AIS injection) at switching nodes
SNC vs SPRing
Up to 2xN paths N/2 wk resources N/2 wk resources N/2 wk resources N wk resources Up to N paths
Total N paths
N/2 wk resources
WITH ADJACENT TRAFFIC ALLOCATION THE PROTECTION SCHEME WITH MOST PROFITABLE BANDWIDTH OCCUPATION IS
WITH HUBBED TRAFFIC ALLOCATION THE PROTECTION SCHEME WITH MOST PROFITABLE BANDWIDTH OCCUPATION IS
SPRING
A. Bellato CTO T&A Team - OND 75
SNC
SNC vs SPRing
Ring protection
e2e protection
Content
>
>
> > >
Restoration
>
Centralized Restoration
Centralized restoration is historically an application of network management in Transport Network (i.e. SDH), where the amount of operators was very limited and a complete geographical network (e.g. country) used to be configured and controlled by a single(few) manager(s).
Operating System
DCN Network
ECC
DCN Network
NE from vendor a ECC
Distributed Restoration is an application thought for a multi vendor enviroment. The de-regulation in Public Networks, has made distributed management, then distributed restoration attractive also for Transport Network. This implies a standard activity in order to align applications from different vendors.
Distributed Manger
Content
>
>
> > > >
SDH layering
PHYSk RSTSk MSTSk PHYSo RSTSo MSTSo
LAYERS
PHYSICAL RS TRAIL
MSPC
MSASk
HTCM HPOM HTCT HSUT
MS TRAIL
MSASo
HPC HO Trail
HPTSo
HO PATH/TRAIL
HPTSk
HPASk
LTCM LPOM LTCT LSUT
LPASo
LPC LO Trail
LPTSo CLIENT
LO PATH/TRAIL
LPTSk CLIENT
A. Bellato CTO T&A Team - OND 81
SDH Network
STM-N RS trail MS trail 2R
TM
STM-N RS trail
3R
TM
DXC
TM TM
DXC
ADM
ADM
KEY TM Terminal Multiplexer LE (2R) Line Equipment: repeater (no Ck recovery) LE (3R) Line Equipment: regenerator (Ck recovery) DXC Digital Cross-Connect ADM Add Drop Multiplex
Administrative pointers
High Order
MSOH
KEY RSOH Regenerator Section OverHead MSOH Multiplex Section OverHead AUG Administrative Unit Group VC Virtual Container POH Path OverHead
V C 4 P O H
High Order
V C 3 P O H
Low Order
V C 12 P O H
Low Order
MS Trail
ITU-T G.841
50 ms 50 ms ITU-T G.783 ITU-T G.808.1
HO/LO Path
Linear 1+1 SNCP/I (uni) Linear 1+1 SNCP/N (uni) Linear 1+1 SNCP/S (uni)
50 ms
HO/LO Trail
50 ms
Layer
Switching Mode Operation Mode W.T.R. timer APS channel
(Revertive mode)
MS Trail
Unidirectional / Bidirectional Revertive / Not Revertive 5 12 min K1 K2 byte of MSOH Clear SF on Protection Lockout Pr FS SF High Priority SF Low Priority SD High Priority SD Low Priority MS WTR EX NR N x Clear N x Lockout Wk (in 1:N scheme only) 50 ms (line/NE propagation delay not included) NOT DEFINED by ITU-T G.841
(Bidirectional Mode)
MSOH
K2 byte (bits 5-8) MS-AIS (due to LOS, LOF) (SF) B2 bytes B2 Exber (SF) / B2 Signal Degrade (SD)
STM-N
RSOH
Pointers K1 K2 bits 1-4
MSOH
MSOH
Request Type Req. Ch. Id. Br. Ch. Id. (Bridge Status) Arch. Mode
MS trail
Working TM
MS trail
2R
3R
TM
DXC
TM
Protection TM
DXC
DXC
W.T.R. timer
APS channel
H1, H2 bytes AUAIS / AULOP (HO VC3/VC4 SSF SF) H1, H2 bytes TUAIS / TULOP (LO VC3 SSF SF)
VC 12
V1 V2 V3 V4 V5
MSOH
V1, V2 bytes TUAIS / TULOP (LO VC12 SSF SF) K4 Stuff byte
50 ms (due to the lack of APS protocol, line propagation delay not applicable)
Hold-Off timer
J1 Trace Identifier Mismatch (SF) B3 B3 Exber (SF) / B3 Signal Degrade (SD) C2 Signal Label Mismatch (SF) / UNEQ (SF)
HO/LO Sub-Net.
2R
3R
TM
DXC
TM
Protection TM
DXC
ADM
ADM
HO/LO SNCP N
HO/LO SNCP I
DXC
50 ms (due to the lack of APS protocol, line propagation delay not applicable)
Hold-Off timer
N1 Bip8 Signal Degrade (SD) / UNEQ (SF) / Loss of Tandem Connection (SF) / Trace Identifier Mismatch (SF)
K3 N1 VC 12 POH V5 J2
N2 Bip2 Signal Degrade (SD) / UNEQ (SF) / Loss of Tandem Connection (SF) / Trace Identifier Mismatch (SF)
N2 K4 Stuff byte
HTCT/LTCT
DOMAIN A
DXC
DXC
DXC
DOMAIN C
DXC
Working
DXC
Layer
Switching Mode Operation Mode W.T.R. timer APS channel
(Revertive mode) (Bidirectional Mode)
HO/LO PATH
LINE
STS-N Signal
SECTION
Light Pulses
PHYSICAL
STE Regenerator Terminal
SONET Network
OC-M Section Line 3R
TM TM
OC-M Section
DCS
TM TM
DCS
ADM
ADM
KEY TM Terminal Multiplexer RGTR Regenerator (3R) DCS Digital Cross-Connect ADM Add Drop Multiplex
Low Order
Line Overhead
Transport Overhead
S T S 1 P O H
Low Order
High Order
V T 3 P O H V T 6 P O H
Low Order
Low Order
REFERENCE STANDARDS
Line
Linear 1+1 APS (uni/bid) Linear 1:N APS (uni/bid) 2F/4F classic MS-SPRing (bid)
HO/LO Path
Layer
Switching Mode Operation Mode W.T.R. timer APS channel
(Revertive mode)
Line
Unidirectional / Bidirectional Revertive / Not Revertive 5 12 min; 1 min step K1 K2 byte of Line Overhead Clear SF on Protection Lockout Pr FS SF High Priority SF Low Priority SD High Priority SD Low Priority MS WTR EX NR N x Clear N x Lockout Wk (in 1:N scheme only) 50 ms (line/NE propagation delay not included) NOT DEFINED by Bellcore GR-253
(Bidirectional Mode)
2/4F Bidirectional Line Selfhealing Ring (BLSR) Line Bidirectional Revertive 5 12 min; step 1 min (optionally, lower bound of 0 min)
(Bidirectional Mode)
Line Overhead LOS (Loss of Signal) and LOF (Loss of Frame) are considered as direct triggers (both as SF) for Line protection scheme
Transport Overhead
K2 byte (bits 5-8) AIS-L (SF) B2 bytes B2 Exber (SF) / B2 Signal Degrade (SD)
OC-N
SectionOH
Pointers K1 K2 bits 1-4
LineOH
LineOH
Request Type Req. Ch. Id. Br. Ch. Id. (Bridge Status) Arch. Mode
APS channel
(Bidirectional Mode)
* - P for STS path (HO) / V for VT path (LO) ^ - Applicable only to STS path ** - Excessive STS path BER (HO) / Excessive VT path BER + (LO) - STS Signal Degrade (HO) / VT Signal Degrade (LO)
A. Bellato CTO T&A Team - OND 107
VT
V1 V2 V3
STS1
J1 B3 C2 G1 F2 H4 Z3 Z4 Z5
V4 V5 J2 Z6
STS1 POH
Z7 Stuff byte
OTH Layering
OTSSk OMSSk OMSnP OTSSo OMSSo
LAYERS
MULTIPLEXED SIGNAL TRANSMISSION OPTICAL CHANNEL () ASSIGNMENT & MULTIPLEXING
OMS/OCH_A
OCH POM
OCHSo
ELECTRO/OPTICAL CONVERSION
OTUkSk
ODUkSk
TCT TCM ODU POM
ODUkSo ODUk_C
OTUkSo
OPUkSo
OPUkSk
DIGITAL PATH
CLIENT
CLIENT
OTH Network
ODUk path (trail) OCH, OTUk trail OMSn trail OTSn trail
3R LT LT
OCH, OTUk trail OMSn trail OMSn trail OTSn trail OTSn trail
3R OADM LT
OXC
STM-N LT LT
OXC
STM-N
OSn
LT
DXC
3R IP data
DXC
IP
KEY LT Line Terminal (optical channel multiplexing) OADM Optical Channel Add/Drop Multiplexer OXC ODU Cross-Connect 3R Wavelength assignment/regeneration (O/E/O, w/ clock recovery) R repeater (Optical Amplifier)
A. Bellato CTO T&A Team - OND 110
Digital domain
Associated overhead
OH OH OH
Client
OPUk
ODUk FEC
OCh Payload Unit (OPUk) OCh Data Unit (ODUk) OCh Transport Unit (OTUk) Optical Channel (OCh)
OTUk
Non-associated overhead Optical domain OCh OH
OMS OH OTS OH
Optical Channel Carrier (OCC) Optical Physical Section Optical Multiplex Section Optical Transmission Section
OSC
OMS layer LOS + OMS OH OOS defects (SF/SD) OCH layer LOS (through OCH POM) + OCH OH OOS defects (SF/SD) OTUk defects (SF/SD)
Linear 1+1/1:N ODUk SNCP/I (uni/bid) Linear 1+1/1:N ODUk SNCP/N (uni/bid)
(Linear protection)
50 ms
50 ms
Operation Mode
W.T.R. timer APS channel
(Revertive mode)
(Bidirectional Mode)
OTU
OCh OH
OMS OH OTS OH
OSC
Loss of Signal Payload TSF-P (SF)
(LOS-P)
OMSn trail
OSC LT OADM
OMSn trail
3R
LT
R
LT
Wk 1 N Pr 1 N
OXC
STM-N LT
OXC
LT STM-N
LT 3R
IP
IP data
WK s PR s
x2 x2
Wavelength accomodation
Operation Mode
W.T.R. timer APS channel
(Revertive mode)
(Bidirectional Mode)
OTU
OCH OH OMS OH OTS OH
OCH OCC
OCC
OSC
OCH trail
OSC (OCH OH-OOS)
R
LT
Wk 1 N Pr 1 N
LT
OADM
OXC
STM-N LT
OXC
LT
OXC
LT
3R IP data
Optical Fiber
WK s WK s
x2 x2
x2
PR s WK s PR s PR s
x1
Operation Mode
W.T.R. timer APS channel
(Revertive mode)
(Bidirectional Mode)
BEI/BIAE
BDI IAE
3
RES
SM
1 2
TTI
Column #
1 2 3 4 5 6 7 8 9 10 11 12 13
BIP8
14
15..3824 38254080
Row#
1 2 3 4
FAS
MFAS
SM
GCC0
RES
FEC
ODU Overhead
OH
FEC
KEY FAS: Frame Alignment Signal (3xF6h, 3x28h) MFAS: Multi-frame alignment signal (0..255) SM: Section Monitoring overhead
ODUk
1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Row#
2 3 4
TCM6
TCM3
GCC1 GCC2
TCM2
TCM1
PM
RES
EXP
APS/PCC
Request Type Req. Ch. Id. Br. Ch. Id. (Bridge Status) Arch. Mode
Bytes 5-6-7 Automatic Protection Switching / Protection Communication Channel Byte 8 reserved for future use
OTUk trail
LT
R
LT
OADM
OXC
STM-N
LT LT
OXC
OXC
LT 3R
IP data
IP
Optical Fiber
WK s WK s
x2 x2
x2
PR s WK s PR s PR s
x1
Operation Mode
W.T.R. timer APS channel
(Revertive mode)
(Bidirectional Mode)
BEI
BDI
3
STAT
PM
1 2
TTI
1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
BIP8
Row#
2 3 4
TCM6
TCM3
GCC1 GCC2
TCM2
TCM1
APS/PCC
PM
RES
EXP
OH OH
LT
LT
R
LT LT
OADM
OXC
STM-N LT LT
OXC
OXC
LT
DXC
3R IP data
IP
Optical Fiber
WK s WK s
x2 x2
x2
PR s WK s PR s PR s
x1
Operation Mode
W.T.R. timer APS channel
(Revertive mode)
(Bidirectional Mode)
STAT Locked Defect (SF) / AIS (SF) / LTC (SF) TTI Trace Identifier Mismatch (SF) BIP-8 DEG (SD)
BEI/BAEI
BDI
STAT
TCMi
1 2 3
TTI
1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
BIP8
Row#
2 3 4
TCM6
TCM3
GCC1 GCC2
TCM2
TCM1
APS/PCC
PM
RES
EXP
OH OH
Linear 1+1 ODUk SNC/S (A) User QoS supervision (TCM1) End-to-End path supervision (PM)