---
# System prepended metadata

title: Daily Report day 1 (Afternoon)

---

# Daily Report day 1 (Afternoon)
:::    success
19/07/2021
:::

## 1. Aspects : Introduction to (O-RAN) and 5G Standard

:::info
### A. 5G Network Operation Mode
Has 2 Operation modes :
- Non-Stand-Alone (NSA)
![](https://i.ibb.co/qmdBfZb/2021-07-20-22h56-47.png)
<center>Fig. 1.A.1. NSA Operation</center>

- Stand-Alone (SA)
![](https://i.ibb.co/jDcXbWt/2021-07-20-22h59-51.png)
<center>Fig. 1.A.2. SA Operation</center>

EPC is call network for 4G. NGC is next generation call network for 5G. ECP do Control Plane and User Plane betweeen LTE eNB and gNB but just User Plane for EPC to gNB. NGC do Control Plane and User Plane for all.
:::

:::info
### B. RAN Transformation

![](https://i.ibb.co/H7Z3Vp2/2021-07-20-23h20-05.png)
<center>Fig. 1.B.1 Transformation of RAN</center>
Mobile Core connnect serial network with User Equipment by LTE eNB from base station that has BBU and RRU. BBU have network management function of monitoring/logging/config/control portal. Control portal by OSS/BSS and provide by mobile operator, management interface system. SON is AI for eNB.

![](https://i.ibb.co/87xXkFk/Group-33-1-1.webp)
<center>Fig. 1.B.2 RAN Transformation</center>
Operators, through the O-RAN consortium, are advocating for a disaggregation of RAN networks into interoperable RU, DU, CU components.
:::

:::info
### C. O-RAN Architecture

![](https://i.ibb.co/1XTWMCF/Group-15a-1-png.webp)
<center>Fig. 1.C.1 O-RAN Architecture</center>
A near real-time RIC (RAN Intelligent Controller) is integral to the O-RAN architecture. The nRT-RIC supports xApps responsible for advanced functions (like handover) that historically have been opaque vendor proprietary functions embedded in the base stations.
The SD-RAN project is building an open source nRT-RIC and exemplar xApps to accelerate the adoption of the O-RAN architecture and the availability of interoperable O-RAN components.

![](https://i.ibb.co/6PmZMFJ/o-ran-alliance-reference-architecture.png)
<center>Fig. 1.C.2 O-RAN Alliance Reference Architecture</center>
OpenRAN is also defining an open white box device using standard server and accelerator components that meet the needs of operators for the speeds and densities required for 5G NR. The TIP projects use O-RAN interfaces and specifications.

![](https://i.ibb.co/zXtNR7k/High-Level-Architecture-of-O-RAN.png)
<center>Fig. 1.C.3 O-RAN Architecture</center>
The key elements of the Alliance’s O-RAN architecture are:

- Service Management and Orchestration Framework (SMO)
- RAN Intelligent Controller (RIC)
- O-Cloud
- O-RAN central unit (O-CU)
- O-RAN distributed unit (O-DU)
- O-RAN Radio unit (O-RU)

Non-Real Time (> 500 ms) RAN Intelligence Controller (non-RT RIC)
- perform policy management, RAN analytics, and AI-based function management

Near-Real Time (< 500 ms) RIC (near-RT RIC)
- Provide radio resource management (RRM) functions (e.g., load balancing, RB management, QoS management, seamless handover control) with embedded intelligence. AI/ML workflow

Multi-RAT CU Protocol Stack
- Support virtualization abd 3GPP F1/W1/E1/X2/Xn interfaces

O-DU and O-RAN radio Unit (O-RU)
- real-time Layer 2 (L2) functions; BB, and radio signal processing

#### Non-Real Time RIC
- Programming language used mainly: JSON, Shell, and Java. Python is also used.
- Total file count is 367
- Total LOC is 33,418

#### Near-Real Time RIC
- Near-RT RIC consist of 2 groups: ric-app & ric-plt. Total components to track is 47 components (14+33)
- Programming language used are mainly: C/C++, Python, and Go. Shell, Docker, JSON, and XML are also used.
- Total file count is 11,747 (7825+3922)
- Total LOC is 1,615, 795 (963,717+652,078) 

#### O-CU
- Programming language is: C/C++
- Total file count is 73
- Total LOC is 10,173

#### O-DU
- O-DU concists of 2 groups: O-DU High & O-Du Low
- Programming language is: C/C++
- total file count is 2,974 (2774+200)
- Total LOC is 555,480 (508,315+74,165)
:::

:::info
### D. Software Architecture for O-RAN

![](https://i.ibb.co/K6fgtxS/2021-07-21-00h07-46.png)
<center>Fig. 1.D.1 O-RAN Software Architecture</center>
:::

:::info
### E. Vision of O-RAN

- Intelligence and Standardization
- Open Source and Virtualization
- White box and Reference design
![](https://i.ibb.co/XxP7Zbg/2021-07-20-23h49-42.png)
<center>Fig. 1.E.1 Vision of O-RAN</center>
:::

:::info
### F. Benefits of O-RAN Architecture

O-RAN is capable of:
- reducing network CAPEX and OPEX
- improving network efficiency and performance
- importing new capability with great agility
:::

:::    info
### G. O-RAN Key Use cases
Phase 1:
- White-box hardware design
  - Low Cost Radio Access Network White-box Hardware (O-DU, O-RU, Fronthaul Gateway)
- AI-enabled RAN and Open RAN Interfaces (O1/A1/E2)
  - Traffic Steering
  - QoE Optimization
  - QoS Based Resource Optimization
  - Massive MIMO Optimization

Phase 2:
- AI-enabled RAN and Open RAN Interfaces (O1/A1/E2)
  - RAN Slice SLA Assurance
  - Context Based Dynamic Handover Management for V2X
  - Flight Path Based Dynamic UAV Resource Allocation
  - Radio Resource Allocation for UAV Applications
- Virtual RAN Network
  - RAN Sharing
:::

## 2. Summary
:::info
### A. O-RAN Summary

<iframe src="https://drive.google.com/file/d/1lRvhJ9jfLfQ0qH6CcuoTUTMeuur2YKZg/preview" width="100%" height="400"></iframe>

<center>O-RAN Summary</center>
:::

## 3. Comment
Open Radio Access Network (O-RAN) is a concept based on interoperability and standardization of RAN elements including a unified interconnection standard for white-box hardware and open source software elements from different vendors. 

---
# <center>Discussion with Team</center>

1. Introduce Ourself
2. Discuss About Video Assignments
3. Discuss About Next Meeting