OTN For 5G Backhaul Final

OTN for 5G Fronthaul
and backhaul
© BHARAT SANCHAR NIGAM LIMITED Slide No. 1 of 83

Objective of the presentation
Understand the 5G RAN Architecure
RAN deployment scenarios
Basic concept of OTN
Advantages of OTN Technology
ITU-T Series G Supplement 67 (07/2019)
OTN transport network architectures to support 5G

Background
• It is estimated that by 2020 there will be 20 billion

Internet of Things (IoT) connections.
• Additionally, global mobile data traffic will increase
sevenfold between 2016 and 2021, growing at a
compound annual growth rate (CAGR) of 47 percent
from 2016 to 2021, reaching 49 exabytes per month
by 2021.
• Most of this traffic will be video streaming along with
new use cases such as augmented reality, virtual
reality, and machine-to-machine communications.
• The current 4G network doesn’t have the capacity to
gracefully handle this explosion of traffic.

Background

Background
• 5G communication technology extends the wireless
networking beyond the users, to support network
connectivity for everything which can advantageous from
being connected that include personal belongings, home
appliances, pervasive to medical equipment and everything
which connects to each other.
• 5G network provides tremendous services for example;
remote monitoring and real time smart device control, which
supports M2M (machine to machine) services and IoT
applications, such as smart vehicles, smart pervasive
systems, robots and sensor
• 5G is an end-to-end ecosystem to enable a fully mobile
and connected society.

Main usage scenarios of 5G/IMT-2020
• ITU-R has defined the following main usage scenarios for
IMT-2020 and beyond in their Recommendation ITU-R
M.2083:
1. Enhanced Mobile Broadband (eMBB)
2. Massive Machine-type Communications (mMTC)
3. Ultra-reliable and Low Latency Communications
(uRLLC)

Main usage scenarios of 5G/IMT-2020

Gaps and challenges towards 5G/IMT-2020

5G RAN architecture
• In general, 5G is different from previous mobile
generations in three ways:
• Densification or an increase in the number of cell
sites per unit area along with greater fiberization of
cell towers
• Cloudification or greater centralization of baseband
resources that connect to “street level” radio nodes
over optical fiber
• Disaggregation or flexible and “software-centric”
separation of control and data plane for higher
scalability and dynamic resource allocation.

5G RAN architecture
• 5G transport network architecture can be

classified into two major types:
–C-RAN and
–D-RAN

Traditional D-RAN Architecture

Transition to C-RAN Architecture

Virtualized/Cloud RAN Architecture

5G C-RAN architecture
• The main change in 5G is that the original Base Band Unit (BBU) in
4G/LTE is in 5G is now split into three parts as defined in TR
38.801:
– Central Unit (CU)
– Distributed Unit (DU)
– Remote Radio Unit (RRU)/Active Antenna Unit (AAU)/RRH

5G C-RAN architecture
Access/Fronthaul Aggregation/Midhaul Core/backhaul
RU DU
MEC
RU CU
DU
RU
Core
RU
DU
CU MEC
DU
Up to 10 Km Up to 80 Km
Various transport and Connecting radios to core Providing capacity, latency

aggregation technologies networks (through X-haul) and flexibility
Radio unit (RU) Distributed Unit (DU) Centralized Unit (CU)

© 2019 EXFO Inc. All rights reserved.
Mobile edge computing (MEC)
X-haul C-RAN architecture

C-RAN Architecture for 4G & 5G

RAN deployment scenarios
1) Independent RRU, CU and DU locations
In this scenario, there are fronthaul, midhaul and backhaul networks.
2) Co-located CU and DU
In this scenario, the CU and DU are located together, consequently there
is no midhaul.
3) RRU and DU integration
In this scenario, an RRU and DU are deployed close to each other,
maybe hundreds of meters, for example in the same building. In order
to reduce cost, an RRU is connected to a DU just through straight fibre
and no transport equipment is needed. In this case, there are midhaul
and backhaul networks.
4) RRU, DU and CU integration
This network structure may be used for small cell and hot-spot
scenarios. There is only backhaul in this case.

5G RAN functional split
Massive MiMo
macro base
station
5G split option 2
Legacy 3G/4G (option

8) & 5G split option 7
5G split option
2 and option 7

Network Slicing in C-RAN

Network slicing in Cloud-RAN.
• The exact location of the separation between these two entities
is referred to as the functional split. The DU and the CU are
connected using a so-called fronthaul network. The simplest
division between DU and CU leaves only the Radio Frequency
(RF) functions in the DU.
• CUs from several sites can be centralized in the same
datacenter which is an enabler for modern network
virtualization techniques. This way, processing functions are
gathered in one place, the CU-datacenter, which can be
virtualized. Network functions virtualization moves the network
processes into software, and, instead of the functions running
at a base station, they will be able to run at any server.
• Virtualization of several functions is an important enabler for
network slicing.

Mapping of CU and DU functions
according to the split points

Existing Transport Technology options for
5G fronthaul
• PDH
• SDH
• Next Generation SDH
• DWDM
• Dark Fiber
• TDM and WDM PON based Network
• OTN
• MPLS-TP

Requirements for 5G fronthaul transport
• Latency requirements
• With regard to latency the transport at the
interfaces of split options 1-8 falls into two
categories:
– ''non-real-time'' transport with latencies in the range
of several milliseconds (options 1-3)
– ''real-time'' transport with latencies in the range of a
few hundred μsec (options 4-8)

5G transport network: latency analysis

Required Fronthaul bandwidth
• Required fronthaul bandwidth in 5G wireless

network

OTN - an overview
• Integrated switching and multiplexing

structure with electronic and photonic layers’

Advantages
• Reliable switching and transparent transport for all
client types:
– Ethernet (1-100 GbE, VLAN), IP-MPLS/MPLS-TP, Data
Center/Video/SAN, SDH/SONET
– End user views exactly what was transmitted
• Maximizes wavelength utilization, reducing capex
and extending network lifetime.
• The ability to mix OTN, SONET/SDH, and packet
traffic on the same 100G interface
• Full suite of OAM (Operations, Administration and
Management) features
• Framing of client signal of different protocols for
transport over the physical optical layer
Advantages
• Better Forward Error Correction (FEC)
– Increased reach
– Can increase number of channels (the required power
has been lowered 6.2 dB)
• Better scalability
– Multiplexing structure less complicated
– SONET/SDH created to carry voice
• Backward compatibility for existing protocols
– OTN supports existing protocols like SDH/SONET,
Ethernet etc
• Tandem Connection Monitoring (TCM)
– Allowing each network to be monitored

Converged transport over OTN

Typical signals, transported via OTN
• SONET/SDH
• Ethernet
• Fibre Channel
• CPRI / eCPRI

OTN Frame Structure
There are three overhead areas in an OTN frame:

 Optical Payload Unit (OPU) overhead
 Optical Data Unit (ODU) overhead
 Optical Transport Unit (OTU) overhead
• These overhead bytes provide path and section performance monitoring,
alarm indication, communication, and protection switching capabilities.
• One additional feature is the inclusion of a Forward Error Correction (FEC)
function for each frame.
• The FEC improves the Optical Signal-to-Noise Ratio (OSNR) by 4 to 6 dB,
resulting in longer spans and fewer regeneration requirements.

Signal framing according to ITU-T G.709
Client
OH Client OCh Payload Unit (OPUk)

Associated
overhead
Wrapper
OH OPUk OCh Data Unit (ODUk)
OH ODUk FEC OCh Transport Unit (OTUk)
OH OTUk Optical Channel (OCh)

Non-associated overhead
OCC OCC OCC Optical Channel Carrier (OCC)
OH OPS0 Optical Multiplex Section
OH Optical Transmission Section
OOS OTM Overhead Signal

OSC
OSC Optical Supervisory Channel
Optical Transport Module
Optical Physical Section

ODU Multiplexing Hierarchy

ODU Multiplexing Hierarchy
Basic ODU frames
• ODU0 ~1.25 Gbit/s (suitable for GbE, 1G FC, etc.
client signals)
• ODU1 ~2.5 Gbit/s (STM-16, OC-48, etc.)
• ODU2 ~10 Gbit/s (STM-64, OC-192, 10 GbE, etc.)
• ODU3 ~40 Gbit/s (STM-256/OC-768, 40 GbE, etc.)
• ODU4 ~100 Gbit/s (100 GbE, etc.)
Additional ODU frames

• ODU flex ~ client signal bit rate (CBR client signals); N x 1.25Gbit/s
(N = 1..80) ~ configured bit rate acc. to ITU-T G.709
• ODU 2e ~10.4 Gbit/s (10GBASE-R)

Full function OTN

Transport Technology options for
Fronthaul Network Technologies in the
C-RAN Architecture

Transport Technology options for
Fronthaul Network Technologies in the
C-RAN Architecture

Fronthaul Networking Modes

Fronthaul Networking Modes

WDM/OTN Solution for Fronthaul-I
The Muxponder of WDM/OTN multiplexes the 10 Gbps or 25 Gbps

CPRI or eCPRI signals of multiple RRUs/AAUs into 100/200 Gbps high-
speed signals and transfers them to DU, meeting the high bandwidth
transmission requirement.

OTN Solution for Fronthaul-II

OTN Solution for Fronthaul-II

Unified Backhaul of Fixed-Mobile
Convergence

ITU-T Standard
ITU-T Series G Supplement 67 (07/2019)
Application of optical transport

network Recommendations to 5G
transport

5G wireless fronthaul architecture
• The terms fronthaul, midhaul and backhaul are frequently
used when describing 5G architecture. The use of the terms
fronthaul, midhaul and backhaul in the context of a
transport network is described below:
• A transport network that supports the low layer functional
split point of 3GPP NG-RAN, (e.g., Option 6 for MAC/PHY
split or Option 7 for intra PHY split) [3GPP TR 38.801], is
commonly known as fronthaul.
• A transport network that supports 3GPP NG-RAN F1
interface (between a gNB-CU and a gNB-DU), or the Xn
interface that provides interconnection between different
NG-RAN nodes (gNB or ng-eNB), is sometimes referred to
as midhaul.

5G wireless fronthaul architecture
• A transport network that supports the 3GPP NG
interface (between the 5GC and the NG RAN) or the
Xn interface that provides interconnection between
different NG-RAN nodes (gNB or ng-eNB) [3GPP TS
38.401], is commonly known as backhaul.
• Due to the reason that 3GPP specifies several
functional split options, and it drives the deployment
of NGC network to the cloud edge, there are four
possible deployment locations of transport network,
fronthaul, midhaul, backhaul and NGC
interconnection.
Deployment location of core network
in 5G network

Fronthaul
• The function split point is located between a high
PHY and low PHY; the bandwidth of a UNI interface
is about 25 Gbit/s.
• For a new 5G network, the typical bandwidth of an
NNI interface is about 75 Gbit/s or 150 Gbit/s
(considering a high frequency case).
• For a 4G and 5G hybrid network, the typical
bandwidth of NNI interface is about 100 Gbit/s or
200 Gbit/s.
• The latency requirement is strict (< 100 us). The
transport network is always deployed in P2P mode.

Midhaul
• The function split point is located between the

PDCP(Packet Data Convergence Protocol) and RLC
(Radio link control).
• The bandwidth of a UNI interface is about 10 or
25 Gbit/s, and the bandwidth of an NNI interface
is about N times 10 Gbit/s or 25 Gbit/s (related to
the aggregation capability of a DU).
• The transport network is always deployed in tree
or ring mode. Multiple DUs are aggregated to one
CU.

Backhaul
• The function split point is above the RRC, and the
bandwidth requirements are similar to midhaul.
• There are two types of traffic: horizontal traffic
and vertical traffic. Xn is the interface which
carried a coordination service between the base
stations, therefore, horizontal traffic scheduling is
needed.
• NG is the interface which carried different services
(such as V2X, eMBB and IoT) from the base station
to the 5G core.
• Usually, different services are deployed in different
clouds, therefore vertical traffic grooming is
needed.
NGC interconnection
Transport network requirement summary for NGC

NGC interconnection
• This is the interconnection between nodes

after the core network has been deployed in
the cloud edge; the bandwidth of the UNI and
NNI interface is equal or larger than 100
Gbit/s.
• One hop connection is required to reduce the
bandwidth waste caused by multiple hops.

OTN transport network architectures
to support 5G
• As for each AAU, the bandwidth requirements for midhaul
and backhaul are very similar; also, packet based flexible
networking capabilities (e.g., IP/MPLS forwarding) are
required for both midhaul and backhaul. So, using one
universal transport solution for both midhaul and backhaul
is desired.
• On the other hand, the bandwidth requirement for
fronthaul is much higher than midhaul and backhaul, and
simply point-to-point transport of eCPRI traffic is enough
for fronthaul.
• Therefore, from perspective of bandwidth requirement
and flexible networking capabilities, 5G transport network
architecture can be classified into two major types: C-RAN
and D-RAN.
OTN transport network architectures to
support 5G
5G transport network architecture: C-RAN
• Based on the location of centrally deployed DUs, C-RAN

can be further divided into the following two types:
• Large C-RAN
• Small C-RAN
Deployment scenarios
• Large C-RAN: DUs are centrally deployed at the central office (CO), which
typically is the intersection point of metro-edge fibre rings. The number of DUs
within in each CO is between 20 and 60 (assume each DU is connected to 3
AAUs).
• Small C-RAN: DUs are centrally deployed at the metro-edge site, which typically
is located at the metro-edge fibre ring handover point. The number of DUs
within each metro-edge site is around 5~10

support 5G
5G transport network architecture: D-RAN
• In this scenario the AAU and DU are co-located; the DU and CU could be
co-located or separated. Therefore, there is only a backhaul network, and
possibly also a midhaul one, but no fronthaul.
• For D-RAN the transport network metro-edge node will be co-located
with 5G gNB. In order to improve the link utilization and network
reliability, usually packet ring topology will be deployed at the metro-
edge domain
support 5G
• This OTN network is providing connectivity between the following
5G network elements:
– Active antenna unit (AAU) to next generation node B (gNB),
– AAU to gNB distributed unit (DU),
– DU to DU,
– DU to gNB centralized unit (CU),
– CU to CU to gNB to gNB,
– CU to mobile edge computing (MEC),
– gNB to MEC,
– MEC to MEC,
– MEC to core network (CN) and
– Cn to CN.
support 5G
• The connectivity (Xn) between CUs and gNBs can be supported by a
multipoint-to-multipoint connection or by a set of point-to-point
connections.
• NOTE – This OTN network architecture will also support connectivity
between
– 4G network elements: active antenna unit (AAU), baseband unit
(BBU), enhanced node B (eNB) and evolved packet core (EPC) ,
– broadband network elements: optical line terminal (OLT) or
digital subscriber line access multiplexer (DSLAM), broadband
network gateway (BNG) and core router (CR)),
– data centres, and
– private line customer premises network elements (CPE).
support 5G
• OTN network elements in the network domains are interconnected
via OTUk and OTUCn/FlexO interface signals compliant with [ITU-T
G.709], [ITU-T G.709.1], [ITU-T G.709.2] and [ITU-T G.709.3].
• Only in case there is no direct optical layer connection possible,

such OTN to OTN network element interconnectivity is established
via one or more intermediate OTN network elements; e.g., two
OTN network elements located at the boundary of a metro-
aggregation and a metro-edge domain (EA) may be interconnected
via the OTN network element located at the boundary of the
metro-aggregation and metro-core domains (AC).

OTN network architecture with 5G
client network elements

OTN network architecture with 4G
client network elements

OTN network architecture with
broadband client network elements

OTN network architecture with data
centre client network elements

OTN network architecture with
private line client network elements

5G fronthaul and midhaul domain
relationship with OTN network domains

5G backhaul domain relationship
with OTN network domains

OTN metro-core network domain
• The OTN metro-core network domain may deploy an optical mesh
network topology, optical ring network topology or hybrid mesh
and ring network topology. Optical path distances are assumed to
be between 20 km and 450 km. The bandwidth requirements
between the OTN network elements at the domain boundaries will
be around N×100G.
• 100G, 200G and 400G OTN interfaces are available in the formats
OTU4-SC as specified in [ITU-T G.709]/[ITU-T G.709.2],
OTUC1/FlexO-1-SC, OTUCn/FlexO-1-SC-n, OTUC2/FlexO-2-DSH,
OTUCn/FlexO-2-DSH-m (m= n/2), OTUC4/FlexO-4-DSH and
OTUCn/FlexO-4-DSH-m (m= n/4) as specified in [ITUT-G.709]/[ITU-
T G.709.3]. The 100G and future 200G and 400G application codes
in [ITU-T G.698.2] are applicable.

OTN metro-core network domain
Optical metro-
aggregation
network ring
interconnecting a
pair of OTN
network elements
at the boundary
with the metro-
core domain with 4
to 6 OTN network
elements at the
boundary with the
metro-edge
domains

OTN metro-aggregation network domain
• The OTN metro-aggregation domain may deploy a point-to-point
(p2p) optical layer network topology or an optical ring based optical
layer network topology. Optical path distances are assumed to be
between 5 and 20 km in a metropolitan area and 5 and 40 km in a
rural area. Via the longest optical path in an optical ring these values
would double to 40 km and 80 km. The bandwidth requirements
between the OTN network elements at the domain boundaries will
be around 100G~200G.
• For a point-to-point scenario, 100G or 200G OTN interfaces are
available in the formats OTU4 as specified in [ITU-T G.709

OTN metro-aggregation network domain
• For an optical ring scenario, Figure 8-11 shows a pair of OTN
network elements at the boundary of the metro-core and metro-
aggregation domains that are connected to up to e.g., four optical
metro-aggregation rings, each connected to 4 to 6 OTN network
elements at the boundary of the metro-aggregation and metro-edge
domains. The ring bandwidth will be in the range of 400~1200G.
• 100G and 200G OTN interfaces are available in the formats OTU4-SC
[ITU-T G.709], [ITU-T G.709.2], OTUC1/FlexO-1-SC, OTUC2/FlexO-1-
SC-2 and OTUC2/FlexO-2-DSH [ITU-T G.709]/[ITU-T G.709.3]. The
100G and future 200G application codes in [ITU-T G.698.2] are
applicable.
• Data centre to data centre connections with bit rates in the same
order as the bit rates of the OTN interfaces would typically be
provided via the OTN optical layer directly.
OTN metro-edge network domain
• OTN large C-RAN metro-edge network domain
• The OTN large C-RAN metro-edge domain may deploy a point-to-
point (p2p) optical layer network topology or an optical chain
based optical layer network topology. Optical path distances
between an OTN node at the boundary of metro-edge and metro-
aggregation domains and an OTN node at the edge of the metro-
edge domain are assumed to be between 1 and 5 km in a
metropolitan area and 1 and 10 km in a rural area. The bandwidth
requirements between the OTN network elements at the domain
boundaries will be around 100G~200G.
• For an optical chain scenario, an OTN network element at the
boundary of the metro-aggregation and metro-edge domains that
are connected to up to five optical large C-RAN metro-edge chains,
each connected to 6 OTN network elements at the boundary of
the metro-edge domains. The chain bandwidth will be in the range
of 700~1000G. © BHARAT SANCHAR NIGAM LIMITED Slide No. 75 of 83
OTN large C-RAN metro-edge network
domain
Optical large C-
RAN metro-edge
chain
interconnecting a
pair of OTN
network elements
at the boundary
with the metro-
aggregation
domain with 6
OTN network
elements at the
boundary of the
metro-edge
domain

OTN metro-edge network domain
• Small C-RAN metro-edge network domain
• In the small C-RAN metro-edge network domain there is no true
optical layer network.
• The OTN small C-RAN metro-edge domain deploys a point-to-point
(p2p) optical layer network topology in which the OTN node at the
metro-edge and metro-aggregation boundary is interconnected via
a p2p fibre with an OTN node at the edge of the metro-edge
domain. Optical path distances are assumed to be between 1 and 5
km in a metropolitan area and 1 and 10 km in a rural area. The
bandwidth requirements between the OTN network elements at
the domain boundaries will be around 25G~50G.
• For this point-to-point scenario, 10G or 100G OTN interfaces are
available in the formats OTU2 and OTU4.

Small C-RAN metro-edge network
domain
Optical small C-RAN
metro-edge fibres
interconnecting a
pair of OTN network
elements at the
boundary with the
metro-aggregation
domain with 3 or 4
OTN network
elements at the
boundary of the
metro-edge domain

D-RAN metro-edge network domain
• In the D-RAN metro-edge network domain there is no true optical
layer network.
• The OTN D-RAN metro-edge domain deploys a point-to-point
(p2p) optical layer network topology in which a pair of OTN nodes
at the metro-edge and metro-aggregation boundary are
interconnected via an MPLS-TP or Ethernet packet over OTN ring
with OTN nodes at the edge of the D-RAN metro-edge domain.
Optical path distances between adjacent OTN nodes in this ring
are assumed to be between 1 and 5 km in a metropolitan area and
1 and 10 km in a rural area. The bandwidth requirements between
all OTN network elements at the domain boundary will be around
25G~50G.

D-RAN metro-edge network domain
D-RAN metro-
edge packet over
OTN ring
interconnecting
OTN network
elements at the
boundary with
the metro-
aggregation
domain with 6
OTN network
elements in the
D-RAN metro-
edge domain

Network slicing support in OTN
• OTN provides network slicing support in which

client layer characteristic information
forwarding is performed via ODUk or ODUflex
based slice tunnels and client layer switching
functions that support ODUP/<client>_A
functions defined in [ITU-T G.798] and
<client>_C functions.
• Clients include SDH VCn, Ethernet MAC/VLAN
(ETH), MPLS-TP PW/LSP, etc.

Frequency and time synchronization
in the OTN network
• In the 5G OTN transport network, frequency
and phase/time synchronization are needed
to support requirements at the air interface of
a mobile system. This section describes 5G
synchronization requirements and defines the
synchronization solution for the OTN transport
network.

Synchronization requirement
• Based on 5G mobile technology, the frequency offset at the
air interface of every AAU should be less than the value in the
following table, which is a copy of Table 6.5.1.2-1 of [3GPP TS
38.104].
• The relevant phase/time synchronization requirements are
listed in Tables II.1 and II.2 of [ITU-T G.8271]
Frequency offset requirement

Conclusion
• In conclusion to this analysis, OTN provides

capabilities such as interfaces, OAM,
survivability and synchronization applicable to
transport 5G, and in addition is fully ready
today to do so


OTN For 5G Backhaul Final

Uploaded by

Copyright:

Available Formats

You might also like

OTN For 5G Backhaul Final

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OTN For 5G Backhaul Final

Uploaded by

Copyright:

Available Formats

OTN for 5G Fronthaul

© BHARAT SANCHAR NIGAM LIMITED Slide No. 1 of 83

Understand the 5G RAN Architecure

RAN deployment scenarios

Basic concept of OTN

Advantages of OTN Technology

ITU-T Series G Supplement 67 (07/2019)

OTN transport network architectures to support 5G

© BHARAT SANCHAR NIGAM LIMITED Slide No. 2 of 83

• It is estimated that by 2020 there will be 20 billion

© BHARAT SANCHAR NIGAM LIMITED Slide No. 3 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 4 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 5 of 83

1. Enhanced Mobile Broadband (eMBB)

2. Massive Machine-type Communications (mMTC)

3. Ultra-reliable and Low Latency Communications

© BHARAT SANCHAR NIGAM LIMITED Slide No. 6 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 7 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 8 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 12 of 83

• 5G transport network architecture can be

© BHARAT SANCHAR NIGAM LIMITED Slide No. 13 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 14 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 15 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 16 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 17 of 83

Various transport and Connecting radios to core Providing capacity, latency

Radio unit (RU) Distributed Unit (DU) Centralized Unit (CU)

© BHARAT SANCHAR NIGAM LIMITED Slide No. 19 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 20 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 21 of 83

Legacy 3G/4G (option

© BHARAT SANCHAR NIGAM LIMITED Slide No. 22 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 23 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 24 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 25 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 26 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 27 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 28 of 83

• Required fronthaul bandwidth in 5G wireless

© BHARAT SANCHAR NIGAM LIMITED Slide No. 29 of 83

• Integrated switching and multiplexing

© BHARAT SANCHAR NIGAM LIMITED Slide No. 30 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 32 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 33 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 34 of 83

There are three overhead areas in an OTN frame:

© BHARAT SANCHAR NIGAM LIMITED Slide No. 35 of 83

OH Client OCh Payload Unit (OPUk)

OH OPUk OCh Data Unit (ODUk)

OH ODUk FEC OCh Transport Unit (OTUk)

OH OTUk Optical Channel (OCh)

OCC OCC OCC Optical Channel Carrier (OCC)

OH OPS0 Optical Multiplex Section

OH Optical Transmission Section

OOS OTM Overhead Signal

© BHARAT SANCHAR NIGAM LIMITED Slide No. 36 of 83

© BHARAT SANCHAR NIGAM LIMITED Slide No. 37 of 83