Time & Location:

Meeting Detail: Times & Joining Info

Wednesdays at 16:00 UTC in Summer (DST), 17:00 UTC in Winter !

Zoom Bridge :  https://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09

  • Ensure you are signed into your Zoom account to join.
  • Meeting ID: 890 6970 8424.
  • See the Calendar: (https://lists.o-ran-sc.org/g/main/calendar)
  • NOTE: During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of the meetings may fluctuate. 
    • Summer Daylight Savings time eventually stabilizes to: 9am PDT | 12pm EDT | 16:00 UTC | 17:00 BST | 18:00 CEST | 19:00 EEST | 21:30 IST | 00:00 CST (Thurs) | 01:00 JST (Thurs)
    • Winter (non-DST) time eventually stabilizes to: 9am PST | 12pm EST | 17:00 UTC | 17:00 GMT | 18:00 CET | 19:00 EET | 22:30 IST | 01:00 CST (Thurs) | 02:00 JST (Thurs)
    • (During Winter→Summer DST changeover follow US time. Summer→Winter DST changeover follow Europe time
  • Meeting ID: 890 6970 8424
  • You will need a Participant ID so you will need to join the meeting from a Zoom client first to get this.
  • Dial in: (Local numbers)
    • +1 646 558 8656 US (New York)
    • +49 30 5679 5800 Germany
    • +49 69 3807 9883 Germany
    • +353 1 240 8941 Ireland
    • +46 8 4468 2488 Sweden
    • +46 8 5016 3827 Sweden
    • +358 3 4109 2129 Finland
    • +358 9 7252 2471 Finland

Date

Attendees

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

Contents


Recording

Notes:

Housekeeping:

OSC SMO Meeting Series: Reminder from previous weeks:

Vacation plans in coming weeks:

  • John Keeney will be unavailable for call on 11Aug ... Will discuss next week if this/other calls should be cancelled, depending on availability of key attendees.

OSC Project roundup:

NONRTRIC (John Keeney)

  • Little new to report since last week as team members on vacation
  • A1 Policy Functions in ONAP - Istanbul M3 approaching
    • Work continues on A1 Adapter & A1 Policy Management Service extensions.
  • Continue Release E planning
    • Looking at how to deploy & LCM Apps in OSC E
      • Based on work in ONAP: https://wiki.onap.org/display/DW/TOSCA+Defined+Control+Loops%3A+Architecture+and+Design
        • While this is based on older work on ONAP Control Loops/Clamp - it is basically a full re-architect & build.
      • Still at a very early stage, not yet ready to present / demo ... Hope to demo/present at upcoming RSAC meetings a few weeks.
      • Current prototyping going very well - using the OSC D "Link Monitor" Apps as requirements drivers & "pipe cleaner".

SIM (Alex Stancu)

  • Martin Skorupski : Alex is working on an issue with ODL & Netopeer on RestConf-Netconf translation.

OAM (Martin Skorupski)

  • Release planning & examining use case proposals

O-DU (HariomGupta(HCL))

  • E-Release Planning
    • Discussing with O-DU-High&O-DU-low team for O1 config parameters - based on 3GPP parameters.

News from OSC TOC call this week

OSC Release E usecases:

ONAP SMO deployment options

  • @Martial: No major update on the deployment work:
    • Need to wrap up initial PoC for ONAP Istanbul, but not tied by ONAP M3 date
  • @Martial Next step will look at CNF deployment

  • CNF Deployment / Combined PoCs:

    • Pawel Slowikowski Good overlap with Samsung Demo for last year - deploying a simulator CNF
    • John Keeney Can we also combine with ongoing PoC work on rApps / Control Loops in ONAP?
    • Lets discuss if we can pull 3 PoC workstreams together

Q&A:

PM Collection / VES PMMapper

  • @33:30 in recording
  • Pawel Slowikowski Krystian Kedron @Stanislav
    • Struggling with PM Mapper for O1 PM-Bulk measurements - can only use bulk collection (ves:fileReady & File collection), but PMMapper translate to VES events does not seem to work very well ...
    • Potential to improve how PMMapper → VES event translation
    • @Stanislav presented slides:
    • Difficulty identifying temporal granularity of the individual events
      • Semantic of the Granularity period is misleading? wrong?
      • Martin Skorupski Is the start/end times in header? This would define the granularity?
      • Granularity should be inside the message? - Would have a knock on effect in spec/standardization.
      • Likely that new approach to use stndDefined schemas for 3gpp events might work around this?
      • Martin Skorupski will reach out to some interested parties.
    • Issues mapping meastype with measvalue
    • Version, VESVersion, Priority, Domain seems to be hardcoded in VES PMMapper. SourceID is missing.
      • may be a broader with VES Collector in general
    • Martin Skorupski Should start by creating tickets in JIRA - VES Collector & PMMapper

SON Usecase: