Legend:
NOT STARTED IN PROGRESS DEFERRED COMPLETED
E2E Integration Tests
Responsibles: Ahila P, @Ratna Shankers:Deepika S, LTE Next Generation
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 | 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 | IN PROGRESS | |||
| 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 | NOT STARTED | ||||
| 3. | Service instantiation | See below table for (a) to (g) | IN PROGRESS | Assumption is manual intervention does not override ONAP selection | ||
| 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) for service instantiation should work first | NOT STARTED | ||
| 5 | Service activation | Activate a service - this should result in activation of new NSI and associated new NSSIs. | (a) or (b) for service instantiation should work first. | NOT STARTED | ||
| 6 | Activate a service - this should result in activation of S-NSSAI, and the activate command should pass to all the NSSMFs | (c) for service instantiation should work first | NOT STARTED | |||
| 7 | Service deactivation | Dectivate a service - this should result in deactivation of new NSI and associated new NSSIs. | Test case 5 should be completed | NOT STARTED | ||
| 8 | Dectivate a service - this should result in deactivation of S-NSSAI, and the deactivate command should pass to all the NSSMFs | Test case 6 should be completed | NOT STARTED | |||
| 9 | Service termination | Terminate a service - this should terminate NSI and all associated NSSIs | NOT STARTED | |||
| 10 | Terminate a service - this should terminate NSI but terminate only | |||||
| 11 | ||||||
| 12 | Terminate a service - this shouldn't terminate NSI or its associated NSSIs | |||||
| 13 | KPI Computation | |||||
| 14 | Closed Loop | |||||
| 15 | Intelligent Slicing |
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 | Tester | Status | Remarks |
|---|---|---|---|---|---|---|---|---|---|
| a | 1 | eMBB like service parameters No sharing | New | New | New | New | IN PROGRESS | ||
| b | 1 | eMBB like service parameters Sharing allowed | New | New | New | New | IN PROGRESS | Pre-requisite: There is no existing shareable suitable NSI or NSSIs | |
| c | 1 | eMBB like service parameters Sharing allowed | Reuse | X | X | X | IN PROGRESS | X = automatically all NSSIs are reused | |
| d | 1 | eMBB or mMTC like service parameters Sharing allowed | New | Reuse | New | New | NOT STARTED | 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 | NOT STARTED | 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 | NOT STARTED | 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 | NOT STARTED | 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.
Note: Core NSSMF can be inside ONAP or outside ONAP for this Option. Only RAN NSSMF has to be outside ONAP.
| S.No. | Topic | Description | Dependency | Tester | Status | Remarks |
|---|---|---|---|---|---|---|