Versions Compared

Old Version 16

changes.mady.by.user Benjamin Cheung

Saved on

compared with

New Version Current

changes.mady.by.user liam burke

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


BUSINESS

...

This section describes Business Drivers for this Use Case.

Executive Summary - A summary for the PM functions:

  • BULK PM develops the capability for the PNF/VNF to send performance measurement data to ONAP. A file ready is sent via VES and the files are pulled via sftp. PNF/VNFs collects performance measurement data periodically (configurable). It also introduces the parsing of files (3GPP defined format) conversion to VES format.
  • REAL-TIME PM -
  • PM DICTIONARY -

Business Impact - It provides a generic ability which ONAP service providers will find useful for the collection of PM information. Performance measurements is viewed as a fundamental capability for Network Elements, "P" in FCAPS. General PM capability most network functions will likely have measurements. The framework of file transfer can be used in future use cases as well.

Business Markets - This capability is added for 5G it is generic and could be used for other services as well. It could be applicable to other products beyond 5G most domains will likely have measurement files including transport.

Funding/Financial Impacts - This capability, once developed, will be able to be used by any service provider deploying and using ONAP. Thus, driving cost savings so that Bulk PM functionality doesn't have to be redeveloped multiple times. This is an enabler for closed-loop automation to collect data to detect anomalous conditions. As such, it can have a large potential OPEX savings impact.

...

DRIVER 

This see the Performance Measurements Use Cases Wiki for the business driver description: PERFORMANCE MEASUREMENTS USE CASES: Bulk, RT, Dictionary


Scope

Continuation of Bulk PM feature from Casablanca. 

Enhancements in Dublin include

  • new 3GPP PM Mapper which will process 3GPP PM XML files to produce VES PM Events in perf3gpp domain
  • robustness and logging enhancements to existing components for improved Bulk PM handling in ONAP (DCAE DFC, DMaaP DR)


...

Project

PTL

JIRA

Description

DCAE

Vijay Venkatesh Kumar

DCAEGEN2-1038: Introduce "3GPP PM Mapper" service

Creation of 3GPP PM Mapper service, including:

  1. 3GPP PM (XML) input and parsing
  2. PM VES Event publication to MR
  3. Error handling (incl. integration with DR)
  4. Configuration handling (incl. integration with SDC DS)
  5. Deployment support (see slide 15 in attachment above):
    1. Central ONAP deployment
    2. Distributed/Edge ONAP deployment with DFC and PM Mapper in edge (see 2, stretch objective)
    3. Distributed/Edge ONAP deployment with DFC in edge, PM Mapper central (see 3a, stretch objective)
DCAEVijay Venkatesh Kumar

DCAEGEN2-1039: DFC enhancements to support Bulk PM

Enhancements to Data File Collector, including:

  1. Retry handling  (incl. DR state interaction handling)
  2. AAF integration
  3. Deployment support (see slide 15 in attachment above)
    1. Central ONAP deployment
    2. Distributed/Edge ONAP deployment with DFC and DR node in edge (see 2 and 3a, stretch objective)
    3. Distributed/Edge ONAP deployment with DFC in edge without DR node in edge (see 3b, stretch objective)
VNFRQTS

Steven wright

VNFRQTS-513: Updated FileReady requirement to add optional re-reporting

Modified VNF reqs for Data File Collector robustness enhancements:

  1. Updated VNF requirement for FileReady to support DFC retry mechanism which relies on xNF reporting all files available for collection be reported in subsequent FileReady events. I.e. not just the new files since the last FileReady was sent. This ensures that if a message or retrieval is missed that DFC is aware of the file and can determine whether it needs to still be collected. See DCAEGEN2-1039: for details of DFC enhancements.
  2. New DFC retry behaviour is optional. Existing Casablanca req (VNFRQTS263) and behaviour continue to be supported. Either existing requirement needs to be updated, or a new requirement for Dublin should be written. E.g. "xNF SHOULD report all files as long as they are available for collection. Recommended period is 24 hours."
DMaaPBhanu Ramesh

DMAAP-912: Data Router updates to support Bulk PM

Data Router enhancements to support Bulk PM use cases, including:

  1. Query of publication history (new API, for use by Data File Collector)
  2. Update to prov API to support 1 above. 
  3. Optional consumer compression feed handling  (new optional API, for use by 3GPP PM Mapper)
  4. OOM integration (sub-charts for supported deployments)
  5. Deployment support (see slide 15 in attachment above)
    1. Distributed/Edge ONAP deployment pub/sub and DR node in edge (see 2)
    2. Distributed/Edge ONAP deployment pub in edge, sub in edge or central, without DR node in edge (see 3a, stretch objective)
    3. Distributed/Edge ONAP deployment pub/sub in edge or central, without DR node in edge (see 3b, stretch objective)
  6. Maria DB investigation (as input to potential El Alto work item to improve robustness)
SDCOfir Sonsino

SDC-2011: Design Studio (DCAE-DS) support for Bulk PM

SDC and DS support for PM Dictionary and PM Mapper configuration, including:

  1. PM Dictionary artifact handling
  2. UI/Form support to create the mapper configuration file


Test Status

E2E Test: 

Tests per component:

Performance Verification: