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
Please checkout the calendars:
Anti-Trust Notice
Date
Attendees
- John Keeney (Ericsson EST & OSC NONRTRIC)
- Martin Skorupski (Highstreet & OSC OAM)
- Alex Stancu (Highstreet & OSC SIM)
- James Li (CMTI & OSC INT)
- N.K. Shankaranarayanan (ONAP TSC)
- Halil Cakal (Ericsson EST)
- Aravindhan Ayyanathan (Ericsson EST)
- Kevin Timoney (Ericsson EST)
- Sonia Sangari (Ericsson EST)
- Carsten Höseler(TU-Dortmund)
- 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 2023-01-25 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)
Contents
Recording
Notes:
Housekeeping:
Happy Chinese New year!
Calendar:
09:00 PST | 12:00 EST | 17:00 UTC | 17:00 GMT | 18:00 CET | 22:30 IST | 01:00 (+1d) CST
OSC SMO project calls now move to its own time slot - alternate Thursdays
See OSC RSAC Calendar: https://wiki.o-ran-sc.org/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 also OSC AIML Project meeting notes
OSC Project roundup:
News from OSC TOC call last week
- https://wiki.o-ran-sc.org/display/TOC#ORANSCTechnicalOversightCommittee(TOC)
- Last week's TOC (Thursday):
- Insights Dashboard - LF Analytics:
- https://openprofile.dev
- Check your Email addresses are linked to the account
- "Add Affiliation" for each project
- Affiliation panel may be hidden behind a blue LinkedIn panel - Dismiss it.
- If you work on more than one project, then affiliation must be added for each project.
- https://openprofile.dev
- Insights Dashboard - LF Analytics:
- This week's TOC (Tomorrow):
- No update.
- Last week's TOC (Thursday):
NONRTRIC (John Keeney)
- As per last week. Development for each of the topics below continue ...
- Release H Planning continues:
(R1) Service Exposure & Management
- CAPIF Aligned Service Registry
- Secured/Sandbox execution environment
- Controlled access & exposure of service to/from rApps
(R1) Data Management & Exposure
- Previous focus on PM data - but will extend to other use cases too
- Aim to work with AIML project for Training (and Inference ?) data access
rApp Management
- Built on ONAP “Automation Composition” model & platform to implement rApp use cases
- rApp-specific extensions needed
- Packaging, Onboarding & Orchestration of rApps
- rApp-specific packaging & Onboarding
- Aim to align with / inform ongoing work in O-RAN (& OSC) about Common App packaging & Onboarding.
- (rApps with & without µService)
- rApp-specific packaging & Onboarding
- Overlap with Service Exposure work to examine role of an rApp Manager to support controlled exposure & LCM of µService and non-µService parts of an rApp
- Built on ONAP “Automation Composition” model & platform to implement rApp use cases
Continued A1-Policy & A1-Enrichment-Information evolution (& R1-A1)
- A1 Spec evolution
- A1-Policy work in ONAP (continues in ONAP London) - candidate for R1-A1(P)
- A1-EI management as part of DME - candidate for how to include A1-EI in R1-DME
- Sample use cases (rApps)
- Requirements Drivers for rApp/R1 development
- High degree of cross-project integration activity
Testing, Maintenance & Housekeeping
- Function Test & Integration Test environment,
- Support integration, deployment & configuration of SMO/Non-RT-RIC related functions & usecases in OSC Integration env.
- Project coordination, Documentation, Delivery, Reporting, Cross-project alignment, Community demos, O-RAN Standardization support, etc.
- Release H Planning continues:
SIM (Alex Stancu)
- Looking at how to collaborate with OAI
- Ref RSAC below.
OAM (Martin Skorupski)
- Looking at OAM Specs from O-RAN Alliance & 3GPP REL 18
- Working on updating stndDefined VES messages with 3GPP REL-18
O-DU (Hariom Gupta Vidhu Shekhar Pandey)
No Update
OSC Integration / INT (James Li )
- X-Testing with other OSC projects
- e.g. Windriver would like to contribute for O2-IMS
- Request from last week's TOC to define an OSC SMO 'package'
- e.g should include cloud orchestration & DMS etc.
- (Aside Discussion ... will be interesting to see relation with Nephio ... )
- e.g should include cloud orchestration & DMS etc.
RSAC/SMO (David Kinsey)
Ref: RSAC Meetings
- Discussion about collaboration between OAI & OSC
- Focus on Integration Collaboration
- ORAN-SC DU inter-working with OAI CU?
- Focus on Integration Collaboration
- Some mention of the need to make progress creating consolidated SMO - based on SMO Disaggregation work
- N.K. Shankaranarayanan ... Discussion about just how "pre-spec" we in opensource can/should be ....
- Maybe at RSAC in 2 weeks we could have some discussion about ONAP REQ subcom & O-RAN related usecases/requirements in ONAP etc?
AI/ML platform project ()
Minutes & Meeting: Meeting notes
No update this week
ONAP / OSC / O-RAN Alliance: Cooperation & Alignment
- N.K. Shankaranarayanan: Follow on from previous weeks: Lots of discussion at ONAP TSC
- No convergence yet, but lots of interest. Ref TSC Minutes: https://wiki.onap.org/display/Meetings/2023+TSC+MEETING+MINUTES
- Will aim for cross-discussions at RSAC / ONAP-ReqSubCom level.
- No convergence yet, but lots of interest. Ref TSC Minutes: https://wiki.onap.org/display/Meetings/2023+TSC+MEETING+MINUTES
ONAP Use cases (N.K. Shankaranarayanan)
- Long discussion this week!
(Recording 00:44:30)
Work progressing on CM VES Messages → ONAP CPS DB.- 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
- https://jira.onap.org/browse/INT-2180 && https://jira.onap.org/browse/INT-2181
- (Somewhat related ... For PM ... a XPath link back to the where reporting entities are defined in Yang Model: Network Slicing Use Case#PMJobcreation)
- O1 CM Notification will (should?) use 3GPP spec for CM notification
- How to find which Object is changed?
- 3GPP TS 28.532 specifies that CM Notifications (e.g. notifyMOIChange) contains fields objectClass and objectInstance
- https://www.3gpp.org/ftp/Specs/archive/28_series/28.532/28532-h30.zip (very recent version of v17 spec)
- Contains word doc spec
- Contains provMnS.yaml
- https://www.3gpp.org/ftp/Specs/archive/28_series/28.532/28532-h30.zip (very recent version of v17 spec)
- Cannot find objectClass and objectInstance in the openAPI spec for notifyMOIChanges in "provMnS.yaml"
- It is in 28.532 sect 11.1.1.11 of Spec document, but not in provMnS.yaml (links to ComDefs.yaml)
- https://www.etsi.org/deliver/etsi_ts/128600_128699/128623/17.02.02_60/ (very recent version of v17 spec)
- TS28623_ComDefs.yaml#/components/schemas/NotificationHeader does not have objectClass and objectInstance
- But it does have an 'extra' field called href (a URI) ???
- Perhaps this should contain the objectClass and objectInstance ... Can these be extracted?
- It is in 28.532 sect 11.1.1.11 of Spec document, but not in provMnS.yaml (links to ComDefs.yaml)
- Continued Discussion
- We spent some time walking through 3GPP specs to verify this for a few different versions. ..... Same result
- 3GPP TS 28.532 specifies that CM Notifications (e.g. notifyMOIChange) contains fields objectClass and objectInstance
Questions / Comments / AOB:
- Went over time this week - No update.
Meeting ends