You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 11
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 | Vijay Venkatesh Kumar |
| - SON Handler Microservice shall be onboarded onto DCAE (JIRA xx)
- A VES Collector shall accept FM/PM VES messages from RAN Simulator and publish to DMaaP
- SON Handler microservice shall filter for specific alarms (e.g. PCI Confusion) and trigger OOF Optimization as needed.
- There shall be a FM/PM database (postgreSQL) for FM/PM data with a query interface to read and write data.
- The SON Handler microservice shall filter specific FM/PM messages published by the VES Collector and write to the FM/PM database.
- The SON Handler MS to Policy interfaces shall be modified as needed by DCAE onboarding. e.g. MS shall receive configuration policy via DCAE Controller
- Microservice shall support centralized ANR SON functionality to modify neighbor cell relationshbased on handover KPIs.
|
| OOF | |
| - OOF PCI Algorithm shall support different optimization objectives (e.g. minimize changes, minimize confusion, joint PCI/ANR)
- OOF shall support joint PCI and ANR functionality
|
| Policy | | | - 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.
- Need to check use of Policy designer, and also CLAMP
|
| SDC | |
| - SON Handler Microservice shall be added to SDC Catalog to support DCAE onboarding
|
| 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 (SDN-R / OOF interface).
NOTE: ConfigDB work should align with larger Controller and configuration projects/use cases. - 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 should maintain an operational database and configuration database. May be a modification of SDNC-431.
|
| (RANSim) |
|
| - 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
Testing Blockers
- High visibility bugs
- Other issues for testing that should be seen at a summary level
- Where possible, always include JIRA links
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 | |
