Versions Compared

Key

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

Table of Contents

This page is related to Jira

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyONAPMODEL-35


Motivaton

Based on discussion between ONAP and O-RAN-SC there is a need to provide a common model to µServices with respect to (network) topologies.

In previous proof-of concept and demonstrations several different topologies of different types were presented. Such use-case driven topologies have several "things" in common.  For multi topology networks based on virtual and physical network functions a view across technologies is required to optimize the network in terms of utilization and/or latency and other criteria's. 


Use case driven topology representations

Geographical Topology

Physical Topology

Ethernet Topology

PTP-Topology


Idea

The idea could be to define an ONAP topology model across all ONAP components and technologies and describe a kind of mapping to technology and/or use case specific topology models, such as:

  • PCEP
  • LLDP
  • IEEE 802.3
  • TAPI
  • OpenROADM
  • 3GPP-EP
  • IETF-Interfaces
  • ONF:LogicalTerminationPoints
  • OpenConfig
  • kubernetes (O-RAN O2?)
  • Cluster?
  • ...


Initial draft proposal

PlantUML Macro
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 
' Copyright 2021 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 
  Abstract Topology Model
end title

package AbstractTopology {
  interface Top {
    UUID Identifier
    String Name
    String Label
    ENUM LifeCycleState
        ENUM OperationalState
        ENUM AdminstrativeState
  }
  class Topology implements Top
  class Node implements Top
  class Edge implements Top
  class Path implements Top
}

Topology *--> "*" Node: hasNodes
Topology *--> "*" Edge: hasEdges
Topology *--> "*" Path: hasPaths
Node *--> "*" Node: hasChildren
Node *--> "*" Node: hasNeighborsOfSameType
Edge *--> "*" Edge: hasChildren
Edge "1" o--> "2" Node: refrencesNodesOfSameType
Path "1" o--> "*" Edge: referencesLinks


' 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! 
  2021-01-29 | onap.org
end footer

skinparam backgroundColor #fefefe

skinparam backgroundColor #fefefe
'skinparam handwritten true
skinparam roundcorner 15

skinparam class {
  BorderColor #444444
  BackgroundColor #ffffdd
  FontColor #444444
}

skinparam database {
  BorderColor #444444
  BackgroundColor #ffffdd
  FontColor #444444
}

skinparam sequence {
  MessageAlign left
  ArrowThickness 2
  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


Principals and Terminology

Principals

more ...

Visualization

It is assumed that every topology model could be visualized. The visualization is basically a case-by-case mapping of topology-nodes and topology-edges and their properties to shapes, lines, sizes, widths and colors. Therefore the topology model itself must not take the requirements for visualization into account. In some cases a kind of profile of stylesheet could describe such mapping, but it would be outside of the topology itself.


Terms and Definitions

This chapter specifies the terms used for an abstract topology model.

Term
Topology
Node
Edge
Group
link

Domain
Edge

Association
TP

Link
physical

Point
virtual

Inventory
Network
Physical
Virtual
more....


Use cases

Network Slicing

  • Transport to RAN - RAN to Transport - RAN to Core , ....

Alarm Correlation

Multi Domain Concepts

Multi Layer

O-RU recovery (from O-RAN-SC)

The O-RAN SC (Software community) defined a closed loop use case. A trigger (Fault-Notification) by O-RU is send to SMO (ONAP components are used to build the SMO layer). A µService should listen to this trigger and will perform an configuration on the corresponding O-DU.

Please see further details of the use case description:

The µService needs to know the connectivity between O-DUs and O-RUs for layer "Management Plane" to send the right configuration to the the right O-DU and with the right identification of the O-RU on O-DU level. Here a complete topology of the RAN connections on ONAP level could support such use case. The use case can be easyl enhanced by adding active and passive transport components between O-RU and O-DUs.

Requirements


Impact on ONAP components

Candidates:

  • AAI
  • CPS
  • SDC
  • CCSDK
  • DCAE