Versions Compared

Old Version 18

changes.mady.by.user Swaminathan Seetharaman

Saved on

compared with

New Version 19

changes.mady.by.user Swaminathan Seetharaman

Saved on

Key

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

...

Test case IDComponentsTest caseStatus
POLICY_OOF_PAIRWISE_001Policy, OOF(Initial) Configuration of OOFNot tested
POLICY_PCIMS_PAIRWISE_001Policy, PCI-MS(Initial) Configuration of PCI-MSNot tested
SDNR_RAN_PAIRWISE_001SDN-R, RAN (Sim)

Connecting SDN-R with RAN (Sim) (netconf servers)

Not tested
SDNR_RAN_PAIRWISE_002SDN-R, RAN (Sim)

Receiving neighbor list change notification from RAN

Not tested
SDNR_PCIMS_PAIRWISE_001SDN-R, PCI-MS

Handle neighbor list change notification from SDN-R

Not tested
SDNR_PCIMS_PAIRWISE_002SDN-R, PCI-MSConfig DB API accesaccess (for getNbrList)Not tested
OOF_PCIMS_PAIRWISE_001OOF, PCI-MSRequest for PCI optimizationNot tested
OOF_SDNR_PAIRWISE_001OOF, SDN-RConfig DB API access (for getNbrList)Not tested
OOF_PCIMS_PAIRWISE_002OOF, PCI-MSPCI optimization resultNot testedOOF_



Test Case ID

Anchor
POLICY_OOF_PAIRWISE_001
POLICY_OOF_PAIRWISE_001
POLICY_OOF_PAIRWISE_001

Test Case Name

Configuration of OOF


Description

Test if the OOF is onboarded and configuration policies are fetched and loaded correctly (Step 1c of flow)

Release

Casablanca

Pre-conditions

(a) Policy module is onboarded.

(b) Config policies related to OOF are provisioned properly in Policy module.

Testing Steps

Steps

Expected Result

  1. Bring up the OOF using the installation steps.
  2. Check the OOF database to see the contents of the OOF config policy for PCI optimization use case.
  1. OOF comes online and the database and local datastructures for PCI optimization use case are initialized correctly.
  2. Config-policy is correctly fetched and stored in the OOF DB.
    Sample config policy contents are given below:
    ALGO_CATEGORY:OOF-PCI-OPTIMIZATION
    PCI_OPTMIZATION_ALGO_NAME:OOF-PCI-OPTIMIZATION-LEVEL1
    PCI_OPTIMIZATION_NW_CONSTRAINT:MAX5PCICHANGESONLY
    PCI_OPTIMIZATION_PRIORITY: 2
    PCI_OPTIMIZATION_TIME_CONSTRAINT:NONE

Conclusion (Pass /Fail)


Testing Lab

https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine

...

Test Case ID

Anchor
OOF_PCIMS_PAIRWISE_001
OOF_PCIMS_PAIRWISE_001
OOF_PCI_PAIRWISE_001

Test Case Name

Request for PCI optimization

Description

Request for PCI optimization algorithm to be executed by OOF to address PCI collision/confusion

Release

Casablanca

Pre-conditions

(a) PCI-MS has fetched the config policies successfully from the Policy module.

(b) (SDN-R) Config DB should be populated with the details of the cells in the network.

(c) SDNR_PCIMS_PAIRWISE_002 has been completed (otherwise some dummy code for REST API call to OOF to be written in PCI-MS).

Testing Steps

Steps

Expected Result

  1. After receiving neighbor list change notification from SDN-R, PCI-MS processes it and determines OOF to be called.
  2. PCI-MS invokes the OOF PCI API (https://{host}:{port}/api/oof/v1/pci) for executing the PCI optimization.
    An example of the API contents is available in PCI Optimization API


OOF accepts the API request and sends a 200 OK response. An example of the (synchronous) response contents is available in PCI Optimization API

Conclusion (Pass /Fail)


Testing Lab

https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine

Test Case ID

Anchor
OOF_SDNR_PAIRWISE_001
OOF_SDNR_PAIRWISE_001
OOF_SDNR_PAIRWISE_001

Test Case Name

Request for PCI optimization

Config DB API access by OOF

Description

Request

Accessing Config DB APIs by OOF for PCI optimization algorithm

to be executed by OOF to address PCI collision/confusion

execution

Release

Casablanca

Pre-conditions

(a)

PCI-MS

OOF has fetched the config policies successfully from the Policy module.

(b)

(SDN-R) Config DB should be populated with the details of the cells in the network.(c) SDNR

OOF_PCIMS_PAIRWISE_

002

001 has been completed successfully (otherwise some dummy code for REST API call to

OOF

Config DB to be written in

PCI-MS

OOF).

Testing Steps

Steps

Expected Result

  1. After receiving
neighbor list change notification from SDN-R, PCI-MS processes it and determines OOF to be called.
  • PCI-MS invokes the OOF PCI API (https://{host}:{port}/api/oof/v1/pci) for executing the PCI optimization.
    An example of the API contents is available in PCI Optimization API
    1. a request for PCI optimization, OOF does a Config DB API query for getting the cellList (for a given networkID) and nbrList (for the set of cells sent in the PCI optimization request by PCI-MS).
    2. API contents are available in https://wiki.onap.org/download/attachments/28382769/5GUseCase_OOFPCI_SDN_R_Impacts_v_0_11.docx?api=v2


    SDN-R accepts the API and sends a response with the requested details.

    OOF accepts the API request and sends a 200 OK response. An example of the (synchronous) response contents is available in PCI Optimization API

    Conclusion (Pass /Fail)


    Testing Lab

    https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine

    Test Case ID

    Anchor
    OOF_PCIMS_PAIRWISE_002
    OOF_PCIMS_PAIRWISE_002
    OOF_PCI_PAIRWISE_002

    Test Case Name

    Request for
    PCI optimization result reported by OOF to PCI-MS

    Description

    Request for
    PCI optimization
    algorithm to be executed
    result sent by OOF to
    address PCI collision/confusion
    PCI-MS via REST call.


    Release

    Casablanca

    Pre-conditions

    (a)

    PCI-MS

    OOF has fetched the config policies successfully from the Policy module.

    (b) (SDN-R) Config DB should be populated with the details of the cells in the network.

    (c)

    SDNR

    OOF_PCIMS_PAIRWISE_

    002

    001 has been completed (otherwise some dummy code for REST API call to

    OOF

    PCI-MS to be written in

    PCI-MS

    OOF).

    Testing Steps

    Steps

    Expected Result

    1. After
    receiving neighbor list change notification from SDN-R, PCI-MS processes it and determines OOF to be called.PCI-MS invokes the OOF PCI API (https://{host}:{port}/api/oof/v1/pci) for executing the PCI optimization
    1. executing the PCI optimization algorithm, OOF invokes the callback API provided by the PCI-MS in the PCI optimization request API call. This API contains the results of the PCI optimization, i.e., the cells whose PCI values should be modified.
    2. An example of the API contents is available in PCI Optimization API
    OOF

    PCI-MS accepts the API

    request

    and sends a 200 OK response.

    An example of the (synchronous) response contents is available in PCI Optimization API


    Conclusion (Pass /Fail)


    Testing Lab

    https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine