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

Compare with Current View Page History

« Previous Version 6 Next »


Test Lab: Winlab

Legend:

NOT STARTED IN PROGRESS DEFERRED COMPLETED

JIRA: https://jira.onap.org/browse/REQ-1159

S. No

Test Case

Description

Priority

Dependency/Issue

Tester

Status

Remarks

Test Details

1.Initial ConfigurationRANSIM loads O-RAN model initial data and displays the cell, cell neighbors and cell data configuration in the UI.1

NOT STARTED



2.Initial ConfigurationRANSIM must send the initial data configuration to honeycomb according to the ORAN Alignment1


IN PROGRESS




3.Trigger Collision/Confusion

RANSIM will send  the new neighbors and the Fault message to honeycomb if addition of new neighbors to a cell causes a Collision/Confusion in the UI.(Will send only the new neighbor data if there is no collision/confusion)

1

NOT STARTED



4.Trigger Collision/ConfusionHoneycomb(using ORAN model) stores the neighbor change and sends the Fault Notification message to VES.1

NOT STARTED



5.PCI closed loopSON-Handler receives the FM message(through Dmaap). Triggers OOF for optimization result, and triggers Closed Loop action towards Policy.1

NOT STARTED

Prerequisite:

  1. Data should be loaded in CPS
  2. TBDMT templates should be preloaded

6.PCI closed loopPolicy starts Closed Loop. Sends notification to SDNR(through DMAAP) to configure the PCI of the cells in the payload and waits for a response from SDNR to complete the Closed Loop.1

NOT STARTED



7.PCI closed loopSDNR configures the PCI of the cells in the payload(in honeycomb), updates the CPS and send sends success response to Policy.1

NOT STARTED

Prerequisite:

  1. Data should be loaded in CPS
  2. TBDMT templates should be preloaded

8.ReconfigureHoneycomb sends the data of the cells whose PCI have been reconfigured to RANSIM.1

NOT STARTED



9.ReconfigureRANSIM updates the DB and the UI shows the collision/confusion as resolved.1

NOT STARTED



  • No labels