Jira reference: REQ-632 - Getting issue details... STATUS
Test lab: Winlab
Legend:
NOT STARTED IN PROGRESS DEFERRED COMPLETED
Italics - Regression test cases
| S. No. | Topic | Test Case Description | Priority | Dependency/Issue | Tester | Status | Remarks |
|---|---|---|---|---|---|---|---|
| RAN_01 | Service/template design | Successful design of RAN NSST, RAN NF NSST, RAN Slice Profile and RAN NF Slice Profile Templates | 1 | NOT STARTED | |||
| RAN_02 | 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). | 1 | NOT STARTED | |||
| RAN_03 | Service instantiation (Option 1) - New NSI, new RAN NSSI | SO (RAN NSSMF) creates new RAN NF NSSI and configuring it by calling SDN-R. AAI is also updated with relevant Slice Profile info. | 1 | Deepika S | NOT STARTED | ||
| RAN_04 | 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 | 1 | NOT STARTED | |||
| RAN_05 | 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 (netconf) messages to RAN-Sim) and updates SO of the completion. | 1 | NOT STARTED | |||
| RAN_06 | 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. | 1 | Deepika S | NOT STARTED | ||
| RAN_07 | Service instantiation (Option 1) - New NSI, new RAN NSSI | SO (RAN NSSMF) makes suitable updates to AAI about Slice Profiles, RAN NF NSSI, etc. | 1 | NOT STARTED | |||
| RAN_08 | 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 | 1 | NOT STARTED | |||
| RAN_09 | Service instantiation (Option 1) - New NSI, reuse RAN NSSI | 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). | 1 | NOT STARTED | |||
| RAN_10 | Service instantiation (Option 1) - New NSI, reuse RAN NSSI | SO (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. | 1 | NOT STARTED | |||
| 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 | 1 | NOT STARTED | |||
| RAN_12 | Service instantiation (Option 1) - New NSI, reuse RAN NSSI | SDN-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-NSSAI | 1 | NOT STARTED | |||
| RAN_13 | Service instantiation (Option 1) - New NSI, reuse RAN NSSI | SDN-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. | 1 | NOT STARTED | |||
| RAN_14 | 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 using modifyNSSI API. | 1 | NOT STARTED | |||
| RAN_15 | Service instantiation (Option 1) - Reuse existing NSI | 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) | 1 | NOT STARTED | |||
| RAN_16 | Service 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. | 9 | ||||
| RAN_17 | Service 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. | 9 | ||||
| RAN_18 | Service activation (Option 1) | SO (RAN NSSMF) triggers SO (TN NSSMF) for activating the TN FH and TN MH NSSIs. | 9 | ||||
| RAN_19 | Service 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. | 10 | ||||
| RAN_20 | Service 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. | 10 | ||||
| RAN_21 | Service deactivation (Option 1) | SO (RAN NSSMF) triggers SO (TN NSSMF) for deactivating the TN FH and TN MH NSSIs. | 10 | ||||
| RAN_22 | Service 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. | 11 | ||||
| RAN_23 | Service termination (Option 1) | SDN-R makes relevant updates to ConfigDB (removal of S-NSSAI and RAN NF Slice Profile, RRM Policy update) | 11 | ||||
| RAN_24 | Service termination (Option 1) | SDN-R sends relevant (netconf) messages to RAN-NFs (CUs, DUs, Near-RT RICs) of S-NSSAI removal, and update of RRM Policy, etc. | 11 | ||||
| RAN_25 | Service termination (Option 1) | SO (RAN NSSMF) triggers SO (TN NSSMF) for updating the TN FH and TN MH NSSIs. Slice Profiles of TN FH and MH NSSIs are also removed. | 11 | ||||
| RAN_26 | Service 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) | 12 | ||||
| RAN_27 | Service 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 be terminated. | 12 | ||||
| RAN_28 | Service termination (Option 1) | SO (RAN NSSMF) calls OOF to determine if RAN NF NSSI has to be terminated. OOF returns that RAN NF NSSI should be terminated. | 12 | ||||
| RAN_29 | Service termination (Option 1) | 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) | 12 | ||||
| RAN_30 | Service termination (Option 1) | SO (RAN NSSMF) triggers SO (TN NSSMF) with deallocateNSSI API call for deallocation of TN FH and TN MH NSSIs | 12 | ||||
| RAN_31 | Service termination (Option 1) | 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) | 12 |