Transport of Client Protocols

Jorge M. Finochietto

Córdoba – 2012

Laboratorio de Comunicaciones Digitales

LCD EFN UNC Facultad de Ciencias Exactas, Físicas y Naturales
Universidad Nacional de Córdoba, Argentina
 Optical Layer
Overview

Clients 2 / 35
 Optical Layer
Optical Transport Network (OTN)

Clients 3 / 35
 Optical Layer
Och Data Unit (ODU)

Clients 4 / 35
 Optical Layer
Och Payload Unit (OPU)

ITU-T G.709 defines OPU Payload bit rates :

OPU1 2,488,320kbit/s ± 20ppm
OPU2 238/237 × 9,953,280kbit/s ± 20ppm
OPU3 238/236 × 39,813,120kbit/s ± 20ppm
OPU4 238/227 × 99,532,800kbit/s ± 20ppm

Clients 5 / 35
 Optical Layer
Fitting the Payload in the Container

Clients 6 / 35
 Outline

1 Mapping

2 Multiplexing

Clients 7 / 35
 Outline

1 Mapping
Synchronous Mapping
Aynchronous Mapping
Generic Mapping

2 Multiplexing

Clients → Mapping 8 / 35
 Constant Bit Rate (CBR) Signals
Client Signals
CBR signals specifies an nominal bit rate X with some tolerance
∆ expressed as parts per million (ppm)
X
CBRX = X ± ∆ppm = X ± ∆ ×
1e6
X X
X −∆× ≤ CBRX ≤ X + ∆ ×
1e6 1e6
ITU-T G.870 defines CBR signals:
CBR2G5 2,488,320kbit/s ± 20ppm
CBR10G 9,953,280kbit/s ± 20ppm
CBR40G 39,813,120kbit/s ± 20ppm
Examples of these signals are:
CBR2G5: SDH STM-16 and GPON
CBR10G: SDH STM-64 and XGPON
CBR40G: SDH STM-256
Clients → Mapping 9 / 35
 Outline

1 Mapping
Synchronous Mapping
Aynchronous Mapping
Generic Mapping

2 Multiplexing

Clients → Mapping → Synchronous Mapping 10 / 35

 Synchronous Mapping

Simplest mapping method

Wraps a client signal with OTN framing
Server (i.e., OPU) clock is locked to client signal
Rates compensated through fixed stuff (FS) if required

CRate
SRate = CRate + KFS × SRate = , 0 ≤ KFS < 1
1 − KFS
Client bit rate tolerance (ppm) must not exceed server’s tolerance

CTolerance [ppm] ≤ STolerance [ppm]

OTN defines this as Bit-synchronous Mapping Procedure (BMP)

Clients → Mapping → Synchronous Mapping 11 / 35

 Synchronous Mapping
CBR2G5 into OPU1
Signals
Client: CBR2G5 2,488,320kbit/s ± 20ppm
Server: OPU1 2,488,320kbit/s ± 20ppm
No stuffing at all: KFS = 0

SRate = CRate

Clients → Mapping → Synchronous Mapping 12 / 35

 Synchronous Mapping
CBR10G into OPU2
Signals
Client: CBR10G 9,953,280kbit/s ± 20ppm
Server: OPU2 238/237 × 9,953,280kbit/s ± 20ppm
Fixed stuffing: 16 columns (i.e., 16 × 4bytes)
Payload columns: 238 × 16 = 3824 − 16 = 3808
Mapped columns: 237 × 16 = 3792 = 1888 + 1904
238
SRate = CRate ×
237

Clients → Mapping → Synchronous Mapping 13 / 35

 Synchronous Mapping
CBR40G into OPU3
Signals
Client: CBR40G 39,813,120kbit/s ± 20ppm
Server: OPU3 238/236 × 39,813,120kbit/s ± 20ppm
Fixed stuffing: 2 × 16 columns (i.e., 32 × 4bytes)
Payload columns: 238 × 16 = 3824 − 16 = 3808
Mapped columns: 236 × 16 = 3776 = 1248 + 1264 + 1264
238
SRate = CRate ×
236

Clients → Mapping → Synchronous Mapping 14 / 35

 Outline

1 Mapping
Synchronous Mapping
Aynchronous Mapping
Generic Mapping

2 Multiplexing

Clients → Mapping → Aynchronous Mapping 15 / 35

 Asynchronous Mapping

Part of the original version of ITU-T G.709

Rates compensated through
Fixed Stuff (FS), and
Variable Stuff (VS), time/frame dependent
Server (i.e., OPU) clock is independent from client signal
Client bit rate tolerance (ppm) must be within variable stuffing
(i.e., justification) tolerance

SRate = CRate + KFS × SRate + KVS (t) × SRate

OTN defines this as Asynchronous Mapping Procedure (AMP)

Clients → Mapping → Aynchronous Mapping 16 / 35

 Asynchronous Mapping
Variable Stuffing
Negative Justification Opportunity (NJO)
One byte from the OPU overhead can be used to map client data
Increases the effective payload area by one byte
Positive Justification Opportunity (PJO)
One byte from the OPU payload can be used to insert suffing
Decreases the effective payload area by one byte
Justification Control (JC) bytes are used to signal whether NJO,
PJO or no justification at all is present on the frame

Clients → Mapping → Aynchronous Mapping 17 / 35

 Asynchronous Mapping
Bit-Rate Tolerance
Since we can adapt the effective payload by one byte, the
resulting payload is given by
4 × 3808 ± 1
Thus,
4 × 3808 ± 1
SRate = CRate + KFS × SRate + × SRate
4 × 3808
SRate ≈ CRate + KFS × SRate ± 65[ppm]
since KFS ≈ 0
SRate ≈ CRate ± 65[ppm]
Maximum tolerance between OPUk and the client signal clock is
then ±65ppm.
With a tolerance of ±20ppm for the OPU clock, the client
signal’s bit-rate tolerance can be ±45ppm
Clients → Mapping → Aynchronous Mapping 18 / 35
 Asynchronous Mapping
CBR2G5 into OPU1
Signals
Client: CBR2G5 2,488,320kbit/s ± 45ppm
Server: OPU1 2,488,320kbit/s ± 20ppm

Clients → Mapping → Aynchronous Mapping 19 / 35

 Asynchronous Mapping
CBR10G into OPU2
Signals
Client: CBR10G 9,953,280kbit/s ± 45ppm
Server: OPU2 238/237 × 9,953,280kbit/s ± 20ppm

Clients → Mapping → Aynchronous Mapping 20 / 35

 Asynchronous Mapping
CBR40G into OPU3
Signals
Client: CBR40G 39,813,120kbit/s ± 45ppm
Server: OPU3 238/236 × 39,813,120kbit/s ± 20ppm

Clients → Mapping → Aynchronous Mapping 21 / 35

 Outline

1 Mapping
Synchronous Mapping
Aynchronous Mapping
Generic Mapping

2 Multiplexing

Clients → Mapping → Generic Mapping 22 / 35

 Other CBR Signals
Client Signals
IEEE defines 802.3 (aka, Ethernet)
1000BASE-R 1,250,000kbit/s ± 100ppm
10GBASE-R 10,312,500kbit/s ± 100ppm
40GBASE-R 41,250,000kbit/s ± 100ppm
100GBASE-R 103,125,000kbit/s ± 100ppm
Finally, ANSI defines Fibre Channel (FC)
FC-100 1,062,500kbit/s ± 100ppm
FC-200 2,125,000kbit/s ± 100ppm

Clients → Mapping → Generic Mapping 23 / 35

 Generic Mapping

Part of the new version of ITU-T G.709 (2010)

Represents a much more flexible / scalable scheme than AMP
Rates compensated through
Fixed Stuff (FS), and
Variable Stuff (VS), time/frame dependent
Server (i.e., OPU) clock is independent from client signal
Client bit rate tolerance (ppm) must be within variable stuffing
(i.e., justification) tolerance

SRate = CRate + KFS × SRate + KVS (t) × SRate

OTN defines this as Generic Mapping Procedure (GMP)

Clients → Mapping → Generic Mapping 24 / 35

 Generic Mapping
Variable Stuffing
Only Positive Justification Opportunities (PJO)
One or more bytes from OPU payload can be used to insert suffing
Decreases the effective payload area by one byte
OPU payload rate always much higher than worst case signal rate
Justification Control (JC) bytes are used to signal the number of
stuffing bytes inside the OPU payload

Clients → Mapping → Generic Mapping 25 / 35

 Generic Mapping
OPU4 Fixed + Variable Stuffing

Clients → Mapping → Generic Mapping 26 / 35

 Generic Mapping
Variable Stuffing Signaling
The number N of client data on the server signal is given by
CRate
N=
SRate
Since we can only insert an integer number of stuff units per
frame and N may be fractional, it has to be represented by a an
integer sequence N(t) such that
M−1
1 X
N= N(t)
M
t=0

To always insert the minimum amount of stuff, we can represent

N as a sequence of ceiling and floor values of N

N = α × floor (N) + β × ceil(N)

Clients → Mapping → Generic Mapping 27 / 35
 Outline

1 Mapping

2 Multiplexing

Clients → Multiplexing 28 / 35
 Multiplexing Hierarchy

Multiple OTN signals (ODUs) can be multiplexed into a higher

order OPU, identified as OPU(H)
These ODU tributaries need first to be mapped to an Optical
channel Data Tributary Unit (ODTU) and then multiplexed into
an ODTU Group (ODTUG)
OPU(L) and OPU(H) are the same information structures, but
with different client signals
Clients → Multiplexing 29 / 35
 Multiplexing Hierarchy
Optical channel Data Tributary Unit

An ODTU carries a justified ODU signal

If AMP is used, the ODTU is referred as ODTUjk
If GMP is used, the ODTU is referred as ODTUk.ts (we will only
discuss briefly this case)
Besides, an ODTU overhead is required to signal stuffing
(justification) decisions

Clients → Multiplexing 30 / 35
 Multiplexing Hierarchy
ODTU with Tributary Slots

An ODTU4.ts consists of
payload area: carries the tributary signal (ts=1...80)
overhead area: carries GMP justification
Clients → Multiplexing 31 / 35
 Multiplexing Hierarchy
Tributary Slot Allocation

An OPU4 (100G) is divided into 80 1.25G tributary slots

Each frame (out of 80) tranports a tributary slot overhead
(TSOH) that can be associated to one of the 1.25G slots
Clients → Multiplexing 32 / 35
 Multiplexing Hierarchy
ODU4 Multiplexing Overview

Clients → Multiplexing 33 / 35
 Multiplexing Hierarchy

ODU0 1,244,160kbit/s ± 20ppm

ODU1 239/238 × 2,488,320kbit/s ± 20ppm
ODU2 239/237 × 9,953,280kbit/s ± 20ppm
ODU3 239/236 × 39,813,120kbit/s ± 20ppm

Clients → Multiplexing 34 / 35
 Transport of Client Protocols

Jorge M. Finochietto

Córdoba – 2012

Laboratorio de Comunicaciones Digitales

LCD EFN UNC Facultad de Ciencias Exactas, Físicas y Naturales
Universidad Nacional de Córdoba, Argentina