2024-08-20 Meeting notes - Joint OAM / NONRTRIC / SIM Community meeting

Time & Location:

• Time Change: This meeting is now 1 hour later - 15:00 UTC on Tuesdays

Anti-Trust Notice

• Antitrust Policy Notice

• Antitrust Policy

Date

Aug 20, 2024

Attendees

• @John Keeney (Ericsson EST) (Ericsson EST & OSC NONRTRIC)

• @Martin Skorupski (Highstreet & OSC OAM)

• Subhash Kumar Singh (@subhash) (Samsung & OSC AIMLFW)

• @Aravindhan Ayyanathan (Ericsson EST)

• @Francesco Davide Lapenta (Ericsson EST)

• @Denis G Noonan (Ericsson Software Technology) (Ericsson EST)

• @Simeon Wuthier (NIST)

• @Varadarajan (Samsung)

• @Deena Mukundan (Tech Mahindra)

• Srinivas Yanamadala (Tech Mahindra)

• May not have captured a full correct attendee list for this meeting  ... please add/remove yourself

See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)

• Co-located with ONAP 2024-08-20 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)  (link unlikely to work after ONAP's Atlassian switchover)

Contents

Recording

Notes:

Housekeeping:

• Calendar: 

  • https://lists.o-ran-sc.org/g/main/calendar

  • https://lists.onap.org/g/onap-meetings/calendar

• Time Change:

  • This meeting is now 1 hour later - 15:00 UTC

• OSC SMO project calls now move to its own time slot - alternate Thursdays

  • See OSC RSAC Calendar: https://lf-o-ran-sc.atlassian.net/wiki/display/RSAC/calendars

  • See also OSC Meetings calendar: https://lists.o-ran-sc.org/g/main/calendar

  • (Note this meeting to open to anyone, including non-ORAN members)

  • We will maintain this slot for ONAP Alignment, and try flag issues/question to/from SMO meetings.

  • See OSC SMO Project meeting notes

• See also OSC AIML Project meeting notes

OSC Project roundup:

News from OSC TOC & OSFG calls last week

• TOC:

  • https://lf-o-ran-sc.atlassian.net/wiki/display/TOC/#ORANSCTechnicalOversightCommittee(TOC)

  • Last week's TOC (Thursday):

    • Short meeting this week. No major update.

  • This week's TOC (in 2 days):

    • No major topic planned yet (AFAIK)

• OSFG:

  • Discussions around CVE vulnerability reports & how to process them

NONRTRIC (@John Keeney (Ericsson EST))

• Still working away on issue from previous weeks:

  •  A1-Controller

    • NBI Issues: Last Week WG2 R1 spec for Nov release changes from March version (not backwards-compatible)Still trying to stabilise API for R1.

      • May cause disruption to users that have already adopted the New-Delhi or J-Release versions

    • Fixing a bug in A1-PMS in ONAP & OSC - Where 'transient' Policies were being deleted when a service is deleted.

      • Fix available & preparing tests & patch releases for ONAP (London, Montreal, New-Delhi) & OSC (J at least & hopefully older)

    • Fixing an issue with Service-ID (request param)  vs ClientID (in auth header) when creating an A1 Policy.

    • Updating to SpringBoot 3.3

    • Database-based persistent storage now enabled.

  • Service Manager

    • Hoping to discuss/demo (below) boot-strap service exposures at SMO start-up - but its proving a bit more difficult than expected.

    • Manual registration via API is still working fine - but currently all Services need to be explicitly registered rather than auto-registered.

  • Release K Planning:

    • No major update this week ... but will continue with more focus on demonstrators - esp aiming towards next F2F

• @subhash Hope to get started soon on integrated demo with AIMLFW & NONRTRIC

  • Ready to start moving AIMLFW SME integration & inference-based rApp LCM.

SIM (@Alex Stancu)

• No update this week - @Alex Stancu - away this week.

OAM (@Martin Skorupski)

• Working on wiki updates to update model links etc.

  • Discussion page: O-RAN YANG published in 2024-06 (awaiting WG5 WG10 clarifications)

    • Spotted some issues - See color-coding

• Planning to demo Hybrid & Hierarchical OAM at F2f - including interesting issues like VES message translation.

  • Hybrid and Hierarchical OAM Architecture

AI/ML platform project (@subhash )

• Minutes & Meeting: Meeting notes

• Calendar: https://lists.o-ran-sc.org/g/main/calendar

• Working on integrating AIMLFW & NONRTRIC SME & rApps.

OSC Integration / INT (@fransiscus bimo )

• Minutes: https://lf-o-ran-sc.atlassian.net/wiki/display/IAT/Current+Meetings

• Difficult for @fransiscus bimo to join this meeting, but martin will update if anything interesting pops up

• Working with O-DU team to get OSC O-DU running in Taiwan lab.

SMO (@Seshu Kumar Mudiganti)

• No update this week.

• Meeting notes Meeting notes

• Topology & Inventory: (@John Keeney (Ericsson EST) :

  • From Last week - Still ongoing

    • Working to add new/improved models

    • New improved image generation from TEIV models

    • Working to add support for grouping/collection in registry & api

    • Working to add tagging/classifiers/decorators to help markup & expressive retrieval of data from TEIV

    • Need to start working with others in OSC & beyond to help populate TEIV registry with data from their 'sources of truth'

    • Hope to make alot of use of TEIV in demos/rapps in K-Release

    • Refs:

      • doc: https://docs.o-ran-sc.org/projects/o-ran-sc-smo-teiv/en/latest/data-models-guide.html

      • code: https://gerrit.o-ran-sc.org/r/gitweb?p=smo/teiv.git;a=tree;f=teiv/src/main/resources/models

RSAC (@Rittwik Jana  @Martin Skorupski )

• Minutes: 2024 RSAC Meetings 

• Created L-Release & K-Release planning pages:

  • Release "L"

  • Release "K"

• Will continue working on Demos for O-RAN F2F in Montreal.

  •  Plan & ideas on Release "K" wiki page

ONAP Update (@N.K. Shankaranarayanan)

• No update this week

ONAP/OSC Usecases (@N.K. Shankaranarayanan)

• No update this week.

Demo: Bootstrapping NONRTRIC SME Service Manager with SMO Platform Services (@Denis G Noonan (Ericsson Software Technology))

• (See recording at 0:22:50)

• Demo how to bootstrap SME Service Manager with existing SMO platform service.

  • Services can be described in a yaml file and bulk loaded by a script at SMO deployment startup time

  • https://gerrit.o-ran-sc.org/r/gitweb?p=it/dep.git;a=tree;f=servicemanager-preload

    • Sample yaml files for SMO, NONRTRIC-only and the script to use them.

  • Tricky dealing with Services where URL has a path parameter

    • URI will have regex patterns/capture groups - and returned/registered/queried URI segments need to be post-processed to remove these.

    • Not sure how CAPIF supports path parameters - so this may not be spec-compliant - TBC

      • Note: After meeting: path parameters are given in {} brackets: e.g  http://host:1234/abc/{pathparam1}/def/{pathparam2}/ghij

        • We will update the service manager to return URLs in this format for discovery operations

  • No security enforcement (See AOB below) - that needs to be done separately depending on commercial/field deployment scenarios - e.g. in Service Mesh.

  • Trade-off how detailed a Service/API registration should be

    • e.g. coarse grained, where just the 'root' resource is registered, so likely some operations/paths may fail when invoked  (e.g. not found, operation not supported, unauthorized, invalid requests, etc)

    • e.g. very fine-grained, where all paths are individually registered, and their allowed operations (reasonable expectation invoke will be able to invoke discovered service/resource/operation results)

  • Script can be called any time - e.g. at runtime - with new different config/yaml files

  • REST API is still available for any operation to be performed any time.

    • https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-sme/en/latest/overview.html#service-manager

Questions / Comments / AOB:

• Hello to new joiner: @Simeon Wuthier (NIST) 👋

• @Deena Mukundan

  •    Question about CAPIF & Keycloak integration

    • When Service Manger performs a discovery request, how is it checked which APIs the invoker can access?

      • If invoker is registered - All registered services are returned (depending on filter passed to query) 

      • Currently, our ServiceManager/SME implementation does not perform any authorization or access control check. Basically, all services are discoverable right now. The only requirement is that the invoker is actually registered.

      • However, authentication, authorization and access control is needed in any real deployment. We delegate this to the Service Mesh and API Gateway – to do RBAC at least.
        We show an assortment of options of how to enforce service/data exposure & access on:

        • Release F: Coordinated Service Exposure
          Release G: Coordinated Service Exposure
          extended in:

        • Release H: Coordinated Service Exposure

        ONAP takes a similar approach:

        • https://wiki.onap.org/pages/viewpage.action?pageId=103417456#ONAPNextGenerationSecurity&LoggingArchitecture-ONAPSecurityArchitecture-LeveragingIstio,Keycloak,Cert-Mgr,Ingress,Egress

      • We feel that the OSC SMO deployment is not intended for commercial use or real-world deployments, so we don’t think the OSC deployments needs/should-have this AAA/exposure enforcement enabled.

      • @John Keeney (Ericsson EST) unlikley to work more on this in this release

        • Limited bandwidth

  • Can 3GPP & ORAN stuff be reused commercially - Is there a license issue

    • "IANAL" - Just make sure not to redistribute any 3GPP or O-RAN copyrighted material. Be prepared to FRAND license any IPR from copyright & IPR owners. OSC code however is Apache 2, so reuse should not be difficult.

Meeting ends 70 min