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
Date
Attendees
- John Keeney
- Martin Skorupski
- Alex Stancu
- Andrew Lamb
- Chris Dent (VMWare)
- user-4594e
- Dibas Das
- David Allabaugh
- Fernando (Fred) Oliveira
- Gervais Martial Ngueko
- HariomGupta(HCL)
- Kamel Idir
- Kevin Tang
- Krystian Kedron
- Lathishbabu Ganesan
- Manoj Nair
- Sandeep Shah
- Sebastien Determe (AT&T)
- N.K. Shankaranarayanan
- Sonia Sangari
- Timo Perala
- Vidhu Shekhar Pandey
- 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-08-25 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://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.
- See OSC SMO Project meeting notes
OSC Project roundup:
NONRTRIC (John Keeney)
Skipped
SIM (Alex Stancu)
- Skipped
OAM (Martin Skorupski)
- Skipped
O-DU (HariomGupta(HCL))
- Skipped
News from OSC TOC call this week
PM over VES N.K. Shankaranarayanan
- (01:50-48:00 in recording)
- PM Data from RAN to SMO over O1 - using VES
- O1 is currently focused on file-based PM, with VES used for notifications to coordinate File collection.
- VES already used for FM and CM notifications etc
- Some sample / pre-spec / prototypes using VES messages to relay PM-like data to SMO
- O1 PM streaming: Specifies ASN.1 data over websocket (aligns with 3GPP)
- Suggestion/Proposal that JSON VES for PM Streaming might be useful too
- Suggest proposal to O-RAN WG10 & 3GPP - wider audience
- VES domain (3gpp 28.532 Annex B) - perf3gpp vs stndDefined
- perf3gpp is older (pre-stndDefined) - used in ONAP until now - and would need to be maintained if kept in future versions.
- stndDefined is schema-based & more extensible (& preferred?).
- Krystian Kedron Test with stndDefined Schema validation in ONAP VES collector has some issues:
- validates whole schema not just relevant part
- Some schemas are missing, & some schema in 3gpp forge are incorrect
- Martin Skorupski CM Notification: Sometimes hard to map CM change back to the Yang model for the change
- Martin Skorupski Similar for other VES messages - when referring to a managed object it is not clearly mandated how to map back to yang model.
- Krystian Kedron Currently ONAP PM Mapper does not support stndDefined ... all notifications mapped to perf3gpp messages
- Krystian Kedron Update of PM Mapper to VES 7.2: https://jira.onap.org/browse/DCAEGEN2-2880
Update for ONAP Requirements Sub Committee
- Timo Perala, Alla Goldner : ONAP Requirements subcommittee request an update on areas where ONAP and O-RAN share interest.
- What is/are the area/s of common interest?
- What is the current state of affairs?
- What are the future topics to address?
- Any issues that require more emphasis from the community, or more formal collaboration relation between the two communities is needed?
- Anything else you think it worthwhile to highlight.
- Others presenting / providing input
- SMO deployment (Christophe)
- Slicing Use case (Ahila)
- ASD container / descriptor
- SON (Shankar)
- Update from OSC/ONAP alignment topics (from last presentation in Mar? 2021)
- Update from this meeting series: (Note this meeting series is informational/discussion only - refer to related decision fora for detail/reference)
- Some topics/headings discussed recently:
- Use cases / prototypes
- ONAP SON use case
- ONAP Slicing use case
- Sleeping Cell etc
- O1
- VES message formats
- CM, FM, PM (File), PM (Stream) etc
- CM yang model alignment
- FM / Alarm coordination
- VES message formats
- A1 Policy
- SMO Deployment (ONAP & OSC & other project's components)
- Test environments
- Simulators
- OSC O1 simulators (generic, O-RU, O-DU)
- OSC A1 simulator
- O1/A1 (Sleeping Cell) CNF simulator
- ONAP RAN simulator
- CNF packaging
- Topology
- Need for higher-level CM models - beyond canonical/spec models
- (later ... O2)
- Use cases / prototypes
- Need to re-stress the desire to have a Formal collaboration between OSC & ONAP, e.g. at requirements & TOC/TSC committee level
- 5G Super Blueprint initiative was proposed as a candidate to drive this, but different levels of engagement in ONAP vs OSC.
- Some topics/headings discussed recently:
Q&A:
- Ran out of time this week