###### tags: `osc` `VIAVI` `Meeting minutes`
# Update Viavi - NTUST

### Meeting Name:
Update Viavi - NTUST

### Purpose / Objective:
Sync status of RIC tester with Viavi

### Date:
8/16/2022

### Note Taker:
Bimo

### Meeting Attendees:
- Baruch Friedman
- Mohammad Abaii
- Triantafyllos Zervas
- Ultan Kelly
- Agustin Pozuelo
- Ray
- Rico
- Yueh huan
- Bimo
- Winnie

### Agenda

1. **Topic**: NTUST present status of RIC tester
**Presenter**: Yueh-Huan
**Notes**:
- NTUST facing to subscription issue due to KPM V1.0. Baruch: may caused by incompatibility issues. Since KPM V2.0 is most up-to-date version. Should be solved by upgrade it.

2. **Topic**: Slices and potential coop in the future
**Presenter**: Baruch
**Notes**:
- In ric test today, we have 2 option for L2/l3 traffic with basic and advance mode.
- advance mode -> using part of NS3 to produce all different protocol for layer 2, PDCP and MAC and also Scheduler
- In version 1.3 we dont have advance mode for slices. But we support in basic mode for traffic model. If you want to do simulation for slices in 1.3 you need to use basic mode.
- There is a limitation in slices where you can only assign only 1 type in the UE. Advance mode is built to avoid this limitation.
- We are working on QoS support (target 1.4)

3. **Topic**: Slices demo
**Presenter**: Agustin
**Notes**: N/A
### Q&A

**Is there anyone in OSC work on KPMv2 ?**
- HCL updated KPIMon v2, Amit can be in touch from HCL. Can ask him for details.

**How many slices can support?**
- i dont think we have limitation for this.

**Is it possible to have different type of scheduler? The goal is to replace the existing scheduler with user-define scheduler. We looking the case from OSC for ODU which separate job e.g RLC, MAC they briefly define scheduler for each of them.**
- (Baruch)
- Should need to have support for this. Should use advance traffic mode.
- Maybe we need to have extend discussion for this.
- This is something that extemerly intereiting. If part of ODU can be controller from RIC then maybe by we can consider to enabling RIC tester to change parameter as an feature in the future.
- (Agustin)
- Not sure if its feasible but we want to do feasibility test.
- The practical way is to develop on top of NS3 code-base and then compile the same way we compile. NS3 code is GPL anyway so should be tweak it.
- We are building based on case for RIC part not considering (yet) the RU part
- (Zervas)
- From the NS3 perspective, need math equation to calculate weights, etc. We cannot use the same approach.
- Maybe we can think about this if we have clue on how specific module will act but for now cannot give proper answer, need further study.

### Next steps
For NTUST -> Please share the example of use case or study evidence about the need of custom scheduler.

For Viavi -> Please help to reach New Jersey's Viavi support team to share configuration of TM500

ODU High will do local dev
If we can achive slot indication and receiving signal from RU simulator, we can move towards UE simulator.

indication that PTP is up:
1. DU can receive PTP from RU simulator
2. Check C/U plane for indication
3.

1. In all scenario, we set up flexric with OSC or setup OAI gNB?
2. How to access the KPM-SM branch?
3. Yueh huan think tts impossible to test "Test type ‘O-RAN DU/NTUST ’" because in v1 and v2, starts from E2 setup procedure will not be able to decode due to unkonown RAN function.
4. What is the "SM unit tests" means? Is it just encode and decode message or it has other meaning?
5. What is pending developments?
6. In "Test type ‘3 nodes test’", How to find a file to be able to recompile for each component?
7. In OSC, Different e2 node will support different RAN function even if they support the same spec therefore based on spec, the xApps need to check the ran function. But from your MSC seems flexric decode e2ap and e2sm to get ran function. How xApps know the RAN function?