Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Operation and Maintenance (OAM)

Primary Goals:

According to the O-RAN-SC-OAM-Architecture document, all ManagedElements (near-real-time-RIC, O-CU-CP, O-CU-UP, O-DU and O-RU) implement the O1-interface.

F Feature Scope / Achievements:: 

  • Providing and an abstract topology for rApp and CNF deployment
    • Interfaces: A1, E1, E2, F1, N1, N2, N3, O1, O2, OFH-CUSM
    • Components:
      • SMO = Non-RT-RIC, O1-Controller, VES-Collector, File-Client, O2-Controller;
      • 5G Core = UPF, AMF
      • RAN = Near-RT-RIC, O-CU-UP, O-CU-CP, O-DU, O-RU
      • User Equipment
  • Topology Generator, Topology Reader
  • Enhancing automated test cases validating the end-to-end message flows related to OAM interfaces (O1, OpenFronthaul M-Plane)
    • Adding Wireshark for traffic flow analysis

F release source code, container images and deployment instructions (and status)

Jira: Count of Epics ( 15 issues ), User Stories, Tasks, and Issues:  166 issues

Source Code:

Integration:

Release notes:

Code coverage: 

...

Simulators (SIM)

Primary Goals:

  • Keep alignment with latest O-RAN specifications (O1, E2)

F Feature Scope / Achievements:

  • Provide topology-service image
  • Implement Preparations for code-coverage testsfor the C/C++ code

Jira: Count of Epics, User Stories, Tasks, and Issues:  5 issues

Status:

  • topology-service docker image available
  • alignment with latest O-RAN specifications for O1 and E2 is done
  • code-coverage in progress - will spill to G release because code modifications are needed for Sonar integration

F release source code, container images and deployment instructions

Source code: https://gerrit.o-ran-sc.org/r/gitweb?p=sim%2Fo1-interface.git;a=shortlog;h=refs%2Fheads%2Fe-release TODO

Container images are described here: TODO

Instructions: Network Slicing Use Case TODO update

Code coverage: in progress (sonar for C/C++ code in LF repos)

...