Page History

...

SO request OOF for NSI/NSSI selection
OSDF fetches the optimization policies for the requested NST/NSST
OSDF request HAS(conductor) for optimization
HAS fetches the list of NSIs/NSSIs from AAI
Using the NSI/NSSI id that it fetched from AAI, HAS requests DCAE(Slice Analysis MS) with attributes present in the service profile
DCAE returns current ~~capacity~~ utilization of the resources by the requested NSIs/NSSIs
Based on the current ~~capacity~~, utilization, HAS run the optimization to choose the suitable NSI/NSSI
The selected NSI/NSSI is returned to OSDF, which forwards it to SO

Step 7 - Optimization to be done based on the following points :

NSI Selection:

Find the configuration requested for the NSI for the current request from AAI ( Fetch Service Profile)
Find the difference between the response from DCAE and the requested config for the NSI (maxNoOfConnections in DCAEResponse – MaxNoOFPDUSessions in ServiceProfile)
If the difference is > 0, allow for NSI reuse

RAN NSSI Selection:

Find the configuration requested for the RAN NSSI for the current request from AAI ( Fetch AN Slice Profile)
Find the difference between the response from DCAE and the requested config for the RAN NSSI
If the difference is > 0, allow for RAN NSSI reuse
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:

Find the configuration requested for the RAN NF NSSI for the current request from AAI ( Fetch AN NF Slice Profile)
Find the difference between the response from DCAE and the requested config for the RAN NF NSSI
If the difference is > 0, allow for RAN NF NSSI reuse

Outgoing APIs

Already present in the code. The below pages contain the details regd. the AAI APIs used.

...

}]

}

NOTE: sliceIdentifier – NSI/NSSI ~~can be SNSSAI/slice-profile-id~~ NSSI

...