Versions Compared

Old Version 6

changes.mady.by.user Martin Skorupski

Saved on

compared with

New Version Current

changes.mady.by.user Martin Skorupski

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Note:

The first implementation of this use case was implemented and demonstrated for O-RAN-SC A release.

For the C release a regression test is required.



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 PNF registration 
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\nONAP DCAE VES Collector" as ves
  participant "Message bus\nONAP DMaaP" as dmaap
  participant "O1-Controller\nONAP SDN-R" as sdnr
end box

autonumber 1 1 "<b>[00]"
ntsim -> ves: REST: VES:pnfRegistration
ves -> dmaap: REST: Publish event \nunauthenticated.VES_PNFREG_OUTPUT
loop polling for VES pnfRegistration
sdnr -> dmaap: REST: Get topic \nunauthenticated.VES_PNFREG_OUTPUT
end loop
dmaap -> sdnr: REST: pnfRegistration
sdnr ->sdnr: create \nmountpoint
sdnr -> ntsim: NETCONF <hello/>-req \n[TLS,SSH]
ntsim -> sdnr:  <hello/>-res

' 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

  1. The O-RAN component sends a VES 7.1 pnfRegistration event after its startup and/or its VES end-point-configuration.
  2. The VES Collector verifies the content and forwards the event to the message bus (ONAP DMaap)
  3. After initialization and startup of the O1-controller, the O1 controller starts polling on the message bus for topic "unauthenticated.VES_PNFREG_OUTPUT" 
  4. After such topic is received by the O1 Contoller ....
  5. ... the O1 Controller checks its content, if all information to setup an NetConf connections are part of the VES message content, a mountpoint is created to automatically establish a NetConf connection. The minimal content is
    1. IP address in IPv4 or IPv6 format
    2. the NetConf port: standard port number is 830
    3. the security protocol; TLS of SSH and its user credentials
  6. Once the SSH or TLS connection is established, the standard NetConf <hello/> message is request.
  7. If the security requirements for a NetConf connection are fulfilled, the NetConf Server of the O-RAN Component exposes its NetConf APIs and NetConf features.


Verification Command

The following command should display the new mounted device and its connection-status:

Code Block
HTTP-GET 
BasicAuth admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U
Accept: application/yang-data+json

/rests/data/network-topology:network-topology/topology=topology-netconf?content=nonconfig&fields=node(node-id;netconf-node-topology:connection-status)