ONAP TSC is setting up ONAP strategies and roadmaps for ONAP future focus areas and releases
- Lightweight ONAP Core with function aggregation capabilities
- Component interface normalization and/or standardization
Evaluate innovative solutions and technologies to ensure that ONAP remains the best fit
- Secure CI/CD, Repository-based, Declarative intents
- AI/ML-based network provisioning configuration, optimization…
Collaborate with other communities and standard organizations for complete and secure network automation solutions
- O-RAN, O-RAN SC, Nephio, 5G Super Blueprint
- 3GPP, TMForum, ETSI, IETF, others

ONAP Focus Areas

Manage “Right-size & Focused” functions, which can be used by operators/vendors, and industry

Continuation of ONAP Streamlining evolutions
Removal of unmaintained ONAP components
Removal of any dependencies of unmaintained ONAP components
Component interface normalization / standardization for functional aggregations, based on use cases
Component catalogs / documentation to guide functional aggregations on demand

Seek collaborations with other open-source projects, especially O-RAN, O-RAN SC and Nephio

Use cases, interface models and specifications for interacting with O-RAN SC and Nephio
For core components such as DCAE, Policy Framework, CPS, SDN-C/R, UUI, AI/ML Intent-driven network automation, SO and A1 Adapter. Update them with normalized interfaces, possibly AI-based intents
Enhancements of streamlining OOM scripts for security and CD-based individual component deployment
Becoming an integral part of initiatives such as the O-RAN SC, Nephio and 5G Super Blueprint

ONAP Core Components

The following diagram depicts Oslo ONAP Component Architecture:

Image Added

The remaining ONAP components/projects are now ONAP Core components:

SDC