Versions Compared

Old Version 2

changes.mady.by.user Seshu Kumar Mudiganti

Saved on

compared with

New Version 3

changes.mady.by.user Seshu Kumar Mudiganti

Saved on

Key

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

...

View file
nameORAN Plugfest NA.pptm
height250


Nephio SIG-1 - WG2 integration with OSC:


Widget Connector
urlhttps://urldefense.com/v3/__https:/docs.google.com/presentation/d/11HU2FViGtrfvrcSK3LKJJiMcxulaP_VSqLn9-2XAU-E/edit*slide=id.g28c0a3d23ff_1_162__;Iw!!AjveYdw8EvQ!Zl0XOetJUqAQssJEiFk0cjvfRrJIkjBQ_GhziXc8J0iv6oM8Edfx9uu-mQk_vnv1eqWHiy4q5r4092OD7_WBnFEGDu41b4c$

  1. SMO (FOCOM/NFO) functionality:
    1. Would the SMO be able to have the ability to define an O-Cloud and then support the registration of the O-Cloud via the IMS interface? 
    2. Would the SMO be able to deploy a packaged O-RAN using the K8s DMS profile? 
  2. O-RAN NF
    1. Can we at least 1 O-RAN NF (say O-CU CP) and deploy that package via the SMO/NFO? (This would mean the package would have to be in the format the SMO could understand) 
    2. Can use O1 to change the configuration of an O-RAN NF (e.g., DU) – what, if anything, do we want to show regarding the O1 interface? Sagar said: DU we can configure via O1 and get the heartbeat. Can the SMO support this type of change?




Previous Agenda

23-11-27

  1. O-RAN SMO enhancements - Aarna Networks (Bhanu and Sandeep)
    View file
    nameSMO_Upstream_Aarna.xlsx
    height250

  2. Problem Statement: While trying to remove the device, the callhome device doesn’t get removed and the mount point that we’re trying to remove is not found.
    Impact: Customer will not be able to remove the call home device from SMO
    Workaround: None. In the worst case scenario, restarting of the call home device or disconnecting the netconf client will work which may not be a viable option for the customer
    RCA: Document Attached
    Community JIRA: https://jira.opendaylight.org/browse/NETCONF-989
    Community Forum: Attached the image (in ONAP CCSDK)

  3. Continuation to the previous discussion on ONAP SO vs SMO
    1. Planning to have a discussion on the Nephio R2 F2F meeting - to talk on how these communities can collaborate in the long run
    2. Operator based, ASD, integration points across these communities and see how can we leverage the functionalities.
    3. Timo, Seshu and Byung to participate and present the ideas around the topic.
    4. ONAP E2E orch, Nephio domain and ORAN for the RAN specific workloads as a starting point.
    5. (Byung) Sana discussed on WG1 Nephio on how the NFVO and other components would interact.

...