Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Work Items

Frankfurt Improvements

No.TrackDescriptionJiraImpactsRemarks
1.1NST selectionImplementation of NST selection in HAS
HASCommon understanding of how to fetch template details from SDC
1.2

OSDF, SO
1.3NSI/NSSI selection

For NSI/NSSI selection, fetching NSST details - from SDC or to be provided in the request from SO
OSDF?Common understanding of how to fetch template details from SDC
1.4

During NSI/NSSI selection, when the attribute (e.g., reliability) in Threshold Policy is not part of Slice Profile, it should be ignored by HAS (error should not be returned)


HAS
1.5

Aggregate policy to be implemented, e.g., latency of all NSSIs chosen to be < latency in Service Profile.




1.6

When considering existing NSSI as a candidate, consider ALL slice profiles (not just “best” one).




1.7Slice profile generation - candidates should be generated at appropriate granularity

  • To be generated even when reusing an existing NSI?
  • Which parameters to generate (per domain type) to be policy driven or come from Slice Profile Template, as well as should depend on the parameters received in the service profile 
1.8Slice profile selection - choose best one, based on service profile, subnet capabilities (and optionally existing NSSIs, if sharing is allowed???)


1.9Implement callback for NSI/NSSI selection
OSDF, SO
1.10API alignment - service/slice profile parameters, json blob at the end
OSDF, SO
1.11Selecting "final" solution by OOF based on policy - minimum change policy, maximum slice count policy, reuse policy, etc.
OSDF?OOF API also to be updated to remove the 'list' of solutions
1.12NSI/NSSI TerminationResponse for NSI termination - yes or no (check Policy also)
OSDF
1.13Response for NSSI termination - yes or no (check Policy also)
OSDF

RAN Slicing

  • No labels