You are on page 1of 57

OTN NEWBIES

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

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 management

G.874 G.874.1 G.8251

Management features of NEs on an OTN network OTN network: Protocol-neutral management information model for the network element Jitter and shift control on an OTN network

Jitter and performance

G.8201
G.873.1 G.873.2 G.798 G.806

Bit error performance parameters and specifications on international channels of multiple carriers on an OTN network
Linear protection on an OTN network Ring protection on an OTN network Features of function blocks of equipment on an OTN network Transport network equipment features: description methods and general functions Ports on an OTN network Generic frame protocol (GFP) Link capacity adjustment scheme (LCAS) for virtual concatenation signals Physical-layer ports on an OTN network Optical ports for intra-office systems Optical security rule and requirements in an optical transport system OTN network structure ASON network structure

Network protection

OTN

Equipment functions and features

G.709
Structure and mapping

G.7041 G.7042 G.959.1

Physical-layer features

G.693 G.664 G.872

Structure

G.8080

OTN NETWORK LAYERS AND PORT STRUCTURE


OPUk: optical channel payload unit-k ODUk: optical channel data unit-k IP/MPLS ATM Ethernet STM-N

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

OPUk ODUk (ODUkP and ODUkT) OTUk OTUkV OTUk OTUkV

OCh OMSn OTSn


OTM-n.m

OChr OPSn
OTM-0.m OTM-nr.m

OPS: optical physical section


OTM: optical transport module

Page10

OTM-N.M CONTAINMENT RELATIONSHIPS


Client signal
OPUk OH ODUk OH OTUk[V] OH OCh
Non-associated OH Common management OCCo OH OChOH

OPUk payload OPUk ODUk OCh payload FEC


OTM-n. m

l2 l1 l
OSC

OCG-n.m
OMU-n.m OTM-n.m

OCCo

OCCo

OCCp

OCCp

OCCp
OTM overhead signal (OOS)

OMSn OH

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 OTM-16r.m OPUk OH ODUk OH OTUk[V] OH OChr

l 16

OPUk payload OPUk

ODUk
OCh payload OCCp

FEC

l l

2 1

OCG-nr.m OCCp OTM-nr.m

OCCp

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


OTM-0.m
Client signal OPUk OH ODUk OH OTUk[V] OH OChr OTM-0.m

OPUk payload OPUk ODUk OCh payload OPS0 FEC

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
USER A OTM UNI OTM NNI IaDI-IaVI Network Operator B OTM NNI IaDI-IrVI OTM NNI IaDI-IaVI OTM NNI IrDI Network Operator C

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

1 i+j+k n
OTM-nr.m OCG-nr.m

i j k

OCCr

1 OChr 1 1

1 1 1
OTU2[V]

OCCr

OChr

OTU3[V]

ODU3

Client signal
OPU3

OCCr

OChr

16
ODTUG3

4
ODU2

Client signal
OPU2

Client signal

1 i+j+k n
OTM-n.m OCG-n.m

OCC

OCh

1 1 1
OTU1[V]

ODTUG2
4

ODU1

OPU1

j OCC 1 OCh k 1

OCC

OCh

OSC

Multiplexing
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


OPUflex

1.25G ODU0 10.3G ODU2e

104G ODU4
ODUflex
40.149G

OPUflex(GFP)

OPU3

OPUflex

10.312G 9.995G

OPU2e OPU2
OPUflex

2.488G

OPU1
1.238G

OPU0

LO OPU

19

OPU4/21
(ODU0, ODU1, ODU2, ODU2e, ODU3, ODU3e2, ODUflex)

OPU3e2/21
(ODU0, ODU1, ODU2, ODU2e, ODUflex)

OPU3/21
(ODU0, ODU1, ODU2, ODU2e, ODUflex)

OPU3/20
(ODU1, ODU2)

OPU2/21
(ODU0, ODU1, ODUflex)

OPU2/20
(ODU1)

LO ODU rate

OPU1
(ODU0)

OTN LINE BEARING CAPABILITY (HO ODU)

ODUflex

ODUflex(GFP) ODUflex

ODUflex

ODU3e2 ODU3

ODU2e ODU2

ODU4

ODU1

New HO ODU signals

Signals with extended

41.7GG ODU3e2

104G ODU4

2.5G ODU1

capabilities

(G.sup43)

40G ODU3

10G ODU2

ODU0

HO OPU

20

OTUK FRAME RATE


OTUk rate = 255/(239 - k) x STM-N frame rate

OTU Type OTU1 OTU2 OTU3 OTU4

OTU Nominal Bit Rate 255/238 x 2488320 kbit/s 255/237 x 9953280 kbit/s 255/236 x 39813120 kbit/s 255/227 x 99532800 kbit/s

OTU Bit Rate Tolerance

20 ppm

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 ODU0 ODU1 ODU2 ODU3 ODU4 ODU2e ODUflex for CBR client signals ODU Nominal Bit Rate 1244160 kbit/s 239/238 x 2488320 kbit/s 239/237 x 9953280 kbit/s 239/236 x 39813120 kbit/s 239/227 x 99532800 kbit/s 239/237 x 10312500 kbit/s 239/238 x Client signal bit rate Client signal bit rate tolerance, with a maximum of 100 ppm Pre-set bit rate 20 ppm 100 ppm ODU Bit Rate Tolerance

20 ppm

ODUflex for GFP-F mapped client signals

OPUK FRAME RATE


OPUk payload rate = 238/(239 - k) x STM-N frame rate
OPU Type OPU0 OPU1 OPU2 OPU3 OPU4 OPU2e OPUflex for CBR client signals OPUflex for GFP-F mapped client signals OPU Payload Nominal Bit Rate 238/239 x 1244160 kbit/s 2488320 kbit/s 238/237 x 9953280 kbit/s 238/236 x 39813120 kbit/s 238/227 x 99532800 kbit/s 238/237 x 10312500 kbit/s Client signal bit rate 100 ppm Client signal bit rate tolerance, with a maximum of 100 ppm 20 ppm 20 ppm OPU Payload Bit Rate Tolerance

238/239 x ODUflex signal rate

OPU1-Xv OPU2-Xv

X x 2 488 320 kbit/s 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 ODTU12 JOH

ODU1 payload

ODU1

ODU1

ODTU12

ODTU12 JOH

ODTU12 JOH

ODU1

ODU1

ODTUG2

ODTUG2

OPU2 OH ODU2 OH

OPU2 payload

OPU2

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.

OPU1 OH

Alignment

ODU1

ODU1OH

Client-layer signal (STM-16, ATM, or GFP)

x4
OPU1 OH OPU1 OH OPU1 OH

OPU2 OH

ODU2

ODU2 OH

OPU2 OH

OTU2 ODU2 OH

OPU1 OH

Client Layer Signal Alignment Client Layer Signal (for example, STM-16) ODU1 OH Client Layer Signal Client-layer signal (for example, STM-16) ODU1 OH (for example, STM-16) ODU1 OH (STM-16, ATM, or GFP) ODU1 OH

OPU1 OH OPU1 OH OPU1 OH

Alignment

OTU2 OH

OPU1 OH

Alignment

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

OPU2 Payload

OTU2 FEC

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 OH ODTU23 JOH

ODU2 payload

ODU2 ODTU23 ODTU13 JOH

ODU1 ODU1 payload OH ODU1

ODU1 ODTU13

ODU2

ODTU13 JOH

ODTU13 ODTU23 JOH JOH

ODTU23 JOH

ODU2

ODU2

ODU1

ODU1

ODTUG3

ODTUG3 OPU3 OH ODU3 OH

OPU3 payload

OPU3

ODU3 payload

ODU3

Page27

GMP Mapping
Payload Area OH client data
client data indication = read/write enable Cm(t) 0 Pserver Pserver? enable memory

payload area frame start clock

stuff

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 a fixed bit rate Client signals BMP GMP

OH
ODUflex

OH

TSi TSj Packet services Client services


GFP OH ODUflex

GMP OH

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

Non-associated overhead

TTI
BDI-O OMSn BDI-P OTSn PMI

FDI-P
2

OOS functions subject to standardization. Bit rate and format are not standardized.

BDI-O BDI-P PMI OCh

FDI-O
FDI-P 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 BDI-O OTSn BDI-P PMI

MI_TxTI dLOS_P RI_BDI-O RI_BDI-P 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)


3824

2 3 4

OPUk OH

Alignment

OTUk OH

ODUk OH

Client signal mapped in OPUk OPU k payload

3825

OTUK FEC

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

OTUk - Optical Channel Transport Unit


Alignment

Page33

4080

14 15 16 17

7 8

33

OTN ELECTRICAL OVERHEAD OVERVIEW


1 1 2 3 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

FAS RES TCM3 GCC1 GCC2


TCM ACT

MFAS

SM TCM5

GCC0 TCM4 PM RES

RES EXP

RES JC RES JC PSI NJO

TCM6 TCM2 APS/PCC

FTFL RES JC

TCM1

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 FTFL: fault type and fault location reporting OPUk OH PSI: payload structure identifier channel JC: justification control PM: path monitoring NJO: negative justification opportunity EXP: experimental GCC1/2: general communication channel OTUk OH 1/2 SM: section monitoring APS/PCC: automatic protection switching GCC0: general communication channel 0 coordination channel/protection RES: reserved for future international communication control channel standardization
Page34

FRAME ALIGNMENT SIGNAL


1 1 2 3 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

FAS
RES
TCM ACT

MFAS
TCM6 APS/PCC Byte 3

SM
TCM5

GCC0
TCM4

RES EXP

RES JC
RES JC PSI NJO

FTFL RES JC

TCM3
GCC1 Byte 1 OA1 GCC2

TCM2

TCM1

PM
RES Byte 4 OA2

Byte 2 OA1

Byte 5 OA2

Byte 6 OA2

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

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 1 2 3 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

FAS
RES
TCM ACT

MFAS
TCM6 APS/PCC

SM
TCM5

GCC0
TCM4

RES EXP

RES JC
RES JC PSI NJO

FTFL RES JC

TCM3
GCC1 GCC2

TCM2

TCM1

PM
RES

MFAS OH byte 1 2 3 4 5 6
. .

7 8

Multiframe alignment signal (MFAS)

It is defined in row 1 and column 7.

0 0 0 0 0

0 0 0 0 0

0 0 0 0 0

0 0 0 0 0

. . . .

0 0 0 0 0

0 0 0 0 1

0 0 1 1 0

0 1 0 1 0

The value of the MFAS byte is increased by


OTUk/ODUk frame and the MFAS byte provides a maximum of 256 multiframes.

MFAS sequence

Individual OTUk/ODUk overhead signals may use this

1 1 0 0

1 1 0 0

1 1 0 0

1 1 0 0

. .

1 1 0 0

1 1 0 0

1 1 0 0

0 1 0 1

central multiframe to lock their 2, 4, 8, 16, or 32


multiframes to the main frame.

Page36

OTUK SECTION MONITORING OVERHEAD


1 1 2 3 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

FAS
RES
TCM ACT

MFAS
TCM6 APS/PCC

SM
TCM5

GCC0
TCM4

RES EXP

RES JC
RES JC PSI NJO

FTFL RES JC

TCM3
GCC1 GCC2

TCM2

TCM1

PM
RES

Trail trace identifier (TTI)

TTI

BIP-8

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


signals.

BDI

SAPI
15 16

IAE

BEI/BIAE

RES

The 64-byte TTI signal should be aligned with the OTUk multiframe and transmitted four times per multiframe.

DAPI
31 32

TTI structure:

Operator specified
63

16-byte SAPI: source access point identifier 16-byte DAPI: destination access point identifier 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.

14

15

3824

Frame i Frame i+1

OPUk
BIP8

Frame i+2

Page38

OTUK SECTION MONITORING OVERHEAD


1 1 2 3 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

FAS
RES
TCM ACT

MFAS
TCM6 APS/PCC

SM
TCM5

GCC0
TCM4

RES EXP

RES JC
RES JC PSI NJO

FTFL RES JC

TCM3
GCC1 GCC2

TCM2

TCM1

PM
RES

Backward

TTI

BIP-8

error indication/backward incoming alignment error (BEI/BIAE)

A four-bit BEI and BIAE signal is defined. This signal is used to transmit in the upstream direction the count of interleaved-bit blocks and incoming alignment error (IAE) conditions.

BDI

IAE

SAPI
15 16

BEI/BIAE

RES

DAPI
31 32

Operator specified
63

During an IAE condition the code "1011" is inserted into the BEI/BIAE field and the error count is ignored. Otherwise the error count (0-8) is inserted into the BEI/BIAE field.

Page39

OTUK SECTION MONITORING OVERHEAD


1 1 2 3 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

FAS
RES
TCM ACT

MFAS
TCM6 APS/PCC

SM
TCM5

GCC0
TCM4

RES EXP

RES JC
RES JC PSI NJO

FTFL RES JC

TCM3
GCC1 GCC2

TCM2

TCM1

PM
RES

Backward

defect indication (BDI)

TTI

BIP-8

A single-bit BDI signal is defined to transmit the signal failure status detected by the section

BDI

SAPI
15 16

IAE

BEI/BIAE

RES

termination sink function in the upstream direction.


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

DAPI
31 32

Operator specified
63

Page40

OTUK SECTION MONITORING OVERHEAD


1 1 2 3 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

FAS
RES
TCM ACT

MFAS
TCM6 APS/PCC

SM
TCM5

GCC0
TCM4

RES EXP

RES JC
RES JC PSI NJO

FTFL RES JC

TCM3
GCC1 GCC2

TCM2

TCM1
Incoming

PM
RES

alignment error (IAE)

TTI

BIP-8

A single-bit IAE signal is defined to allow the SCMEP ingress point to inform its peer S-CMEP egress point that an alignment error in the incoming

BDI

IAE

SAPI
15 16

BEI/BIAE

RES

signal has been detected.


IAE is set to "1" to indicate a frame alignment error; otherwise it is set to "0".
RES

DAPI
31 32

(reserved)

Operator specified
63

Two bits are reserved (RES) for future international


standardization. They are set to "00".

Page41

OTUK GCC0 AND RES OVERHEAD


1 1 2 3 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

FAS
RES
TCM ACT

MFAS
TCM6 APS/PCC

SM
TCM5

GCC0
TCM4

RES EXP

RES JC
RES JC PSI NJO

FTFL RES JC

TCM3
GCC1 GCC2

TCM2

TCM1

PM
RES

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.

Page42

ODUK PATH MONITORING OVERHEAD


1 1 2 3 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

FAS
RES
TCM ACT

MFAS
TCM6 APS/PCC
3

SM
TCM5

GCC0
TCM4

RES EXP

RES JC
RES JC PSI NJO

FTFL RES JC

TCM3
GCC1
1 TTI

TCM2
GCC2
2 BIP-8

TCM1

PM
RES

TTI / BIP-8 / BEI / BDI

For path monitoring, this overheads functions are

SAPI 15 16 DAPI 31 32 Operator specified 63

BEI

BDI

1 2 3 4 5 6 7 8 STAT

the same as those of the OTUk SM signal, except


that BEI signals do not support the BIAE function. They are located in row 3 and columns 10 to 12.

Page43

ODUK PATH MONITORING OVERHEAD


1 1 2 3 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

FAS
RES
TCM ACT

MFAS
TCM6 APS/PCC
3

SM
TCM5

GCC0
TCM4

RES EXP

RES JC
RES JC PSI NJO

FTFL RES JC

TCM3
GCC1
1

TCM2
GCC2
2

TCM1

PM
RES

Status (STAT)

TTI

BIP-8

For path monitoring, three bits are defined as status bits. They indicate the presence of a maintenance signal.
Status Reserved for future international standardization Normal path signal Reserved for future international standardization Reserved for future international standardization Reserved for future international standardization Maintenance signal: ODUk - LCK
Page44

SAPI 15 16 DAPI 31 32 Operator specified 63

BEI

BDI

7 STAT

8 Bit 678 000 001 010 011 100 101

ODUK TCM OVERHEAD


1 1 2 3 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

FAS RES TCM3 GCC1


1 TTIi TCM ACT

MFAS TCM6 APS/PCC


3

SM TCM5

GCC0 TCM4 PM RES

RES EXP

RES JC RES JC PSI NJO

FTFL RES JC

TCM2 GCC2
2 BIP-8i

TCM1

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

For each tandem connection monitoring field,


this overheads functions are the same as those of OTUk SM signals.

0 SAPI 15 16 DAPI

BEIi/BIAEi

BDIi

STATi

Six fields of the ODUk TCM overhead are

31 32
Operator specific 63

defined in row 2 and columns 5 to 13, and


row 3 and columns 1 to 9 of the ODUk overhead.

Page45

ODUK TCM OVERHEAD


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

1
2 3 4

FAS RES TCM3 GCC1


1 TCM ACT

MFAS TCM6 APS/PCC


3

SM TCM5

GCC0 TCM4 PM RES

RES EXP

RES JC RES JC PSI NJO

FTFL RES JC

TCM2 GCC2
2

TCM1

STAT (status)

TTIi

BIP-8i

0 SAPI 15 16 DAPI 31 32 Operator specified 63

3 4

5 BDIi

7 8

BEIi/BIAEi

STATi

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 TCCMEP active.
Bit 678 000 001 010 011 100 101 Status

No source TC In use without IAE In use without IAE


Reserved for future international standardization Reserved for future international standardization Maintenance signal: ODUk -LCK

110

Maintenance signal: ODUk -OCI

Page46

NESTED AND CASCADED ODUK MONITORED CONNECTIONS


TCM6 TCM5 TCM4 TCM3 TCM2 TCM1 TCM6 TCM5 TCM4 TCM3 TCM2 TCM1 TCM6 TCM5 TCM4 TCM3 TCM2 TCM1 TCM6 TCM5 TCM4 TCM3 TCM2 TCM1 TCM6 TCM5 TCM4 TCM3 TCM2 TCM1 TCM6 TCM5 TCM4 TCM3 TCM2 TCM1 TCM6 TCM5 TCM4 TCM3 TCM2 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 TCM5 TCM4 TCM3 TCM2 TCM1 TCM6 TCM5 TCM4 TCM3 TCM2 TCM1 TCM6 TCM5 TCM4 TCM3 TCM2 TCM1 TCM6 TCM5 TCM4 TCM3 TCM2 TCM1 TCM6 TCM5 TCM4 TCM3 TCM2 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 1 2 3 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

FAS RES TCM3 GCC1 GCC2


TCM ACT

MFAS TCM6 TCM2 APS/PCC TCM1

SM TCM5

GCC0 TCM4 PM RES

RES EXP

RES JC RES JC PSI NJO

FTFL RES JC

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 1 2 3 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

FAS RES TCM3 GCC1 GCC2


TCM ACT

MFAS TCM6 APS/PCC TCM2 TCM1

SM TCM5

GCC0 TCM4 PM RES

RES EXP

RES JC RES JC PSI NJO

FTFL RES JC

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 1 2 3 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

FAS RES TCM3 GCC1 GCC2


TCM ACT

MFAS TCM6 APS/PCC TCM2 TCM1

SM TCM5

GCC0 TCM4 PM RES

RES EXP

RES JC RES JC PSI NJO

FTFL RES JC

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 1 2 3 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

FAS RES TCM3 GCC1 GCC2


TCM ACT

MFAS TCM6 APS/PCC TCM2 TCM1

SM TCM5

GCC0 TCM4 PM RES

RES EXP

RES JC RES JC PSI NJO

FTFL RES JC

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
2 3 4

FAS RES TCM3 GCC1 GCC2


TCM ACT

MFAS TCM6 APS/PCC TCM2 TCM1

SM TCM5

GCC0 TCM4 PM RES

RES EXP

RES JC RES JC PSI NJO

FTFL RES JC

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.

Page53

OPUK PAYLOAD STRUCTURE IDENTIFIER


1 1 2 3 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

FAS RES TCM3 GCC1 GCC2


TCM ACT

MFAS TCM6 APS/PCC TCM2 TCM1

SM TCM5

GCC0 TCM4 PM RES

RES EXP

RES JC RES JC PSI NJO

FTFL RES JC

0 1

Payload structure identifier (PSI)

PT

One byte is allocated in the OPUk

overhead to transport a 256-byte payload


Mapping and concatenation specific
255

structure identifier (PSI) signal.


It is aligned with the ODUk multiframe. PSI[0] contains a one-byte payload type. PSI[1] to PSI[255] are mapping and concatenation specific.
Page54

PAYLOAD TYPE CODE POINTS


MSB 1234 0000 0000 0000 0000 0000 LSB 1234 0001 0010 0011 0100 0101 Hex Code 01 02 03 04 05 Experimental mapping Asynchronous CBR mapping Bit synchronous CBR mapping ATM mapping GFP mapping Meaning

0000
0001 0001 0010 0101

0110
0000 0001 0000 0101

06
10 11 20 55

Virtual Concatenated signal


Bit stream with octet timing mapping Bit stream without octet timing mapping ODU multiplex structure Not available

0110
1000 1111

0110
xxxx 1101

66
80-8F FD

Not available
Reserved codes for proprietary use NULL test signal mapping

1111
1111 Page55

1110
1111

FE
FF

PRBS test signal mapping


Not available

OPUK MAPPING SPECIFIC OVERHEAD


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

1
2 3 4

FAS RES TCM3 GCC1 GCC2


TCM ACT

MFAS TCM6 APS/PCC TCM2 TCM1

SM TCM5

GCC0 TCM4 PM RES

RES EXP

RES JC RES JC PSI NJO

FTFL RES JC

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