---
# System prepended metadata

title: 'RAN Intelligent Controller (RIC), Network Management and Security'
tags: [5G O-RAN, PNJ, ITB NTUST 5G course]

---

# RAN Intelligent Controller (RIC), Network Management and Security
Day 8: July 29th, 2021

###### tags: `PNJ` `5G O-RAN` `ITB NTUST 5G course`

:::success
### 3 Most Important Aspects
1.	RIC (RAN Intelligent Controller)
2.	RIC Interfaces
3.	Network Management and Security
:::

:::info
### Summary
1.	RIC (RAN Intelligent Controller)
RIC for Open RAN was born to enable eNB/gNB functionalities as X-Apps on northbound interfaces. The main purpose of RIC is to configure or control RAN. Applications like mobility management, admission control, and interference management are available as apps on the controller, which enforces network policies via a southbound interface toward the radios. RIC provides advanced control functionality, which delivers increased efficiency and better radio resource management. These control functionalities leverage analytics and data-driven approaches including advanced ML/AI tools to improve resource management capabilities. RIC consists of Non-Real Time RIC and Near Real Time RIC.
•	**Non-Real-Time RIC (Non-RT RIC)**
Non-RT RIC supporting tasks that require > 500 ms latency. Non-RT RIC functionality includes configuration management, device management, fault management, performance management, and lifecycle management for all network elements in the network. It is similar to Element Management (EMS) and Analytics and Reporting functionalities in legacy networks. Non-RT RIC do service and policy management, collect the data to do analytics, and the important function is the model training for Near-RT RIC that means by collecting the data, Near-RT RIC need the user data to train AI.
•	**Near Real-Time RIC (Near-RT RIC)**
Near-RT RIC supporting tasks that require < 500 ms latency and is a near‐real‐time, micro‐service‐based software platform for hosting micro-service-based applications called xApps. Near-RT RIC has functions to do Radio Resource Management (RRM), QoS management, connectivity management, and seamless handover control. Near-RT RIC shall consist of:
    -	Multiple xApps
    -	A set of platform functions to support the specific functions hosted by xApps.

2.	RIC Interfaces
There are several interfaces in RIC:
•	**A1 Interface**
An A1 interface is used between the Orchestration/NMS layer with non-RT RIC and eNB/gNB containing near-RT RIC. The A1 interface support from Non-RT RIC to Near-RT RIC for transfer policy management and delivery of A1 enrichment information. Also support from Near-RT RIC to Non-RT RIC for policy feedback, discovery and request of A1 Enrichment Information.
•	E2 Interface
An A2 interface is used between Near-RT RIC and E2 Nodes that has support functions to interface management, Near-RT RIC Service Update, E2 setup, E2 reset, E2 node configuration update, and reporting of general error situations.
•	**O1 Interface**
An O1 interface is used between Non-RT RIC and other components that has function to support Non-RT RIC to do FCAP management, software management, and file management.

3.	Network Management and Security
**Network Management**
Network management encompasses all activities related to maintaining a healthy status of the network. The most accepted standardised model in this area is the FCAPS model, which separates network management tasks into five categories: 
•	**Fault Management**
Fault management is used to monitor the network, identify the key network infrastructure that is responsible for service outage, notify the impact and the estimated restoration time, and also mitigate the customer impact.
•	**Configuration Management**
Network configuration define the current state of the network. It is common used for customer services, traffic routing, security setting, element provisioning, and configuration update.
• **Accounting Management**
Accounting management is used for tracks service usage, enable usage restriction, throughput shaping, and customer billing.
•	**Performance Management**
Performance information can be user real-time for fault detection and long-term for improving the product performance and tracking of customer Service Level Agreement (SLA)
• **Security Management**
Security plays a support role to other management function to do configuration that restrict access to network element to reduce the amount of change. It also has function in billing that data security to reduce fraudulent transactions and maintain accurate records. O-RAN security protocol in 5G are SSHv2 and Transport Layer Security (TLS).

**Security**
The objective of communication security is the preservation of three principles: confidentiality, intregrity, and availability.

:::info
### Comment
The Near-RT RIC is responsible for creating a software platform for a set of xApps for the RAN; non-RT RIC provides configuration, management and analytics functionality. For Open RAN deployments to be successful, both functions need to work together to helps strengthen a multi-vendor open ecosystem of interoperable components for a disaggregated and truly open RAN. 
:::

:::success
### Discussion Team
1. Discuss about our main theme for final project
2. Explain our sub-topic that we choose before
3. Makes the powerpoint together
4. Presentation trial
:::

