Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 3 Next »

Table of Contents

Scope

The ONAP TSC has an objective of promoting collaboration between ONAP and O-RAN Software Community (OSC). The plan was to start with a discussion with the O-RAN SC RSAC team to share ideas and thoughts about plans for future work, with a view of improving harmonization of efforts and reducing duplication of work. In this page, we have a list of common areas where ONAP and OSC interests have overlap.

Areas

  • O1-/OFHM-related OAM, IM/DM Models→ WG10 (O1, OAM), WG4 (OFHM), WG5 ?
    • Good amount of existing work and harmonization effort (e.g., yang models, VES msgs)
    • Very strong alignment between OSC & ONAP (avoid duplication - single codebase)
      • Would be helpful to make release timelines etc better aligned.

  • Non-RT-RIC A1-related:  → WG2

    • Good amount of existing work and harmonization effort (e.g. A1 interface, modification of ONAP RAN-Sim to support A1)

    • Continue effort to re-use code and principles

  • Non-RT-RIC rApp:  → WG2 (WG10, app management)

    • Good amount of work in OSC - reusing a lot from ONAP

    • (**New area) - Ongoing effort to seek out ways to align with ONAP control loops and use cases (originally designed without knowledge of R1)

    • e.g. Already reusing ONAP functions as part of  rApp management/LCM

  • SMO Policy Functions:

    • (** New area) - ONAP has had a Policy Enforcement Function since beginning, and there is no obvious mapping to existing SMO architecture

    • e.g. inter-rApp coordination ??
    • rApps using Policy Functions - as rApp might use any other SMO service, or rApp might contains Policies (ref work in ONAP ACM / App manager)

  • O2 related, cloud management → WG6

    • ONAP has a lot of work on NF orchestration and management - looking at O2 support

    • (**New area) - Relatively less focus on cloud infrastructure management (role for other LFN projects? - e.g. Nephio?)

    • (**New area) - integration of use cases which cover both IMS and DMS part of O2 (FOCOM, NFO)

  • Orchestration (end-to-end aspects, including components inside SMO) -

    • (**New area) - ONAP has lot of work on Service Design and Orchestration. May be worthwhile for OSC to align and leverage past work?

  • AI/ML related (Training, ...) → WG2

    • (**New area) - ONAP AI/ML work was generic. Did not assume role of Non-RT and Near-RT RIC. .

    • (**New area) - ONAP did not consider controlled data access / exposure.

  • Security → WG11

    • Good amount of shared objectives - security of interfaces design, system implementation, code design etc

    • Can share best practices etc

  • Simulation work -> OSC

    • Ongoing effort to leverage/harmonize work in both groups

    • OSC sim work oriented towards OAM (CU/DU/O1), ONAP Sim work oriented towards use case (RAN-Sim)

    • Reusing OSC simulators in ONAP usecases (e.g. RANSim, A1 Policy functions)

    • ONAP RAN-Sim adaptation - A1 termination, abstraction of near-rt-ric and xapp, exploring porting

  • End-to-end use cases -> WG1, OSC

    • End-to-end slicing, SON, Intent-based networking, OAM, life-cycle management

    • Scope for sharing work and aligning objectives

  • SMO Architecture  -> WG1

    • (**New area) - Identification of building block sub-systems - esp. related to SMO. (SMOS/SMOF concept from WG1 Decoupled SMO TR?)

    • Target to have only small list of recommended approaches, harmonization/code re-use within same approach

  • No labels