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

Compare with Current View Page History

« Previous Version 13 Next »




This use case started in Casablanca Release. We have carryover items and enhancements. Please see 5G - OOF (ONAP Optimization Framework) and PCI (Physical Cell ID) Optimization for the base wiki page for this use case.

Showcase VNFTest Environment

Integration Team Liaison







Development Status

ProjectPTLJIRA Epic / User Story*Requirements
AAI
James Forsyth

  1. No impact. ConfigDB objects for pnf shall be aligned with with A&AI (e.g. use the same primary key for pnf, which is expecte to be pnf-id)
DCAEVijay Venkatesh Kumar
  • Epic: DCAEGEN2-1108: DCAE Support for OOF-PCI solution
  • US DCAEGEN2-1109: Onboard SON Handler microservice to DCAE
  • US DCAEGEN2-1110: VES Collector for FM/PM data from RAN-SIM PNFs
  • US DCAEGEN2-1111: FM/PM Database for SON solution
  1. SON Handler Microservice shall be onboarded onto DCAE (DCAEGEN2-1109)
  2. A VES Collector shall accept FM/PM VES messages from RAN Simulator and publish to DMaaP - DCAEGEN2-1110
  3. SON Handler microservice shall filter for specific alarms (e.g. PCI Confusion) and trigger OOF Optimization as needed - DCAEGEN2-1109
  4. Implement PostgreSQL database to store FM/PM data and any other data needed by the SON Handler Microservice. This database provide a query interface so that the SON Handler MS can read and write data. - DCAEGEN2-1111
  5. The SON Handler microservice shall filter specific FM/PM messages published by the VES Collector and write to the FM/PM database. DCAEGEN2-1109
  6. The SON Handler MS interfaces to Policy, OOF, SDN-C, ConfigDB shall be modified as needed by DCAE onboarding. e.g. MS shall receive configuration policy via DCAE Controller - DCAEGEN2-1109
  7. Microservice shall support centralized ANR SON functionality to modify neighbor cell relations based on handover KPIs. DCAEGEN2-1109
 OOF
 Sarat Puthenpura

  1. US - OPTFRA-416
  2. OOF PCI Solver and interface shall support at least two optimization objectives (e.g. minimize changes, minimize PCI confusion)
  3. OOF PCI Solver policy shall use a PCI range specified in the configuration policy
  4. OOF shall provide a joint PCI/ANR solver which will optimize PCI and also recommend a removal of a neighbor relation if there PCI allocation is difficult for a cell which also has a neighbor link for which the successful_handover KPI is below a pre-specified threshold
 Policy
 Pamela Dragosh


  1. Policy module shall support handling of partial success where only some of the PCI change actions from a set of changes are successful (e.g. allow partial changes, revert to previous state)
  2. Policy CLC shall co-ordinate between PCI SON Control Loop (CL) and some other control loops (CL) which are acting on the same cells.
  3. Need to check use of Policy designer, and also CLAMP
 SDC
 Michael Lando

  1. SON Handler Microservice shall be added to SDC Catalog to support DCAE onboarding
 SDNC
 Dan Timoney

(Carryover items from Dublin)

-SDNC-430: Modify RAN informational model and yang model for RAN
-SDNC-431: Implement config DB and REST API (SDN-R / OOF interface)
-SDNC-432: Interfacing SDN-R with Policy
•Receive DMaaP message in CL format from Policy (Modify Config message using existing LCM API), send netconf message changing PCI value to cellID as specified, update config DB, and publish change on DMaaP (DMaaP client is available and can be called)
-SDNC-432: Receive netconf notification from RAN, update configDB, and publish change on DMaaP

  1. SDNC-430: Modify RAN informational model and yang model for RAN
  2. SDNC-431: Implement config DB and REST API (SDN-R / OOF interface).
    NOTE: ConfigDB work should align with larger Controller and configuration projects/use cases.
  3. SDNC-432: Interfacing SDN-R with Policy - Receive DMaaP message in CL format from Policy (Modify Config message using existing LCM API), send netconf message changing PCI value to cellID as specified, update config DB, and publish change on DMaaP (DMaaP client is available and can be called)
  4. SDNC-433: Receive netconf notification from RAN, update configDB, and publish change on DMaaP
  5. SDNC should maintain an operational database and configuration database. May be a modification of SDNC-431.
(RANSim)

  1. RANSim shall send FM/PM data (e.g. PCI confusion alarm, Handover KPI) to VES Collector

*Each Requirement should be tracked by its own User Story in JIRA 

Testing

Current Status

  1. Testing Blockers

  2. High visibility bugs
  3. Other issues for testing that should be seen at a summary level
  4. Where possible, always include JIRA links


End to End flow to be Tested

**This should be a summary level Sequence diagram done in Gliffy** 

Summary SeqDia Template

Test Cases and Status


#Test CaseStatus
1There should be a test case for each item in the sequence diagram

NOT YET TESTED

2create additional requirements as needed for each discreet step

COMPLETE

3Test cases should cover entire Use Case

PARTIALLY COMPLETE

4 Test Cases should include enough detail for testing team to implement the test

 FAILED

  • No labels