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 16 Next »

Test Lab: Win Lab, Rutgers University

Legend:

NOT STARTED IN PROGRESS DEFERRED COMPLETED

JIRA: REQ-937 - Getting issue details... STATUS

RAN NSSMF with CPS

S.NoTopicDescriptionDependencyTesterStatusRemarksTest Details
1Service Instantiation(new ran nssi) OOF should return slice profiles with Coverage Area to coverageAreaTAList mapping OOF

NOT STARTED

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

DEFERRED

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

DEFERRED



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

NOT STARTED

Prerequisite: CPS needs to be preloaded with coverage Area TA 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

NOT STARTED

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



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

NOT STARTED

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
7Service ActivationRequired details should be properly queried from CPS SDN-R, CPS

NOT STARTED

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

NOT STARTED

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

NOT STARTED

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

NOT STARTED

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

NOT STARTED

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

NOT STARTED

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: REQ-938 - Getting issue details... STATUS

NSMF driven TN Slices 

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

NOT STARTED



2Service Instantiation (Shared Scenario)Instantiate service instance for option2 template with resource sharing level sharedSO, OOF, AAI

NOT STARTED



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

NOT STARTED



JIRA: REQ-939 - Getting issue details... STATUS

Closed Loop with CPS 

S.NoTopicDescriptionDependencyTesterStatusRemarksTest Details
1

Generate PM data

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

NOT STARTED



2

Generate PM data

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

NOT STARTED



3

Generate PM data

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

NOT STARTED



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

NOT STARTED



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

NOT STARTED



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

NOT STARTED



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

DEFERRED



8ReconfigureRAN-Sim updates DB and netconf servers.

DEFERRED




JIRA: REQ-939 - Getting issue details... STATUS

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.


DEFERRED



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

DEFERRED



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



DEFERRED



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

DEFERRED



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

DEFERRED



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

DEFERRED



7ReconfigureRAN-Sim updates DB and netconf servers.

DEFERRED











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









































  • No labels