...
We have yet to present it in a future meeting, where we need to present the way Nephio and OSC.
Futuristic Functions in SMO:
Inventory
Currently we are dependent on the IMS data base for all the related info of the clusters.
This needs to be corrected and have the updates directly in the SMO Inventory (closer to IMS).
IMS should update this inventory on any change made to the underlying O-cloud.
Esp NFO currently fetches the DMS id from IMS database.
The current inventory simulator in the OAM component is more of a reference than a realistic inventory.
AAI was one of the candidates, but is found too heavy for the RAN based operations.
SO (as an E2E orchestration piece)
This is being discussed in the ORAN WG1 and would be integrating with both FOCOM and NFO.
SBI of SO would integrate with the current FOCOM and NFO.
Homing and placement decisions would be part of the SO and would drill down to the NFO for the actual work delegation.
| View file | ||||
|---|---|---|---|---|
|
J release:
Updates from Nephio, OAI integration work.
...
- ETSi DMS (through Tacker) - Toshi
- OAI oDU to be instantiation through the ETSi Profile (Tacker)
- Stretch : FM Data from the OAI oDU (TB Checked on API and workload) if can be generated and captured by the Tacker (This is in-line to the Plugfest NA (Dec -2023) usecase).
- Action 1 : Seshu to check with OAI team on the possibilities. ODU PTL (Ankit) to be checked for the example implemented in the OSC.
- 2 : Toshi To discuss the E2E scope of this functionality. (Involve OAM)
- PM Data would be a future scope item.
- 3GPP File based are already supported by RIC- John
- Stream based is open - John.
- FOCOM - Seshu
- NFO K8s Profile - Seshu
- Recording:
View file name video1481058530.mp4 height 150View file name NF Orchestration Using SMO (Design details).pdf height 150 
...