Versions Compared

Key

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

The main list of test cases is available at E2E Network Slicing Use Case in R7 Guilin.

Important Note: Status update of test cases, prioritization and scenario-based reduction in testing scope is in progress. Majority of Priority 1

...

Venue: CMCC Lab

...

test cases alone will be targeted to be completed for Guilin. This page will be updated in the next few days with the proper status of completed/ongoing tests (the parts which are completed), and other relevant details.

Remark: We will continue to update the status as we continue the testing of various e2e scenario combinations, along with the P2 test cases beyond Guilin. Bugs found (if any) from now onwards will be solved in Honolulu.

1. Common CSMF, NSMF

Venue: CMCC Lab

S.No.CategoryTest Case DescriptionReference to main TCPriorityDependencyTesterStatus
COM_01Service/template designSuccessful design of CST and Service Profile Templates11
Zhang Min, He Tengjiao

Status
colourGreen
titleCompleted

COM_02Service/template designSuccessful design of NST (option 1 and option 2)21
Zhang Min, He Tengjiao

Status
colourGreen
titleCompleted

COM_03Service instantiationService 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.31COM_01, COM_02Zhang Min, He Tengjiao

Status
colourGreen
titleCompleted

COM_04Service 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.32COM_03Zhang Min, He Tengjiao

Status
colourYellow
titleIN PROGRESS

COM_05Service instantiation (Option 1) - New NSINSMF (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).32COM_04Zhang Min, He Tengjiao

Status
colourYellow
titleIN PROGRESS

COM_06Service instantiation (Option 1) - New NSISO (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.32COM_05Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_07Service instantiation (Option 1) - New NSINSMF (SO) triggers RAN NSSMF with allocateNSSI operation via the NSSMF adaptor, and RAN NSSI is allocated successfully.32COM_06Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_08Service instantiation (Option 1) - New NSINSMF (SO) triggers Core NSSMF with allocateNSSI operation via the NSSMF adaptor, and Core NSSI is allocated successfully.32COM_06Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_09Service instantiation (Option 1) - New NSINSMF (SO) triggers TN NSSMF with allocateNSSI operation via the NSSMF adaptor along with the RAN & Core endpoint info, and TN NSSI is allocated successfully.32COM_08Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_10Service instantiation (Option 2) - New NSIAfter NST selection, NSMF (SO) fetches sub-net capabilities for the 3 constituent sub-nets (RAN, Core and Transport) for Option 2.4
COM_03Zhang Min, He Tengjiao

Status
colourGreen
titleCompleted

COM_11Service instantiation (Option 2) - New NSINSMF (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).4
COM_10Zhang Min, He Tengjiao

Status
colourGreen
titleCompleted

COM_12Service instantiation (Option 2) - New NSINSMF (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).42COM_11Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_13Service instantiation (Option 2) - New NSINSMF (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.41COM_12Zhang Min, He Tengjiao

Status
colourGreen
titleCompleted

COM_14Service instantiation (Option 2) - New NSINSMF (SO) triggers 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)41COM_13Zhang Min, He Tengjiao

Status
colourYellow
titleIN PROGRESS

COM_15Service instantiation (Option 2) - New NSINSMF (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)41COM_14Zhang Min, He Tengjiao

Status
colourYellow
titleIN PROGRESS

COM_16Service instantiation (Option 1) - New NSINSMF (SO) triggers RAN NSSMF with allocateNSSI operation via the NSSMF adaptor, and RAN NSSMF responds that an existing RAN NSSI can be reused.52COM_11Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_17Service instantiation (Option 1) - New NSINSMF (SO) triggers Core NSSMF with allocateNSSI operation via the NSSMF adaptor, and Core NSSMF responds that an existing Core NSSI can be reused.52COM_11Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_16Service instantiation (Option 2) - New NSINSMF (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).62COM_11Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_17Service instantiation (Option 1) - Reuse existing NSINSMF (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.72COM_04Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_18Service instantiation (Option 1) - 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 Profiles72COM_17Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_19Service instantiation (Option 1) - 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)72COM_18Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_20Service instantiation (Option 1) - Reuse existing NSINSMF then calls modifyNSSI API towards RAN, Core and Transport NSSMFs with details of existing NSI to be reused and the respective Slice Profile72COM_19Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_21

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.82COM_04Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_22Service instantiation (Option 1) - 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)82COM_21Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_23

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 Profile82COM_22Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_24Service 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

92COM_09 or COM_20Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_25Service 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 NSSMF92COM_15 or COM_23Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_26Service 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

102COM_24Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_27Service 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 NSSMF102COM_25Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_28Service 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 terminated112COM_24 or COM_25Priyadharshini, Reshmasree

Status
titleNot yet tested

COM_29Service 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.112COM_28Priyadharshini, Reshmasree

Status
titleNot yet tested

COM_30Service 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 terminated122COM_24 or COM_25Priyadharshini, Reshmasree

Status
titleNot yet tested

COM_31Service termination (Option 1)SO (NSMF) triggers RAN, Core and TN NSSMF with deallocateNSSI API. NSI is also removed by SO(NSMF).122COM_30Priyadharshini,  Reshmasree

Status
titleNot yet tested

COM_32Service instantiation via ExtAPIService instantiation via ExtAPI for Option 1/2 resulting in new NSI to be created131COM_05 or COM_11Priyadharshini

Status
colourGreen
titleCOMPLETED

COM_33Service instantiation via ExtAPIService instantiation via ExtAPI for Option 1/2 resulting in existing NSI to be reused142COM_17 or COM_21Priyadharshini

Status
colourYellow
titleIN PROGRESS

COM_34Service activation via ExtAPIService activation via ExtAPI for Option 1/2 resulting in slice service activation152COM_24 or COM_25Priyadharshini

Status
colourGreen
titleCOMPLETED

COM_35Service deactivation via ExtAPIService deactivation via ExtAPI for Option 1/2 resulting in slice service deactivation162COM_34Priyadharshini

Status
colourYellow
titleIN PROGRESS

COM_36Service termination via ExtAPIService deallocation via ExtAPI for Option 1/2 resulting in NSI not being terminated. S-NSSAI, Service and Slice profiles and their links are removed from NSI/respective NSSIs.172COM_29Priyadharshini

Status
colourYellow
titleIN PROGRESS


Note: KPI Monitoring, Closed Loop and Intelligent Slicing test cases are covered in separate sections below.


2. RAN Slicing

Venue: Winlab (Rutgers University)

S.No.CategoryTest Case DescriptionReference to main TCPriorityDependencyTesterStatus
RAN_01Service/template designSuccessful design of RAN NSST, RAN NF NSST, RAN Slice Profile and RAN NF Slice Profile Templates21
Borislav

Status
colourGreen
titleCOMPLETED

RAN_02Service instantiation (Option 1) - New NSI, new RAN NSSIProvide RAN subnet capabilities when queried by NSSMF adaptor31
Reshmasree, Priyadharshini

Status
colourGreen
titleCOMPLETED

RAN_03Service instantiation (Option 1) - New NSI, new RAN NSSIWhen triggered by NSSMF Adaptor with allocateNSSI for allocating a new RAN NSSI, RAN NSSMF (SO) triggers OOF for RAN NSSI selection, OOF provides Slice Profiles for RAN NF, TN FH and TN MH NSSIs (i.e., creation of a new RAN NSSI).31COM_07Reshmasree, Priyadharshini

Status
colourGreen
titleCOMPLETED

RAN_04Service instantiation (Option 1) - New NSI, new RAN NSSISO (RAN NSSMF) creates new RAN NF NSSI and configuring it by calling SDN-R. AAI is also updated with relevant Slice Profile info.31RAN_03Reshmasree, Priyadharshini

Status
colourBlue
titlePartially COMPLETED

Depends on completion of RAN_06

RAN_05Service instantiation (Option 1) - New NSI, new RAN NSSISDN-R updates Config DB with the details of the new RAN NSSI and S-NSSAI and other configuration details (e.g., RRM Policy, Slice Profile) for the new S-NSSAI32RAN_04Sandeep Shah, Ahila

Status
titleNot yet tested

COM
RAN_
04
06Service 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.3COM_03Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_05
- New NSI, new RAN NSSISDN-R configures RAN NFs (CUs, DUs, Near-RT RICs) with the info related to the new RAN NSSI/S-NSSAI (by sending suitable (netconf) messages to RAN-Sim) and updates SO of the completion.32RAN_04Sandeep Shah, Ahila

Status
colourYellow
titleIn Progress

RAN_07Service instantiation (Option 1) -
New
 New NSI, new RAN NSSI
NSMF
SO (RAN NSSMF) triggers SO (TN NSSMF)
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).3COM_04Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_06
for allocation of FH and MH NSSIs. It passes the respective Slice Profiles (determined by OOF), and static values of endpoints for FH and MH to TN NSSMF.32RAN_06Reshmasree, Priyadharshini

Status
colourGreen
titleCOMPLETED

RAN_08Service instantiation (Option 1) -
New
 New NSI, new RAN NSSISO (
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
RAN NSSMF) makes suitable updates to AAI about Slice Profiles, RAN NF NSSI, etc.3
COM
2RAN_
05
07
Zhang Min
Reshmasree,
He Tengjiao
Priyadharshini

Status
colourGreen
title

Not yet tested

COMPLETED

COM
RAN_
07
09Service instantiation (Option 1) -
New
 New NSI
NSMF (SO) triggers RAN NSSMF with allocateNSSI operation via the NSSMF adaptor, and RAN NSSI is allocated successfully.3COM_06Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_08
, new RAN NSSIUpon reception of completion indication from TN NSSMF (for FH and MH subnets), SO (RAN NSSMF) informs NSSMF Adaptor of SO about completion of RAN NSSI creation32RAN_07Reshmasree, Priyadharshini

Status
colourBlue
titlePARTIALLY COMPLETED

RAN_10Service instantiation (Option 1) -
New
 New NSI
NSMF (SO) triggers Core NSSMF with allocateNSSI operation via the NSSMF adaptor, and Core NSSI is allocated successfully.3COM_06Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_09
, reuse RAN NSSIWhen triggered by NSSMF Adaptor with allocateNSSI for allocating a new RAN NSSI, SO (RAN NSSMF) triggers OOF for RAN NSSI selection, OOF provides existing RAN NSSI (i.e., reuse of an existing RAN NSSI).52COM_07Reshmasree, Priyadharshini

Status
colourYellow
titleIN PROGRESS

RAN_11Service instantiation (Option 1) -
New
 New NSI, reuse RAN NSSI
NSMF
SO (
SO) triggers TN NSSMF with allocateNSSI operation via the NSSMF adaptor along with the RAN & Core endpoint info, and TN NSSI is allocated successfully.3COM_08Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_10
RAN NSSMF) calls OOF a second time for obtaining the Slice Profiles for RAN NF NSSI, TN FH and MH NSSIs. Slice Profile details are then updated in AAI.52RAN_10Reshmasree, Priyadharshini

Status
colourYellow
titleIN PROGRESS

RAN_12Service instantiation (Option
2
1) -
New
 New NSI
After NST selection, NSMF (SO) fetches sub-net capabilities for the 3 constituent sub-nets (RAN, Core and Transport) for Option 2.4COM_03Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_11
, reuse RAN NSSISO (RAN NSSMF) calls SDN-R for configuring the existing RAN NF NSSI (reuse) with the new S-NSSAI and Slice Profile52RAN_11Reshmasree, Priyadharshini

Status
colourYellow
titleIN PROGRESS

RAN_13Service instantiation (Option
2
1) -
New
 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).4COM_10Zhang Min, He Tengjiao
, reuse RAN NSSISDN-R updates Config DB with the details of the RAN NSSI and S-NSSAI and other configuration details (e.g., RRM Policy, Slice Profile) for the new S-NSSAI52RAN_12Sandeep Shah, Ahila

Status
titleNot yet tested

COM
RAN_
12
14Service instantiation (Option
2
1) -
New NSINSMF (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).4COM_11Zhang Min, He Tengjiao
 New NSI, reuse RAN NSSISDN-R sends relevant (netconf) messages to RAN-Sim for updating the RAN NFs (CUs, DUs, Near-RT RICs) with details of the new S-NSSAI, RRM Policy updates, Slice Profile, etc.52RAN_13Sandeep Shah, Ahila

Status
titleNot yet tested

COM
RAN_
13
15Service instantiation (Option
2
1) -
New
 New NSI, reuse RAN NSSI
NSMF
SO (RAN NSSMF) calls 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.4COM_12Zhang Min, He Tengjiao
(TN NSSMF) for configuring the existing TN FH/MH NSSIs (reuse) with the new S-NSSAI and respective Slice Profiles using modifyNSSI API.52RAN_12Reshmasree, Priyadharshini

Status
titleNot yet tested

COM
RAN_
14
16Service
instantiation 
instantiation (Option
2
1) -
New COM_15Service instantiation (Option 2) - New NSINSMF (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)4COM_14Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_16Service instantiation (Option 1) - New NSINSMF (SO) triggers RAN NSSMF with allocateNSSI operation via the NSSMF adaptor, and RAN NSSMF responds that an existing RAN NSSI can be reused.5COM_11Zhang Min, He Tengjiao
Reuse existing NSI
NSMF (SO) triggers 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)4COM_13Zhang Min, He Tengjiao

Status
titleNot yet tested

When triggered by NSSMF Adaptor with modifyNSSI for reusing an existing NSI, SO (RAN NSSMF) triggers OOF for obtaining the Slice Profiles of RAN NF, TN FH and TN MH subnets for updating the respective NSSIs. Slice Profile details are then updated in AAI.

(Remaining flows are similar to test cases RAN_12 to RAN_15)

72COM_20Reshmasree, Priyadharshini

Status
colourYellow
titleIN PROGRESS

RAN_17Service activation (Option 1)When triggered by NSSMF Adaptor with activateNSSI for activating the RAN NSSI, SO (RAN NSSMF) triggers SDN-R for activating the S-NSSAI in the RAN NFs.91COM_24Reshmasree, Priyadharshini

Status
colourGreen
titleCompleted

RAN_18Service activation (Option 1)SDN-R sends relevant (netconf) messages to RAN NFs (RAN-Sim) (CUs, DUs, Near-RT RICs) for activation of the S-NSSAI.92RAN_17Sandeep Shah, Ahila

Status
titleNot yet tested

COM
RAN_
17
19Service
instantiation 
activation (Option 1)
- New NSI
NSMF
SO (
SO
RAN NSSMF) triggers
Core NSSMF with allocateNSSI operation via the NSSMF adaptor, and Core NSSMF responds that an existing Core NSSI can be reused.5COM_11Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_16Service instantiation (Option 2) - New NSINSMF (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).6COM_11Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_17Service instantiation (Option 1) - Reuse existing NSINSMF (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.7COM_04Zhang Min, He Tengjiao
SO (TN NSSMF) for activating the TN FH and TN MH NSSIs.91RAN_17Reshmasree, Priyadharshini

Status
colourYellow
titleIn Progress

RAN_20Service deactivation (Option 1)When triggered by NSSMF Adaptor with deactivateNSSI for deactivating the RAN NSSI, SO (RAN NSSMF) triggers SDN-R for deactivating the S-NSSAI in the RAN NFs.102COM_25Reshmasree, Priyadharshini

Status
colourGreen
titleCOMPLETED

RAN_21Service deactivation (Option 1)SDN-R sends relevant (netconf) messages to RAN NFs (RAN-Sim) (CUs, DUs, Near-RT RICs) for deactivation of the S-NSSAI.102RAN_20Sandeep Shah, Ahila

Status
titleNot yet tested

COM
RAN_
18
22Service
instantiation
deactivation (Option
1) - 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 Profiles7COM_17Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_19Service instantiation (Option 1) - 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)7COM_18Zhang Min, He Tengjiao

Status
titleNot yet tested

COM_20Service instantiation (Option 1) - Reuse existing NSINSMF then calls modifyNSSI API towards RAN, Core and Transport NSSMFs with details of existing NSI to be reused and the respective Slice Profile7COM_19Zhang Min, He Tengjiao
1)SO (RAN NSSMF) triggers SO (TN NSSMF) for deactivating the TN FH and TN MH NSSIs.102RAN_20Reshmasree, Priyadharshini

Status
colourYellow
titleIN PROGRESS

RAN_23Service termination (Option 1)When triggered by NSSMF Adaptor with modifyNSSI for removing S-NSSAI, SO (RAN NSSMF) triggers SDN-R for removing the S-NSSAI in the RAN NFs. Slice Profile of RAN NF NSSI is also removed.112COM_29Reshmasree, Priyadharshini

Status
colourYellow
titleIN PROGRESS

RAN_24Service termination (Option 1)SDN-R makes relevant updates to ConfigDB (removal of S-NSSAI and RAN NF Slice Profile, RRM Policy update)112RAN_23Sandeep Shah, Ahila

Status
titleNot yet tested

COM
RAN_
21
25Service
instantiation
termination (Option
2
1)
- 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.8COM_04Zhang Min, He Tengjiao
SDN-R sends relevant (netconf) messages to RAN-NFs (CUs, DUs, Near-RT RICs) of S-NSSAI removal, and update of RRM Policy, etc.112RAN_24Sandeep Shah, Ahila

Status
titleNot yet tested

COM
RAN_
22
26Service
instantiation
termination (Option 1)
- Reuse existing NSI
NSMF
SO (RAN NSSMF) triggers SO
) provides details of existing NSI and Slice Profiles to UUI (NSMF Portal) for manual intervention. Existing NSI is chosen via UUI (regression)8COM_21Zhang Min, He TengjiaoZhang Min, He Tengjiao
(TN NSSMF) for updating the TN FH and TN MH NSSIs. Slice Profiles of TN FH and MH NSSIs are also removed.112RAN_23Reshmasree, Priyadharshini

Status
titleNot yet tested

COM_23

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 Profile8COM_22
RAN_27Service termination (Option 1)

When triggered by NSSMF Adaptor with deallocateNSSI API, SO (RAN NSSMF) calls OOF to determine if RAN NSSI has to be terminated. OOF returns RAN NSSI should not be terminated. (Remaining steps are the same as in test cases RAN_23 to RAN_26)

122COM_30Reshmasree, Priyadharshini

Status
titleNot yet tested

COM
RAN_
24
28Service
activation Zhang Min, He Tengjiao
termination (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

9COM_09 or COM_20
When triggered by NSSMF Adaptor with deallocateNSSI API, SO (RAN NSSMF) calls OOF to determine if RAN NSSI has to be terminated. OOF returns RAN NSSI should be terminated.122COM_30Reshmasree, Priyadharshini

Status
titleNot yet tested

COM
RAN_
25
29Service
activation 
termination (Option
2
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 internal Core and Transport NSSMFs, and external RAN NSSMF9COM_15 or COM_23Zhang Min, He Tengjiao
RAN NSSMF) calls OOF to determine if RAN NF NSSI has to be terminated. OOF returns that RAN NF NSSI should be terminated.122RAN_28Reshmasree, Priyadharshini

Status
titleNot yet tested

COM
RAN_
26
30Service
deactivation Zhang Min, He Tengjiao
termination (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

10COM_24

SO (RAN NSSMF) triggers SDN-R for removing the S-NSSAI in the RAN NFs. Slice Profile of RAN NF NSSI and RAN NF NSSI are also removed.

(SDN-R actions are covered in test cases RAN_24 and RAN_25)

122RAN_29Reshmasree, Priyadharshini

Status
titleNot yet tested

COM
RAN_
27
30Service
deactivation 
termination (Option
2for Option 1/2 resulting in NSI Dectivation API called towards
1)
Service deactivation from CSMF portal (UUI)
SO (
NSMF
RAN NSSMF)
.
triggers SO (
NSMF) calls deactivateNSSI APIs towards internal Core and Transport NSSMFs, and external RAN NSSMF10COM_25Zhang Min, He Tengjiao
TN NSSMF) with deallocateNSSI API call for deallocation of TN FH and TN MH NSSIs122RAN_29Reshmasree, Priyadharshini

Status
titleNot yet tested

COM
RAN_
28
31Service 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 terminated11COM_24 or COM_25Priyadharshini, Reshmasree
)

When OOF returns that RAN NSSI should be terminated, SO (RAN NSSMF) calls OOF to determine if RAN NF NSSI has to be terminated. OOF returns that RAN NF NSSI should not be terminated.

(RAN NF NSSI update actions are covered by RAN_23 to RAN_25, and TN FH and MH NSSI actions are covered by RAN_30)

122RAN_28Reshmasree, Priyadharshini

Status
titleNot yet tested

COM_29Service 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.11COM_28Priyadharshini, Reshmasree

Status
titleNot yet tested

COM_30Service 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 terminated12COM_24 or COM_25Priyadharshini, Reshmasree

Status
titleNot yet tested

COM_31Service termination (Option 1)SO (NSMF) triggers RAN, Core and TN NSSMF with deallocateNSSI API. NSI is also removed by SO(NSMF).12COM_30Priyadharshini,  Reshmasree

Status
titleNot yet tested

COM_32Service instantiation via ExtAPIService instantiation via ExtAPI for Option 1/2 resulting in new NSI to be created13COM_05 or COM_11Priyadharshini

Status
titleNot yet tested

COM_33Service instantiation via ExtAPIService instantiation via ExtAPI for Option 1/2 resulting in existing NSI to be reused14COM_17 or COM_21Priyadharshini

Status
titleNot yet tested

COM_34Service activation via ExtAPIService activation via ExtAPI for Option 1/2 resulting in slice service activation15COM_24 or COM_25Priyadharshini

Status
titleNot yet tested

COM_35Service deactivation via ExtAPIService deactivation via ExtAPI for Option 1/2 resulting in slice service deactivation16COM_34Priyadharshini

3. Core Slicing

Venue: Windriver

S.No.CategoryTest Case DescriptionReference to main TCPriorityDependencyTesterStatus
CORE_01Service/template designSuccessful design of Core NSST, Core NF NSST, Core Slice Profile and Core Network Service21
Sanchita, Aleem

Status
colourGreen
titleCOMPLETED

CORE_02Service instantiationWhen triggered by NSSMF Adaptor with allocateNSSI for allocating a new Core NSSI, Core NSSMF (SO) triggers OOF for Core NSSI selection, OOF provides Slice Profiles for Core NF.31COM_07Sanchita, Aleem

Status
colourYellow
titleIn pROGRESS

CORE_03Service instantiation (New NSSI)SO (Core NSSMF) creates new Core NSSI in AAI32
Sanchita, Aleem

Status
colourGreen
titleCOMPLETED



Prepare Service order and trigger EXTAPI for instantiating new Core  NFs3

Sanchita, Aleem

Status
colourGreen
titleCOMPLETED



On successful response from EXTAPI for the serviceOrderId associate instantiated core network service to NSSI. And update SO database with service operation status3

Sanchita, Aleem

Status
colourGreen
titleCOMPLETED

CORE_04Service instantiation (Existing NSSI)When triggered by NSSMF Adaptor with allocateNSSI for allocating a new Core NSSI, Core NSSMF (SO) triggers OOF for Core NSSI selection, OOF provides Slice Profiles for Core NF.32COM_18Sanchita, Aleem

Status
titleNot yet tested



OOF returns existing NSSI. Find the associated network service with NSSI5

Sanchita, Aleem

Status
titleNot yet tested

COM_36Service termination via ExtAPIService deactivation via ExtAPI for Option 1/2 resulting in NSI not being terminated. S-NSSAI, Service and Slice profiles and their links are removed from NSI/respective NSSIs.17COM_29Priyadharshini

Status
titleNot yet tested

Note: KPI Monitoring, Closed Loop and Intelligent Slicing test cases are covered in separate sections below.

...



Venue: Winlab (Rutgers University)

...

Status
titleNot yet tested

...

Status
titleNot yet tested

...

Status
titleNot yet tested

...

Status
titleNot yet tested

...

4. Transport Slicing

Venue: CMCC Lab

S.No.Test Case DescriptionReference to main TCDependencyTesterStatusTN_01Service/template designSuccessful design of TN NSSTs (for FH, MH and BH), TN Slice Profile templates for FH, MH and BH2Chuyi StatuscolourYellowtitleIN PRoGRESSTN_02Service instantiation (Option 1) - New NSI, new TN NSSIProvide TN subnet capabilities when queried by NSSMF adaptor3Henry, Hesham

Status
titleNot yet tested

TN_03Service instantiation (Option 1) - New NSI, new TN NSSIWhen triggered by NSSMF Adaptor with allocateNSSI for allocating a new TN NSSI for BH, TN NSSMF (SO) triggers OOF for TN BH NSSI selection, OOF provides Slice Profile for TN BH NSSIs (i.e., creation of a new TN NSSI).3COM_07Henry, Hesham

Status
titleNot yet tested

TN_04Service instantiation (Option 1) - New NSI, new TN NSSISO (RAN NSSMF) creates new TN BH NSSI and configuring it by calling SDN-C3TN_03Henry, Hesham

Status
titleNot yet tested

TN_05Service instantiation (Option 1) - New NSI, new TN NSSISDN-C calls the Domain controller for performing necessary configuration and informs SO of the completion3TN_04Henry, Hesham

Status
titleNot yet tested

TN_06Service instantiation (Option 1) - New NSI, new TN NSSIWhen triggered by RAN NSSMF with allocateNSSI for allocating a new TN NSSI for FH/MH, TN NSSMF (SO) triggers OOF for TN FH/MH NSSI selection, OOF provides Slice Profile for TN FH/MH NSSIs (i.e., creation of a new TN NSSI).3COM_07Henry, Hesham

Status
titleNot yet tested

TN_07Service instantiation (Option 1) - New NSI, new TN NSSISO (RAN NSSMF) creates new TN BH NSSI and configuring it by calling SDN-C3TN_06Henry, Hesham

Status
titleNot yet tested

TN_08Service instantiation (Option 1) - New NSI, new TN NSSISDN-C calls the Domain controller for performing necessary configuration and informs SO of the completion3TN_07Henry, Hesham StatustitleNot yet tested allocateNSSI for allocating a new RAN NSSI, RAN NSSMF (SO) triggers OOF for RAN NSSI selection, OOF provides Slice Profiles for RAN NF, TN FH and TN MH NSSIs (i.e., creation of a new RAN NSSI).
S.No.CategoryTest Case DescriptionReference to main TCDependencyTesterStatus
RAN_01Service/template designSuccessful design of RAN NSST, RAN NF NSST, RAN Slice Profile and RAN NF Slice Profile Templates2Borislav
Status
colourYellow
titleIN PRoGRESS
RAN_02Service instantiation (Option 1) - New NSI, new RAN NSSIProvide RAN subnet capabilities when queried by NSSMF adaptor3Reshmasree, Priyadharshini

Status
titleNot yet tested

RAN_03Service instantiation (Option 1) - New NSI, new RAN NSSIPrepare request payload to trigger SO macro flow to update the Core network service NFs5

Sanchita, Aleem

Status
colourGreen
titleCOMPLETED



Trigger SO macro flow (by calling serviceInstance api PUT method).5

Sanchita, Aleem

Status
colourGreen
titleCOMPLETED



On successful response update the SO database with service operation status5

Sanchita, Aleem

Status
colourYellow
titleIn pROGRESS

CORE_05Service Activation and Service DeactivateWhen triggered by NSSMF Adaptor with activateNSSI or deactivateNSSI for activating/deactivating Core NSSI

7,8

2COM_24, COM_26Sanchita, Aleem

Status
colourYellow
titleIn pROGRESS



Get all s-nssai and orchestration status from slice profiles associated with NSSI7.8

Sanchita, Aleem


Get VNF/VFs associated with NSSI. Prepare request payload to trigger SO macro service to activate/deactivate the status of s-nssai received from NSSMF adapter7.8

Sanchita, Aleem


Onsuccessful response update slice profile instance in AAI7.8

Sanchita, Aleem
CORE_06Service DeallocateWhen triggered by NSSMF Adaptor with 3COM_07Reshmasree, PriyadharshinideAllocate for deallocating Core NSSI9, 10, 152COM_29, COM_31Alexander BorovitzkyRAN_05Service instantiation (Option 1) - New NSI, new RAN NSSISDN-R updates Config DB with the details of the new RAN NSSI and S-NSSAI and other configuration details (e.g., RRM Policy, Slice Profile) for the new S-NSSAI3RAN_04Sandeep Shah, Ahila

Status
titleNot yet tested

RAN_04Service instantiation (Option 1) - New NSI, new RAN NSSISO (RAN NSSMF) creates new RAN NF NSSI and configuring it by calling SDN-R3RAN_03Reshmasree, Priyadharshini

Status
titleNot yet tested



Get the network service instance and slice profile associated with NSSI


Alexander Borovitzky


If TerminateNSSI=true then 


Alexander Borovitzky


trigger EXPAPI to delete network service instance
Remove NSSI association with NSI
Remove association of  slice profile instance with NSSI
Delete the slice profile instance
Delete NSSI service instance



Alexander Borovitzky


Update SO database with operation status


Alexander Borovitzky
CORE_07Service DeallocateWhen triggered by NSSMF Adaptor with deAllocate for deallocating Core NSSI92COM_29, COM_31Alexander BorovitzkyRAN_07Service instantiation (Option 1) - New NSI, new RAN NSSISO (RAN NSSMF) triggers SO (TN NSSMF) for allocation of FH and MH NSSIs. It passes the respective Slice Profiles (determined by OOF), and static values of endpoints for FH and MH to TN NSSMF.3RAN_06Reshmasree, Priyadharshini

Status
titleNot yet tested

RAN_06Service instantiation (Option 1) - New NSI, new RAN NSSISDN-R configures RAN NFs (CUs, DUs, Near-RT RICs) with the info related to the new RAN NSSI/S-NSSAI (by sending suitable messages to RAN-Sim) and updates SO of the completion.3RAN_04Sandeep Shah, Ahila

Status
titleNot yet tested



Get the network service instance and slice profile associated with NSSI


Alexander Borovitzky


If TerminateNSSI=false then  


Alexander Borovitzky


Get VNF/VFs associated with NSSI. Get all the s-nssai  and orchestration status from the slice profiles associated with NSSI


Alexander Borovitzky


Prepare request payload to trigger SO macro flow to update the Core network service NFs


Alexander Borovitzky


Remove NSSI association with NSI
Remove association of  slice profile instance with NSSI
Delete the slice profile instance



Alexander Borovitzky


Update SO database with operation status


Alexander Borovitzky
CORE_08Service Modify (create new slice profile instance)When triggered by NSSMF Adaptor with modify for modifying Core NSSI11, 142COM_28Alexander Borovitzky

Status
titleNot yet tested

RAN_08Service instantiation (Option 1) - New NSI, new RAN NSSISO (RAN NSSMF) makes suitable updates to AAI about Slice Profiles, RAN NF NSSI, etc.3RAN_07Reshmasree, Priyadharshini

Status
titleNot yet tested

RAN_09Service instantiation (Option 1) - New NSI, new RAN NSSIUpon reception of completion indication from TN NSSMF (for FH and MH subnets), SO (RAN NSSMF) informs NSSMF Adaptor of SO about completion of RAN NSSI creation3RAN_07Reshmasree, Priyadharshini

Status
titleNot yet tested



RAN_10Service instantiation (Option 1) - New NSI, reuse RAN NSSIGet the network service instance and slice profile associated with NSSI


Alexander Borovitzky


Get VNF/VFs associated with NSSI. Get all the s-nssai  and orchestration status from the slice profiles associated with NSSI


Alexander Borovitzky


Prepare request payload to trigger SO macro flow to update the Core network service NFs


Alexander Borovitzky


On success response, create slice profile instance in AAI
Associate slice profile instance with NSSI



Alexander Borovitzky


Update SO database with operation status


Alexander Borovitzky
CORE_09Service Modify (delete slice profile instance)When triggered by NSSMF Adaptor with allocateNSSI for allocating a new RAN NSSI, SO (RAN NSSMF) triggers OOF for RAN NSSI selection, OOF provides existing RAN NSSI (i.e., reuse of an existing RAN NSSI).5COM_07Reshmasree, Priyadharshinimodify for modifying Core NSSI
2
Alexander Borovitzky

Status
titleNot yet tested

RAN_11Service instantiation (Option 1) - New NSI, reuse RAN NSSISO (RAN NSSMF) calls OOF a second time for obtaining the Slice Profiles for RAN NF NSSI, TN FH and MH NSSIs.5RAN_10Reshmasree, Priyadharshini

Status
titleNot yet tested

RAN_12Service instantiation (Option 1) - New NSI, reuse RAN NSSISO (RAN NSSMF) calls SDN-R for configuring the existing RAN NF NSSI (reuse) with the new S-NSSAI and Slice Profile5RAN_11Reshmasree, Priyadharshini

Status
titleNot yet tested

RAN_13Service instantiation (Option 1) - New NSI, reuse RAN NSSISDN-R updates Config DB with the details of the RAN NSSI and S-NSSAI and other configuration details (e.g., RRM Policy, Slice Profile) for the new S-NSSAI5RAN_12Sandeep Shah, Ahila

Status
titleNot yet tested

RAN_14Service instantiation (Option 1) - New NSI, reuse RAN NSSISDN-R sends relevant messages to RAN-Sim for updating the RAN NFs (CUs, DUs, Near-RT RICs) with details of the new S-NSSAI, RRM Policy updates, Slice Profile, etc.5RAN_13Sandeep Shah, Ahila

Status
titleNot yet tested

RAN_15Service instantiation (Option 1) - New NSI, reuse RAN NSSISO (RAN NSSMF) calls SO (TN NSSMF) for configuring the existing TN FH/MH NSSIs (reuse) with the new S-NSSAI and respective Slice Profiles5RAN_12Reshmasree, Priyadharshini

Status
titleNot yet tested

RAN_16Service instantiation (Option 1) - Reuse existing NSIWhen triggered by NSSMF Adaptor with modifyNSSI for reusing an existing NSI, SO (RAN NSSMF) triggers OOF for obtaining the Slice Profiles of RAN NF, TN FH and TN MH subnets for updating the respective NSSIs.7COM_20Reshmasree, Priyadharshini

Status
titleNot yet tested

3. Core Slicing

Venue: ???

...

Status
titleNot yet tested

...

Status
titleNot yet tested

...

Status
titleNot yet tested

...

Status
titleNot yet tested

...

Status
titleNot yet tested

...

7,8

...

Status
titleNot yet tested

...



Get the network service instance and slice profile associated with NSSI


Alexander Borovitzky


Get VNF/VFs associated with NSSI. Get all the s-nssai  and orchestration status from the slice profiles associated with NSSI


Alexander Borovitzky


Prepare request payload to trigger SO macro flow to update the Core network service NFs


Alexander Borovitzky


On success response, remove NSSI to slice profile association
Delete the slice profile instance



Alexander Borovitzky


Update SO database with operation status


Alexander Borovitzky

4. Transport Slicing

Venue: CMCC Lab

S.No.CategoryTest Case DescriptionReference to main TCPriorityDependencyTesterStatus
TN_01Service/template designSuccessful design of TN NSSTs (for FH, MH and BH), TN Slice Profile templates for FH, MH and BH21
Chuyi

Status
colourGreen
titleCompleted

TN_02Service instantiation (Option 1/2) - New NSI, new TN NSSIProvide TN subnet capabilities when queried by NSSMF adaptor3, 41
Henry, Hesham

Status
colourGreen
titleCompleted

TN_03Service instantiation (Option 1/2) - New NSI, new TN NSSIWhen triggered by NSSMF Adaptor with allocateNSSI for allocating a new TN NSSI for BH, TN NSSMF (SO) triggers OOF for TN BH NSSI selection, OOF provides Slice Profile for TN BH NSSIs (i.e., creation of a new TN NSSI).3, 42COM_07Henry, Hesham

Status
colourBlue
titlenot started

TN_04Service instantiation (Option 1/2) - New NSI, new TN NSSISO (RAN NSSMF) creates new TN BH NSSI and configuring it by calling SDN-C3, 41TN_03Henry, Hesham

Status
colourGreen
titleCompleted

TN_05Service instantiation (Option 1/2) - New NSI, new TN NSSI (BH)SDN-C calls the Domain controller for performing necessary configuration and informs SO of the completion3, 41TN_04Henry, Hesham

Status
colourGreen
titlecompleted

TN_06Service instantiation (Option 1) - New NSI, new TN NSSI (FH/MH)When triggered by RAN NSSMF with allocateNSSI for allocating a new TN NSSI for FH/MH, TN NSSMF (SO) triggers OOF for TN FH/MH NSSI selection, OOF provides Slice Profile for TN FH/MH NSSIs (i.e., creation of a new TN NSSI).32COM_07Henry, Hesham

Status
titleNot yet tested

TN_07Service instantiation (Option 1) - New NSI, new TN NSSI (FH/MH)SO (TN NSSMF) creates new TN FH/MH NSSI and configuring it by calling SDN-C31TN_06Henry, Hesham

Status
colourGreen
titlecompleted

TN_08Service instantiation (Option 1) - New NSI, new TN NSSI (FH/MH)SDN-C calls the Domain controller for performing necessary configuration and informs SO of the completion31TN_07Henry, Hesham

Status
colourGreen
titlecompleted

TN_09

Service instantiation (Option 1) - New NSI, reuse existing RAN NSSI (=> configuration update of TN NSSI (FH/MH))

AND

Service instantiation (Option 1) - Reuse existing NSI

When triggered from RAN NSSMF with modifyNSSI API for the FH/MH, SO (TN NSSMF) calls SDN-C to update the new S-NSSAI info, etc.5, 72RAN_15Henry, Hesham

Status
colourBlue
titleNot yet tested

TN_10

Service instantiation (Option 1) - New NSI, reuse existing RAN NSSI (=> configuration update of TN NSSI (FH/MH))

AND

Service instantiation (Option 1) - Reuse existing NSI

SDN-C calls the Domain controller for performing necessary configuration and informs SO of the completion5, 72TN_10Henry, Hesham

Status
colourBlue
titleNot yet tested

TN_11Service instantiation (Option 1/2) - Reuse existing NSIWhen triggered by NSSMF Adaptor with modifyNSSI for the BH, SO (TN NSSMF) calls SDN-C to update the new S-NSSAI info, etc.7, 82COM_20/COM_21Henry, Hesham

Status
colourBlue
titleNot yet tested

TN_12Service instantiation (Option 1/2) - Reuse existing NSISDN-C calls the Domain controller for performing necessary configuration and informs SO of the completion7, 82TN_11Henry, Hesham

Status
colourBlue
titleNot yet tested

TN_13Service activation (Option 1/2)When triggered by NSSMF Adaptor with activateNSSI for activating the TN BH NSSI, SO (TN NSSMF) triggers SDN-C for activating the S-NSSAI in the transport NFs.91COM_24/COM_25Henry, Hesham

Status
colourGreen
titlecompleted

TN_14Service activation (Option 1/2)SDN-C sends relevant  messages to TN NFs for activation of the S-NSSAI.91TN_14Henry, Hesham

Status
colourGreen
titlecompleted

TN_15Service activation (Option 1)

When triggered by NSSMF Adaptor with activateNSSI for activating the TN FH/MH NSSI, SO (TN NSSMF) triggers SDN-C for activating the S-NSSAI in the transport NFs.

(SDN-C actions are covered by TN_14)

91RAN_19Henry, Hesham

Status
colourGreen
titlecompleted

TN_16Service deactivation (Option 1/2)When triggered by NSSMF Adaptor with deactivateNSSI for deactivating the TN BH NSSI, SO (TN NSSMF) triggers SDN-C for deactivating the S-NSSAI in the transport NFs.101COM_26/COM_27Henry, Hesham

Status
colourGreen
titlecompleted

TN_17Service deactivation (Option 1/2)SDN-C sends relevant  messages to TN NFs for deactivation of the S-NSSAI.101TN_16Henry, Hesham

Status
colourGreen
titlecompleted

TN_18Service deactivation (Option 1)

When triggered by NSSMF Adaptor with deactivateNSSI for deactivating the TN FH/MH NSSI, SO (TN NSSMF) triggers SDN-C for deactivating the S-NSSAI in the transport NFs.

(SDN-C actions are covered by TN_17)

101RAN_22Henry, Hesham

Status
colourGreen
titlecompleted

TN_19Service termination (Option 1/2)When triggered by NSSMF Adaptor with modifyNSSI for removing S-NSSAI, SO (TN NSSMF) triggers SDN-C for removing the S-NSSAI in the TN NFs. Slice Profile of TN NSSI is also removed.111COM_29Henry, Hesham

Status
colourGreen
titlecompleted

TN_20Service termination (Option 1/2)SDN-C sends relevant messages to TN NFs for removal of the "service" (S-NSSAI)111TN_19Henry, Hesham

Status
colourGreen
titlecompleted

TN_21Service termination (Option 1/2)

When triggered by NSSMF Adaptor with deallocateNSSI API, SO (TN NSSMF) calls OOF to determine if TN NSSI has to be terminated. OOF returns RAN NSSI should not be terminated. (Remaining steps are the same as in test cases TN_19 and TN_20)

121COM_30Henry, Hesham

Status
colourGreen
titlecompleted

TN_21Service termination (Option 1/2)

When triggered by NSSMF Adaptor with deallocateNSSI API, SO (TN NSSMF) calls OOF to determine if TN NSSI has to be terminated. OOF returns RAN NSSI should be terminated. SO (TN NSSMF) triggers SDN-C for removal of TN NSSI, and associated links (S-NSSAI, Slice Profile) are also removed

121COM_30Henry, Hesham

Status
colourGreen
titlecompleted

TN_22Service termination (Option 1/2)SDN-C sends relevant messages to TN NFs for removal of the TN NSSI121TN_21Henry, Hesham

Status
colourGreen
titlecompleted

5. KPI Monitoring

Venue: CMCC Lab

S.No.Test Case DescriptionReference to main TCPriorityDependencyTesterStatus
KPI_01Update sql templates of DES MS for fetching relevant KPI/PM data from Mongo DB181
LuKai

Status
colourGreen
titleNot yet testedComplete

KPI_02Provide input from UUI on KPI/PM data to monitor along with details of the S-NSSAI/Slice identifier, this should trigger an API request towards DES MS181
LuKai

Status
colourGreen
titleNot yet testedComplete

KPI_03DES MS should provide a response by fetching the relevant KPI/PM data and giving it back to UUI (the data shall be pre-populated in Mongo DB as PM Mapper functionality is not fully done)191KPI_01, KPI_02LuKai

Status
colourGreen
titleNot yet testedComplete

KPI_04UUI shall display the KPI/PM data requested by the user192KPI_03LuKai

Status
titleNot yet tested

6. Closed Loop (Stretch Goal)

Venue: Winlab

S.No.Test Case DescriptionReference to main TCPriorityDependencyTesterStatus
CL_01PM data on DL/UL PRBs used for data traffic as reported by RAN-Sim (in a file) are posted on DMaaP by PM-Mapper.20
Dhebeha
2
Ahila

Status
titleNot yet tested

CL_02RAN-Sim sends PM data fileReadyNotification to VES-Collector for RAN PM data202RAN_09
Dhebeha
Ahila

Status
titleNot yet tested

CL_03Slice Analysis MS triggers Control Loop action towards Policy for throughput update at Near-RT RIC level based on analysis of DL/UL PRB used for data traffic for each S-NSSAI201RAN_09Dhebeha

Status
colourGreen
title

Not yet tested

COMPLETED

CL_04Upon reception of CL action from Slice Analysis MS, Policy triggers SO (RAN NSSMF) for reconfiguration of RAN resources.201RAN_09
Dhebeha
Ahila

Status
colourGreen
title

Not yet tested

completed

CL_05Upon CL trigger from Policy, SO (RAN NSSMF) triggers SDN-R for updating the throughput per Near-RT RIC.202RAN_09Ahila

Status

Dhebeha

colour

status

Green
title

Not yet tested

completed

CL_06Upon receiving the reconfiguration trigger from SO, SDN-R sends the config updates to RAN-Sim (Near-RT RIC) successfully.202RAN_09
Dhebeha
Ahila

Status
titleNot yet tested

Note: The RAN NSSI that has been created should span cells coming under the control of 2 Near-RT RICs.

7. Intelligent Slicing (Stretch Goal)

Venue: Winlab

S.No.Test Case DescriptionReference to main TCPriorityDependencyTesterStatus
INT_01PM data on PDU sessions requested, setup successfully and failed to setup reported by RAN-Sim (in a file) are posted on DMaaP by PM-Mapper.212
Dhebeha/Ahila

Status
titleNot yet tested

INT_02Slice Analysis MS receives updates to maxNumberofConns per cell for each S-NSSAI from ML-MS (onboarded just for flow testing and demo), and triggers Policy for Control Loop action211RAN_09Dhebeha/Ahila

Status
colourGreen
titleNot yet testedCOMPLETED

INT_03Upon reception of CL action from Slice Analysis MS, Policy triggers SO (RAN NSSMF) for reconfiguration of RAN resources.211RAN_09Dhebeha/Ahila

Status
colourGreen
titleNot yet testedcompleted

INT_04Upon CL trigger from Policy, SO (RAN NSSMF) triggers SDN-R for updating the throughput per Near-RT RIC.212RAN_09Dhebeha/Ahila

Status
colourGreen
titleNot yet testedcompleted

INT_05Upon receiving the reconfiguration trigger from SO, SDN-R sends the config updates to RAN-Sim (Near-RT RIC) successfully.212RAN_09Dhebeha/Ahila

Status
titleNot yet tested

...