The Base PCI (SON) Wiki is at: 5G - OOF and PCI (Casablanca carry-over items)
Weekly Meetings: OOF-SON Meetings
Frankfurt demo was given at LFN DTF Virtual F2F Meetings on June 24, 2020:
Slides: OOF_SON_Frankfurt_demo_20200624_v2.0.pptx
Recording: https://wiki.lfnetworking.org/download/attachments/40370243/
...
ONAP_5G_OOF_SON_use_case_demo.mp4?api=v2
R5 El Alto Carry-over
Two Jira carry over items in SDN-C
R6 Frankfurt development
(1) PCI ENHANCEMENTS
Enhancements of Neighbor relations.
Complete the loop, when a new cell is added A&AI update, SO W/F.
Assign a PCI for the new cell (not considered in R4).
When a nbr list is updated a collision/confusion can happen.
New Cell Additions, go through the entire life cycle; cell addition; nbr list update.
(2) NEW SON U/C -
Additional SON U/C.
(3) INTEGRATION WITH REAL SYSTEMS -
SDN-R integration with a real DU. Evolving model to align with ORAN
...
1. Functional enhancements:
- Onboard RAN-Simulator as an official ONAP component (e.g., as part of Demo VNFs repo or Integration test repo),
- Contribute to ConfigDB (or RuntimeDB) enhancements for SON use case (including any impacts in SON-Handler MS, OOF and SDN-C) => this scope currently only includes yang model driven automatic Config DB schema and API generation.
2. Alignment with O-RAN
- Netconf config (O1-CM interface), yang model sourced from OIM => this is now de-scoped as we don't have yang models from O-RAN as of Jan 20th, 2020
- VES messages for config-update notifications also => the scope only includes reception of DMaaP message by SDN-R that would be triggered when RAN sends a VES config-update message. The real VES message sending as well as reception by VES Collector in DCAE is de-scoped as we don't yet have the VES message definition from O-RAN.
3. Control Loop Co-ordination (CLC)
Demonstrate CLC with PCI and ANR CLs
4. Optimization feature enhancements (stretch goal)
Adaptive SON functionality
DEVELOPMENT IMPACTS
| PROJECT | PTL | User Story / Epic | Requirement | |||||||||||||||||||||||||||||||
| A&AI | Epic#1 - OOF/SON Enhancements | E1a: Models & relationship between Config, Operational DB & AAI | ||||||||||||||||||||||||||||||||
| AAF | ||||||||||||||||||||||||||||||||||
| APPC | ||||||||||||||||||||||||||||||||||
| CLAMP | Epic#1 - OOF/SON Enhancements | Control Loop Deployment | ||||||||||||||||||||||||||||||||
| CC-SDK | Epic#1 - OOF/SON Enhancements | Enhance Yang model to align with 3GPP and O-RAN Configuration/Operational Database, Config History (e.g. to revert changes) RAN Simulator – enhance and include in ONAP codebase* | ||||||||||||||||||||||||||||||||
| DCAE | Epic#1 - OOF/SON Enhancements | Functionality enhancement to SON Handler MS
| Other impacts to be addressed in DCAE:
Java 11 migration (Stretch goal) | |||||||||||||||||||||||||||||||
| DMaaP | NA | No impact | ||||||||||||||||||||||||||||||||
| External API | NA | No impact | ||||||||||||||||||||||||||||||||
| Integration |
| |||||||||||||||||||||||||||||||||
| MODELING | NA | No impact | ||||||||||||||||||||||||||||||||
Multi-VIM / Cloud | NA | No impact | ||||||||||||||||||||||||||||||||
| OOF | Epic#1 - OOF/SON Enhancements |
| Dynamic and static optimization, DMaaP interface, Harden the OOF features supporting SON | |||||||||||||||||||||||||||||||
| POLICY | Epic#1 - OOF/SON Enhancements |
| Enhance the Policy functionality for Control Loop Coordination | |||||||||||||||||||||||||||||||
| PORTAL | NA | No impact | ||||||||||||||||||||||||||||||||
| SDN-C | Epic#1 - OOF/SON Enhancements | SON service creation |
| Related O-RAN Jira: https://jira.o-ran-sc.org/secure/RapidBoard.jspa?rapidView=7&projectKey=OAM&view=detail&selectedIssue=OAM-9 | ||||||||||||||||||||||||||||||
| SDC | NA | No impact | ||||||||||||||||||||||||||||||||
| SO | NA | No impact | ||||||||||||||||||||||||||||||||
| VID | NA | No impact | ||||||||||||||||||||||||||||||||
| VNFRQTS | NA | No impact | ||||||||||||||||||||||||||||||||
| VNF-SDK | NA | No impact | ||||||||||||||||||||||||||||||||
| CDS | NA | No impact |
List of PTLs:Approved Projects
Test cases
| No. | Description | Involved components | Status |
1 | Successful reception and handling of DMaaP message by SDN-R with CM notification (simulated from RAN). | DMaaP, SDN-R | NOT YET TESTED |
2 | Successful update of ConfigDB with CM notification updates by SDN-R (upon reception of CM notification over DMaaP from RAN) | SDN-R, DMaaP | NOT YET TESTED |
3 | Control Loop co-ordination – denial of 2nd control loop trigger (by Policy) received from SON-Handler MS when first control loop is active | SON-Handler MS, OOF |
...
xyz
SDN-R
xyz
DCAE
xyz
POLICY
xyz
A&AI
xyz
SDC
xyz
CLAMP
...
| , Policy, SDN-R, RAN-Sim | NOT YET TESTED | ||
4 | Control Loop co-ordination – re-submitting of 2nd control loop trigger (by SON-Handler MS) and initiating appropriate actions | SON-Handler MS, Policy, SDN-R, RAN-Sim | NOT YET TESTED |
5 | Keep track of PCI updates being successfully implemented in the RAN and update DB accordingly for future optimizations. | SON-Handler MS, Policy, SDN-R, RAN-Sim | NOT YET TESTED |
6 | Trigger OOF for adaptive SON with FixedPCI cell list (by SON-Handler MS) when previous PCI updates are not implemented in the RAN | OOF, SON-Handler MS | NOT YET TESTED |
7 | Yang-model based schema and API generation for ConfigDB (PoC only) | ConfigDB | NOT YET TESTED |
Detailed Impacts
Refer to the child wiki pages for the detailed impacts.
SUPPORTING FILES
View file name OOF_SON_Frankfurt_20190913.pptx height 250
Dec 20, 2019 version of OOF-SON Frankfurt slide deck:
View file name OOF_SON_Frankfurt_20191220.pptx height 250