Radio Access Network Function
Configuration Management (CM)
Update in ONAP London Release
Feb 16, 2023
Contributors: N. K. Shankaranarayanan, Vishal Varvate, Priyank Maheshwari,
CPS Team (Toine Siebelink, Tony Finnerty et al), Murali Parthasarthy, Tarashree Mulge,
Martin Skorupski, John Keeney, Ahila Pandaram, Dharani S, Malarvizhi P, Krishna M
Companies: CapGemini, Ericsson, Wipro, highstreet technologies, Rutgers Winlab, AT&T
ONAP SON Use Case
Co-ordination, Decisions • ONAP SON Use Case focus:
Optimization (OOF)
(Policy) control loop flow for
management and optimization
of O-RAN network
Data Collection,
& Analysis
(DCAE) • Aligned with O-RAN interfaces
Action and architecture
(SDN-R)
Control loop • “ONAP Layer” maps to
A1 O1 O-RAN SMO
VES Collector
CM A1 • O1 interface supported for
RAN A1
FM O1 several ONAP releases
App Termn O1 CM
PM
CU/DU NFs • A1 interface added in Kohn
RAN-Sim (O-RAN) release
2
ONAP SON Use Case
Data Analysis,
SON Algorithm
SDN-R (SDN-C)
SON
A1 PMS
Handler
Policy Simulated
MS A1
OOF SLI RAN
A1 Policy
Control O1
RAN-Sim
Loop
FM/PM DB Config A1 RAN App
DES Change
TBDMT O1
MS Data VES CM
FM, PM, CU/DU
Lake DMI Coll O1
DMaaP NCMP
REST API
CPS DB
O1
RAN configuration
A1
datastore
3
ONAP SON Use Case – FM and PM event data
Data Analysis, Configuration (O1) and
SON Algorithm Policy Guidance (A1)
from SMO to RAN SDN-R (SDN-C)
SON
A1 PMS
Handler
Policy Simulated
MS A1
OOF SLI RAN
FM/PM to mS A1 Policy
O1
Control RAN-Sim
FM/PM DB Loop Config A1 RAN App
DES Change
TBDMT O1
MS Data VES CM
FM, PM, CU/DU
Lake DMI Coll O1
O -R A N O 1
FM, PM
DMaaP NCMP Info from RAN
REST API
CPS DB
O1
RAN configuration
A1
datastore
4
ONAP SON Use Case – CM event data
Data Analysis, Configuration (O1) and
SON Algorithm Policy Guidance (A1)
from SMO to RAN SDN-R (SDN-C)
SON
A1 PMS
Handler
Policy Simulated
MS A1
OOF SLI RAN
A1 Policy
O1
CM Notifn Control RAN-Sim
FM/PM DB to mS Loop Config A1 RAN App
DES Change
TBDMT O1
MS Data VES CM
FM, PM, CU/DU
Lake DMI Coll O1
O -R A N O 1
CM update CM Info
DMaaP NCMP from RAN
to CPS DB
REST API
CPS DB
O1
RAN configuration
A1
datastore
5
RAN NF Configuration Management
Updates: Problem formulation
• CPS DB keeps a consistent copy of RAN NF configuration
• RAN NF config change may be done by SDN-R over O1, or other mechanism
• All RAN NF config changes generate CMNotify VES event message over O1
• CPS DB consistency requires efficient updates based on CMNotify VES message
• After config update to CPS DB, CPS publishes CPS update notification on DMaaP
• Used by use case applications as needed
• CPS DB uses same yang model as RAN NF – “primary yang model”
• CPS DB can also have supplementary information:
• RAN NF config-like information which is not in the “primary” yang model
• Pending or planned config changes
• Solution for secondary yang model (using TBDMT) out of scope for London release
6
ONAP SON Use Case – London release
focus on CM update process
SDN-R (SDN-C)
SON
A1 PMS
Handler
Policy Simulated
MS A1
OOF SLI RAN
A1 Policy
O1
CM Notifn Control RAN-Sim
FM/PM DB to mS Loop Config A1 RAN App
DES Change
TBDMT O1
MS Data VES CM
FM, PM, CU/DU
Lake DMI Coll O1
O -R A N O 1
Update RAN config Generate CM VES event message
DMaaP NCMP - aligned with O-RAN O1 spec
in CPS DB
REST API - efficient - aligned with 3GPP models
CPS DB
O1 - model-driven
RAN configuration - reusable
A1
datastore
7
CM VES Event Generation
CM VES Event Message Generation
• RAN Simulator
generates a CM VES
RAN-Sim
SDN-R (SDN-C) event whenever any
Action Request config change happens
(O1-Config, A1-Policy etc) A1 Policy
A1 A1 RAN App on the RAN Simulator
O-RAN A1 whether its O1(direct) or
RAN-Sim A1(indirect) config
O1 Con Controller change request.
fi gc
han
g e Config change • As the data tree gets
O-RAN O1 CU modified, RAN simulator
VES CU/DU triggers the CM
DMaaP DU event generation and
Coll O1
N o ti f y V ES event DU
Topic: CM sends it over the
unauthenticated.SEC_3GPP_PROVISIONING_OU CU configured VES
TPUT RAN NFs collector endpoint.
• CM VES event message
format aligned with
3GPP 28.532
specification
CM VES Message Specification
RAN Simulator generates CM Notification VES message of type notifyMOIChanges (28.532 clause 11.1.1.11) which can report different types of
possible NRM updates:
• Creation and deletion of an object.
• Creation and deletion of an attribute, attribute field, attribute element and attribute field element.
• Replacement of an attribute value, attribute field value, attribute element and attribute field element.
Below are the input parameters that will be reported in notifyMOIChanges notification (from 3GPP clause 11.1.1.11.2).
Parameter Name S Information Type / Legal Values Comment
objectClass M It shall carry the ManagedEntity class name. Identifies the classe name of a common ancestor object of the objects for which changes are
reported. A MnS producer may set this parameter always to the class name of the parent of
the local root object in the MIB.
objectInstance M It shall carry the DN of the ManagedEntitiy. Identifies the instance of a common ancestor object of the objects for which changes are
reported. A MnS producer may set this parameter always to the instance of the parent of the
local root object in the MIB.
notificationId M This is an identifier for the notification, which may be See clause 11.1.1.7.2
used to correlate notifications.
notificationType M It specifies the type of provisioning management services See clause 11.1.1.7.2
related notifications. The value “notifyMOIChanges” shall
be carried.
eventTime M It indicates the MOI change event time. See clause 11.1.1.7.2
systemDN M See clause 11.1.1.7.2 See clause 11.1.1.7.2
mOIChanges M SEQUENCE OF SET {notificationId (M), This parameter describes the NRM updates to be reported. The notificationId is an identifier of
correlatedNotifications (O), additionalText (O), one MOI change. The path specifies the MOI created or deleted, or the MOI with replaced
sourceIndicator (O), path (M), operation (M), value (CM)} attribute values. The path may identify also parts of an attribute in case the attribute is a
structured data type. … See 3GPP clause 11.1.1.11.2 for remaining text …
10
CM VES Event Message Format
• We have a fully specified sample for O-RAN O1 CM VES event message format (Thanks to @Martin and
@John!)
• Details will be refined in ongoing implementation work.
• We hope it will be useful to other projects, and will plan to contribute example to O-RAN O1 Spec (Annex)
11
CM VES Event Message
• Selected fields showing object and its attribute change (“isHOAllowed” modified with new value
as “true”)
{
"event": {
"commonEventHeader": {
"domain": "stndDefined",
"version": "4.0.1",
"vesEventListenerVersion": "7.2"
},
"stndDefinedFields": {
"schemaReference": "https://forge.3gpp.org/rep/sa5/MnS/blob/Rel16/OpenAPI/provMnS.yaml#/components/schemas/
NotifyMoiChanges",
"data": {
"href": "172.16.100.130",
"notificationId": 1,
"notificationType": "notifyMOIChanges",
"eventTime": "2021-08-23T11:52:10.6Z",
"systemDN": "xyz",
"moiChanges": [
{
"notificationId": 123,
"correlatedNotifications": [],
"additionalText": "AdditionalTextDetails",
"sourceIndicator": "MANAGEMENT_OPERATION",
"path": "/restconf/data/ran-network:ran-network/NearRTRIC=22/
GNBCUCPFunction=cucpserver2/NRCellCU=15549/NRCellRelation=14427/isHOAllowed",
"operation": "REPLACE",
"value": {
"isHOAllowed": "true"
}}]
}}}
CPS DB CM Update
CPS Components
CPS – Configuration and Persistency Service
NCMP – Network Configuration Model Proxy
NCMP CPS-Core DMI – Data Model Inventory
CPS
DMI-Plugin Data
Store
Device
CPS Datastore CM Update
DMI Data AVC
• DMI Data AVC follows the RFC-8641 specification
(Subscription to YANG Notifications for Datastore Updates)
{
"eventId" : "9999",
“eventCorrelationId” : “cmhandleId-001”,
"eventTime" : "2021-11-16T16:42:25-04:00",
"eventSource" : "org.onap.ncmp",
"eventType" : "org.onap.ncmp.cm-network-avc-event",
”eventSchema” : “org.onap.ncmp:cm-network-avc-event.rfc8641",
”eventSchemaVersion” : “1.0",
"event": {
<RFC 8641-yang-datastore-notification-payload>
}
}
DMI Data AVC Example
{
"eventId" : "9999",
“eventCorrelationId” : “cmhandleId-001”,
"eventTime" : "2022-12-16T16:42:25-04:00",
"eventSource" : "ncmp-datastore:passthrough-operational",
"eventType" : "org.onap.ncmp.cm-network-avc-event",
”eventSchema” : “org.onap.ncmp:cm-network-avc-event.rfc8641",
”eventSchemaVersion” : “1.0",
"event": {
"push-change-update" : {
"datastore-changes" : {
"ietf-yang-patch:yang-patch" : {
"patch-id" : "34534ffd98", # Some unreadable patch id generated by the machine
"edit" : [
{
"edit-id" : "ded43434-1",
"operation" : "create",
"target" : "/_3gpp-common-managed-element:ManagedElement=XYZ-001/_3gpp-nr-nrm-gnbdufunction:GNBDUFunction=1/_3gpp-nr-nrm-nrcelldu:NRCellDU=1",
"value" : {
"_3gpp-nr-nrm-nrcelldu:NRCellDU" : [
{
"id" : 1,
}
]
}
}
]
}
}
}
}
}
Conclusion
• RAN rApps and use cases require availability of
consistent RAN NF configuration - provided here by CPS DB
• We have converged on a good design for CM update of RAN NF
configuration data in CPS DB
• CM VES message notification from RAN NF in alignment
with O-RAN O1 and 3GPP
• Efficient update of configuration in CPS DB based on CM VES message
• Implementation details will be finalized as part of ongoing work
• Our work should be reusable for:
• CM of RAN NF in other use cases in ONAP, OSC, LFN projects, etc
• CM of any yang-based NF in ONAP
