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

Compare with Current View Page History

« Previous Version 5 Next »

7

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
  • ...


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

  • No labels