Skip to content

Home

Jump to bottom
Gino Carrozzo edited this page Aug 6, 2019 · 5 revisions

5g-catalogue wiki!

The 5G App and Service Catalogue is a catalogue for SDN/NFV applications and service package descriptors which provides all the functionalities needed for the management of NSDs and App/VNF Packages (i.e. on-boarding, removal, queries, enabling and disabling of specific descriptors or packages).

The catalogue originates from the following problem areas

  • Problem #1: High fragmentation in VNF packages and NSD formats/contents
    • Multiple Formats (TOSCA vs. YANG/JSON, JuJu charms vs. cloud-init + Day1/Day2 configuration)
    • Different approaches to encode variables (e.g. for conf, mon, output, auto-scaling rules)
    • Need to support NFVI specific extensions (SR-IOV, DPDK, containers instead of VMs, etc.)
    • Need to support also non NFV apps: SDN-Apps, MEC apps(AppD), etc.
    • Need to be able specify application-specific monitoring params (not for the VM but for the service/function running on it)
  • Problem #2: NFV standards mostly refer to single domain scenarios
    • Typically NFV Service Providers own a complete NFVI and act as Infrastructure providers and NFV operators.
    • Difficult to compose services from different providers
    • Difficult tointroduce new virtual applications from the customers (i.e. the Vertical)
    • NS delivery limited by the characteristics and capabilities of the provider’s NFVI geographical coverage (i.e. where edge platforms are w.r.t. the service to be delivered)
    • Limitation in knowledge of available functions (i.e. which functions are available in my SP domain and which a could be borrowed from a federated domain)

The 5G App& Service Catalogue allow:

  • service customers to bring their own VNFs or VApps into the SP’s MANO
  • to compose services from multiple service providers, each with its own specialized offer of VNF(s) and NS(s)
  • to use a generalized standard format and contents for descriptors and translate it into the various descriptions needed by the different targets (e.g. different NFVO)
  • to adopt core standard descriptions for the VNF, NS, MEC App that can be instantiated based on IFA-11, SOL-004, etc.
  • to add NFVI capabilities (e.g. placing of MEC platforms, HW accelerations, GPU availability and where, etc.)
  • to add description of additional VNF/VApp characteristics not related to LCM (e.g. App monitoring/configuration after instantiation)

Key features (design objectives)

  • Unified and extendable format for descriptors
    • VNF packages [ETSI GS NFV IFA 011, ETSI GS SOL 004]
    • MEC apps [ETSI GS MEC 010-2]
    • virtual apps, virtual functions
    • NSs [ETSI GS NFV IFA 014, ETSI GS SOL OO1 draft]
  • Package descriptors
    • Common base + domain specific extensions for app config/monit, NFVI options, etc.
  • MANO domain-specific translation from common to specific descriptors
    • Support OSM, Tacker, etc.
  • Extended Interfaces to MANO (NFVO, VIM)
    • Base LCM behaviors based on basic NFV interfaces and descriptors
    • Additional behaviors (e.g. load images, configure hw acceleration, other tuning on NFVI, etc.) based on additional interfaces and descriptors
  • Discovery, advertising, publishing, validation of descriptors across catalogues from different providers

NAVIGATION

Clone this wiki locally