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 (China Mobile & OSC INT)
- N.K. Shankaranarayanan (ONAP TSC)
- Pawel Pawlak (F5 & ONAP TSC chair)
- Magnus Buhrgard (Ericsson & ONAP TSC)
- Ranny Haiby (LF)
- Bob Heinemann (MITRE)
- Halil Cakal (Ericsson EST)
- Aravindhan Ayyanathan (Ericsson EST)
- Kevin Timoney (Ericsson EST)
- Sonia Sangari (Ericsson EST)
- Carsten Höseler(TU-Dortmund)
- user-941ad (Fujitsu)
- 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-11 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)
Contents
Recording
Notes:
Housekeeping:
Happy 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):
- Cancelled
- No update.
- This week's TOC (Tomorrow):
- No update.
- Last week's TOC (Thursday):
NONRTRIC (John Keeney)
Release G completed before Christmas/New Year break.
- 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.
SIM (Alex Stancu)
- Still working on OSC H Release Planning
OAM (Martin Skorupski)
- Looking at OAM Specs from O-RAN Alliance & 3GPP REL 18
- e.g. Updating VES stddefined support etc, new versions of SDNR etc.
O-DU (Hariom Gupta Vidhu Shekhar Pandey)
No Update
OSC Integration / INT (James Li )
- Plan to use XTesting integration tests with INF project (esp for O2)
RSAC/SMO (David Kinsey)
Ref: RSAC Meetings
Update from AIML project re Release H plans
Included discussion on overlap/alignment/integration opportunities with NONRTRIC, SMO, Near-RT-RIC, RICAPPs, OAM projects.
Update from O-DU HIgh project re Release H plans
Update from SMO Tacker project re Release H plans
OSC/ONAP
Mentioned this meeting - Unfortunately David Kinsey cannot attend today - meeting clash.
Upcoming Open RAN workshop
(... will add a link when i find it: https://www.knaintl.com.tw/2023OpenRan/ ??)
AI/ML platform project ()
Minutes & Meeting: Meeting notes
No update this week
- See discussion at RSAC this week.
- Also some good discussions at this week AIMLFW Project meeting
ONAP Use cases (N.K. Shankaranarayanan)
No time for an update this week
ONAP / OSC / O-RAN Alliance: Cooperation & Alignment
Discussion: ONAP TSC Would like to better formalize relations between ONAP & O-RAN SC, and ONAP & O-RAN Alliance
- @00:13:00 in Recording
- Pawel, Magnus Buhrgard, Bob, N.K. Shankaranarayanan
- Also trying to establish a snapshot of interactions currently
- How to improve cooperation
- Goal: Avoid fragmentation, improve synergy, avoid duplication, raise awareness
- (Unfortunately .. (or fortunately) ONAP TSC & OSC TOC calls are at the same time)
- Areas being considered in ONAP: Is there a need to streamline requirements gathering process & cadence, release processes & cadence, integrated platforms vs services, using licensed specs
- Same considerations could be looked at in OSC too - to have a 2-way flow of awareness, requirements, software,
- For example, there can be a very significant lag between a requirement becoming obvious in one project, and released software being available in the other ... often Many months.
- Rule of thumb: A project should only use 'released' software from other communities
- It would be better to have a much more flexible, continuous, faster cadence of requirements planning & interim or continuous software releases. (while also keeping the periodic Major Release time scales)
- Would be good to have better cooperation between specification work & implementation (pre-spec & post-spec)
- Note: Any project - not just OSC - including ONAP - can consume/feedback to O-RAN Alliance on a equal basis
- Would be good to better understand if/what 'special relationship' between OSC & O-RAN Alliance. No blocker exists to other projects.
- O-RAN Licensing remains an issue for all opensource projects - including ONAP & OSC
- Note: Any project - not just OSC - including ONAP - can consume/feedback to O-RAN Alliance on a equal basis
- Some topics where there is a clear interaction ONAP/OSC - and alignment would be beneficial:
- release cadence
- non-rt-ric / smo
- rapps
- oam
- orchestration and cloud
- simulator (O-CU, O-DU, O-RU)
- use cases alignment
- integration
- license issues
Potential actions
- Invite attendees from ONAP REQ and O-RAN-SC RSAC to join the other - Even if just a once off initially
- Just a "hello" to start?
- Links:
- OSC Requirements & Software Architecture Committee: https://wiki.o-ran-sc.org/display/RSAC
- ONAP Requirements Subcommittee: https://wiki.onap.org/display/DW/Requirements+subcommittee
- Invite attendees from ONAP TSC and O-RAN-SC TOC to join the other - Even if just a once off initially
- Just a "hello" to start ?
- Links:
- Further discussion in ONAP TSC about ways forward.
- Explanation of the difference between O-RAN Alliance and O-RAN SC
- Clarify if there is a 'special relationship'
- Invite attendees from ONAP REQ and O-RAN-SC RSAC to join the other - Even if just a once off initially
Questions / Comments / AOB:
- Follow up Note on opensource/specification alignment: :
- Magnus Buhrgard, Martin Skorupski, John Keeney
- Would be good to have a separate discussion about how opensource and specification activities could benefit each other better if there was better interactions.
- O-RAN Alliance seems like a particularly good candidate to examine this
- Lets discuss this further in another call.
- Magnus Buhrgard, Martin Skorupski, John Keeney
- No more time this week
Meeting ends