---
# System prepended metadata

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

---

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


---

## Schedule:
1. Study background ( what ? why ? how ? ) about V2x Communication.
2. Study about implementing V2x Communication using Non- RT RIC.
3. Study detailed architecture of Near - RT RIC.

## Outcome : 
1. Explain the detailed background of V2x Communication.
2. Explain detailed works of implementing V2x Communication using Non- RT RIC.
3. Explain general architectures of Near- RT RIC.
## Further Plan : 
- Study Detailed work of xApps in Near- RT RIC
- Study more detailed about AIO Installation in Kubernets
- Try to deploy Acumos AIO in NTUST server


---

## Daily Log

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

### 2. Study background ( what ? why ? how ? ) about V2x Communication.<mark>(11.30)</mark>
- Study more detail explanation in [Reference](https://www.zdnet.com/article/what-is-v2x-communication-creating-connectivity-for-the-autonomous-car-era/) and other resources.


### 3. Study about implementing V2x Communication using Non- RT RIC. <mark>(12.00)</mark>
- Study more detail explanation in [documentation](https://static1.squarespace.com/static/5ad774cce74940d7115044b0/t/5eba82a1a2f250476651b033/1589281448944/O-RAN.WG2.Use-Case-Requirements-v02.00.pdf) and [Reference](https://www.zdnet.com/article/what-is-v2x-communication-creating-connectivity-for-the-autonomous-car-era/)

### 4. Study detailed architecture of Near - RT RIC.<mark>(16.00)</mark>
- Study more detail explanation in [Work Group's Notes](https://www.o-ran.org/specification-access) and other resources.


---

## Report


### 1. What is V2x Communication?

> In this note Writer use [Reference](https://www.zdnet.com/article/what-is-v2x-communication-creating-connectivity-for-the-autonomous-car-era/) and [Akmal's Notes](https://hackmd.io/@akmalns/B1lM_HYkD) as study sources. 

#### What is V2x Communication?

From reference , Vehicle to everything ( ususally called "V2x" ) is the **term for the car’s communication system where information from sensors and other sources travels via high-bandwidth, low-latency, high-reliability links, paving the way to fully autonomous driving**. There are some components of V2x communication as below.

1. Vehicle to Vehicle ( V2V )
2. Vehicle to Infrastructures ( V2I )
3. Vehicle to Pedestrians ( V2P )
4. Vehicle to Communication ( V2C )

#### How does V2x Work ?

The simple works scheme can be shown as below.

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

There are two main standard widely used now in V2x Communication that is **IEEE 802.11p** and **Cellular V2X**. The comparison can shown as below.

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

#### Why using V2X Communication ?
In the future, **V2X communication will increase autonomous vehicle safety and reliability**. This picture below is the direct communication for active safety use cases.

---

### 2. Implement V2x Communication Using Non- RT RIC

> In this note Writer use [Reference](https://www.zdnet.com/article/what-is-v2x-communication-creating-connectivity-for-the-autonomous-car-era/) and [O-RAN Non-RT RIC & A1 Interface : Use Cases and Requirements 2.0 - April 2020](https://www.o-ran.org/s/O-RANWG2Use-Case-Requirements-v0200.pdf) as study sources. 

####  Context-based dynamic handover management for V2X

Part of the V2X architecture is the V2X UE (SIM + device attached to vehicle) which communicates with the V2X application server. The exchanged information comprises Cooperative Awareness Messages (CAMs), radio cell IDs, Connection IDs, and basic radio measurements.
As vehicle traverse along a highway, due to their high speed and the heterogenous naturan environment V2X UE-s are handed over frequently which may cause handover (HO) anomalies: e.g., short stay, ping-pong and remote cell. This anomalies could disturb the functionality of V2X applications.

This use case aims **to present a method to avoid and/or resolve problematic HO scenarios by using past navigation and radio statistics in order to customize HO sequences on a UE level**.

---

### 3. Implementing Context- based Dynamic HO using Non- RT RIC

Systems that works in this process:

- **Non-RT RIC** 
  - Retreive necessary performance, configuration and other data for constructing/training relevant AI/ML models that will be deployed in Near-RT RIC to assist in the V2X HO management function.
  - Support deployment and update of AI/ML models into Near-RT RIC xApp
  - Support communication of intents and policies (system-level and UE-level) from Non-RT RIC to Near-RT RIC
  - Support communication of Non-RAN data to enrich control function in Near-RT RIC (enrichment data)
- **Near-RT RIC**
  - Support update of AI/ML models retreived from Non-RT RIC
  - Support interpretation and execution of intents and policies from Non-RT RIC
  - Support necessary performance, configuration and other data for defining and updating intents and policies for tuning relevant AI/ML models
  - Support communication of configuration parameters to RAN
- **RAN**
  - Support data collection with required granularity to SMO over O1 interface
  - Support Near-real-time configuration-based optimization of HO parameters over E2 interface
  - Report necessary performance, configuration and other data for performing real-time V2X HO optimization in the near-RT RIC over E2 interface
- **V2X Application Server**
  - Support data collection with required granularity from V2X UE over V1 interface
  - Support communication of real-time traffic related data about V2X UE to Non-RT RIC as enrichment data.

The detailed process can be shown as below.

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


The requiered data:

:::info
The measurement counters and KPIs (as defined by 3GPP) should be appropriately by cell, QoS type, slice, etc.
:::

1. Measurement reports with RSRP/RSRQ/CQI information for serving and neighboring cells.
2. UE connection and mobility/handover statistics with indication of successful and failed handovers and error codes etc.
3. V2X related data: position, velocity, direction, navigation data, CAMs.

---
### 4. Architectures of Near - RT RIC

> In this note Writer use [WG3 - The Near-real-time RIC and E2 Interface Workgroup](https://www.o-ran.org/specification-access) and [Ferlinda's Notes](https://hackmd.io/@ferlinda/SkvEbeWRI) as study sources. 
> 
#### General Architectures

Near RT- RIC general architectures can be seen as below.

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


#### General Function

From Ferlinda's Notes, the general function of architectures above can be explained as below.

1. **Database** that allows reading and writing of RAN/UE information 
  - UE related information to be stored in the **UE-NIB (UE-Network Information Base)** database.
  - RAN related information to be stored in the **R-NIB (Radio-Network Information Base)** database.
2. **xApp subscription management** that merges subscriptions from different xApps and provides unified data distribution to xApps.
3. **Conflict mitigation** that resolves potentially overlapping or conflicting requests from multiple xApps.
4. **Messaging infrastructure** that enables message interaction amongst Near-RT RIC internal functions.
5. **Security** that provides the security scheme for the xApps.
6. **Management services** which consists of: 
  - **Fault management, configuration management, and performance management** as a service producer to SMO;
  - **Life-cycle management** of xApps;
  - **Logging, tracing and metrics collectio**n, which capture, monitor and collect the status of Near-RT RIC internals and can be transferred to external system for further evaluation;
7. **Interface Termination** which consists of: 
  - **E2 termination** which terminates the E2 interface from an E2 Node.
  - **A1 termination** which terminates the A1 interface from the non-RT RIC.
  - **O1 termination** which terminates the O1 interface from Service Management & Orchestration layer.
8. **Functions hosted by xApps** which allow services to be executed at the Near-RT RIC and the outcomes sent to the E2 Nodes via E2 interface.

:::info
**Next Writer will try to learn more details of xApps works in Near- RT RIC.**
:::

---


## Reference
1. https://www.zdnet.com/article/what-is-v2x-communication-creating-connectivity-for-the-autonomous-car-era/
2. https://www.o-ran.org/specification-access