Versions Compared

Old Version 3

changes.mady.by.user Seshu Kumar Mudiganti

Saved on

compared with

New Version 4

changes.mady.by.user Seshu Kumar Mudiganti

Saved on

Key

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

...

Nephio SIG-1 - WG2 integration with OSC: Widget Connectorurlhttps://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$


Nephio Deck  (5,6)

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? 
    3. If so then we can do the use cases (bolded) in slide 5, 6. The others would be incorporated once the SMO supports those features (e.g., inventory, O-Cloud retrieval)
  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?

...