Open RAN

Zero to Zenith

Introduction
 Open RAN Executive Summery

Open RAN = overall Open RAN movement of

opening interfaces

Open RAN Movement

Open RAN = TIP group and anything related to TIP

deployments
Open RAN

Open RAN or #ORAN {for hashtag) = O-RAN

Alliance references of org itself or interfaces
Open RAN
Open RAN
Open RAN Alliance Organizational Structure
Nutshell

The management structure consists of an

Operating Board made up of 15 operators and a
Technical Steering Committee (TSC) co-chaired.

Sachin Katti
Sachin Katti Professor at Stanford University.

Dr. Chih-Lin I, Chief Scientist of Wireless

Technologies at China Mobile.
Dr. Chih-Lin I
Organizations Driving Open RAN

There are two main organizations driving Open

RAN:
The term "OpenRAN" refers to a Telecom Infra
Group (TIP) project group whose main goal is to
implement fully programmable RAN solutions
based on 3GPP/COTS and disaggregated
applications.

The O-RAN Alliance is another major proponent of

the Open RAN concept, with only a focus on
interface standardization. AT&T, China Mobile,
Deutsche Telekom, NTT DOCOMO, and Orange
founded the alliance in 2018.
 Evolution of HW/SW Disaggregation

VM Ware
Linux Red Hat Cloud ARISTA Open
Microsoft vEPC Compute
Distributed Open-source computing Linux based
PC OS across ALL G
Apps Linux-based Platform OS SDN
Software's virtualization

1965s 1980s 1990s 2000s 2004s 2018 Now

Moore’s The cost of computer power The cost of computer power The cost of computer power
Law to the consumer falls to the enterprise falls to the telecom falls
Hardware's

• Mainframes • Intel x86 proliferation • Switches h/w • X86 enables • RAN HW gets
become • Service hardware gets gets scale/performance standardized
obsolete standardized standardized • Delivers CAPEX
• PCs emerge reduction 60%
and OPEX by 90%

Consumer Enterprise Telecom

Traditional Mobile Network Architecture

Data (IP) Voice

Network (PSTN) Network

Core
Network P-GW EPC GGSN

S-GW MME SGSN MSC

RNC BSC

Access
RNS BSS
Network

NodeB BTS

eNodeB

2.5G

3G
Air
Interface 3G
UE UE MS 4G
 Traditional Base Station

Antennas The traditional base station was employed in the

deployment of 2G, 3G, and the initial phases of 4G.
TMA

And here we can observe the connection between

RF Cabling

the core network and the base station.

There is a cabinet located inside the base station

BBU + RRU that contains the Base Band Unit (BBU) and Radio
Unit (RU) equipment.

Traditional Base Station Suppose now that the core network is

• Signal Processing transmitting data to the base station, which is
• RF Equipment
• Network Access
then transmitted by the antenna.
• Long RF Cables
 Evolution to Contemporary Base Station
The traditional base station
evolved into the contemporary
RF
base station in 4G LTE to resolve
Antennas the problem of power loss on the
Remote Radio Propriety RF cable. In this instance, the
Unit (RRU) Hardware
radio unit was shifted away from
• DAC/ADC
• RF Equipment the baseband unit and
moved closer to the antenna.
CPRI
Fiber Cabling

And now that it is nearer the

antenna, this radio unit is referred
Propriety to as a remote radio unit (RRU).
Hardware +
Baseband Unit Propriety
(BBU) Software
We also have optical fibre cable
connecting the baseband unit and
the remote radio unit.

Contemporary Base Station

• Signal Processing
• Network Access Power loss in the optical fibre cable
• Floor Optic Cables is relatively low.
C – RAN Architecture

S1/X2

X2
\
Synch
Synch
Synch
Synch
Control
Synch
Synch
Synch
Transport
Synch
Synch
Synch
Baseband
Virtual BBU
Pool

Ir

RF RRH RF RRH
RF RRH
Virtualized RAN (vRAN) Approach

RF
Antennas

Remote Radio Propriety Hardware

Unit (RRU)
• DAC/ADC
• RF Equipment
CPRI
Propriety Interfaces
Fiber Cabling

COTS Server
+
Baseband Unit Propriety Software with
(BBU) Virtualized Functions

Contemporary Base Station

• Signal Processing
• Network Access
• Floor Optic Cables
 From vRAN towards Open RAN

vRAN OpenRAN
"Virtualized
Software"
- running on -
COTS based Hardware
RF "Open Interfaces
Antennas SW Define Radio (SDR)
Hardware"
Can be purchased from
Remote Radio Proprietary Hardware Anything Else is
any ODM/OEM/RAN
Unit (RRU) Considered
Hardware Vendor
• DAC/ADC Proprietary
• RF Equipment

CPRI
Open Interface
RF Cabling

Proprietary Interfaces Any vendor software

can work on this
hardware

Baseband COTS Server and Proprietary

Unit (BBU) Software With Virtualized Functions

Contemporary Base Station

• Signal Processing
• Network Access
• Floor Optic Cables
 Example Scenario : Open RAN Deployment
Model
C

A 2 COTS
C

Open B Open Open

Transport Core Service
RAN RAN RAN
Network Network
RU B DU CU
3 COTS 2
C
COTS
Services
A

C 4 COTS

RU Vendors DU Software CU Software

Vendors Vendors
COTS Vendors COTS Vendors
Open RAN Architecture

Orchestration & Automation (MANO, ONAP)

Design Inventory Policy Configuration RAN Intelligent Controller (RLC) Non-Real Time

A1

Application Layer RAN Intelligent Controller (RIC) Near-Real Time

Radio
3rd Party Mobility QoS Interface
Connection Trained Model
Application Management Management Management
Management
Antenna

RAN Database

E2 E2
RAN
Multi RAT CU C-plane CU U-plane Distributed Unit
Control Unit E1 F1 R M PHY (DU)
RRC SDAP L A Hig PHY Remote
(CU)
C C h Low Radio Unit
Higher Layer
Protocol Stack PDCP-C PDCP-U Open Fronthaul

NFVI Platform NFVI Platform

Open RAN Deployment Scenarios – Private
5G and Macro Network
Public Macro sites & Small Cells

RU RU

DU
DU
RU
CU- CU-
UP/RIC/UPF CP/RIC/5GC/APP
RU /APP
DU

Private Networks
In building solutions Ru Ru
DU DU
Ru
DU
Ru Ru
DU DU
Ru
DU
CU/5GC-CP/UPF/APP
CU-UP
Traffic Steering Scenario in Open RAN

5G BTS 2 5G BTS 1

Cell X : Band Cell A : Band 700MHz, BW : 10 MHz

3.5GHz, BW:100 Cell B : Band 1.8GHz, BW : 20 MHz
MHz Cell C : Band 3.5GHz, BW : 100 MHz

Which cell should I

move to it?

Cell X Cell A Cell B Cell C

 What is Beam-based Mobility Robustness
Optimization in Open RAN?

UE1
What is Beam-based Mobility
UE2
Robustness Optimization in
Open RAN?

gNB1 gNB2

UE1 with TE HO, and UE2 with TL HO

Beam-based Mobility Robustness Optimization in Open RAN

How does DSS work in Open RAN?

SMO
nonRT-RIC

R-APP(DSS)

O1 A1
O1

nRT-RIC
EPC/NGCore
X-APP(DSS)

E2
Spectrum X CU+DU CU+DU Spectrum X+Y
(LTE) (5G)
X2/Xn

NG-eNodeB/eNB gNB
X
Y

UE-4G UE-
UE-5G
4G+5G

RIC Based DSS Architecture

How is Network Slicing accomplished in an
Open RAN with multiple vendors?

NG-U

F1-C

F1-U vO-CU- E1 vO-CU-

FH vO-DU NG-C Slice #1: eMBB
CP CP
5G
O-RU
Core
F1-U vO-CU- E1 vO-CU-
vO-DU
UP F1-C CP Slice #2: URLLC
NG-U
UPF

O-Cloud O-Cloud

Edge Cloud Regional Cloud

Network Slicing in Open RAN using multi-vendors

 Open RAN Working Groups
WG 9: Open X-haul Transport
Workgroup
Orchestration & Automation (e.g., ONAP): MANO, NMS
Focus on the transport domain –
Design Inventory Policy configuration
RAN Intelligent
Controller (RIC) non-RT
consisting of transport equipment,
A1 near-RT / non-RT
physical media and control /
management protocols
RAN Intelligent Controller (RIC) near-RT associated with the transport
3rd party
Radio
Connection
Mobility QoS Interference Trained network underlying the assumed
Mgmt.
Mgmt. Mgmt. Mgmt. Model
Ethernet interfaces (for fronthaul,
Application Layer Radio Network Information Base
mid-haul and backhaul).

E2 near -RT

CU-CP E1 CU-UP
WG 10: OAM Work Group.
Multi-RAT
CU Protocol Stack
RRC
PDCP-C
SDAP
PDCP-U
This WG focuses on the O1
interface Operations,
F1
Administration and Maintenance
NFVI Platform: Virtualization layer and COTS platform (OAM) specifications (e.g., unified
O1 operation and notification) and
RAN DU ( RLC/MAC/PHY-high )
on creating OAM architecture and
NGFI-I requirements for the
O-RAN architecture and use cases
RAN RRU ( PHY-low/RF )
identified by WG1
 Open RAN Working Groups

Orchestration & Automation (e.g., ONAP): MANO, NMS

RAN Intelligent
Design Inventory Policy configuration
Controller (RIC) non-RT

A1 near-RT / non-RT

RAN Intelligent Controller (RIC) near-RT

Radio
Mobility QoS Interference Trained
3rd party Connection
Mgmt. Mgmt. Mgmt. Model
Mgmt.

Application Layer Radio Network Information Base WG 11: Security Work Group.
This WG focuses on the security
E2 near -RT
aspects of the O-RAN ecosystem.
CU-CP E1 CU-UP
Multi-RAT
RRC SDAP
CU Protocol Stack
PDCP-C PDCP-U

F1

NFVI Platform: Virtualization layer and COTS platform

RAN DU ( RLC/MAC/PHY-high )

NGFI-I

RAN RRU ( PHY-low/RF )

White – Box Hardware Design

The white-box hardware design will

focus on:
O-DU: Downlink and uplink baseband
processing, supply system
synchronization clock, signaling
processing, OM function, interface
with O-CU and the fronthaul gateway.

O-RU: Downlink baseband signal

gNB-CU PDCP
convert to RF signal, uplink RF signal
convert to baseband signal, and
F1 F1
F1 interface with the fronthaul gateway.

RLC
Fronthaul gateway (if needed):
MAC Downlink broadcasting, uplink
combining, power supply for O-RU,
Physical
cascade with other fronthaul gateway,
synchronization clock.
 Open RAN : Enabling White Box RAN

Traditional Networking Equipment White box Product

Proprietary Custom built

Closed Open APIs

Fixed Disaggregated

High Cost Low cost

Choice of Applications
Choice of Network OS
Choice of Merchant chip
Choice of Hardware
Open RAN : White Box Hardware

O-RUy
F1
Interface
FH
O-CU O-DUx Interfacex (Optional)
FHGW x→y . O-RUy
Or .
Switch
. .
.
O-CU & O-DUx may/may not be integrated into one FH .
Whitebox Interfacey
O-RUy
Open RAN : White Box Hardware

O-Dux & O-RUx

O-CU F1 Interface Switch

.. O-DUx & O-RUx

.
..
.

O-DUx & O-RUx

Open RAN
Zero to Zenith

Advance
 26

OpenRAN Network Architecture Components

Here the gNB comprises of following functional
units:
Service Management and Orchestration Framework
1. Open Radio Unit (O-RU) that consists of the
Non-Real Time RIC O1
3GPP interfaces RF chain to transmit or receive the over-the-
O-RAN interfaces
O2 O1 A1 For future study air signal and provide transformation of the
analog radio signal and digital signals. It links
Near-Real Time RAN Intelligent through fronthaul to the Open Distributed
Controller (RIC)
Unit (O-DU).
E2 E2 X2-c
X2-u
O-eNB O-CU-CP E1
O-CU-UP
2. Open Distributed Unit (O-DU), which
E2 NG-u
Xn-u handles the lower layers of baseband
Xn-c
Open Fronthaul
M-Plane
E2
NG-c processing up to the PDCP layer of the
F1-c F1-u
protocol stack. In older RAN systems, this
O-DU
Open Fronthaul CUS-Plane Open Fronthaul M-Plane runs on hardware made by a single vendor.
O-RU However, today's software can run on COTS
O-Cloud hardware, which makes it possible to
virtualize this function. Since it is virtualized,
Overall Architecture of O-RAN it gives you the freedom to put the
processes in different places, such as the cell
site, the far edge, or the centralized places.
 27

Different RAN Splits for Rural and Dense Areas

Split 2 Split 7.2x

PDCP PDUs Symbol/bits
LOW HIGH
RF PHY MAC RLC PDCP RF RLC MAC PDCP
PHY PHY

Distributed Unit (DU) Centralized Unit (CU) DU CU

Split 6 Split 8
MAC PDUs IQ Time Domain
RF PHY MAC RLC PDCP RF PHY MAC RLC PDCP

DU/CU DU CU
 28

RAN Split Logical View

CU/DU
Split 8 Split 7 Split 6 Split 5 Split 2
PDCP PDCP PDCP PDCP PDCP
RLC RLC RLC RLC
To OpenRAN
MAC MAC MAC MAC
Controller
PHY PHY RLC
RRU
MAC MAC
PHY PHY PHY PHY PHY
RF RF RF RF RF
CPRI Split PHY MAC/PHY Split MAC PDCP/RLC
Delay IDEAL DELAY GOOD DELAY NON-IDEAL DELAY
Requirements ~100US (one way) ~0.5-1ms (one way) ~1-10ms (one way)

BEST PERF. LAST PERF.

IMPROVEMENT IMPROVEMENT

5200 Mbps 2600 Mbps 410 Mbps 410 Mbps 410 Mbps User throughput
(Reference): 370Mbps*

Support of multiple splits on the

Best for 2G, 3G Best for 4G, 5G
same RRU for ALL G
 29

Split option 7.2x for OpenRAN

Packet Packet Packet

Core Core Core
➢ The 7.2x split is the ideal
solution between bringing this
technology to market fast and
minimizing implementation
Backhaul Backhaul Backhaul expenses.

Layer 3
CU Layer 3
CU Layer 3
CU
➢ It decreases uncertainty
Mid-haul Mid-haul regarding split-specifics while
Mid-haul
Layer 2 Layer 2 simultaneously reducing traffic
DU DU
Higher
Layer 1
Layer 1 and enhancing traffic-
Fronthaul Fronthaul
reduction gains.

Layer 2

Layer 1 DU + RU
Lower
Layer 1 DU + RU RU
➢ Based on Open RAN
specifications, the functional
Split 2 Split 7.2 (O-RAN) Split 8
modules of the PHY layer are
split between Low-PHY and
Highest fronthaul bandwidth
Higher latency
requirement High-PHY in this split option.
 30

Why is eCPRI used for 5G and OpenRAN?

• 2-8 TRX branches
• 20 MHz carries
• Up to 8 layers
4G Radio Access Network (eNB)
2G/3G/4G
Air Coax Fronthaul Backhaul
Mobile
Interface
Antenna
cabling
Radio
CPRI
Baseband
(S1)
Core
➢ eCPRI is an open interface that makes it
easy for MNOs to choose different
device Unit Network
2.5G-10G 100M-1G

100M-1G
suppliers for RUs and DUs, unlike CPRI,
X2
(to neighbouring basebands) which is regarded as proprietary because
each vendor implements CPRI
5G Radio Access Network (gNB)
independently, and as we are aware,
Distributed Unit (DU) Central Unit (CU)
openness is the foundation of Open RAN.
Backhaul
(NG, Xn)
5G/5G+ F1-C
CU-UP
Air Fronthaul Radio control
Mobile
device
Interface
Antenna
Array
Radio
Unit
CPRI
RAN
Compute
1G-10G E1
Core
Network
➢ And, unlike CPRI, eCPRI's traffic may be
10G-50G
CU-UP
Radio control
transported on Ethernet, a crucial feature
50-75G F1-U
for the growth of open RAN because
Coordination Interlace Ethernet supports virtualization by
(to neighboring RAN computes)
LLS HLS •
•
64-256 TRX branches
100 MHz carries allowing fronthaul traffic to transfer
• Up to 16 layers
• Multi-band (incl. high-band) between physical nodes using standard
networking equipment.
RAN and Fronthaul Interface Evolution in5G
 31

Difference between eCPRI and CPRI

CPRI Protocol Stack eCPRI Protocol Stack

Control & Control &
User Plane Management Sync User Plane Management Sync
Plane Plane

PTP or
eCPRI Protocol Layer SNMP
SynE

Inband Protocol
Vendor specific

Ethernet

Layer 1
HDLC

Layer 2 IQ Data
Layer 4 UDP UDP/TCP etc.

Layer 3 IP UDP/TCP etc.

Division MultiplexTime Layer 2 Ethernet

Layer 1
Electrical Optimal
Transmission Transmission Layer 1 Electrical or Optimal Transmission
 32

Implementation of DU and CU

The intention of Separating:

RADIO

Option Option Option Option

Option 8
7.2x 7.2x 7.2x 7.2x

➢ To minimize cost - less

CPRI eCPRI eCPRI eCPRI eCPRI
intelligent RUs cost less

➢ Capability to view a sector

AT SITE

DU-
DU-Bare DU-Bare DU- DU+CU-
Containerized
Metal Metal Containerized
on VNF
Containerized
of RUs simultaneously
Option 2 Option 2 Option 2 Option 2 D-RAN
(rather than a single RU).

➢ Pooling of resources: the

CENTRAL

CU-
CU-Bare
Metal
CU-Bare
Metal
CU-
Containerized
Containerized processing is performed in
on VNF
the DU.

➢ For optimum latency

Variables: support, software for
What types of x86 hardware should be used?
What are the key transmission latency & BW, consideration for each type of deployment? baseband functions DU
Whether to use Bare Metal or Virtualization? and CU is separated from
System integration & commercial
hardware and deployed on
NFVI or in containers.
 33

O-RAN Control Loops

Service Management and Orchestration Framework

Typical Ranges

Non-RT
Non-Real Time RIC O1
3GPP interfaces The O-RAN architecture
control loops
O2 O1 A1
O-RAN interfaces supports at least the
For future study
Non-Real Time control loops following control loops
Near-Real Time RAN Intelligent
Near-Real Time control loops
involving different O-RAN
Real Time control loops
>=~1s
Controller (RIC) functions:
E2 E2 X2-c
Near-RT
control loops O-eNB O-CU-CP E1
X2-u • Non-RT (Non-Real
E2 O-CU-UP NG-u Time) control loops
Xn-u
>=~10ms<~1s
Open Fronthaul E2
Xn-c • Near-RT (Near-Real-
M-Plane
F1-c F1-u
NG-c
Time) control loops
O-DU • RT (Real Time) control
Open Fronthaul CUS-Plane Open Fronthaul M-Plane loops
<~10ms RT control loops O-RU

O-Cloud
 Address
465 W President George
Bush Hwy

Thank You Contact Number

+1 214 575 4500

Email
www.mcpsinc.com