The OAM architecture is defined by WG1 in the O-RAN OAM architecture document. WG2 clarified the function split between non-real-time-RIC and an Orchestrator FCAPS Framework. Please see the attached document.
According to the O-RAN-OAM-interface specification (O1) each MnS Provider (ME) implements a (TLS/)NetConf interface for Configuration Management and consumes TLS/HTTP-POST messages with a json body in VES message format.
The method for the VES subscription/un-subscription must be performed via NetConf, because VES itself does not provide such function. The MnS Consumer will use the NetConf interface for such an operation.
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
' Copyright 2020 highstreet technologies GmbH
' Licensed under the Apache License, Version 2.0 (the "License");
' you may not use this file except in compliance with the License.
' You may obtain a copy of the License at
'
' http://www.apache.org/licenses/LICENSE-2.0
'
' Unless required by applicable law or agreed to in writing, software
' distributed under the License is distributed on an "AS IS" BASIS,
' WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
' See the License for the specific language governing permissions and
' limitations under the License.
@startuml
' Diagram
title
O-RAN-SC
O1-interface Component Architecture
end title
node "\nManagement-Service (MnS) Consumer\nOAM Controller" #gold {
interface "TLS/HTTP" as http
[VES-Provider] -down-> http: provides
[NetConf Client] as ncc
}
node "\nManagement-Service (MnS) Provider\nManagedElement" #lightpink {
interface "TLS/NetConf" as nc
[NetConf Server] -up-> nc: provides
[VES Consumer] .up.> http: <font color=#222222>use
[VES Consumer] -[hidden]left- [NetConf Server]
}
ncc .down.> nc: <font color=#222222>use
' End Diagram
' Format
header
<b><font color=#8888ff>License</font></b>
<b><font color=#8888ff>Apache 2.0</font></b>
end header
right footer
Thanks to plantUml!
2019-07-16 | o-ran-sc.org
end footer
skinparam backgroundColor #fefefe
'skinparam handwritten true
skinparam roundcorner 15
skinparam componentStyle uml2
skinparam databaseBorderColor #444444
skinparam databaseBackgroundColor #fefefe
skinparam databaseFontColor #444444
skinparam component {
BorderColor #666666
BackgroundColor #fefefe
}
skinparam interface {
BorderColor #666666
BackgroundColor #fefefe
FontColor #fefefe
}
skinparam node {
FontColor #ffffff
}
skinparam sequence {
MessageAlign left
ArrowColor #2277dd
ArrowThickness 3
ArrowFontColor #444444
ActorBorderColor #444444
LifeLineBorderColor #444444
LifeLineBackgroundColor #eeeeee
BoxColor #444444
BoxBorderColor #444444
GroupBorderColor #444444
GroupBackgroundColor #eeeeee
ParticipantBorderColor #444444
ParticipantBackgroundColor #ffffdd
ParticipantFontColor #444444
ActorBackgroundColor #ffffdd
'ActorFontColor DeepSkyBlue
'ActorFontSize 17
'ActorFontName Aapex
}
@enduml
|
In the meeting from 2019-08-26 was clarified the expected integration of the OAM Architecture into a Service Management and Orchestration Framework (SMO).
The VES collectors will receive the VES messages of the O1 interface.
