Versions Compared

Key

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

...

NOT STARTED
S.NoTopicDescriptionDependencyTesterStatusRemarksTest Details
1Service Instantiation(new ran nssinsi) OOF should return slice profiles with Coverage Area to coverageAreaTAList mapping mapping in NSMFOOF

Status
colourBlue
titleDEFERRED

Prerequisite: CPS needs to be preloaded with coverage Area TA listUUI is having discrepancy with TA Mapping as List
2Service Instantiation(new ran nssi)SDNR integration with  CPS - allocate flow: CPS should be updated with the RAN configurations   SDN-R, CPS

Status
colourBlue
titleDEFERRED

TBDMT templates should be preloaded
3Service Instantiation (new RAN NSSI)SDN-R configures RAN NFs via O1. All NFs and the cells should be updated with the proper configuration    SDN-R, CPS, RANSimulator

Status
colourBlue
titleDEFERRED



4Service Instantiation(reuse existing ran nssinsi) OOF should return slice profiles with Coverage Area to coverageAreaTAList mapping OOFNOT STARTED

Status
colourBlue
titleDEFERRED

Prerequisite: CPS needs to be preloaded with coverage Area TA listUUI is having discrepancy with TA Mapping as List
5Service Instantiation(reuse existing ran nssi)SDNR integration with  CPS - modify allocate flow: CPS should be updated with the RAN configurations  SDN-R, CPS

Status
colourGreen
titleNOT STARTEDcompleted

Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done,

  • Configure SDN-R to support Config DB (ran-slice-api-dg.properties)
  • Trigger (UUI) and complete the allocate flow with ConfigDB
  • Manually preload the initial RAN NF configuration and RAN Slice (RAN NF NSSI) configuration in CPS 
  • Configure SDN-R to support CPS (ran-slice-api-dg.properties)
  • Trigger the E2E Slice shared flow from UUI
  • Verify the results

6Service Instantiation(reuse existing ran nssi)SDN-R sends relevant (netconf) messages to RAN-NFs and update the relevent cells SDN-R, CPS, RANSimulator

Status
colourGreen
titleNOT STARTEDcompleted

Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done,

  • Configure SDN-R to support Config DB (ran-slice-api-dg.properties)
  • Trigger (UUI) and complete the allocate flow with ConfigDB
  • Manually preload the initial RAN NF configuration and RAN Slice (RAN NF NSSI) configuration in
CPS and RAN Simulator
  • CPS 
  • Configure SDN-R to support CPS (ran-slice-api-dg.properties)
  • Trigger the E2E Slice shared flow from UUI
  • Verify the results

7Service ActivationRequired details should be properly queried from CPS SDN-R, CPS

Status
colourBlue
titleNOT STARTEDdeferred

Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done, preload the RAN Slice configuration in CPS 
8Service ActivationRAN Slice should be activated: status should be set to ACTIVE in honeycomb devicesSDN-R, CPS, RANSimulator

Status
colourBlue
titleNOT STARTEDdeferred

Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done, preload the RAN Slice configuration in CPS and RAN Simulator
9Service DeactivationRequired details should be properly queried from CPS SDN-R, CPS

Status
colourBlue
titleNOT STARTEDdeferred

Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done, preload the RAN Slice configuration in CPS 
10Service DeactivationRAN Slice should be deactivated: status should be set to INACTIVE in honeycomb devicesSDN-R, CPS, RANSimulator

Status
colourBlue
titleNOT STARTEDdeferred

Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done, preload the RAN Slice configuration in CPS and RAN Simulator
11Service TerminationRemove the RAN slice details from CPS from the applicable NFsSDN-R, CPS

Status
colourGreen
titleNOT STARTEDcompleted

Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done, preload the RAN Slice configuration in CPS
12Service TerminationRemove the RAN Slice from the RAN NFs and cellsSDN-R, CPS, RANSimulator

Status
colourGreen
titleNOT STARTEDcompleted

Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done, preload the RAN Slice configuration in CPS and RAN Simulator

...

JIRA:
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-938

NSMF driven TN Slices 

S.NoTopicDescriptionDependencyTesterStatusRemarksTest Details
1Option2 template creationDesign option2 templates in SDC and distribute it to SO & AAISDC, SO, AAI

Status
colourGreen
title

NOT STARTED

COMPLETED

Option2 templates are created and distributed successfully. Only difference from option1 templates is that TN-FH and TN-MH templates will come under NST instead of RAN-NSST
2Service Instantiation (Shared Scenario)Instantiate service instance for option2 template with resource sharing level sharedSO, OOF, AAI

Status
colourGreen
title

NOT STARTED

COMPLETED



3Service Instantiation (Non shared Scenario)Instantiate service instance for option2 template with resource sharing level non sharedSO, OOF, AAI

Status
colourGreen
title

NOT STARTED

COMPLETED



4Service ActivationActivate the communication service from UUISO, AAIkrishna moorthy 

Status
colourGreen
titleCOMPLETED



5Service TerminationTerminate the communication service from UUISO, OOF, AAI

Status
colourGreen
titleCOMPLETED



JIRA:
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-939

...

S.NoTopicDescriptionDependencyTesterStatusRemarksTest Details
1

Generate PM data

Generate closed-loop  PM data in Ransim, store the XML files in VM and send VES notification

Status
colourGreen
titleNOT STARTEDcompleted



2

Generate PM data

DataFileCollector reads the VES notification, fetches the PM xml file from the VM (SFTP) and posts it in data router

Status
colourGreen
titleNOT STARTEDcompleted



3

Generate PM data

PM Mapper reads the PM file from data router, generates PM events and posts in the message router

Status
colourGreen
titleNOT STARTEDcompleted



4Closed LoopSlice Analysis MS reads the message from message router and triggers Control Loop action towards Policy for throughput update 

Status
colourGreen
titleNOT STARTEDcompleted



5Closed LoopUpon reception of CL action from Slice Analysis MS, Policy triggers SO (RAN NSSMF) for reconfiguration of RAN resources.

Status
colourGreen
titleNOT STARTEDcompleted



6Closed LoopUpon CL trigger from Policy, SO (RAN NSSMF) triggers SDN-R for updating the throughput per Near-RT RIC.

Status
colourGreen
titleNOT STARTEDcompleted



7Closed LoopUpon receiving the reconfiguration trigger from SO, SDN-R sends the config updates to RAN-Sim.

Status
colourBlue
titleDeferred



8ReconfigureRAN-Sim updates DB and netconf servers.

Status
colourBlue
titledeferred

...

...




Closed Loop with Intelligent Slicing - This testing will be done in the upcoming release

S.NoTopicDescriptionDependencyTesterStatusRemarksTest Details
1Generate PM data

Generate intelligent slicing PM data in Ransim and send VES notifications.


Status
colourBlue
titleNOT STARTEDdeferred



2ML MS actionML microservice reads the message, calculates the maxNumberofConns per cell and posts the data on message-router.

Status
colourBlue
titleNOT STARTEDdeferred



3Slice Analysis MS action

Slice Analysis MS receives updates to maxNumberofConns per cell for each S-NSSAI from ML-MS and triggers Policy for Control Loop action



Status
colourBlue
titleNOT STARTEDdeferred



4Closed LoopUpon reception of CL action from Slice Analysis MS, Policy triggers SO (RAN NSSMF) for reconfiguration of RAN resources.

Status
colourBlue
titleNOT STARTEDdeferred



5Closed LoopUpon CL trigger from Policy, SO (RAN NSSMF) triggers SDN-R.

Status
colourBlue
titleNOT STARTEDdeferred



6Closed LoopUpon receiving the reconfiguration trigger from SO, SDN-R sends the config updates to RAN-Sim (Near-RT RIC) successfully.

Status
colourBlue
titleNOT STARTEDdeferred



7ReconfigureRAN-Sim updates DB and netconf servers.

Status
colourBlue
titleNOT STARTEDdeferred












KPI Monitoring

S.NoTopicDescriptionDependencyTesterStatusRemarksTest Details
1. KPI policy type and policy instanceCreate Kpi policy type and Kpi policy instance and deploy the policies.PolicyCompleted

2.Config Fetch from policyMention the deployed policy-id in the pom.xml of kpi-ms and the corresponding policy is fetched using the policy sidecar container during deployment and placed inside the kpi-ms container. And during the startup of the microservice the config is fetched from the policy.PolicyCompleted

Earlier the "kpi.config" was fetched from the app-config/application_config.yaml and stored in the variable kpiConfig inside the code and now when the config is fetched using the policy the config is overridden with the config fetched from policy.


3.Configurable Kpi Config.By updating the SDK version to 1.8.6 in pom.xml of KPI-MS, the config is configurable in run-time .By changing the Kpi-config value in the policy inside the /etc/policies/policy.json , the Config gets updated in the code without the need to redeploy the application.Cbs-clientCompleted









































...