Wednesdays at 16:00 UTC in Summer (DST), 17:00 UTC in Winter ! Zoom Bridge : https://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09
Please checkout the calendars: |
Co-located with ONAP 2023-02-08 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)
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
(R1) Service Exposure & Management
(R1) Data Management & Exposure
rApp Management
Continued A1-Policy & A1-Enrichment-Information evolution (& R1-A1)
Testing, Maintenance & Housekeeping
No Update
Ref: RSAC Meetings
Minutes & Meeting: Meeting notes
No update this week
Non-RT-RIC A1-related: → WG2
Good amount of existing work and harmonization effort (e.g. A1 interface, modification of ONAP RAN-Sim to support A1
Continue effort to re-use code and principles
Non-RT-RIC rApp: → WG2 (WG10, app management)
Good amount of work in OSC - reusing alot from ONAP
(**New area) - Ongoing effort to seek out ways to align with ONAP control loops and use cases (originally designed without knowledge of R1)
SMO Policy Functions:
(** New area) - ONAP has had a Policy Enforcement Function since beginning, and there is no obvious mapping to existing SMO architecture
O2 related, cloud management → WG6
ONAP has a lot of work on NF orchestration and management - looking at O2 support
(**New area) - Relatively less focus on cloud infrastructure management (role for other LFN projects? - e.g. Nephio?)
(**New area) - integration of use cases which cover both IMS and DMS part of O2
Orchestration (end-to-end aspects, including components inside SMO) -
(**New area) - ONAP has lot of work on Service Design and Orchestration. May be worthwhile for OSC to be align to leverage past work?
AI/ML related (Training, ...) → WG2
(**New area) - ONAP work did not assume role of Non-RT and Near-RT RIC. AI/ML work was generic.
Security → WG11
Good amount of shared objectives - security of interfaces design, system implementation, code design etc
Can share best practices etc
Simulation work -> OSC
Ongoing effort to leverage/harmonize
OSC sim work oriented towards OAM (CU/DU/O1), ONAP Sim work oriented towards use case (RAN-Sim)
ONAP RAN-Sim adaptation - A1 termination, abstraction of near-rt-ric and xapp, exploring porting
End-to-end use case -> WG1, OSC
End-to-end slicing, SON, Intent-based, OAM, life-cycle management
Scope for sharing work and aligning objectives
Architecture -> WG1
(**New area) - Identification of building block sub-systems - esp. related to SMO. (SMOS/SMOF concept?)
Target to have only small list of recommended approaches, harmonization/code re-use within same approach
Meeting ends