You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 23
Next »
| Showcase VNF | Test Environment | Integration Team Liaison |
|---|
|
| |
Development Status
| Project | PTL | JIRA Epic / User Story* | Requirements |
|---|
| AAI | |
| - 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)
|
| DCAE | | - 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
- US DCAEGEN2-1116: Preparation steps for onboarding of SON Handler MS
|
- SON Handler Microservice shall be onboarded onto DCAE (DCAEGEN2-1109)
- A VES Collector shall accept FM/PM VES messages from RAN Simulator and publish to DMaaP - DCAEGEN2-1110
- SON Handler microservice shall filter for specific alarms (e.g. PCI Confusion) and trigger OOF Optimization as needed - DCAEGEN2-1109
- 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
- The SON Handler microservice shall filter specific FM/PM messages published by the VES Collector and write to the FM/PM database. DCAEGEN2-1109
- 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
- Microservice shall support centralized ANR SON functionality to modify neighbor cell relations based on handover KPIs. DCAEGEN2-1109
|
| OOF | | - US - OPTFRA-416
|
- OOF PCI Solver and interface shall support at least two optimization objectives (e.g. minimize changes, minimize PCI confusion)
- OOF PCI Solver policy shall use a PCI range specified in the configuration policy
- 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 | | EPIC POLICY-1438 US POLICY-1463: US POLICY-1464: | EPIC POLICY-1438 - US POLICY-1463:
- 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)
- Policy CLC shall co-ordinate between PCI SON Control Loop (CL) and some other control loops (CL) which are acting on the same cells.
- US POLICY-1464: Covers all additional/changed configuration related aspects, for e.g., algorithm names/constraints for optimization (e.g., minimize number of PCI values used, minimize number of changes), thresholds, etc.
Note: Including CLAMP for Dublin is not recommended based on guidance from Policy and DCAE PTLs.
|
| SDC | |
| - SON Handler Microservice shall be onboarded manually and not via SDC (as agreed with DCAE PTL)
|
| SDNC | | (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 | - SDNC-430: Modify RAN informational model and yang model for RAN
- SDNC-431: Implement config DB and REST API which can be used by ONAP component. API shall support all CRUD operations. Schema and data model shall be aligned with A&AI.
- 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-433: Receive netconf notification from RAN, update configDB, and publish change on DMaaP
|
| (RANSim) |
|
| - RANSim shall send FM/PM data (e.g. PCI confusion alarm, Handover KPI) to VES Collector
- Provide UI support to ANR updates @sa
|
*Each Requirement should be tracked by its own User Story in JIRA
Integration Testing
Current Status
Testing Blockers
- High visibility bugs
- Other issues for testing that should be seen at a summary level
- Where possible, always include JIRA links
Note: DMaaP should be setup for most of the test cases below.
| # | Component(s) | Test Case | Status |
|---|
| 1 | DCAE (SON Handler MS) | SON Handler Micro-service successfully on-boarded on to DCAE | |
| 2 | DCAE (SON Handler MS) | SON Handler Micro-service's DB is up and the Micro-service is able to read/write data. | |
| 3 | DCAE (SON Handler MS) | SON Handler Micro-service is able to successfully fetch config policies from Consul. | |
| 4 | DCAE (SON Handler MS) and |
|
|
| 3 | DCAE (SON Handler MS) and Config DB | SON Handler Micro-service is able to successfully fetch neighbor list details from Config DB. | |
| 4 | DCAE (SON Handler MS) | SON Handler Micro-service is able to successfully fetch PNF details from Config DB. | |
| 5 | DCAE (SON Handler MS) and OOF | SON Handler Micro-service invokes REST API of OOF for PCI optimization and receives response from OOF via callback URL | |
| 6 | DCAE (SON Handler MS) and OOF | SON Handler Micro-service invokes REST API of OOF for Joint PCI/ANR optimization and receives response from OOF via callback URL | |
| 7 |
|
|
|
Use Case Testing - End to End flow to be Tested
**This should be a summary level Sequence diagram done in Gliffy**
Test Cases and Status
| # | Test Case | Status |
|---|
| 1 | There should be a test case for each item in the sequence diagram | |
| 2 | create additional requirements as needed for each discreet step | |
| 3 | Test cases should cover entire Use Case | |
| 4 | Test Cases should include enough detail for testing team to implement the test | |
