...

Organization Mgmt, Sales Strategies - (It is suggested that you use the following wording): There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.

Control Loop LCM

R8 PRESENTATION:

Key Contacts -  Michela Bevilacqua, Liam Fallon, Zu Qiang (Ericsson)

Executive Summary - CLAMP (Control Loop Automation Management Platform) functionalities, recently moved to Policy project , want to provide a Control Loop Lifecycle management architecture. A control Loop is a key concept for Automation and assurance Use Cases and remain a top priority for ONAP as an automation platform. This requirement wants to improve Control Loop LCM architecture focusing on an abstract CL management logic,  isolating CL logic vs ONAP component logic, providing a common CL Design time catalogue with a  generic CL definition, and elaborate API to integrate with other design systems as well as 3PP component integration. PoCs have been progressed in ONAP Rel G and H in this area, CL LCM redesign has reached a relevant viable set of features and it is ready to be moved in Rel I to mainstream as part of the Policy framework.

Business Impact - Deployment and orchestration of automation and control loop use cases across CNFs,  VNFs and PNFs in a model driven way simplifies the network management. Enables operators and service providers to manage the Life Cycle of a Network Service. Assuring continuity of operation of services is crucial for production and carrier grade environments. The actualization or upgrades of software and in consequence required changes in the service model is a natural part of service instance life cycle. Without the support of ONAP service update with schema change, service life cycle management by ONAP can be very difficult which can impact the quality and continuity of services.

Business Markets - All operators and service providers that are using ONAP for automation and assurance.

Funding/Financial Impacts - CL LCM wants to reduce operational expense  and its abstraction will provide an added value with multiple  integration points.

Organization Mgmt, Sales Strategies - (It is suggested that you use the following wording): There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. (This would typically describe the "WHO", but because use cases are all deployed with ONAP itself, these two areas come with the actual ONAP deployment and uses the organizational management and sales strategies of a particular service provider's ONAP deployment)

PM Data Collection Control: Subscription update

Key Contacts - Mark Scott, Zu Qiang (Ericsson), Michela Bevilacqua

Executive Summary - PM data collection control provides network operators with a dynamic and more efficient way to configure performance measurement collection on a selected subset of  PNFs/VNFs in the network and complements the existing PM data collection and processing capabilities in ONAP/DCAE. An initial version has been delivered in Rel 6 (REQ-129) then enhanced in Rel 7 (REQ-381). Planned enhancements for Rel 8 intend to improve the (PMSH) subscription management about subscription update.

Business Impact - PM control is a critical business function because it is vital to enable the PM data collection in ONAP.

Business Markets - All operators and service providers that want to use ONAP for PM data collection.

Funding/Financial Impacts - PM data collection control can provide OPEX savings for operators due to increased automation of a critical function. 

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.