Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Table of Contents |
---|
This page is related to Jira
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
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
Use cases
Requirements