You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

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.CategoryTest Case DescriptionReference to main TCDependencyTesterStatus
COM_01Service/template designSuccessful design of CST and Service Profile Templates1

NOT YET TESTED

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

NOT YET TESTED

COM_03Service instantiationService instantiation via CSMF Portal (UUI) for Option 1 (RAN NSSMF within ONAP) resulting in NST Selection request from SO towards OOF, and receiving the NST details in the callback from OOF.3COM_02

NOT YET TESTED

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.3COM_03

NOT YET TESTED

COM_05Service instantiation (Option 1) - New NSINSMF (SO) to trigger OOF for NSI selection, resulting in OOF providing Slice Profiles (in callback API) for new NSI creation (Option 1).3COM_04

NOT YET TESTED

COM_06Service instantiation (Option 1) - New NSINSMF Portal (UUI) provides endpoints for RAN and Core sub-nets3COM_05

NOT 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.3COM_06

NOT 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.3COM_06

NOT 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.3COM_06

NOT 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.
COM_01 - 03

NOT YET TESTED

2. RAN Slicing

Venue: Winlab

S.No.Test Case DescriptionReference to main TCDependencyTesterStatus
RAN_01Successful design of RAN NSST and RAN Slice Profile Templates2

NOT YET TESTED

RAN_02Provide RAN subnet capabilities when queried by NSSMF adaptor3

NOT YET TESTED

RAN_03When triggered by NSSMF Adaptor with allocateNSSI for allocating a new RAN NSSI, NSSMF (SO) triggers OOF for RAN NSSI selection, OOF provides Slice Profiles for RAN NF, TN FH and TN BH NSSIs (i.e., creation of a new RAN NSSI).


NOT YET TESTED

RAN_04




3. Core Slicing

Venue: ???

S.No.Test Case DescriptionReference to main TCDependencyTesterStatus
CORE_01Successful design of Core NSST and Core Slice Profile Templates1

NOT YET TESTED

CORE_02










4. Transport Slicing

Venue: ???

S.No.Test Case DescriptionReference to main TCDependencyTesterStatus
TN_01Successful design of Transport NSST and Transport Slice Profile Templates1

NOT YET TESTED

TN_02










5. Interaction with external RAN and Core NSSMF

Venue: CMCC Lab

S.No.Test Case DescriptionReference to main TCDependencyTesterStatus
EXT_01
1

NOT YET TESTED

EXT_02










6. KPI Monitoring

Venue: CMCC Lab

7. Closed Loop

Venue: Winlab

8. Intelligent Slicing

Venue: Winlab

  • No labels