Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 3 Next »


A detailed overview of the R11 Kohn release enhancements for the SON Use Case was presented in the LFN DTF on Nov 18, 2022.

Please see: 2022-11 - ONAP: 5G SON Use Case enhancements for Kohn Release - LF Networking - LF Networking Confluence

Here are links to the slides and recordings:

Slides: https://wiki.lfnetworking.org/download/attachments/80281686/LFN_DTF_Nov18_ONAP_SON_R11.pdf?version=1&modificationDate=1668811840000&api=v2

Recording: https://wiki.lfnetworking.org/download/attachments/80281686/video1806089153.mp4?version=1&modificationDate=1668811891000&api=v2 


Figure 1 shows the overall architecture of the SON Use Case, with the Kohn release enhancements shown in Figure 2.
For the R12 London release, the work plan is to focus on the CM Update Notification flow. 

Global use case requirement:
 [REQ-1404] 5G SON use case enhancements for London release - ONAP JIRA


There are two new requirements:

1. Generate CM VES Message which is aligned with O1 interface and models

[INT-2177] Generate O1-aligned CM VES message to support config update in CPS DB - ONAP JIRA

Modules: RAN-Sim
Description: Generate an O-RAN O1 aligned CM update notification VES message from RAN-Sim. The objective is pursue maximum alignment with O-RAN/3GPP and to the models in ONAP and RAN-Sim.

See O1 CM Update Notification VES Message - Developer Wiki - Confluence (onap.org) for more detail.


2. Process CM VES Message

[CPS-1407] Update CPS DB based on CM VES message for SON Use Case - ONAP JIRA

Modules: CPS, SDN-C, use existing DCAE VES Collector:
Description: Complete the CM update flow - set up CPS DB, process the CM VES message published by the VES Collector, update CPS DB.


Figure 1: SON Use Case flow for O1-based and A1-based control loop actions actions in ONAP Rel 11




 Figure 2: Detail of components being changed in Kohn release for O1-based and A1-based control loop actions




  • No labels