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

---

## Schedule:
1. Weekly Meeting and Meeting with Compal.
2. Study Detailed Works of Near RT- RIC Clusters RICAPP.
3. Continue to try installing Acumos AI in NTUST Server.

## Outcome :
1. Explained detiled works of KPM.
2. Create Slide Presentation for Tomorrow's Meeting with Akmal.
3. Couldn't find server name that asked by command when try to set up needed services in NTUST server.

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

---

## Daily Log

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

### 2.Study Detailed Works of Near RT- RIC Clusters RICAPP.<mark>(11.30)</mark>
- Slide Presentation can be seen [here](https://docs.google.com/presentation/d/1L2bpcbmDt7wbZuDUOJFIZ-DOy-2Jy4TeRIIDNWPqw8E/edit?usp=sharing).

### 2.Continue to try deploying Acumos AIO in NTUST server. <mark>(15.00)</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. Near- RT RIC Cluster RICAPP

>In this note Writer use [Documentation](https://www.o-ran.org/s/ORAN-WG3E2SM-v0100.docx) and [Ferlinda's Notes](https://hackmd.io/@ferlinda/S1j7WCckD) as study sources.

#### RIC Installation Architectures

From references, simple architectures of RIC Installation Architectures can be shown as below.


The simple clusters scheme can be seen as below.


#### RICAPP Cluster

From scheme above , there are 4 main components as below.

1. **Admission Control**
2. **Measurement Campaign**
3. **ML- Based**
4. **Key Performance Indicators (KPI) Monitor**

#### Admission Control
> Writer use the [documentation](https://docs.o-ran-sc.org/projects/o-ran-sc-ric-app-admin/en/latest/overview.html) as study references.

- Can execute the **full control loop to regulate the number of 5G connection requests at a gNodeB**.
- Responsible for as below.
- **subscribes and listens** for SgNBAdditionRequest message in the gNB
- Executing logic to **determine if a dual connection should be accepted or rejected** and generating the RIC CONTROL message
- **Update metrics of decision** above: If the decision is to accept the request, it sends an SgNB Addition Acknowledge, else it sends an SgNB Addition Reject message.
- Repo will handle:
- E2 subscription process
- **Encode/decode E2AP Indication/Control messages**
- X2AP SgNB Addition Request/Response
- **supports A1-interface** (can be used to send policies to configure AC behaviour)
- Control via A1:
- Example of received policy via A1:

  - Example of response on successful application of policy  : 

- Repo: ric-app/admin

#### Measurement Campaign
> Writer use the [documentation](https://wiki.o-ran-sc.org/display/RICA/Measurement+Campaign+xApp?src=contextnavpagetreemode) as study references.

- Calculates a number of **metrics and KPIs based on X2 messages formatted as protobufs** as defined in /ric-plt/streaming-protobufs.
- **Compute 5G KPIs at customized fine-grained granularities** in the following manner:
- **per-UE per-bearer basis**
- **per-UE basis**
- **UE-group basis**
- **NR cell-wide basis**
- **NR gNB-wide basis**
- Key 3GPP EN-DC X2AP procedures handled in the MC xApp include:
- SgNB Addition
- SgNB Release
- SgNB Modification
- RRC Transfer
- Secondary RAT Data Usage Report
- Repo: ric-app/mc

#### ML-based
> Writer use the [documentation](https://wiki.o-ran-sc.org/display/RICA/ML-based+xApp?src=contextnavpagetreemode) as study references.

- Using Acumos ML models in the RIC
- Amber Release features can be seen as below.
- Repo: ric-app/ml

#### Key Performance Indicators (KPI) Monitor

> Writer use the [documentation](https://wiki.o-ran-sc.org/display/RICA/KPI+Monitor+xApp) as study references.

- Provides the **first step towards the successful closed-loop control**, through the monitoring E2 Node’s performance metrics, and writing it into Redis DB.
- Includes:
- **UE measurement**
- **E2 Node Measurement**
- **E2 Node Load-related measurement**
- With KPIs reports, the near Real-Time RIC can immediately control E2 Nodes.
- Repo: ric-app/kpimon

#### Other Functions

From Ferlinda's notes, other functions of RICAPP clusters can be seen as below.

* [Alarm Go Library](https://docs.o-ran-sc.org/projects/o-ran-sc-ric-plt-alarm-go/en/latest/index.html)
* RIC Alarm System
* Repo: ric-plt/alarm-go
* [GS-lite Stream Processing Engine](https://docs.o-ran-sc.org/projects/o-ran-sc-com-gs-lite/en/latest/index.html)
* An open-source, real-time, low-latency, high-throughput stream processing engine.
* Repo: com/gs-lite
* [HelloWorld xAPP](https://docs.o-ran-sc.org/projects/o-ran-sc-ric-app-hw/en/latest/index.html)
* Contains open-source code for a prototype xAPP for near real-time RAN Intelligent Controller.
* Aims to provide basic implementation of:
* E2, A1 interfaces interactions
* Read-write operations into a persistent storage
* xAPP Configuration management
* RMR & A1 Healthcheck
* Repo: ric-app/hw
* [QoE Predictor xApp](https://docs.o-ran-sc.org/projects/o-ran-sc-ric-app-qp/en/latest/index.html)
* An Xapp in the Traffic Steering O-RAN use case below
* Uses the following Xapps:
* Traffic Steering, which sends prediction requests to QP Driver.
* QP Driver, which fetches data from SDL on behalf of traffic steering, both UE Data and Cell Data, merges that data together, then sends off the data to the QoE Predictor.
* QoE Predictor, which predicts and sends that prediction back to Traffic Steering
* KPIMONN, which populates SDL in the first place.
* The QP Xapp expects a prediction-request JSON message via RMR and should send a prediction for both downlink and uplink throughput as a JSON message via RMR.
* Repo:
* ric-app/qp
* ric-app/qp-driver
* [Traffic Steering xAPP](https://docs.o-ran-sc.org/projects/o-ran-sc-ric-app-ts/en/latest/index.html)
* Traffic Steering Use Case demonstrates intelligent inferences in the Near-RT RIC and E2 interaction in order to execute on the inferences.
* Current Use Cases:
* Traffic Steering xApp: Consume A1 Policy Intent, regularly monitor RAN metrics and request prediction for badly performing UEs, and listen for messages that show UE throughput predictions in different cells, in order to make a decision about UE Handover.
* QoE Prediction (QP) xApp: Receive a feature set of metrics for a given UE, and output Throughput predictions on the Serving and any Neighbor cells
* QoE Prediction Driver (QP Driver) xApp: Generate a feature set of metrics to input to QoE Prediction, based on SDL lookups in UE-Metric and Cell-Metric namespaces
* Repo: ric-app/ts

:::info
**Next Writer will study more about RIC Global Procedures Elements**
:::

---

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

>This deployment is continuation from [yesterday's notes]( https://hackmd.io/@christofel04/TEEP_Daily_Notes_04_8_2020 ).
In this note Writer use [Previous Notes](https://hackmd.io/@christofel04/TEEP_Daily_Notes_10_7_2020) as study sources.

Writer still try to solve the host asked by command. This time Writer try to find server **host name , IP address and domain**.

:::danger

But when Writer use the name, the command still don't recognize it.


:::

:::info
**Next Writer Will Continue to Find the Server's Name For the Command**
:::

---

## Reference
1. https://www.o-ran.org/s/ORAN-WG3E2GAP-v0100.docx
2. https://www.o-ran.org/s/ORAN-WG3E2SM-KPM-v0100.docx
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