2023-08-01 Meeting notes - Joint OAM / NONRTRIC / SIM Community meeting
Time & Location:
Meeting Detail: Times & Joining Info
Tuesdays at 14:00 UTC in Summer (DST), 15:00 UTC in Winter
https://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09
Ensure you are signed into your Zoom account to join.
Meeting ID: 890 6970 8424. By Phone: Dial in (Local numbers): You will need a Participant ID so you will need to join the meeting from a Zoom client first to get this.
NOTE: During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of the meetings may fluctuate.
Summer Daylight Savings time (Q2, Q3) eventually stabilizes to:
7am PDT | 10pm EDT | 14:00 UTC | 15:00 BST | 16:00 CEST | 17:00 EEST | 19:30 IST | 22:00 CST | 23:00 JSTWinter (non-DST) time (Q4, Q1) eventually stabilizes to:
7am PST | 10am EST | 15:00 UTC | 16:00 GMT | 17:00 CET | 18:00 EET | 20:30 IST | 23:00 CST (Thurs) | 00: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
Aug 1, 2023
Attendees
@John Keeney (Ericsson EST) (Ericsson EST & OSC NONRTRIC)
@Martin Skorupski (Highstreet & OSC OAM)
@Alex Stancu (Highstreet & OSC SIM)
@James Li (CMTI & OSC INT)
@Varadarajan (Samsung)
@Denis G Noonan (Ericsson Software Technology) (Ericsson EST)
@Ambrish Singh (Ericsson EST)
@Sonia Sangari (Ericsson EST)
@Kevin Timoney (Ericsson EST)
@Aravindhan Ayyanathan(Ericsson EST)
@Rohith Rajneesh (Ericsson EST)
@Kevin Timoney (Ericsson EST)
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-08-01 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)
Contents
- 1 Time & Location:
- 2 Anti-Trust Notice
- 3 Date
- 4 Attendees
- 5 See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)
- 6 Contents
- 7 Recording
- 8 Notes:
- 8.1 Housekeeping:
- 8.2 OSC Project roundup:
- 8.2.1 News from OSC TOC call last week
- 8.2.2 NONRTRIC (@John Keeney (Ericsson EST))
- 8.2.3 SIM (@Alex Stancu)
- 8.2.4 OAM (@Martin Skorupski)
- 8.2.5 O-DU @Vidhu (Deactivated))
- 8.2.6 OSC Integration / INT (@James Li )
- 8.2.7 SMO (@Seshu Kumar Mudiganti )
- 8.2.8 RSAC (@David Kinsey [AT&T] @Rittwik Jana )
- 8.2.9 AI/ML platform project (@Joseph Thaliath)
- 8.3 SMO end-to-end & SMO in Opensource (@N.K. Shankaranarayanan )
- 8.4 ONAP Update (@N.K. Shankaranarayanan @Seshu Kumar Mudiganti )
- 8.5 ONAP/OSC Usecases (@N.K. Shankaranarayanan)
- 8.6 PM Data Streaming (@Martin Skorupski & All)
- 8.7 Questions / Comments / AOB:
Recording
Notes:
Housekeeping:
Calendar:
7am PDT | 10pm EDT | 14:00 UTC | 15:00 BST | 16:00 CEST | 17:00 EEST | 19:30 IST | 22:00 CST | 23:00 JST
OSC SMO project calls now move to its own time slot - alternate Thursdays - TBC
See OSC RSAC Calendar: https://lf-o-ran-sc.atlassian.net/wiki/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://lf-o-ran-sc.atlassian.net/wiki/display/TOC/#ORANSCTechnicalOversightCommittee(TOC)
Last week's TOC (Thursday):
OAI & OSC collaboration is making some progress
Discussion on a whitepaper for SWRBP for end-to-end use case (Super Wireless RAN BluePrint)
This week's TOC (in 2 days):
NONRTRIC (@John Keeney (Ericsson EST))
Work ongoing - as per last week:
RAN PM functions - tidying up & re-releasing in maintenance release.
Working with AIMLFW project: @Joseph Thaliath to use newer versions
Making good progress on rApp manager. More in coming weeks
3PP dependency updates & addressing vulnerability
OpenAPI-first in A1-PMS & ICS
Change from code→openapi→docs to openapi → code-stubs & docs
To better align with R1 specs as they mature
To improve expressivity of docs etc.
Issue with test framwwork
underscore in URI hostnames - introduced by docker-compose (v1)
Some changes in A1-Mediator in near-RT-RIC plt in H-Release.
Further investigation needed re effects on A1-PMS/ICS & A1-SIM
SIM (@Alex Stancu)
No major update
@Alex Stancu was away last week.
OAM (@Martin Skorupski)
Looking at Netconf "Yang Schema Mount" for O-DU/O-RU relationship (WG5 yang models)
making some progress ... more to come
Request (from RSAC) to make proposal for RAN PM streaming
See below
Working with team in T-Systems to update ONAP VES collector to work with native kafka.
O-DU @Vidhu (Deactivated))
No update this week
OSC Integration / INT (@James Li )
Near-RT-RIC team today showed a demo of osc near-rtr-ric with an updated version of OAI DU/CU
To work with KPIMon xApp.
Hope to be able to reuse this work in ongoing OAI collaboration
SMO (@Seshu Kumar Mudiganti )
Meeting notes Meeting notes
No Update this week
RSAC (@David Kinsey [AT&T] @Rittwik Jana )
No update this week
Minutes: 2024 RSAC Meetings
Good discussion about I-Release plans, & how to report progress according to new streams/usecases.
More to follow in coming RSAC & TOC calls.
Some concern about scope ambition vs resourcing ...
Maybe discuss at SMO call tomorrow?
AI/ML platform project (@Joseph Thaliath)
Minutes & Meeting: Meeting notes
No update this week
SMO end-to-end & SMO in Opensource (@N.K. Shankaranarayanan )
No update this week
ONAP Update (@N.K. Shankaranarayanan @Seshu Kumar Mudiganti )
No update this week
ONAP/OSC Usecases (@N.K. Shankaranarayanan)
No update this week
PM Data Streaming (@Martin Skorupski & All)
(Recording timestamp @ 10:30)
O-RAN OAM spec refers to 3GPP specs to use websocket for transport
Data serialisation format options presented by 3GPP: Ref sect 11.5 TS 28.532
Suggestion to do 3gpp-XML→yang→GPB ...
Refer to "establishStreamingConnection" operation, table 11.5.1.1.2 "streamInfoList" input parameter where PM stream job is defined
But how will the SMO terminate streams, parse, and distribute the data?
Proposal
SMO needs a Websocket stream terminator (e.g. to: S3 bucket, or Kafka?)
SMO needs a GPB data parser (to: XML, or JSON?)
<a big gap - for further study>
Alot depends on the data characteristics & scalability concerns
Then re-use NONRTRIC RAN PM functions so rApps can subscribe to filtered PM data in JSON format in Kafka and/or InfluxDB
Need to read-up some more and come back to this in future weeks.
Need to clearly demonstrate if there is a benefit beyond file-based PM and/or streamed trace data.
e.g. shorter reporting period (ROP) file-based?
Very significant scalability challenges as reporting period decreases, network function increases, job count per function increases.
Questions / Comments / AOB:
None this week.
Meeting ends 51min