Versions Compared

Key

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

The main list of test cases is available at E2E Network Slicing Use Case in R7 Guilin.

Important Note: Status update of test cases, prioritization and scenario-based reduction in testing scope is in progress.

...

Majority of Priority 1 test cases alone will be targeted to be completed for Guilin. This page will be updated in the next few days with the proper status of completed/ongoing tests (the parts which are completed), and other relevant details

...

.

Remark: We will continue to update the status as we continue the testing of various e2e scenario combinations, along with the P2 test cases beyond Guilin. Bugs found (if any) from now onwards will be solved in Honolulu.

1. Common CSMF, NSMF

Venue: CMCC Lab

...

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

Status
colourYellowGreen
titleIN PRoGRESSCOMPLETED

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

Status
colourGreen
titleCOMPLETED

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.31RAN_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-NSSAI32RAN_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.312RAN_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.312RAN_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.312RAN_07Reshmasree, Priyadharshini

Status
colourYellow
titleIN PROGRESS

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 creation312RAN_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-NSSAI512RAN_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.512RAN_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.92RAN_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.1012COM_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.102RAN_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.1012RAN_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)112RAN_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.112RAN_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

...

111122
S.No.CategoryTest Case DescriptionReference to main TCPriorityDependencyTesterStatus
CORE_01Service/template designSuccessful design of Core NSST, Core NF NSST, Core Slice Profile and Core Network Service21
Sanchita, Aleem

Status
colourYellow
titleIn 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.31COM_07Sanchita, Aleem

Status
colourYellow
titleNot yet testedIn pROGRESS

CORE_03Service instantiation (New NSSI)SO (Core NSSMF) creates new Core NSSI in AAI312
Sanchita, Aleem

Status
titleNot yet tested



Prepare Service order and trigger EXTAPI for instantiating new Core  NFs31

Sanchita, Aleem

Status
titleNot yet tested



On successful response from EXTAPI for the serviceOrderId associate instantiated core network service to NSSI. And update SO database with service operation status31

Sanchita, Aleem

Status
titleNot 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.312COM_18Sanchita, Aleem

Status
titleNot yet tested



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

Sanchita, Aleem


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

Sanchita, Aleem


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

Sanchita, Aleem


On successful response update the SO database with service operation status51

Sanchita, Aleem
CORE_05Service Activation and Service DeactivateWhen triggered by NSSMF Adaptor with activateNSSI or deactivateNSSI for activating/deactivating Core NSSI

7,8

12COM_24, COM_26Sanchita, Aleem

Status
titleNot yet tested



Get all s-nssai and orchestration status from slice profiles associated with NSSI7.81

Sanchita, Aleem


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

Sanchita, Aleem


Onsuccessful response update slice profile instance in AAI7.81

Sanchita, Aleem
CORE_06Service DeallocateWhen triggered by NSSMF Adaptor with deAllocate for deallocating Core NSSI9, 10, 152COM_29, COM_31Alexander Borovitzky

Status
titleNot yet tested



Get the network service instance and slice profile associated with NSSI2


Alexander Borovitzky


If TerminateNSSI=true then 2


Alexander Borovitzky


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
2


Alexander Borovitzky


Update SO database with operation status2


Alexander Borovitzky
CORE_07Service DeallocateWhen triggered by NSSMF Adaptor with deAllocate for deallocating Core NSSI92COM_29, COM_31Alexander Borovitzky

Status
titleNot yet tested



Get the network service instance and slice profile associated with NSSI2


Alexander Borovitzky


If TerminateNSSI=false then  2


Alexander Borovitzky


Get VNF/VFs associated with NSSI. Get all the s-nssai  and orchestration status from the slice profiles associated with NSSI2


Alexander Borovitzky


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


Alexander Borovitzky


Remove NSSI association with NSI
Remove association of  slice profile instance with NSSI
Delete the slice profile instance2



Alexander Borovitzky


Update SO database with operation status


Alexander Borovitzky
CORE_08Service Modify (create new slice profile instance)When triggered by NSSMF Adaptor with modify for modifying Core NSSI11, 142COM_28Alexander Borovitzky

Status
titleNot yet tested



Get the network service instance and slice profile associated with NSSI2


Alexander Borovitzky


Get VNF/VFs associated with NSSI. Get all the s-nssai  and orchestration status from the slice profiles associated with NSSI2


Alexander Borovitzky


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


Alexander Borovitzky


On success response, create slice profile instance in AAI
Associate slice profile instance with NSSI2



Alexander Borovitzky


Update SO database with operation status2


Alexander Borovitzky
CORE_09Service Modify (delete slice profile instance)When triggered by NSSMF Adaptor with modify for modifying Core NSSI
2
Alexander Borovitzky

Status
titleNot yet tested



Get the network service instance and slice profile associated with NSSI2


Alexander Borovitzky


Get VNF/VFs associated with NSSI. Get all the s-nssai  and orchestration status from the slice profiles associated with NSSI2


Alexander Borovitzky


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


Alexander Borovitzky


On success response, remove NSSI to slice profile association
Delete the slice profile instance2



Alexander Borovitzky


Update SO database with operation status


Alexander Borovitzky

4. Transport Slicing

...

S.No.CategoryTest Case DescriptionReference to main TCPriorityDependencyTesterStatus
TN_01Service/template designSuccessful design of TN NSSTs (for FH, MH and BH), TN Slice Profile templates for FH, MH and BH21
Chuyi

Status
colourYellowGreen
titleIN PRoGRESSCompleted

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

Status
colourGreen
titleCompleted

TN_03Service instantiation (Option 1/2) - 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).3, 42COM_07Henry, Hesham

Status
colourBlue
titlenot started

TN_04Service instantiation (Option 1/2) - New NSI, new TN NSSISO (RAN NSSMF) creates new TN BH NSSI and configuring it by calling SDN-C3, 41TN_03Henry, Hesham

Status
colourGreen
titleCompleted

TN_05Service instantiation (Option 1/2) - New NSI, new TN NSSI (BH)SDN-C calls the Domain controller for performing necessary configuration and informs SO of the completion3, 41TN_04Henry, Hesham

Status
colourGreen
titlecompleted

TN_06Service instantiation (Option 1) - New NSI, new TN NSSI (FH/MH)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).32COM_07Henry, Hesham

Status
titleNot yet tested

TN_07Service instantiation (Option 1) - New NSI, new TN NSSI (FH/MH)SO (TN NSSMF) creates new TN FH/MH NSSI and configuring it by calling SDN-C31TN_06Henry, Hesham

Status
colourGreen
titlecompleted

TN_08Service instantiation (Option 1) - New NSI, new TN NSSI (FH/MH)SDN-C calls the Domain controller for performing necessary configuration and informs SO of the completion31TN_07Henry, Hesham

Status
colourGreen
titlecompleted

TN_09

Service instantiation (Option 1) - New NSI, reuse existing RAN NSSI (=> configuration update of TN NSSI (FH/MH))

AND

Service instantiation (Option 1) - Reuse existing NSI

When triggered from RAN NSSMF with modifyNSSI API for the FH/MH, SO (TN NSSMF) calls SDN-C to update the new S-NSSAI info, etc.5, 72RAN_15Henry, Hesham

Status
colourBlue
titleNot yet tested

TN_10

Service instantiation (Option 1) - New NSI, reuse existing RAN NSSI (=> configuration update of TN NSSI (FH/MH))

AND

Service instantiation (Option 1) - Reuse existing NSI

SDN-C calls the Domain controller for performing necessary configuration and informs SO of the completion5, 72TN_10Henry, Hesham

Status
colourBlue
titleNot yet tested

TN_11Service instantiation (Option 1/2) - Reuse existing NSIWhen triggered by NSSMF Adaptor with modifyNSSI for the BH, SO (TN NSSMF) calls SDN-C to update the new S-NSSAI info, etc.7, 82COM_20/COM_21Henry, Hesham

Status
colourBlue
titleNot yet tested

TN_12Service instantiation (Option 1/2) - Reuse existing NSISDN-C calls the Domain controller for performing necessary configuration and informs SO of the completion7, 82TN_11Henry, Hesham

Status
colourBlue
titleNot yet tested

TN_13Service activation (Option 1/2)When triggered by NSSMF Adaptor with activateNSSI for activating the TN BH NSSI, SO (TN NSSMF) triggers SDN-C for activating the S-NSSAI in the transport NFs.91COM_24/COM_25Henry, Hesham

Status
colourGreen
titlecompleted

TN_14Service activation (Option 1/2)SDN-C sends relevant  messages to TN NFs for activation of the S-NSSAI.91TN_14Henry, Hesham

Status
colourGreen
titlecompleted

TN_15Service activation (Option 1)

When triggered by NSSMF Adaptor with activateNSSI for activating the TN FH/MH NSSI, SO (TN NSSMF) triggers SDN-C for activating the S-NSSAI in the transport NFs.

(SDN-C actions are covered by TN_14)

91RAN_19Henry, Hesham

Status
colourGreen
titlecompleted

TN_16Service deactivation (Option 1/2)When triggered by NSSMF Adaptor with deactivateNSSI for deactivating the TN BH NSSI, SO (TN NSSMF) triggers SDN-C for deactivating the S-NSSAI in the transport NFs.101COM_26/COM_27Henry, Hesham

Status
colourGreen
titlecompleted

TN_17Service deactivation (Option 1/2)SDN-C sends relevant  messages to TN NFs for deactivation of the S-NSSAI.101TN_16Henry, Hesham

Status
colourGreen
titlecompleted

TN_18Service deactivation (Option 1)

When triggered by NSSMF Adaptor with deactivateNSSI for deactivating the TN FH/MH NSSI, SO (TN NSSMF) triggers SDN-C for deactivating the S-NSSAI in the transport NFs.

(SDN-C actions are covered by TN_17)

101RAN_22Henry, Hesham

Status
colourGreen
titlecompleted

TN_19Service termination (Option 1/2)When triggered by NSSMF Adaptor with modifyNSSI for removing S-NSSAI, SO (TN NSSMF) triggers SDN-C for removing the S-NSSAI in the TN NFs. Slice Profile of TN NSSI is also removed.111COM_29Henry, Hesham

Status
colourGreen
titlecompleted

TN_20Service termination (Option 1/2)SDN-C sends relevant messages to TN NFs for removal of the "service" (S-NSSAI)111TN_19Henry, Hesham

Status
colourGreen
titlecompleted

TN_21Service termination (Option 1/2)

When triggered by NSSMF Adaptor with deallocateNSSI API, SO (TN NSSMF) calls OOF to determine if TN NSSI has to be terminated. OOF returns RAN NSSI should not be terminated. (Remaining steps are the same as in test cases TN_19 and TN_20)

121COM_30Henry, Hesham

Status
colourGreen
titlecompleted

TN_21Service termination (Option 1/2)

When triggered by NSSMF Adaptor with deallocateNSSI API, SO (TN NSSMF) calls OOF to determine if TN NSSI has to be terminated. OOF returns RAN NSSI should be terminated. SO (TN NSSMF) triggers SDN-C for removal of TN NSSI, and associated links (S-NSSAI, Slice Profile) are also removed

121COM_30Henry, Hesham

Status
colourGreen
titlecompleted

TN_22Service termination (Option 1/2)SDN-C sends relevant messages to TN NFs for removal of the TN NSSI121TN_21Henry, Hesham

Status
colourGreen
titlecompleted

...

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

Status
colourGreen
titleComplete

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

Status
colourYellowGreen
titleIN PROGRESSComplete

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

Status
colourGreen
titleNot yet testedComplete

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

Status
titleNot yet tested

6. Closed Loop (Stretch Goal)

Venue: Winlab

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

Status
titleNot yet tested

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

Status
titleNot 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-NSSAI201RAN_09Dhebeha

Status
colourGreen
titleCOMPLETED

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

Status
colourYellow
titleIn Progress

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

Status
titleNot yet tested

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

Status
titleNot yet tested

Note: The RAN NSSI that has been created should span cells coming under the control of 2 Near-RT RICs.

7. Intelligent Slicing (Stretch Goal)

Venue: Winlab

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

Status
titleNot 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 action211RAN_09Dhebeha/Ahila

Status
colourGreen
titleCOMPLETED

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

Status
colourYellow
titleIn Progress

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

Status
titleNot yet tested

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

Status
titleNot yet tested

...