...
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.
| PlantUML Render Macroplantuml |
|---|
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Copyright 2019 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 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. ' ' Author: martin.skorupski@highstreet-technologies.com @startuml ' Diagram title O-RAN-SC O1-Interface: VES Subscription architecture end title node "\nManagement-Service (MnS) Consumer\nOAM Controller" #8064A2 { interface "TLS/HTTP" as http [VES Server] -down-> http: provides [NetConf Client] as ncc } node "\nManagement-Service (MnS) Provider\nManagedElement" #ED7D31 { interface "TLS/NetConf" as nc [NetConf Server] -up-> nc: provides [VES Client] .up.> http: <font color=#222222>use [VES Client] -[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 'caption "\n UML Formatting" right footer VES Subscription Thanks to plantUml! 2019-07-16 | o-ran-sc.org end footer skinparam backgroundColor #fefefe skinparam backgroundColor #fefefe 'skinparam handwritten true skinparam roundcorner 15 skinparam componentStyle uml2 skinparam component { BorderColor #666666 BackgroundColor #fefefe } skinparam interface { BorderColor #666666 BackgroundColor #fefefe FontColor #fefefe } skinparam databaseBorderColor #666666 skinparam databaseBackgroundColor #fefefe skinparam databaseFontColor #666666 skinparam node { FontColor #ffffff } skinparam sequence { MessageAlign left ArrowColor #fefefe ArrowFontColor #fefefe ArrowThickness 2.5 ActorBorderColor #666666 LifeLineBorderColor #666666 LifeLineBackgroundColor #eeeeee BoxBorderColor #666666 GroupBorderColor #666666 GroupBackgroundColor #eeeeee ParticipantBorderColor #666666 ParticipantBackgroundColor #ffffdd 'ParticipantFontName Impact 'ParticipantFontSize 17 ParticipantFontColor #666666 ActorBackgroundColor #ffffdd 'ActorFontColor DeepSkyBlue 'ActorFontSize 17 'ActorFontName Aapex } @enduml |
Integration into SMO
In the meeting from 2019-08-26 was clarified the expected integration of the OAM Architecture into a Service Management and Orchestration Framework (SMO).
...