...
Key Contacts - Oskar Malm, Michela Bevilacqua
Executive Summary - CM mirror use case for xNFs managed by ONAP will provide to ONAP an updated version of the xNF CM data. The initial focus for Rel 8 is to support initial data synchronization when a new xNF instance is created in ONAP
Business Impact - xNF CM control is a critical business function because it is vital to enable different OSS services
Business Markets - All operators and service providers that want to use ONAP for CM operations on xNF can benefit from this common centralized configuration persistency service.
The Network CM Proxy (NCMP) is a component in CPS that will be responsible for Network CM access and synchronization in order that CPS CM data will be maintained aligned with CM data in the network (e.g. xNF instances). The complete solution will rely on integration with other ONAP components such as SDNC. The Network CM Proxy will also in turn provide an interface to other ONAP applications to access the network CM data.
NCMP is an evolution of the CPS NF Proxy component first introduced in Rel H. For release I it is proposed to continue work on use cases such as initial data synchronization and reading and writing network CM data. Development of this feature is expected to span multiple releases
Business Impact - CM data management is a central function for many applications and use cases. Network CM Proxy provides a common solution for Network CM data management in order to simplify the accessibility from any upper layer components
Business Markets - This feature applies to any domain (wireless, transport, optical, and wireline) that ONAP may manage
Funding/Financial Impacts - This feature represents a potential Operating Expense (OPEX) savings for operators because of the ability to retrieve network information and Funding/Financial Impacts - CM data collection control can provide OPEX savings for operators due to configure networks saving time and expenses.
Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
A1 Adapter and Policy Management Extension (ORAN/ONAP/3GPP Harmonization)
ITEM | DETAILS |
|---|---|
| Presentation | |
| Recording mp4 | |
| Audio only |
Key Contacts - John Keeney, Michela Bevilacqua
Executive Summary - This requirement enhances the A1 interface capabilities provided in Rel 6 as part of 5G/ORAN & 3GPP Standards Harmonization requirement ( REQ-38) and extended in Rel 7 with the introduction of A1 policy management. O-RAN has defined A1 interface specification in the context of the management of 5G RAN elements to provide intent based policies for optimization of the RAN network performance. Planned enhancements for Rel 8 include support of new A1 interface version in alignment to O-RAN alliance and common logging/audit.
Business Impact - Continuing the convergency between ONAP and ORAN for A1 interface to used by all service providers and avoid duplicate development efforts.
Business Markets - Enhanced A1 capabilities, once developed, will be useable by any service provider deploying and using ONAP.
Funding/Financial Impacts - A1 interface provides a flexible way for the operator to manage wide area RAN network optimization, reducing capex investment needs.
Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.