OTN NEWBIES

1
 FOREWORD
 According to the ITU-T Recommendation G.709, an Optical
Transport Network (OTN) is composed of a set of optical
network elements connected by optical fiber links. The network
provides functionality of transport, multiplexing, routing,
management, supervision, and survivability of optical channels
carrying client signals.
 This architecture can be seen as a combination of the
advantages of SDH/SONET technology with the flexibility of
DWDM. Using OTN, the OAM&P functionality of SDH/SONET is
applied to DWDM optical networks.
 Compared to SDH/SONET, OTN has the following advantages:
 • Stronger error correction mechanisms
 • More levels of tandem connection monitoring
 • Transparent transport of client signals
 • Switching scalabilityIntroduction

Page2
 ABOUT THIS COURSE

 This course is based on the following ITU-T

recommendations:
 ITU-T G.709
 ITU-T G.805
 ITU-T G.806
 ITU-T G.798

Page3
LEARNING GUIDE

Just little Basics

4
 CONTENTS

1. OTN Introduction
2. Typical OTN Scenarios

Page5
 CONTENTS

1. OTN Introduction
1.1 OTH
1.2 OTN Port Structure
1.3 Multiplexing/Mapping Principles and Bit Rates
1.4 Overhead Description
1.5 Maintenance Signals and Functions of Different
Layers
1.6 Alarms and Performance Events

Page6
OTN

 Optical transport network (OTN)

 An OTN network is composed of a set of optical
NEs connected by optical fiber links. These NEs
are able to provide functions such as transport,
multiplexing, routing, management, supervision,
and protection (survivability) of client signals,
according to the requirements specified in REC.
G.872.

Page7
FEATURES OF OTN
 Compared with SDH and SONET networks, an OTN
network has the following features:
 Ultra capacity with high accuracy, T-bit/second per fiber over
DWDM lines
 Service transparency for client signals
 Asynchronous mapping, powerful FEC function, simplified
network design, and reduced costs
 Compared with traditional WDM networks, an OTN
network has the following features:
 Enhanced OAM and networking capabilities for all services
 Dynamic electrical/optical-layer grooming

Page8
 OTN STANDARD SYSTEM
Equipment G.874 Management features of NEs on an OTN network
management OTN network: Protocol-neutral management
G.874.1 information model for the network element

Jitter and G.8251 Jitter and shift control on an OTN network

performance Bit error performance parameters and specifications on
G.8201 international channels of multiple carriers on an OTN network

Network G.873.1 Linear protection on an OTN network

protection G.873.2 Ring protection on an OTN network

OTN Equipment
G.798 Features of function blocks of equipment on an OTN network
functions
and
features G.806 Transport network equipment features: description methods and general functions

G.709 Ports on an OTN network

Structure and
G.7041 Generic frame protocol (GFP)
mapping
Link capacity adjustment
G.7042 scheme (LCAS) for virtual concatenation signals

G.959.1 Physical-layer ports on an OTN network

Physical-layer
G.693 Optical ports for intra-office systems
features

G.664 Optical security rule and requirements in an optical transport system

G.872 OTN network structure

Structure
G.8080 ASON network structure

9
OTN NETWORK LAYERS AND PORT STRUCTURE

 OPUk: optical channel payload unit-k

IP/MPLS ATM Ethernet STM-N
 ODUk: optical channel data unit-k
 OTUk: completely standardized optical
channel transport unit-k OPUk
 OTUkV: functionally standardized Optical ODUk (ODUkP and ODUkT)
channel transport unit-k
OTUk OTUkV OTUk OTUkV
 OCh: optical channel with full
functionality OCh OChr
 OChr: optical channel with reduced OMSn
OPSn
functionality OTSn
 OMS: optical multiplex section
OTM-n.m OTM-0.m
 OTS: optical transmission section OTM-nr.m
 OPS: optical physical section
 OTM: optical transport module

Page10
 OTM-N.M CONTAINMENT RELATIONSHIPS
Client signal
ln
OPUk OH OPUk payload

ODUk OH OPUk

OTM-n. m
OTUk[V] OH ODUk FEC l2
l1
OCh OChOH OCh payload
l OSC
OCG-n.m
OCCo
management OCCo

OCCo

OCCp OCCp OCCp

Non-associated OH

OTM overhead signal (OOS)

OMU-n.m OMSn OH
Common

OH

OTM-n.m OTSn OH

OOS
 “n” represents the maximum number of wavelengths that can be supported at the lowest bit rate
supported by the wavelengths. “m” equals 1, 2, 3, 12, 23, or 123.
 OTS_OH, OMS_OH, OCh_OH and COMMS OH information fields are contained in the OOS.
 The optical supervisory channel (OSC) is used to transmit OOSs.

Page11
OTM-NR.M CONTAINMENT RELATIONSHIPS
Client signal
l 16
OPUk OH OPUk payload

OTM-16r.m
ODUk OH OPUk
l 2
OTUk[V] OH ODUk FEC l 1

OChr OCh payload

OCG-nr.m OCCp OCCp OCCp

OTM-nr.m

 Fixed channel spacing, irrelevant to the signal rate

 1 < n ≤ 16; m = 1, 2, 3, 12, 23, or 123

 Without optical supervisory channels

Page12
OTM-0.M CONTAINMENT RELATIONSHIPS

Client signal

OTM-0.m
OPUk OH OPUk payload

ODUk OH OPUk

OTUk[V] OH ODUk FEC

OChr OCh payload

OTM-0.m OPS0

 The OTM 0.m supports a non-colored optical channel on a single optical span with 3R
regeneration at each end.
 m = 1, 2, or 3
 Without optical supervisory channels

Page13
OTN PORTS

Network Operator B
USER Network
A Operator
OTM NNI OTM C
OTM IaDI-IrVI NNI
UNI IrDI
OTM NNI
OTM NNI
IaDI-IaVI
IaDI-IaVI

Vendors X Vendors Y

 User to network interface (UNI)

 Network node interface (NNI)
 Inter-domain interface (IrDI)
 Intra-domain interface (IaDI)
 Between equipment provided by different vendors (IrVI)
 Within subnet of one vendor (IaVI)
 The completely standardized OTUk is used at OTM IrDIs and OTM IaDIs.
 The partly standardized OTUk is used at OTM IaDIs.

Page14
 CONTENTS

1. OTN introduction
1.1 Optical transport hierarchy
1.2 OTN interface structure
1.3 Multiplexing/mapping principles and bit rates
1.4 Overhead description
1.5 Maintenance signals and function for different
layers
1.6 Alarm and performance events

Page15
 OTN MULTIPLEXING AND MAPPING STRUCTURE

OTM-0.m

OCCr
1 OChr
i
1
1 ≤ i+j+k ≤ n
j 1
OTM-nr.m OCG-nr.m OCCr OChr Client signal
k 1 1 1
OTU3[V] ODU3 OPU3
1 1 16
OCCr OChr ODTUG3
1 4
Client signal
1 1
OTU2[V] ODU2 OPU2

Client signal
1 1
1 ODTUG2
OCC OCh
i 4 1
1 ≤ i+j+k ≤ n OTU1[V] 1 ODU1 OPU1
j 1 1
OTM-n.m OCG-n.m OCC OCh
k
1 1
OCC OCh
1
1
Multiplexing
OSC OOS OTS, OMS, OCh, COMMS
Mapping

Page16
OTN Multiplexing and Mapping Structure

17
OTN Multiplexing and Mapping Structure

18
OTN Service Bearing Capability (LO ODU)
Client service rate
 LO ODU
104.134G OPU4
 New LO ODU signals
1.25G ODU0

OPUflex


 10.3G ODU2e
 104G ODU4

OPUflex(GFP)
 ODUflex 40.149G OPU3

OPUflex
10.312G OPU2e
9.995G OPU2

OPUflex
2.488G
OPU1
1.238G
OPU0
LO OPU

19
 20

OPU4/21
(ODU0, ODU1, ODU2, ODU2e, ODU3, ODU3e2, ODUflex)
OPU3e2/21
(ODU0, ODU1, ODU2, ODU2e, ODUflex)
OPU3/21
(ODU0, ODU1, ODU2, ODU2e, ODUflex)
HO OPU

OPU3/20
(ODU1, ODU2)
OPU2/21
(ODU0, ODU1, ODUflex)
OPU2/20
(ODU1)
OPU1
(ODU0)
LO ODU rate

ODUflex(GFP)
OTN LINE BEARING CAPABILITY

ODUflex ODUflex ODUflex

ODU2e
ODU3e2
ODU4

ODU1

ODU0
ODU3

ODU2
41.7GG ODU3e2 (G.sup43)

Signals with extended

New HO ODU signals

40G ODU3
10G ODU2
104G ODU4
(HO ODU)

capabilities
2.5G ODU1

–




OTUK FRAME RATE
OTUk rate = 255/(239 - k) x STM-N frame rate

OTU Type OTU Nominal Bit Rate OTU Bit Rate Tolerance

OTU1 255/238 x 2488320 kbit/s

OTU2 255/237 x 9953280 kbit/s

20 ppm
OTU3 255/236 x 39813120 kbit/s

OTU4 255/227 x 99532800 kbit/s

Note 1: The nominal OTUk rates are approximately 2666057.143 kbit/s (OTU1), 10709225.316
kbit/s (OTU2), 43018413.559 kbit/s (OTU3) and 111809 973.568 kbit/s (OTU4).
Note 2: OTU0, OTU2e and OTUflex are not specified in this recommendation. ODU0 signals
are transported over ODU1, ODU2, ODU3 or ODU4 signals, ODU2e signals are transported
over ODU3 and ODU4 signals, and ODUflex signals are transported over ODU2, ODU3 and
ODU4 signals.
ODUK FRAME RATE
ODUk rate = 239/(239 - k) x STM-N frame rate

ODU Type ODU Nominal Bit Rate ODU Bit Rate Tolerance

ODU0 1244160 kbit/s

ODU1 239/238 x 2488320 kbit/s

ODU2 239/237 x 9953280 kbit/s

20 ppm
ODU3 239/236 x 39813120 kbit/s

ODU4 239/227 x 99532800 kbit/s

ODU2e 239/237 x 10312500 kbit/s

100 ppm

ODUflex for CBR 239/238 x Client signal bit rate

client signals Client signal bit rate tolerance, with a
maximum of 100 ppm

ODUflex for GFP-F Pre-set bit rate 20 ppm

mapped client
signals
 OPUK FRAME RATE
OPUk payload rate = 238/(239 - k) x STM-N frame rate

OPU Type OPU Payload Nominal Bit Rate OPU Payload Bit Rate Tolerance

OPU0 238/239 x 1244160 kbit/s

OPU1 2488320 kbit/s

OPU2 238/237 x 9953280 kbit/s
20 ppm
OPU3 238/236 x 39813120 kbit/s

OPU4 238/227 x 99532800 kbit/s

OPU2e 238/237 x 10312500 kbit/s

100 ppm

OPUflex for CBR client Client signal bit rate

Client signal bit rate tolerance, with a
signals
maximum of 100 ppm

OPUflex for GFP-F 238/239 x ODUflex signal rate 20 ppm

mapped client signals

OPU1-Xv X x 2 488 320 kbit/s

OPU2-Xv X x 238/237 x 9953280 kbit/s
20 ppm
ODUK (TDM)

 Low-rate ODUk signals are multiplexed into high-

rate ODUk signals using time-division multiplexing:
 A maximum of four ODU1 signals are multiplexed into
one ODU2 signal using time-division multiplexing.
 Hybrid j (j  4) ODU2 and 16-4j ODU1 signals are
multiplexed into one ODU3 signal using time-division
multiplexing.
 Multiple LO ODUi[j] signals at different levels are
multiplexed into one HO ODUk signal.

Page24
ODU1 MULTIPLEXED INTO ODU2
 ODTU12: optical channel data tributary unit 1 into 2
 ODTUG2: optical channel data tributary unit group 2
 JOH: justification overhead
ODU1
OH
ODU1 payload ODU1

ODTU12 ODTU12
ODU1
JOH

ODTU12 ODTU12 ODTUG2

JOH JOH
ODU1 ODU1

ODTUG2

OPU2
OPU2 payload OPU2
OH

ODU2
OH
ODU2 payload ODU2

Page25
ODU1 MULTIPLEXED INTO ODU2
 ODU1 floats in one quarter of the OPU2 payload area.
 An ODU1 frame travels cross multiple ODU2 frame boundaries.

Alignment

OPU1 OH
Client-layer signal
ODU1
ODU1OH (STM-16, ATM, or GFP)

x4

OPU1 OH
OPU2 OH

OPU1 OH
Alignment Client Layer Signal

OPU1 OH
Client(for
Layer SignalSTM-16)
ODU2 ODU1 OH example,

OPU1 OH
ODU1 OH Client Layer
Client-layer
(for SignalSTM-16)
signal
example,
ODU2 OH ODU1 OH
ODU1 OH
(for example,
(STM-16, ATM, or GFP)
STM-16)

Alignment OTU2
OH
OPU1 OH
OPU1 OH
OPU2 OH

Alignment Client Layer Signal

OTU2
OPU1 OH

OTU2 ODU1 OH Client(for

Layer SignalSTM-16)
example,
OPU1 OH

ODU1 OH OPU2 Payload

Client-layer
Client(for signal
Layer SignalSTM-16)
example, FEC
ODU2 OH ODU1 OH
ODU1 OH
(for example, STM-16)
(STM-16, ATM, or GFP)

Page26
 ODU1 AND ODU2 MULTIPLEXED INTO ODU3
 ODTU23: optical channel data tributary unit 2 into 3
 ODTU13: optical channel data tributary unit 1 into 3

ODU2 ODU2 payload ODU1 ODU1 payload

OH ODU2 OH ODU1

ODTU23 ODU2 ODTU23 ODTU13 ODU1 ODTU13

JOH JOH

ODTU13 ODTU13 ODTU23 ODTU23 ODU2 ODU2 ODU1 ODU1 ODTUG3

JOH JOH JOH JOH

ODTUG3

OPU3 OPU3 payload OPU3

OH

ODU3 ODU3 payload

OH ODU3

Page27
GMP Mapping

Payload Area 0

Pserver
OH
client data Pserver? enable
client
data
indication memory payload area
= frame start
stuff read/write
clock
enable

Cm(t)
server frame or multi-frame

 GMP can automatically adapt CBR services to an OTN container. It is the key
technology for an OTN network to bear multiple services.
 Service rate information transmitted in overheads
 Sigma-delta algorithm
 M byte bit width
 Separation of data and clocks

28
 ODUflex

TSi TSj
Services with BMP GMP
OH OH
a fixed bit rate

Client signals ODUflex

TSi TSj
GFP GMP
Packet services OH OH

Client services ODUflex

 Map CBR services to ODUflex services using synchronized packet encapsulation.

 Map packet services to ODUflex services using GFP.
 Map ODUflex services to HO OPUk services using GMP.

29
 CONTENTS

1. OTN introduction
1.1 Optical transport hierarchy
1.2 OTN interface structure
1.3 Multiplexing/mapping principles and bit rates
1.4 Overhead description
1.5 Maintenance signals and function for different
layers
1.6 Alarm and performance events

Page30
OOS

FDI-O OOS functions subject to

n
standardization. Bit rate
TTI FDI-P and format are not
Non-associated

3
2
standardized.
overhead

1
BDI-O BDI-O FDI-O

BDI-P OMSn BDI-P FDI-P

OTSn

OCh
PMI PMI OCI

General management communication

 TTI: trail trace identifier

 PMI: payload missing indication
 OCI: open connection indication
 BDI-O: backward defect indication - overhead
 BDI-P: backward defect indication - payload
 FDI-O: forward defect indication - overhead
 FDI-P: forward defect indication - payload

Page31
OPTICAL-LAYER FUNCTION
OTSn OH Payload

TTI MI_TxTI
dLOS_P
BDI-O RI_BDI-O

BDI-P RI_BDI-P
OTSn

PMI aPMI

OA, DCM

Payload and OH combined together APR control

 The OTS source function is used as an example.

Page32
OTN FRAME FORMATS (K = 1, 2, OR 3)

4080
3825
3824
15
14
16
17
1

8
7

OTUk
1 Alignment Client signal
OH

OPUk OH
2 mapped in
OTUK
OPUk
OPU payload
k payload
3 ODUk FEC
OH
4

Client signal
OPUk - optical channel payload unit K:
ODUk - Optical Channel Data Unit 1 - 2.5G
2 - 10G
OTUk - Optical Channel Transport Unit 3 - 40G

Alignment

Page33 33
OTN ELECTRICAL OVERHEAD OVERVIEW
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO

 ODUk OH  Alignment OH
 TCMACT: tandem connection monitoring  FAS: frame alignment signal

activation/deactivation control channel  MFAS: multiframe alignment signal

 TCMi: tandem connection monitoring i

OPUk OH
 FTFL: fault type and fault location reporting
 PSI: payload structure identifier
channel
 JC: justification control
 PM: path monitoring
 NJO: negative justification opportunity
 EXP: experimental
 GCC1/2: general communication channel 1/2  OTUk OH
 APS/PCC: automatic protection switching  SM: section monitoring

coordination channel/protection  GCC0: general communication channel 0

communication control channel  RES: reserved for future international

standardization

Page34
FRAME ALIGNMENT SIGNAL
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO

Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6

1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
OA1 OA1 OA1 OA2 OA2 OA2

 Frame alignment signal (FAS)

 A six-byte OTUk-FAS signal is defined in row 1 and columns 1 to 6 of the
OTUk overhead.

 OA1 is 0xF6 (1111 0110) and OA2 is 0x28 (0010 1000).

Page35
MULTIFRAME ALIGNMENT SIGNAL
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO

MFAS OH byte  Multiframe alignment signal (MFAS)

1 2 3 4 5 6 7 8  It is defined in row 1 and column 7.
.
.
0 0 0 0 0 0 0 0  The value of the MFAS byte is increased by OTUk/ODUk
0 0 0 0 0 0 0 1
0 0 0 0 0 0 1 0 frame and the MFAS byte provides a maximum of 256
0 0 0 0 0 0 1 1
MFAS sequence

0 0 0 0 0 1 0 0 multiframes.
..
..
 Individual OTUk/ODUk overhead signals may use this
1 1 1 1 1 1 1 0
1 1 1 1 1 1 1 1 central multiframe to lock their 2, 4, 8, 16, or 32
0 0 0 0 0 0 0 0
0 0 0 0 0
..
0 0 1 multiframes to the main frame.

Page36
 OTUK SECTION MONITORING OVERHEAD
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO

1 2 3  Trail trace identifier (TTI)

TTI BIP-8
 A one-byte overhead is defined to transport 64-byte TTI
0 1 2 3 4 5 6 7 8 signals.
BDI
IAE

SAPI BEI/BIAE RES

15  The 64-byte TTI signal should be aligned with the OTUk
16
multiframe and transmitted four times per multiframe.
DAPI
31
32  TTI structure:
 16-byte SAPI: source access point identifier
Operator
specified
 16-byte DAPI: destination access point identifier
63  32-byte operator specified information

Page37
 OTUK SECTION MONITORING OVERHEAD
 Bit interleaved parity-8 (BIP-8)
 For section monitoring and a one-byte error detection code signals are defined.
 This byte provides a bit interleaved parity-8 (BIP-8) code.
 OTUk BIP-8 is computed over bits in the OPUk (columns 15 to 3824) area of OTUk frame
i, and inserted in the OTUk BIP-8 overhead location in OTUk frame i+2.

1 14 15 3824

Frame i OPUk
BIP8

Frame i+1

Frame i+2

Page38
 OTUK SECTION MONITORING OVERHEAD
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO

1 2 3  Backward error indication/backward incoming

TTI BIP-8 alignment error (BEI/BIAE)
 A four-bit BEI and BIAE signal is defined.
0 1 2 3 4 5 6 7 8
This signal is used to transmit in the upstream direction
BDI


IAE

SAPI BEI/BIAE RES

15
16
the count of interleaved-bit blocks and incoming
DAPI alignment error (IAE) conditions.
31
32  During an IAE condition the code "1011" is inserted into
the BEI/BIAE field and the error count is ignored.
Operator
specified Otherwise the error count (0-8) is inserted into the
BEI/BIAE field.
63

Page39
 OTUK SECTION MONITORING OVERHEAD
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO

1 2 3  Backward defect indication (BDI)

TTI BIP-8
 A single-bit BDI signal is defined to transmit the
signal failure status detected by the section
0 1 2 3 4 5 6 7 8
termination sink function in the upstream direction.
BDI
IAE

SAPI BEI/BIAE RES

15
16  BDI is set to "1" to indicate an OTUk backward
DAPI defect indication; otherwise, it is set to "0".
31
32

Operator
specified

63

Page40
 OTUK SECTION MONITORING OVERHEAD
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO
 Incoming alignment error (IAE)
1 2 3
 A single-bit IAE signal is defined to allow the S-CMEP
TTI BIP-8
ingress point to inform its peer S-CMEP egress point
0 1 2 3 4 5 6 7 8 that an alignment error in the incoming signal has
BDI

been detected.
IAE

SAPI BEI/BIAE RES

15
16
 IAE is set to "1" to indicate a frame alignment error;
DAPI
31 otherwise it is set to "0".
32
 RES (reserved)
Operator
specified  Two bits are reserved (RES) for future international
standardization. They are set to "00".
63

Page41
OTUK GCC0 AND RES OVERHEAD
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO

 General communication channel (GCC0)

 Two bytes are allocated in the OTUk overhead to support a general
communications channel between OTUk termination points.
 A clear channel is located in row 1 and columns 11 and 12.
 RES (reserved)
 Two bytes of the OTUk overhead are reserved for future international
standardization.
 They are located in row 1 and columns 13 and 14.
 They are set to all “0”s.

Page42
 ODUK PATH MONITORING OVERHEAD
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO

1 2 3  TTI / BIP-8 / BEI / BDI

TTI BIP-8
 For path monitoring, this overhead’s functions are the
0 1 2 3 4 5 6 7 8 same as those of the OTUk SM signal, except that BEI
BDI

SAPI BEI STAT signals do not support the BIAE function.

15
16
DAPI
 They are located in row 3 and columns 10 to 12.
31
32

Operator
specified

63

Page43
 ODUK PATH MONITORING OVERHEAD
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO

1 2 3
 Status (STAT)
TTI BIP-8
 For path monitoring, three bits are defined as status bits.
 They indicate the presence of a maintenance signal.
0 1 2 3 4 5 6 7 8
BDI

SAPI BEI STAT Bit 678 Status

15
16
DAPI 000 Reserved for future international standardization
31 001 Normal path signal
32
010 Reserved for future international standardization
Operator
specified 011 Reserved for future international standardization

63 100 Reserved for future international standardization

101 Maintenance signal: ODUk - LCK

Page44
 ODUK TCM OVERHEAD
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO

1 2 3  TTIi/BIP-8i/BEIi/BIAEi/BDIi
TTIi BIP-8i
 For each tandem connection monitoring field,
0 1 2 3 4 5 6 7 8
this overhead’s functions are the same as
BDIi

SAPI BEIi/BIAEi STATi those of OTUk SM signals.

15
16  Six fields of the ODUk TCM overhead are
DAPI
31
defined in row 2 and columns 5 to 13, and row
32
3 and columns 1 to 9 of the ODUk overhead.
Operator
specific

63

Page45
 ODUK TCM OVERHEAD
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO

1 2 3
 STAT (status)
 For each tandem connection monitoring field, three
TTIi BIP-8i
bits are defined as status bits.
 They indicate the presence of a maintenance signal if
0 1 2 3 4 5 6 7 8 there is an incoming alignment error at the source
TC-CMEP, or if there is no source TC-CMEP active.
BDIi

SAPI BEIi/BIAEi STATi

15
16
Bit 678 Status
DAPI
000 No source TC
31 001 In use without IAE
32
010 In use without IAE

Operator 011 Reserved for future international standardization

specified
100 Reserved for future international standardization

63 101 Maintenance signal: ODUk -LCK

110 Maintenance signal: ODUk -OCI

Page46
NESTED AND CASCADED ODUK MONITORED
CONNECTIONS

TCM6 TCM6 TCM6 TCM6 TCM6 TCM6 TCM6

TCM5 TCM5 TCM5 TCM5 TCM5 TCM5 TCM5
TCM4 TCM4 TCM4 TCM4 TCM4 TCM4 TCM4
TCM3 TCM3 TCM3 TCM3 TCM3 TCM3 TCM3
TCM2 TCM2 TCM2 TCM2 TCM2 TCM2 TCM2
TCM1 TCM1 TCM1 TCM1 TCM1 TCM1 TCM1

A1 B1 C1 C2 B2 B3 B4 A2

C1 - C2

B1 - B2 B3 - B4

A1 - A2

TCMi TCM OH field not in use TCMi TCM OH field in use

Page47
OVERLAPPED ODUK MONITORED CONNECTIONS
TCM6 TCM6 TCM6 TCM6 TCM6
TCM5 TCM5 TCM5 TCM5 TCM5
TCM4 TCM4 TCM4 TCM4 TCM4
TCM3 TCM3 TCM3 TCM3 TCM3
TCM2 TCM2 TCM2 TCM2 TCM2
TCM1 TCM1 TCM1 TCM1 TCM1

A1 B1 C1 B2 C2 A2

C1 - C2

B1 - B2

A1 - A2

TCMi TCM OH field not in use TCMi TCM OH field in use

Page48
ODUK TCM ACT COORDINATION PROTOCOL
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO

 TCM activation/deactivation (TCMACT)

 A one-byte TCM activation/deactivation field is located in row 2 and
column 4.

 Its definition is to be defined in future.

Page49
ODUK GCC1/GCC2
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO

 General communication channel (GCC1/GCC2)

 Two fields of the two bytes are allocated in the ODUk overhead to support two
general communication channels between any two NEs with access to the ODUk
frame structure (for example, at 3R regeneration points).

 The bytes for GCC1 are located in row 4 and columns 1 and 2, and the bytes for
GCC2 are located in row 4 and columns 3 and 4 of the ODUk overhead.

Page50
ODUK APS/PCC CHANNEL
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO

 Automatic protection switching/protection communication control

(APS/PCC)
 A four-byte ODUk-APS/PCC signal is defined in row 4 and columns 5 to 8 of the ODUk
overhead.

 For linear protection schemes, bit assignments for these bytes and the bit oriented
protocol are given in ITU-T G.873.1. Bit assignment and byte oriented protocol for ring
protection schemes are to be defined in future.

 A maximum of eight levels of nested APS/PCC signals may be present in this field.

Page51
ODUK FTFL CHANNEL
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO

 Fault Type & Fault Location (FTFL)

 One byte is allocated in the ODUk overhead to transport a 256-byte FTFL
message.
 The byte is located in row 2 and column 14 of the ODUk overhead.
 The 256-byte FTFL message consists of two 128-byte fields. The forward field is
allocated in bytes 0 to 127 of the FTFL message. The backward field is allocated
in bytes 128 to 255 of the FTFL message.

Page52
 ODUK EXPERIMENTAL AND RESERVED OVERHEAD
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO

 Experimental (EXP)
 Two bytes are allocated in the ODUk overhead for experimental use.
 They are located in row 3 and columns 13 and 14 of the ODUk overhead.
 There is no requirement for forwarding the EXP overhead over different (sub)networks.

 RES
 9 bytes are reserved in the ODUk overhead for future international standardization.
 They are located in row 2 and columns 1 to 3, and row 4 and columns 9 to 14 of the ODUk
overhead.
 They are set to all “0”s.

Page53
OPUK PAYLOAD STRUCTURE IDENTIFIER
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
1 FAS MFAS SM GCC0 RES RES JC
TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO

 Payload structure identifier (PSI)

0 PT
 One byte is allocated in the OPUk overhead
1
to transport a 256-byte payload structure
Mapping identifier (PSI) signal.
and concatenation  It is aligned with the ODUk multiframe.
specific
 PSI[0] contains a one-byte payload type.
255 PSI[1] to PSI[255] are mapping and
concatenation specific.

Page54
PAYLOAD TYPE CODE POINTS

MSB 1234 LSB 1234 Hex Code

Meaning

0000 0001 01 Experimental mapping

0000 0010 02 Asynchronous CBR mapping
0000 0011 03 Bit synchronous CBR mapping
0000 0100 04 ATM mapping
0000 0101 05 GFP mapping
0000 0110 06 Virtual Concatenated signal
0001 0000 10 Bit stream with octet timing mapping

0001 0001 11 Bit stream without octet timing mapping

0010 0000 20 ODU multiplex structure

0101 0101 55 Not available
0110 0110 66 Not available
1000 xxxx 80-8F Reserved codes for proprietary use

1111 1101 FD NULL test signal mapping

1111 1110 FE PRBS test signal mapping
1111 Page55 1111 FF Not available
OPUK MAPPING SPECIFIC OVERHEAD
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

1 FAS MFAS SM GCC0 RES RES JC

TCM
2 RES ACT TCM6 TCM5 TCM4 FTFL RES JC
3 TCM3 TCM2 TCM1 PM EXP RES JC
4 GCC1 GCC2 APS/PCC RES PSI NJO

 Justification control/negative justification opportunity/reserved

(JC/NJO/RES)
 Seven bytes are reserved in the OPUk overhead for the mapping and concatenation
specific overhead.
 These bytes are located in rows 1 to 3 and columns 15 and 16, and row 4 and column
16.
 255 bytes in the PSI are reserved for mapping and concatenation specific purposes.

Page56
THANKS FOR BEING PATIENT

57