Versions Compared

Old Version 39

changes.mady.by.user Mahesh Jethanandani

Saved on

compared with

New Version Current

changes.mady.by.user subhash kumar singh

Saved on

Key

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


Project KeyProject NamePTLDescription
RICAPPRIC Applications
Matti HiltunenInitial
SUNIL SINGHThis includes open source sample xAPPs and platform applications that can we used for integration, testing, and demonstrations.
RIC

Near Realtime RAN Intelligent Controller

Thoralf Czichy

Abdul Wahid W 
RIC Platform to support xAPPs with limited support for O1, A1, and E2 interfaces.
OCUO-RAN Central Unit
user-a934b 
TBD

The OCU should target an initial software deliverable with limited functionality. Focus on aa basic E2 interface to enable initial integration testing between RIC and OCU.

ODUHIGH

O-RAN Distributed Unit High Layers 

Sachin Srivastava

Ankit Barve 

Focus on initial L2 functional blocks based on seed code contributions.
ODULOWO-RAN Distributed Unit Low Layers
Zhimin Yuan
peng Lu Focus on initial L1 functional blocks based on seed code contributions.
ORUO-RAN Radio UnitTBDOut of scope for release "A".
OAMOperations and Maintenance

Martin Skorupski

O1-related sysdev; initial dashboard for monitoring and demonstration of contributions. More ...
SIMSimulationsAlex StancuInitial simulators used for testing O-RAN NF interfaces.
INFInfrastructure
Xiaohua Zhang

Jackie Huang

Initial building blocks for infrastructure to run O-RAN NF components.
INTIntegration and Testing
user-d3360 

James Li

The integration and test effort will focus on testing the requirements documented in each release. This will focus on end to end test and use case testing.

NF Testing shall primarily be done on the Akraino-REC (Radio Edge Cloud) blueprint. While Non-RT RIC and O1 interface testing will primarily use ONAP components

In addition, it's a ultimate goal to establish a full end-to-end call flow using OSC components to carry out end-to-end integration tests and/or plug-and-play interoperability tests; but before that will try to perform pairwise tests based on release use cases as much as possible. Another target is to establish a CI/CD/CT pipeline to improve code stablity/quality and adopt modern Dev/Ops methodology.

DOC

Documentationweichen niDocumentation on contributions and O-RAN SC contents.
NONRTRICNon-RealTime RIC (RAN Intelligent Controller)

John Keeney

Non-

realtime

Realtime RIC focus on feature functionality of A1-interface

(consumer and provider), and closed-loop use cases. The NONRTRIC project will also work together with the OAM project to align activities on a case-by-case based for O1 interfaces. Project should focus on use cases supported in ONAP. The work should be sponsored in O-RAN and initial code contributions in O-RAN SC. Interoperability with ONAP should be aligned between the standards and will follow initial contributions in this project.

, R1 interface, and support rApp (applications). More ...

SMOService Management and Orchestration (SMO)
Mahesh Jethanandani

Seshu Kumar Mudiganti 

The primary goal of the SMO project is to integrate different software artifacts of existing open-source projects creating a fully functional open-source Service Management and Orchestration (SMO). 
AIMLFWAI/ML Frameworksubhash kumar singh Initial AI/ML workflow implementation for O-RAN environment. Need to interact with another project to accomplish a whole life cycle management of the AI model.


NOTE: Repositories that are indicated as scp/ repositories are repositories maintained by the O-RAN Alliance and licensed under the O-RAN Specification Code Project under licenses that are different from the licensing of the O-RAN Software Community Project. For questions concerning an O-RAN Specification Code Project code or documentation, please contact the O-RAN Alliance.