Versions Compared

Key

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

...

DetailsItemWhoNotes

ETSi Profile Tacker flow discussion




I release 

Toshiaki

 

Review the ETSi profile DMS slide deck through Tacker flows and prep for RSAC meeting.

Find the integration points,

correct the ETSi sol definitions around the APIs, 

Architecture diagram to be reviewed from the E2E flow.

Test cases to be reviewed if and when they are ready.


30th Sept Aug 2023

Create Stories under the Epic for the I release and follow up.

This is the current target for the I release

  • Tacker would be integrated with Inf project and DMS interfaces would be tested .
  • Tacker should continue the H release effort and then take it forward
  • Who would start the flow (David)
    • We would start with the interfaces with the inf (Seshu)
    • This is ok, but need to also make sure we would need the other components in the SMO in the long run. need to check when and how long would it take to reach it.
  • O2 should have some way in IMS to register that would help us to make the connect to the DMS, DMS would be exposed and consumed but we would need to have the connect to have the E2E registration between the IMS to the DMS flow. (David)
  • This would also include the parts of the inventory that would need to be on the FoCOM part that needs to be exposed and consumed by the DMS and deploy  the workloads (Seshu and David)
  • Missing part is not described in ORAN yet but in ONAP with the interactions with the inventory function (Shankar).
  • E2E flow would be to have the FoCOM and NFO to have the interactions and have the handsoff with the change in the inventory record, the nature of the de-coupled SMO would not have the explicit event to DMS.
  • A messaging bus with a pub-sub would be ideal to have to this transition notified.

--------

SMO to OAM

  • Toshi CRs for the possible flows on the SMO in the WG1 - (need to reexamine and start it to see how would it help us to have the above points addressed).
  • Try to influence the WG1 with a sample implementation. 
  • Restore the older flows of Toshi and put them up for the upcoming meetings. (David).




Energy Saving 
Rittwiki

4 capacity cells and coverage cell in center, generate the PM metrics (Like throughput) and use it for AI ML mode testing.

The ask is was to check if we have a simulator that can generate such a data can be used dynamic based on the time of the day.

Once they are generated they can be used by the AI ML project and then the rApp projects to simulate the required data and validate the flows.

Step 1: Detect / predict, through AI ML body.

Step 2 : once detected we should be able to perform action through the rApp. handle the users and switch off the cell.

Alex confirms we don't have a ready to use simulator yet but needs to check if that can be made available. 

This can further be checked in ToC meeting this week.


30 Sept Aug 2023:

Data set from Tim would be a starter.

Viavi volunteered to help and test it 

Train a model and Bimo (Taiwan) would help

Connect Udi with Ritwik for Energy efficiency Plugfest data. - Seshu


...