...
Use Case Blueprint | Sub-Blueprint | Key Updates | Benefits | |
5G | OOF SON (PCI) | First steps towards realizing Machine Learning (ML) based SON. Offline trained ML model used to provide additional inputs for PCI optimization. Provides interface for fetching PM data to determine additional inputs for SON. | Enables onboarding ML models to realize ML-based SON use cases. | |
Service Modeling & Definition | Incorporating This use case incorporated the 5G RAN Wireless Network Resource Model (NRM) into ONAP. The 5G NRM is defined from the 3GPP standards 3GPP TS28.540 & 3GPP TS28.541 . | Allows for RAN Wireless vendors to use standardized 3GPP support TS28.540/TS28.541 5G NRM parameters | which builds upon the FNIM, UIM specified in 3GPP TS28.620 and TS28.622 The 5G NRM is a common vendor agnostic network model inspired from the standards which provides a common basis for all wireless vendors to have a set of parameters that are in common across the vendor so that service providers have a more uniform set of objects, parameters and models to represent a wireless network. | Allows for RAN Wireless vendors to use standardized 3GPP support TS28.540/TS28.541 5G NRM parameters |
Standards Alignment: StndDefined VES EventStandards Alignment: VES | Development of support for Standard Defined (stndDefined) VES Event. This new domain of a VES event would allow ONAP to support many more standards based & standards defined messages. It opens the possibility for ONAP to support a wide variety of messaging from Optical, Wireless, Core and Transport standardsmessages. It opens the possibility for ONAP to support a wide variety of messaging from Optical, Wireless, Core and Transport standards. "stndDefined" is a new VES domain. And it is described in the VES 7.2 specification VES 7.2 and also in the readthedocs. It also introduces a new field "namespace" to be published onto the DMaaP bus which allows for internal routing of the information coming from xNFs. For example 3GPP_Configuration would indicate a CM type information coming from an xNF. | Allows for Standards Bodies such as 3GPP (RAN Wireless) alignment and support of messaging from xNF messages defined by standards to be compatible with ONAP | ||
Standards Alignment: A1 | ||||
5G NRM (CM) | (No Updates in R7) | |||
E2E Network Slicing |
|
| ||
Bulk PM: PM Control | ||||
Intent Based Network |
|
| ||
PNF | PNF Plug-and-Play | Development of Building Blocks in SO to support PNF Plug and Play Flow. Migration of BPMN Workflow to Building Blocks. | Internal SO development to streamline execution of PNF Plug and Play. Migration of BPMN Workflow to Building Blocks allows for much more streamlined management of SO workflow execution. | |
Onboarding/Pre-onboarding | Enhanced package security ETSI SOL004 option 2 security implemented | Enhanced entire package security Aligned now with ETSI SOL004 standrads. | ||
PNF software upgrade | ||||
Configuration Persistence Service | (Note this has been renamed to Configuration Persistence Service) Proof of Concept developed in R7 to demonstrate key concepts in CPS and also to lay foundational software for CPS. The PoC has:
| Proof of Concept developed in R7 to demonstrate key concepts in CPS and also to lay foundational software for CPS. | ||
CMPv2 | CMPv2 is a standardized certificate based exchange protocol to introduced enhanced security in ONAP. It allows for intra-component security and affect many components. | CMPv2 introduced standardized certificate exchange security into ONAP. | ||
License Management | Licensing Management enhancements allows for ONAP to work with an external licensing service | Licensing Management enhancements allows for ONAP to work with an external licensing service this allows for greater interoperability between service providers & vendors. | ||
sMDONS Extension | ||||
ETSI Alignment |
...