Versions Compared

Key

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

...

S.No.CategoryTest Case DescriptionReference to main TCPriorityDependencyTesterStatus
COM_01Service/template designSuccessful design of CST and Service Profile Templates1

Zhang Min, He Tengjiao

Status
colourGreen
titleCompleted

COM_02Service/template designSuccessful design of NST (option 1 and option 2)2

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.3
COM_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
colourYellow
titleNot yet testedIN PROGRESS

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
titleNot yet testedIN 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
titleNot yet testedIN 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
colourYellow
titleIN PROGRESS

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

Status
titleNot yet tested

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

Status
titleNot yet tested

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

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.172COM_29Priyadharshini

Status
titleNot yet tested

...

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 Templates2

Borislav

Status
colourYellow
titleIN PRoGRESS

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).3
COM_07Reshmasree, Priyadharshini

Status
colourYellowGreen
titleIN PROGRESSCOMPLETED

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.3
RAN_03Reshmasree, Priyadharshini

Status
colourYellow
titleIN PROGRESS

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-NSSAI3
RAN_04Sandeep Shah, Ahila

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 (netconf) messages to RAN-Sim) and updates SO of the completion.3
RAN_04Sandeep Shah, Ahila

Status
titleNot yet tested

RAN_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.31RAN_06Reshmasree, Priyadharshini

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.31RAN_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 creation31RAN_07Reshmasree, Priyadharshini

Status
titleNot yet tested

RAN_10Service instantiation (Option 1) - New NSI, 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
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. Slice Profile details are then updated in AAI.52RAN_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 Profile52RAN_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-NSSAI52RAN_12Sandeep Shah, Ahila

Status
titleNot yet tested

RAN_14Service instantiation (Option 1) - 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

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 Profiles using modifyNSSI API.52RAN_12Reshmasree, Priyadharshini

Status
titleNot yet tested

RAN_16Service 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)

72COM_20Reshmasree, Priyadharshini

Status
titleNot yet tested

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.9
RAN_17Sandeep Shah, Ahila

Status
titleNot yet tested

RAN_19Service activation (Option 1)SO (RAN NSSMF) triggers 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.101COM_25Reshmasree, Priyadharshini

Status
titleNot yet tested

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.10
RAN_20Sandeep Shah, Ahila

Status
titleNot yet tested

RAN_22Service deactivation (Option 1)SO (RAN NSSMF) triggers SO (TN NSSMF) for deactivating the TN FH and TN MH NSSIs.101RAN_20Reshmasree, Priyadharshini

Status
titleNot yet tested

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
titleNot yet tested

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

Status
titleNot yet tested

RAN_25Service 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_24Sandeep Shah, Ahila

Status
titleNot yet tested

RAN_26Service 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.112RAN_23Reshmasree, Priyadharshini

Status
titleNot yet tested

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

RAN_28Service 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.122COM_30Reshmasree, Priyadharshini

Status
titleNot yet tested

RAN_29Service 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.122RAN_28Reshmasree, Priyadharshini

Status
titleNot yet tested

RAN_30Service 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)

122RAN_29Reshmasree, Priyadharshini

Status
titleNot yet tested

RAN_30Service termination (Option 1)SO (RAN NSSMF) triggers SO (TN NSSMF) with deallocateNSSI API call for deallocation of TN FH and TN MH NSSIs122RAN_29Reshmasree, Priyadharshini

Status
titleNot yet tested

RAN_31Service 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)

122RAN_28Reshmasree, Priyadharshini

Status
titleNot yet tested

...