You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 4
Next »
Showcase VNF | Test Environment | Integration Team Liaison |
---|
|
| |
Development Status
Project | PTL | JIRA Epic / User Story* | Requirements |
---|
AAI | |
| - May need to add attributes for 5G DU and 5G CU PNF / VNF objects. (TBD).
|
DCAE | Vijay Venkatesh Kumar |
| - DCAE should onboard PCI Handler Microservice
- Collector should accept FM/PM messages from RAN Simulator and publish to DMaaP
- PCI-Handler microservice should process PCI Collision and PCI Confusion messages and trigger OOF Optimization as needed.
- Microservice should support ANR function
|
OOF | |
| - OOF PCI Algorithm should support different optimization objectives (e.g. minimize changes, minimize confusion)
- OOF should support joint PCI and ANR function
|
Policy | | | - Policy module should 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 should co-ordinate between PCI SON Control Loop (CL) and other control loops (CL) acting on the same PNF or VNF
|
SDC | |
| - PCI Handler Microservice should 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.
|
*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 | |