Page Comparison

History

Use cases from the very beginning of O-RAN-SC required some sort of “topology” - so associations between the O-RAN Functions. At this time a topology model was discussed in ONAP. We suggest to read this the following page and its subpages:
https://wiki.onap.org/display/DW/Abstract+Topology+Model

There a terminology and also requirements are described.

That this time O-RAN-SC project has validated and implemented the ONF:TAPI-Topology data models to challenge it against the documented requirements. However, TAPI was not accepted in O-RAN Alliance. Discussions in O-RAN Alliance WG9 pointed us to https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwj6g_bt2tGIAxW9g_0HHYiVAEgQFnoECBUQAQ&url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc8345&usg=AOvVaw2318fbRzjCaWQttP35SHof&opi=89978449 . We are generating such models to deploy simulated network functions.

Objectives

This wiki should describe how the different topology models used in the industry and in O-RAN-SC can co-exist and or modified into a common direction. We are aware and to O-RAN Alliance WG10 Topology Exposure discussion.

Use case

The current discussion is driven by deployment use cases. If O-RAN network function are going to be mounted and deployed it is necessary to understand how the network functions are connected to each other for proper configuration of the interface end-points. The Topology model must answer question like:

• How many Network Functions are part of RAN and 5G-Core.

• Is an O-RU connected only to an O-DU (hierarchical) or in addition to the SMO (hybrid). Endpoint configuration and even access-control depend on the answer.

• …

Visualization on a Map

Image Added

References

Output validation

yanglint \
network_generation/model/yang/ietf-network.yang \
network_generation/model/yang/ietf-network-topology.yang \
network_generation/model/yang/o-ran-common-identity-refs.yang \
network_generation/model/yang/o-ran-sc-network.yang \
\
output/o-ran-network-operational.json