Time & Location:

New Meeting Slot

We have now moved to new meeting slot Wednesdays at 16:00 UTC in Summer (DST), 17:00 UTC in Winter !


Please note our new Zoom Bridge

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

Meeting ID: 890 6970 8424



NOTE: During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of the meetings may fluctuate. See the Calendar: (https://lists.o-ran-sc.org/g/main/calendar) 

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)

  • Meeting ID: 890 6970 8424
  • 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:

  • Reminder from last week:
    • OSC SMO calls now move to its own time slot - Thursdays
      See OSC RSAC Calendar: https://wiki.o-ran-sc.org/display/RSAC/calendars
      (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.

OSC Project roundup:

NONRTRIC (John Keeney)

  • No major update.
    • Still wrapping up A1 Policy contributions in ONAP Honolulu as M3 approaches - of course integration, documentation, testing etc will continue.
    • Still training & initial prototyping around rApp execution platform.
    • Checking dependencies, updating versions etc.

SIM (Alex Stancu)

  • Alex Stancu NS3 5G RAN simulator ....
    • Joined weekly meeting
    • 5G RAN Simualtor - focussing on E2
    • Currently internal project funded by Mavenir. Will open source later.
    • No plan for A1 or O1
  • OTF looking at integrating E2 simulator

OAM (Martin Skorupski)

  •  Still discussing topology in ONAP: Abstract Topology Model
  • For O-RU use case O-DU netconf client configuration for connecting to O-RUs (e.g. call home etc)
    • Implementing in C but has similar to functionality provided by ODL
    • Thinking of reusing early  usecase-specific yang models:  Use case driven YANG modules for O-DU
      • Investigating how/if these need to be cleaned - might be suitable for use  as pre-spec models?
  • Continuing ONAP M4 activities & ONAP H requirements planning

ONAP - OSC:

Other

  • Hieu Nguyen: Question:
    • "Hello, I am currently investigating HTTP/HTTPS Proxy to support for A1 Southbound communications, and would like to understand about the benefit to having such HTTP/HTTPS Proxy. So, could you please pointing out some benefits (or even business benefits) to having HTTP/HTTPS Proxy support within "A1 Adapter & A1 Policy Management Service". Thank you!"
    • From Last Week: 
      • Hieu Nguyen: What is the HTTP/S proxy support in ONAP A1 Policy Management Service and A1 Adapter?
        • John Keeney Some operators maintain a proxy between their RAN domain & OAM layer. It is not common (prior to A1) to have a REST interface between RAN & OAM - so this requirement in CCSDK is only now becoming apparent.
        • user-4594e Sees this requirement in operator networks, e.g. connecting through Bastion.
        • John Keeney HTTP/S Proxy support is added to A1 Policy Management Service (specifically for A1 connection only) - Configurable via configuration files. See documentation for details.
        • John Keeney HTTP/S Proxy support is not yet added to A1 Adapter, since it uses the CCSDK SLI node function to perform REST calls southbound. This function needs to be extended in CCSDK (or a new one added). This changes, and associated regression testing will be quite tricky.
        • John Keeney Operators often keep RAN domain and OSS domains separated (security, traffic separation, etc) - so often a proxy is needed between the domains.
        • John Keeney In ONAP - Currently implemented for A1 Policy Management Service only. Not implemented for ONAP A1 Adapter: 
          • CCSDK-3153 (HTTPS Proxy support for A1 adapter southbound - A1 Honolulu )
        • Hieu Nguyen: Why not just use secure cert & TLS rather than proxy John Keeney Both are orthogonal can have either with/without each other.
        • Hieu Nguyen: Performance issues? John Keeney In any commercial env would need a performant proxy. Lots of high performing proxies available.
    • Pawel Slowikowski Proxy for A1 Adapter John Keeney Will add more details to JIRA ticket: CCSDK-3153 (HTTPS Proxy support for A1 adapter southbound - A1 Honolulu )
      • Hieu Nguyen: Proxy config is in A1 PMS - How would A1 adapter be configured? John Keeney Few options ... still investigating. Configuration, documentation, testing is probably hardest part beyond implementation.


  • Pawel Slowikowski Why have A1 Adapter at all? Will A1 adapter be supported ongoing?Will we continue with direct connection from A1 PMS
    • We have no plans to deprecate with option yet.
    • Ref discussion with Lasse Kaihlavirta last week :
      • Currently A1 adapter is a straight-thu connector.
        • Reasons to use A1 Adapter
          • Co-locate A1 terminate with O1 CM/Netconf connections in same controller instance.
          • Good Interception/integration point to add implement specific load-balancing or security functions etc.
          • Good Interception/integration point to do O1/A1 coordination - e.g. no A1 if function is in locked administrative state. SLI can be used for this check.
    • Pawel Slowikowski Why have A1 PMS direct:
      • John Keeney Started as a demo. Also has requests for other user that so not want to use ODL-based controller especially since controller/adapter part is mostly pass-thru anyway. So we support both.  



  • HariomGupta(HCL) O-RU Closed loop use case - O-DU startup part.
    • Ref: 3. ODU Startup 
    • How to do DHCP functionality for O-DU (Deferred from Release D - so how will we do it)
    • Martin Skorupski Needs to be done manually - so start - so use case would likely start after DHCP step.
    • HariomGupta(HCL) Still trying to figure out how to do VES from O-DU. Continue to work with Alex Stancu
    • Is step 12 - TLS or SSH? Cert is needed. Where does this cert come from? Felix in INT is providing support for cert management / root cert. A new cert will be needed. Then TLS can be used.
    • Step 13-14 Martin Skorupski Working on sample models. - See above.
      • Which Netconf server? HariomGupta(HCL) Netopeer.
      • Still ALOT of work to do on the model ... but should minimize it as much as possible for this use case.
    • Line 25 Subscription. Martin Skorupski Not needed. Subscription is already live.
    • WIll discuss more at RSAC call