Versions Compared

Key

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

...

#

Component(s)

Test Case

Status

Remarks

IT#001DCAE (SON Handler MS)SON Handler Micro-service successfully on-boarded on to DCAE

NOT YET TESTED


IT#002DCAE (SON Handler MS)SON Handler Micro-service's DB is up and the Micro-service is able to read/write data.

NOT YET TESTED


IT#003DCAE (SON Handler MS)SON Handler Micro-service is able to successfully fetch config policies from Consul.


NOT YET TESTED

IT#004OOF and PolicyOOF is able to successfully fetch config policy from Policy

NOT YET TESTED


IT#005DCAE (SON Handler MS)SON Handler Micro-service is able to successfully receive a message over DMaaP containing PM/FM data (from VES Collector)

NOT YET TESTED


IT#006

DCAE (SON Handler MS) and SDN-R

SON Handler Micro-service is able to successfully receive a message over DMaaP containing neighbor list update (from SDN-R)

NOT YET TESTED


IT#007DCAE (SON Handler MS) and Config DBSON Handler Micro-service is able to successfully fetch neighbor list details from Config DB.

NOT YET TESTED


IT#008DCAE (SON Handler MS) and OOFSON Handler Micro-service invokes REST API of OOF for PCI optimization and receives response from OOF

NOT YET TESTED

IT#009DCAE (SON Handler MS) and OOFSON Handler Micro-service invokes REST API of OOF for PCI optimization and receives response from OOF

NOT YET TESTED


IT#01009OOF and Config DBOOF is able to obtain relevant neighbor list information for optimization algorithm from ConfigDB (REST API)

NOT YET TESTED


IT#01110DCAE (SON Handler MS) and OOFSON Handler Micro-service receives optimization result from OOF (via callback URL) and sends response

NOT YET TESTED


IT#01211DCAE (SON Handler MS) and Config DBSON Handler Micro-service is able to successfully fetch PNF details from Config DB

NOT YET TESTED


IT#01312DCAE (SON Handler MS) and PolicySON Handler Micro-service is able to send PCI/neighbor list updates via DMaaP to Policy

NOT YET TESTED


IT#01413Policy and SDN-RPolicy is able to successfully send a DMaaP message (to SDN-R) with PCI/neighbor list updates.

NOT YET TESTED


IT#01514Policy and SDN-RPolicy is able to successfully receive a DMaaP message (fromSDN-R) with PCI/neighbor list update response

NOT YET TESTED


IT#01615DCAE (SON Handler MS) and PolicySON Handler Micro-service is able to receive PCI/neighbor list update response via DMaaP from Policy, process it and logs the results.

NOT YET TESTED


IT#01716

DCAE (SON Handler MS)SON Handler Micro-service is able to process FM KPI data, store as needed, and apply rules to recommend removal of a neighbor relationship.

NOT YET TESTED


IT#01817ConfigDBConfigDB established with Dublin enhancements (update single cell's details)

NOT YET TESTED


IT#01918SDN-RSDN-R receives netconf notification, updates ConfigDB for neighbor list change

NOT YET TESTED


IT#020IT#019SDN-RUpon receiving message from Policy, SDN-R sends netconf message to RAN-Sim.

NOT YET TESTED


IT#02120DCAE (VES Collector)VES Collector receives VES messages from RAN-Simulator

NOT YET TESTED


...

Test Case ID

IT#007

Test Case Name

Config DB interaction with SON-Handler MS

Description

SON Handler Micro-service is able to successfully fetch neighbor list details from Config DB.

Release

Dublin

Pre-conditions

(a) DCAE platform is up and running

(b) SON-Handler MS is online

(c) DMaaP IT#006 is upcompleted

Testing Steps


Ensure relevant DMaaP topics are created (

Steps

Expected Result

  1. Bring up ConfigDB using the installation steps. Pre-populate RAN topology data in ConfigDB using a configuration file.
  2. Post a neighbor-list change notification message (topic: PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO_OUTPUT) on DMaaP as done for IT#006.
  1. SON-Handler MS receives the DMaaP PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO_OUTPUT ), along with producer and consumers (using unauthenticated mode).message and invokes ConfigDB APIs to obtain neighbor list details for cluster formation and determination of collisions and confusions (verified via logs).


Conclusion (Pass /Fail)


Testing Lab

Winlab



Test Case ID

IT#008

Test Case Name

OOF trigger for PCI optimization

Description

SON Handler Micro-service invokes REST API of OOF for PCI optimization

Release

Dublin

Pre-conditions

(a) DCAE platform is up and running

(b) SON-Handler MS is online

(c) OOF is online

(d) IT#004 is completed.

(e) IT#005 or IT#006 is completed

Testing Steps


Steps

Expected Result

  1. Post a neighbor-list change notification message (topic: PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO_OUTPUT) on DMaaP either manually (or) using SDN-R and RAN-Simulator (or) using SDN-R and a netconf serverSON-Handler MS receives the DMaaP as done for IT#006 (or) post a DMaaP SEC_FAULT_OUTPUT message as done for IT#005. In either case, the message contents should be such that the number of resulting collisions/confusions should be more than the threshold for triggering OOF for PCI optimization.
  1. SON-Handler MS receives the DMaaP message and and processes it.
  2. After determining that the number of collisions/confusions is greater than the threshold for triggering OOF, SON-Handler triggers OOF for PCI optimization (verified by logs on SON-Handler MS and OOF sides).


Conclusion (Pass /Fail)


Testing Lab

Winlab



Test Case ID

IT#009

Test Case Name

Config DB interaction with OOF

Description

OOF is able to obtain relevant neighbor list information for optimization algorithm from ConfigDB (REST API)

Release

Dublin

Pre-conditions

(a) OOF is online

(b) ConfigDB is up and running

Testing Steps


Steps

Expected Result

  1. Configure Config-DB with the RAN topology information using a configuration file.
  2. If IT#008 is completed, either post a neighbor-list change notification message (topic: PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO_OUTPUT) on DMaaP as done for IT#006 (or) post a DMaaP SEC_FAULT_OUTPUT message as done for IT#005, else, invoke OOF's REST API for PCI optimization.
  1. OOF receives PCI optimization request, and invokes ConfigDB APIs to obtain information about the neighbors for executing the PCI optimization algorithm (verified by logs).


Conclusion (Pass /Fail)


Testing Lab

Winlab



Test Case ID

IT#010

Test Case Name

OOF trigger for PCI optimization

Description

SON Handler Micro-service receives optimization result from OOF (via callback URL) and sends response

Release

Dublin

Pre-conditions

(a) DCAE platform is up and running

(b) SON-Handler MS is online

(c) OOF is online

(d) IT#004 is completed.

(e) IT#005 or IT#006 is completed

Testing Steps


Steps

Expected Result

  1. Post a neighbor-list change notification message (topic: PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO_OUTPUT) on DMaaP as done for IT#006 (or) post a DMaaP SEC_FAULT_OUTPUT message as done for IT#005. In either case, the message contents should be such that the number of resulting collisions/confusions should be more than the threshold for triggering OOF for PCI optimization.
  1. SON-Handler MS receives the DMaaP message and and processes it.
  2. After determining that the number of collisions/confusions is greater than the threshold for triggering OOF, SON- verified via logs and DB contentsHandler triggers OOF for PCI optimization (verified by logs on SON-Handler MS and OOF sides).
  3. OOF executes PCI optimization algorithm and provides the result to SON-Handler MS using the callback URL (verified by logs on OOF and SON-Handler MS sides).


Conclusion (Pass /Fail)


Testing Lab

Winlab

...