The main list of test cases is available at E2E Network Slicing Use Case in R7 Guilin.
1. Common CSMF, NSMF
Venue: CMCC Lab
| S.No. | Category | Test Case Description | Reference to main TC | Dependency | Tester | Status |
|---|---|---|---|---|---|---|
| COM_01 | Service/template design | Successful design of CST and Service Profile Templates | 1 | Zhang Min, He Tengjiao | IN PROGRESS | |
| COM_02 | Service/template design | Successful design of NST (option 1 and option 2) | 2 | Zhang Min, He Tengjiao | IN PROGRESS | |
| COM_03 | Service 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. | 3 | COM_01, COM_02 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_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. | 3 | COM_03 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_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). | 3 | COM_04 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_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. | 3 | COM_05 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_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. | 3 | COM_06 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_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. | 3 | COM_06 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_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. | 3 | COM_08 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_10 | Service instantiation (Option 2) - New NSI | After NST selection, NSMF (SO) fetches sub-net capabilities for the 3 constituent sub-nets (RAN, Core and Transport) for Option 2. | 4 | COM_03 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_11 | 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). | 4 | COM_10 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_12 | 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). | 4 | COM_11 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_13 | 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. | 4 | COM_12 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_14 | Service instantiation (Option 2) - New 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) | 4 | COM_12 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_15 | 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 Core NSSI is already covered in COM_09) | 4 | COM_14 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_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 RANNSSI can be reused. | 5 | COM_11 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_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 | COM_11 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_16 | 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). | 6 | COM_11 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_17 | 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 existing NSI details in the response. | 7 | COM_04 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_18 | 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 | COM_17 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_19 | Service instantiation (Option 1) - Reuse existing NSI | NSMF then calls modifyNSSI API towards RAN, Core and Transport NSSMFs with details of NSI to be reused and the respective Slice Profile | 7 | COM_18 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_20 | 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 details 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 | COM_04 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_21 | Service instantiation (Option 2) - Reuse existing NSI (similar to testcase COM_19) | 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 | 8 | COM_20 | Zhang Min, He Tengjiao | NOT YET TESTED |
| COM_22 | Service activation | Service activation from CSMF portal – resulting in slice service activation 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:
2. RAN Slicing
Venue: Winlab (Rutgers University)
| S.No. | Category | Test Case Description | Reference to main TC | Dependency | Tester | Status |
|---|---|---|---|---|---|---|
| RAN_01 | Service/template design | Successful design of RAN NSST, RAN NF NSST, RAN Slice Profile and RAN NF Slice Profile Templates | 2 | Borislav | IN PROGRESS | |
| RAN_02 | Service instantiation (Option 1) - New NSI, new RAN NSSI | Provide RAN subnet capabilities when queried by NSSMF adaptor | 3 | Reshmasree, Priyadharshini | NOT YET TESTED | |
| RAN_03 | Service instantiation (Option 1) - New NSI, new RAN NSSI | When 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). | 3 | COM_07 | Reshmasree, Priyadharshini | NOT YET TESTED |
| RAN_04 | Service instantiation (Option 1) - New NSI, new RAN NSSI | SO (RAN NSSMF) creates new RAN NF NSSI and configuring it by calling SDN-R | 3 | RAN_03 | Reshmasree, Priyadharshini | NOT YET TESTED |
| RAN_05 | Service instantiation (Option 1) - New NSI, new RAN NSSI | SDN-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-NSSAI | 3 | RAN_04 | Reshmasree, Priyadharshini | NOT YET TESTED |
| RAN_06 | Service instantiation (Option 1) - New NSI, new RAN NSSI | SDN-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. | 3 | RAN_04 | Reshmasree, Priyadharshini | NOT YET TESTED |
| RAN_07 | Service instantiation (Option 1) - New NSI, new RAN NSSI | SO (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. | 3 | RAN_06 | Reshmasree, Priyadharshini | NOT YET TESTED |
| RAN_08 | Service instantiation (Option 1) - New NSI, new RAN NSSI | SO (RAN NSSMF) makes suitable updates to AAI about Slice Profiles, RAN NF NSSI, etc. | 3 | RAN_07 | Reshmasree, Priyadharshini | NOT YET TESTED |
| RAN_09 | Service instantiation (Option 1) - New NSI, new RAN NSSI | Upon 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 creation | 3 | RAN_07 | Reshmasree, Priyadharshini | NOT YET TESTED |
| RAN_10 | Service instantiation (Option 1) - New NSI, reuse RAN NSSI | When triggered by NSSMF Adaptor with allocateNSSI for allocating a new RAN NSSI, RAN NSSMF (SO) triggers OOF for RAN NSSI selection, OOF provides existing RAN NSSI (i.e., reuse of an existing RAN NSSI). | 5 | COM_07 | Reshmasree, Priyadharshini | NOT YET TESTED |
| RAN_11 | Service instantiation (Option 1) - New NSI, reuse RAN NSSI | SO (RAN NSSMF) calls SDN-R for configuring the existing RAN NF NSSI (reuse) with the new S-NSSAI and Slice Profile | 5 | RAN_10 | Reshmasree, Priyadharshini | NOT YET TESTED |
| RAN_12 | Service instantiation (Option 1) - New NSI, reuse RAN NSSI | SO (RAN NSSMF) calls SO (TN NSSMF) for configuring the existing TN FH/MH NSSIs (reuse) with the new S-NSSAI and respective Slice Profiles | 5 | RAN_11 | Reshmasree, Priyadharshini | NOT YET TESTED |
3. Core Slicing
Venue: ???
| S.No. | Category | Test Case Description | Reference to main TC | Dependency | Tester | Status |
|---|---|---|---|---|---|---|
| CORE_01 | Service/template design | Successful design of Core NSST, Core NF NSST, Core Slice Profile and Core Network Service | 2 | IN PROGRESS | ||
| CORE_02 | Service instantiation | 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. | 3 | NOT YET TESTED | ||
| CORE_03 | Service instantiation (New NSSI) | SO (Core NSSMF) creates new Core NSSI in AAI | 3 | NOT YET TESTED | ||
| Prepare Service order and trigger EXTAPI for instantiating new Core NFs | 3 | NOT YET TESTED | ||||
| On successful response from EXTAPI for the serviceOrderId associate instantiated core network service to NSSI. And update SO database with service operation status | 3 | NOT YET TESTED | ||||
| CORE_04 | Service 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. | 3 | NOT YET TESTED | ||
| OOF returns existing NSSI. Find the associated network service with NSSI | 5 | |||||
| Prepare request payload to trigger SO macro flow to update the Core network service NFs | 5 | |||||
| Trigger SO macro flow (by calling serviceInstance api PUT method). | 5 | |||||
| On successful response update the SO database with service operation status | 5 | |||||
| CORE_05 | Service Activation and Service Deactivate | When triggered by NSSMF Adaptor with activateNSSI or deactivateNSSI for activating/deactivating Core NSSI | 7,8 | NOT YET TESTED | ||
| Get all s-nssai and orchestration status from slice profiles associated with NSSI | 7.8 | |||||
| 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 adapter | 7.8 | |||||
| Onsuccessful response update slice profile instance in AAI | 7.8 | |||||
| CORE_06 | Service Deallocate | When triggered by NSSMF Adaptor with deAllocate for deallocating Core NSSI | 9, 10, 15 | NOT YET TESTED | ||
| Get the network service instance and slice profile associated with NSSI | ||||||
| If TerminateNSSI=true then | ||||||
| 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 | ||||||
| Update SO database with operation status | ||||||
| CORE_07 | Service Deallocate | When triggered by NSSMF Adaptor with deAllocate for deallocating Core NSSI | 9 | NOT YET TESTED | ||
| Get the network service instance and slice profile associated with NSSI | ||||||
| If TerminateNSSI=false then | ||||||
| Get VNF/VFs associated with NSSI. Get all the s-nssai and orchestration status from the slice profiles associated with NSSI | ||||||
| Prepare request payload to trigger SO macro flow to update the Core network service NFs | ||||||
| Remove NSSI association with NSI Remove association of slice profile instance with NSSI Delete the slice profile instance | ||||||
| Update SO database with operation status | ||||||
| CORE_08 | Service Modify (create new slice profile instance) | When triggered by NSSMF Adaptor with modify for modifying Core NSSI | NOT YET TESTED | |||
| Get the network service instance and slice profile associated with NSSI | ||||||
| Get VNF/VFs associated with NSSI. Get all the s-nssai and orchestration status from the slice profiles associated with NSSI | ||||||
| Prepare request payload to trigger SO macro flow to update the Core network service NFs | ||||||
| On success response, create slice profile instance in AAI Associate slice profile instance with NSSI | ||||||
| Update SO database with operation status | ||||||
| CORE_09 | Service Modify (delete slice profile instance) | When triggered by NSSMF Adaptor with modify for modifying Core NSSI | NOT YET TESTED | |||
| Get the network service instance and slice profile associated with NSSI | ||||||
| Get VNF/VFs associated with NSSI. Get all the s-nssai and orchestration status from the slice profiles associated with NSSI | ||||||
| Prepare request payload to trigger SO macro flow to update the Core network service NFs | ||||||
| On success response, remove NSSI to slice profile association Delete the slice profile instance | ||||||
| Update SO database with operation status |
4. Transport Slicing
Venue: CMCC Lab
| S.No. | Test Case Description | Reference to main TC | Dependency | Tester | Status | |
|---|---|---|---|---|---|---|
| TN_01 | Service/template design | Successful design of TN NSSTs (for FH, MH and BH), TN Slice Profile templates for FH, MH and BH | 2 | Chuyi | IN PROGRESS | |
| TN_02 | Service instantiation (Option 1) - New NSI, new TN NSSI | Provide TN subnet capabilities when queried by NSSMF adaptor | 3 | Henry, Hesham | NOT YET TESTED | |
| TN_03 | Service instantiation (Option 1) - New NSI, new TN NSSI | When 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 | COM_07 | Henry, Hesham | NOT YET TESTED |
| TN_04 | Service instantiation (Option 1) - New NSI, new TN NSSI | SO (RAN NSSMF) creates new TN BH NSSI and configuring it by calling SDN-C | 3 | TN_03 | Henry, Hesham | NOT YET TESTED |
| TN_05 | Service instantiation (Option 1) - New NSI, new TN NSSI | SDN-C calls the Domain controller for performing necessary configuration and informs SO of the completion | 3 | TN_04 | Henry, Hesham | NOT YET TESTED |
| TN_06 | Service instantiation (Option 1) - New NSI, new TN NSSI | 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). | 3 | COM_07 | Henry, Hesham | NOT YET TESTED |
| TN_07 | Service instantiation (Option 1) - New NSI, new TN NSSI | SO (RAN NSSMF) creates new TN BH NSSI and configuring it by calling SDN-C | 3 | TN_06 | Henry, Hesham | NOT YET TESTED |
| TN_08 | Service instantiation (Option 1) - New NSI, new TN NSSI | SDN-C calls the Domain controller for performing necessary configuration and informs SO of the completion | 3 | TN_07 | Henry, Hesham | NOT YET TESTED |
5. KPI Monitoring
Venue: CMCC Lab
| S.No. | Test Case Description | Reference to main TC | Dependency | Tester | Status |
|---|---|---|---|---|---|
| KPI_01 | Update sql templates of DES MS for fetching relevant KPI/PM data from Mongo DB | 18 | LuKai | NOT YET TESTED | |
| KPI_02 | Provide 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 MS | 18 | LuKai | NOT YET TESTED | |
| KPI_03 | DES 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) | 19 | KPI_01, KPI_02 | LuKai | NOT YET TESTED |
| KPI_04 | UUI shall display the KPI/PM data requested by the user | 19 | KPI_03 | LuKai | NOT YET TESTED |
6. Closed Loop
Venue: Winlab
| S.No. | Test Case Description | Reference to main TC | Dependency | Tester | Status |
|---|---|---|---|---|---|
| CL_01 | PM 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 | NOT YET TESTED | |
| CL_02 | RAN-Sim sends PM data fileReadyNotification to VES-Collector for RAN PM data | 20 | RAN_09 | Dhebeha | NOT YET TESTED |
| CL_03 | Slice 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-NSSAI | 20 | RAN_09 | Dhebeha | NOT YET TESTED |
| CL_04 | Upon reception of CL action from Slice Analysis MS, Policy triggers SO (RAN NSSMF) for reconfiguration of RAN resources. | 20 | RAN_09 | Dhebeha | NOT YET TESTED |
| CL_05 | Upon CL trigger from Policy, SO (RAN NSSMF) triggers SDN-R for updating the throughput per Near-RT RIC. | 20 | RAN_09 | Dhebeha | NOT YET TESTED |
| CL_06 | Upon receiving the reconfiguration trigger from SO, SDN-R sends the config updates to RAN-Sim (Near-RT RIC) successfully. | 20 | RAN_09 | Dhebeha | NOT YET TESTED |
7. Intelligent Slicing
Venue: Winlab
| S.No. | Test Case Description | Reference to main TC | Dependency | Tester | Status |
|---|---|---|---|---|---|
| INT_01 | PM 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. | 21 | Dhebeha/Ahila | NOT YET TESTED | |
| INT_02 | Slice 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 action | 21 | RAN_09 | Dhebeha/Ahila | NOT YET TESTED |
| INT_03 | Upon reception of CL action from Slice Analysis MS, Policy triggers SO (RAN NSSMF) for reconfiguration of RAN resources. | 21 | RAN_09 | Dhebeha/Ahila | NOT YET TESTED |
| INT_04 | Upon CL trigger from Policy, SO (RAN NSSMF) triggers SDN-R for updating the throughput per Near-RT RIC. | 21 | RAN_09 | Dhebeha/Ahila | NOT YET TESTED |
| INT_05 | Upon receiving the reconfiguration trigger from SO, SDN-R sends the config updates to RAN-Sim (Near-RT RIC) successfully. | 21 | RAN_09 | Dhebeha/Ahila | NOT YET TESTED |