This page captures the consolidated list of key assumptions.
| Table of Contents |
|---|
...
| outline | true |
|---|
1. Common aspects
Association between NST and NSST shall be fixed at design time. In other words, an NST shall be composed of a set of NSSTs at design time.
As a result of (1), the AllocateNSSI API shall contain NSST info. This shall be re-visited beyond Guilin.
If the NSSMF is not capable of NSSI selection, ONAP acting as NSMF shall perform NSSI selection also and then pass the NSSI info in the AllocateNSSI API. This situation shall arise only when connecting to an external NSSMF, as all NSSMFs within ONAP shall support NSSI selection.
Sub-net capabilities are assumed to be pre-configured, i.e., no dynamic updates due to resource occupancy levels, etc.
When selecting an NSI or NSSI, resource occupancy levels shall not be taken into consideration when deciding to reuse an existing shareable NSI/NSSI (when the request allows sharing). The match with existing NSI/NSSI by OOF shall be made only on the attributes related to performance requirements (e.g., latency, throughput, etc.) and not based on attributes related to the slice/slice sub-net 'dimensions'.
...