OTN NEWBIES

WHY OTN
SDH/SONET
OAMP for a transparnet mixture for protocols
including ip,ethernet,generic frame procedure
etc.
Single wavelength technology

DWDM
Served to increase the existing fibre bandwidth
Introduced new network elements like optical
amplifiers ,mux,demux ,switchs etc
Lacked the protection and management of sonet

WHY OTN CONTINUE

OTN ----->HYBRID OF SONET AND
DWDM
Combines the benefits of sonet with the
bandwidth expandabilty of dwdm
Applies oamp of sonet to the dwdm
networks
Enables transparent and wave length
manageability multi wavelength networks
to sonet networks

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
Page4

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

Page5

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.
Page6

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

Page7

OTN Standard System

OTN

Equipment

G.874

Management features of NEs on an OTN network

management

G.874.1

OTN network: Protocol-neutral management

information model for the network element

Jitter and

G.8251

Jitter and shift control on an OTN network

performance

G.8201

Bit error performance parameters and specifications on

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

Equipment
functions
and
features

G.798

Features of function blocks of equipment on an OTN network

G.806

Transport network equipment features: description methods and general functions

G.709

Ports on an OTN network

G.7041

Generic frame protocol (GFP)

G.7042

Link capacity adjustment

scheme (LCAS) for virtual concatenation signals

G.959.1

Physical-layer ports on an OTN network

G.693

Optical ports for intra-office systems

G.664

Optical security rule and requirements in an optical transport system

G.872

OTN network structure

G.8080

ASON network structure

Structure and
mapping

Physical-layer
features

Structure

OTN Network Layers and Port Structure

OPUk: optical channel payload

unit-k

ODUk: optical channel data unit-k

OTUk: completely standardized

optical channel transport unit-k

OTUkV: functionally standardized

Optical channel transport unit-k

OCh: optical channel with full

functionality

OChr: optical channel with

reduced functionality

OMS: optical multiplex section

OTS: optical transmission section

OPS: optical physical section

OTM: optical transport module

IP/MPLS ATM

EthernetSTM-N

OPUk
ODUk (ODUkP and ODUkT)
OTUk

OTUkV

OTUk

OTUkV

OCh

OChr

OMSn
OTSn

OPSn

OTM-n.m

OTM-0.m
OTM-nr.m

Page9

OTM-n.m Containment Relationships

Client signal

ODU OH
k
OTUk[V OH
]

OCCo

OCCo

Common
management OCCo
OH

OTM-n.m

OCh payload
OCCp

OCCp

OMSn OH

OTSn OH

OTSn payload

OMU-n.m

FEC

OMSn payload

Non-associated
OH

OCG-n.m

OPUk
ODUk

OCh OChOH

ln

OPUk payload

OCCp

OTM-n.m

OPUk OH

l2
l1
l OSC
OTM overhead signal (OOS)

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.
Page10

OTN Ports
Network Operator
B

USER
A
OTM
UNI
OTM NNI
IaDI-IaVI

OTM
NNI
IaDI-IrVI

Vendors X

OTM NNI
IaDI-IaVI

Network
Operator
OTM
C
NNI
IrDI

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.
Page11

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

Page12

1 Alignment
2
3
4

ODUk
OH

Client signal
mapped in
OPUk
payload
OPU
k payload

4080

3825

3824

OTUk
OH

OPUk OH

14
15
16
17

7
8

OTN Frame Formats (k = 1, 2, or 3)

OTUK
FEC

Client signal
OPUk - optical channel payload unit
ODUk - Optical Channel Data Unit
OTUk - Optical Channel Transport Unit

K:
1 - 2.5G
2 - 10G
3 - 40G

Alignment

Page13

13

OTN Electrical Overhead Overview

1

FAS

1
2

RES

TCM3
GCC1

TCM
ACT

TCM6

11

13

PM

APS/PCC

14

RES

TCM4

TCM1

TCMACT: tandem connection

monitoring activation/deactivation
control channel
TCMi: tandem connection monitoring i
FTFL: fault type and fault location
reporting channel
PM: path monitoring
EXP: experimental
GCC1/2: general communication
channel 1/2
APS/PCC: automatic protection
switching coordination
channel/protection communication
control channel

12

GCC0

TCM5

ODUk OH

10

SM

MFAS

TCM2
GCC2

15

RES

17

RES JC

FTFL RES

EXP

16

JC

RES JC
PSI NJO

Alignment OH

FAS: frame alignment signal

MFAS: multiframe alignment signal

OPUk OH

PSI: payload structure identifier

JC: justification control

NJO: negative justification opportunity

OTUk OH

SM: section monitoring

GCC0: general communication
channel 0
RES: reserved for future international
standardization
Page14

Frame Alignment Signal

1

FAS

1
2

RES

TCM3
GCC1

Byte 1

MFAS

TCM
ACT

SM

TCM6

TCM2
GCC2

10

12

GCC0

TCM5

TCM4

TCM1

PM

APS/PCC

Byte 2

11

RES

Byte 3

Byte 4

13

14

RES

15

16

17

RES JC

FTFL RES JC
EXP

RES JC
PSI NJO

Byte 5

Byte 6

1 234 5 67 81 2 345 678 1 23 45 67 81 2 345 6 78 12 3 456 7812 34 56 78

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).

Page15

Multiframe Alignment Signal

1

FAS

RES

TCM3
GCC1

GCC2

TCM1

1
1
0
0

0
0
0
0
0
1
1
0
0

0
0
0
0
0
1
1
0
0

0
0
0
0
0

..
..

1
1
0
0

..

0
0
0
0
1
1
1
0
0

0
0
1
1
0
1
1
0
0

0
1
0
1
0
0
1
0
1

11

12

GCC0
TCM4
PM
RES

13

14

RES

15

16

17

RES JC

FTFL RES JC
EXP

RES JC
PSI NJO

Multiframe alignment signal (MFAS)

It is defined in row 1 and column 7.

The value of the MFAS byte is increased by

OTUk/ODUk frame and the MFAS byte provides

MFAS sequence

1
1
0
0

0
0
0
0
0

10

TCM5

APS/PCC

MFAS OH byte

0
0
0
0
0

SM

TCM6

TCM2

1 2 3 4 5 6
8
.

MFAS

TCM
ACT

a maximum of 256 multiframes.

Individual OTUk/ODUk overhead signals may

use this central multiframe to lock their 2, 4, 8,
16, or 32 multiframes to the main frame.

Page16

OTUk Section Monitoring Overhead

1

FAS

1
2

RES

TCM3
GCC2

BIP-8

SAPI
15
16

BEI/BIAE

RES

12

GCC0
TCM4
RES

13

14

RES

15

16

17

RES JC

FTFL RES JC
EXP

RES JC
PSI NJO

Trail trace identifier (TTI)

11

PM

APS/PCC
3

10

SM

TCM1

IAE

TTI

TCM5

BDI

TCM6

TCM2

MFAS

TCM
ACT

GCC1

31
32

A one-byte overhead is defined to transport 64byte TTI signals.

The 64-byte TTI signal should be aligned with the

OTUk multiframe and transmitted four times per

DAPI

multiframe.

Operator
specified

TTI structure:

16-byte SAPI: source access point identifier

16-byte DAPI: destination access point identifier

32-byte operator specified information

63

Page17

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

Frame i

3824

14 15

OPUk
BIP8

Frame i+1

Frame i+2

Page18

OTUk Section Monitoring Overhead

1

FAS

RES

TCM3
GCC1

TCM6

GCC2
2

TTI

BIP-8

SM

10

11

TCM1

APS/PCC

12

GCC0

TCM5

TCM2

MFAS

TCM
ACT

TCM4
PM
RES

13

14

RES

15

16

RES JC

FTFL RES JC
EXP

RES JC
PSI NJO

Backward error indication/backward

incoming alignment error (BEI/BIAE)

15
16

DAPI
31
32

Operator
specified

BEI/BIAE

IAE

SAPI

BDI

A four-bit BEI and BIAE signal is defined.

1

RES

This signal is used to transmit in the upstream

direction the count of interleaved-bit blocks
and incoming alignment error (IAE) conditions.
During an IAE condition the code "1011" is
inserted into the BEI/BIAE field and the error
count is ignored. Otherwise the error count (08) is inserted into the BEI/BIAE field.

63

Page19

OTUk Section Monitoring Overhead

1

FAS

1
2

RES

TCM3
GCC1

TCM6

GCC2

TTI

BIP-8

SM

10

11

TCM1

12

GCC0

TCM5

TCM2

MFAS

TCM
ACT

13

RES

TCM4
PM

APS/PCC

14

15

16

17

RES JC

FTFL RES JC
EXP

RES

RES JC
PSI NJO

Backward defect indication (BDI)

A single-bit BDI signal is defined to transmit

SAPI
15
16

DAPI
31
32

BEI/BIAE

IAE

BDI

the signal failure status detected by the

8

RES

section termination sink function in the

upstream direction.
BDI is set to "1" to indicate an OTUk
backward defect indication; otherwise, it is

Operator
specified

set to "0".

63

Page20

OTUk Section Monitoring Overhead

1

FAS

RES

TCM3
GCC1

MFAS

TCM
ACT

TCM6

TCM2
GCC2

10

SM

11

GCC0

TCM5
TCM1

12

TCM4
PM

APS/PCC

RES

13

14

RES

15

16

17

RES JC

FTFL RES JC
EXP

RES JC
PSI NJO

Incoming alignment error (IAE)

3

TTI

BIP-8

SAPI
15
16

A single-bit IAE signal is defined to allow the

S-CMEP ingress point to inform its peer S-

BEI/BIAE

IAE

BDI

RES

CMEP egress point that an alignment error in

the incoming signal has been detected.
IAE is set to "1" to indicate a frame

DAPI
31
32

alignment error; otherwise it is set to "0".

RES (reserved)
Operator
specified

Two bits are reserved (RES) for future

international standardization. They are set to

63

"00".
Page21

OTUk GCC0 and RES Overhead

1

RES

TCM3

FAS

GCC1

MFAS

TCM
ACT

TCM6

TCM2
GCC2

SM

10

11

GCC0

TCM5
TCM1

APS/PCC

12

TCM4
PM

13

14

RES

15

16

17

RES JC

FTFL RES JC
EXP

RES

RES JC
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 0s.

Page22

ODUk Path Monitoring Overhead

1

FAS

1
2

RES

TCM3

GCC1

GCC2

TTI

BIP-8

TCM1

GCC0
TCM4
RES

13

14

RES

15

16

17

RES JC

FTFL RES JC
EXP

RES JC
PSI NJO

TTI / BIP-8 / BEI / BDI

BDI

12

PM

APS/PCC
3

BEI

11

TCM5

For path monitoring, this overheads functions

are the same as those of the OTUk SM signal,

1 2 3 4 5 6 7 8
SAPI

10

SM

TCM6

TCM2

MFAS

TCM
ACT

except that BEI signals do not support the

STAT

15
16

BIAE function.
DAPI

31
32

They are located in row 3 and columns 10 to

12.

Operator
specified
63
Page23

ODUk Path Monitoring Overhead

1

FAS

1
2

RES

TCM3
GCC1

TCM6

TCM2
GCC2
2

TTI

BIP-8

15
16
DAPI
31
32
Operator
specified

SM

TCM1

BDI

12

GCC0
TCM4

13

14

RES

15

16

17

RES JC

FTFL RES JC
EXP

RES

STAT

11

PM

APS/PCC
3

BEI

10

TCM5

1 2 3 4 5 6 7 8
SAPI

MFAS

TCM
ACT

63

RES JC
PSI NJO

Status (STAT)
For path monitoring, three bits are defined as
status bits.
They indicate the presence of a maintenance
signal.
Bit 678

Status

000

Reserved for future international standardization

001

Normal path signal

010

Reserved for future international standardization

011

Reserved for future international standardization

100

Reserved for future international standardization

101

Maintenance signal: ODUk - LCK

Page24

ODUk PM delay measurement

(DMp)
For ODUk path monitoring, a one-bit path
delay measurement (DMp) signal is defined
to convey the start of the delay
measurement test.
DMp signal is inserted by the DMp
originating P-CMEP and sent to the far-end
P-CMEP, This far-end P-CMEP loops back the
DMp signal towards the originating P-CMEP

ODUk TCM Overhead

1

FAS

RES

TCM3
GCC1

TCM6

TCM2
GCC2

TTIi

BIP-8i

MFAS

TCM
ACT

10

SM

12

GCC0

TCM5
TCM1

TCM4
PM

APS/PCC

13

14

RES

15

16

RES JC

FTFL RES JC
EXP

RES

11

RES JC
PSI NJO

TTIi/BIP-8i/BEIi/BIAEi/BDIi

For each tandem connection monitoring

field, this overheads functions are the

1 2 3 4
SAPI

15
16

BEIi/BIAEi

5 6 7 8

BDIi

same as those of OTUk SM signals.

STATi

DAPI
31
32

Six fields of the ODUk TCM overhead

are defined in row 2 and columns 5 to
13, and row 3 and columns 1 to 9 of the

Operator
specific

ODUk overhead.

63
Page26

ODUk TCM Overhead

1

FAS

1
2

RES

TCM3

GCC1

GCC2

TTIi

BIP-8i

TCM1

15
16
DAPI
31
32
Operator
specified
63

BDIi

1 2 3 4 5 6 7 8
BEIi/BIAEi

STATi

TCM4

13

14

RES

15

16

17

RES JC

FTFL RES JC
EXP

RES

RES JC
PSI NJO

STAT (status)

SAPI

12

PM

APS/PCC
3

11

GCC0

TCM5

10

SM

TCM6

TCM2

MFAS

TCM
ACT

For each tandem connection monitoring

field, three bits are defined as status bits.
They indicate the presence of a
maintenance signal if there is an incoming
alignment error at the source TC-CMEP, or if
there is no source TC-CMEP active.
Bit 678
000
001
010

Status
No source TC
In use without IAE
In use without IAE

011

Reserved for future international standardization

100

Reserved for future international standardization

101

Maintenance signal: ODUk -LCK

110

Maintenance signal: ODUk

-OCI
Page27

Nested and Cascaded ODUk Monitored

Connections

A1

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

B1

C1

C2

B2

B3

B4

C1 - C2
B1 - B2

B3 - B4
A1 - A2

TCMi TCM OH field not in use

TCMi

TCM OH field in use

Page28

A2

Overlapped ODUk Monitored

Connections

A1

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

B1

C1

B2

C2

A2

C1 - C2
B1 - B2
A1 - A2
TCMi TCM OH field not in use TCMi

TCM OH field in use

Page29

ODUk TCM ACT Coordination Protocol

1

RES

TCM3

FAS

GCC1

TCM
ACT

MFAS
TCM6
TCM2

GCC2

SM

10

11

APS/PCC

13

GCC0

TCM5
TCM1

12

TCM4
PM
RES

14

RES

15

16

17

RES JC

FTFL RES JC
EXP

RES JC
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.

Page30

ODUk GCC1/GCC2
1

RES

TCM3

FAS

GCC1

MFAS

TCM
ACT

TCM6

TCM2
GCC2

SM

10

11

GCC0

TCM5
TCM1

APS/PCC

12

TCM4
PM
RES

13

14

RES

15

16

17

RES JC

FTFL RES JC
EXP

RES JC
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.

Page31

ODUk APS/PCC Channel

1

RES

TCM3

FAS

GCC1

MFAS

TCM
ACT

TCM6

TCM2
GCC2

SM

10

11

GCC0

TCM5
TCM1

APS/PCC

12

TCM4
PM
RES

13

14

RES

15

16

17

RES JC

FTFL RES JC
EXP

RES JC
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.
Page32

ODUk FTFL Channel

1

RES

TCM3

FAS

GCC1

MFAS

TCM
ACT

TCM6

TCM2
GCC2

SM

10

11

GCC0

TCM5
TCM1

APS/PCC

12

TCM4
PM
RES

13

14

RES

15

16

17

RES JC

FTFL RES JC
EXP

RES JC
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.

Page33

ODUk Experimental and Reserved Overhead

1

FAS

1
2

RES

TCM3

GCC1

MFAS

TCM
ACT

TCM6

TCM2
GCC2

SM

10

11

GCC0

TCM5
TCM1

APS/PCC

12

TCM4
PM
RES

13

14

RES

15

16

17

RES JC

FTFL RES JC
EXP

RES JC
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 0s.

Page34

OPUk Payload Structure Identifier

1

FAS

1
2

RES

TCM3

GCC1

MFAS

TCM
ACT

TCM6

TCM2
GCC2

SM

TCM1

GCC0
TCM4

13

14

RES

15

16

17

RES JC

FTFL RES JC
EXP

RES

RES JC
PSI NJO

Payload structure identifier

(PSI)
One byte is allocated in the OPUk

Mapping
and concatenation
specific
255

12

PM

APS/PCC

PT

11

TCM5

10

overhead to transport a 256-byte

payload structure identifier (PSI)
signal.
It is aligned with the ODUk
multiframe.
PSI[0] contains a one-byte payload
Page35
type. PSI[1] to PSI[255]
are mapping

Payload Type Code Points

Page36

MSB 1234

LSB 1234

Hex Code

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

1111

1101

FD

NULL test signal mapping

1111

1110

FE

PRBS test signal mapping

1111

1111

FF

Not available

Meaning

Reserved codes for proprietary use

OPUk Mapping Specific Overhead

1

FAS

1
2

RES

TCM3

GCC1

MFAS

TCM
ACT

TCM6

TCM2
GCC2

SM

10

11

GCC0

TCM5
TCM1

APS/PCC

12

TCM4
PM
RES

13

14

RES

15

16

17

RES JC

FTFL RES JC
EXP

RES JC
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.

Page37

Forward Error Correction (FEC)

Forward Error Correction (FEC)

Add redundancy to a message through encoding prior to transmission to enable the

receiver (decoder) to correct errors induced in the communication channel
Roughly 7%-25% of each OTN frame is dedicated to an error correcting code
Resulting in (choice of) lower error rates, lower transmission power, greater
transport distance
Standardized G.975 (Reed-Solomon) code and also proprietary enhanced codes

Reed-Solomon Code (RS) 255/239

239 base data bits

16 added overhead bits: (6.7% overhead)
Corrects for 8 or less bit errors in 239 bits

Log
BER

8 x 16 x 4 = 512 bits per OTU frame

Anything over 8 bits is completely uncorrected

Typical gain (NCG) is ~6.5 dB at 1e-12 BER
10-12

No FEC
With FEC
~6.5dB Gain @ 10-12 BER

Enhanced FEC schemes are defined in ITU-T G975.1

Defines super FEC codes that have higher correction ability than
RS (255, 239)
OSNR (dB)
G.975.1 - I.4 and I.7 are popular

FEC
The OTUk (k=1,2,3,4) forward error correction (FEC) contains
the Reed-Solomon RS(255,239) FEC codes. Transmission of the
OTUk FEC is mandatory for k=4 and optional for k=1,2,3. If no
FEC is transmitted, fixed stuff bytes (all-0s pattern) are to be
used

For interworking of equipment supporting FEC, with equipment

not supporting FEC (inserting fixed stuff all-0s pattern in the
OTUk (k=1,2,3) FEC area), the FEC supporting equipment shall
support the capability to disable the FEC decoding process
(ignore the content of the OTUk (k=1,2,3) FEC)

Client Signal Mapping Methods

o

Mapping methods provide a means for rate adapting a client signal into a
server layer container (ODUj or ODUflex)

Bit-synchronous Mapping Procedure (server rate synchronous to client rate)

Bit synchronously maps client signal into server layer payload area

Asynchronous Mapping Procedure (client and server rates asynchronous)

Three methods: Asynchronous Mapping Procedure (AMP), Bit-synchronous Mapping

Procedure (BMP) and Generic Mapping Procedure (GMP)
Mapping may also utilize client signal transcoding (e.g., GFP, 1024B/1027B, etc)

Monitors client rate relative to server rate (derived from local oscillator) and
performs stuffing operations once per lower rate container frame (negative and
positive justification operations)
Signals stuffing operations through justification control bits to far end (demux)

Generic Mapping Procedure (client and server rates synchronous or

asynchronous)

Monitors client rate relative to server rate, adjusts number of bytes sent per server
frame, and distributes bytes evenly throughout server frame
Signals bytes (and residual bits) per frame via C m and CnD control bits to far end
(demux)

GMP Mapping
Payload Area

0
Pserver

OH
client data

stuff

Pserver?

enable

client
data
indication
=
read/write
enable

memory

payload area
frame start
clock

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

41

ODUflex
TSi TSj
Services with
a fixed bit rate

BMP

Client signals

Packet services
Client services

OH

GMP

OH

ODUflex
GFP

OH

TSi TSj

GMP
OH

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.

42

OTN Mapping Procedure Summary

Mapping method

Application

Asynchronous Mapping
Procedure (AMP)

Mapping SONET/SDH client signals into OTN

Bit-synchronous Mapping
Procedure (BMP)

Alternative method for mapping SONET/SDH client signals into

OTN
Mapping CBR clients into ODUflex(CBR)

Generic Mapping Procedure

(GMP)

Mapping non-SONET/SDH CBR clients into ODUk (k = 0, 1, 2, 3, 4)

and low rate TDM clients into ODU0

Timing Transparent
Transcoding (TTT) using a
combination of GFP and GMP

Transcoding the native client signal into a lower bit rate CBR
stream in order to increase bandwidth efficiency, and maintain
client character and timing information transparency

GFP frames or ATM cells into

an OPU payload container

Mapping packet clients into ODUk (k = 0, 1, 2, 3, 4) with GFP

(Generic Framing Procedure) encapsulation
Mapping packet clients into an ODUflex(GFP) with GFP
encapsulation
Mapping ATM (Asynchronous Transfer Mode) cells into OTN

Overclocked OTN
o OTN line rates were originally defined to match SONET/SDH signals.
Unfortunately, the 10 GigE LAN PHY signal (10.3125 Gbit/s) does not fit into a
standard OPU2 (9.995 Gbit/s) payload rate.
o Overclocking enables the transport of 10 GbE LAN signals transparently over
OTN networks as per ITU-T series G supplement 43. Offers real bit
transparency of 10GbE LAN signals.
o Compensates for rate mismatch between 10GbE LAN and the OPU2 payload
by raising the overall OTU2 data rate from the standard 10.709 Gbit/s to fit
the 10GbE LAN client signal.
o Over-clocked OTN supports the following optical line rates for mapping and
multiplexing 10GigE LAN signals (10G FC is also an overclocked rate, i.e.
OTU1f and OTU2f):

OTU2e: 11.0957
OTU1e: 11.0491
OTU3e1: 44.569
OTU3e2: 44.583

Gbits/s
Gbits/s
Gbits/s
Gbits/s

100
100
100
100

ppm
ppm
ppm (for multilpexing ODU1e)
ppm (for multilpexing ODU2e)

o The transparent transportation of 10 GigE LAN signals means that the full 10
Gigabit Ethernet data rate (10.3125 Gbit/s) is transported over OTN, including
PCS 64B/66B coded information, inter-frame filler (IPG), MAC FCS, preamble,
start-of-frame delimiter (SFD) and ordered sets (remote fault indication).

Client Signal Mapping Summary

Client Signal

OPUk

Justificatio Comment
n Method

OPU0
OPU0

GMP
GMP

CBR clients:
OPU1
1.238 Gbit/s < client 2.488
Gbit/s
STS-48
OPU1

GMP

1GE
CBR clients: 1.238 Gbit/s

Uses GFP-T
Includes STM-1,
STM-4, FC-100
Includes FC-200

AMP or BMP

STS-192

OPU2

AMP or BMP

10GE LAN PHY

OPU2e

BMP

Fiber Channel FC-1200

STS-768

OPU2e
OPU3

BMP
Uses TTT/GFP-T
AMP or BMP

40GE
100GE

OPU3
OPU4

GMP
GMP

Transcoded

OPUflex(CBR)

BMP

OPUk,
k=0,1,2,3,4
OPUflex(GFP)

GFP Idles

Includes FC400,
FC-800, IB-SDR,
IB-DDR, IB-QDR
GFP-F

GFP Idles

GFP-F

CBR clients: client > 2.488

Gbit/s
Packet clients
Packet client streams

ODU Definitions

ODU0 Definition
o Smallest container defined in G.709 (OTN Standard)

1.25G container size (specifically 1.244160 Gbit/s, +/- 20ppm)

Established in October 2009 for transport of Gigabit Ethernet

o Sized to fit existing OTN hierarchy

x
x
x
x

2 into ODU1
8 into ODU2
32 into ODU3
80 into ODU4

o ODU0 can carry:

1GbE
OC-3
OC-12
1G-FC

o No OTU0 physical layer

Only a lower order wrapper for 1GbE mapped into standardized

physical layers
OTU1 and above

ODU1 Definition
o Original tier of the hierarchy to transport 2.5G signals

ODU1 = 2.498775Gbit/s
OTU1 = 2.666057Gbit/s
Can be used as a higher order ODU to carry lower order ODU0s

o Divided into 2 x 1.25G tributary slots:

ODU0 maps into 1 tributary slot

o OPU1 can carry:

OC-48
2G-FC

ODU2 Definition
o Original tier of the hierarchy to transport 10G signals

ODU2 = 10.037273Gbit/s
OTU2 = 10.709224Gbit/s
Can be used as a higher order ODU to carry lower order ODUs

o Divided into 4 x 2.5G or 8 x 1.25G tributary slots:

ODU0 maps into 1 tributary slot

ODU1 maps into 1 x 2.5G or 2 x 1.25G tributary slot(s)
ODUflex maps into 1-8 x 1.25G tributary slots

o OPU2 can carry:

OC-192

ODU2e Definition
o Newer Low Order (LO) tier of the hierarchy (Oct 2009) to
transport proprietary 10G signals

Serves as a logical wrapper for 10GbE when carried over a

standardized physical layer of OTU3 or OTU4
Part of compromise made to enable standards progress - most
commonly deployed proprietary transparent mapping of 10GbE
Over-clocked physical OTU2e signal remains in G.sup43

o Can map 10 into OPU4 (which is sized to carry 100GBASER)

o Can map as ODUflex in 9 x 1.25G OPU3 tributary slots
(up to 3 ODU2e per OPU3)

o OPU2e can carry:

10GbE
Transcoded 10GFC

ODU3 Definition
o Original tier of the hierarchy to transport 40G
signals

ODU3 = 40.319218Gbit/s
OTU3 = 43.018410Gbit/s
Can be used as a higher order ODU to carry lower order

ODUs

o Divided into 16 x 2.5G or 32 x 1.25G tributary

slots:

ODU0 maps into 1 tributary slot

ODU1 maps into 1 x 2.5G or 2 x 1.25G tributary slot(s)
ODU2 maps into 4 x 2.5G or 8 x 1.25G tributary slot(s)
ODU2e maps into 9 x 1.25G tributary slots
ODUflex maps into 1-32 x 1.25G tributary slots

o OPU3 can carry:

OC-768
Transcoded 40GbE

ODU4 Definition
o Newer tier of the hierarchy (Oct-09)

ODU4 = 104.794445Gbit/sBased on support for 100GE or (10 OC192/STM64

OTU4 = 111.809973Gbit/s239/227)
Can be used as a higher order ODU to carry lower order ODUs

o Divided into 80 x 1.25G tributary slots:

ODU0 maps into 1 tributary slot

ODU1 maps into 2 tributary slots
ODU2 or ODU2e maps into 8 tributary slots
ODU3 maps into 32 tributary slots
ODUflex maps into 1-80 tributary slots

o OPU4 can carry:

100GBase-R

ODUflex Description
o Flexible ODU rate for transport of arbitrary client rates to improve HO ODUk
bandwidth utilization (transport efficiency, basically replaces VCAT)
o Provides a single variable size container for client mapping
o Two forms of client signal to ODUflex mapping:

Constant Bit Rate (CBR) client signals

ODUflex Rate = 239/238 x CBR rate with up to 100ppm clock tolerance (bitsynchronous to client clock, BMP)
Ex. ODUflex (CBR) carrying FC-400 is 4.268Gbit/s (239/238 x
4.250Gbit/s) 100 ppm

GFP-F mapped packet client signals

Chosen to be multiples of tributary slot (TS) rate
ODUflex Rate = N TS with 100ppm clock tolerance
Client mapped to ODUflex then to 5 x 1.25Gbps HO Tributary Slots
6
Gbps
Client

~6G
ODUFlex

10G ODU2

Re-usable Capacity
Wasted Capacity

Client mapped to ODU2 then to 8 x 1.25Gbps HO Tributary Slots

Multiplexing

High and Low Order ODUs

The terminology Low Order ODU (LO ODU) and High Order ODU (HO
ODU) were introduced to distinguish the function being served by
the ODU in that application:

LO ODU: Lower Order ODU. The LO ODUj (j can be 0, 1, 2, 2e, 3, 4, or flex)

represents the container transporting a client of the OTN that is either
directly mapped into an OTUk (k = j) or multiplexed into a server HO ODUk
(k > j) container. When an ODUk is being discussed in terms of carrying a
client signal, it is referred to as a LO ODUk. For example, client signals are
mapped into the OPU of a LO ODU. ODUj is often used to refer to ODU
entities acting as LO ODU.
HO ODU: Higher Order ODU. The HO ODUk (k can be 1, 2, 2e, 3, or 4)
represents the entity transporting a multiplex of LO ODUj tributary signals in
its OPUk area. Essentially, an ODUk that directly becomes an OTUk is
referred to as a HO ODU. ODUk is often used to refer to ODU entities used as
an HO ODU.

High and Low Order ODUs

The concepts of lower order and high order ODU are specific to the role that the ODU plays within a
single domain. The same ODU can be both LO and HO, depending on the functional context. For
example, a client signal is mapped into a LO ODUk, but if that ODUk is transmitted directly within an
OTUk, then the ODUk is also a HO ODU.
Intermediate carrier applications create a similar situation. The HO ODUk transmitted by the end carrier
may have multiple LO ODU signals multiplexed into it. When the intermediate carrier multiplexes this
ODUk into a higher rate HO ODUj for transparent transport, the intermediate carrier is treating the
ODUk as a LO ODU. High and Low order ODUs can also be referred to simply by using (L) or (H) as in the
example below.
Client

ODU3 (L)

OPU3

ODU3 (H)

ODTU13
ODTU23
x4

x16

Client

OPU3

OPU2

ODU2 (L)

OPU2

ODU2 (H)

or

OTU3

OCh

43.018G

OTU2

OCh

10.709G

OTU1

OCh

2.666G

40.319G

or

10.037G
ODTU12
x4
Client

OPU1

ODU1 (L)

2.499G
Mapping
Multiplexing

ODUk (L) = Low Order ODU

ODUk (H) = High Order ODU

ODU Multiplexing

OPU2 OH

Align
Align
Align
AlignODU1

Align
AlignODU1

OPU1 OH

ODU1 OH

OH
ODU1 OH
ODU1 OH

ODU1 OH

OPU Client Signal

OPU
k Payload

OH
ODU1 OH
ODU1 OH

OPU1 OH

OTU2

ODU2 OH

OPU1 OH

(OC-48) is mapped into an ODU1

frame. Four of these 2.5 Gbps
containers can be mapped into an
Alignm
OPU2 frame and then wrapped
with additional OH and FEC for
ODU2 OH
transport in an OTU2. This is
ODU2
single-stage multiplexing (ODU1
ODU2), but multistage
multiplexing is defined as well,
Align
Alignm OTU2 OH
e.g. ODU1 ODU2 ODU3.
Align

SONET OC48

OPU1 OH

OTN standards have evolved to include a

standard multiplexing hierarchy, defining
exactly how the lowerrate signals map into higher-rate payloads. This
allows any OTN switch and WDM platform to
electronically groom and switch lower-rate
services within 10 Gbps, 40 Gbps, or 100 GbpsAlign
wavelengths.
ODU1 OH
As an example, a 2.5 Gbps signal
ODU1

OPU Client Signal

OPU Client Signal
OPU Client Signal
OPU Client Signal

OPU Client Signal

OPU Client Signal
OPU Client Signal
OPU Client Signal

OTU2
FEC

Client

Standard G.709 Mapping and Multiplexing

Structure
OPU4

ODU4 (L)

OPU4

ODU4 (H)

or

OTU4

OCh

111.809
G

or

OTU3

OCh

43.018G

or

OTU2

OCh

10.709G

or

OTU1

OCh

2.666G

104.794G

x80

x40

x10

ODTU4.ts
x10

Client

x32

10GbE

OPU2e

ODU2e (L)

Client

OPU2

ODU2 (L)

OPU2

ODU2 (H)

x8

Client

x4

OPU1

ODU1 (L)

OPU1

ODU1 (H)

OPU3

ODU3 (L)

OPU3

ODU3 (H)

ODTU3.ts
ODTU13
x3
x4 ODTU23

x16

ODTU2.ts
ODTU12

x80/ts

x2

40.319G
x32/ts

10.037G
x8/ts

2.499G
x2

ODTU01

ODUflex (L)

OPUflex

Client

Client
OPU0

ODU0 (L)

1.244G

Mapping

ODUk (L) = Low Order ODU

Multiplexing

ODUk (H) = High Order ODU

Non-standard rates not shown

OTN Multiplexing and Mapping Structure

59

OTN Multiplexing and Mapping Structure

60