...
2. Call from SO to OOF to get suitable NSI
1. Call from SO to OOF to Get suitable NST
Inputs: Service Profile parameters, NST id
...
Let us assume that the NSI inventory is as follows:
| NSI Id | NST Id | NSSI RAN Id | NSSI Core Id | NSSI Transport Id |
|---|---|---|---|---|
| NSI-1 | NST_URLLC1 | NSSI-R-1 | NSSI-C-2 | NSSI-T-1 |
| NSI-2 | NST_ |
| URLLC2 | NSSI-R- |
| 6 | NSSI-C- |
| 4 | NSSI-T- |
| 3 |
| NSI-3 |
| NST_eMBB2 | ... |
Solution 1
----------
NSI-10 which has URLLC1_NST
...
| ... | ... | |
| NSI-4 | NST_URLLC2 | NSSI-R-1 |
...
| NSSI-C-1 | NSSI-T-1 | |||
| ... | ... | ... | ... | ... |
| NSI-10 | NST_URLLC3 | NSSI-R-5 | NSSI-C2 | NSSI-T-4 |
Say, HAS returns the foll. solutions:
Solution 1 = (Solution 2
----------
NSSI-R-1, NSSI-C-newC2, NSSI-T-2 (HAS to OSDF) => New NSI (OOF to SO) with slice profile
T1)
Solution 2 = (NSSI-R-1, NSSI-C2(Core-slice profile), NSSI-T-1 (HAS to OSDF) => Re-use NSI-1 (OOF to SO)NSSI-R1 is part of NSI-1,NSI-3) (assuming NSSI-T-3 has NSST_URLLC_TRAN2 as its template).
OSDF then does the following:
- For Solution 1, it sees:
NSSI-R1 is part of NSI-1,NSI-4
NSSI-C2 is part of NSI-1, NSI-10
NSSI-T1 is part of NSI-4, NSI-1
There is a common "NSI" which is "NSI-1". So NSI-
...
1 can be reused. It fills the shared NSI solutions part of response to SO with NSI-1.
- For solution 2, NSSI-R-1, NSSI-C-new, NSSI-T-3 => It fills New NSI solutions part of the response to SO with NSSI ids and slice profile(s).