Page Comparison

...

Test Case ID

IT#017

Test Case Name

ConfigDB updates

Description

ConfigDB established with Dublin enhancements (update single cell's details)

Release

Dublin

Pre-conditions

(a) SON-Handler MS is online

(b) Policy is online

(c) IT#005, IT#007 and IT#011 are completedConfig DB is online and populated with RAN topology details

Testing Steps

Steps	Expected Result
Ensure SEC_MEASUREMENT_OUTPUT and DCAE_CL_OUTPUT DMaaP topics are created, along with producer and consumers (using unauthenticated mode) Post a sequence of PM messages (REST) to VES Collector. If feasible, use the RAN-Simulator to post the PM message.	SON-Handler MS receives the DMaaP messages with topic SEC_MEASUREMENT_OUTPUT from VES Collector. SON-Handler MS stores the information as needed, processes and determines neighbors to be removed based on the handover metrics. SON-Handler MS then sends a DMaaP message with topic DCAE_CL_OUTPUT to Policy containing details of the neighbors to be removed (verified via logs)Invoke the ConfigDB API to update single cell's details - this can be done manually or by executing the steps for IT#013.	ConfigDB updates the details of the cell as received in the API request (verified by viewing the DB contents).

Conclusion (Pass /Fail)

Testing Lab

Winlab

Test Case ID

IT#018

Test Case Name

Netconf interface of SDN-R (notification)

Description

SDN-R receives netconf notification, updates ConfigDB for neighbor list change

Release

Dublin

Pre-conditions

(a) Config DB is online and populated with RAN topology details

(b) SDN-R is up and running

(c) (RAN) devices are mounted on to SDN-R

Testing Steps

Steps	Expected Result
Send a netconf message for neighbor list change to SDN-R. This may be done using a netconf server, or using the RAN-Simulator.	SDN-R receives the netconf message successfully (verified via logs). SDN-R processes the message and updates ConfigDB with the received neighbor list updates (verified by viewing ConfigDB contents).

Conclusion (Pass /Fail)

Testing Lab

Winlab

Test Case ID

IT#019

Test Case Name

Netconf interface of SDN-R (edit-config)

Description

Upon receiving message from Policy, SDN-R sends netconf message to RAN-Sim.

Release

Dublin

Pre-conditions

(a) SDN-R is up and running

(b) (RAN) devices are mounted on to SDN-R

Testing Steps

Steps	Expected Result
Send a DMaap message to SDN-R with topic SDNR-CL containing details of PCI/neighbor list updates. This can be done by executing the steps for IT#013, or by manually sending a DMaaP message (after ensuring DMaaP topic creation, and registration of producer/consumer).	SDN-R successfully receives the DMaaP message with topic SDNR-CL (verified via logs). SDN-R sends a netconf edit-config message to RAN-Sim (or netconf server) with details of the PCI/neighbor updates.

Conclusion (Pass /Fail)

Testing Lab

Winlab

Test Case ID

IT#020

Test Case Name

Netconf interface of SDN-R (edit-config)

Description

VES Collector receives VES messages from RAN-Simulator

Release

Dublin

Pre-conditions

(a) SDN-R is up and running

(b) (RAN) devices are mounted on to SDN-R

Testing Steps

Steps	Expected Result
Send a DMaap message to SDN-R with topic SDNR-CL containing details of PCI/neighbor list updates. This can be done by executing the steps for IT#013, or by manually sending a DMaaP message (after ensuring DMaaP topic creation, and registration of producer/consumer).	SDN-R successfully receives the DMaaP message with topic SDNR-CL (verified via logs). SDN-R sends a netconf edit-config message to RAN-Sim (or netconf server) with details of the PCI/neighbor updates.

Conclusion (Pass /Fail)

Testing Lab

Winlab

...

Versions Compared

Old Version 15

New Version 16

Key