You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

This page is related to Jira ONAPMODEL-35 - Getting issue details... STATUS . 


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

LicenseApache 2.0Abstract Topology Model AbstractTopology Top UUID IdentifierString NameString LabelENUM LifeCycleStateENUM OperationalStateENUM AdminstrativeState Topology Node Edge Path hasNodes* hasEdges* hasPaths* hasChildren* hasNeighborsOfSameType* hasChildren* refrencesNodesOfSameType12 referencesLinks1*Thanks to plantUml!2021-01-29 | onap.org

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
Domain
Association
Link
Point
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
  • No labels