Versions Compared
compared with
Key
- This line was added.
- This line was removed.
- Formatting was changed.
...
Table of Contents |
---|
Message Flow
Diagram
PlantUML Macro |
---|
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
' PlantUML for ONAP/O-RAN pnfRegistration use case 2019-12
'
' 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 Performance Management
end title
box “Radio Access Network” #lightpink
participant "O-RAN O1 Component" as ntsim
end box
box "Service Management and Orchestration (SMO) (e.g. ONAP)" #gold
participant "Streaming Consumer\nDCAE VES Collector" as ves
participant "Data File Collector\nDCAE" as fileClient
participant "PM Data Mapper\nDCAE" as pmMapper
participant "Message Router\nDMaaP" as mr
participant "Data Router\nDMaaP" as dr
end box
box "User space" #lightblue
actor "µService, rApp\nREST client" as user
end box
autonumber 1 1 "<b>[00]"
ntsim -> ves: REST: VES:fileReady
ves -> mr: REST: Publish event \nunauthenticated.VES_NOTIFICATION_OUTPUT
loop polling for VES fileReady
fileClient -> mr: REST: Get topic \nunauthenticated.VES_NOTIFICATION_OUTPUT
end loop
mr -> fileClient: REST: fileReady content
fileClient -> ntsim: Send File upload request
ntsim -> fileClient: Respnse with file in 3GPP xml format
fileClient -> dr: Provides file in Data Router
dr -> pmMapper: fetchind data
pmMapper -> pmMapper: converting 3GPP xml file format \nto VES pm events
pmMapper -> mr: provide VES PM events on \nMessage Router for futher processing
loop polling for VES perf3gpp
user -> mr: REST: Get topic \norg.onap.dmaap.mr.PERFORMANCE_MEASUREMENTS
end loop
mr -> user: processing of performance monitoring data \nfrom the O-RAN O1 commonent
' 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!
2020-12-03 | o-ran-sc.org
end footer
skinparam backgroundColor #fefefe
skinparam backgroundColor #fefefe
'skinparam handwritten true
skinparam roundcorner 15
skinparam databaseBorderColor #444444
skinparam databaseBackgroundColor #fefefe
skinparam databaseFontColor #444444
skinparam sequence {
MessageAlign left
ArrowColor #2277dd
ArrowFontColor #444444
ActorBorderColor #444444
LifeLineBorderColor #444444
LifeLineBackgroundColor #eeeeee
BoxBorderColor #444444
GroupBorderColor #444444
GroupBackgroundColor #eeeeee
ParticipantBorderColor #444444
ParticipantBackgroundColor #ffffdd
ParticipantFontColor #444444
ActorBackgroundColor #ffffdd
'ActorFontColor DeepSkyBlue
'ActorFontSize 17
'ActorFontName Aapex
}
@enduml |
Description
- The O-RAN O1 Component sends a VES fileReady notification to the SMO
- The VES collector put the fileReady event on the Message Router (DMaaP)
- The File Collector was triggered by the fileReady event …
- … to download the file mentioned in the fileReady event.
- Via the Data Router (DMaaP) the file is forwarded to PM mapper
- The PM mapper converts the file into VES “perf3gpp” messages
- PM consumers (in your case a simple REST client) processes the VES “perf3gpp” data
Verification command
The following command reads the event content form the message bus:
HTTP-GET
BasicAuth dmaap-bc@dmaap-bc.onap.org:demo123456!
https://message-router.onap:30226/events/org.onap.dmaap.mr.PERFORMANCE_MEASUREMENTS/1/1