---
# System prepended metadata

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

---

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


---

## Schedule:
1. Study Detailed Works of E2 Service Models.
2. Study Detailed Works of RAN Function Network Interface ( NI ).
3. Continue to try installing Acumos AI in NTUST Server.


## Outcome : 
1. Explained Detailed works of E2 Services Models.
2. Explained Detailed Works of RAN Function Network Interfaces ( NI ) .
3. Successfully set up Kubernetes Cluster in NTUST Server.


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



---

## Daily Log


### 1.Study Detailed Works of E2 Service Models. <mark>(9.00)</mark>
- Study more detail explanation in [Documentation](https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=3604819 ) and other sources.


### 2.Study Detailed Works of RAN Function Network Interface ( NI ). <mark>(11.00)</mark>
- Study more detail explanation in [Documentation](https://www.o-ran.org/s/ORAN-WG3E2SM-KPM-v0100.docx) and other sources.

### 3.Continue to try deploying Acumos AIO in NTUST server. <mark>(13.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. How E2 Service Models Work ?

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

#### What is E2 Services Model

From reference, RAN Function offers a set of services to be exposed over the **E2** (report  insert , control adn policy) using **E2AP** defined procedures. 

Each of the E2AP Procedures contains specific E2 Node RAN Function dependent Information Elements (IEs), most are part of **RIC Functional procedures**.

From Ferlinda's notes , the list of procedures can be seen as below.


|RAN Function specific E2AP Information Elements|Related E2AP Procedures|
|---|---|
|RIC Event Trigger Definition IE|RIC Subscription|
|RIC Action Definition IE|RIC Subscription|
|RIC Indication Header IE|RIC Indication|
|RIC Indication Message IE|RIC Indication|
|RIC Call Process ID IE|RIC Indication, RIC Control|
|RIC Control Header IE|RIC Control|
|RIC Control Message IE|RIC Control|
|RIC Control Outcome IE|RIC Control|
|RAN Function Definition IE (Global Procedures)|E2 Setup, RIC Service Update|

#### Supported O- RAN Specified Service Models

There are 2 supported O- RAN Specified SM as below.

1. **E2SM Network Interface (NI )**
2. **E2SM KPM**

The detailed specifictaions of bth SM can be seen as below.

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




---

### 2.  E2SM Network Interfaces

>In this note Writer use [Documentation](https://wiki.o-ran-sc.org/display/RICNR/Release+A) as study sources.

#### What is E2SM Network Interfaces ?

E2 Node terminating the E2 Interface is assumed to host the RAN Function NI which performs as belwo.

1. **Exposure of Network Interfaces**
2. **Modification of both incoming and outgoing network interface message contents**
3. **Execution of policies that may result in change of network behavior**

#### E2SM NI Functions

From reference, the functionality of E2SM NI can be seen as below.

1. **Report** service 
- **Copy of Complete message** with **header providing network interface type, identifier and direction** with optional network interface timestamp.
- **Copy of Partial message** selected by target message protocol IE identifier with with header providing network interface type, identifier, direction and message type with optional network interface timestamp.
2. **Insert**
- **Copy of Partial message** selected by target message protocol IE identifier with with header providing network interface type, identifier, direction and message type with optional network interface timestamp.
3. **Control service** 
- **Injection of Complete message** with header providing target network interface type, identifier and direction and optional RIC Control Message Priority.
4. **Policy service** 
- **Handling of Message Admission process** according to a list of parameters to be applied to different RAN UE groups.



#### RAN Function Description

From reference the RAN Function Description can be seen as below.

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

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


#### RAN Functionality

From the table above there are 5 types RIC Services and Style as below.

#####  1. Event trigger definition styles
#### Style: Interface message Event


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

**Function:** used to detect a specific interface message event in E2 Node RAN Function based on specified target Network Interface Type, Network Interface Identifier, Network Interface Direction, Network Interface Message Type, Message Protocol IE Identifier, Message Protocol IE Test Condition and Message Protocol IE Test Value.



##### 2. Supported RIC REPORT Service styles

There are 2 main styles as below.

![](https://i.imgur.com/Cnqw0HY.png)
1. **Style: Complete message**
    * RIC Action Definition IE contents
        * ![](https://i.imgur.com/Q0AH3jF.png)
    * RIC Action Definition IE contents (refer to blue box above)
    * RIC Indication message IE contents (refer to blue box above)
2. **Style: Partial message**
    * RIC Action Definition IE contents
        * ![](https://i.imgur.com/3TUfzx4.png)
    * RIC Indication header IE contents (refer to blue box above)
    * RIC Indication message IE contents (refer to blue box above)

##### 3. Supported RIC INSERT Service styles
##### Style: Complete Message
![](https://i.imgur.com/e7rbnv4.png)

* RIC Action Definition IE contents
    * ![](https://i.imgur.com/ofbgqmI.png)
* RIC Indication header IE contents (refer to blue box above)
* RIC Indication message IE contents (refer to blue box above)
* RIC Call Process ID IE contents
    * contains identifier used by the RAN Function to match the outgoing INSERT Service message with a subsequent incoming CONTROL Service message.
    * uses RIC Call Process ID type 1 to carry a local RAN Function assigned call process instance sequence number that, under normal traffic conditions, shall be unique to the given RAN function instance for a period of 1 hour.

##### 4.Supported RIC CONTROL Service styles
##### Style: Complete Message
![](https://i.imgur.com/YbAEGCV.png)
* RIC Control Header IE contents
    * contains the following information Network Interface Type, Network Interface Identifier and Network Interface Direction and the optional RIC Control Message Priority. 
    * uses RIC Control Header Format 1 .
* RIC Control Message IE contents
    * contains a transparent container used to carry the complete message with contents defined by the specific network interface specification.
    * uses RIC Control Message Format 1.
* RIC Call Process ID IE contents
    * contains identifier used by the Near-RT RIC to allow the RAN Function to match the outgoing **INSERT** Service message with a subsequent incoming **CONTROL** Service message.
    * uses RIC Call Process ID IE Format 1.
* RIC Control Outcome IE contents
    * contains a transparent container used to carry the outcome of executing the RIC Control Request.
    * ![](https://i.imgur.com/jZR68lX.png)

##### 5. Supported RIC POLICY Service styles
##### Style: Message Admission
![](https://i.imgur.com/nlajiBa.png)

* RIC Action Definition IE contents
    * uses RIC Action Definition IE Format 2, where:
        * RAN UE group is described in terms of a list of test conditions using RAN Parameters.
        * Imperative E2 Policy is encoded in terms of a list of specific RAN Parameters and shall be applied to any UE within a given RAN UE Group.


:::info
**Next writer will study Message Functional Definition and Content from Ferlinda's Notes** 
:::


---

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

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

To solve previous problems, Writer reboot the server to stop the old- installed Open Shift.

Then Writer use the command again as below.

```
bash system-integration/tools/setup_k8s_stack.sh setup
```
![](https://i.imgur.com/0Or03tY.png)

Then the Kubernetes Cluster on Open Shift

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

---



## 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
