...
E2E Integration Tests
- Instantiation - create new NSI (not-shared, no match with shared, all matching are not-shared, different coverageArea so not matching)
- RAN NSSI - new, Core NSSI - new, TN BH NSSI - new
- RAN NF NSSI - new, ??
RAN NSSI - reuse , Core NSSI - new, TN BH NSSI - new - RAN NSSI - new, Core NSSI - reuse, TN BH NSSI - new
- RAN NSSI - new, Core NSSI - new, TN BH NSSI - reuse
- RAN NSSI - reuse, Core NSSI - reuse, TN BH NSSI - new
- RAN NSSI - reuse, Core NSSI - new, TN BH NSSI - reuse
- RAN NSSI - new, Core NSSI - reuse, TN BH NSSI - reuse
- RAN NSSI - reuse, Core NSSI - reuse, TN BH NSSI - reuse (but all 3 are not part of same NSI, otherwise that NSI would have been reused) Instantiation - reuse existing NSI
- Activation
- Deactivation
- Termination
...
Option 1: RAN NSSMF shall be responsible for entire RAN subnet, including RAN NFs, FH and MH. All 3 NSSMFs are within ONAP.
| S.No. | Topic | Description | Dependency | Tester | Status | Remarks | ||||
|---|---|---|---|---|---|---|---|---|---|---|
| 1. | Service Design | 1a. Design of CST, and necessary templates for 1 type of service (e.g., eMBB): NST, NSST for RAN, RAN NF, Core & TN, Service Profile and Slice Profiles |
| |||||||
| 2. | Design of necessary templates for 2nd type of service (e.g., mMTC): NST, NSST for RAN, RAN NF, Core & TN, Service Profile and Slice Profiles | |||||||||
| 3. | Service instantiation | See below table for (a) to (g) | ||||||||
| 4 | Service instantiation with manual intervention | For scenario (c) in below table, operator shall override via NSMF portal in UUI the selection of reusable NSI and indicate creation of new NSI. | (c) should work first | |||||||
| 5 | Service activation | Activate an S-NSSAI/ |
Instantiation - Should involve call to NSMF, calls to NSSMFs (allocate or modifyNSSI API calls), and then SB calls/actions on NSSI constituents. In case of RAN NSSI, it should involve calls to TN (for FH and MH) and RAN NF NSSI creation/update.
| S.No. | Priority | Input service | NSI | RAN NSSI | Core NSSI | TN BH NSSI | TN FH & MH NSSIRemarks | |
|---|---|---|---|---|---|---|---|---|
| a | 1 | eMBB like service parameters No sharing | New | New | New | New | ||
| b | 1 | eMBB like service parameters Sharing allowed | New | New | New | New | Pre-requisite: There is no existing shareable suitable NSI or NSSIs | |
| c | 1 | eMBB like service parameters Sharing allowed | Reuse | X | X | X | X = automatically all NSSIs are reused | |
| d | 1 | eMBB or mMTC like service parameters Sharing allowed | New | Reuse | New | New | Pre-requisite: There is an existing RAN NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way RAN NSSI is reused, or creating a suitable and shareable RAN NSSI upfront. | |
| e | 1 | eMBB or mMTC like service parameters Sharing allowed | New | New | Reuse | New | Pre-requisite: There is an existing Core NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way Core NSSI is reused, or creating a suitable and shareable Core NSSI upfront. | |
| f | 2 | eMBB or mMTC like service parameters Sharing allowed | New | New | Reuse | New | Pre-requisite: There is an existing RAN & Core NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way RAN & Core NSSI are reused, or creating suitable and shareable RAN & Core NSSIs. | |
| g | 2 | eMBB or mMTC like service parameters. with coverageArea more than what is already supported in a suitable existing and shareable NSI Sharing allowed | New | New | New | New | Pre-requisite: There should be a suitable existing NSI that is shareable, but whose coverageArea is smaller or does not have full overlap with the new service request. |
Option 2: RAN NSSMF shall be responsible for RAN NFs alone. FH and MH are not included. Only TN NSSMF is within ONAP.
...