Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

S. No

Test Case

Description

Priority

Dependency/Issue

Tester

Status

Remarks

Test Details

1.Service/template design (Option1) Design of CST, and necessary templates: NST, NSST for RAN, RAN NF, Core & TN, Service Profile and Slice Profiles

1


Deepika S 

COMPLETED




2

Service Instantiation (Option1)

Reuse existing TN BH NSSI1At least 1 service needs to be instantiatedDeepika S 

COMPLETED

Pre-requisite: There is an existing TN BH NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way TN BH NSSI is reused, or creating a suitable and shareable TN BH NSSI upfront.

3

Service Termination (Option1)

Terminate a service - this should terminate NSI but terminate only Core NSSI and RAN NSSI, and not TN BH NSSI


1

Service instantiation test case involving reuse should be completed

IN PROGRESS

COMPLETED

This can happen  when only 1 Service Profile is linked to NSI and 1 Slice Profile each is linked to RAN & CORE NSSIs, but > 1 Slice Profile is linked to TN BH NSSI.

4Service Instantiation with CPS (Option1)Allocate a service - this should result in allocation of new NSI and associated new NSSIs.1
Deepika S 

COMPLETED

TBDMT templates should be preloaded

5Service reuse with CPS (Option1)Allocate a service - this should result in modifying the allocated NSI and associated NSSIs.1

COMPLETED

At least 1 service needs to be instantiated

6

Service Activation with CPS (Option1)

Activate a service - this should result in activation of new NSI and associated new NSSIs.

1

IN PROGRESS

At least 1 service needs to be instantiated

CN NSSMF - ActivateNSSI WF needs to be fixed.

Image AddedSO-3838 - Error while executing core NSSMF activate flow OPEN


7Service deactivation with CPS (Option1)Deactivate a service - this should result in deactivation of new NSI and associated new NSSIs.1

IN PROGRESS

At least 1 service needs to be instantiated

CN NSSMF - ActivateNSSI WF needs to be fixed.

Image AddedSO-3838 - Error while executing core NSSMF activate flow OPEN


8Service termination of a shared slice with CPS (Option1)

Terminate a service - this should terminate NSI but terminate only Core NSSI and TN BH NSSI, and not RAN NSSI. 

1

This can happen  when only 1 Service Profile is linked to NSI and 1 Slice Profile each is linked to Core & TN BH NSSIs, but > 1 Slice Profile is linked to RAN NSSI.




9Service termination with CPS (Option1)

Terminate a service - this should terminate NSI and ALL associated NSSIs.

1

At least 1 service needs to be instantiated

10Service activation (Option 2)Service activation from CSMF portal (UUI) resulting in NSI Activation API called towards SO (NSMF). SO (NSMF) calls activateNSSI APIs towards internal Core and Transport NSSMFs, and external RAN NSSMF1
Deepika S 
At least 1 service needs to be instantiated
11Service deactivation (Option 1)

Service deactivation from CSMF portal (UUI) resulting in NSI Deactivation API called towards SO (NSMF). SO (NSMF) calls DeactivateNSSI APIs towards internal Core and Transport NSSMFs, and external RAN NSSMF

1
Deepika S 
At least 1 service needs to be instantiated
12Service/template design (Option2)Design of CST, and necessary templates: NST, NSST for RAN, Core & TN, Service Profile and Slice Profiles1

Option2 - NSMF Driven TN Slices in Network Slicing

13

Service instantiation (Option 2) - 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.1At least 1 service needs to be instantiatedsravya sherla 



14Service instantiation (Option 2) - Reuse existing NSINSMF (SO) triggers OOF for obtaining Slice Profiles for the new Service Profile when an existing NSI is reused, and OOF provides the Slice Profiles.1At least 1 service needs to be instantiated



15Service instantiation (Option 2) - Reuse existing NSINSMF (SO) provides details of existing NSI and Slice Profiles to UUI (NSMF Portal) for manual intervention. Existing NSI is chosen via UUI (regression)1At least 1 service needs to be instantiatedsravya sherla 



16Service instantiation (Option 2) - 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

NOTE: This involves reuse of RAN NF NSSI, CORE NSSI, TN BH NSSI, TN FH NSSI and TN MH NSSI

1At least 1 service needs to be instantiatedsravya sherla 



17

Service instantiation (Option 2) - Reuse existing  TN BH NSSI

Reuse existing TN BH NSSI1
sravya sherla 
Pre-requisite: There is an existing TN BH NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way TN BH NSSI is reused, or creating a suitable and shareable TN BH NSSI upfront.

18Service instantiation (Option 2) - Reuse existing  TN MH NSSIReuse existing TN MH NSSI1
sravya sherla 
Pre-requisite: There is an existing TN MH NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way TN MH NSSI is reused, or creating a suitable and shareable TN MH NSSI upfront.

19Service instantiation (Option 2) - Reuse existing  TN FH NSSIReuse existing TN FH NSSI1
sravya sherla 
Pre-requisite: There is an existing TN FH NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way TN FH NSSI is reused, or creating a suitable and shareable TN FH NSSI upfront.

20Service activation (Option 2)

Service activation from CSMF portal (UUI) for Option 2 resulting in NSI Activation API called towards SO (NSMF). SO (NSMF) calls activateNSSI APIs towards internal Core and Transport NSSMFs, and internal RAN NSSMF

NOTE: This involves activation of RAN NF NSSI, CORE NSSI, TN BH NSSI, TN FH NSSI and TN MH NSSI

1At least 1 service needs to be instantiated



21Service deactivation (Option 2)

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

NOTE: This involves deactivation of RAN NF NSSI, CORE NSSI, TN BH NSSI, TN FH NSSI and TN MH NSSI

1At least 1 service needs to be activated



22Service Termination (Option2)

Service termination from CSMF portal (UUI) for Option 2. SO (NSMF) triggers OOF to check for NSI termination, OOF returns NSI should be terminated

1At least 1 service needs to be instantiatedsravya sherla 



23Service Termination (Option2)

SO (NSMF) triggers RAN, Core and TN NSSMF with deallocateNSSI API. NSI is also removed by SO (NSMF).

NOTE: This involves termination of RAN NF NSSI, CORE NSSI, TN BH NSSI, TN FH NSSI and TN MH NSSI

1At least 1 service needs to be instantiatedsravya sherla 



24

Service Termination (Option2)

Terminate a service - this should terminate NSI but terminate only Core NSSI and RAN NSSI, and not TN BH NSSI1
sravya sherla 
This can happen  when only 1 Service Profile is linked to NSI and 1 Slice Profile each is linked to RAN & CORE NSSIs, but > 1 Slice Profile is linked to TN BH NSSI.

25Service Termination (Option2)Terminate a service - this should terminate NSI but terminate only Core NSSI and RAN NSSI, and not TN MH NSSI1
sravya sherla 
This can happen  when only 1 Service Profile is linked to NSI and 1 Slice Profile each is linked to RAN & CORE NSSIs, but > 1 Slice Profile is linked to TN MH NSSI.

26Service Termination (Option2)Terminate a service - this should terminate NSI but terminate only Core NSSI and RAN NSSI, and not TN FH NSSI1
sravya sherla 
This can happen  when only 1 Service Profile is linked to NSI and 1 Slice Profile each is linked to RAN & CORE NSSIs, but > 1 Slice Profile is linked to TN FH NSSI.

...