Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 27 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
Zhang Min, He Tengjiao

IN PROGRESS

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

IN PROGRESS

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.3COM_01, COM_02Zhang Min, He Tengjiao

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

NOT YET TESTED

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

NOT YET TESTED

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.3COM_05Zhang Min, He Tengjiao

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

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

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

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

NOT YET TESTED

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).4COM_10Zhang Min, He Tengjiao

NOT YET TESTED

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).4COM_11Zhang Min, He Tengjiao

NOT 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.4COM_12Zhang Min, He Tengjiao

NOT YET TESTED

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)4COM_13Zhang Min, He Tengjiao

NOT YET TESTED

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

NOT 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

NOT 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.5COM_11Zhang Min, He Tengjiao

NOT 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

NOT 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

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

NOT 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

NOT 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

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

NOT 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)8COM_21Zhang Min, He Tengjiao

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

NOT 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

9COM_09 or COM_20Zhang Min, He Tengjiao

NOT 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 NSSMF9COM_15 or COM_23Zhang Min, He Tengjiao

NOT 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

10COM_24Zhang Min, He Tengjiao

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

NOT 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 terminated11COM_24 or COM_25Priya, Reshmasree

NOT 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_28Priya, Reshmasree

NOT 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_25Priya, Reshmasree

NOT 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_30Priya, Reshmasree

NOT YET TESTED









2. RAN Slicing

Venue: Winlab (Rutgers University)

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 Templates2
Borislav

IN PROGRESS

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

NOT YET TESTED

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

NOT 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

NOT YET TESTED

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-NSSAI3RAN_04Reshmasree, Priyadharshini

NOT 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_04Reshmasree, Priyadharshini

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

NOT 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

NOT 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

NOT YET TESTED

RAN_10Service instantiation (Option 1) - New NSI, reuse 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 existing RAN NSSI (i.e., reuse of an existing RAN NSSI).5COM_07Reshmasree, Priyadharshini

NOT YET TESTED

RAN_11Service 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_10Reshmasree, Priyadharshini

NOT YET TESTED

RAN_12Service 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_11Reshmasree, Priyadharshini

NOT YET TESTED

3. Core Slicing

Venue: ???

S.No.CategoryTest Case DescriptionReference to main TCDependencyTesterStatus
CORE_01Service/template designSuccessful design of Core NSST, Core NF NSST, Core Slice Profile and Core Network Service2

IN PROGRESS

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

NOT YET TESTED

CORE_03Service instantiation (New NSSI)SO (Core NSSMF) creates new Core NSSI in AAI3

NOT YET TESTED



Prepare Service order and trigger EXTAPI for instantiating new Core  NFs3

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 status3

NOT YET TESTED

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

NOT YET TESTED



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




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




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




On successful response update the SO database with service operation status5


CORE_05Service Activation and Service DeactivateWhen 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 NSSI7.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 adapter7.8




Onsuccessful response update slice profile instance in AAI7.8


CORE_06Service DeallocateWhen triggered by NSSMF Adaptor with deAllocate for deallocating Core NSSI9, 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_07Service DeallocateWhen triggered by NSSMF Adaptor with deAllocate for deallocating Core NSSI9

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_08Service 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_09Service 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 DescriptionReference to main TCDependencyTesterStatus
TN_01Service/template designSuccessful design of TN NSSTs (for FH, MH and BH), TN Slice Profile templates for FH, MH and BH2
Chuyi

IN PROGRESS

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

NOT 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

NOT 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

NOT 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

NOT 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

NOT 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

NOT 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

NOT YET TESTED

5. KPI Monitoring

Venue: CMCC Lab

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

NOT YET TESTED

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 MS18
LuKai

NOT YET TESTED

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)19KPI_01, KPI_02LuKai

NOT YET TESTED

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

NOT YET TESTED

6. Closed Loop

Venue: Winlab

S.No.Test Case DescriptionReference to main TCDependencyTesterStatus
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

NOT YET TESTED

CL_02RAN-Sim sends PM data fileReadyNotification to VES-Collector for RAN PM data20RAN_09Dhebeha

NOT 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-NSSAI20RAN_09Dhebeha

NOT YET TESTED

CL_04Upon reception of CL action from Slice Analysis MS, Policy triggers SO (RAN NSSMF) for reconfiguration of RAN resources.20RAN_09Dhebeha

NOT YET TESTED

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

NOT YET TESTED

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

NOT YET TESTED

7. Intelligent Slicing

Venue: Winlab

S.No.Test Case DescriptionReference to main TCDependencyTesterStatus
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.21
Dhebeha/Ahila

NOT 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 action21RAN_09Dhebeha/Ahila

NOT YET TESTED

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

NOT YET TESTED

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

NOT YET TESTED

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

NOT YET TESTED

  • No labels