Work Items
1. Frankfurt Improvements
| No. | Track | Description | Jira | Impacts | Remarks |
|---|---|---|---|---|---|
| 1.1 | NST selection | Implementation of NST selection in HAS | HAS | Common understanding of how to fetch template details from SDC | |
| 1.2 | Implement callback for NST selection | OSDF, SO | |||
| 1.3 | NSI/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.7 | Slice profile generation - candidates should be generated at appropriate granularity |
| |||
| 1.8 | Slice profile selection - choose best one, based on service profile, subnet capabilities (and optionally existing NSSIs, if sharing is allowed???) | ||||
| 1.9 | Implement callback for NSI/NSSI selection | OSDF, SO | |||
| 1.10 | API alignment - service/slice profile parameters, json blob at the end | OSDF, SO | |||
| 1.11 | Selecting "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.12 | NSI/NSSI Termination | API and response for NSI termination - yes or no (check Policy also) | OSDF, SO | Request should come from SO acting as NSMF | |
| 1.13 | API and response for NSSI termination - yes or no (check Policy also) | OSDF, SO | Request should come from SO acting as NSSMF |
2. NSSI Selection
- RAN NSSI Selection
- Core NSSI Selection
- Transport NSSI Selection