Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info
iconfalse

16:00 UTC, 09:00 PST, 12:00 EST,  17:00 BST, 18:00 CEST, 19:00 EEST, 21:30 IST, 00:00 CST (Thurs), 01:00 JST (Thurs)


ZOOMhttps://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09
Meeting ID: 890 6970 8424

Calendars:

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)


Table of Contents

Table of Contents

Attendees

Administration

Please tag yourself using LF ID User Name.
Don't have an LF ID yet? Go here:
https://myprofile.lfx.linuxfoundation.org/.

LF Antitrust

See also / Co-Located

Goals

  • share information between
    • O-RAN-SC Non-RT-RIC
    • O-RAN-SC OAM
    • O-RAN-SC O-DU
    • ONAP CCSDK/SDNC/SDN-R
    • LFN (wink)

Recording

Discussion items

TimeItemWhoNotes
00:00Admin


Next meetings: 

Please follow the calendar


00:02O-RAN-SCO-RAN-SC PTLs
  • O-RAN-SC ToC
  • Non-RT-RIC: John Keeney (Ericsson EST)
    • demo service management exposure (SME) → demo later ??video will be available later
    • demo for PM - data management → video later today (smile)
    • rApp Management → first experience
    • analytics/insights → also LF issue raised
  • SIM: Alex Stancu
    • NS3-E2: work on documentation
      • github not synched with gerrit → LF issue raised
  • OAM: Martin Skorupski
    • networkupdates network updates in OWL
  • O-DU:Hariom Gupta) / @Vidhu
    • nothing to report
  • AI/ML: @Sandeep J
    • in progress check-in seed-code

00:15ONAP Release managementDavid McBride 

Target for Kohn - nov10

London kick off tomorrow 


00:25SON/slicing Use caseN.K. Shankaranarayanan 
  • A1 policy artifacts are used for the use case.
  • Abstraction for RAN
  • ongoing implementation on RAN-SIM 
  • all in Kohn
  • Tracking RAN-Sim activity: 
    Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-1212
     
  • SON Use Case Architecture Review link: 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyINT-2127
  • https://jira.onap.org/secure/attachment/18086/ONAP_OOF_SON_R11_ArchitectureReview_20220606.pptx

2022-10-05

  • integration with RAN-SIM complete and testing in progress

2022-10-12/19

  • preparation for DTF - email to Timo - Nov17 reserved for x-community - Nov18 for ONAP and this use case

00:26Non-RT-RIC demoJohn Keeney (Ericsson EST) 

Demo PM Data collection


00:00Q/A
None this week.
Have a good week (big grin)

END



00:303GPP copyright issue

Still! "not ok" - how to use NETCONF YANGs from 3GPP and O-RAN

Problem Statement might be not fully understood. 

Next step: Call with Magnus Buhrgard (Unlicensed) 

After the call and some emails: Magnus it preparing a call with 3GPP SA5 representatives and then another ONAP LS to 3GPP

The topic is on the ONAP TSC agenda tomorrow: TSC 2022-09-08

> Magnus wont give up (smile)




Action items

  •