Versions Compared

Old Version 32

changes.mady.by.user Malarvizhi Paramasivam

Saved on

compared with

New Version 33

changes.mady.by.user Ahila P

Saved on

Key

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

...

Step 7 - Optimization to be done considering the following points : 

NSI Selection:

  1. Find the configuration requested for the NSI for the current request from AAI ( Fetch Service Profile).  This step is not required as Service Profile comes as an input to OOF for NSI Selection.
  2. Find the difference between the response from DCAE and the requested config for the NSI (MaxNoOFPDUSessions ulThptPerSlice in DCAEResponse - ulThptPerSlice in ServiceProfile – maxNoOfConnections in DCAEResponse, similarly for dlThptPerSlice)
  3. If the difference is > 0, allow for NSI reuse

RAN NSSI Selection:

  1. Find the configuration requested for the RAN NSSI for the current request from AAI ( Fetch AN Slice Profile)  Slice Profile need not be fetched from AAI, it is an input to OOF for RAN NSSI Selection
  2. Find the difference between the response from DCAE and the requested config for the RAN NSSI (ulThptPerSlice in DCAEResponse - expDataRateUL in SliceProfile, similarly for dlThptPerSlice)
  3. If the difference is > 0, allow for RAN NSSI reuse
  4. For the moment, we can assume that the calculation for TN-FH and TN-MH slices returns true by default. But keep a place holder to do all these findings for TN-FH and TN-MH slices. We can enhance it later.

RAN NF NSSI Selection:

  1. Find the configuration requested for the RAN NF NSSI for the current request from AAI ( Fetch AN NF Slice Profile)  Slice Profile need not be fetched from AAI, it is an input to OOF for RAN NF NSSI Selection
  2. Find the difference between the response from DCAE and the requested config for the RAN NF NSSI (ulThptPerSlice in DCAEResponse - expDataRateUL in SliceProfile, similarly for dlThptPerSlice)
  3. If the difference is > 0, allow for RAN NF NSSI reuse

...