5G NF FM Meta Data:

Scope: 

Gain approval for the content and delivery of the FM Meta Data as part of the FM YAML Registration for a 5G NF to ONAP.  This assumes that the work to support the collection and publication of PNF artifacts is covered under the PNF Onboarding Package 5G USE Case Work Item—it is not addressed here.

Next Steps: 

The Fault Event will carry key information about a fault that is occurring.  However, for efficiency sake, information that does not change but is still important for understanding the fault and determining an appropriate response should be available to the Policy creators and potentially analytics applications.  In legacy RAN products this information was provided in an FM Dictionary/Meta Data File.  In ONAP, the information is recommended to be provided as part of the YAML Registration.  In this exercise the goal is to identify fields and provide common names and definitions for the content of those fields. Below are steps envisioned

• Finalize the fields applicable for FM meta-data (those that were provided in dictionaries in the past) and gain agreement that this information should be provided by the NF.
• Identify which fields are mandatory and with fields are optional. 
• Review with the community the meta data content including which fields are already covered in the fault event. 
• Present again the proposal to have the fault event include this information in the registration YAML.
• Publish requirements on NFs to provide the FM Dictionary information in the Fault Event registration YAML (NOTE this approach means that there is NOT a separate FM Dictionary artifact that is delivered as part of NF onboarding.

Projects Impacted:

VNF Requirements, DCAE (VES Registration Document needs to be updated), potentially policy so that the processing of the YAML with the use of the dictionary fields is automated (stretch goal).  This approach does not require SDC or modeling changes because NFs already have to provide registration YAMLs.  This is extending what that YAML provides.  No new things have to be catalogued or defined.

Associated Files:

5G PM Dictionary:

Scope:

• Obtain agreement on the PM Dictionary content
  • What fields are in the PM Dictionary and whether they are mandatory or optional
• Obtain agreement on the PM Dictionary format
  • YAML schema
  • Whether PM Dictionary is in the Event Registration YAML or is a separate artifact
• Artifact processing
  • Support the onboarding and cataloging of PM Dictionary for VNFs and PNFs
• Artifact usage
  • Stretch goal - Operator ability to show PM Dictionary on a GUI in human-readable form
  • Stretch goal – Be able to use PM Dictionary to create Policies for measurement TCAs
  • Future release – Operator ability to select measurements for RTPM and PM Mapper and generate configuration
  • Future release – Ability for Analytics Applications to use PM Dictionary directly

Casablanca Progress:

PM Dictionary proposal has been presented to ONAP community on multiple occasions:

• SDC – Aug 14 2018
• Modeling Subcommittee Resource Info Model – Sep 10 2018
• 5G Use Case Subcommittee – Sep 20 2018
  • Received comments from Ericsson and incorporated them into the proposal
• VES – Oct 10 2018

All comments have been incorporated into the proposal.

Next Steps:

1. Determine the process to get approval for this proposal
2. Present to Modeling subcommittee to approve content and format
3. Present to other Impacted Projects for commitment

Projects Impacted:

• Modeling – agreement on content and format
• SDC – onboarding and cataloging of PM Dictionary artifact
• VES – document the PM Dictionary format and content
• NF Requirements – requirement for 3GPP compliant NFs to provide a PM Dictionary in the proper format and content as part of NF package at onboarding
• GUI – display PM Dictionary in human-readable form (What GUI? What project?)

PM Dictionary Proposal:

PM Dictionary Example: