2021-10-20 Meeting notes - Joint OAM / NONRTRIC / SIM SCRUM meeting
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
2021-10-27:
16:00 UTC, 09:00 PDT, 12:00 EDT, 17:00 BST, 18:00 CEST, 19:00 EEST, 21:30 IST, 00:00 CST (Thurs), 01:00 JST (Thurs)
2021-11-03:
16:00 UTC, 09:00 PDT, 12:00 EDT, 16:00 GMT, 17:00 CET, 18:00 EET, 21:30 IST, 00:00 CST (Thurs), 01:00 JST (Thurs)
Note: 1 hour earlier in Europe - Just this week
2021-11-10:
17:00 UTC, 09:00 PST, 12:00 EST, 17:00 GMT, 18:00 CET, 19:00 EET, 22:30 IST, 01:00 CST (Thurs), 02:00 JST (Thurs)
Note: 1 hour later in Asia, revert to normal time in Europe.
2021-11-17:
17:00 UTC, 09:00 PST, 12:00 EST, 17:00 GMT, 18:00 CET, 19:00 EET, 22:30 IST, 01:00 CST (Thurs), 02:00 JST (Thurs)
Note: Continues like this until mid March 2022.
Please checkout the calendars:
Date
Oct 20, 2021
Attendees
@John Keeney (Ericsson EST)
@Martin Skorupski
@Alex Stancu
Arnold Alvarado (NIWC)
@Chris Dent
Christophe Closset (AT&T)
@David Johnson
@Dibas Das
Dilip Krishnaswamy (STL)
Doug Evans (USN)
@Hariom Gupta
@Jakub Dominik
@Kevin Tang
Martial Ngueko (AT&T)
@michal.cmarada@gmail.com
@N.K. Shankaranarayanan
Ryan McAllister
Sebastien Determe (AT&T)
@Sonia Sangari
@Tracy Van Brakle
@Vidhu (Deactivated)
@Vishal Varvate
May not have captured a full attendee list for this meeting ... please add/remove yourself
See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)
Co-located with ONAP 2021-10-20 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)
Contents
Recording
Notes:
Housekeeping:
OSC SMO Meeting Series: Reminder from previous weeks:
OSC SMO calls now move to its own time slot - Thursdays
See OSC RSAC Calendar: https://lf-o-ran-sc.atlassian.net/wiki/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.
NOTE: DST Changeover in coming weeks!
See above & Keep a close eye on the calendars!
OSC Project roundup:
News from OSC TOC call this week
We all remain somewhat confused about copyright..... will update when we know more
Integration project PTL election completed: James from CMCC elected!
NONRTRIC (@John Keeney (Ericsson EST))
Working mainly on Helm chart updates ... see also below
SIM (@Alex Stancu)
Topology service available!
TAPI topology simulator. (See below)
Image: nexus3.o-ran-sc.org:10004/o-ran-sc/smo-nts-ng-topology-server:1.3.6
OAM (@Martin Skorupski)
Working on helm charts.
Struggling with licensing issues. (See below)
O-DU (@Hariom Gupta )
@Hariom GuptaStill figuring out if 3GPP Yang model can be used / implemented.
Topology Models:
No model suits everyone
TAPI model is quite abstract / domain independent - basically functions & endpoints ( edge-point, interface, logical termination point, connection points etc)
Simulator/Usecases considers CUs, DUs, RUs, & their location
Topology model loaded/configured at start time (JSON/XML). Made available using TAPI Netconf model. (Netconf server)
@All - Discussion:
Cell/Neighbour-Relation? Not explicitly modeled ... but would it be a function, connection, logical grouping, parameter?
All valid for different usecases! Everyone has their own topology model for their own use case!
TAPI is very abstract, so a good starting point for more specific topology models.
Discussion continue in ONAP modelling work.
Is ANR (Automated Neighbor Relations) supported in O-RAN?
Not O-RAN specific ... feature/usecase that can be implemented in various ways in 4g, 5g, etc ... Centralized, Distributed, Hybrid, in xApp, etc....
ONAP SMO deployment options
Sebastien: Pull Request on OSC it/dep repo for existing SMO Deployment package - will overwrite existing version
It very big though so will take some time.
@John Keeney (Ericsson EST) & Sebastien should talk offline about changes from original, and proposed changes to NONRTRIC helm charts (also in progress)
Should also now include new INT PTL
@David Johnson Mini deployment in POWDER lab seems to be working well! Will also look at SMO Deployment here & feedback.
Sebastien: Also working on OOM changed (DCAE/VES Collector config for SDNC)
Sebastien: Also has an issue with O-RU-use case App ... issue with HTTPS .... Python issue?
Copyright & Licensing
SCCL:
Recent "Special TOC Call" about licensing, but was not SCCL recorded
SCCL does not address 3GPP license issue - Issue continues as before
O-RAN Alliance will try persuade 3GPP to use SCCL ... but progress stalled.
SCCL is currently only for O-RAN Alliance material - to be agreed to by anyone using/redistributing these specs
OSC is a first mover to put procedures in place
SCCL is copyright only - IPR licensing is a seperate issue and not addressed
SCCL is not an open-source license
We are making some progress understanding SCCL (but we're not there yet!)
Can SCCL specs be redistributed freely?: No.
3GPP:
Surely there is potential to request a PoC/Demos/non-Commercial derogation from 3GPP
We need to keep pushing.
@Tracy Van Brakle IIRC 3GPP does allow use for demos/poc/exhibitions ? Will check up on this! This should be enough for our requirements.
Simulators
@N.K. Shankaranarayanan The RANSIM work in ONAP is making good progress! (Ref Krishna in SON, Slicing & OOF in ONAP)
@Tracy Van Brakle @N.K. Shankaranarayanan Should all these simulators be consolidated?
They could be more aligned, but probably should not be "merged" - they have different priorities / simplifications embedded - by design!
But they do have some shared/shareable functions/requirements, so some alignment might be helpful.
@Tracy Van Brakle Is there something like Mininet for O-RAN/3GPP/RAN? Maybe academic contributors would be best suited to help here
Q&A
Ran out of time