| S. No. | Topic | Test Case Description | Priority | Dependency/Issue | Tester | Status | Remarks |
|---|
| NSMF_01 | Service/template design | Successful design of CST and Service Profile Templates | 1 |
| Zhang Min| Status |
|---|
| colour | Grey |
|---|
| title | NOT STARTED |
|---|
| COMPLETED |
|
| NSMF_02 | Service/template design | Successful design of NST (option 1 and option 2) | 1 |
| | COMPLETED |
|
| Status |
|---|
|
| colour | Grey |
|---|
| title | NOT STARTED |
|---|
NSMF_03Service instantiation | Service instantiation via CSMF Portal (UUI) for Option 1/2 resulting in NST Selection request from SO towards OOF, and receiving the NST details in the callback from OOF. Note: Since OOF fetches NST details from SDC, there is no need for any manual configuration to onboard templates in a flat file. | 1 | NSMF_04 | Service instantiation (Option 1) | After NST selection, NSMF (SO) fetches sub-net capabilities for the 3 constituent sub-nets (RAN, Core and Transport) for Option 1. | 2 | NSMF_05 | Service instantiation (Option 1) - New NSI | NSMF (SO) triggers OOF for NSI selection (passing Service Profile, NST and sub-net capabilities), resulting in OOF providing Slice Profiles (in callback API) for new NSI creation (Option 1). Note: In the RAN Slice Profile, coverageAreaTAList shall contain a valid list of TAs corresponding to the coverageArea provided by the user (and passed in the Service Profile by SO (NSMF) to OOF) - see Remarks. |
| | COMPLETED |
| | NSMF_ | 1 | This test case requires setup of CPS (including TBDMT manually). | NSMF_06 | Service instantiation (Option 1) - New NSI | SO (NSMF) presents the NSI solution to NSMF Portal (UUI) for manual intervention. NSMF Portal (UUI) provides endpoints for RAN and Core sub-nets while allowing creation of new NSI. | 1 | NSMF_07 | Service instantiation (Option 1) - New NSI | NSMF (SO) triggers RAN NSSMF with allocateNSSI operation via the NSSMF adaptor, and RAN NSSI is allocated successfully. | 1 | NSMF_08 | Service instantiation (Option 1) - New NSI | NSMF (SO) triggers Core NSSMF with allocateNSSI operation via the NSSMF adaptor, and Core NSSI is allocated successfully. | 1 | NSMF_09 | Service instantiation (Option 1) - New NSI | NSMF (SO) triggers TN NSSMF with allocateNSSI operation via the NSSMF adaptor along with the RAN & Core endpoint info, and TN NSSI is allocated successfully. | 1 | NSMF_10 | Service instantiation (Option 2) - New NSI | NSMF (SO) triggers OOF for NSI selection (passing Service Profile, NST and sub-net capabilities), resulting in OOF providing Slice Profiles (in callback API) for new NSI creation (Option 2). Note: In the RAN Slice Profile, coverageAreaTAList shall contain a valid list of TAs corresponding to the coverageArea provided by the user (and passed in the Service Profile by SO (NSMF) to OOF) - see Remarks. | 1 | 4 |
| | COMPLETEDThis test case requires setup of CPS (including TBDMT manually). |
|
| NSMF_11 | Service instantiation (Option 2) - New NSI | NSMF (SO) calls OOF using selectNSSI API for the RAN NSSI selection (in case of external RAN NSSMF) with RAN Slice Profile and RAN sub-net capabilities. OOF provides (empty) response that no RAN NSSI exists (that can be reused). | 1 |
| | DEFERRED | Option 2 regression testing is deferred to Istanbul4 |
| NSMF_12 | Service instantiation (Option 2) - New NSI | NSMF (SO) triggers External RAN NSSMF with allocateNSSI operation via the NSSMF adaptor (it also sends Slice Profile info), and new RAN NSSI is created successfully. RAN EP info is updated in AAI by NSMF Adaptor. | 1 |
| | DEFERRED | Option 2 regression testing is deferred to Istanbul4 |
| NSMF_13 | Service instantiation (Option 2) - New NSI | NSMF (SO) triggers (external) Core NSSMF with allocateNSSI operation via the NSSMF adaptor, and Core NSSI is allocated successfully. (This is more of a regression test case as new Core NSSI is already covered in COM_08) | 4 | 1 | | 1 |
| | DEFERRED | Option 2 regression testing is deferred to Istanbul |
| NSMF_14 | Service instantiation (Option 2) - New NSI | NSMF (SO) triggers TN NSSMF with allocateNSSI operation via the NSSMF adaptor along with the RAN & Core endpoint info, and TN NSSI is allocated successfully. (This is more of a regression test case as new TN NSSI is already covered in COM_09)4 | 1 | NSMF_16 | Service instantiation (Option 1) - New NSI | NSMF (SO) triggers RAN NSSMF with allocateNSSI operation via the NSSMF adaptor, and RAN NSSMF responds that an existing RAN NSSI can be reused. | 5 | 2 | NSMF_17 | Service instantiation (Option 1) - New NSI | NSMF (SO) triggers Core NSSMF with allocateNSSI operation via the NSSMF adaptor, and Core NSSMF responds that an existing Core NSSI can be reused. | 5 | 2 |
| | DEFERRED | Option 2 regression testing is deferred to Istanbul |
| NSMF_15NSMF_18 | Service instantiation (Option 2) - New NSI | NSMF (SO) calls OOF using selectNSSI API for the RAN NSSI selection (in case of external RAN NSSMF) with RAN Slice Profile and RAN sub-net capabilities. OOF provides response with a suitable RAN NSSI exists (that can be reused). | 1 |
| | DEFERRED | Option 2 testing is deferred to Istanbul |
| NSMF_16 | Service instantiation (Option 2) - New NSI | NSMF (SO) triggers External RAN NSSMF with modifyNSSI operation via the NSSMF adaptor (it also sends info of NSSI to be reused), and RAN NSSI is updated successfully. | RAN EP info is updated in AAI by NSMF Adaptor. | 1 |
| | DEFERRED | Option 2 testing is deferred to Istanbul | 6 | 2 |
| NSMF_1917 | Service instantiation (Option 1) - Reuse existing NSI | NSMF (SO) triggers OOF for NSI selection (passing Service Profile, NST and sub-net capabilities), resulting in OOF providing details of existing NSI to be reused in the response. | 7 | | 1 |
| | | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | COMPLETED |
|---|
|
|
|
| NSMF_2018 | Service instantiation (Option 1) - Reuse existing NSI | NSMF (SO) triggers OOF for obtaining Slice Profiles for the new Service Profile when an existing NSI is reused, and OOF provides the Slice Profiles | 7 | . | 1 |
| | | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | COMPLETED |
|---|
|
| A fix was provided in SO (NSMF) (SO-3629) which will officially be available on H-release-MNT.2 |
| NSMF_2119 | Service instantiation (Option 1) - Reuse existing NSI | NSMF (SO) provides details of existing NSI and Slice Profiles to UUI (NSMF Portal) for manual intervention. Existing NSI is chosen via UUI (regression) | 7 | | 1 |
| | | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | COMPLETED |
|---|
|
|
|
| NSMF_2220 | Service instantiation (Option 1) - Reuse existing NSI | NSMF then calls modifyNSSI API towards RAN, Core and Transport NSSMFs with details of existing NSI to be reused and the respective Slice Profile | 7 | | 1 |
| | | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | COMPLETED |
|---|
|
|
|
| NSMF_2321 | Service instantiation (Option 2) - Reuse existing NSI(similar to testcases COM_17 and 18) | NSMF (SO) triggers OOF for NSI selection (passing Service Profile, NST and sub-net capabilities), resulting in OOF providing existing NSI to be reused in the response. NSMF (SO) triggers OOF for obtaining Slice Profiles for the new Service Profile when an existing NSI is reused, and OOF provides the Slice Profiles.8 | 1 | 2 | NSMF_24 | Service instantiation (Option 1) - Reuse existing NSI | NSMF (SO) provides details of existing NSI and Slice Profiles to UUI (NSMF Portal) for manual intervention. Existing NSI is chosen via UUI (regression) | 8 | 2 |
| | DEFERRED | Option 2 testing is deferred to Istanbul |
| NSMF_22NSMF_25 | Service instantiation (Option 2) - Reuse existing NSI(similar to testcase COM_20) | NSMF then calls modifyNSSI API towards internal Core and Transport NSSMFs, and external RAN NSSMF with details of NSI to be reused and the respective Slice Profile | 1 |
| | 8DEFERRED | Option 2 testing is deferred to Istanbul |
| NSMF_2623 | Service activation (Option 1) | Service activation from CSMF portal (UUI) for Option 1/2 resulting in NSI Activation API called towards SO (NSMF). SO (NSMF) calls activateNSSI APIs towards RAN, Core and Transport NSSMFs | 1 |
| | 9 | DEFERRED | This regression testing is deferred to Istanbul2 |
| NSMF_2724 | Service activation (Option 2) | Service activation from CSMF portal (UUI) for Option 1/2 resulting in NSI Activation API called towards SO (NSMF). SO (NSMF) calls activateNSSI APIs towards internal Core and Transport NSSMFs, and external RAN NSSMF | 1 |
| | 9DEFERRED | Option 2 testing is deferred to Istanbul |
| NSMF_2825 | Service deactivation (Option 1) | Service deactivation from CSMF portal (UUI) for Option 1/2 resulting in NSI Deactivation API called towards SO (NSMF). SO (NSMF) calls DeactivateNSSI APIs towards RAN, Core and Transport NSSMFs | 1 |
| | 10 | DEFERRED | This regression testing is deferred to Istanbul2 |
| NSMF_2926 | Service deactivation (Option 2) | Service deactivation from CSMF portal (UUI) for Option 1/2 resulting in NSI Dectivation API called towards SO (NSMF). SO (NSMF) calls deactivateNSSI APIs towards internal Core and Transport NSSMFs, and external RAN NSSMF | 1 |
| | 10DEFERRED | Option 2 testing is deferred to Istanbul |
| NSMF_3027 | Service termination (Option 1/2) | Service termination from CSMF portal (UUI) for Option 1/2. SO (NSMF) triggers OOF to check for NSI termination, OOF returns NSI should not be terminated | 11 | 1 |
| | DEFERRED | Service termination testing is deferred to Istanbul as this also requires e2e testing2 |
| NSMF_3128 | Service termination (Option 1/2) | SO (NSMF) triggers RAN, Core and TN NSSMF with modifyNSSI API to remove S-NSSAI from the respective NSSIs. Service and Slice profiles and their links are also removed. | 11 | | 1 |
| | DEFERRED | Service termination testing is deferred to Istanbul as this also requires e2e testing2 |
| NSMF_3229 | Service termination (Option 1) | Service termination from CSMF portal (UUI) for Option 1/2. SO (NSMF) triggers OOF to check for NSI termination, OOF returns NSI should be terminated | 2 |
| | 12 | DEFERRED | Service termination testing is deferred to Istanbul as this also requires e2e testing2 |
| NSMF_3330 | Service termination (Option 1) | SO (NSMF) triggers RAN, Core and TN NSSMF with deallocateNSSI API. NSI is also removed by SO (NSMF). | 2 |
| | 12 | DEFERRED | Service termination testing is deferred to Istanbul as this also requires e2e testing2 |
