Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Table of Contents |
---|
Scope
The project aims to provide simulation solutions to all the projects that have such a need.
The project can be split according to the type of interfaces it simulates:
- A1
- E1
- E2
- F1
- FH
- O1
The project structure is flexible and it can be changed according to the needs of the other projects.
Project meetings
Currently, there is a weekly joined meeting with NON-RT-RIC on Mondays 14:00 UTC (9am EST, 10pm CST):
NOTE: During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of the meetings may fluctuate. Please keep a close eye on the project calendar.
Zoom: https://zoom.us/j/436210993
Development
Jira
https://jira.o-ran-sc.org/projects/SIM/summary
Gerrit
- https://gerrit.o-ran-sc.org/r/admin/repos/sim
- https://gerrit.o-ran-sc.org/r/admin/repos/sim/a1-interface
- https://gerrit.o-ran-sc.org/r/admin/repos/sim/e1-interface
- https://gerrit.o-ran-sc.org/r/admin/repos/sim/e2-interface
- https://gerrit.o-ran-sc.org/r/admin/repos/sim/f1-interface
- https://gerrit.o-ran-sc.org/r/admin/repos/sim/fh-interface
- https://gerrit.o-ran-sc.org/r/admin/repos/sim/o1-interface
Open issues in Jira
In the OSC Community Lab, a SMO instance was deployed, with inputs from the OAM, NONRTRIC and SIM projects. It is based on an ONAP post-Honolulu and pre-Istanbul release. The purpose for this deployment is to demonstrate, with the help of simulators initially, the Closed Loop Use Case proposed in this release.
OSC Community Lab deployment
The VM used for this deployment is 192.168.130.90
List of docker containers
The list of docker containers which are running can be seen in the below picture:
Image Added
ODLUX GUI
The topology simulated consists of an O-DU exposing the o-ran-sc-hello-world.yang and 3 O-RUs exposing the O-RAN FH YANG models from November 2020 train. The O-DU was connected using the VES pnfRegistration method, while the O-RUs are connected via NETCONF Call Home. We can see the NETCONF Servers are connected to the OAM-Controller via its ODLUX GUI, like in the below picture:
Image Added
Fault Management
The O-DU and O-RUs are configured to send events to the SMO: O-DU sending VES Fault Notifications, while the O-RUs send faults via NETCONF Notifications. The below picture shows the events as captured by the OAM-Controller:
Image Added
More detailed integration tests by OAM project can be found here.
NONRTRIC Dashboard
The NONRTRIC components are also deployed successfully. Below are some screenshots from its dashboard:
Image Added
Image Added
Detailed logs
We can see also in the logs of the OAM and NONRTRIC and their components that faults are being processed:
OAM Logs
Image Added
NONRTRIC Logs
Image Added
O-DU-HIGH
CLA use case demo with intel L1 and netconf CLI
This video contains demo of CLA use case with O-DU-HIGH using L1 and netconf CLI.
Blockers:
1- L1 is crashing very quickly
2- Multiple Slot indication
3- No Config response for cell bring up
Expected Solution: During the D release maintenance phase new intel L1 binary with fixes expected.
View file | ||||
---|---|---|---|---|
|
CLA use case demo with PHY-STUB and SMO
This video contains demo of CLA use case with O-DU-HIGH using PHY-STUB and SMO.
View file | ||||
---|---|---|---|---|
|