Page History

Support   for PNF   - Onboarding

Disaggregated 5G RAN consists of hybrid network elements (PNF   and VNF) and will require a cloud infrastructure deployment at the edge.  This sub-case will expand/enhance ONAP   capabilities to support limited lifecycle management aspects of PNF   (including enhancements in SDK / certification, PNF onboarding, and SO, DCAE,   A&AI support for PNF). This requires addressing the missing platform   capabilities:
    1.Enhanced Platform Awareness  (e.g.   access to real-time VIM features)

    2.Enhance SDC (e.g. PNF onboarding)
    3.Enhance SO (e.g. PNF, nested services )
    4.Integrated design environment (e.g. complex service composition)
    5.PNF Modeling Capability (e.g. PNF modeling, connections)

5G SubCase1 participants:

AT&T
Amdocs
Ciena
Ericsson
Intel

Wind River

Support for PNF - Data Collection & Monitoring

Access to real-time VIM features for VNFs

Many providers are interested in using ONAP to manage the   general concept of Slicing (Extending the cloud notion of sharing   network/compute/storage to sharing network functions and Services implemented   across PNFs & VNFs). Supporting such a generic slicing concept could   require ONAP enhancements in the areas of SDC/AAI modeling and service   definition, lifecycle management of slices (whether done within the existing   SO/controller context or via a new layer of control e.g. slice controller)   since slices could have their own state, metrics and scaling procedures   different and distinct from those of the underlying network functions (e.g.   service/slice across multiple NFs from different providers). This requires   addressing the missing platform capabilities:
    2.Enhance SDC (e.g. PNF onboarding)
    3.Enhance SO (e.g. PNF, nested services )
    4.Integrated design environment (e.g. complex service composition)
    5.PNF Modeling Capability (e.g. PNF modeling, connections)
    6.Service Aggregation Capability (e.g. complex service hierarchy)
    7.Service Chaining Capability (e.g. chaining across multiple clouds,   service path)
    8.Service Modification Capability (e.g. modifying without downtime)

5G SubCase2 participants:

AT&T
Amdocs
China Mobile
Ciena
Cisco
Ericsson
Huawei
Intel

Wind River

ZTE

Many providers are interested in flexibly   deploying network optimization functions from various vendors into the ONAP   framework.  We need such an ONAP   Optimization Framework (OOF) to support two aspects. The first one is for the   optimal placement of 5G virtual network functions. The second one is for   performance optimization, where SON is a key functionality.  Since optimization problems in general have   a common structure (viz. maximizing/minimizing an objective subject to   various constraints), a framework exploiting this commonality would render   significant efficiency in creating optimization functions in these two areas.   Also, when different optimization capabilities are deployed, there is a need   for potential conflict resolution across these different schemes (both at   design and run time). Hence the OOF should support policy-driven optimization   capabilities that can be quickly developed and on-boarded. To support OOF,   the data collection/processing in DCAE need to satisfy the needed latency   requirements based on various use cases. Also, Multi Cloud should support export of aggregate infrastructure statistics (tenant etc.) through an efficient push mechanism.

5G SubCase3 participants:

AT&T

Amdocs
Cisco
Intel
VMware

Wind River

New+

Enhancement