---
# System prepended metadata

title: Daily Note 29/07/2020
tags: [O-RAN, Daily Notes, Acumos]

---

# Daily Note 29/07/2020
###### tags: `Daily Notes` , `O-RAN` , `Acumos`
## Name : Christofel Rio Goenawan
## University : Bandung Institute of Technology (ITB)


---

## Schedule:
1. Weekly Meeting
2. Study Non-RT RIC on O-RAN Software Community.
3. Study Non- RT RIC Development Guide.
4. Continue to try installing Acumos AI in NTUST Server


## Outcome : 


## Further Plan : 
- Continue to deploy Acumos AIO in NTUST server
- Study more detailed about AIO Installation in Kubernets



---

## Daily Log

### 1.Weekly Meeting. <mark>(9.00)</mark>
- In this meeting Writer presents the progress and latest result to Prof Ray, mentors and internee.


### 2.Study Non-RT RIC on O-RAN Software Community. <mark>()</mark>
- Study more detail explanation in [Documentation](https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=3604819 ) and other sources.

### 3.Study Non- RT RIC Development Guide. <mark>()</mark>
- Study more detail explanation in [Documentation](https://wiki.o-ran-sc.org/display/RICNR/Release+A ) and other sources.

### 4.Continue to try deploying Acumos AIO in NTUST server. <mark></mark>
- Continue to try to deploy Acumos AIO in NTUST server using Prep- Deploy Process based one previous [study notes](https://hackmd.io/@christofel04/TEEP_Daily_Notes_10_7_2020).






---

## Report


### 1. Non-RT RIC on O-RAN Software Community

>TIn this note Writer use [Documentation](https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=3604819)  as study sources.

#### What is Non- RT RIC?

From reference, Non- RT RIC is **an Orchestration and Automation function described by the O-RAN Alliance for non-real-time intelligent management of RAN (Radio Access Network) functions**.

#### What is Objective of Non- RT RIC ?

The primary goal of the NONRTRIC is **to support non-real-time radio resource management, higher layer procedure optimization, policy optimization in RAN, and providing guidance, parameters, policies and AI/ML models to support the operation of near-RealTime RIC functions in the RAN to achieve higher-level non-real-time objectives**.

#### How Non- RT RIC works ?

From reference the simple works of Non- RT RIC can be seen as below.

1. Non- RT RIC will communicate with near-Real Time RIC elements in the RAN via the **A1 interface**. 
2. Using the A1 interface the Non- RT RIC will:
  - Facilitate the provision of policies for individual UEs or groups of UEs.
  - Monitor and provide basic feedback on policy state from near-RealTime RICs.
  - Provide enrichment information as required by near-RealTime RICs.
  -  Facilitate ML model training, distribution and inference in cooperation with the near-Real Time RICs. 

#### Functional Block

From refrence, the simple functional block scheme of Non- RT RIC on Software Community ( Non- RT RIC OSC ) can be seen as below.

![](https://i.imgur.com/p5IpKlx.png)

Many of the functions will be supported by the underlying **SMO platform**.

##### Latest Availability Functionality Scheme

The latest availability functionality scheme can be seen as below.

![](https://i.imgur.com/sZ4BaS1.png)

The figure above shows the latest released functionality for the Non-RealTime-RIC function in OSC (Amber+ Release & ONAP Frankfurt).
For more information see out [here](https://wiki.o-ran-sc.org/display/RICNR/Release+B)

#### Integration into ONAP

The simple schee of ontegration into ONAP can be seen as below.

![](https://i.imgur.com/XeeLFYz.png)


---

### 2.  Non- RT RIC Development Guide

>In this note Writer use [Documentation](https://wiki.o-ran-sc.org/display/RICNR/Release+A) and [Akmal's Note](https://hackmd.io/@akmalns/HkNBqO6kw) as study sources.

#### Release A

:::info
The code base for Release A is in the [**Non- RT RIC source repository (Gerrit)**](https://gerrit.o-ran-sc.org/r/gitweb?p=nonrtric.git;a=tree;h=refs/heads/master;hb=refs/heads/master)
:::
##### Architectures

The simple  architectures scheme of Non- RT RIC Release A can be seen as below.

![](https://i.imgur.com/5g1PvBj.png)

##### Components

The Non- RT RIC components can be seen as below.
1. **Policy Management GUI / NONRTRIC Dashboard** 
2. **Policy agent / A1 Policy Management Service**
3. **SDNC A1 Controller**
4. **Near-RT RIC Simulator**

##### 1. Policy Management GUI / NONRTRIC Dashboard

- View and Manage A1 policies in the RAN (near-RT RIC).
- Interacts with the policy agent’s NBI (REST API)
- Graphical A1 policy creation/editing is model-driven, based on policy type’s JSON schema
- Implementation : 
  - Frontend : Angular framework
  - Backend : Java Springboot Application

##### 2. Policy Agent / A1 Policy Management Service

- It provides :
  - Unified REST & DMAAP APIs for managing A1 policies in all near-RT-RICs
  - Synchronized view of policy instances for each R-APP
  - Synchronized view of policy instances in all near-RT-RICs
  - Synchronized view of policy types in all near-RT-RICs
  - Policy Query API
  - etc.

###### 3. SDNC A1 Controller

- Implemented as OSGI feature/bundles
- A1 Rest southbound
- NETCONF YANG Northbound
- RESTCONF > NETCONF adapter
- Mapping Logic/Provider
- Can be included in an any SDNC/CCSDK persona


##### 4. Near-RT RIC Simulator

- Used to create multiple stateful A1 providers (Simulated near-RT-RICs)
- Umplemented as a Java Springboot application
- Swagger-based northbound interface

---

### 3.  Continue to try deploying Acumos AIO in NTUST server 

>This note is countinuation from [Previous Notes](https://hackmd.io/@christofel04/TEEP_Daily_Notes_28_7_2020). In this note Writer use [Previous Notes](https://hackmd.io/@christofel04/TEEP_Daily_Notes_10_7_2020)  as study sources.

After releas the port for Open Shift Writer tried to set up Kubernetes Cluster again using  command in previous notes. 

But Writer got the error as below.

![](https://i.imgur.com/21rEwu6.png)


:::warning
Apparently the problem is because **there are another uncomplete Open Shift Installation in Server**. The solution is Writer will find the way to stop the existing Open Shift cluster and remove the installation.
:::

:::info
**Next Writer Will Continue to Install Acumos AIO in NTUST Server**
:::

---



## Reference
1. https://wiki.o-ran-sc.org/display/ORANDU/O-DU+High
2. https://www.o-ran.org/specification-access
3. https://docs.o-ran-sc.org/en/latest/architecture/architecture.html
4. https://docs.acumos.org/en/clio/submodules/system-integration/docs/oneclick-deploy/user-guide.html
