2023-02-08 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting) - Agenda

Next meetings: 

first ideas are formulated for ONAP Req ↔ O-RAN-SC RSAC communications

• background
  • plan - more synergy between the projects
  • start on requirements work

Fruitful discussion in today's O-RAN-SC RASC meeting

• Minutes: https://wiki.o-ran-sc.org/display/RSAC/RSAC+Meetings (will come soon, if not available yet)
• Action Items defined
  • identifying overlapping areas and new areas
  • identifying subsystems in interfaces between components 

• Topics: Draft from N.K. Shankaranarayanan 
  
  • 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 alot 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

  • 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 be align to leverage past work?

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

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

    • (**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

    • 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 case -> WG1, OSC

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

    • Scope for sharing work and aligning objectives

  • Architecture  -> WG1

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

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

Presentation for such interworking

• https://wiki.o-ran-sc.org/download/attachments/57377183/Integration_plan_v1.pptx?version=1&modificationDate=1675778705403&api=v2

• data formats
  • PM vs list of key/value pairs
  • Who (which component) is mapping/translating the data into the preferred training format?
• Training component within Non-RT-RIC or outside (discussion)

• both use cases are addressed
• SON: R12 5G SON Use Case
  • https://forge.3gpp.org/rep/sa5/MnS/-/blob/Rel-18/OpenAPI/TS28532_ProvMnS.yaml
  • AI Martin: VES to YANG → identifiers in VES to identifiers in YANG 
    INT-2180 - Getting issue details... STATUS
    https://wiki.o-ran-sc.org/display/SIM/Network+Slicing+Use+Case#NetworkSlicingUseCase-PMJobcreation
    
    
• Interesting links about CPS etc: 
  https://wiki.onap.org/display/DW/Configuration+Persistence+Service+Developer%27s+Landing+Page
  https://wiki.onap.org/display/DW/CPS-1434%3A+VES+Message+to+update+CPS+DB

2023-02-01:

• see discussion on CM VES messages
• VES goes directly to CPS - please see: 
  • CPS-1407 - Getting issue details... STATUS  
  • CPS-1434: VES Message to update CPS DB