SON Use Case London Release R12 Requirements presented on 12/19/2022 in Requirements Subcommittee call: Slide deck:  ONAP_SON_R12_Requirements_20221219.pptx


An overview of the R12 London release enhancements for the SON Use Case was presented in the LFN DTF on Feb 16, 2023

LFN-DTF February 16, 2023 / Radio Access Network Function Configuration Management (CM) Update in ONAP London Release

Link: 2023-02 - ONAP: Radio Access Network Function Configuration Management (CM) Update in ONAP London Release - LF Networking - LF Networking Confluence

Slides (ppt): 20230216_LFN_DTF_Network_CM_Update.pptx

Slides (pdf): 20230216_LFN_DTF_Network_CM_Update.pdf

Recording: 20230216_LFN_DTF_Network_CM_Update_video.mp4


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

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


There are two new use case requirements:

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

[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: Focus of London release is on CM VES event message generation and CPS DB update based on CM VES event message.




  • No labels