Radio Access Network Topology:
The picture below is an example of how the RAN may be disaggregated. It is only used
to illustrate the use case in the previous section; the specific ways and options by
which the RAN is disaggregated may be addressed by 3GPP and or other standards and is
not the focus of this use case description.
Slicing Network Topology:
ONAP Architecture for RAN Management:
Note: The ONAP architecture diagram below will be aligned with the ONAP architecture diagram for R2, when available.
Users and Benefits:
This ONAP use case enables automated lifecycle management of large scale disaggregated 5G radio access networks and E2E network slices. It also enables the deployment and life cycle management of hybrid 5G networks (a combination of PNFs and VNFs)
Project Impact:
This is a significantly broad use case and will impact all major modules of ONAP. List of enhancements in each module will have to be identified over the next several weeks.
Work Commitment:
AT&T may provide development resources but would like to collaborate with other ONAP members to fully realize this use case.
Acronyms/Glossary
SP | Service Provider |
SDC | ONAP Service Design & Creation |
DCAE | ONAP Data Collection, Analytics & Events |
SO | Service Orchestrator |
Multi-VIM interface | ONAP interface agnostic to the Virtual Infrastructure Manager used |
eMBB | Enhanced Mobile Broadband |
mIoT | Massive Internet Of Things |
URLLC | Ultra-reliable low latency communication |
SON | Self-Organizing Network |
|
|
2 Comments
Vladimir Yanover
Shekar,
Thanks for contributing the diagrams.
I need your help to understand them. Can you please provide (or point to) the functional description of the involved blocks, such as L2nrt, L1+L2rt, .... Description of the interfaces will be helpful too.
I noticed that the diagram "Radio Access Network Topology" assumes specific scheme of eNB disaggregation which is different from the CU/DU architecture published in 3GPP 38.401. We cannot therefore use 3GPP specs to understand the scheme and the terms used.
Thanks
Vladimir
Shekar Sundaramurthy
I believe the focus of the picture (from the subcase 1 contribution by Peter) was "a way" to show the disaggregated deployment for the use case. The focus of the use case and description in this forum is more on how ONAP can 'deploy' and 'slice' in such an environment and the picture is an example used for illustration. Peter - feel free to expand or clarify.