R9 Integration Testing

1

Service Instantiation(new nsi)

 OOF should return slice profiles with Coverage Area to coverageAreaTAList mapping in NSMF

DEFERRED

Prerequisite: CPS needs to be preloaded with coverage Area TA list

UUI is having discrepancy with TA Mapping as List

2

Service Instantiation(new ran nssi)

SDNR integration with  CPS - allocate flow: CPS should be updated with the RAN configurations

   SDN-R, CPS

@Sandeep Shah 

DEFERRED

TBDMT templates should be preloaded

3

Service 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

@Sandeep Shah 

DEFERRED

4

Service Instantiation(reuse nsi)

 OOF should return slice profiles with Coverage Area to coverageAreaTAList mapping 

@Deepika S 

DEFERRED

Prerequisite: CPS needs to be preloaded with coverage Area TA list

UUI is having discrepancy with TA Mapping as List

5

Service Instantiation(reuse existing ran nssi)

SDNR integration with  CPS - modify allocate flow: CPS should be updated with the RAN configurations

  SDN-R, CPS

@Ahila P 

completed

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

6

Service Instantiation(reuse existing ran nssi)

SDN-R sends relevant (netconf) messages to RAN-NFs and update the relevent cells

 SDN-R, CPS, RANSimulator

@Ahila P 

completed

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

7

Service Activation

Required details should be properly queried from CPS

 SDN-R, CPS

@YASHWANTH GANDHAPU 

deferred

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

8

Service Activation

RAN Slice should be activated: status should be set to ACTIVE in honeycomb devices

SDN-R, CPS, RANSimulator

@YASHWANTH GANDHAPU 

deferred

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

9

Service Deactivation

Required details should be properly queried from CPS

 SDN-R, CPS

@YASHWANTH GANDHAPU 

deferred

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

10

Service Deactivation

RAN Slice should be deactivated: status should be set to INACTIVE in honeycomb devices

SDN-R, CPS, RANSimulator

@YASHWANTH GANDHAPU 

deferred

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

11

Service Termination

Remove the RAN slice details from CPS from the applicable NFs

SDN-R, CPS

@Hariharan Ramanathan 

completed

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

12

Service Termination

Remove the RAN Slice from the RAN NFs and cells

SDN-R, CPS, RANSimulator

@Hariharan Ramanathan 

completed

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

1

Option2 template creation

Design option2 templates in SDC and distribute it to SO & AAI

SDC, SO, AAI

@krishna moorthy  

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

2

Service Instantiation (Shared Scenario)

Instantiate service instance for option2 template with resource sharing level shared

SO, OOF, AAI

@krishna moorthy 

COMPLETED

3

Service Instantiation (Non shared Scenario)

Instantiate service instance for option2 template with resource sharing level non shared

SO, OOF, AAI

@krishna moorthy 

COMPLETED

4

Service Activation

Activate the communication service from UUI

SO, AAI

@krishna moorthy 

COMPLETED

5

Service Termination

Terminate the communication service from UUI

SO, OOF, AAI

@krishna moorthy 

COMPLETED

1

Generate PM data

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

@Niranjana Y 

completed

2

Generate PM data

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

@Niranjana Y 

completed

3

Generate PM data

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

@Niranjana Y 

completed

4

Closed Loop

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

@Niranjana Y 

completed

5

Closed Loop

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

@Niranjana Y 

completed

6

Closed Loop

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

@Niranjana Y 

completed

7

Closed Loop

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

@Niranjana Y 

Deferred

8

Reconfigure

RAN-Sim updates DB and netconf servers.

@Niranjana Y 

deferred

1

Generate PM data

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

@Niranjana Y 

deferred

2

ML MS action

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

@Niranjana Y 

deferred

3

Slice 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

@Niranjana Y 

deferred

4

Closed Loop

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

@Niranjana Y 

deferred

5

Closed Loop

Upon CL trigger from Policy, SO (RAN NSSMF) triggers SDN-R.

@Niranjana Y 

deferred

6

Closed Loop

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

@Niranjana Y 

deferred

7

Reconfigure

RAN-Sim updates DB and netconf servers.

@Niranjana Y 

deferred

1.

 KPI policy type and policy instance

Create Kpi policy type and Kpi policy instance and deploy the policies.

Policy

@Hariharan Ramanathan 

Completed

2.

Config Fetch from policy

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

Policy

@Hariharan Ramanathan 

Completed

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-client

@Hariharan Ramanathan 

Completed